Deleting your Astra Style account and your data
Last updated: 8 October 2026
1. If you are using the guest trial
The trial uses an anonymous Supabase account for server-side profile, wardrobe and styling records. Personal garment photographs remain on your device until identity linking; generated inspiration may be stored privately on our servers. Deleting the app removes local files but does not delete server data. Use the in-app account deletion control before uninstalling.
2. How to request deletion
Open Profile → Privacy & Data → Delete account, review the confirmation and submit the request. The server verifies your current identity and removes owned files and account data. The app shows the returned status; a pending or failed request is not a completed deletion.
If you cannot use the app, contact us using the email process below.
Email [[NEEDS INPUT: deletion request email address]] from the email address on your account, with the subject "Delete my account".
We will confirm that we have your request, verify that it came from the account holder, and tell you when it is done. [[NEEDS INPUT: identity verification method for a deletion request, particularly for Sign in with Apple users whose account email is a private relay address]]
[[NEEDS INPUT: the completion window we commit to — e.g. within 30 days of a verified request — and the interim status we give you]]
Cancel your subscription separately
Deleting your account does not cancel an App Store subscription. Cancel it in your Apple account settings before or after deletion, or Apple will keep billing you.
3. What deletion removes
Deleting your account removes your authentication identity. Every record in our database that belongs to you is linked to that identity and is removed with it:
| Removed | What it contains |
|---|---|
| Profile | Display name, avatar, location name, time zone, preferences, subscription tier. |
| Style profile | Style goals and identities, colour preferences, fit and formality preferences, style summary, the preference-quiz vector, and the style embedding. |
| Body profile | Height, weight, chest, waist, inseam and neck measurements, sizes, fit notes, the derived frame characteristics, and the appearance details including any reference to your selfies. |
| Lifestyle profile | Occupation, dress code, typical week, occasions, budget, brands, laundry and travel habits, attire needs, sustainability preference. |
| Closet | Every garment record and every garment image record, with their attributes, purchase details, wear counts and embeddings. |
| Outfits | Outfits, their contents, and your entire wear history including ratings and written feedback. |
| Kyra | Every conversation thread and every message in it. |
| Style memories and feedback | Every inferred preference, with its embedding, and every like, dislike and reason you recorded. Style memories are hard-deleted by design — the schema has no "hidden but kept" state for them. |
| Planning | Occasions, including any calendar event identifiers, and daily briefs. |
| Style Studio | Every generation record, including the prompt payload and the paths of the reference and result images. |
| Shopping | Every product evaluation we produced for you. |
| Subscription record | Our copy of your subscription state. |
| Authentication identity | The account itself. |
Your images
Your photographs and generated images are files in private storage, not database rows, and deleting them is a separate operation from deleting the records that point at them. Deletion is designed to remove everything stored under your account's own storage path — the garment photos, the background-removed versions, the reference selfies and body images, and the Style Studio outputs — and then, as a second line of defence, to sweep any storage record left behind under that path.
The deployed account-deletion server routine removes the owned files through the private Storage API before deleting the authentication identity, then verifies cleanup. Individual image removal also uses server-owned jobs with tracked, retryable file cleanup. Copies you already exported or shared outside the app are not recalled by removing the private origin.
4. What survives, and why
- A record that a deletion happened. We keep the deletion request record — its status and its timestamps. When the deletion completes, your user identifier is removed from that record and replaced with a one-way SHA-256 hash of it, so we can confirm a specific deletion completed without keeping the identifier.
- The shared product catalogue. Products, retailers, prices and links are shared across all users and contain nothing personal about you. They are not deleted, because they are not yours.
- Apple's records. Apple holds your purchase and subscription history under its own policies. We cannot delete those.
- Backups. [[NEEDS INPUT: backup retention window, and whether and how deletions propagate into backups]]
- Anything we must keep by law. [[NEEDS INPUT: whether tax, chargeback or fraud-audit obligations require retaining an anonymised billing record after deletion. The schema currently deletes subscription records outright with everything else; the migration notes flag this as a question for legal and finance before launch, and no anonymised-retention table exists]]
- Data already sent to our model provider. Provider-side retention depends on the API and the settings and contractual terms of the account we use. Copies held by a provider are outside our direct deletion control; this draft does not assert that zero retention has been approved for the account. [[NEEDS INPUT: OpenAI's retention window for API requests under the account this app uses, and whether a zero-retention arrangement is in place]]
5. Deleting less than everything
You can edit your profile and closet, remove individual reference or generated images, and inspect and delete individual style memories. Removing a reference also removes its derived variations and saved memberships. The app refuses the reference-removal request while a related generation is active, so an active job is not partially erased.
6. Getting a copy of your data first
Profile → Privacy & Data provides a shareable JSON export of your account records and safe Storage metadata. Image-file attachments are not included in that structured export. Prepare your copy before requesting account deletion; completed deletion removes the server records used for export. Contact us if you need further assistance. [[NEEDS INPUT: the turnaround time for assisted access and export requests]]
7. Contact
Deletion requests: [[NEEDS INPUT: deletion request email
address]]
Privacy questions: [[NEEDS INPUT: privacy contact email
address]]
[[NEEDS INPUT: full legal entity name]],
[[NEEDS INPUT: registered entity address]]