Skip to main content
Legal

Privacy Policy

What we collect, why we collect it, and the rights you have over your data.

Last updated · 13 November 2026

1. Who controls your data

RatioNexF OÜ (registry code 17605569, Estonia), operating the service as RatioNexFlow, is the data controller for the personal data we process about you. You can reach us at privacy@rationexflow.com.

2. What we collect

You give us

  • Waitlist (closed on 20 October 2026): if you joined the waitlist before then, we keep the e-mail address, the sign-up source (the utm_source, ref or source value in the link you used; otherwise the host name of the site that referred you; otherwise "direct"), the referral code when one was used, your browser's user-agent string and the date, as described under Retention (section 7).
  • Account data: email address, password (hashed), authentication identifiers (e.g. Google account ID if you sign in with Google).
  • Profile: every account has a display name, which starts as the part of your e-mail address before the @. In the new look, Settings → Profile lets you change it and add, if you want, a picture, a headline (for example your job title and company), a short bio and your country. If your account is linked to a Google or Facebook sign-in and you use the new look, the app copies that sign-in's profile picture into your profile once, while your profile has no picture and you have never removed one. The picture is stored as a file in our file storage at a public address that contains your account ID: anyone who has that address can open the picture, but nobody else can list the pictures. Anyone you share a portfolio with, or who shares one with you, can read your whole profile (name, e-mail address, picture, headline, bio, country, and when the account was made and last updated), together with your account ID and whether your picture is your own or was copied from your sign-in. "Download my data" in Settings includes your profile and the picture file, and deleting your account deletes both.
  • Portfolio data: the contents of the transaction-history files you import, or the balances and history read through an exchange connection you add – trades, fees, transfers, balances – and any public wallet address you choose to track. If you connect an exchange, its query-only API key passes once, over TLS, through our API function in Frankfurt, Germany, where it is encrypted (AES-256-GCM) before being stored; it is used solely to read that data and is never sent back to your browser.
  • Communications: messages you send to support.
  • Withdrawal from Pro: when you withdraw from Pro, we keep a record of your withdrawal (your name, e-mail, the contract, your statement, the time you sent it and the time we received it) as evidence for as long as claims about the contract can be made. The record also holds when we sent you the confirmation, Stripe's reference for any refund and, when you use the "Withdraw from contract here" button, your account ID until you delete the account.

We collect automatically

  • Technical data: IP address, browser/device type, language, time-zone, and interactions with the service, used for security and reliability. Our hosting provider sees this for every request (see section 5).
  • Visit statistics (without cookies): our own statistics record how the site is used, for every visitor, without setting a cookie or storing anything on your device. For each page you open we record the page path; the referring site (host name only); the campaign tags (utm_*) and affiliate code (ref) in the link you arrived by; your browser's user-agent string and, from it, the type of device, browser and operating system; your browser's language and window size; the approximate location of the request (country, region, city and that place's coordinates rounded to about 1 km), which our hosting provider Vercel derives from your IP address; how long the page was visible and how far you scrolled; and a few actions (clicking the landing page's main button or a plan's button on the pricing page, starting a sign-up, opening the demo). To group your page views into one visit, our database computes a key from your IP address, your user-agent string and a random value that changes every day. The IP address is used only for that and is not stored, and each day's random value is deleted after two days, after which nobody, including us, can recompute the key from an IP address. Because the key changes every day, it cannot link your visits on different days. We do not record the rest of the web address (other query parameters, or fragments such as sign-in tokens), full referring URLs or anything you type into forms. How long we keep these records is in section 7.
  • If you accept analytics: if you choose Accept in the cookie notice, we also store a random visitor identifier in your browser's local storage (rnf_vid) and send it with the visit statistics, so that your visits on different days can be counted as one returning visitor, and Vercel Analytics runs (section 5). If you decline, or your browser sends Global Privacy Control, no visitor identifier is created and Vercel Analytics sends nothing; the visit statistics above are still recorded, without cookies.
  • While you are signed in: the visit statistics are linked to your account, whether or not you accepted analytics. Our server checks your sign-in with our authentication service and stores your account ID with each record; the visit in which you sign up or sign in is linked to your account, including the pages you viewed before signing in; and that day's key (and your visitor identifier, if you accepted analytics) is linked to your account, so your other visits that day from the same browser and network can be linked to it too. We use this to support you and to see how the product is used, for example how many new accounts go on to add a tracker, connect an exchange or ask a question. We do not store your email address in these records.
  • Old page-view log: until 12 October 2026 a separate page-view log recorded, for each page opened, the time, the page path, the referring site (host name only), your browser's user-agent string and the visitor identifier above (rnf_vid). From 24 May to 9 October 2026 the site created that identifier in your browser's local storage and recorded it without asking for your consent; from 9 October 2026 it did so only if you had accepted analytics, and otherwise recorded the page view without an identifier. The visit statistics replaced the log on 12 October 2026, and the site no longer writes to it. Its rows are deleted 13 months after they were written. Daily page-view totals per page taken from it are kept; they contain no visitor identifier.
  • Browser error log: if something breaks in your browser while you use the site, the app records the error text and stack trace, the page path, your browser's user-agent string, the build it came from and, when you are signed in, your account ID, so that we can find and fix the fault. If you accepted analytics, the visitor identifier above is recorded with it, so an error can be matched to that visitor's page views; otherwise it is not. No third-party error-tracking service is involved. We keep these records for 30 days; a weekly purge removes them, so a record can remain for up to 37 days.
  • Affiliate code: if you arrive through a link that carries a ?ref code, the code is recorded with the visit statistics above. It identifies the link you clicked, not you.
  • Cookies: as described in our Cookies policy.

Information about other people in risk flags

Threat Protection shows up to ten of the largest holder addresses of a token, as reported by GoPlus, with links to a public block explorer. An address can belong to a person. We show addresses so that you can see what the rules counted (legitimate interests, GDPR art 6(1)(f)). We do not try to find out who is behind an address and we do not label addresses as people. If you believe an address shown belongs to you, you can object or ask for a correction at privacy@rationexflow.com.

Public posts by other people

Every 30 minutes our server searches public posts on Bluesky and Hacker News for words about crypto portfolio tracking and the tools for it (for example "crypto portfolio tracker"). The searches send Bluesky and Algolia (which runs the Hacker News search) only the search words and a time window, nothing about any person. For each post that contains one of the words, we store the author's name on that site (their handle or user name; on Bluesky also their permanent account ID), the post's text and title (for a Hacker News comment, the title of the story it was posted under), its link, its first hashtag, when it was posted and which words it matched, and later the model's rating, a label for what the post is about and any draft reply. We use these posts to see where people talk in public about what RatioNexFlow does, and to draft replies that a person reads; nothing is posted automatically. We send a new post's title and text, with the site, its first hashtag and the words it matched, but not its author or link, to Anthropic, whose Claude model rates how close the post is to what RatioNexFlow does, labels what it is about and can draft a reply (section 5). When it has drafted replies, Resend e-mails the best of those posts (each one's author, title or opening words, link, rating and draft) to our own team's addresses, at most twice a day. Basis: our legitimate interests in finding and answering public conversations about what RatioNexFlow does (GDPR art 6(1)(f)). We delete each stored post, with its rating, label and draft reply, 90 days after we stored it (section 7). If a post stored here is yours, you can object or ask us to delete it sooner at privacy@rationexflow.com.

3. How we use it

  • To provide the service – show your portfolio, run analytics, evaluate alerts, generate risk profiles.
  • To answer your questions in "Ask your portfolio", if you enable it – your question and a redacted summary of your portfolio go to Anthropic (see the Anthropic entry in section 5).
  • To count visits, see which pages, referring sites and campaigns bring people to the site, and see how many visitors go on to create an account and use it (visit statistics, section 2).
  • Feedback. When you send feedback with the Feedback button, we keep your account id, your e-mail address, what you write, the page you were on, the app version and your browser's user agent. We use it to read and answer your report, to fix what you report and, where your feedback earns free Pro, to grant it. Basis: performance of our contract with you (GDPR art 6(1)(b)); for improving RatioNexFlow from reports in general, our legitimate interests (art 6(1)(f)). We keep it for 24 months after we receive it, or until you delete your account, whichever comes first. When you send feedback without an account, with the form on the Help or Pricing page, we keep the e-mail address you type, what you write, the page and your browser's user agent; no IP address is stored with it. We use that e-mail address only to answer you and, where your feedback earns free Pro, to apply a Pro grant to it; the grant switches on when an account with that address is created and confirmed. Basis: our legitimate interests in answering the messages people send us (art 6(1)(f)); for the Pro grant, steps you ask for before a contract (art 6(1)(b)). We keep it for 24 months after we receive it; write to privacy@rationexflow.com to have it deleted sooner. A free Pro grant is a record of its own: it keeps the e-mail address it was made to, that it was for feedback (and any founding slot number), when it was made, when it switched on and when it ends, and the account it switched on for until that account is deleted. We delete the e-mail address from a grant 30 days after the grant switches on, or within a day after the account it switched on for is deleted, whichever comes first. A grant that has not switched on is deleted 24 months after it was made. We keep the rest of a grant that switched on so that an account gets free Pro for feedback only once, also after the feedback that earned it is deleted (section 7).
  • To secure the service – fraud prevention, abuse detection, account recovery.
  • To communicate with you – service emails, support replies, security notifications.
  • To comply with law – e.g. responding to lawful requests.

We do not sell your data, and we do not show you advertising on the service.

4. Lawful basis (EU GDPR)

  • Performance of a contract – to provide the service you signed up for.
  • Legitimate interests – to keep the service secure, fix bugs (including the browser error log in section 2), improve features, and measure how the site is used without cookies (the visit statistics in section 2, including their link to your account while you are signed in). You can object to this at any time (section 8).
  • Consent – for the visitor identifier stored in your browser (rnf_vid) and Vercel Analytics, other non-essential cookies, "Ask your portfolio", and marketing emails, where applicable.
  • Legal obligation – when required to comply with law.

5. Who we share your data with

We do not sell your data and we do not share it with advertisers. The companies below process personal data on our behalf (sub-processors) or receive it because a feature you use needs them. Where a provider is outside the European Economic Area we rely on an EU adequacy decision or the EU Standard Contractual Clauses, as set out in section 6.

Core infrastructure (always on)

  • Supabase – database, authentication, file storage and server functions. Holds your account data, portfolio data, encrypted exchange keys, waitlist sign-ups, our own visit statistics (and the old page-view log until its rows expire), the browser error log and the statement files described below. The database function that groups page views into visits receives your IP address with each batch and uses it only to compute the daily key (section 2). Database, authentication and file storage are in London, United Kingdom (AWS eu-west-2); server functions run in Supabase's global edge network, in the region closest to the visitor, unless pinned to one region; none of ours is pinned.
  • Resend – delivers our emails. Account emails from our authentication service (sign-up confirmation, password reset and invitations) are sent from noreply@rationexflow.com through Resend's mail servers (smtp.resend.com). Resend also sends portfolio-share invitations (the recipient's address and the inviter's name or email), the confirmation of a withdrawal from Pro (your name, e-mail address, the contract, your statement and the time you sent it), and the thank-you e-mail when we grant free Pro for your feedback (your e-mail address, a short topic, which can be the opening words of your feedback, how long the free Pro lasts and when it ends, and any founding slot number). It also delivers to our own team's addresses the e-mails about public posts described in section 2. Resend receives the recipient address and the content of each message. Resend, Inc., United States.
  • Vercel – hosts the website and runs our API functions, including the one that tests, saves and syncs exchange connections. Sees the technical data of every request (IP address, browser, pages requested). If you connect an exchange, your read-only key passes through this function once, over TLS, before it is encrypted and stored; it is never sent back to your browser. It also runs the function that receives our visit statistics, and derives the approximate location of each request (country, region, city and coordinates) from its IP address for them (section 2). Functions run in Frankfurt, Germany; static files are served from Vercel's global network. Vercel, Inc., United States.
  • Vercel Analytics – aggregate usage analytics (page views, referrer, browser type, approximate location from the IP address). We do not use it for advertising or cross-site tracking. It runs only if you accept analytics in the cookie notice.

Features you choose to use

  • Google (Sign in with Google) – if you sign in or link your account with Google, Google sends us your Google account ID, email address, name and profile picture, and Google learns that you use RatioNexFlow. When you use the new look, your profile has no picture and you have never removed one, we copy that picture into your profile once (section 2).
  • Anthropic – powers "Ask your portfolio" with its Claude models. When you ask a question, we send Anthropic a summary of your portfolio: coin symbols, amounts, values and weights; concentration figures; threat-protection rule results and the rules behind them; the cost basis of each holding (average cost, remaining cost basis, unrealised gain or loss) and the total you invested; realised gain or loss for the year to date, the last twelve months and all time, with the number of closed trades; the names of your exchanges or other sources with their values and last sync times; headline titles for coins you hold; and the market-cycle reading – plus your question and up to two earlier questions and answers. Before sending, our server strips anything that looks like an email address, wallet address, transaction hash, IBAN, account identifier or API key. We do not send your name, email, user ID, wallet addresses, exchange keys, transaction IDs or file names. Anthropic stores what we send in the United States and may process it in the United States and other countries where it runs its service. Its commercial terms do not allow it to train models on this data. Its standard policy is to delete it within 30 days, unless the law requires it to keep it longer or its safety systems flag a request as breaking its usage policy, in which case it may keep that request for up to two years. We keep no copy of your question, the summary or the answer: only counters (how many questions you asked or we refused, per day and per minute, the tokens used and their cost), the time of your latest question, a short label saying which of our suggested questions it was, or that you typed your own, and the time you enabled the feature. These are deleted with your account. The feature is off until you enable it. You can withdraw your consent at any time with Turn off Ask on the Ask page or in Settings → Privacy; after that nothing from your portfolio is sent to Anthropic. For customers in the EEA, Anthropic's contracting company is Anthropic Ireland, Limited, Ireland. Anthropic's data processing addendum incorporates the EU Standard Contractual Clauses, and Anthropic is responsible for safeguards on transfers out of the EEA (section 6). Apart from Ask, and not as a feature anyone chooses, Anthropic also receives the title and text of the public posts described in section 2 (not their authors or links), to rate them and draft replies.
  • Stripe – handles payment if you subscribe to RatioNexFlow Pro. Stripe handles payment as the merchant of record, through its Link service and under its own terms. On its own checkout and billing pages it collects your card or other payment details, name, email and billing address, charges you, calculates and collects VAT or sales tax, sends receipts and handles payment questions and disputes, as a separate controller under its own privacy policy. RatioNexFlow never sees your card details. When you open the Pro checkout we create a customer record at Stripe with your email address and your RatioNexFlow account ID, so the subscription can be tied to your account. We keep a copy of the subscription's status, plan, price, currency and period dates, and Stripe's customer and subscription IDs; these are deleted with your account. The customer record at Stripe is not: it stays in our Stripe account, with your email address and your former account ID, also if you never paid, and we have not yet set a period after which it is deleted (section 7). Stripe keeps its own payment records for as long as the law requires it to.
  • Your exchange – if you add a read-only API key, our Frankfurt function uses it to read your balances, trades, ledger, deposits, withdrawals and open positions from that exchange (Kraken, Bybit, OKX, Binance, Coinbase, KuCoin, Bitget, Crypto.com Exchange, Kraken Futures, Bitstamp, Bitvavo, Gemini, Bitfinex, MEXC, Gate or HTX). The exchange sees that request coming from our server, not from your device. The exchange is a separate data controller under its own privacy policy. Your key is stored only as AES-256-GCM ciphertext, is never shown to your browser again, and can be removed at any time from Connect Exchange.
  • Public blockchain nodes – if you look up or save a wallet by address, our server sends that public address to public node providers (PublicNode, dRPC, Merkle, the Arbitrum, Optimism, Base and Solana public endpoints, 1RPC) to read its balances: when you look it up, when you open the wallet page, and every five minutes while that page is open. It prices the tokens it finds with Kraken, dYdX and Hyperliquid, and with CoinGecko for a token none of them lists; those price requests name the tokens, never your address. Your IP address reaches none of these services, and the address you typed reaches the node providers only.
  • "Help us improve imports" submissions – if you submit a cleaned statement on the Help us improve imports page, our submit-fixture function stores the file in a private Supabase bucket (fixture-submissions) that only RatioNexFlow staff can read, together with a record of the file's original name and size, the exchange you picked, the reply-to email if you gave one, a salted hash of your IP address (used only to limit submissions to ten an hour) and your browser's user-agent string. We keep a submission until we have reviewed it and turned it into an anonymised test file, then delete it; email privacy@rationexflow.com to have it deleted sooner.
  • Statement uploads on the training page – raw statements you upload on the /training-uploads page (available when signed in) go to a separate private bucket (training-statements) readable only by RatioNexFlow staff; a daily purge deletes the file 7 days after upload. The record of the upload (file name, size, type and date) stays with your account. Deleting your account deletes the record and any file the purge has not yet taken.

Market data your browser fetches directly

Some price and market data is loaded straight into your browser from the provider, so the provider sees your IP address and browser type in the same way any website you visit does. These providers are: Kraken (prices for the coins in your portfolio, every minute while the app is open, the BTC, ETH and SOL prices in the market bar, and daily price history for your portfolio chart, the market bar and the Bitcoin pages), dYdX and Hyperliquid (prices for coins Kraken does not list), CoinGecko (coin logos, matching a coin's symbol to its CoinGecko entry, and past prices for your imported history when Kraken has none), Alternative.me (Fear & Greed index), Frankfurter (ECB exchange rates) and mempool.space (Bitcoin block height). The Kraken and CoinGecko requests can name the coins being priced or shown, which can include coins you hold; the dYdX and Hyperliquid requests fetch each venue's whole price list and name no coin. None of them receives your name, email or account data.

Market data we fetch from our own servers

The prices our servers store every minute (which price alerts are checked against), the market table and global figures we keep one copy of for everyone, Threat Protection, the intel feed, the Screener and the derivatives pages read public data from Kraken, CoinGecko, DefiLlama, Cointelegraph, the GDELT Project, Hyperliquid, dYdX, the SEC, mempool.space, Alternative.me, GoPlus and DexScreener, and read Ethereum gas fees and stablecoin supply from public blockchain nodes (dRPC, TronGrid and Solana's public endpoint; for stablecoin supply also PublicNode, when dRPC or TronGrid does not answer). These calls come from our servers; no personal data and none of your technical data is sent to them. Wallet tracking is the one exception, described under "Public blockchain nodes" above.

We do not use any third-party error-tracking, session-recording or advertising service; the browser error log in section 2 is our own and stays in our database. We will update this list before adding a provider.

6. Where your data is stored and international transfers

Your account and portfolio data are stored in London, United Kingdom (AWS eu-west-2). The United Kingdom holds an EU adequacy decision, so transfers there are permitted under the EU GDPR. Our API functions run in Frankfurt, Germany. The Supabase server functions that your browser calls (section 5) run in Supabase's region closest to you, which can be outside the United Kingdom and the EEA when you are; what they handle there is your request and what it reads from or writes to our database and file storage in London. Supabase, Vercel, Vercel Analytics, Resend, Google and Stripe are US companies; transfers to them rely on the EU Standard Contractual Clauses (and the EU-US Data Privacy Framework where the provider is certified) with any supplementary measures required. For "Ask your portfolio", Anthropic's contracting company for customers in the EEA is Anthropic Ireland, Limited, in Ireland; Anthropic stores what we send in the United States and may process it in other countries where it runs its service. Anthropic's data processing addendum incorporates the EU Standard Contractual Clauses, and Anthropic is responsible for safeguards on transfers out of the EEA.

7. Retention

We retain account and portfolio data for as long as your account is active. If you delete your account, we delete or anonymize your data within 30 days, except where we are required to retain records to comply with law or to defend legal claims, and except these records, each described below or in the section named: the waitlist and approval records, which follow their own 12-month rule; a portfolio-share invitation another user sent to your address, until that user's account is deleted; the record of a withdrawal from Pro, for as long as claims about the contract can be made (section 2); a free Pro grant that was made to your e-mail address and never switched on, for 24 months after it was made (section 3); feedback you sent without an account, for 24 months after we receive it (section 3); a statement you sent on the "Help us improve imports" page, until we have reviewed it (section 5); the customer record we created at Stripe if you opened the Pro checkout, which keeps your e-mail address and former account ID and for which no deletion period is set yet (section 5); the browser error log, which keeps your account ID until its weekly purge (up to 37 days); and the visit statistics, which keep your former account ID until they expire (up to 13 months). We keep the visit statistics (section 2) as follows: each page view, page exit and action for 90 days; the summary of each visit (its key, first and last page, referring site, campaign tags and affiliate code, location, device, browser, operating system and language, and your account ID if you were signed in) for 13 months; the links between a day's key or a visitor identifier and an account for 13 months; and each day's random value for two days. Daily totals, which contain no key, visitor identifier or account ID, are kept without a time limit. When you delete your account, the account ID stored with each visit-statistics record is cleared and the links between a key or visitor identifier and your account are deleted. The records themselves stay until they expire as above. Each page view, page exit and action recorded while you were signed in, and the summary of each visit in which you were signed in, also keeps its visitor key, which is your former account ID with the prefix u:. Your account ID therefore stays in those records until they expire, although no account has that ID any more. We delete the old page-view log (section 2) 13 months after each row was written, and keep the browser error log (section 2) for 30 days (its purge runs weekly, so a record can remain for up to 37 days), then delete it. A browser error recorded while you were signed in keeps your account ID until then, also after you delete your account. Raw statements uploaded on the /training-uploads page are deleted by a daily purge 7 days after upload; the record of the upload stays with the account. Deleting the account deletes the record and any file the purge has not yet taken. Your profile and its picture are kept until you change or remove them, or until you delete your account, which deletes them. Submissions from the "Help us improve imports" page are kept until reviewed and turned into anonymised test files, or deleted earlier on request. Waitlist sign-ups are deleted 12 months after sign-up, or earlier if you ask us. An approved sign-up whose email belongs to an account is kept while that account exists, because it is part of what grants the account access; once the account is gone it is deleted by the same 12-month rule. The approval record made when we approve a sign-up – the invitation (your email address, a hash of the single-use registration link, who approved it, when it was issued, when it expires and when it was used) and the log entries for the approval, the invitation email and your registration, which carry your email address too – is deleted 12 months after it was written, or earlier if you ask us. Deleting your account does not by itself remove the waitlist record or the approval record; the 12-month rule does. When a user shares a portfolio with an email address that does not already have access to it, we store an invitation in that user's account: the invited address, the portfolio and the access level. The user who sent it can remove it while it is pending, and it is deleted when their account is deleted. Once the invited person signs in with that address, or signs up with it, the invitation is marked accepted and no longer appears in the sender's share list, so neither of them can remove it in the app: it stays, with the invited address, after the invited person deletes their own account, until the sender's account is deleted. If it holds your address, ask us and we delete it earlier. A free Pro grant made to an e-mail address is a record of its own (section 3). We delete the address from a grant 30 days after the grant switches on, or within a day after the account it switched on for is deleted, whichever comes first; the grant's other details stay, without the address. A grant that never switched on is deleted, with its address, 24 months after it was made; ask us and we delete it sooner. The public posts by other people (section 2) are deleted 90 days after we stored them. Where we posted a reply to a post, our record of that reply stays: our reply's text and link, and the post's title or opening words (up to 300 characters), without its author's name. An e-mail our team received about a post is not deleted by that rule: when a post's author asks us, we delete the post and our team's e-mails about it.

8. Your rights

You have the right to:

  • access the personal data we hold about you;
  • correct it if it's wrong;
  • delete it ("right to be forgotten");
  • port it to another service;
  • object to or restrict certain processing;
  • withdraw consent where consent is the basis;
  • complain to a supervisory authority. Our supervisory authority is the Estonian Data Protection Inspectorate (Andmekaitse Inspektsioon, aki.ee); you can also complain to the data protection authority of the EU country where you live.

Submit a request via our data requests page or by emailing privacy@rationexflow.com.

9. Security

We take reasonable technical and organizational measures to protect your data – encryption in transit and at rest, row-level isolation of user data, least-privilege access for engineers, and regular review. See our Security page for detail.

10. Children

RatioNexFlow is not intended for children under 18. We do not knowingly collect data from minors.

11. Changes

We may update this Privacy Policy. Material changes will be communicated via the service or by email. The "Last updated" date at the top reflects the most recent change.

12. Contact

For privacy questions, email privacy@rationexflow.com.