Manage your
Splicely data.

You may ask us to remove your Splicely app-user record and associated personal information, including all remaining creations, or name particular information if you want a narrower request. Splicely has no registration or login: an app-user record refers to service information connected with your use, not a sign-in account.

Removal reaches the information we control and the information held for us by processors. We direct those providers to remove the relevant records too. A creation means its whole set of information, including:

• The source and result: input and output images or videos, prompts, previews, thumbnails and derived files.
• The work behind the result: template choices, settings, parameters, task IDs and records, status, timestamps and other metadata.
• The connections and copies: links and associations, duplicates, and creation information in logs, reports, support messages or attachments, caches and backups.

Before removal, export any available result you want to keep. Deleted media and task records cannot provide that download again, and the history connecting a creation with your installation is removed as well. A file you already downloaded or independently shared stays with you or its recipient; use their controls to remove that separate copy. A processor holding a file for us is still covered by our removal process.

Keep a receipt or order reference for an unresolved purchase. Removing Splicely data does not close your Google account, erase Google's independent payment records or automatically claim a refund. It also does not waive a valid purchase remedy. You can ask for both deletion and purchase help in one message; resolving a charge or missing benefit is not a prerequisite for removal. /refunds explains the purchase process.

If you have the app available, open Personal Settings and find the data-deletion control. Read the confirmation information, then follow the steps shown to request removal. The control addresses your app-user record and associated information; it does not require you to create or sign in to an account.

You may instead write directly to support@splicely.net. Say that you want your Splicely information deleted and describe the scope. A subject such as “Remove my Splicely data” helps identify the purpose. You can use your inbox when the app is unavailable or uninstalled, or simply because email is the more convenient route for you.

Choose either route. There is no requirement to try Settings first, reinstall the app or complete an unsuccessful in-app attempt before emailing. If you do not have access to an identifier or the deletion control, tell us that rather than trying to recreate a record solely to make the request.

Splicely is in development for Android and Coming soon on Google Play; a published download link is not available here yet. The app route applies when the function is available. Email can already be used for enquiries or information you have supplied in correspondence, so you do not need to wait for release to contact us.

A short explanation is the starting point. An app, task or order reference you already have, relevant device context, or an earlier exchange may help us find the right information. These details are optional in the form on this page. If a reference is missing, say so; do not guess it, send a new private creation to demonstrate access or assume there must be a registered Splicely email address.

The form asks you to confirm that the request concerns you or that you are authorized to act for the person concerned. We may need limited follow-up information to verify that authority and avoid disclosing or removing someone else's records. Verification should be proportionate to the request. Passwords, authentication codes, complete payment-card details and unrelated identity documents should not be included.

Preparing the form assembles a draft on your device for you to review. It does not open an outside service or submit, send or store the fields on this website. Check the recipient and message in the preview before deciding how to send it. A request reaches support only when your email arrives; preparing or copying the text alone does not deliver it.

After reviewing the draft, choose your email app, Gmail or Outlook.com from the delivery selector and use Continue to open that service. You still review and send the email there. If it does not open, try the same route again, choose another service, copy the complete message or select the displayed text and paste it into an email. You can also write directly to our address. Selecting a webmail route passes the draft to that provider's compose interface, not to support.

We can discuss another proportionate way to locate the information when the details you have are incomplete. You do not need to give us access to your Google account or attach private source images to begin. Other information rights, including access and correction rather than deletion, are described at /privacy.

Creations have an automatic deadline whether or not you contact us: all their information is deleted within 48 hours from upload start. When a request involves no upload, prompt submission is the starting event. A generated result, its records and every controlled or processor-held copy share that original deadline.

Completion, a retry within the request, copying or transferring a file does not start another 48 hours. Nor does adding it to a support message, report, log, cache or backup. The full creation scope listed above is removed; deleting the visible result while keeping a task link or association would not satisfy the deadline.

Your manual request addresses the wider app-user information and the removal you have asked us to carry out. Support begins handling it promptly on receipt, and we expect completion within 30 days. If particular circumstances require an extension permitted by law, we explain why and the extension needed. A shorter legal deadline takes precedence.

The manual process cannot extend a creation's automatic lifetime. While we locate a record, verify authority or answer an enquiry, its original clock keeps running. A payment dispute, report, safety investigation or legal matter cannot keep creation information or its links past that deadline. Removing creation information does not depend on a support reply or verification being completed first.

We explain the outcome, any verification still needed and any part of a request we cannot complete, with the reason and available options. A necessary remaining record must have an independent purpose. It cannot be a hidden copy of a deleted creation or a way to continue ordinary use of an app-user record that should have been erased.

For example, accounting and tax obligations, a payment dispute, security, fraud prevention or a legal claim may justify limited independent information. Only the content, access, use and retention needed for that purpose may remain. By a creation's original deadline, every such record must have its creative content, task details, metadata, references, links and associations removed.

Independent installation-source attribution records are addressed in /privacy and do not contain creations. No remaining user information is used to train AI. The distinction is between a separately justified record and the creation information that must already be gone, not between different places where the same creative file has been copied.

Backups do not provide extra time for creations: their information and associations are removed by the same original deadline. A protected backup containing only independent non-creation records is restricted from ordinary use and removed through the relevant retention process. If a backup is restored, deletion must be reapplied so that removed information does not return to ordinary service use.

For clarification or review, contact MUSKUN PROPERTIES ( PRIVATE ) LIMITED at support@splicely.net and identify what remains unresolved. You may ask about information located, removed or retained for a stated independent purpose. The rights and complaint routes in /privacy remain available, including applicable access, correction, review and regulator routes. You can follow up without creating a login or withdrawing a separate purchase concern.