Delete your account

Account deletion in Moonjar is permanent and immediate. There’s no soft-delete, no grace period, no recovery path. This page is what gets purged and what to know before you do it.

Before you start

• You’re sure. Once deleted, there is no way to restore an account or its data.
• If you want to keep anything, export or screenshot it first — the deletion runs through every table at once.

Steps

1. Open Settings → Account.
2. Tap Delete account. [TODO: VERIFY exact button label and location.]
3. Confirm. The deletion runs in a single database transaction.

When the delete finishes, you’re signed out. Trying to sign in again is the same experience as a fresh user — the email is no longer registered.

What gets deleted

Everything you own:

• Documents and document fields, attachments, embeddings.
• Conversations and every message you sent (including in chats shared with other people — see Shared content, below).
• Memories.
• Collections, collection fields, collection items, item values, references between items.
• Reminder lists, items, checklists.
• Trips and every booking attached to them — flights, accommodations, ground transports, rail journeys, bus and coach bookings, ferries, cruises, activities, restaurants, parking, shows. Saved places, trip checklists, trip suggestions, trip conversations, trip summaries.
• Notifications, daily summaries, push tokens, automation runs, automation daily-usage rows.
• Memberships in groups (and the groups themselves if you owned them — see Shared content).
• AI cost telemetry, processing-queue rows, OAuth-issued tokens (Moonjar’s MCP server tokens), and per-account auth artifacts (OTP codes, sessions).

Every row is hard-deleted, not soft-deleted.

Shared content

A few cases worth knowing about:

• Groups you own are deleted outright. If the group has other members, their shared state goes with it. (Group ownership doesn’t currently transfer.)
• Conversation messages you sent in chats owned by other users are also hard-deleted. Better to leave the chat clean than to leave “[Deleted]” placeholders.
• Items other people shared with you are unaffected — their documents, memories, and collections still exist on their accounts.

Why it’s a single transaction

Account deletion runs as one database transaction. Either every row is purged or none of it is. There’s no half-deleted state where some content sticks around but the user row is gone. Cascading foreign keys handle most child rows; the deletion route explicitly enumerates the tables that don’t cascade so nothing is missed.

Limits

• No undo. Once committed, the data is gone.
• No grace period. Some apps queue deletions for 30 days; this one doesn’t.
• No partial export bundled with the delete. If you want a copy first, do it before tapping the button.

See also

• AI consent — revoking consent means deleting the account; this is that path.
• Privacy policy — what’s retained on Moonjar’s side after deletion (nothing user-owned; some aggregate logs stripped of identifiers may persist as retention requires).