Privacy Policy
This page is available in English and German.
Last updated: November 10, 2026
This privacy policy explains how we process personal data when you visit the website empose.app and when you use the app Empose for iOS and Android ("the App"). Where the iOS and Android versions differ, the relevant section says so. Section 2 covers the website, the following sections cover the App; your rights (Section 11) apply to both.
1. Controller
The controller responsible for data processing within the meaning of Art. 4 (7) GDPR is:
Hakan BayindirBreslauerstraße 19b
54516 Wittlich
Germany
Email: hello@empose.app
Website: https://empose.app
"We" and "us" in this policy refer to the controller named above.
2. Website empose.app
2.1 Hosting (Cloudflare)
The website empose.app is hosted by Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA, which acts as our processor. When you request a page, Cloudflare processes the data that is technically necessary to deliver the website and keep it secure: your IP address, the date and time of the request, the requested URL, the referrer (the page you came from) and your browser's user agent.
- Legal basis: Art. 6 (1)(f) GDPR. Our legitimate interest is to deliver the website reliably and to protect it against attacks.
- Retention: Cloudflare keeps these logs only briefly.
- Third-country transfer: data may be processed in the USA. Cloudflare is certified under the EU-U.S. Data Privacy Framework (see also Section 6).
2.2 No cookies, analytics or tracking
The website sets no cookies and uses no analytics, no tracking and no advertising. Fonts and images are served from empose.app itself; we do not embed Google Fonts or any other third-party content.
2.3 Links to the App Store
The website links to Empose in the Apple App Store. Apple only receives data when you click such a link and open the App Store. From then on, Apple's own privacy policy applies: https://www.apple.com/legal/privacy/
2.4 Contact by email
If you write to hello@empose.app, your message is forwarded via Cloudflare Email Routing to our mailbox. We process your email address, the content of your message and any other details you include in order to answer your request.
- Legal basis: Art. 6 (1)(b) GDPR if your request concerns a contract with us or steps prior to entering into one; otherwise Art. 6 (1)(f) GDPR, based on our legitimate interest in answering inquiries.
- Retention: we delete your message once it is no longer needed, unless statutory retention obligations require us to keep it.
3. Overview of Processing Activities in the App
Empose is a photography app with two parts: pose guides shown over the live camera (processed entirely on your device — camera frames never leave your device) and an AI Studio that restyles a photo you select using generative AI — as a whole-photo Look, as Styling that changes single features such as the hair color or lips (Section 4.8), or as a pose change that moves the person into a pose from the App's library (Section 4.9). You can also put a photo of your choice over the camera as a photo guide (it never leaves your device), or turn it into your own pose with My Poses — a mannequin drawn by generative AI (Section 4.5). In doing so, we process the following data:
| Data Category | Purpose | Legal Basis | Recipients |
|---|---|---|---|
| Photo you select for an AI Look, Styling or pose change | AI image generation, display of your creations | Art. 6 (1)(b) GDPR | Cloudflare (R2, Worker), OpenAI (Images API) |
| Photo you turn into a mannequin pose (My Poses), optional note for a re-render | Drawing the mannequin, writing its name, steps and camera tip in your app language | Art. 6 (1)(b) GDPR | Cloudflare (R2, Worker), OpenAI (Images API, text model) |
| Photo guide (camera) | Showing the photo over the live camera | — (stays on your device) | None |
| Generated result image | Delivery to the App, display of your creations | Art. 6 (1)(b) GDPR | Cloudflare (R2), Google (Firestore: metadata only) |
| Anonymous Firebase user ID (UID) | Authenticating requests from your app instance | Art. 6 (1)(b) GDPR | Google (Firebase Auth), Cloudflare |
| Random Empose app user ID (UUID) | Associating creations, AI credits, and purchases with your app instance | Art. 6 (1)(b) GDPR | Cloudflare, RevenueCat, Google (Firestore) |
| Purchase information (App Store or Google Play transaction) | Processing subscriptions, restoring purchases, AI credit assignment | Art. 6 (1)(b) GDPR | Apple or Google, RevenueCat |
| Look/template ID, image dimensions, timestamps, status | Displaying your creation history, error analysis | Art. 6 (1)(b) GDPR | Google (Firestore) |
| Expo push token | Push notification when a generation is finished | Art. 6 (1)(a) GDPR | Expo (push service), Apple Push Notification Service (iOS), Google Firebase Cloud Messaging (Android) |
| Usage analytics and crash reports | App stability and improvement | Art. 6 (1)(f) GDPR | Google (Firebase Analytics, Crashlytics) |
| Feedback you send from Settings, with your app user ID, app version, iOS or Android version, device model, app language and subscription status | Reading and answering product feedback; filtering spam and abuse | Art. 6 (1)(f) GDPR | Cloudflare (Worker, Email Routing), OpenAI (text model), Google (Gmail inbox of the team) |
| Creator application: name, channel (platform, handle, follower range), e-mail address, optional message, app user ID and app details | Reviewing the application and contacting you about a paid collaboration | Art. 6 (1)(b) GDPR (steps prior to a contract) | Cloudflare (Worker, KV, Email Routing), OpenAI (text model), Google (Gmail inbox of the team) |
| iOS only: advertising ID (IDFA), device information (e.g. device model, iOS version, app version, IP address) and two app events: onboarding completed, and the start of a trial or subscription with price, currency and product ID. Only if you allow tracking. | Measuring which TikTok ad campaign led to an install and purchase (ad attribution) | Art. 6 (1)(a) GDPR, § 25 (1) TDDDG (your consent via Apple's tracking prompt) | TikTok |
| iOS only: anonymous SKAdNetwork values (install, onboarding, trial, subscription) | Counting which ad campaign led to installs and purchases, without identifying you | Art. 6 (1)(f) GDPR, insofar as personal data is concerned at all | Apple (sends an anonymised, delayed report to the ad network) |
| Error and server logs (IP address, time, status code) | Operational security, troubleshooting | Art. 6 (1)(f) GDPR | Cloudflare |
In the App, apart from a creator application you choose to send (Section 4.11), we collect no real names, no email addresses, no location data and no contacts, and no cross-app advertising ID unless you allow tracking (Section 5.3). Sign-in to Firebase is fully anonymous (no account, no passwords). There is no free-text prompt input in the App — the AI applies only predefined, curated style templates. The one exception is an optional short note when you ask for a mannequin to be drawn again (e.g. "the head should turn toward the camera"); our backend turns it into a description of the pose for the image model. Feedback you write in Settings is free text too, but it never reaches an image model (Section 4.10).
4. Processing of Photos and Generated Images
4.1 Process
- You select a photo from your library or capture a new one. The pose-guide camera itself runs entirely on your device; nothing is uploaded from it.
- Only when you actively confirm and tap Generate — and only if you hold an active Premium subscription — is the photo transmitted encrypted (HTTPS/TLS) to our backend (Cloudflare Worker) and stored in Cloudflare R2 under a random key bound to your app user ID (users/{your-ID}/sources/{random-ID}.jpg). Without an active subscription, nothing is uploaded.
- For generation, the Worker sends the photo together with the predefined style instruction of the Look you chose to the OpenAI Images API (model gpt-image-2.5-flare). The result is stored in Cloudflare R2 under users/{your-ID}/results/{generation-id}.jpg.
- A metadata record is created in Google Firestore (collection "generations"): your IDs (Section 3), the Look/template ID, image dimensions, timestamps and status. The photos themselves are never stored in Firestore.
- The App displays the result and, only if you tap Save, additionally saves it to your device's photo library.
4.2 Retention Periods
- Cloudflare R2 (original + result): stored for a maximum of 90 days, then deleted server-side via an automatic lifecycle rule. If you delete a creation in the App beforehand, the associated R2 objects are removed immediately as well. The same applies to mannequin poses (Section 4.5).
- Google Firestore (metadata): until you delete the creation in the App or request deletion pursuant to Section 11.
- Photo library on your device: managed by you.
- At OpenAI (Images API): see Section 5.
4.3 Deletion by You
- In the App: every creation can be deleted individually, and Settings → "Delete all AI creations" removes all metadata plus all source and result images from Cloudflare R2 in one step — including the photos and renders of your mannequin poses. Poses already saved on your device stay there until you delete them. Deleting a mannequin pose in the App also deletes its photo and renders from Cloudflare R2.
- On request: to have all data stored under your IDs deleted in a single operation, write to hello@empose.app stating your app user ID (shown at the bottom of the App's Settings screen).
4.4 Face Data
Empose does not collect or process face data in the sense of biometric identifiers. The App does not perform facial recognition, does not identify or authenticate you, and does not create faceprints or any other biometric templates. Photos you select may contain faces; they are processed exclusively as image files in accordance with Sections 4.1–4.3 (storage for a maximum of 90 days in Cloudflare R2, transmission to OpenAI solely for image generation, deletion by you at any time) and are never used to identify individuals. The predefined style templates additionally instruct the AI model to preserve each person's identity and appearance unchanged; Styling changes only the features you choose and keeps the identity (Section 4.8). A mannequin pose contains no face at all: the person is replaced by a featureless figure.
Optional face scan during onboarding. On iPhones with a TrueDepth camera (not in the Android app), onboarding offers an optional face scan that you can skip at any time. For this scan, the App uses Apple's ARKit face tracking, which relies on the TrueDepth camera. While the scan screen is open, the App uses this data for only two things:
- to draw a live wireframe of your face over the camera preview as visual feedback; and
- to read whether a face is detected and how your head is turned (left/right and up/down angles), so it can check that you have turned your head as instructed.
This data is processed exclusively on your device, and only in memory while the scan screen is open. It is discarded as soon as you leave the screen. The App does not save, upload, log or share any face tracking data, face geometry, depth data or camera images from the scan, and does not send them to us or to any third party, including analytics providers. It is not used for advertising, analytics, identification or any purpose other than guiding you through the scan in real time. Since nothing is retained, there is no face data to access, export or delete.
On devices without a TrueDepth camera, the face scan is skipped.
Face check for Styling and pose changes. Before a Styling or a pose change is created, the App checks on your device whether — and for a pose change, how many — faces the selected photo shows (Sections 4.8 and 4.9). The check only detects whether and where faces appear in the picture; it does not identify anyone, and nothing from it is uploaded or kept.
Camera preview. Apart from the face scan, the App uses the front or rear camera as a regular camera to show a live preview with your chosen pose guide over it. These camera frames are processed on your device and are never uploaded, stored or shared with third parties.
4.5 Photo guide and My Poses (your own pose guides)
- Photo guides never leave your device. In the camera you can pick a photo that is then shown over the live camera instead of a pose. It is kept only temporarily in the App's own storage on your device — until you choose a pose or close the App — and never uploaded: not to us, not to OpenAI, not to analytics. It is never part of a photo you take.
- Mannequins are drawn by generative AI. Only when you confirm — and only with an active Premium subscription — is the photo transmitted encrypted to our backend and stored in Cloudflare R2 under users/{your-ID}/custom-poses/{random-ID}/. The Worker sends it to the OpenAI Images API (model gpt-image-2), which repaints the person as a featureless Empose mannequin in the same pose; if you indicate that a long dress or coat hides the legs, the photo is first redrawn in plain sportswear so the legs can be traced. A text model (OpenAI gpt-4.1-mini) receives the photo once to write the pose's name, three steps and a camera tip in your app language, and rewrites an optional re-render note into a pose description. The photo, the renders and the job record are stored for a maximum of 90 days (same lifecycle rule as Section 4.2); the mannequin you keep is also saved on your device, and poses you kept are restored from your account after a reinstall while they are within that period. Only kinds and counts of these actions (never the photo, its file name or location) are recorded in usage analytics.
4.6 Pose for here (scene scan)
When you tap "Pose for here" in the camera on an iPhone (the Android app has no scene scan), the App takes one small frame from the live camera and analyses it entirely on your device with Apple's built-in image recognition, to suggest where you are (for example a bench, stairs or a beach) and whether a person is in view full-length or from the waist up. Nothing is uploaded — not to us, not to OpenAI, not to anyone — and no one is identified. The frame is deleted as soon as it has been analysed, is never saved to your photo library and is never part of a photo you take. Usage analytics record only the App's own spot categories (such as "bench"), the framing and how long the scan took — never the image, Apple's recognition labels or their confidence values.
4.7 Monthly recap
To show you a recap of last month (how many photos you saved, which poses you used most, and a few of your photos), the App keeps a small count of the photos you save each month on your device, with references to the six most recent ones. It is not uploaded and is kept for three months. The recap image is created on your device and only shared if you choose to share it. Usage analytics record only that the recap was opened or shared, the month and the number of photos.
4.8 Styling
Styling changes single features of the person in your photo at your request — for example the hair color or hairstyle, lips, makeup, brows, lashes, a beard, glasses, or temporary blemishes. Before anything is uploaded, the iPhone app checks on your device, with Apple's built-in image recognition, whether the photo shows a face at all (the Android app does not run this check), so a photo without one does not use a generation. This check only finds whether and where faces appear in the picture; it does not identify anyone, creates no facial geometry or template, and nothing from it is uploaded or kept. When you tap Create, the photo is processed exactly like a Look (Sections 4.1–4.3 and 5.1): it is sent with the predefined instructions of the options you chose, which tell the AI model to change only those features and to keep the person's identity — face shape and features, skin tone, expression and age — unchanged. Usage analytics record only that a Styling was created and which categories were chosen (for example "hair color, lips"), never the photo.
4.9 Pose changes ("Change the pose")
A pose change moves the person in your photo into a pose you pick from the App's pose library — for example from crouching to standing with a hand on the hip — and keeps the rest of the photo. It works on photos of one person only. Before anything is uploaded, the iPhone app counts the faces in the photo on your device, as for Styling (Section 4.8), and does not accept a photo with several people; the Android app does not run this check. When you tap Create, the photo is processed exactly like a Look (Sections 4.1–4.3 and 5.1): it is sent together with the chosen library pose — a featureless mannequin figure that belongs to us — and predefined instructions that tell the AI model to change only the pose and to keep the person's identity, body shape, clothing, the place and the light unchanged. Usage analytics record only that a pose change was created and which library pose was chosen, never the photo.
4.10 Feedback
In Settings → Feedback you can tell us which features you would like. Only what you type there is sent, and only when you tap Send. Together with it we receive your random app user ID, the app and operating system version, the device model, the app language and whether you have Empose Premium, so we can understand and act on your message. Please do not include personal details; we collect no e-mail address and cannot reply.
Before it reaches us, our backend checks the message so that only real feedback arrives — no empty messages, spam or insults. An OpenAI text model (gpt-4.1-mini, Section 5.1) judges the text and translates it into German for the team. Messages that pass are e-mailed to the team via Cloudflare Email Routing and kept in the team's mailbox (Google Gmail) as long as needed to evaluate the feedback, at most 2 years. Rejected messages are not delivered; they remain in Cloudflare's server logs for up to 7 days so we can check the filter. Usage analytics record only that feedback was sent, its topic and its length — never the text.
4.11 Creator applications
In Settings you can apply to make paid videos about Empose ("Become an Empose Creator"). The application holds what you enter — your name, the platform and handle of your channel, its follower range, your e-mail address and an optional message — plus your random app user ID, the app and operating system version, the device model, the app language and whether you have Empose Premium. It is sent only when you tap Send.
We use it only to review the application and to contact you about a collaboration (Art. 6 (1)(b) GDPR, steps prior to a contract). Before it reaches us, an OpenAI text model (gpt-4.1-mini, Section 5.1) checks it for spam and abuse and translates your message into German. The application is stored in Cloudflare (Workers KV) for our team's review and e-mailed to the team via Cloudflare Email Routing (mailbox: Google Gmail). It is deleted automatically 12 months after its last change, or earlier on request; if we start working together, the contract governs further processing. Usage analytics record only that an application was sent, the platform and the follower range — never your name, handle or e-mail address.
5. Disclosure to OpenAI (Image Generation), Google (Firebase), TikTok and Apple (Ad Measurement)
5.1 OpenAI (Images API)
The actual image generation is performed by the OpenAI Images API (model gpt-image-2.5-flare for Looks and Styling, gpt-image-2 for mannequin poses), and the texts of mannequin poses and the check and translation of feedback and creator applications (Sections 4.10, 4.11) by an OpenAI text model (gpt-4.1-mini). Provider: OpenAI Ireland Ltd (contracting party for the EEA) or OpenAI, L.L.C. (USA). The photo and the predefined instruction are transmitted — exclusively from our backend, never directly from the App.
- Retention at OpenAI: OpenAI states that it does not use API inputs and outputs for training its models and only retains them temporarily for abuse monitoring (typically up to 30 days). Current details: https://openai.com/enterprise-privacy/
- Third-country transfer: data may be transferred to the USA; the EU Standard Contractual Clauses apply (part of the OpenAI Data Processing Addendum).
- Contractual data protection: OpenAI is contractually bound by its Data Processing Addendum (including the EU Standard Contractual Clauses) to provide the same or an equal level of data protection as described in this Privacy Policy and processes the data solely to provide the image generation service.
- OpenAI privacy policy: https://openai.com/policies/privacy-policy/
5.2 Google (Firebase Authentication, Cloud Firestore, Analytics, Crashlytics)
We use services provided by Google Ireland Ltd. and Google LLC:
- Firebase Authentication — assigns an anonymous UID per app installation. No personal login data is transmitted.
- Cloud Firestore — stores the generation metadata described in Section 4.1 (never the photos themselves).
- Firebase Analytics & Crashlytics — pseudonymous usage events (e.g. "a generation was started") and crash reports for stability. Not used for advertising or cross-app tracking.
- Third-country transfer: data may be transferred to the USA. Google is certified under the EU-U.S. Data Privacy Framework; in addition, the EU Standard Contractual Clauses apply.
- Google privacy policy: https://policies.google.com/privacy
- Firebase privacy policy: https://firebase.google.com/support/privacy
5.3 TikTok (ad measurement, only with your consent)
We advertise Empose on TikTok. This section applies only to the iOS app; the Android app contains no TikTok SDK. To find out which ad campaign led to an install and a purchase, the App contains the TikTok App Events SDK. It is started only if you allow tracking in Apple's prompt; before that, and if you don't allow it, it is never started and nothing is sent to TikTok.
- When we ask: only after a purchase, never before the subscription screen, so your answer cannot influence a buying decision. Nothing is offered for allowing it.
- What is sent if you allow it: your device's advertising ID (IDFA), device information that the SDK collects (such as device model, iOS version, app version, language and IP address) and two events: "onboarding completed" and the start of a trial or subscription with price, currency and product ID. No photos, no names, no e-mail addresses and no content you create.
- Events before your answer: the two events wait on your iPhone (at most 10) until you answer. If you allow tracking they are sent; if you don't, they are deleted.
- Recipient: for users in the EEA, the UK and Switzerland, TikTok Technology Limited, 10 Earlsfort Terrace, Dublin, D02 T380, Ireland; elsewhere TikTok Pte. Ltd., Singapore. TikTok uses the data to attribute installs and purchases to ads and to measure and improve campaigns. For the collection and transmission via the SDK, we and TikTok are jointly responsible (Art. 26 GDPR) under TikTok's Business Products (Data) Terms; TikTok is solely responsible for its further processing.
- Legal basis: your consent (Art. 6 (1)(a) GDPR and § 25 (1) TDDDG).
- Withdrawal: you can withdraw your consent at any time with effect for the future: iPhone Settings → Privacy & Security → Tracking → Empose.
- Third-country transfer: TikTok may process data outside the EEA (for example in Singapore, Malaysia or the USA). TikTok uses the EU Standard Contractual Clauses for this.
- Retention: according to TikTok's retention rules.
- TikTok privacy policy: https://www.tiktok.com/legal/page/eea/privacy-policy/en; TikTok Business Products (Data) Terms: https://ads.tiktok.com/i18n/official/policy/business-products-terms
5.4 Apple SKAdNetwork (anonymous ad measurement)
Independently of the tracking prompt, the iOS app uses Apple's SKAdNetwork (the Android app does not). The App only tells iOS how far an install has got (installed, onboarding completed, trial started, paid subscription). Apple then sends the ad network a delayed, anonymised report that cannot identify you or your device; neither we nor TikTok receive any personal data from it. Apple may also send us a copy of that anonymous report.
6. Backend Hosting and Image Storage (Cloudflare)
Our backend runs as a Cloudflare Worker and stores images in Cloudflare R2. Provider: Cloudflare, Inc., 101 Townsend Street, San Francisco, CA 94107, USA.
- Cloudflare necessarily processes IP addresses, timestamps and request metadata for delivery and protection against attacks.
- R2 stores your uploaded and generated images encrypted.
- To size the weekly AI credit allowance and the credit packs, the Worker records when credits are spent, returned or added, and what an AI generation cost, in Cloudflare Workers Analytics Engine. These records hold only a one-way hash of your app user ID, never the ID itself, your photos or any other content, and are deleted after at most 3 months.
- Legal basis: Art. 6 (1)(b) and (f) GDPR. A data processing agreement including the EU Standard Contractual Clauses is in place. Cloudflare is certified under the EU-U.S. Data Privacy Framework.
- Privacy policy: https://www.cloudflare.com/privacypolicy/
7. Subscriptions & Purchases (Apple, Google / RevenueCat)
Purchases within the App — subscriptions and AI credit packs — are processed via the Apple App Store (iOS) or Google Play (Android). For purchase validation, restoration and AI-credit assignment we use RevenueCat (RevenueCat, Inc., USA).
We transmit to RevenueCat a pseudonymous app user ID, the purchase transaction provided by the App Store or Google Play (transaction or order ID, product ID, purchase date, expiration date) and technical metadata (app version, operating system version, device class).
- Purpose: proof of an active subscription, unlocking the Premium AI credits (25 per week, 15 during a free trial; a Look or Styling uses 1, a mannequin pose 2), granting purchased credit packs, restoration after reinstallation. Your credit balance (weekly use and purchased credits) is stored on our backend (Cloudflare) under your pseudonymous app user ID; purchased credits do not expire.
- Legal basis: Art. 6 (1)(b) GDPR.
- Privacy policy: https://www.revenuecat.com/privacy
The actual payment process takes place exclusively between you and Apple or Google. We receive neither your payment data nor your real name.
Subscription Details (Transparency Notice for the Paywall)
- Product names: Empose Pro Weekly (empose_pro_weekly) and Empose Pro Annual (empose_pro_annual)
- Duration: 1 week / 1 year; each renews automatically unless canceled at least 24 hours before the end of the current period.
- Cancellation: at any time in the Apple Account settings on your iPhone, or on Android in Google Play under Payments & subscriptions → Subscriptions.
- Price / trial period (if any): see the information shown directly on the paywall. Any unused portion of a free trial period is forfeited when a subscription is purchased.
AI Credit Packs (one-time purchases)
- Product names: 10 Credits (empose_credits_10), 30 Credits (empose_credits_30) and 60 Credits (empose_credits_60).
- One-time purchases (consumables), not subscriptions. Purchased credits do not expire; your weekly credits are used first. Credits can be used with an active Empose Premium subscription.
- Price: see the information shown in the App before purchase.
8. Push Notifications
If you consent to push notifications, the App sends you a notification as soon as your AI generation or mannequin pose is finished. For this we use the Expo push service (Expo, Inc., USA) together with the Apple Push Notification Service (APNs) on iOS or Google Firebase Cloud Messaging (FCM) on Android. A pseudonymous push token linked to the progress status of your generation is transmitted; it is stored on our backend only temporarily. The contents of your photo are not transmitted to Expo, APNs or FCM.
- Legal basis: Art. 6 (1)(a) GDPR (consent via the system dialog of iOS or Android).
- Withdrawal: at any time in the iOS settings under "Notifications → Empose", in the Android settings under "Apps → Empose → Notifications", or via the switch in the App's Settings.
9. App Permissions
| Permission | Purpose |
|---|---|
| Camera | Live preview with your chosen pose guide; frames are processed on-device only and never uploaded |
| Photos (select/read) | Selecting the source photo for an AI Look or Styling, a photo guide in the camera or your own pose (My Poses). On Android the system photo picker is used: it needs no permission and gives the App only the photo you pick. |
| Photos (add) | Saving captured photos and results to your photo library (only when you tap Save); on Android 13 and later this needs no permission |
| Notifications | Notification when a generation is finished |
| Tracking (App Tracking Transparency, iOS only) | Asked only after a purchase; if you allow it, the TikTok SDK starts for ad measurement (Section 5.3). You can change your choice anytime in iPhone Settings → Privacy & Security → Tracking. |
All permissions are optional. If a permission is not granted, only the corresponding feature is unavailable. The App requests no microphone or location permission.
10. Retention Periods at a Glance
- Uploaded and generated images in Cloudflare R2 (Looks, Styling and mannequin poses): maximum of 90 days (automatic deletion via lifecycle rule); earlier as soon as you remove the creation or pose in the App.
- Photo guides on your device: until you choose a pose or close the App.
- Poses saved on your device: until you delete them in the App or delete the App.
- Generation metadata in Firestore: until deleted by you or by us on request.
- Push token on our backend: temporary, expires automatically.
- Error logs at Cloudflare: per Cloudflare's standard retention (typically a few days).
- Subscription/purchase status at RevenueCat: for the duration of the contractual relationship plus statutory retention periods.
- Creator applications: 12 months after their last change (Cloudflare KV and the team's mailbox), earlier on request.
- Feedback e-mails in the team's mailbox: as long as needed to evaluate the feedback, at most 2 years; rejected messages only in server logs (up to 7 days).
- Temporary retention at OpenAI: see Section 5.
- Data received by TikTok (iOS only, and only if you allow tracking): according to TikTok's retention rules. Events waiting on your iPhone for your answer are deleted if you don't allow tracking.
11. Your Rights
Under the GDPR you have the following rights: access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18), data portability (Art. 20), objection to processing based on legitimate interests (Art. 21), withdrawal of consent with effect for the future (Art. 7 (3)), and the right to lodge a complaint with a supervisory authority (Art. 77), e.g. the authority competent for us:
Der Landesbeauftragte für den Datenschutz und die Informationsfreiheit Rheinland-Pfalz (State Commissioner for Data Protection and Freedom of Information of Rhineland-Palatinate)
Hintere Bleiche 34
55116 Mainz
Germany
https://www.datenschutz.rlp.de
Please direct any requests to: hello@empose.app
Since the App stores neither real names nor email addresses (apart from creator applications, Section 4.11), we need your anonymous app user ID to identify your data. You can find it at the bottom of the App's Settings screen (tap to copy). Without this ID we are technically unable to identify you as a data subject.
12. Children
Empose is not directed at children under the age of 13. We do not knowingly collect personal data from children under 13.
13. Security
All data transfers between the App, the backend, Cloudflare R2, OpenAI and Google are exclusively encrypted (TLS 1.2+). The OpenAI API key and all other credentials (Firebase service account, RevenueCat secret, signing secret) are stored exclusively as Cloudflare Worker secrets and never leave the backend. Direct access to stored images is only possible via signed, time-limited backend URLs bound to your user ID.
14. Changes to This Policy
We update this privacy policy whenever processing activities, legal bases or the services we use change. The current version is always available at empose.app/privacy and via the link in the App (paywall / settings). We will announce material changes in the App.
Contact: hello@empose.app