Delete Your Data

01 Email directly or prepare a message here

Email contact@takeloft.app and state that you want your Takeloft app-user record and associated personal information deleted, or describe the particular information concerned. A subject such as “Takeloft deletion request” is sufficient. You can email without the app installed, without app access and without a prior in-app request.

The optional form on this page prepares a message addressed to us in your own email service. You may describe the deletion scope and supply an app-user reference, creation or order reference, device model and additional explanation if useful. These details are optional; the required confirmation concerns whether you are the person involved or are authorised to act for them.

Preparing or opening the email does not send a request to Takeloft. The website does not send or store the form information. Review the recipient and prepared text, then send the message from your own email account. We receive the request only when the email reaches us.

If the usual email action does not open a composer, the page also offers Open in Gmail, Open in Outlook.com, a retry action, copying the complete email and the full prepared text. Use whichever option works for your device or browser, or write directly to our address. A draft or copied message still needs to be sent by you.

An available reference may help locate the records, but there is no Takeloft registered email address or password to supply. Explain when an identifier is unavailable. We may need limited information to confirm your authority and avoid removing someone else's data; do not send store credentials, authentication codes, full payment details or unrelated identity documents.

02 Save any result and relevant purchase reference

Export an available image or video you want to keep before deletion or its routine removal deadline. Once the service record and its media have been erased, they cannot be recovered from those deleted records. Removal can also erase the task history and associations that connected your device with previous creative activity.

Downloaded files and copies shared with another person or independent service remain outside our controlled systems and processors. Our deletion process does not reach those separate copies. Use the relevant device or recipient's controls if you want them removed too; copies held by a provider for us remain within our service deletion scope.

Keep an available order reference or receipt for an unresolved purchase. You may ask support about a paid benefit before or alongside deletion, but doing so is not a requirement for removal. Deleting information does not automatically ask for a refund and does not by itself waive a valid purchase remedy.

You can request purchase help and deletion in the same message. Explain both purposes so that the relevant data and any necessary independent transaction records can be handled separately. The Google account used for a store purchase is independent, and deleting Takeloft information does not close it or remove Google's own payment records.

03 Use the deletion control in Personal Settings

Open Personal Settings in Takeloft and use the deletion control provided there. Review the confirmation information and follow the steps shown to request removal. This concerns the app-user record and associated personal information; Takeloft does not require registration or login.

You do not have to complete this route before emailing us or using the website's email-preparation form. If you cannot open the app, locate the control or complete its steps, use email independently and explain the issue. Reinstallation and a new login are not conditions for starting a deletion request.

The Android app is currently coming soon, with no published Google Play download link. Email remains available for questions before release. The request routes described here address the same removal scope, subject to necessary verification and the limited treatment of independent records below.

Use available references if they help describe the request, but do not send private creative files merely to demonstrate app access. We can discuss proportionate alternatives if a reference is missing. The Privacy Policy explains other information rights and how to raise a concern about their handling.

04 Removal across our systems and processors

Following the verification reasonably needed for the request, we remove the relevant app-user record, associated personal information and creation information across systems we control and processors acting for us. Appropriate removal instructions extend to providers holding information on our behalf. The scope is not confined to the final media file.

Creation information includes source and output media, input and output images or videos where present, prompts, parameters, settings, task identifiers and records, status, timestamps, metadata, links, associations, previews, thumbnails, derived files and every copy. The same scope applies inside logs, support conversations and attachments, reports, caches and backups.

All creation information is independently deleted within 48 hours from input upload start, or from prompt submission when there is no upload. Outputs, related records and copies share the original deadline. Completion, a retry within the request, copying or internal transfer cannot create a new period.

Automatic creation deletion does not wait for verification of a manual request, a support response or completion of a payment or safety investigation. Any independent record still needed after that deadline must contain no creation content, task details, metadata or associations. A processor or backup does not provide a longer retention exception.

The manual-request timetable below concerns handling your request and the wider app-user information. It never extends the automatic creation deadline. Files you exported beyond our systems and Google's independently held records have the separate treatment described earlier, while all copies processed for us remain within scope.

05 Expected handling and limited independent records

We begin addressing a manual deletion request promptly after we see it and expect to complete it within 30 days. Special circumstances may require a lawful extension; we will tell you when an extension is needed and explain it. If applicable law requires a shorter period, we follow that requirement.

That expectation does not change the 48-hour maximum for creation information. Routine deletion continues from the original upload start or prompt submission without an upload, even while a manual request is being located, verified or processed. No extension of the manual process permits creation information or associations to remain longer.

Independent records may be needed for accounting, tax, a payment dispute, security, fraud prevention, a legal claim or another applicable obligation. We limit their content, access, use and retention to the purpose that justifies them. They must not preserve creative material, task information, metadata or links after the creation deadline, or continue ordinary use of a deleted app-user record.

Independent installation-source attribution information is addressed in the Privacy Policy and does not contain creation data. No retained user information is used for AI training. Non-creation information temporarily held in a protected backup is isolated from ordinary use, removed through the relevant process and subject to reapplication of deletion if a backup is restored. Creation information in backups follows its original deadline.

We will explain any verification or relevant retention exception. If we cannot complete a request in full, we will give the reason and available options. You can ask FM DISTRIBUTORS ( PRIVATE ) LIMITED about information found, removed or retained for a separate lawful purpose by contacting contact@takeloft.app, and use any further privacy or complaint rights available to you.