Privacy and security
Your matter is not a product.
What we hold, what we never do with it, and what the other person can and cannot see. Written to be checked, including by your professional's IT reviewer.
What we hold and why
A plain inventory.
Account
Your email and device, to let you sign in and to send the weekly digest.
Decisions
Your answers, notes, and the record of who proposed and confirmed what, so both of you can rely on the same history.
Financial
Figures you enter and balances from accounts you link, to compute the worksheets and fill the disclosure.
Documents
Files you upload, to organize disclosure and to print the packet.
Commitments
Encrypted in transit and at rest.
No advertising, no data sale, no third-party trackers.
Export everything at any time.
Both parties' consent is required to share the matter with anyone, including professionals.
The other person cannot see everything
Private surfaces, enumerated.
Your budget.
Your unexchanged disclosure.
Your unshared linked accounts, including that they exist.
Privacy between the two of you is enforced in the database, not the interface.
Meridian savings
Off means invisible, including the fact that this account exists.
No AI is deciding anything
Every word in your matter was typed by one of you.
The app does not use AI to decide, suggest, judge, or write anything.
No suggested compromises.
Nothing summarizes or rephrases what the other person wrote.
No tone or sentiment analysis.
No scoring or profiling of either of you.
Nothing in your matter is used to train anything.
What computes the numbers is ordinary statutory arithmetic. It shows every step with its citation, and the same figures are checked against a hand-worked set of test vectors in the code's own test suite. Publishing that set for you or a professional to run independently is not built yet.
Subpoenas
Where we stand on legal demands: we require valid legal process, we narrow overbroad requests, and we notify both people unless a court forbids it. That is a position, not a published policy. Nothing is drafted yet, and this page is the whole of what is written down.
Security practices
Every table enforces row-level access, so one person's private data is unreachable by the other at the data layer rather than hidden by the screen. Bank tokens are sealed server-side and never reach either person's device. There are no third-party analytics in the app or on this site.
Technical appendix
Row-level security policies on every table · per-person policies wherever the data is private · sealed Plaid tokens with server-side exchange · no third-party analytics or tag managers · encryption in transit and at rest.
For your professional's reviewer
What a vendor review asks for.
Lawyers have their own duty to vet the software their clients' information goes into. Rather than answer that one firm at a time, the answers live here, and they are the same answers for everybody.
Subprocessors
The vendors that touch matter data today: Supabase for the database and auth, Vercel for hosting, Resend for email, and Plaid for linked accounts. A published, versioned list with notice before it changes is not built yet; this line is that list until it is.
Legal process
Where we stand on subpoenas, preservation demands, and legal holds: valid process required, overbroad requests narrowed, both people notified unless a court forbids it. The written policy is not published yet.
Data processing
A data processing agreement for practices, and security-questionnaire answers assembled in advance, are both planned and not yet written.
Independent audit
A SOC 2 Type II engagement is planned and not yet complete. We would rather write that sentence than imply a report exists.
The math itself
The statutory arithmetic runs against a hand-worked set of test vectors in the code's own test suite, so a build that drifts from the math fails loudly. Publishing that set for an outside reviewer to run independently is not built yet.
Anything here that you need on paper, ask and we will send it. Request the vendor pack.