Data Deletion

Send a message to support@warmpath.net saying that you want your Warm Path user data deleted. A subject such as “Warm Path data deletion” helps identify the request. You do not need to register, sign in, reinstall the app or complete an in-app step before using this route.

Include available information that helps identify the relevant app records, such as an app reference or an order reference if the request also concerns a purchase. Do not guess an identifier you no longer have; explain that it is unavailable so we can work out what proportionate alternative information is needed. Verification is used to avoid deleting someone else's data, not to require a Warm Path account.

Do not send passwords, verification codes, full payment-card details or unnecessary identity documents. You do not need to attach your creative files just to request deletion. If clarification is necessary, it should be limited to identifying the records and your connection to them.

Warm Path's deletion option is in Personal Settings. Open that area, choose the deletion option and review the confirmation before proceeding. It concerns the user data and service records associated with your use of the app, even though Warm Path does not have registered logins.

The app is currently in development with its Google Play release coming soon. If you cannot access Personal Settings, no longer have the app or cannot complete that flow, email support instead. The email route is independent; you do not have to make the in-app option work first.

A Google account used for the store is separate. This process requests deletion from Warm Path and does not close your Google account or remove records Google independently holds under its own obligations and policies.

Save creations you want to keep before deletion or the ordinary retention deadline. Once information is erased, we cannot recover the creation from that deleted record. Removal can also affect the app history or links that previously connected you with a task. Warm Path is not a permanent storage service.

A file already downloaded to your device or shared with another person or service is a separate copy. You control removal of those copies using the relevant device or service; requesting deletion from us does not reach them.

For an unresolved payment issue, keep the store receipt or order reference. Deletion is not itself a refund request, but it does not require you to abandon a purchase remedy. You can request deletion and purchase support at the same time. Do not delay a privacy request merely because a separate transaction still needs investigation.

A deletion request covers applicable app-user information and service records, including all information associated with your creations. That includes input and output images and videos, prompts, template selections, parameters, task IDs, status, timestamps, metadata, links, associations and copies. It is not restricted to finished media or a single generation environment.

Ordinarily, all creation information is removed within 36 hours from upload start, or prompt submission when no upload is involved, without a deletion request. All results and associated records from the same request share that deadline. Copying a record, generating an output or including information in a support case does not restart it.

This scope includes all controlled systems and systems processing for us, including task records, logs, attachments, caches and backups. A support or safety process is not an exception permitting longer retention of creation details. Separate exported files and records held by an independent store remain subject to their own handling, as explained above.

We may need independent records for tax or accounting duties, purchase disputes, security, fraud prevention or another legal obligation. They are limited to the information and period needed for that purpose. Retaining such a record cannot preserve creation content, task information, metadata or associations beyond the creation deadline, and does not authorise ordinary continued use of app-user records that should have been deleted.

Attribution information is distinct from creation information and is handled under the Privacy Policy and applicable deletion rights. A necessary independent record is not used for AI training. If non-creation information remains in an isolated backup while it is removed through the applicable backup process, it must not return to active use on restoration; relevant deletion instructions must be reapplied. Backups containing creation information remain subject to the same creation deadline, not a longer backup exception.

Where a legal requirement affects removal of independent information, we explain the relevant reason and available options as applicable. Contact us if you need clarification about what was located, what was removed or a record retained for a separate lawful purpose. Privacy complaint and rights routes remain available.