Privacy Policy

Overview

Finance OS is a private financial operating system built and operated by Ryan DeCook. This policy describes how data is collected, stored, and used within the platform. Finance OS is not a public SaaS product and does not sell, share, or monetize any user data.

What data is collected

Finance OS processes and stores the following types of data:

• Entity and account registry information (names, types, institution details)
• Financial transactions imported via CSV or connected bank feeds
• Documents uploaded to the vault (statements, receipts, tax forms, formation docs)
• Review actions, reporting period status, and claim review decisions
• Authentication session information
• Security audit records — for sign-in, failed sign-in, sign-out, password reset, document upload, claim review, and connecting or disconnecting an AI provider. Each record holds the actor, action, resource identifier, outcome, timestamp, client IP address, and browser user agent.

Bank and card account numbers are stored as the last four digits only. The security audit trail never records passwords, session tokens, API keys, taxpayer identification numbers, full account numbers, document contents, or financial values.

How data is stored and protected

All operational data is stored in a Supabase-hosted PostgreSQL database. Uploaded documents are stored in a private Supabase Storage bucket. Both are encrypted at rest with AES-256, and all traffic to and from the application is encrypted in transit with TLS.

Access is restricted by PostgreSQL row-level security and by owner-only storage policies, so a signed-in session can only reach its own records and its own documents. The owner may also issue a revocable, expiring, scoped Finance OS token to an authorized headless agent. A complete-context authorization exposes the owner's financial, bookkeeping, evidence, and tax records because that context is required for bookkeeping and return preparation; it does not expose credential stores, deployment secrets, raw access tokens, or another owner's rows. Some server-side processing — document extraction, accounting seeds, tax calculation, and reporting — still runs with service-role credentials that bypass row-level security. The security page describes this and the other current limitations in detail.

Third-party services

Finance OS integrates with the following third-party services:

• Supabase — database hosting, file storage, and authentication infrastructure
• Vercel — application hosting and deployment
• Plaid — consumer-authorized bank account connectivity and transaction sync. Production access is pending; no production bank data has flowed through Plaid
• GitHub — private source code repository and build checks. No financial data
• OpenAI / Anthropic — optional document extraction, using credentials the operator supplies. Document text is sent for extraction only while a provider is connected, and the connection can be removed at any time

No data is shared with advertising networks, analytics platforms, or data brokers, and no data is sold.

Plaid consent and control

Finance OS does not launch Plaid Link until the signed-in owner explicitly authorizes collection and storage of account metadata and up to 24 months of transaction history for bookkeeping. The consent receipt records the policy version, selected Finance OS account, timestamp, and resulting Plaid Item; it never contains bank credentials or financial values.

The owner can disconnect an institution from the Plaid settings page. That action asks Plaid to revoke the Item, deletes the encrypted access token, webhook payloads, raw provider staging, account mappings, and unreviewed staged transactions, and revokes the consent receipt. Bookkeeping records already reviewed by the owner and audit-locked statement evidence remain subject to the retention policy below, with Plaid-specific raw payloads and identifiers removed from retained ledger rows.

Data retention

Reviewed financial records, documents, claims, and audit records are retained indefinitely to support tax filing, amended returns, basis tracking, and audit defence. Because IRS assessment periods can reach back many years, short retention would be actively harmful here.

Authentication sessions expire according to the Supabase Auth configuration, with refresh tokens rotated by Supabase. Signing out ends the session immediately.

Your rights

Finance OS is a private, single-operator system. It has no customers and processes no third party's financial data. As the sole operator and data owner, Ryan DeCook retains full control over all data in the system, which can be exported or corrected at any time. Plaid consent can be withdrawn and provider data deleted from the Plaid settings page. Reviewed bookkeeping and audit evidence may be retained where needed for tax, accounting, fraud-prevention, and legal obligations.

If Finance OS ever processes another person's financial data — including through a production bank connection — this policy will be updated first to describe how that person may access, correct, export, or delete their data, and how to withdraw consent for a connected account.

Security

Finance OS maintains a written information security policy covering access control, encryption, secrets handling, logging, retention, and incident response. The security page sets out both the controls that are implemented and the gaps that remain.

Contact

For questions about this privacy policy, data handling practices, or to report a security concern, contact the system operator directly.