What is deleted
After a verified request is approved for fulfillment, Moira removes the account’s saved charts and synastry data; complete natal reading packets and prose; Urania Speak threads, messages, summaries, insights, and packet snapshots; AI and dashboard caches; uploads; booking inquiries; local relationship records held on the server; unpublished drafts and revisions; bookmarks; reactions; first-party Moira product review and associated reports; and other account-private operational content covered by the request.
Verified account-deletion fulfillment bypasses the 30-day saved-chart Trash and permanently removes both active and already-trashed covered server records. Browser-local Trash still must be cleared on each device as described below.
Active Moira subscriptions are cancelled as part of fulfillment. Cancelling first remains recommended so you receive the quickest confirmation and avoid a renewal while verification is pending.
What may be anonymized or retained
Public blog posts and comments may remain under “Deleted user” unless you separately request their removal. Your first-party Moira product review is deleted rather than preserved under anonymous attribution. A practitioner profile and practitioner-specific reviews follow separate directory rules and may be removed or anonymized. Moira may preserve minimized billing, transaction, tax, security, deletion, dispute, and content-free audit records where law or a legitimate operational need requires them.
Moira sends the processor actions that are available and applicable: Clerk identity deletion and cancellation of recurring Stripe subscriptions are part of fulfillment. Anthropic does not provide this workflow with an account-specific erasure call, so its standard API-retention period applies to previously transmitted inputs and outputs. Providers may independently retain billing, fraud, security, legal, or backup records under their own obligations.
The live application records are removed immediately when fulfillment succeeds. Current MySQL backup copies rotate within 21 days and the public maximum is 30 days; deleted records are not available to the user during that interval and must be re-deleted before service resumes after any full backup restoration. Urania Memory is not included in those MySQL or backend-source backup sets. Deletion is not represented as instantaneous across independent provider backups.
Browser-local data must be cleared on each device
Signing out does not erase browser-local state. Server-side chart deletion or account deletion cannot remotely erase localStorage, sessionStorage, IndexedDB, exports, downloads, screenshots, or other copies outside Moira’s server records.
Browser-local data may include Workspace workstreams and checkpoints; current-subject state; settings and onboarding; stellium and Time Map preferences; astrocartography pins; computed chart, checkpoint-result, and Time Map caches; and chart-wheel session offsets. It may also include chart identities, names, birth dates/times, locations, saved-chart caches, and Writer Studio recovery drafts. After exporting anything you need, clear site data for moira-astro.com in every browser profile you used.
The Cookie & Browser Storage Policy lists the exact active storage keys and databases.
Request workflow
- Submit the account email below. A signed-in matching owner may be verified immediately.
- Otherwise, open the verification link sent to that email within 24 hours. No account information is revealed by the public form.
- After verification, Moira reviews and fulfills the request within 30 days, subject to a lawful exception or necessary clarification.
- Moira confirms completion to the verified contact channel. Deletion is permanent; retained/anonymized categories remain governed by the retention schedule.