Privacy Policy
1. Who this policy is for
Bessey · Household is a private, two-person family finance application maintained by a single developer-owner. It is used exclusively by the two members of one household and is not offered to the public, to other households, or to any third party. The users of the application and the operator of the application are the same household.
This policy describes how the application handles personal and financial data that flows through it. It exists for transparency between the operator and the household members, and to satisfy disclosure requirements imposed by the third-party services the application depends on (notably Plaid).
2. Information the application processes
2.1 Identity data (collected at sign-up)
- Email address — used as the account identifier and for password reset.
- Password — stored as a bcrypt hash, never in plaintext.
- Display name — chosen by the user at sign-up.
2.2 Bank-account data (received from Plaid)
- A long-lived Plaid
access_tokenper linked bank login, used to fetch transactions and balances on the household’s behalf. - Account names, last-four masks, current and available balances, and account types.
- Transaction details — merchant name, raw description, amount, date, pending status, and Plaid’s suggested category.
The application does not request, receive, or store account numbers, routing numbers, card numbers, or any bank-login credentials. The user authenticates to their bank directly through Plaid Link; the application never sees the bank password.
2.3 Household data (created by the user)
- The monthly budget plan — category names and planned amounts.
- Merchant rules — learned mappings of merchants to categories, generated when the user files an uncategorized transaction.
- Manual category re-files of individual transactions.
2.4 Automatically logged data
- Application server logs (request method, path, response status, timing) generated by Vercel.
- Database query and authentication logs generated by Supabase.
- Plaid API call logs surfaced in the Plaid dashboard.
The application does not embed third-party analytics, advertising, or behavioral tracking. No data is sent to Google Analytics, Meta, or any equivalent service.
3. How information is used
The application uses the information described above only to provide the household finance features: showing balances, categorizing transactions against the monthly plan, and computing the over-budget and under-budget figures the household members see. The data is not used to build a profile, train a model, advertise, or make decisions about the household members.
4. Third parties that process this data
The application depends on a small number of third-party platforms to operate. Personal and financial data is processed by each of them as described below. Each party is bound by its own privacy policy.
- Plaid Inc. — connects the household’s bank accounts and returns transaction and balance data. Plaid sees the bank credentials at link time (the application never does) and the ongoing data stream the application reads. Plaid’s end-user privacy policy is at plaid.com/legal.
- Supabase, Inc. — hosts the Postgres database, the authentication service, and the Edge Function runtime. All application data (excluding Plaid credentials in the Edge Function environment) lives in Supabase’s managed infrastructure. See supabase.com/privacy.
- Vercel Inc. — hosts and serves the Next.js application and terminates TLS for the public domain. See vercel.com/legal/privacy-policy.
- GitHub, Inc. — hosts the private source code repository. It does not receive household data or production secrets. See GitHub Privacy Statement.
The application does not sell, rent, or otherwise transfer household data to anyone outside this short list.
5. Storage and security
All data is transmitted over TLS (HTTPS) and is encrypted at rest by Supabase’s underlying storage (AES-256). The Plaid access_token is stored in a database column whose Row Level Security policy denies all access to the authenticated role — only server-side Edge Functions can read it, so the token never reaches a browser. The Plaid API client_id and client_secret live in Supabase Edge Function environment secrets and are never present in client code or in any NEXT_PUBLIC_* variable.
The complete set of security controls is documented in SECURITY.md and ACCESS_CONTROLS_POLICY.md in the source repository.
6. Retention and deletion
The application retains data on the following basis:
- Identity data — retained for as long as the user maintains an account. Deleted within 30 days of the user requesting account deletion.
- Plaid
access_token— retained for as long as the user maintains the corresponding bank connection. Deleted (set to empty string and marked revoked) within 7 days of the user disconnecting the bank or deleting their account, whichever comes first. The corresponding Item is also revoked in Plaid. - Transaction history, plan lines, and merchant rules — retained indefinitely as the household’s financial record, unless the household collectively requests deletion. These are data of the household, not of an individual member, so an individual departing the household does not automatically trigger their deletion.
- Server logs — retained on a rolling basis by Vercel and Supabase per their own retention policies (Vercel: 30 days at the time of writing; Supabase: 7 days for Postgres logs, 30 days for Auth logs on the current plan). Not under direct application control.
Deletion on request. A household member who wants their personal data removed can request it from the operator at any time. The operator will, within 30 days: (a) provide a JSON export of all application-controlled data associated with the requestor, and (b) delete the requestor’s identity row, revoke any Plaid Items they connected, and clear the corresponding access_tokens from the database.
The operator enforces this policy directly by running the relevant SQL deletion statements and revoking the Plaid Items via the Plaid dashboard. There is no automated cron-based deletion at this scale.
7. Your rights
Because the user of the application and the operator are the same household, all of the rights commonly enumerated in a privacy policy are available on request and fulfilled directly:
- Right to access — request a copy of all data the application holds about you.
- Right to rectify — correct your display name from the Settings page; correct other data on request.
- Right to delete — delete your account from Settings, or request a complete deletion.
- Right to portability — request a JSON export of all your data.
- Right to disconnect — disconnect a linked bank in Plaid’s portal or via the operator.
8. Cookies and tracking
The application uses cookies set by @supabase/ssr exclusively to maintain the user’s authenticated session. These cookies are HTTP-only, secure, and same-site. The application sets no analytics cookies, no advertising cookies, and no third-party trackers.
9. Children
The application is intended for adult household members. It is not directed at children under 13 and does not knowingly collect data from children.
10. International users
The application operates from the United States. The Supabase project is located in the AWS us-west-1 region. Vercel serves the application from a global edge network with TLS termination. If a household member accesses the application from outside the United States, their data will be transferred to and processed in the United States.
11. Changes to this policy and periodic review
Material changes to this policy will be communicated by updating the “Last Updated” date at the top of this page. Because the operator and the user are the same household, ongoing notice is direct.
The operator reviews this policy at least once per calendar year, and additionally whenever a material change occurs (a new external integration is added, a change in how data flows through the application is made, or a new applicable legal requirement is identified). The most recent review date is recorded in the “Last Updated” field above.
12. Contact
For any question about this policy, the data the application holds, or any of the rights described in Section 7, contact the operator directly. The operator is the household member who maintains this application; the household members already have this contact information through their household relationship.
For Plaid-initiated communications regarding this application, use the email registered on the Plaid dashboard.