Service Diaries
Account & Data Deletion
AIM ATTITUDE INC. · Version 1.0 · Published October 11, 2026
Service Diaries is in development. This guidance explains the current local controls and distinguishes them from planned community account deletion. There is no live Service Diaries account to delete today.
1. Choose which information you mean
A private diary entry, a separate sharing copy, an online account and an exported backup are different things. Deleting one does not necessarily remove the others. If writing is missing or the app fails to open, do not uninstall, reset or experiment with a recovery file as a troubleshooting step. Ask for help with the app version and error message, without sending private writing or recovery codes.
| Action | What the current app does | What it does not do |
|---|---|---|
| Delete an entry in My Diary → Kept for Me | Removes the selected original and its reflections from active local diary storage | Does not remove separate review copies, earlier exports or independent copies |
| Remove an earlier demo post | Removes that local demo post and marks its related sharing history as removed | Does not erase the private original or perform a remote takedown |
| Delete your own local reply | Removes the reply from the local demo | Does not contact another device or server |
| Remove or change a local profile picture | Changes the local profile | Does not delete the original from your photo library or older backups |
| Reset demo and delete my local activity | Clears local diary and demo activity and profile through the confirmed reset flow; restores fictional examples and clears policy and signup acknowledgments | Does not delete a real account; age restrictions remain; the encryption key is not destroyed and forensic erasure is not guaranteed |
| Delete an exported backup | You remove the file from your chosen destination | The app cannot remove copies, trash folders or provider backups elsewhere |
The current app does not provide a dedicated delete or discard control for every ordinary sharing review copy. Deleting an original therefore does not promise deletion of all copies. Do not use a whole-app reset to remove a single copy from a working diary.
2. Preserve recovery before intentional deletion
If you want to keep a copy, prepare an encrypted export and separately retain its matching recovery code before intentionally deleting writing. An export contains diary entries, drafts, tags and reflections. It excludes profiles, sharing copies, reports and age or policy acknowledgments. Import is designed to merge writing; device-restoration and upgrade verification is continuing.
An old export may restore an entry you later deleted. Remove obsolete backups from each chosen location if you do not want that possibility. AIM ATTITUDE cannot retrieve a lost recovery code or remotely erase a user-held export. A system or source-code backup is not a substitute for a usable diary export and code.
3. Current account status
Create account and Sign in are previews. There is no live Service Diaries account to erase, and Reset demo is not account deletion. Uninstalling is not a request to delete an online account or support email.
Online account deletion is still under development. A recorded request, revoked session or hidden story is not the same as completed erasure.
4. In-app account deletion — planned community
Before accounts launch, a discoverable Delete account action would be available in Settings & privacy, with accessible navigation, a clear explanation and appropriate recent authentication. Support email would not be the ordinary required route. Deletion would not involve surprise charges, retention pressure or unnecessary obstacles.
A confirmed request would receive a reference. Community access would be disabled, sessions revoked and authored content hidden while deletion runs. Account identifiers, profile, submitted stories and replies, unnecessary report or block links, caches and retained identity tokens would be removed according to the published schedule. Any Sign in with Apple revocation requirements would be incorporated into the completed process.
The app would distinguish “request received” from “deletion completed,” with understandable progress, failure and completion information. Recovery from a partial failure must not duplicate data or restore removed visibility.
Deleting a community account would not silently erase independent local writing. Local deletion would be a separate, explicit choice, with an opportunity to preserve a backup. Account loss or a new identity must not expose another person's local diary. These protections require implementation and verification before live accounts are offered.
5. Copies, retention and legal exceptions — planned community
Online deletion periods are not yet finalized or implemented. The periods for primary erasure and recovery-copy expiry, and any permitted extensions, will be explained before community launch. Internal targets do not replace legal deadlines.
Limited information may need to remain for a specific legal duty, an established legal claim or a documented security purpose where law permits. Any exception would need a reason, restricted access and a review or expiry date, with an explanation to the requester where permitted. A limited exception would not justify retaining an entire account indefinitely.
Restoring service backups must not restore deleted accounts or removed stories. Deletion and restriction records would need to be applied before reopening access. Staff-held exports and provider copies would be included in the deletion process. Independently retained screenshots cannot necessarily be recalled, but AIM ATTITUDE remains responsible for copies it controls.
6. Support and nonmember requests
Contact servicediaries@aimattitude.com about privacy, deletion or identification concerns. You do not need to join a community to contact us. Send a relevant reference and brief explanation; do not send a full diary, password, recovery code or unnecessary identification documents. This address is not an emergency or continuously monitored moderation service.
For support emails or other information actually received, requests require proportionate verification, application of relevant rights and deadlines, and confirmation of the outcome. A person asking to remove an identifying story would not need to own the author's account. A report alone does not establish a violation; protective restriction and contextual review may be appropriate while a concern is assessed.
Where applicable, rights may include using an authorized representative and appealing a refusal, with an explanation of the reason and relevant escalation route. The live community's request, verification and appeal procedures remain under development. Applicable legal rights remain available.
7. Updates and related policies
Instructions will be updated to describe verified controls before live accounts become available. The distinction between a request and completed deletion, user-held backups, legal exceptions and independent copies will remain clear.
Read the Privacy Policy, Terms of Use and Safety & Moderation Policy for related information.