Architecture & Privacy Declaration

Our Commitment to the Black Box Standard

I built Takomi after experiencing the burnout that comes from using wellness apps designed for engagement, not relief. Calm must come from ownership, not constant digital interaction. This document is our promise: a transparent look at the technical architecture (Flutter, Hive) that keeps your mind your space, ensuring you are never the product.

1. Data Residency (Local-Only)

All user data, including journal entries, custom layouts, and logs, is stored exclusively on your device. We use the Hive database for fast, encrypted local storage.

• No Accounts: Takomi operates without user logins or accounts, preventing server-side identity correlation.
• Offline-First: The app is fully functional with zero network access. All core tools are built to execute locally.
• Data Sovereignty: The Export Spaces feature allows you to download a raw .takomifile, putting full custody of your structured data in your control.

2. Unavoidable Platform Dependencies

To ensure the app can be distributed and monetized legally, Takomi must interact with the operating system (OS) vendors. These are the only instances where data communication leaves your device, and they are strictly OS-controlled.

• Purchases (Studio Membership): When you purchase or restore a Studio membership, the OS communicates with Apple's StoreKit or Google Play Billing to validate your receipt. Takomi never sees or stores your Apple ID or payment information. We only process the anonymized transaction status to unlock features.
• OS Crash Logs: If the app crashes, the OS may generate a crash report and submit it to the platform (Apple/Google), depending on your system preferences. Takomi implements PII stripping and does not use third-party crash reporters to ensure user content does not unintentionally leak.

3. Logging & Telemetry Commitment

Takomi is built with zero third-party analytics SDKs. We have taken steps at the code level to eliminate all internal log transmissions.

• Debug Silence: All in-app logging is routed through thesafeLog() utility, which is compiled out of the Release binary to ensure absolute silence in production environments.
• Notifications (Local Only): All mindful reminders for Studio members are implemented using Local Notifications. This means the schedule is stored on your device only, requiring zero server component and no unique push tokens.

4. Future Proofing (Local AI)

Should we proceed with the Aika reflective assistant concept, our commitment to ownership remains absolute. Any future AI function will be:

• Model on Device: The AI model will be shipped with the app binary and run entirely locally.
• Opt-in & User-initiated: It will be an optional Studio feature, never running in the background.
• Zero API Calls: No user data will ever be sent to a remote AI server (e.g., OpenAI, Google, etc.) for processing.