We never have custody of your funds, and we only ever read.
We never take custody and never have withdrawal rights, and RatioNexFlow only ever reads with an exchange key. Binance, Bybit and Coinbase keys are checked read-only with the exchange; for the other exchanges you confirm it when you connect, so create the key without trading or withdrawal rights. With a read-only key, a breach of RatioNexFlow cannot move your funds – the worst case is information disclosure.
No custody, ever
RatioNexFlow does not custody crypto. Your assets stay where they are – on the exchange or in your wallet. RatioNexFlow never moves or trades them; it only reads balances and history.
Read-only exchange keys
Connecting an exchange is optional. If you do, create the key without trading or withdrawal rights. Binance, Bybit and Coinbase keys are checked read-only with the exchange; for the other exchanges you confirm it when you connect, and a key you do not confirm is refused. Keys are encrypted with AES-256-GCM on our server and never returned to your browser. Prefer to stay keyless? Upload a read-only transaction-history file instead; it is parsed in your browser before being saved to your account.
Encryption in transit and at rest
All traffic to and from RatioNexFlow uses TLS 1.2 or newer. Data at rest is encrypted by our managed database provider (Supabase).
Row-level user isolation
Every table that holds account data ties each row to its owner, and Postgres row-level security (RLS) is on for every table we create in our database. A database query made with your sign-in reaches only your own data, the portfolios others have shared with you, the invitations sent to your e-mail address, and the whole profile of anyone you share a portfolio with or who shares one with you (name, e-mail address, picture, headline, bio, country, and when the account was made and last updated), even if there's a bug in the application layer. Profile pictures sit at public links: anyone who has a picture's link can open it, but nobody can list them. Our own admin accounts can also read what support, account administration and our visit statistics need, such as support chats, error reports and the pages a signed-in account opens.
Where your data is stored and processed
Your portfolio data lives in AWS eu-west-2 (London, United Kingdom); our Vercel API functions run in Frankfurt, Germany, and the Supabase edge functions your browser calls run in the region closest to you. US providers (Supabase, Vercel, Resend, Google, Stripe) are covered by the EU Standard Contractual Clauses. If you turn on Ask your portfolio, your question and a redacted summary go to Anthropic, which stores them in the United States and may process them in other countries; for customers in the EEA its contracting company is Anthropic Ireland, Limited, and its data processing addendum incorporates the EU Standard Contractual Clauses. The Privacy policy lists every one.
Least-privilege access
Engineers do not access user data routinely. Production database access is logged, scoped to specific incident-response needs, and reviewed.
Security scorecard
TLS 1.2 or newer in transit
HTTPS only: plain HTTP is redirected, and TLS 1.0 and 1.1 are refused
AES-256 at rest
Supabase managed database encryption
Postgres row-level security (RLS)
On for every table we create; outside our admin accounts, a user's database queries reach only their own data, invitations sent to them, the portfolio shares they are part of and the profiles of the people in those shares; profile pictures sit at public links
Data stored in London, Vercel functions in Frankfurt
Supabase database, auth and storage in AWS eu-west-2 (London, UK); the Supabase edge functions your browser calls in the region closest to you; Vercel functions in fra1 (Frankfurt). US providers – Supabase, Vercel, Resend, Google, Stripe – under EU Standard Contractual Clauses; Anthropic (Ask your portfolio, opt-in) through Anthropic Ireland, Limited for EEA customers, with the Standard Contractual Clauses in its data processing addendum; see the Privacy policy
Exchange keys query-only + encrypted
Optional read-only connections; keys stored as AES-256-GCM ciphertext, never returned to the browser
Checks before and after each merge
Before each merge, lint, the test suite, a production build and a Playwright smoke test run locally; after each merge, the live site is checked
Dependency audit (npm audit) on every push
Not automated: npm audit is not part of the checks before each merge
Independent penetration test
Not yet conducted
SOC 2 / ISO 27001 certification
Supabase infrastructure is SOC 2 Type II certified; RatioNexFlow itself has not been audited at this scale
Sub-processors
We share data only with the minimum set of third parties required to run the service. Any change is reflected here.
Supabase
Managed Postgres, auth, storage, edge functions
eu-west-2 (London, UK); edge functions your browser calls in the region closest to the visitor
Vercel
Frontend hosting, edge network, API functions (exchange sync; our own cookieless visit statistics, with the approximate location of each request)
fra1 (Frankfurt) + global edge
Vercel Analytics
Aggregate usage analytics, if you accept analytics
United States
Google
Sign in with Google, only if you use it
United States
Resend
Account emails (sign-up confirmation, password reset, invitations) and share invitations
United States
Anthropic
Ask your portfolio (opt-in, Claude models): your question and a redacted portfolio summary
Stored in the United States; may be processed in other countries
Stripe
Payment for RatioNexFlow Pro, only if you subscribe: the merchant of record (through its Link service), which takes your payment details on its own pages as a separate controller under its own privacy policy; we send it your email and account ID and never see your card
United States
These are the sub-processors that handle personal data on our behalf, and Stripe, which handles payment as a separate controller if you subscribe; section 5 of the Privacy policy is the full list, including your exchange and the public blockchain nodes a feature you use may contact, and it says which market-data providers your browser fetches directly (so they see your IP address like any site you visit) and which only our servers read.
Reporting a vulnerability
Found something? Email security@rationexflow.com. Please give us a reasonable window to fix the issue before public disclosure. I read every report and respond as soon as I can, and will work with you on resolution.