Data Deletion

The deletion option is in Framelet's Personal Settings. Open that area, choose deletion and review the confirmation before proceeding. It concerns the app-user information and service records associated with your use, not a registered Framelet login. The app is currently unreleased, with Google Play availability coming soon.

If the app is unavailable, has been removed from your device or you cannot complete the in-app flow, you can use the email route described below. You do not have to solve an app-access problem before asking for deletion.

A Google account used for the store is separate from Framelet's records. This process does not close that Google account or remove information independently held by the store under its own legal obligations and policies.

Write to support@framelet.net and state that you want your Framelet user information deleted. A subject such as “Framelet deletion request” helps identify the purpose. Email is an independent route: registration, sign-in, reinstallation and an earlier in-app request are not required.

Provide available details that help locate the records, such as an app reference or an order reference if a purchase is relevant. If you do not have an identifier, explain that instead of guessing. We can establish what proportionate alternative information is needed. Verification is intended to avoid removing someone else's information, not to impose a new login requirement.

Do not attach passwords, verification codes, full card details or unnecessary identity documents. Your creative files are not required merely to ask for deletion. Any further request for information should be limited to locating the affected records and verifying your connection to them.

Export a creation you want to keep before it is deleted or reaches the ordinary retention deadline. Once the information has been erased, it cannot be recovered from that deleted record. Deletion can also remove task history or associations that previously linked your app use to a result. Framelet should not be used as a permanent archive.

Files you already downloaded to a device, shared with another person or sent to an independent service are separate copies. Use the relevant device or service to manage those copies. A request to us does not reach files outside the systems we control or that process information on our behalf.

Keep receipts or order references if a payment issue is unresolved. You can ask for purchase assistance and deletion at the same time; neither request requires abandoning the other. Data deletion does not itself open a refund request or remove statutory purchase rights. State both purposes if your message concerns both.

Removal covers applicable app-user data and all information associated with creations. This includes source inputs, generated images and videos, prompts, settings, template selections, task identifiers, status, timestamps, metadata, links, associations and copies. It is not limited to finished media files or the environment that generated them.

All creation information is ordinarily deleted within 48 hours from upload start, or from prompt submission when there is no upload, without a separate request. Information and outputs belonging to the same request share that deadline. Completion, copying, support handling or an internal transfer does not create a new retention period.

The scope covers every controlled system and system processing on our behalf, including task records, logs, support attachments, caches and backups. A support or safety case is not an exception that permits creation details to remain longer. Exported copies outside these systems and independent store records have the separate treatment described above.

Some independent information may be necessary for accounting or tax duties, payment disputes, security, fraud prevention or another legal obligation. Its scope, use and retention are limited to the purpose that justifies it. Such a record cannot preserve creation content, task details, metadata or associations past the creation deadline. It also cannot be used to continue ordinary use of an app-user record that should have been erased.

Attribution information is separate from creative information and remains subject to the Privacy Notice and applicable deletion rights. No independently retained user information is used for AI training. If non-creation information remains temporarily in an isolated backup while the relevant backup process removes it, it must not return to active use on restoration; deletion instructions must be reapplied. A backup containing creation information has the same creation deadline, not an extended backup exception.

If a legal requirement affects deletion of an independent record, we explain the relevant reason and available options as applicable. You can contact us about what was located, removed or retained for a distinct lawful purpose. Further privacy rights and complaint routes remain available through the Privacy Notice.