Deletion levels
Not all deletions are the same.
- Hide from archive.
- Remove private question text.
- Delete full reading.
- Delete profile.
deletion
Deletion should be clear and careful
Dangerous buttons should not be hidden, but they also must not be easy to click by accident.
promise
Prepare deletion for readings, profile, and future export before deletion.
value
Users know they control their history.
privacy
Deleting a private question should remove it from archive and future public cards.
Accident protection
Deletion should require explicit confirmation.
- Consequence text.
- Type DELETE later.
- Delay or confirmation email for profile.
- Export link first.
Empty state
Deletion tools are being prepared. Use support for urgent requests.
nearby rooms
Other account doors
live
All sealed answers in one place
Main job: restore access to a paid or saved reading across phone and desktop.
plannedPDFs, share-cards, and keepsake artifacts
Gather saved PDF scrolls, share-safe cards, and future premium reports.
plannedPayments without fog or panic
Gather payments, membership, gifts, refunds, and receipts in one clear room.
plannedPurchase history without accounting smoke
Separate user-facing purchases from internal accounting events.
plannedMembership as a habit, not a trap
Connect membership to retention: day, letters, passport, archive, and discounts.
plannedSettings without a labyrinth
Gather settings in one calm page.