Ootry
Ootry

Privacy Policy

Ootry

Effective date: 27 August 2026

This Policy sets out the categories of personal data processed through the Ootry mobile application, the purposes and legal bases of that processing, the recipients to whom data is transferred, retention periods, and the rights of data subjects.

1. Controller

The Ootry application (“the Application”) is developed and operated by Ailancer, established in the Republic of Türkiye (“the Controller”, “we”). The Controller is the data controller within the meaning of Turkish Law No. 6698 on the Protection of Personal Data (“KVKK”) and of Regulation (EU) 2016/679 (“GDPR”).

All requests and notices under this Policy are to be addressed to dev@ailancer.com.

2. Scope

This Policy applies to personal data processed through the Application. It does not apply to the practices of third-party stores or websites reached from links displayed in the Application, which are governed by their own privacy notices.

3. Categories of personal data and purposes of processing

3.1 Installation identifier and device key. On first launch the Application generates a random identifier and a secret device key, both held in the device keychain. The identifier is processed in order to associate user content and credit balance with a device before an account exists. The device key is not transmitted; the Controller stores only its SHA-256 digest, which is processed in order to verify that requests concerning a user's library originate from the device entitled to make them.

3.2 Account data. Where the User elects to create an account, the user identifier and email address are processed in order to operate the account and to make credits, purchases and library content available across the User's devices. Authentication is performed by Supabase on the Controller's behalf. Where Sign in with Apple is used with the “Hide My Email” option, the Controller receives only the relay address assigned by Apple.

3.3 Profile data. Name, date of birth, height, weight and profile image may be provided at the User's option. Date of birth is processed in order to verify the minimum age requirement under Section 10; height and weight are processed in order to adapt generated output to the User's proportions.

3.4 Image data. Photographs of the User saved for try-on, garment images added to the wardrobe, output generated by the Application, crops submitted for product search, and the profile image are processed in order to provide the functions requested by the User. Image data is held in private storage and is accessible only by means of signed links which expire within minutes. No permanent public address is created for any image.

3.5 Device name and push notification token. The device name configured in the operating system and a push notification token are processed in order to distinguish the User's devices from one another and to notify the User of the completion of a generation the User has initiated.

3.6 Transaction records. Records of credits granted and spent, of search operations and of subscription status are processed in order to deliver purchased services, to apply rate limits, to prevent abuse, and to comply with accounting obligations.

3.7 Data retained on the device only. Product search history, language selection, notification preferences, the record of consent given under Section 5, and any cropping or colour correction applied by the User to output are stored solely on the User's device and are not transmitted to the Controller.

4. Legal bases

  • Explicit consent — KVKK Art. 5(1); GDPR Art. 6(1)(a): the transfer of image data to the providers identified in Section 5. Consent may be withdrawn at any time in accordance with Section 5.3.
  • Performance of a contract — KVKK Art. 5(2)(c); GDPR Art. 6(1)(b): operation of the account, storage and synchronisation of library content, and delivery of subscriptions and credits.
  • Legitimate interests — GDPR Art. 6(1)(f): application of rate limits, prevention of abuse, and security of the service.
  • Compliance with a legal obligation — KVKK Art. 5(2)(a); GDPR Art. 6(1)(c): retention of accounting records.

5. Transfer of image data to processors

5.1 The generation and search functions cannot be performed on the device alone. Image data is transferred to the following processors, each acting on the Controller's instructions and for the stated purpose only:

  • OpenAI — the User's photograph and the garment image, for the purpose of generating try-on output, applying a retouch selected by the User, and determining the category, colours and style of a garment. Data submitted through OpenAI's application programming interface is not used to train its models.
  • SerpApi, which in turn queries Google Lens — the crop submitted for product search, for the purpose of returning visually similar products. Photographs of the User do not form part of a product search.

5.2 No transfer under this Section takes place before the User has given explicit consent within the Application. Image data is not used for advertising, profiling or the training of any model, is not sold, and is not disclosed to any recipient other than those identified in this Policy.

5.3 Consent may be withdrawn at any time under Profile → Privacy in the Application. Withdrawal takes effect immediately and disables the try-on and product search functions. Withdrawal does not affect the lawfulness of processing carried out before it, and does not delete existing library content.

6. Other recipients

  • Supabase — database, authentication and image storage.
  • RevenueCat — verification and maintenance of subscription status; receives the installation identifier or, following sign-in, the user identifier.
  • Apple or Google — processing of payments, according to the store from which the Application was obtained. Payment instrument details are not disclosed to the Controller.
  • Sovrn or Skimlinks — where the User opens a shop from a search result, the destination address and the installation identifier are transmitted to the affiliate network for the sole purpose of attributing a click to a transaction. Name, email address and image data are not transmitted.

7. International transfers

The processors identified in Sections 5 and 6 may process personal data outside the User's country of residence, including in the United States. Transfers from the European Economic Area or from Türkiye are carried out on the basis of the safeguards made available by those providers, including the Standard Contractual Clauses adopted by the European Commission.

8. Retention

Image data, wardrobe content, generated output and profile data are retained until deleted by the User in accordance with Section 9. Records referred to in Section 3.6 are retained for the periods prescribed by applicable accounting and limitation legislation. Signed links to stored images expire within minutes of issue and are not reusable thereafter.

9. Deletion

9.1 Deletion of data. The Delete my data function removes saved photographs, wardrobe content, generated output, search crops and profile data from the Controller's systems and from the device. Credit balance and subscription status are not affected.

9.2 Deletion of account. The Delete my account function performs the deletion described in Section 9.1 in respect of every installation associated with the account, closes the credit wallet and deletes the authentication record. Deletion of an account is irreversible and any remaining credit balance is forfeited without refund.

9.3 A deletion request may alternatively be submitted to dev@ailancer.com from the email address associated with the account.

10. Age requirement

The Application is not intended for children under the age of 13, and a date of birth below that age is not accepted. Where the Controller becomes aware that personal data of a child has been processed, that data will be deleted without undue delay.

11. Data not collected

The Application contains no analytics, advertising or third-party tracking software, does not use the advertising identifier, and does not track users across other applications or websites. It does not request access to location, contacts, calendar, microphone or health data, and reads no data from Apple Health. The market used to order search results is derived from the language and region setting of the device and not from location data or IP address.

12. Security

Image data is held in private storage and is accessible only through signed links of limited duration. Requests concerning a user's library must be authenticated by means of the device key described in Section 3.1. Credentials for the providers identified in Section 5 are held on the server and are not present in the Application.

13. Rights of the data subject

Under KVKK Art. 11 and GDPR Arts. 15 to 22, the User has the right to obtain confirmation as to whether personal data concerning them is processed, to access that data, to request its rectification or erasure, to object to processing, to request restriction of processing, and to receive the data in a portable format. Rectification and erasure may be exercised directly within the Application. Other requests are to be addressed to dev@ailancer.com and will be answered within thirty days.

The User also has the right to lodge a complaint with the Turkish Personal Data Protection Authority or with the supervisory authority of their place of residence. The Controller does not sell personal information within the meaning of the California Consumer Privacy Act.

14. Amendment

This Policy may be amended. The amended version is published on this page bearing a new effective date. Where an amendment materially alters the processing of image data, consent is requested again in accordance with Section 5.2.

15. Contact

Ailancer — dev@ailancer.com