Skip to content

DraftThis text describes what the system does today, derived from the code, and is pending legal review.

Privacy

Written from the code, not from a template: what this page says is what the system does.

Controller

The data controller is Carlos, tax ID NIF, registered address C/. For any question about your data, or to exercise your rights, write to portcodex@jefmonjor.dev.

What is stored

Of your identity, the product database holds an opaque identifier, your language, your display currency, your role, your tax residence by period, the version of the Terms you accepted with its date and the date on which you declared you are 18 or older. The service is not intended for anyone under 18. Your email, your name and your password are not there: they live with the identity provider and the product only keeps the reference. Of your portfolio it stores the addresses you declare, the movements read from chain, the positions, the prices applied, the wealth snapshots and the tax result for each year.

The waitlist

If you request beta access from this site we keep your email, your language, what you tell us you would like to track if you write it, the country if you gave one on an earlier form, the version of this text you accepted and the date. We do not keep your IP address with the request: only the counter that limits submissions, which is deleted with its window, as in the rest of the service. We use it to write to you when there is room and to decide which networks and protocols to prioritise; it is not sent to anyone else, it lives in the same database (Netcup, European Union) and we do not use it for newsletters. The request is kept for at most 12 months from when you send it: a daily process deletes the ones past that period. It goes earlier in two cases: when you create your account with that same email, because it has served its purpose, and when you ask for it by writing to portcodex@jefmonjor.dev.

What is never stored

Private keys or recovery phrases —they are never asked for—, plain-text passwords (the identity provider only keeps a hash), payment details, and no card data at all. Raw provider responses are not archived: what the ledger needs is normalised and the rest is discarded. Your wallet addresses do not appear in the system's operational logs, which work with internal identifiers.

Your IP address

It is held in the rate-limit counters, to stop abuse of the service, and it is deleted with the counter's window: minutes, not days.

The audit log

Administration actions —sign-ups, role changes, closures—, the operations on your portfolios and your account’s security events —sign-ins, credential changes, exports of your data and the closure itself— leave a row recording who did what and when. For operations it keeps the portfolio and some details of the operation, such as amounts or tokens; for security events, an opaque identifier, your network prefix and your browser type, never the full IP address. That log is insert-only on purpose: nothing in the system can edit or delete it, because that is exactly its value. If your account was set up by the administration, your email is in the row of that sign-up.

Who it is shared with

Only with the providers the service needs in order to work, and only the data each one needs: Supabase (identities and passwords, in Ireland), Brevo (product email), Netcup (application servers and the database, in the European Union), Backblaze (stores the PDF reports you generate in its B2 storage, in the European Union: they are deleted after 24 hours, and the copy the storage keeps after deletion is gone within one or two more days; and, in a separate private storage, it will keep the daily backup of the database, encrypted before it leaves our servers), Vercel (serves the web application and this site, and processes browsing requests), Sentry (receives the application's technical failures —what failed and where, scrubbed of personal data—, in its European Union region), Umami (counts visits and steps such as «sign-up completed» or «report generated», without cookies and without data that identifies you, on our own instance hosted at Netcup, in the European Union), the providers that read the public networks —Zerion and Alchemy on EVM chains, Mempool.space and Blockstream on Bitcoin, Helius on Solana, and Jupiter, Kamino and Meteora for your DeFi positions on Solana—, which receive the public address of the wallet being read. The price providers —DeFiLlama, CoinGecko and the European Central Bank through Frankfurter— receive token identifiers and dates, never your addresses. And, once billing is active, Stripe processes the subscription payment: your card details never reach us.

Where the data is

The database and the application servers are in the European Union (Netcup); the identity provider, in Ireland (Supabase). The daily backup of the database will be made every day on that same server and will leave it already encrypted towards Backblaze storage in the European Union. For the chain-reading and price providers, which receive public addresses or token identifiers, no region is documented today: it will be published once each contract is signed.

For how long

Honestly: there is no general retention period today, and so none is promised. What is implemented and can be stated: the report files you generate —the PDF and the CSV— are deleted from storage after 24 hours, and the rate-limit counters after a few minutes. The encrypted daily backup of the database will be kept for 30 days, and the one from the first day of each month for 12 months; after that the storage will withdraw it and, 30 days later, delete it for good. The rest of the data is kept while the account exists and is deleted when you close it, except for what is explained below. A period will appear here when the process that enforces it exists, and not before.

Closing an account, as it works today

You can close your account yourself from “My account”, in the danger zone: we ask for your password, a one-time code (the one from your authenticator app, or one of your backup codes, if you have turned it on; otherwise, one sent to your email) and for you to type your email to confirm. Closure happens in two steps. When you confirm it, your access is closed at once: all your sessions are signed out and your portfolios stop being visible. Then, in the background, your portfolios with their addresses, movements, positions, wealth snapshots, tax results and reports, your tax residence and your report files are deleted from the database and storage, and your identity is deleted from the identity provider, together with your email and password; with a lot of data it may take a little longer, and if something fails it is retried on its own. There is no period to change your mind: the closure cannot be undone. If you were a member of a firm, you leave it; if you were the last one, the firm is dissolved and its clients’ portfolios, which they keep, are left without a firm. A closure handled by administration is a different thing: it marks the profile and its portfolios as closed without deleting their data.

What is kept after closure, and why

What remains, and why. A minimal record of your profile —an opaque identifier, language, currency, role and the closure dates, with no name or email—, because the operations you performed as a manager on other people’s portfolios still refer to it and are those people’s records. The audit log described above, which cannot be edited: it is kept for the establishment, exercise or defence of legal claims (Article 17.3.e GDPR). Sessions already signed out, with network prefix and browser type, until the periodic session sweep deletes them. The system’s technical job log, which names portfolios by their opaque identifier. And the database backups, which contain your data until they expire under their own retention window.

Your rights, and where they really stand

Access and portability: from “My account” you download as a JSON file everything we hold about you —profiles, portfolios including closed ones, wallets, exchange accounts without their keys, movements, positions, tax results, the list of reports and your tax residence, subscription and usage data—, with no data about other people; up to three copies per hour. Rectification: you correct your profile details and the movements the reader got wrong in the application itself. Erasure: see “Closing an account, as it works today”. Objection and restriction: write to portcodex@jefmonjor.dev. You may lodge a complaint with the Spanish Data Protection Agency.

Cookies and what is stored in your browser have their own page: Cookies