Security & data
Recurna is built on a simple principle: collect less, not more. Here's what we store, where it lives, and what we never touch.
What we store
No bank connection
Recurna never connects to your bank account. No OAuth handshake, no read access, no Plaid. You enter your transactions manually. That's the whole model.
No PII in our database
Your name and email address never reach our database. Authentication is handled by Clerk — your identity stays with them. What we store: transaction amounts, dates, and labels you write yourself.
You control what we see
Every transaction in Recurna is one you chose to add. We have no background access, no inferred data, no behavioral profile. You decide what the forecast knows.
Where your data lives
Recurna Flow is operated by a Canadian company. Your financial data is stored in a PostgreSQL database hosted on Neon (serverless PostgreSQL). The application backend runs on Cloudflare Workers and the frontend is served from Cloudflare Pages.
Authentication is handled by Clerk. Your identity — name, email, profile picture — stays with Clerk and never reaches our database. We keep a single internal account identifier mapped to your Clerk account so we can associate your financial data with you.
Portability
Recurna is manual-first by design. Because you enter your own transactions, your data is always yours to take with you — export a full CSV from the account page at any time.
Full details in our Privacy Policy.