Privacy policy

What is stored

• Your account: the email address you signed up with, or the identifier from the Google account you signed in with. Passwords are handled by Google’s authentication service and are never seen by, or stored on, our servers.
• Your connections: the public wallet addresses you add, the labels you give exchange accounts, and the exchange API credentials — encrypted before they are written, decrypted only inside the server function that calls that exchange, and never returned to a browser.
• Your balances: the assets and quantities read from those sources, their value in USD, and which source each contributed. Plus one snapshot of the portfolio total per day, which is what draws the trend chart.
• Imported statements: the holdings the file replayed to, along with the row count and the first and last transaction dates. The uploaded file itself is parsed in memory and is not kept.
• Hand-entered holdings: the symbol, quantity and source name you typed.
• Feedback you send: the message, and the email address only if you chose to leave one. A message sent without an email is stored without any account identifier attached to it.
• A rate-limit counter for the feedback form: a count, two timestamps, and a one-way hash of either your account id or your IP address. It is kept apart from the feedback itself and expires after two days.

What is never stored

• Seed phrases and private keys. These are never requested by any part of the service.
• Exchange account passwords. An API key is not a password, and the two are never interchangeable here.
• Payment details. There is nothing to pay for.
• The raw contents of an imported statement file.

Server logs record the account id of whoever made a request and counts of what happened. They deliberately never record wallet addresses, API keys or balances. Feedback is the one exception in the other direction: its logs record no account id at all, because an anonymous message must stay anonymous in the logs as well as in the database.

Where it lives, and who else sees it

Data is held in Google Cloud and Firebase — authentication, database, server functions and the key-management service that encrypts exchange credentials — in a European region. The website itself is static files served by a hosting provider, which sees ordinary web request logs and none of your portfolio.

Reading your balances means these services receive the following, and nothing else:

• Blockchain data provider (Moralis): the public wallet addresses you added, in order to answer what they hold and what it is worth.
• Public network endpoints for Cronos POS and Polkadot: the public addresses on those networks, for the same reason.
• The exchanges you connect: read-only requests signed with your own API key, which is how the exchange knows the request is yours.
• A public market-data feed: asset symbols only, to price them. Nothing identifying you is attached to a price lookup.

Separately from all of that, the website counts its own visits, using the analytics built into Vercel, the hosting provider that already serves you every page. What it records is the page you opened, the site or search you arrived from, and the country, browser and device type that any web request reveals. It stores nothing in your browser at all — no cookie, no identifier, nothing that survives the visit. Repeat visits are counted by hashing the request itself, and that hash is thrown away after 24 hours, so it can report that a page was viewed and cannot build up a picture of you across days. Nothing about your portfolio, your connections or your account reaches it, and a signed-in page sends it nothing a signed-out one would not.

We advertise this site on Google, and if you allow it, a Google tag records that your visit came from one of those ads. It is loaded only after you agree, it runs only on the front page, and all it reports back is that an arrival happened — not who you are, not what you went on to do, and nothing from inside your account. Decline, or simply ignore the question, and the tag is never fetched at all.

Cookies and browser storage

Three things, and you get a say in one of them. Without asking, your browser keeps the session token that signs you in, managed by Google’s authentication library, and your light or dark theme preference — neither identifies you to anyone else, and the site cannot do its job without them. The third is Google’s advertising cookie, which is set only if you choose “Allow” on the banner, and which is what links an ad click to an arrival here.

The banner appears once, remembers your answer, and does not follow you around. To change that answer at any time, use “Cookie choice” at the bottom of any page: declining stops the tag being loaded again from that moment on, and clearing site data removes everything described here and signs you out. Visit counting is not part of this choice, because it uses no cookie to opt out of.

How long it is kept

• Connections and balances: until you remove the connection or delete your account. Removing a connection takes its holdings out of your portfolio on the next refresh, and an exchange credential is deleted together with the connection it belongs to.
• Daily portfolio snapshots: for as long as the account exists — they are the only record of what the portfolio used to be worth.
• Feedback: until it has been read and acted on, and any email address in it for as long as you would still expect a reply.
• Feedback rate-limit counters: two days, after which they delete themselves.

Your rights over your data

You can see everything the app holds about you in the app itself, and you can remove any connection at any time. Beyond that you can ask for a copy of your data, ask for it to be corrected, or ask for your account and everything in it to be deleted. If you are in the UK or the EU these are rights you hold under data protection law, along with the right to object to processing and to complain to your national supervisory authority.

To make any of those requests: Use the feedback form on the homepage, and leave your email address so there is somewhere to reply to.

Children

The service is not intended for anyone under 18, and accounts are not knowingly created for them. If you believe a child has created one, get in touch and it will be removed.

Changes to this policy

When what the service stores or sends changes, this page changes with it and the date at the top moves. It is written to describe how the software actually behaves rather than to describe everything it might one day do.