Privacy Policy — The Algorithm of You
1. Overview
The Algorithm of You is a personal alignment and budgeting app. It has no user accounts, no advertising, no analytics or tracking SDKs, and no in-app purchases. This policy describes exactly what the app stores and the circumstances in which data leaves your device.
2. Data stored on your device
The app stores the following locally on your device (in the app's local storage). It is never transmitted except as described in Section 3, and it is deleted when you delete the app:
- Daily audit entries: date, habit check-ins, custom goals, alignment scores, and your written reflections (trigger, action, interest vector, micro-task)
- Your custom goals list
- Your Budget Counter data: budget period and amount, and your expense labels and amounts
- Your Weekly Planner items: the week, day, optional time, and text of each item, and whether it is marked done
- Your Mental Health Corner check-ins: your mood rating and any optional note you add
- Your settings: the alias/ID you choose to display, and the sync endpoint described below
The app asks for an alias or ID rather than your name. Budget Counter and Weekly Planner data are also stored locally first — and, like Daily Audits, they are synced to the spreadsheet endpoint described in Section 3 whenever they change. Mental Health Corner data is the exception: local only, always.
3. Data sync: Daily Audit, Budget Counter, and Weekly Planner (Google Sheets)
Three features send data to a Google Sheets web-app endpoint so it can be recorded in a spreadsheet:
- Daily Audit: When you tap "Save & Sync Today's Audit," the app saves that day's entry on your device and, in the same action, sends a copy — your alias/ID, the date, habit check-ins, custom goals, alignment score, and reflection text. Saving an audit always uses this sync; the current version has no separate offline-only save mode.
- Budget Counter: Budget data syncs automatically whenever it changes — when you set or change the budget amount or period, add an expense, delete an expense, or start a new period. Each sync sends your alias/ID, a timestamp, the budget period and amount, the expense label and amount (for expense events), and the running total spent and remaining balance after the change. These entries are recorded on a separate "Budget" tab of the same spreadsheet.
- Weekly Planner: Planner items sync automatically whenever they change — when you add an item, mark it done or not done, or delete it. Each sync sends your alias/ID, a timestamp, the week's start date, the item's date, its optional time and text, and its done state. These entries are recorded on a separate "Planner" tab of the same spreadsheet.
Mental Health Corner data is never synced. Mood check-ins and notes are not sent to this endpoint or to any other destination; the Mental Health Corner contains no data-transmission code.
For all three syncing features:
- The endpoint is shown and can be changed in Settings → Google Sheet Web App URL. A default endpoint operated by the publisher is preconfigured so the features work out of the box; if you replace it with your own endpoint, your audit, budget, and planner entries sync to a spreadsheet you control instead.
- Data sent this way is processed by Google Sheets under Google's privacy policy. The publisher does not sell this data, share it for advertising, or use it for any purpose other than maintaining the spreadsheet record.
- No other feature of the app transmits data. The app's interface libraries (styling, charts, icons) are bundled inside the app package, so running the app makes no requests to third-party library servers.
4. What we never collect
No names or government IDs, no email addresses, no location, no contacts, no photos, no device identifiers for tracking, no usage analytics, and no advertising data. The app does not track you across other apps or websites.
5. Children and student use
The app is designed so students can use an alias or advisory ID instead of a real name. Beyond the alias a user types in, the app collects no personal information from any user, including minors. If a school deployment syncs data under Section 3, it does so under that school's own data policies.
6. Changes
If this policy changes, the updated version will be posted at the same URL where this policy is published, with a new effective date.