SubOrganizer Security & Privacy

Your privacy is not for sale

SubOrganizer is built so that we can honestly tell you: we have no access to your bank, we can't see your card numbers, and every piece of data we do hold is isolated to your account alone. Here's exactly how.

Row-level security on every table

Every subscription, profile, and setting is scoped to your account at the database layer via Postgres Row-Level Security (RLS) — not just application code. Even a bug in our UI can't leak another user's data.

No bank or card connections, ever

SubOrganizer never asks for bank credentials, card numbers, or connects to services like Plaid. Subscriptions are added manually, via the browser extension reading page content locally, or from data you explicitly import.

The browser extension never sends raw page data anywhere

Detection runs entirely in your browser. Only a small structured draft (merchant name, price, renewal date) is sent to your account after you approve it — never full page content, emails, or browsing history.

Your calendar link is a private, revocable token

The .ics calendar feed uses a random, unguessable token stored only in your account. You can regenerate it at any time from Settings to instantly invalidate the old link.

Permanent, self-serve deletion

Export or delete your subscriptions and account at any time from Settings. Deletion is immediate and permanent — we don't retain shadow copies.

Built on Supabase (Postgres + Auth)

Authentication, session tokens, and data storage run on Supabase's managed Postgres infrastructure with encrypted connections in transit and at rest.

Questions or found something concerning?

Reach out any time — we take security reports seriously and respond directly, not through a support queue.