Privacy

Identity. Sign-in is handled by Clerk — your email address and a Clerk-issued user ID. This app never sees or stores your password.

Access. FlowMo is invite-only while it's still small — signing up needs an access code or a shared list's invite link. This app stores which access code you used (if any), or that you got in via an invite link, or that your account existed before this started and was let in automatically. It doesn't affect anything covered elsewhere on this page.

What you create. Flows (names, blocks, swappable options, reminder times), to-dos (title, due date, category, notes, recurrence), grocery items, and which blocks you've completed each day — used to show momentum, never a missed-day count or streak.

Push notifications. If you enable them, this app stores your device's push subscription endpoint so it can send reminders, and — for a shared list — notifications like a join request or a shared task being finished. Some of these depend on a grant you or the other person control in Your People; see below.

Feedback. If you use the in-app Feedback button, the text you write, the page/element you were looking at, and which build of the app you were on get saved, tied to your account if you're signed in. If the app crashes, the crash screen has a Report this button; tapping it sends the same kind of record plus the error message and technical details of that crash. Nothing is sent unless you tap it — the app never reports errors on its own. If someone writes back, that reply is saved on the same record and shown to you under Your feedback in Settings — only you can see it, and deleting your account deletes it with everything else.

Waitlist. If you don't have an access code or invite link yet, the landing page has a waitlist that stores just the email address you give it — nothing else about you, and not tied to any account (you might not even have one). It's used only so this app's builder can reach out by hand with an access code later; nothing here sends automated email today, and this address isn't used for anything else.

Analytics, access, and presence. FlowMo collects no analytics or tracking data about you. To answer ten aggregate product questions, the operator may run aggregate-only database queries against the data the app already needs to work; days since last active are grouped into coarse bands, never returned as exact timestamps, and no analytics event store or new tracking columns are used. The operator has database access to the data the app needs to work, including shared lists. Membership in a shared flow, to-do list, or grocery list also means other members can see when you are present in that shared space; this basic presence visibility cannot be turned off while you remain a member, though the Presence detail setting controls whether eligible members can see item or block detail.

Sharing only happens when you invite someone yourself, through one of two doors — this app never shares your lists or flows with anyone you haven't invited. A 6-character code you generate and hand to someone doesn't grant access by itself: entering it sends a join request, visible only to the owner, who approves or denies it before that person gets in. An invite link works differently — anyone who opens it gets access immediately, with no approval step, so only send a link to someone you already want in. Once someone has access, other members can see their display name and permission level (read-only or read-write). Daily completion history stays private to each person even on a shared flow.

Live presence on a shared flow, to-do list, or grocery list. While you both have the same shared flow, to-do list, or grocery list open and on screen at the same time, each of you can see that the other is there right now. On a flow or to-do list, whether you also see what they're currently on — the flow's current block, or the to-do item they have open — depends on a setting each person controls separately in Settings → Presence detail (Detail or Light) — each person's choice controls only what they themselves share, not what they can see of a partner: choosing Detail shows your current block or to-do to anyone in that shared space, choosing Light keeps it hidden, and either way you still see whatever a partner has chosen to disclose about themselves. Grocery-list presence is always just the ambient "they're here too" signal — there's no item-level detail there yet. That preference itself is stored against your account so it's remembered between sessions; the live presence data itself is not saved anywhere, and disappears when either of you closes the page or switches away from it for more than about a minute.

What helps you. Settings has a free-text box where you can write, in your own words, what helps when things are hard. It's stored against your account and nobody else can read it until you explicitly share it — one person at a time, from Settings → Your people, and only with someone you're already in a shared list with. Sharing it doesn't notify them; they see it on their own Your people screen, and they always see the current version, so an edit you make later is what they read next. Either of you can end that sharing at any time, and the moment either does, they can no longer read it at all — but nothing can un-read what they've already seen. Nobody, including the person you shared it with, can see when you wrote or last changed it. Deleting your account deletes the text along with the rest of your data, and removes every sharing arrangement you were on either side of.

Being told a shared task is done. From Settings → Your people, you can allow a specific person to notify you when they finish a shared to-do you asked them to take or that you created. That permission runs one way and lapses automatically after 12 months unless renewed; either of you can end it at any time from Your people. When they finish that task, they can send you one push notification saying it's done — it names the task, nothing more, and there's nothing to reply to or act on. Finishing your own tasks, or a recurring task cycling to its next occurrence, never notifies anyone.

Your personal calendar link, if you create one. Settings has an optional link that turns your FlowMo calendar into a feed a calendar app (Google, Apple, Samsung) can subscribe to. Unlike everything else on this page, whoever holds that link can see those events without a FlowMo account and without being invited to anything — the link itself is the only check, so treat it like a password. Nothing is created until you visit Settings and generate it, and you can replace it at any time from there, which immediately stops the old link from working. FlowMo has no way of knowing who else you gave it to or who's actually fetching it.

Expenses and balances. If a circle has the Expenses tab switched on, everyone in that circle can see every expense in it — what it was, the amount, who paid, who it was split between, and the running balance of who owes whom. There is no way to add an expense that only some members of the circle can see. Anyone in the circle who is named in a split can also delete that expense. Expenses never cross between circles, and your personal (Me) expenses are visible only to you. FlowMo does not move money, connect to any bank or card, and holds no payment details — settling up records that you paid each other somewhere else.

App data (flows, to-dos, groceries, sharing) is stored in a Supabase-hosted Postgres database. Sign-in is handled by Clerk. The app itself is hosted on Vercel. No other third party receives your data — there's no ad network, no third-party analytics service, and nothing is sold.

Export. Settings has a JSON export (flows, to-dos, groceries, your support text, and the sharing arrangements you've granted to others, including ones that have since ended) and a CSV export of your to-dos — generated on your device, no request needed. The JSON export doesn't include arrangements others have granted to you. Anything you add to a shared list without hiding it can be exported by every other member of that list, the same way it's already visible to them in the app — hidden grocery items are the exception, filtered out of everyone's export but your own.

Leave or delete. You can leave any shared list or flow, delete individual flows/to-dos/grocery items, and stop sharing a list you own at any time.

Delete your account. Settings has a "Delete account" section that permanently removes your account and everything tied to it — flows, to-dos, groceries, any list or flow you own, push subscriptions, feedback. Tasks and grocery items you added to a list you share with others stay on that list — they don't disappear, and any ask or assignment naming you is cleared instead of pointing at an account that no longer exists, moving to an Unclaimed group instead. Remaining members see a one-time notice that a member left the list — never who, never why. This can't be undone, and there's no way to recover it after — export your data first if you want a copy.

Deleting your account also deletes shared expenses that name you. This one goes further than the rest, so it is worth knowing in advance: any expense you created, paid for, or were included in the split of is deleted along with your account — even if someone else created it, and even if other people are still in that circle. That means the people you shared with lose that part of their expense history too. The alternative would leave them with a balance owed to an account that no longer exists and can never be settled.

Questions about this policy or your data? Email support@adhdflowmo.com.

If what's collected or how it's used changes in a way that matters, this page gets updated to reflect it — this describes what the app actually does today, not a fixed promise about forever.