Retyla

Privacy Policy

Effective date: 12 October 2026 · Retyla · Applies to the Retyla mobile app for iOS and Android and to the website at retyla.app.

1. Who we are

Retyla ("Retyla", "we", "us") is a mobile application that repairs and enhances photographs you choose. It is operated from Mardin, Türkiye. The operator's verified legal name and postal address are published on the app's App Store and Google Play listings — both stores verify those details and keep them current, so that is the authoritative copy rather than one transcribed here.

Retyla is the controller of the personal data described in this policy — it decides why and how that data is processed — and is reachable at:

Privacy questions and data rights requests
privacy@retyla.app. We reply within one month, as the law requires, and usually within a few days.
Everything else
support@retyla.app.
Data protection officer
None appointed. The core activities here do not involve regular and systematic monitoring of data subjects on a large scale, and do not involve large-scale processing of special category data, so Art. 37 GDPR does not require one. The contact addresses above do the same job.
Representative in the EU / UK (GDPR Art. 27)
None appointed. The processing here is occasional, does not involve large-scale processing of special category data, and is unlikely to result in a risk to your rights and freedoms, which is the Art. 27(2)(a) exemption. If that changes — or if a supervisory authority tells us otherwise — a representative will be appointed and named here before the change takes effect.

2. The short version

This is not a substitute for the sections below, but it is an honest summary of all of them.

3. What we do with your photographs

Retyla has one core function: you choose a photograph, you choose an effect, and we return an enhanced version of that photograph. Everything below describes that single path.

How a photograph reaches us

You select it in your operating system's own photo picker — PHPicker on iOS, the Android Photo Picker on Android. Those pickers hand the app exactly one file and nothing else. The app does not ask for, and does not hold, permission to read your photo library, so there is no way for it to see photographs you did not choose. You can process one photograph at a time; a second request while one is running is refused by the server.

What we do not do to it

The upload path performs no rotation, no cropping, no padding, no resizing, no aspect ratio change and no EXIF correction. The file is passed to the image model as you sent it. There is one exception: if your iPhone gave us a HEIC or HEIF file, we convert the container to JPEG so the model can read it. That conversion does not alter pixel data. There is no enlargement step anywhere in the product, and we make no claim about the dimensions of what comes back — the result is returned in whatever size and format the model produces, and we store and serve it exactly that way.

Who sees it

The photograph is transmitted over an encrypted connection to our own server and from there to the image model provider named in section 8. It is not placed in third-party object storage. It is not shared with anyone else, published anywhere, or used for any purpose other than producing the result you asked for. Server access exists for maintenance, not for looking at content: there is no tooling anywhere in Retyla for browsing the upload directory picture by picture, and the admin panel cannot display a user photograph at all.

Training

Your photographs are never used to train, fine-tune, or evaluate AI models. That promise has two halves, and they rest on different things, so here they are separately rather than merged into one comfortable sentence.

On our side, it is structural
We have no model, no training pipeline, no dataset and no machine to run one on. There is no code path in the service that copies a photograph anywhere but your own account's folder and the provider's API. Your originals are deleted on the schedule in section 7, which would end the question even if we wanted to.
On the provider's side, it is their policy
Photographs go to OpenAI's Images API (section 8). OpenAI states that data submitted through its API is not used to train its models. That is a commitment in their published API data usage policy and in the terms we use the API under — it is not a switch in our code, and we will not pretend it is one. We rely on it, we would stop using a provider that changed it, and we would tell you here if that ever happened.

Sensitive content

A photograph of a person can be biometric or otherwise sensitive data in some jurisdictions. Retyla does not perform facial recognition, does not build face templates on our servers, does not attempt to identify anyone, and does not match a face in one photograph against a face in another. The only face detection in the product runs on your device — see section 4. Please do not upload photographs of other people without their agreement, and do not upload content you would not be comfortable handing to a processing provider.

What those on-device features measure is where features sit in one picture, in order to draw on it. It produces no identifier, is not stored, is not sent anywhere, and cannot be compared against another photograph — see section 4.

4. What never leaves your phone

Several parts of Retyla work on a photograph entirely on your device. This is not a setting and not a mode you have to find — it is how those features are built, and it is the reason they appear in a privacy policy rather than only in the marketing.

For those features the photograph, and everything measured from it, stays on your phone. Nothing is uploaded, nothing reaches our servers, nothing is logged, and the finished picture is saved to your own photo library. There is therefore nothing on our side to delete, and uninstalling the app takes those pictures with it. Where a feature watches the live camera, those frames are likewise never uploaded, never cached, never written to disk and never logged — the only thing that comes out of them is what the screen shows you.

5. What we collect and why

Every category of personal data Retyla handles is listed here, with what it is, why it exists, and where it comes from. There is nothing outside this list.

The photograph you select
The image file and its embedded metadata as your camera wrote it. Purpose: to produce the enhanced result you requested. Source: you, through the system picker.
The enhanced result
The image the model returns, stored in the size and format it returns it. Purpose: to show you the result and keep it available in History until you remove it. Source: generated by the service from your upload.
The preview copy, for free accounts
A second, smaller file made from a copy of the result — scaled so its long edge is at most 1024 pixels and stamped with the Retyla wordmark — which is what a free account sees until it subscribes. The full result is never altered to make it. Purpose: to let you judge the result before paying for it. Source: generated by the service.
Account identifiers
A user ID generated on our server when you first open the app, and a device identifier the app generates and stores in the iOS Keychain or Android keystore. Purpose: to be your account without a sign-up, to keep your credits and subscription attached to you across reinstalls, and to authenticate your requests. Source: generated by us and by your device. These are not advertising identifiers and are not the hardware serial of your phone.
Session token
A signed token issued at start-up so the app can call our API as you. Purpose: authentication. Source: generated by us.
Job records
For each enhancement: the time, the effect used, the status, the file type and recorded dimensions, whether a credit or an allowance unit was spent, and any error code. Purpose: to run your History, to refund a credit automatically when a job fails, to enforce the one-at-a-time rule, and to debug failures. Source: generated by the service.
Credits, allowance and subscription status
Your credit balances, including the separate Face Studio pool, your usage against the periodic allowance, and whether an active subscription exists. Purpose: to give you what you paid for and to apply fair-use limits. Source: our own records and the subscription status relayed from Apple or Google through RevenueCat. We never receive your card number, bank details, or billing address.
Face Studio export records
A ledger row for each export: which makeup categories and presets were used, the credit spent, and when. Purpose: to charge the export correctly, to refund it when a save fails, and to keep the balance auditable. Source: the app. No image data. Note that this ledger is the one thing that outlives account deletion — see section 7, where we say so rather than leave you to find out.
Technical and device data
App version, platform, OS version, device model and language, sent with API calls; server logs containing IP address, timestamp, endpoint and status code. Purpose: to serve the right content for your app version, to keep the service reliable and secure, and to investigate abuse. Source: your device and our servers.
Push notification token
A token issued to your installation and delivered through Firebase Cloud Messaging, stored only if you turn notifications on — up to ten, so the same account can be notified on more than one device. Purpose: to tell you a job has finished, and to send one weekly reminder. The notification itself carries only a type and, at most, the id of the job it refers to: never an image, never a link to one. Source: the platform push service.
Support correspondence
If you email us, your email address and whatever you write. Purpose: to answer you and to keep a record of the request. Source: you.

We do not collect your name, email address (unless you write to us), phone number, contacts, calendar, precise or coarse location, health data, browsing history, or any advertising identifier. We do not use the App Tracking Transparency prompt because we do not track. We do not sell or share personal data in the sense those words carry under US state privacy laws.

6. Legal bases

If you are in the EEA, the UK or Switzerland, we must have a lawful basis under Article 6 GDPR for each purpose. Here is the mapping, purpose by purpose.

Producing the enhancement you asked for
Performance of a contract — Art. 6(1)(b). Without processing the photograph there is no service to deliver.
Creating and maintaining your account identifiers
Performance of a contract — Art. 6(1)(b).
Keeping your History available
Performance of a contract — Art. 6(1)(b).
Handling purchases, credits, allowances and refunds of credits
Performance of a contract — Art. 6(1)(b), and for tax and accounting records, a legal obligation — Art. 6(1)(c).
Security, abuse prevention, rate limiting and fraud detection
Legitimate interests — Art. 6(1)(f). Our interest is keeping a paid service working and not being used to attack others; the processing is limited to technical records and does not involve looking at your pictures.
Reliability, diagnostics and improving the product
Legitimate interests — Art. 6(1)(f), on aggregate and technical data only.
Push notifications
Consent — Art. 6(1)(a), given through the system permission prompt and withdrawable at any time in your phone's settings.
Answering your support or rights request
Legitimate interests — Art. 6(1)(f), or a legal obligation — Art. 6(1)(c) where the request is a statutory one.

Where a photograph you upload contains special category data within the meaning of Art. 9 — for example an image that reveals health or religious belief — we rely on your explicit consent under Art. 9(2)(a), which you give by choosing that photograph and starting the job. You can withdraw it by deleting the result in the app; the original is in any case erased on the schedule in section 7.

You may object to processing based on legitimate interests at any time — see section 11.

7. How long we keep it

Retention is set per category, not by one blanket rule.

Original uploaded photographs
Each upload is given a deletion deadline of 24 hours after it arrives, and a job that sweeps every hour removes everything past its deadline — so a file is gone within the hour after the 24-hour mark, whether or not you ask for anything. The original of a job that failed is deleted at once, not on the deadline. The 24-hour window is a setting rather than a constant: it is set to 24 hours today, it can only be changed by us, and if it ever changes this page changes with it.
Enhanced results and previews
Kept until you delete the item in History, delete your account, or the service is discontinued. There is no automatic expiry, because History would be useless with one.
Job records
When you delete an item in History, all three files — the original if it is still there, the result and the preview — are removed from disk immediately, and the record is marked deleted. The row itself stays, holding the effect used, the timestamps, the status and the recorded dimensions, with no file and no image attached, until you delete your account, at which point it is erased. We would rather describe that exactly than call it "deleted" and leave a row behind.
Account record, identifiers and credit balances
Kept while the account exists; erased when you delete it.
Subscription webhook records
The purchase and renewal events relayed to us for your account are held for 90 days and then expire automatically. They are also erased immediately if you delete your account.
Face Studio credit ledger
Rows recording each Face Studio credit grant, spend and refund against your user ID. These are not erased by account deletion — they survive it, keyed to a user ID that no longer belongs to an account. They hold no image, no device identifier and nothing that could be traced back to you from outside our database. This is the single gap between "delete my data" and "every last row", and it is named here and on the delete my data page instead of being left for you to discover.
Push token
Kept while notifications are enabled; erased when you turn them off, when the platform invalidates the token, or when you delete the account.
Database backups
Seven days at most. A backup taken before you delete something can still hold it until that backup expires on its normal rotation. Backups are encrypted, are not used to serve the app, and are never restored to recover an individual account — the same statement the deletion page makes at greater length.
Server logs
7 days, then rotated out automatically. A log line records the request method, path, status, duration, your IP address and your user ID. It never contains image content, file paths, credentials or request bodies — those are stripped before anything is written. Because we let logs expire rather than rewriting history, a line mentioning a deleted account can survive that deletion by up to a week.
Purchase and transaction records
Our own copies of your purchase events are erased when you delete your account, and expire after 90 days in any case. What survives is Apple's and Google's own record of the transaction, held by them under their own policies for as long as tax and accounting law requires of them, which we do not control and cannot delete. Where a tax obligation requires us to keep an accounting record of our own, it is kept for the statutory period of five years, reduced to the minimum the obligation needs and detached from your content.
Support correspondence
24 months from the last message, so we can recognise a repeat issue, unless it forms part of a legal claim.
Records of rights requests
Kept for as long as needed to demonstrate that we handled the request, which is itself a legal obligation.

8. Processors and sub-processors

We use a small number of providers. Each acts as a processor on our instructions, under a data processing agreement, and receives only what its function needs.

OpenAI — AI image processing
Receives the photograph you submitted and the instruction for the effect you chose, through the OpenAI Images API, and returns the result. It does not receive your user ID, your device identifier, your filename or anything else that identifies you — the request carries the image and the instruction and nothing more. OpenAI states that data submitted through its API is not used to train its models; see section 3 for why we state that as their policy rather than as our configuration. Processing region: the United States. OpenAI offers regional data residency to eligible customers and we have not enabled it, so the standard API region applies and section 9 is what covers the transfer.
RevenueCat — subscription and purchase state
Receives the same random user ID our server generated for you, and the receipt data Apple or Google issues, and tells our server whether an entitlement is active. It never receives photographs or card details. RevenueCat is able to hold an email address, a display name or an advertising identifier against a user; the app sets none of them, and where such a field comes back to us in a purchase event we discard it before storing anything. Processing region: United States.
A managed database service
Stores the account record, job records, credit balances and tokens described in section 5. No image file is ever stored in the database — photographs live on the server's own disk and the database holds only the path to them. Processing region: Germany, in the European Union.
Google Firebase — Remote Config and Cloud Messaging
Remote Config supplies the app's start-up parameters — the API address, the minimum supported version, and whether the service is in maintenance — and receives no personal data from us. Cloud Messaging delivers push notifications and therefore handles your push token and the notification text. Processing region: United States and Google's global infrastructure.
A European hosting provider — servers and storage
Runs the machine and the persistent disk that hold uploads, results, previews and logs for the periods in section 7. Files sit on that disk in a private directory, and each file is served only to the account it belongs to. Processing region: Germany, in the European Union.
Apple and Google — app distribution and payment
Independent controllers, not our processors, for the purchase itself. They take the payment, hold the billing relationship, and apply their own privacy policies. We receive only a status, never a payment instrument.

Beyond these, we disclose personal data only where we must: to comply with a binding legal request, to establish or defend a legal claim, or to a successor in a merger or asset sale, in which case this policy continues to apply to the data transferred until it is replaced by notice to you. We do not sell personal data and do not disclose it to data brokers or advertisers. We will publish material changes to this list under section 18.

9. International transfers

Where your photographs and account records actually sit is inside the EEA: the server, its disk and the database are all in Germany. What leaves the EEA is narrower than the list above may suggest — the image model (OpenAI), subscription state (RevenueCat), and push and start-up configuration (Google Firebase), all principally in the United States. Where personal data leaves the EEA, the UK or Türkiye, we rely on the European Commission's Standard Contractual Clauses (and the UK International Data Transfer Addendum for UK transfers), combined with encryption in transit, encryption at rest where the provider offers it, and the short retention periods above, which keep the volume of transferred content small and its life short. Where a provider is certified under the EU–US Data Privacy Framework we may also rely on that certification. For transfers out of Türkiye, where the controller is an individual with no Board-notified standard contract in place, we rely on your explicit consent under Art. 9 KVKK — given when you start a job after being shown this policy — and, for the incidental technical transfers that keep the service running, on the occasional-transfer ground in the same article. If a standard contract is later notified to the Board, this paragraph will say so and consent will stop being the ground we lean on.

You may ask us for a copy of the safeguard applied to a particular transfer at privacy@retyla.app.

10. Automated decision-making

We do not make decisions about you by automated means that produce legal effects or similarly significant effects, and we do not profile you. The AI in Retyla transforms an image; it does not score you, rank you, price differently for you, or decide anything about you. Automated rules exist only for mechanical enforcement — whether you have a credit left, whether a job is already running, whether a request looks like abuse — and any account restriction that follows can be reviewed by a person if you write to us.

11. Your rights and how to use them

If you are in the EEA, the UK or Switzerland you have the rights below under Articles 15 to 22 GDPR. If you are in Türkiye, the equivalents are in Article 11 KVKK and set out in section 17. Many of them you can exercise yourself, in the app, without asking us — that is faster, and it is how the product is built.

Access — Art. 15
Your History screen already shows every result we hold for you, and Profile shows your identifiers, credits and subscription state. For a full copy in a portable form, email privacy@retyla.app with the user ID shown at the bottom of the Profile screen.
Rectification — Art. 16
There is little to correct, since we hold no name or address. If a credit balance or subscription state is wrong, email support@retyla.app and we will fix the record.
Erasure — Art. 17
Delete a single result by removing it in History. Delete everything through Profile → "Delete my data", or by writing to us; the full procedure and what survives it is on the delete my data page. Uploaded originals are erased on the schedule in section 7 without any request.
Restriction — Art. 18
Email privacy@retyla.app and tell us what you want frozen and why. We will suspend processing of that data other than storage while we resolve the point.
Portability — Art. 20
Your results can be saved to your own phone from the result screen at any time, in the format the model produced, which is the portable form. For the structured records — job history, credits — email us and we will send a machine-readable export.
Objection — Art. 21
You may object to processing we base on legitimate interests. Email privacy@retyla.app. We will stop unless we can show compelling grounds that override your interests, which for security logging we generally can and will explain.
Withdrawing consent — Art. 7(3)
Turn notifications off in your phone's system settings. Withdrawal does not affect processing that already happened.
Not being subject to automated decisions — Art. 22
There are none. See section 10.

How we verify you. We hold no name or email address, so we cannot identify you from an email address alone. Send the user ID from the bottom of the Profile screen, or the store order details of a purchase made on the account. We ask for this to protect you: without it we cannot tell your account from anyone else's, and we will not act on an unverified request to delete or disclose someone's history. If we genuinely cannot identify you from what you send, Art. 11(2) GDPR allows us to decline, and we will tell you so plainly rather than guess.

Exercising these rights is free. If a request is manifestly unfounded or repetitive we may charge a reasonable fee or refuse, and we will explain why.

12. Cookies and similar technologies

This website

Optional website measurement is inactive in the current configuration: no analytics tag or advertising pixel is loaded. The neutral home page can select an edition from your browser's language preferences. When you deliberately choose a language, the site stores only that tag as retyla.language in local storage; it is not a user identifier and is not sent to an analytics service. Your choice lasts until you change it or clear this website's browser data. A localized URL keeps its specified language, and blocked storage does not stop manual selection. The website uses no session storage or IndexedDB, uses system fonts and serves its resources from this website, without a Google Fonts request. Optional measurement remains inactive; this notice must be updated to describe the actual processing before it is enabled, and optional measurement must wait for your permission. Our server keeps standard access logs for the period in section 7. The cookie policy says the same thing at greater length.

The app

A mobile app has no cookies, but it does use identifiers stored on the device, which are the equivalent technology and deserve the same disclosure.

Device identifier
A random value the app generates on first launch and keeps in the iOS Keychain or Android keystore. It is what lets your purchases and credits survive a reinstall. It is not the hardware identifier of your phone, is not shared with any other app, and is deleted with your account.
User ID and session token
Held in the same secure store. They authenticate your requests. Strictly necessary; the app cannot function without them.
Local preferences and cache
Your language choice, onboarding state and cached images and configuration, held in the app's private storage so it starts quickly and works briefly offline. Cleared when you delete the app.
Push token
Only if you enable notifications. See section 5.

None of these are advertising identifiers. The app does not read the IDFA or the Android Advertising ID, does not use the App Tracking Transparency framework, and does not participate in any cross-app or cross-site tracking.

13. Children

Retyla is not directed at children. You must be at least 13 years old to use it, and at least 16 — or the minimum digital consent age in your country, if that is higher — where local law requires it; in Türkiye, users under 18 need their parent's or guardian's consent. We do not knowingly collect personal data from a child below those ages. We do not ask for a birth date, because asking would collect more personal data than the service needs, and we do not operate in the Kids category of either store. To be exact about what that means: the age limit is a condition of the terms of use rather than a technical gate. There is no age-verification screen, and we cannot tell from a user ID how old the person holding the phone is. We rely on the store's own age rating and on the person agreeing to the terms — and we would rather say that plainly than imply a check that is not there.

If you believe a child has used Retyla, write to privacy@retyla.app and we will delete the account and its data. A photograph of a child uploaded by an adult is treated like any other photograph and erased on the same schedule; please do not upload photographs of children who are not in your care.

14. How we protect your data

No system is immune. These measures reduce risk; they do not eliminate it, and we would rather say so than promise otherwise.

15. If something goes wrong

If a personal data breach occurs that is likely to result in a risk to your rights and freedoms, we will notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware of it, as Art. 33 GDPR requires. Where the risk is high, we will also tell affected users directly and in plain language — what happened, what data was involved, what we have done, and what you should do — under Art. 34. For users in Türkiye we will also notify the Personal Data Protection Authority and the affected data subjects in line with the Board's decision on breach notification.

16. EEA and UK: complaints

If you think we have handled your data unlawfully, please tell us first at privacy@retyla.app — most issues are a misunderstanding we can clear up in a day. You do not have to, though. You have the right to complain to a supervisory authority, in the EU member state of your habitual residence, place of work, or the place of the alleged infringement. There is no "lead supervisory authority" for Retyla and we will not name one: the one-stop-shop mechanism in Art. 56 GDPR applies to controllers with a main establishment in the EEA, and Retyla has none — so the authority for your own country is the right one to write to, not a preferred regulator of ours. In the UK, that authority is the Information Commissioner's Office (ico.org.uk). You also have the right to an effective judicial remedy.

17. Turkey: your KVKK notice

This section is the disclosure required by Article 10 of Law No. 6698 on the Protection of Personal Data (KVKK) and sets out the rights in Article 11.

Data controller (veri sorumlusu)
Retyla — see section 1. VERBİS registration: not required. Under the Board's decisions, data controllers whose annual employee count and annual balance sheet stay under the thresholds, and whose main activity is not the processing of special category data, are outside the registration obligation, and Retyla stays under them. Contact for all KVKK matters: privacy@retyla.app.
Personal data processed
The categories in section 5: visual data (the photograph you select and its result), transaction and identifier data, technical and device data, and, if you write to us, contact data.
Purposes of processing
Delivering the enhancement you requested, running your account and credits, completing and recording purchases, keeping the service secure and reliable, fulfilling legal obligations, and answering your requests.
To whom and for what purpose data may be transferred
To the processors in section 8 and, where abroad, on the basis in section 9; and to public authorities where a law obliges us.
Method of collection and legal ground
Collected electronically through the app and this website. Legal grounds under Art. 5: necessity for the performance of a contract, Art. 5(2)(c); necessity for compliance with a legal obligation, Art. 5(2)(ç); legitimate interests that do not harm your fundamental rights, Art. 5(2)(f); and your explicit consent, Art. 6(2), for visual data where it counts as special category data and for notifications.
Your rights under Article 11
To learn whether your personal data is processed; to request information if it is; to learn the purpose and whether it is used accordingly; to know the recipients at home or abroad; to request correction of incomplete or incorrect data and notification of that correction to recipients; to request erasure or destruction under Art. 7 and notification of that to recipients; to object to a result produced solely by automated analysis; and to claim compensation for damage caused by unlawful processing.
How to apply
Under Art. 13 and the Communiqué on Application Procedures, send your request to privacy@retyla.app, including the details the Communiqué requires and the user ID from your Profile screen so we can find the account. We answer within 30 days at the latest and free of charge unless the response requires a cost, in which case the tariff set by the Board applies. If you are not satisfied, or we do not reply in time, you may complain to the Personal Data Protection Board (KVKK) within the statutory period.

18. Changes to this policy

We update this policy when the product changes, when a processor changes, or when the law does. The effective date at the top always reflects the current version. If a change materially affects how your personal data is handled — a new processor, a new purpose, a longer retention period — we will tell you before it takes effect, through a notice in the app, and where consent is required we will ask for it rather than assume it. Continuing to use Retyla after a non-material change means the updated policy applies to you.

19. Contact

Privacy and data rights: privacy@retyla.app. Everything else: support@retyla.app, or the support page. Email is the channel that reaches us; the operator's postal address is published on the app's store listings — see section 1. Related documents: the terms of use, the cookie policy, the refund policy and the delete my data page.