Service Diaries
Privacy Policy
AIM ATTITUDE INC. · Version 1.0 · Published October 11, 2026
Service Diaries is in development. This policy describes the current development app. Live accounts, community sharing and staffed moderation are not available. Sections marked Planned community describe future features that are not operating.
1. Our purpose and this policy
Service Diaries creates space for adults to express how a service interaction affected them, reflect, recognize kindness and connect through shared human experience. Service Diaries is developed by AIM ATTITUDE INC. AIM is the philosophy behind the experience.
Private by intention. Shared by choice. Saving a diary entry and submitting a story are separate actions. This policy concerns the Service Diaries app and communications about it. Visits to the AIM ATTITUDE website are also covered by the website's Privacy Policy. This document does not replace the store's shopping, payment, shipping or refund policies.
Contact: servicediaries@aimattitude.com. Do not send private diary text, recovery codes, passwords or unnecessary identifying information. This address is not an emergency or continuously monitored moderation service.
2. Information in the development app
Account screens are demonstrations. Sample name, email and password fields are held temporarily on screen and cleared when continuing or leaving; they do not create an account. Use fictional information during development testing.
| Information | Location and purpose | Who receives it through this app |
|---|---|---|
| Diary entries, unfinished writing, personal tags and reflections | Encrypted local storage for writing, editing, search and reflection | No Service Diaries server or moderator receives it |
| Sharing review copies and local demo stories, replies, reactions, saved stories, blocks and reports | Local storage for previewing community interactions | No live feed or report recipient; a local report does not reach staff |
| Nickname, work area, avatar and optional profile image | Encrypted local profile for personalizing the demo | Not uploaded; a selected image is resized and re-encoded without its original photo metadata |
| Eligibility declarations, underage restrictions, policy version and acknowledgment timestamps | Local settings for access and prototype acknowledgments | Not a server account record; not every setting is part of the encrypted diary storage |
| Apple age-range response, where available | Used by the signup preview to determine eligibility | The app requests an age range, not a date of birth |
| Optional writer region, feelings and experience tag | Stored with an entry; optional fields for a possible sharing copy | No current upload; a region describes the writer, not the guest or incident location |
| Support email and website visits you initiate | Your email, browser and chosen service | The recipient or website receives what you send and the information normally involved in that connection |
Apple age-range confirmation is not available in every development configuration. Sample sign-in is not verified identity or age assurance.
The current native app has no advertising, tracking SDK, automatic diary upload, session replay, automatic screenshots or live crash-email collector. Its limited support suggestions and sharing checks run on your device. Temporary support classifications are not saved in the diary snapshot or sent to staff. These statements do not describe all processing by iOS, your keyboard, a chosen file provider, email services or the Shopify website.
3. Private writing and deliberate sharing
KEEP FOR ME saves to My Diary. SHARE creates a separate, editable review copy. Personal tags, reflections and reflection drafts are excluded from that copy. Feelings and an experience tag may be included only through the separate sharing choice; inspect the final preview. Editing or deleting the original does not automatically change or delete an existing review copy.
Sharing checks can miss identifying details or misunderstand language. Removing a name does not make a story anonymous: a date, role, region and unusual event can identify someone in combination. Do not include customer records, credentials or other people's confidential information in private writing or submissions.
The current app does not publish the copy. An attempted submission explains that sharing is unavailable. A policy acknowledgment does not grant access to the rest of your diary.
Planned community: only the exact version you intentionally submit would be sent for restricted review. A reviewer could see the submitted text, permitted metadata and necessary account or case information, never your private diary as an attachment. The audience would be explained before submission. The proposed first audience is signed-in members; this restriction is not implemented. Other people could copy shared content. A nickname or members-only audience does not guarantee confidentiality or anonymity.
4. Device protection and recovery
The current app encrypts normal diary and profile snapshots with AES-256-GCM and a device-only Keychain key. It requests device authentication on normal launch, relocks when placed in the background and covers inactive app content. Device, upgrade and accessibility verification is continuing. Anyone who knows your device passcode may unlock the app. No system can guarantee protection against a compromised device or content copied while visible.
New encrypted diary files are excluded from ordinary system backups. An encrypted export you create contains diary entries, drafts, tags and reflections, with a separate random recovery code. It excludes the profile, sharing copies, reports and age or policy acknowledgments. A chosen cloud destination may receive the encrypted file and file metadata. Anyone with both the file and its code can read that backup using compatible software.
AIM ATTITUDE has no copy of your device key or recovery code through this design. Losing both usable device access and a usable backup with its code can permanently lose writing. Apple account recovery and source-code backups do not restore it. Older exports may contain earlier data. See Account & Data Deletion. A failed save is not a durable backup; follow the app's recovery message without resetting it.
5. Planned community data
Planned community: processing would be limited to account identity, sessions and eligibility; nickname and selected role; submitted stories and replies with chosen sharing fields; moderation decisions; reports, blocks and appeals; request records; and necessary technical or security information. The purposes are access, deliberate publication, abuse prevention, support and honoring privacy choices. Private originals and local support classifications would remain separate.
Sign in with Apple and Supabase are proposed services, not deployed app features. Apple may provide a relay email if that sign-in option becomes available. Authorized reviewers would see assigned submissions and reports; support would have a narrower account or case view. Authorized operators and hosting providers may have technical access to server-held community data. That data would not be described as inaccessible to the operator or end-to-end encrypted.
Actual providers, processing locations, access arrangements, recipient categories and any international transfers will be described before community processing begins. No sale of diary content, emotional advertising, targeted-ad profile, third-party AI processing of writing or employer monitoring is proposed. Any change would require truthful notice and any consent required by law; general acceptance is not blanket permission.
For information AIM ATTITUDE actually holds, legally required disclosures are subject to review for validity and scope. A legal request does not give us the technical ability to retrieve an unuploaded device-only diary. Support emails, reports and future shared stories cannot be promised absolute secrecy.
6. Adults and sensitive information
Service Diaries is intended for people 18 and older. Do not misrepresent your age or provide information identifying a child. Contact us if you believe a child has supplied information to AIM ATTITUDE, without sending additional sensitive content. An age statement alone does not verify a person's age; live eligibility, investigation and deletion procedures must be established before community access opens.
Writing about emotions can reveal sensitive personal or health information, even though Service Diaries does not provide medical care. Any required consumer-health-data notice and specific collection or sharing consent must be in place before affected processing starts. A privacy acknowledgment, age confirmation or sharing checkbox does not replace those requirements.
7. Retention, deletion and privacy requests
Current local records remain until changed or deleted using available controls. Deleting an entry removes the original and its reflections; separate review copies and exported files remain. Reset demo clears local activity and restores fictional examples; age restrictions remain. It is not server erasure, secure destruction of every device artifact or deletion of user-held backups.
Planned community: each information category would be retained for its specified purpose and disclosed period, or a narrowly documented legal requirement. Community records, moderation evidence, consent records, support mail, security logs and recovery copies would have separate retention arrangements. Those periods and the deletion schedule are not yet finalized. Retained exceptions would require a reason, limited access and a review or expiry date.
For information AIM ATTITUDE actually receives, contact us about access, correction, a copy, deletion or withdrawal of an optional choice. Depending on applicable law, additional rights may include restrictions on certain uses, information about recipients, an authorized representative and an appeal of a refusal. Verification should be proportionate and must not require your diary or recovery code. Mandatory rights and deadlines apply regardless of this policy. Exercising a right must not result in unlawful discrimination. The live community's request and appeal workflows remain under development.
Deleting a community account would be separate from deleting the local diary. Withdrawing sharing or consent cannot recall independently made screenshots or copies, but does not remove our responsibilities for information under our control. Uninstalling the app is not an account-deletion request.
8. Websites, support and optional destinations
The native app does not attach writing or profile information when it opens an independent support service, the AIM website or a blank support email. Destination and device providers apply their own practices; a link is not a confidentiality guarantee. Service Diaries does not receive your conversation with an independent support provider through these links.
The Shopify website may process connection information and use cookies or integrations under its own privacy practices. The native app's absence of tracking does not mean the website collects nothing.
9. Updates
Material changes will be explained before they apply, with a visible version and date and renewed agreement or separate consent where required. New uses of private writing will not be authorized retroactively. Prototype acknowledgments are not production consent. Policies will be updated to describe verified live features before those features become available. Accessible copies and prior effective versions will remain available.