Your data. Plain language. No fine print.

What we do not do

We do not connect to your bank. Ever.

No bank linking, no read access to your accounts, no imported transaction feeds. You enter your numbers manually. That is the whole point.

We do not sell your data.

Your budget information is not a product. We are funded by your subscription, which means we have no incentive to monetize your data in any other way.

We do not use advertising cookies.

The only cookies on Ritual Runway are the ones required to keep you logged in.

Our infrastructure, disclosed

Supabase

Stores your budget data with standard disk-level encryption at the Postgres layer. Supabase can access server infrastructure but we do not expose raw transaction data beyond what is required to operate the database. No data is sold or shared with third parties under our agreement.

Resend

Handles transactional email such as your welcome message and password reset. Resend has access to your email address and the content of emails we send you. It does not have access to your budget data.

Stripe

Processes your subscription payment. Stripe handles all payment information. Ritual Runway does not store your card details. Stripe does not have access to your budget data.

Vercel Web Analytics

Counts page views and measures page speed so we can keep the site fast. Vercel Web Analytics is cookie-free, does not track you across sites, and does not collect personal information. It does not have access to your budget data.

Sentry

Monitors application errors so we can fix bugs quickly. Sentry receives crash reports, stack traces, the URL path where an error occurred, and your user ID so we can correlate a report to your account if you contact us. Sentry does not receive the contents of your budget, bills, income, or any other financial data. We sample 10% of performance traces in production to limit data collection.

What no bank connection actually means

Not connecting your bank means Ritual Runway never receives a feed of your transactions. No third-party aggregator sees your account credentials or your transaction history on our behalf.

What it does not mean: your budget data is still stored in a cloud database. If you enter a number into Ritual Runway, that number lives on our servers. We protect it with encryption at rest and in transit, and we do not share it. But this is not a local-first or zero-knowledge architecture. If your threat model requires that no server ever sees your data, Ritual Runway is not the right tool for that use case. We would rather tell you that directly.

What you can do with your data

Export:

You can download a full export of your budget data at any time from your account settings.

Delete:

You can delete your account and your budget data from your account settings. Your account and budget rows are removed immediately. Some downstream copies persist temporarily: backups (rolling window), Stripe customer records (retained for tax and chargeback regulations), Resend email send logs (about 30 days), and Sentry error reports (30 to 90 days). None of those downstream copies contain your bills, income, or budget data.

How we protect your data

  • •All data is encrypted in transit using TLS.
  • •Data at rest uses standard disk-level encryption from our cloud provider. We do not encrypt fields client-side; if your threat model requires that, this is not the right tool. The trust page explains the architecture below.
  • •Authentication is handled via secure session tokens.
  • •We do not currently hold a SOC 2 certification. We plan to pursue an independent security review as the product scales. We will update this page when that changes.

Questions about your data? Email us at heydarlin@ritualrunway.com. We respond to every message.