Licences & Acknowledgements

About this page

Last updated: 23 September 2026.

This page is an inventory of two things: the third-party services Pionare actually uses today, and the open-source software included in the Pionare iOS app (version 1.0.0, build 46). It names the services that are in use today. Where we have built an integration that is not switched on, and a user's data would reach a new company if it were, we say so and mark it. Services we no longer use have been removed.

How your data is handled is described in our Privacy Policy. The rules for using the app are in our Terms of Use.

AI providers

Pionare does not run its own image or video models. Two providers are involved, and they receive different things.

Replicate, Inc. — United States

Every image and video Pionare generates is requested through Replicate. The models we use are published by other companies — OpenAI, Google, ByteDance and xAI — and where Replicate serves a model on its publisher's behalf rather than on its own hardware, it passes your photo to that publisher as its sub-processor. We are confirming with Replicate exactly which of the models we use are served that way, and will name the recipients here once we have it in writing. The photo you upload, the photos you add to a personal profile, and the text of your description are sent to Replicate for the generation you asked for. The file itself is not handed over as an upload: it is stored in our own object storage and Replicate fetches it over the internet from a public link, which is how these models take an image (our Privacy Policy explains what that means for access to your files). We do not send Replicate your email address, your name, your device identifier or your advertising identifier. The link we hand it does contain an internal account reference in its path — the folder your files are filed under — and that reference is the same on every upload you make, so a provider could tell that two photos came from the same account. It cannot resolve that reference to you. We would rather state that than write "nothing that identifies you", and we are changing the way those links are built.

A photo is sent as the file you chose, so any information your camera embedded in it — the time it was taken, and a location if your camera records one — can go with it. We do not read that information and we do not currently remove it. Photos on the ordinary generation path are re-encoded on your device before upload, which drops most of it; photos you add to a personal profile are not re-encoded, so assume it travels. We are adding a step that strips embedded metadata on upload.

OpenAI, L.L.C. — United States

We reach OpenAI in two different ways, and it is worth separating them.

Directly. First, the text of your description when you tap "Rewrite with AI" — that text is sent to OpenAI, rewritten, and the rewritten text is what we then use for generation. Using the assistant is optional and no photo is attached to it. Second, the optional gender-detection step on a personal profile: where that step is configured to use an OpenAI vision model, the links to the profile's photos are sent to it and it is asked to infer the gender recorded on the profile. Which model fills that step is a setting in our own dashboard; where it holds a Replicate-hosted model instead, OpenAI is not involved in it at all.

Through Replicate. The model behind the great majority of photo effects is an OpenAI model, which we reach through Replicate rather than by calling OpenAI ourselves. So while we do not send your photo to OpenAI directly for generation, an OpenAI model is what processes most photos in Pionare. See the Models section below.

As with Replicate, we send no email address, no name and no device identifier; where we send a link, that link contains the internal account reference described above.

Each provider applies its own content and safety policies to what is submitted and to what is produced, and may decline to generate certain material.

No AI provider other than these two receives your photos, the photos behind a personal profile, or the text you write — with the qualification stated above, that Replicate may run a model through the company that made it. Earlier versions of this page listed a third provider that in fact received nothing; it has been removed. Separately, and not as an AI matter: a link to a finished result travels inside the push notification that tells you it is ready, so Apple's and Google's push services handle that link in transit — see the section on our own services below. If the list of AI providers changes, we will update this page and the Privacy Policy to name the new one.

Models

The companies whose models run on your photo are OpenAI, Google, ByteDance and xAI, and every one of them is reached through Replicate. That is the part we commit to keeping accurate here. Which exact model a given feature uses is live configuration we can change from our own dashboard without releasing a new app, so the identifiers below are examples current on the date at the top of this page rather than a closed list:

openai/gpt-image-2 — most photo effects and styles.
google/nano-banana-2 — a small number of photo effects.
google/nano-banana — the style menu on the Edit screen.
bytedance/seedance-1.5-pro — video generation.
xai/grok-imagine-video-1.5 — video generation.

Images made from a description you write on the Create screen, and the avatar and banner generated for a personal profile, are produced by a model from this same set; which one is a setting we can change without updating the app.

We use these models under Replicate's terms and under each model's own licence as published on its Replicate model page. A model name identifies who created the model; it does not describe a direct commercial relationship between Pionare and that company. Replicate is the company we send the request to, and it either runs the model itself or forwards the request to the model's publisher, as explained above.

Style names in Pionare describe visual techniques, looks and genres. Where a style name resembles a product, a brand or a franchise, it is used only to describe the look the style produces. Pionare is not affiliated with, endorsed by or sponsored by any studio, franchise, brand, manufacturer or artist, and their trademarks remain the property of their owners. We are reviewing the style catalogue and renaming the titles where a descriptive name would do the same job; if a name in the app concerns you, write to us at the address at the foot of this page.

Other services we use

DigitalOcean, LLC — hosting, database and object storage

Our API, our MongoDB database and the Spaces object storage bucket that holds uploaded photos, personal-profile photos and generated results all run on DigitalOcean, in its Frankfurt region in Germany. Privacy Policy

Cloudflare, Inc. — content delivery and network protection

Requests to pionare.app and to our API pass through Cloudflare's network, which sits in front of our servers as part of our hosting provider's platform. It terminates the connection and relays the request — including the body of a photo upload — so it sees the connection and your IP address in transit. It does not store your photos or your account data. Privacy Policy

Google LLC — Firebase Authentication, Firebase Cloud Messaging, Sign in with Google

Every Pionare account lives in Firebase Authentication, whichever of the three sign-in methods you use. For email and password, Firebase creates and checks the password — we never receive or store it. Firebase Cloud Messaging delivers the notification that tells you a result is ready. Sign in with Google handles the Google button. We use Firebase only for sign-in and push delivery. The Firebase SDK's own supporting components ship alongside those two — including a Firebase installation identifier, which is what routes a notification to your device. We do not include Firebase Analytics and we do not include Firebase Crashlytics. Firebase privacy and security · Google Privacy Policy

Apple Inc. — App Store, in-app purchase, Sign in with Apple, push delivery, Vision framework

Apple distributes the app, is the merchant for everything bought inside it on iPhone, provides Sign in with Apple, and delivers notifications through the Apple Push Notification service. Apple's Vision framework is also used on your device: when you pick photos for a photo effect on the app's photo-picker screen, Pionare asks Vision how many faces are in each one and drops photos with no visible face. It is a convenience filter so you do not spend credits on a photo the effect cannot use — not a check on who is in the photo — and if it cannot run, your selection passes through unchanged. The personal-profile flow does not run it. The check runs entirely on your iPhone and its result is not sent to Apple, to us, or to anyone else. Apple Privacy Policy

Adapty Tech Inc. — subscriptions, paywalls and entitlements

Adapty presents the purchase screens and keeps track of subscription state. It receives an opaque purchase profile identifier, purchase and entitlement status, and your AppsFlyer install identifier, which we hand it so that a subscription can be attributed to the campaign that brought you to the app. We never send Adapty your email address, your name, your photos or anything you generate. Adapty is also the component configured to report subscription revenue back to AppsFlyer server-to-server, using that identifier; whether a given server-side integration is switched on is a setting in Adapty's dashboard rather than something in our code. Privacy Policy

AppsFlyer Ltd. — install attribution

AppsFlyer connects an install back to the advertisement it came from. It starts only after you sign in — before that, the SDK is not running and sends nothing — and it is given your account identifier as its customer user id. Pionare sends AppsFlyer no custom events of its own: no screen you open and no feature you use is reported to it. Whether your device advertising identifier is available to it depends on your answer to the iOS tracking prompt. Privacy Policy

Paddle — merchant of record for web purchases (not active)

Web purchasing is not available today: pionare.app has no checkout and no pricing page, the Paddle integration is switched off in production, and Paddle currently receives nothing from Pionare. We list it only because the integration exists and a user's payment data would reach a new company if it were switched on. If we launch it, the checkout will be operated by Paddle as merchant of record, hosting the checkout and collecting the applicable taxes; we will name the exact contracting entity here before it carries a real payment. Privacy Policy

Pionare contains no advertising SDK, no analytics SDK other than the attribution one named above, and no crash-reporting or error-monitoring service. Nothing in the app or on our servers sends crash reports to a third party. Several AI integrations exist in our backend that are not switched on and receive nothing today. Two of them involve a company already named above: a direct image path to OpenAI that no live feature uses, and a step that would send an uploaded photo to an OpenAI vision model to enrich the prompt, which is off on every feature. Two involve companies that are not otherwise part of the Service, and we name them so the list is honest about where your data could go next: Higgsfield, a connection to its image and video models that we finished building on 23 September 2026, for which no credentials are configured and to which no request has ever been sent; and fal.ai, operated by Features and Labels, Inc., which an earlier version of our legal pages named as a current provider even though it has never received any of your data. Nothing reaches either company today. If we switch one on, this page and the Privacy Policy change first, and the date at the head of each of them changes with it.

Services that are ours, not a vendor's

Two services the app depends on are our own software, deployed alongside our API on DigitalOcean rather than bought from anyone: a purchase service, which holds credits, subscriptions and entitlements, and a notification service, which holds your push registrations and a record of the notifications it has sent, including the link each one carried. Naming them here is for completeness — they are not third parties. The notification a finished generation triggers carries the link to that image or video, and our notification service hands it to Apple's push service or to Firebase Cloud Messaging for delivery to your device.

Open-source components in the iOS app

The Pionare iOS app is built in two layers, and both carry third-party open-source code, so both are listed. The inventory below is a snapshot of version 1.0.0, build 46; it changes whenever a dependency does, and we regenerate it with each release. Each package remains the property of its own copyright holders and its own licence continues to apply.

Native libraries linked into the build (51) — taken from the acknowledgements file the build itself generates for the shipped app target, grouped by the licence each one is actually under.

Apache License 2.0 — 25 libraries

AppAuth
AppCheckCore
fast_float
Firebase
FirebaseAppCheckInterop
FirebaseAuth
FirebaseAuthInterop
FirebaseCore
FirebaseCoreExtension
FirebaseCoreInternal
FirebaseInstallations
FirebaseMessaging
GoogleDataTransport
GoogleSignIn
GoogleUtilities
GTMAppAuth
GTMSessionFetcher
PromisesObjC
PromisesSwift
RCT-Folly
RecaptchaInterop
RNFBApp
RNFBAuth
RNFBMessaging
ZXingObjC

MIT licence — 18 libraries

fmt
hermes-engine
React
React-Core
react-native-adapty-sdk
react-native-appsflyer
react-native-safe-area-context
RNCAsyncStorage
RNGestureHandler
RNGoogleSignin
RNReanimated
RNScreens
RNSVG
RNWorklets
SDWebImage
SDWebImageAVIFCoder
SDWebImageSVGCoder
SDWebImageWebPCoder

BSD 3-Clause licence — 4 libraries

DoubleConversion
glog
libwebp
SocketRocket

BSD 2-Clause licence — 1 library

libavif

Boost Software License 1.0 — 1 library

boost

zlib-style licence — 1 library

nanopb

Not open source — 1 library. AppsFlyerFramework, the AppsFlyer iOS SDK, is closed-source software included under licence from AppsFlyer Ltd. Its notice reads "Copyright 2018 AppsFlyer Ltd. All rights reserved." It is listed here for completeness, not as an open-source component.

JavaScript packages we depend on directly (54) — the application layer. Two of these, react-dom and react-native-web, are part of the dependency tree but have no native counterpart in the iOS build.

MIT licence — 51 packages

@babel/runtime
@expo/vector-icons
@react-native-async-storage/async-storage
@react-native-google-signin/google-signin
@react-navigation/bottom-tabs
@react-navigation/native
@react-navigation/stack
@reduxjs/toolkit
async-mutex
expo
expo-apple-authentication
expo-application
expo-asset
expo-blur
expo-build-properties
expo-camera
expo-constants
expo-crypto
expo-file-system
expo-font
expo-image
expo-image-manipulator
expo-image-picker
expo-linear-gradient
expo-media-library
expo-modules-core
expo-secure-store
expo-sharing
expo-splash-screen
expo-status-bar
expo-store-review
expo-tracking-transparency
expo-video
face-detection
i18next
react
react-dom
react-i18next
react-native
react-native-adapty
react-native-appsflyer
react-native-gesture-handler
react-native-reanimated
react-native-safe-area-context
react-native-screens
react-native-svg
react-native-web
react-native-worklets
react-redux
redux-persist
zustand

Apache License 2.0 — 3 packages

@react-native-firebase/app
@react-native-firebase/auth
@react-native-firebase/messaging

Copyright notices. Every package above carries its own copyright line, and every one of those lines is reproduced verbatim in the acknowledgements file generated for the shipped build. That file is the authoritative notice document and we will send it to anyone who asks, at the address at the foot of this page. The full text of each licence used is set out below, except the Apache License 2.0, which is long and unchanged from the canonical version we link to — we will send that in full on request too.

Modifications. The three @react-native-firebase packages listed above are shipped in a modified form. We apply small patches to four of their iOS source files so that they compile against the version of React Native this build uses; the change is limited to build compatibility and alters no behaviour, no data handling and no network call. The patches are kept in the patches directory of our source tree and are available on request from the address at the foot of this page.

Components that are ours. Two of the modules compiled into the app are our own work rather than a third party's, and so are not listed above: @pio/api-contracts, the shared type definitions between our app and our API, and storekit-ownership, a small native module that asks StoreKit which Apple Account a purchase belongs to. The face-detection module, which runs Apple's Vision face check on your device, is not ours: it is a third-party module published under the MIT licence by Frukanfed <[email protected]>, vendored into our source tree rather than installed from a registry, and it is listed in the MIT group above.

MIT licence

The following notice applies to each MIT-licensed package listed above, with copyright held by that package's own authors and contributors as stated in the generated acknowledgements file:

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

BSD 2-Clause licence

The following notice applies to the BSD 2-Clause library listed above, with copyright held by its own authors:

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

BSD 3-Clause licence

The following notice applies to each BSD 3-Clause library listed above, with copyright held by its own authors:

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

Boost Software License 1.0

Boost Software License — Version 1.0, August 17th, 2003

Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the "Software") to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following:

The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

zlib-style licence

The following notice applies to nanopb:

This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.

Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:

1. The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required.

2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software.

3. This notice may not be removed or altered from any source distribution.

Apache License 2.0

The following applies to every Apache-2.0 library and package listed above, each with the copyright held by its own authors as stated in the generated acknowledgements file.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use these files except in compliance with the License. You may obtain the complete text of the License at apache.org/licenses/LICENSE-2.0, and we will send you a copy on request.

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Content in the app

The styles, categories, preset content, sample imagery, name and logo used in Pionare are created by or licensed to TECHNOGRADE YAZILIM TEKNOLOJİ VE TİCARET LİMİTED ŞİRKETİ, Merkez Mah., Feriköy Fırın Sok. No: 69/2, Şişli, İstanbul, Türkiye.

Trademarks

Apple, the Apple logo, iPhone, iPad and App Store are trademarks of Apple Inc., registered in the U.S. and other countries. Pionare is not affiliated with, endorsed by, or sponsored by Apple Inc. Google, Firebase and Android are trademarks of Google LLC. Replicate, OpenAI, Google, ByteDance, xAI, DigitalOcean, Cloudflare, Adapty, AppsFlyer and Paddle are trademarks of their respective owners; naming a service here indicates only that we use it, and naming a model's publisher indicates only who published the model. All other trademarks are the property of their respective owners.

Contact

Questions about licensing or attribution, or a request for the source of any modification described above: [email protected].