Mustafa Evleksiz
Privacy

Privacy Policy — VibeX

Last updated: October 3, 2026

This Privacy Policy explains what personal data we collect when you use VibeX, why and how we process it, and the rights you have. VibeX is a trust product: our goal is to process your photos only to create the result you asked for, and to keep you in control of your data. The policy applies to our users everywhere and uses the EU General Data Protection Regulation (GDPR) as its baseline; you'll find extra information for where you live in section 12.

1. Data controller

VibeX is a mobile app for iPhone and iPad (an Android version is planned), built and operated by Mustafa Evleksiz, who is the data controller under this policy (the person who decides why and how your data is processed). Use the contact address below (support@vibexapp.com) for any privacy question or request.

2. Data we collect

We collect only what we need to provide the service:

Photos
The photos you upload are processed only to create the AI improvement you requested. If you upload a photo of someone else (for example in Together mode), you must have their permission; we process their photo only to create the result you asked for.
Account info
Email, or a Sign in with Apple / Google identifier. With Sign in with Apple you can hide your email, and if you share your name it becomes your profile name. With Sign in with Google, the name and profile-photo link Google shares are stored in your account record, and the name also becomes your profile name. If you continue as a guest, an anonymous account is created and your device identifier and app language are stored with it.
Profile details
The name you give a profile and optional attributes: gender, age range, body type and ethnicity. You can pick these yourself or leave them blank; for any you leave blank, the AI model may estimate a value from your photo and fill it in (your own choice always wins). We add them to your generation requests only to keep you looking like yourself in the result, and store them with your profile for sync. Ethnicity is sensitive (special-category) data that the law protects separately. We state this estimate, including ethnicity, clearly on the consent screen shown before you add a photo, and we make it only with your consent; we record the date and text version of your consent. If you change a field, your choice is used; if you clear it, it may be estimated again at your next photo analysis.
Settings and preferences
For cross-device sync, some of your settings and preferences are stored in the cloud with your account — for example dark mode and app language, your quality and output preferences, your analytics choice, results you've pinned in Jobs, your favorites, your profile names and each profile's Quick Create presets, results you've removed the watermark from, and your progress in the onboarding tour. They are kept until you delete your account and are deleted when you do. Some device-level information is deliberately not synced: your photo-processing consent is asked for again on a new device, and your device identifier, notification permission and device integrity (App Attest) key stay specific to each device.
Device identifier
A device-specific identifier (UUID) and the device model, used to grant a guest try, limit welcome credits to one per device, provide support, and prevent abuse.
Approximate location
A COUNTRY-level approximate location taken from your device's App Store country and region/language settings, sent by the app with your generation requests, for fraud prevention and abuse detection. No GPS is used, and this data is kept for at most 90 days. We do not use your IP address to determine location; for abuse prevention we keep it only briefly (hashed for up to 36 hours for guest-trial limits, and up to 24 hours after failed code-redemption attempts). While analytics is on, our analytics provider PostHog may derive an approximate location (such as city or country) from the IP address a request comes from; if you don't want that, you can turn analytics off in Settings.
Usage analytics
Event data about how you use the app, linked to your account ID and device identifier, sent to PostHog (US) and stored in our own database (the events themselves for up to 90 days; the hourly summary derived from them is covered in section 7), to improve the product. While analytics is on, the app also sends a short signal to our own servers only, once a minute while it is open on screen, so the minutes when the app was open are kept for 90 days and your device's last-seen record for 180 days after its last use, together with your account ID and device identifier. You can turn analytics off in Settings; crash reporting (Sentry) is separate.
Crash logs
Diagnostics and crash reports (Sentry) to fix problems. While analytics is on, these reports are linked to your account ID.
Purchase info
Verification of credit and subscription purchases (Apple In-App Purchase / RevenueCat) and a server-side purchase event log (no card data). We never see your card details; Apple handles payment.
Ad measurement (Apple Ads)
Once after installation, the app gets an attribution token from Apple's AdServices framework and passes it to RevenueCat. RevenueCat uses the token to ask Apple whether you downloaded the app through an ad on Apple Ads; if so, the campaign, ad group and keyword are linked to your record at RevenueCat. We do this only to measure whether our ads work. This measurement does not use the advertising identifier (IDFA) and does not require tracking permission.
Ad measurement (no tracking)
VibeX does not track you across other companies' apps and websites and does not ask for tracking permission; the app contains no ad-tracking kits. We measure whether our ads work only in ways that do not identify you: Apple's attribution for Apple Ads, described above, and, for links we share in places like Instagram, the aggregate campaign counts App Store Connect shows us (how many people viewed and downloaded the app from a link; anonymous and only in groups larger than a few people). Versions 0.5.17–0.5.19 of the app included Meta's measurement kit: if you allowed tracking in one of those versions and analytics was on, an “app opened” event may be sent to Meta when you open the app (with the Meta anonymous ID, the advertising identifier (IDFA), device model, version, language and IP address); updating the app stops this completely. Your photos, face data, email and profile details were never sent to Meta. Meta processes this data under its own privacy policy; you can withdraw permission at any time in iOS Settings > Privacy & Security > Tracking.
Push notifications
If you allow notifications, your device's Apple push token is stored to send you notifications (including announcements); it is deleted when you delete your account.
Feedback and reports
The reason and note you send about a result; only if you turn on sharing, the result, original and reference photos are uploaded so our team can review them (refunds, moderation).
Website waitlist
If you join the Android waitlist on vibexapp.com, we store your email, language and platform (via Supabase/Upstash) only to notify you at launch, and your signup is also emailed to our team via Resend. Email us to be removed.
Website visits
vibexapp.com sets no cookies and loads no advertising or tracking tools. Your light/dark theme choice is stored only in your own browser. Our web server keeps no access log of visits (IP address, browser details); your IP address is used only to deliver the page to you. If a connection error occurs, the IP address may appear in the server's error log; we use these logs only to fix problems, and older lines are deleted automatically once the log reaches a set size.

3. Why we process data

  • To create and deliver the photo output you requested,
  • To create your account, sign you in, and sync your creations and settings across devices,
  • To manage credits, purchases and free earnings,
  • To prevent abuse, fraud and content-safety violations,
  • To keep the app stable, fix bugs and improve the product,
  • To measure whether our ads work, in ways that do not identify you,
  • To comply with legal obligations.

Laws such as the GDPR require every use of personal data to rest on a legal basis (a lawful reason that permits it). Here is the basis we rely on for each purpose:

Performance of a contract
What we need to do to deliver the service under our terms with you: creating the results you ask for, creating your account and signing you in, syncing your creations and settings across devices, and managing credits, subscriptions and purchases.
Legitimate interests — abuse prevention
A legitimate interest means we have a genuine reason to use the data and that reason is not overridden by your rights and freedoms. Our interest here: stopping fake accounts from exploiting free tries and credits, and preventing fraud and prohibited content.
Legitimate interests — security
Our interest: protecting your account, our servers and our AI key from attacks and unauthorized access (for example, App Attest device integrity checks).
Legitimate interests — bug tracking
Our interest: finding and fixing crashes and errors so the app stays stable.
Legitimate interests — product analytics
Our interest: understanding which features work so we can improve the app. You can turn analytics off in Settings at any time.
Legitimate interests — ad measurement
Our interest: measuring whether our ads on Apple Ads bring in downloads and subscriptions.
Consent
Explicit consent is permission you give freely and specifically for a particular use, and can withdraw at any time. We rely on it for: processing and storing your photos and face references (avatar, angle shots, full-body photo), the ethnicity field in your profile, sharing to the community gallery, notifications, and (only in versions 0.5.17–0.5.19) the tracking permission for ad measurement with Meta. Withdrawing consent does not make processing carried out before then unlawful.
Legal obligation
What the law requires of us: keeping purchase records for as long as the applicable rules require.

4. What happens to your photos

When you upload a photo, processing happens over our secure servers (Supabase Edge Functions), and the photo is sent to the AI model (Google's Gemini vision model) to create the output. The AI key never lives on your device. Under its paid-service terms, Google keeps these requests for 55 days, solely to detect and prevent abuse and to meet legal obligations.

Beautify Me: when you use this feature, the photo you choose is sent through OpenRouter to OpenAI's image model to create the retouch, and the result comes back to you. We tell you this and ask for your permission before sending it. Under its API terms, OpenAI does not use this data to train its models; it may keep it for up to 30 days to monitor for abuse. For retouch suggestions, a crop of your face is sent to Google Gemini (the terms above apply). The areas you don't select come from your original photo on your phone.

Your creations, the original (“before”) photos they were made from, and your profile photos (avatar and identity photos) are stored in a private cloud space that belongs to you, for history and cross-device sync. Server copies of results made for delivery are deleted automatically after 7 days. You can delete them at any time.

Profile Pack (batch creation): a copy of the photos sent for a pack (your avatar and, if you have them, your angle shots and full-body photo) is kept, while the pack is being prepared, in a separate area that only our servers can access, and is deleted once the pack is complete, within 24 hours at the latest. The images are created with Google Gemini: the photo copies uploaded to Google's batch processing service and the batch job are deleted as soon as creation finishes; if for any reason they cannot be deleted, Google deletes those photo copies on its own within 48 hours. The 55-day period above applies to the records Google keeps to prevent abuse. Server copies of the pack's images made for delivery are deleted automatically 7 days after they are added to your History, or 30 days after the pack is complete if they never are.

Your photos are NEVER used to train any AI model. A content-safety filter is applied, and we obtain explicit consent for processing.

Face scan (optional): the 3D face model (mesh) is created and stored only on your device and is never uploaded. The photos you keep from the scan (your avatar, left/right angle shots and an optional full-body photo) are stored in your private cloud space for sync and sent to the AI model (Google Gemini) as identity references when you create images. Delete the profile in the app to remove them.

We do not process your photos to recognize who you are or to verify your identity, and we do not extract or store a face-recognition template (a biometric template) from them; the 3D model from a face scan never leaves your device either. The face comparisons we do make serve only to get the result right: on your device, the app calculates the score showing how much a result looks like you and, in Together mode, checks that the same person hasn't been added twice (the data created for these checks is not stored); the AI model also compares a result with your original photo and rates its realism and likeness (these scores are stored with usage events while analytics is on). We ask for your explicit consent to process your photos on the consent screen shown before you add a photo, and you can withdraw it at any time: when you delete your photos, profile or account, that processing stops.

The community gallery is entirely optional: you can only share a scene with explicit consent — either by confirming (checkbox) that your face may be visible, or by using quick share, where your face is automatically removed before sharing. We keep a record of that consent (scene, time, consent version). Every share goes through moderation review before it appears, and you can remove your share at any time or contact us to have it removed.

5. Third-party services

We rely on the following providers to deliver the service. Each is subject to its own privacy policy:

Apple
Sign in with Apple, in-app purchases, distribution, push notifications (APNs) and App Attest device integrity checks.
Google
Sign in with Google and the Gemini image model.
OpenAI and OpenRouter
The image model behind Beautify Me (OpenAI) and the service we reach it through (OpenRouter).
Supabase
Authentication, secure processing (Edge Functions) and storage.
RevenueCat
Management of purchases and credit entitlements, and Apple Ads measurement.
Meta
Only in app versions 0.5.17–0.5.19 and only if you allowed tracking: the “app opened” event (details in section 2). The current version sends no data to Meta.
PostHog
Product analytics (US servers); can be turned off in Settings.
Sentry
Crash and error monitoring.
Upstash
Data store for credit and quota counters, community-gallery metadata, the in-app notification inbox, abuse-prevention lists and the Android waitlist.
Resend
Emailing website waitlist signups to our team, and sending the app's sign-up and password-reset code emails.
Contabo
Hosting the vibexapp.com website.

These providers process your data on our behalf and on our instructions. Apple (sign-in, payment and push infrastructure), Google (Sign in with Google) and, if you allowed tracking in an older version, Meta (ad measurement; it may also use the data it receives to personalize ads) also process data in those services under their own privacy policies. We never sell your personal data.

6. International transfers

Some of the providers above may host servers outside your country (for example in the European Union or the United States). As a result, your data may be processed and stored abroad to the extent necessary to provide the service. These transfers are carried out in line with applicable data-protection rules.

When we transfer data from the European Union/European Economic Area (EU/EEA) or the United Kingdom to a country that has not been recognized as protecting data adequately, we rely on two safeguards. The first is the European Commission's standard contractual clauses (SCCs: a Commission-approved model contract that binds the recipient to EU-level protection); for data from the UK, the UK's addendum to those clauses also applies. The second, where the recipient benefits from one, is an adequacy decision (an official decision that a country or framework protects data adequately): in the United States, it covers companies certified under the EU–U.S. Data Privacy Framework (DPF) and, for UK data, its UK Extension. Provider by provider:

Supabase
Database and file storage in the EU (Frankfurt, Germany). Server functions (Edge Functions) run in the region closest to the request, so your photos may pass through a region outside the EU while they are processed. SCCs, which are part of Supabase's terms of service, cover processing and access outside the EU.
Sentry
Crash logs are kept in the EU (Germany); SCCs and the DPF for access by the company in the US.
Google
Gemini and Sign in with Google run on Google's global infrastructure, including the US. We use Gemini as a paid service; under the Gemini API terms, Google processes our requests under its data processing terms, which include the SCCs. Google is also DPF-certified (including the UK Extension).
OpenAI and OpenRouter
US. Sending your Beautify Me photo to these providers is based on the explicit permission you give before using the feature.
PostHog
United States. Transfers rely on PostHog's DPF certification (including the UK Extension).
RevenueCat
United States. The SCCs in RevenueCat's data processing addendum, which is part of its terms (with the UK addendum for UK data).
Meta
Only if you allowed tracking in versions 0.5.17–0.5.19: for users in the EU/EEA the recipient is Meta Platforms Ireland Ltd. (Ireland, EU); for other users, Meta Platforms, Inc. (United States). Meta Platforms, Inc. is certified under the EU–U.S. Data Privacy Framework.
Upstash
Data is kept in a global database with copies in several countries, including the EU and the US. The DPF under the data processing addendum that is part of Upstash's terms and, where needed, the SCCs in the same addendum.
Resend
United States; emails are sent from its EU (Ireland) sending region. SCCs; the company is also DPF-certified.
Apple
Apple's global infrastructure; Apple applies its own SCCs to transfers from the EU.
Contabo
The website server is in Germany (EU).

To get a copy of these safeguards, just email support@vibexapp.com.

Transfers out of Türkiye are subject to Article 9 of the KVKK; see our KVKK information notice (in Turkish) at vibexapp.com/tr/kvkk.

7. Data retention

We keep your data for as long as your account is active or as needed to provide the service. Usage-event and generation logs (including device ID, device model and country) are deleted automatically after 90 days. When you delete your account, your data is permanently removed; a waiting period of roughly 30 days may apply before you can re-register.

Two summaries derived from usage-event and generation logs are kept longer. The daily usage summary derived from generation logs (per day, account, device and type of operation: numbers of calls and generations, credits spent and cost) is kept for statistics and cost accounting until your account is deleted. The hourly device activity summary derived from the usage events collected while analytics is on (device identifier, hour, number of events, app version and the account seen in that hour) is also kept until your account is deleted; its entries not linked to any account for that hour are deleted after 400 days. For the streak in Quests, the days on which you open the app are kept for 400 days, regardless of your analytics choice. All of these records that are linked to your account are deleted when you delete your account.

After account deletion we keep only: a hashed form of your email for the re-registration waiting period (30 days by default), purchase event records, records of community-sharing consent and of your photo-processing consent (date and text version), and a ban entry if your account or device was banned for abuse. Copies held by our providers (e.g. PostHog, Sentry, RevenueCat) and, if you allowed tracking in an older version, by Meta are deleted under their own retention periods.

Legal retention obligations (for example, purchase records) may require us to keep certain data for as long as necessary.

8. Security

We apply reasonable technical and organizational measures to protect your data, including encryption in transit and at rest, access controls, and keeping no AI key on the client. No method is 100% secure, but we follow industry standards to protect your data.

9. Your rights

Depending on where you live (under the GDPR, the UK GDPR, Türkiye's KVKK, Brazil's LGPD and similar laws), you may have the right to:

  • Access your data and request a copy (portability),
  • Correct inaccurate or incomplete data,
  • Request deletion of your data,
  • Object to or restrict certain processing,
  • Object, on grounds relating to your situation, to processing based on our legitimate interests (we then stop unless we have compelling grounds that override yours),
  • Withdraw consent you have given,
  • Lodge a complaint with a data protection supervisory authority (section 12 explains which one).

To exercise these rights, you can contact us (support@vibexapp.com) or delete your account directly from inside the app.

We reply to requests within one month at the latest (within 30 days for requests under the KVKK). If a request is complex or we receive many, this may be extended by up to two more months as the GDPR allows; if so, we will tell you why within the first month. To avoid handing your data to the wrong person, we may need to verify your identity — for example, by asking you to write from the email address on your account or to give us some additional details about it.

You can turn product analytics off at any time in the app under Settings > Data & Privacy; crash reporting is separate.

We do not make decisions about you based solely on automated processing that have legal or similarly significant effects. The content-safety filter and usage limits can automatically stop individual generation requests, but a decision to ban an account or device is always made by a person.

10. Children's privacy

VibeX is not directed to children under 13, and we do not knowingly collect data from them. If you believe a child has provided us data, please contact us; when we learn of it, we delete the account and the data concerned.

If you are below the age of digital consent in your country (13–16 in the EU, depending on the country), you need a parent's or guardian's permission.

11. Changes

We may update this policy from time to time. For significant changes we will notify you in the app or on this page. The latest version is always published here.

12. Region-specific information

This section adds to the rest of the policy, depending on where you live.

EU/EEA and United Kingdom
We process your data in line with the GDPR and, in the UK, the UK GDPR; our legal bases are in section 3 and our transfer safeguards in section 6. To exercise your rights, email support@vibexapp.com. You can lodge a complaint with the data protection authority of the EU country where you live, work or believe the infringement took place, or in the UK with the Information Commissioner's Office (ICO).
United States — selling and sharing
We do not sell your personal data, there are no ads in the app, and the current version shares no data with any ad company for ad measurement. Only if you allowed tracking in versions 0.5.17–0.5.19 may an event be sent to Meta when you open the app (details in section 2); updating the app, or withdrawing permission in iOS Settings > Privacy & Security > Tracking, stops it.
United States — Do Not Track
We do not change how we behave in response to a browser's “Do Not Track” signal, because there is nothing to switch off: vibexapp.com has no advertising or tracking cookies, and we do not track you across other websites.
United States — biometric data
The 3D face model (face geometry) from a face scan never leaves your device. We do not keep biometric identifiers such as face geometry or face-recognition templates on our servers; what we store are the photos you upload and create. The score showing how much a result looks like you is also calculated on your device, and the data created for it is not stored.
Brazil (LGPD)
If you live in Brazil, the LGPD gives you the right to: confirm whether we process your data and access it; correct it; have unnecessary, excessive or unlawfully processed data anonymized, blocked or deleted; portability; deletion of data processed on the basis of your consent; know which public and private entities we have shared your data with; know what happens if you do not give consent; and withdraw consent. Our channel for these rights and any question is support@vibexapp.com. As a small-scale processing agent, we do not appoint a separate data protection officer (encarregado), as the ANPD's rules allow; this channel serves that role. You can also petition Brazil's National Data Protection Authority (ANPD).
Türkiye (KVKK)
If you live in Türkiye, our information notice under Law No. 6698 on the Protection of Personal Data (KVKK) is at vibexapp.com/tr/kvkk (in Turkish). We conclude requests within 30 days at the latest; if you get no reply or find the reply insufficient, you can complain to the Personal Data Protection Board (KVKK Kurulu).
United Arab Emirates (PDPL)
If you live in the UAE, Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data (PDPL) gives you rights such as getting information, accessing, correcting or deleting your data, having it transferred, and restricting or stopping processing; you can use them through the same channel (support@vibexapp.com).

Questions? Write to us: support@vibexapp.com