Privacy Policy

The short version

Reading costs you nothing. Public pages set no cookie, run no third-party script and record nothing about you as a person. Visits are counted as one number per page per day — no IP address, no browser fingerprint, no visitor id.
An account holds three things. Your email address, the name you typed, and a one-way hash of your password. If you use Continue with Google there is no password at all — just the account id Google gives us.
Your portfolio stays on the server. The amounts and buy prices you enter are shown back to you and to nobody else. They are in no export, no email, and no model prompt.
The newsletter is opt-in and stays opt-out-able. An address joins the list only by clicking a link sent to it, and every issue carries a one-click unsubscribe that works.
There is nobody to sell you to. No advertising network, no analytics product, no data broker, no embedded third party anywhere on this site.
To see, correct or delete anything: hello@hodlometer.com.

What we store, and why

The table is the whole inventory, read off the code rather than off a template. Where a retention period exists it is the one the software actually enforces; where none exists we say so instead of inventing a number.

What	Why we have it	How long
Email address and name	Signing you in, confirming the address is yours, resetting a forgotten password, and sending you the alerts you set up.	Until the account is deleted. Ask and it goes.
Password hash	Signing you in. It is a one-way hash — we cannot read your password, and nor can anyone who steals the database. Accounts created through Google have no password at all.	Until the account is deleted.
Google account id	Only if you use Continue with Google. At sign-in Google tells us your account id, your email address and your name; we keep the id so we recognise you next time. We never call Google again afterwards, and we ask for no access to anything in your Google account.	Until the account is deleted.
Portfolio	The amounts, buy prices and buy dates you type in, so the site can show what your own position is worth. Nothing here is checked against a blockchain, an exchange or anything else — it is a number you typed.	Until you clear it yourself or the account is deleted.
Price alerts	The asset, the threshold you named, the delivery channel you chose, and whether it has fired. Needed to send the alert you asked for.	Until you delete the alert or the account.
One-time links from email	Address confirmation and password reset. Only a SHA-256 hash of the link is stored, never the link itself, so the database cannot be used to get into an account. Confirmation links live 48 hours, reset links 2 hours and one use.	Deleted by the daily job 7 days after being used or expiring.
Sign-in and form attempts	An email address (or an internal rate-limit key), an IP address and a timestamp. This is the only place we write down an IP address ourselves, and it exists for one reason: stopping password guessing and form spam.	The daily job deletes everything older than 2 days.
Newsletter subscription	Your address, when you confirmed it, whether you have unsubscribed, and hashed tokens for the confirm and unsubscribe links. The confirmation is what proves the subscription was yours and not somebody typing your address into our form.	While you are subscribed. After you unsubscribe the row stays, marked unsubscribed, so nothing can quietly put you back on the list — ask and we delete it outright.
Newsletter send log	Which issue went to which address, whether it was accepted, and the error if it was not. It is what stops a restarted send from mailing you twice, and what lets us answer “why did I not get it”.	No automatic deletion is set. It is removed together with your subscriber row when you ask us to delete it.
Page counters	A date, a path and a number — “/tools/mayer was opened 412 times on this day”. No IP address, no user agent, no cookie, no visitor id, no session. The browser string is read in memory to drop crawlers and is never written anywhere. There is no row here that is about a person, which is the point.	Kept indefinitely. There is nothing in it to link back to you.
Campaign counters	The same counter split by the `utm_source` in the link you followed, so we can see which post brought readers. That value is a property of the link, not of you, and is stored the same way: date, path, source, number.	Kept indefinitely.
Your session	A session file on the server plus a cookie in your browser, which is what keeps you signed in. Changing your password destroys every session of that account everywhere, on purpose.	30 days, or until you sign out.
Logs	Our own application log records errors and the work the daily job does. Two lines in it touch you: the address a subscription confirmation was sent to, and the IP address of a submission caught by the spam trap. Separately, the web server keeps its own access log — IP address, time, URL, browser string — as every web server does.	The application log is written per month and has no automatic deletion; we clear it by hand. The web server log is kept by our host under their retention rules, not ours.

Why we are allowed to hold this: the account, portfolio and alert data exist because you asked for a feature that cannot work without them — the account is the feature. The newsletter runs on your explicit confirmed consent, which you can withdraw at any second. The attempt table and the logs exist to keep the site standing and to stop abuse. The counters hold no personal data at all.

Cookies

Three cookies exist on this site. None of them is for advertising, none is for analytics, and none belongs to anybody but us.

kurs_sid — your sign-in session. Set when you sign in, and on the sign-in, sign-up and password forms, which carry a token that protects them against cross-site request forgery. HttpOnly, SameSite=Lax, Secure over HTTPS, 30 days. Reading a public page never sets it: if you never sign in, you never get one.
kurs_theme — light or dark. Written by our own script when you use the theme toggle, so the server can send the right colours on the next page instead of repainting it in front of you. One year. It holds the word light or dark and nothing else.
WordPress cookies under /learn. They appear only when somebody signs in to the blog's admin area, and that somebody is us. Reading an article sets nothing.

There is no cookie banner here because there is nothing to ask you about: no cookie on this site tracks you, and none of them is set on behalf of a third party.

Two companies, for two narrow reasons.

Hostinger — our hosting provider. The site, its database and its email all run on their machines, requests reach us through their CDN, and mail we send you leaves through their SMTP server. They hold the data because they run the hardware, not because they have any use for it.
Google — only if you press Continue with Google. Pressing it tells Google you are signing in to this site, and Google hands us your account id, email address and name in return. If you never press it, Google learns nothing about you from us.

That is the entire list. We do not sell data, rent it, trade it, or hand it to anyone for marketing. If a court or Georgian law obliges us to produce something we will comply, and we would tell you unless we were forbidden to.

The site does talk to plenty of other services — CoinGecko, Binance, alternative.me, Deribit, Bitstamp, Bitfinex, Coinbase Exchange, Yahoo Finance, the LBMA, Wikimedia and Google's Gemini API — but always in the other direction: our server asks them for market numbers, and nothing about you is in the question. Your browser never contacts any of them, which is exactly why there is no third-party script on these pages to do it. The same goes for our accounts on X, Telegram, Bluesky and Mastodon: we post our own charts and links there, never anything of yours.

One detail about alerts worth naming rather than burying. Your alerts are delivered by email, to your address, and by nothing else. We do have a Telegram channel, but it is a public one that carries our own posts, and there is no private chat between it and you — an alert sent there would show the asset and the threshold you picked to everyone reading the channel. So that delivery route is reserved for the site's own administrator account, and what you configure is never posted to it.

What this site does not do

No advertising networks and no ad tracking of any kind.
No third-party analytics. No Google Analytics, no Meta pixel, no hosted analytics product. The counters described above are ours and stay on our server.
No third-party scripts at all. Every page ships a content security policy that forbids the browser from loading one, so this is enforced rather than promised.
No tracking pixels in email. We do not know whether you opened an issue. We count how many times a link in an issue was clicked in total, never who clicked it.
No profiling, no fingerprinting, no cross-site tracking. We do not build a picture of you, because we hold nothing to build it from.
No selling or renting of data — and it is not a business model we are keeping in reserve either. How the site is funded is written down.

Your rights, and how to use them

We are based in Georgia, not in the EU or the UK, so the GDPR does not apply to us and we are not going to dress up as if it did. Most of the people reading this are in Europe, though, and the rights it gives are the right ones — so we give them to you voluntarily, wherever you live:

See everything we hold about you.
Correct anything that is wrong.
Delete it — the portfolio, the alerts, the subscription, the whole account.
Take it with you, as a machine-readable copy.
Object to a particular use, or ask us to stop processing.
Withdraw consent to the newsletter at any moment; the unsubscribe link is that right, and it is one click.

Some of this you can do without asking anyone: edit or zero your holdings on the portfolio page, delete alerts from the markets page, change your password from your account menu, unsubscribe from the bottom of any issue.

For the rest, write to hello@hodlometer.com. There is no self-service “delete my account” button on the site yet; send the request and we delete the account together with its portfolio rows and its alerts. Please write from the address on the account — that is the only way we can tell it is you, because we deliberately hold nothing else that could prove it. We answer within 30 days and usually much sooner, and deletion requests go first.

An address joins the list one way only: somebody types it into the form, we send a confirmation email to it, and somebody clicks the link in that email. Until that click nothing else is ever sent to the address. That is not politeness — the form is open to the whole internet, so without the click anyone could sign you up.

Every issue carries a one-click unsubscribe, both as a link at the bottom and as the header your mail client uses for its own unsubscribe button. It takes effect immediately, never asks you to sign in, and never asks you why. The list lives in our own database: the addresses are not uploaded to a mailing platform, and the emails are generated on our server and handed straight to our host's SMTP.

The blog at /learn

The articles run on WordPress. Comments are switched off across the whole blog, there is no reader registration, and the theme loads no avatars, no embeds and no fonts from anywhere else. Reading an article records nothing beyond the same date-and-path counter as the rest of the site, plus whatever the web server writes into its access log. Failed sign-ins to the blog's admin area are slowed down by remembering a hash of the IP address for fifteen minutes, and nothing longer.

Children

This site is not built for children and holds nothing they need. Do not create an account if you are under 16. If we find out that an account belongs to somebody younger, we delete it.

Who we are and which law applies

The site is operated by SP Konstantin Protasov, an individual entrepreneur registered in Georgia on 06.06.2022, Identification Number 302221655, at Mikheili Tsinamdzgvrishvilis Street, 52, Tbilisi, Georgia, 0102. Contact: hello@hodlometer.com.

Georgian law governs what we do with your data — specifically the Law of Georgia on Personal Data Protection, adopted on 14 June 2023 and in force since 1 March 2024. If you think we have mishandled something, tell us first; if that gets you nowhere, you can complain to the national supervisory authority. That role belonged to the Personal Data Protection Service of Georgia until 2 March 2026, when its functions passed to the State Audit Office of Georgia.

We are not established in the EU. We have no EU representative and no data protection officer, and saying otherwise would be a nice-sounding lie. The rights in the section above are ours to grant and we grant them anyway.

On location: the site runs on shared hosting from Hostinger, so your data physically sits on their infrastructure rather than on a machine we own, and we do not choose which of their data centres serves it.

Changes, and contact

When this page changes, the date below changes with it and we say what moved. We are not going to rewrite it quietly. If a change actually alters what happens to your data — a new recipient, a new purpose — subscribers hear about it in the newsletter and account holders by email, rather than finding out by re-reading this page.

Anything on this page — a copy of your data, a correction, a deletion, or a sentence here you think is vague — goes to hello@hodlometer.com.

In effect from 30 July 2026. First version; nothing has been changed yet.