Privacy Policy

Who is responsible

This policy covers the tailmypicks.com website and everything served from it.

What we deliberately do not collect

This list comes first because it is the part that took work. None of the following is recorded by this application, anywhere, for any visitor:

• No IP address. Not in the checker, not in any usage counter. Abuse is bounded by rate limiting, which does not require keeping one.
• No user agent and no referrer. Which browser you use and which page sent you here are not written down. One honest qualification: on the three pages we count, the server reads the browser’s name at the door to tell a known crawler from a person, and then drops it; it is never stored, and neither is the verdict.
• No advertising or analytics third party. No tracking pixel, no fingerprinting, no third-party script of any kind. If that ever changes, this list changes first.
• No wallet connection. TailMyPicks never asks you to connect a wallet or to sign anything, and could do nothing with it if you did.

What we collect when you have no account

This is the whole of what a visitor leaves behind. We count the opening of three pages and no others: the landing page, the sign-up page and a wallet’s page. Opening one of them writes down:

• Which of the three pages it was, and the date and time.
• A random number identifying your browser, kept in a cookie on this site for thirteen months. It is set the first time you open one of those three pages and nowhere else. It exists so that ten visits from one person do not read as ten people. It is generated at random, is not derived from anything about you or your device, and cannot be traced back to you by us or by anybody who obtained it. Clear your cookies and you are a new visitor, with nothing connecting you to the old one; we would rather undercount than identify you.
• On a wallet’s page only, two things more: the wallet address you looked at, which is a public identifier on a public blockchain, and which of our four answers you were shown: a record, a wallet we rebuilt that scores nothing, an address we have never seen, or a mistyped one. We want to know whether the second answer is the one people actually reach, because it is the one this product is for.

A known crawler is not counted. When a search engine’s robot announces itself, it is given no cookie and no row is written; the browser name that told us so is read and dropped in the same breath, and is not kept. A robot that pretends to be a person is counted as one, and we accept that rather than try to be cleverer about who you are.

That number is never tied to an account. If you go on to create one, nothing links the account to the random number in your cookie: not a column, not a query. We can say how many visitors of the sign-up page became members on a given day, as one total divided by another, and never which of them you were.

We do not ask your consent for that cookie, and this is why: it is used only to count visits to this site, by us, for us. It is not shared, not combined with anything else, not used to follow you anywhere, and its life is not extended each time you come back. Those are the conditions the CNIL sets for audience measurement that needs no banner, and meeting them was the design rather than the excuse.

Everything on the list above still holds while this happens: no IP address, no user agent, no referrer. No legal page is counted, and reading this policy leaves nothing behind. And if you mistype an address, what you typed is not kept; we record that a typo happened and nothing about what it said.

The server that serves these pages keeps operational logs, as any web server does, for security and debugging. They are not used to build a profile of anyone and are not combined with anything else.

What we collect when you have one

An account is an email address and a password, one statement you make when you create it, and two answers you may give. This is everything stored against it. There is no name, no photograph and no profile, because none is ever asked for.

• Your email address. It is how you sign in, how a forgotten password is reset, and how you are told before a trial ends. It is not sold, not shared, and not used for marketing without asking you separately.
• A hash of your password — argon2id, a deliberately slow function designed to be expensive to attack. We cannot read your password, and neither could anybody who obtained a copy of the database.
• Your statement that you are of legal age where you live and accept the Terms (the box you tick to create the account), kept as the date and time you ticked it and the date of the Terms you accepted. It is a declaration and nothing proves it: no date of birth and no identity document is ever asked for.
• How you heard about TailMyPicks, if you answered. One answer from a fixed list: X, Reddit, a friend, a search engine and so on. There is no box to type into, so it can never hold anything you wrote.
• Your time zone, if you gave one — a name such as Europe/Paris. On the sign-up page your browser fills the field in, where you can see it, change it or empty it before sending; it is not read in any other way. Nothing on the site is shown in it, and nothing records when you use the site.
• When the account was created, when its address was confirmed, and when its trial ends. Confirming the address is what opens the account and starts the trial.
• The wallets you follow, with the nickname you gave each one, the categories you chose for it and whether it may raise an alert; when you last opened your alerts; and whether the bell plays a sound or shows a desktop notification.
• Your subscription, if you take one — the payment provider’s reference for you and for the subscription, its status, the end of the period paid for, and the messages from the provider that changed it. Payment itself is handled entirely by the provider: card numbers never reach our servers and we never see them.
• The devices you are signed in on. One row per signed-in browser, holding a hash of the value in the cookie rather than the value, so a copy of the database signs nobody in. You can sign them all out from the account page.
• Failed sign-in attempts, for fifteen minutes, so that guessing a password is slow. Still no IP address: the count is kept against the account and against a random number in a cookie, and is deleted as soon as it is too old to count.

Your account page shows your address, your statement, your time zone and your answer about how you heard of us, exactly as they are kept.

Deleting your account deletes all of it, immediately, from the account page and without asking anybody: everything listed above and every link that was emailed to it, and every device it was signed in on is signed out. There is no archive and nothing to restore afterwards. What survives outside our database is what any email provider keeps in its own delivery logs, the payment provider’s own records of a payment, and the server’s ordinary operational logs, each for its own period.

The wallet records are not data about you

TailMyPicks publishes the trading record of wallet addresses on prediction markets. Those records are computed from public blockchain activity and public interfaces. They are not data we collected from our members, and being a TailMyPicks member has no bearing on whether your wallet appears: the index was built from the markets, not from the audience.

Why we process it, and for how long

• Counting how many people arrive, use the checker and reach the sign-up page, and how many come back: legitimate interest (GDPR art. 6(1)(f)). We cannot judge a feature we cannot measure, and this is the least we could measure and still know. The rows behind that count are kept for ninety days and then deleted. Before they are, each day is added up into one row of totals (so many openings of each page, so many distinct browsers, so many accounts created), and those daily totals are kept: they identify nobody and are never joined to an account. The cookie itself expires after thirteen months and is never renewed, so after that a returning browser is a new one to us whatever the older rows said.
• Providing the service and your subscription: performance of a contract (GDPR art. 6(1)(b)). Kept while your account exists, and deleted with it the moment you delete it rather than on a schedule afterwards. Your statement that you are of legal age and accept the Terms is the record of that contract, and is kept and deleted the same way.
• The two answers you may give at sign-up (how you heard of us, and your time zone): legitimate interest (art. 6(1)(f)); knowing which ways of finding this site bring the members who subscribe, and in which time zones members live. Both are optional, are only ever read as totals, and are kept while your account exists and deleted with it. You may ask for either to be erased while keeping the account.
• Security, abuse prevention and server logs: legitimate interest (art. 6(1)(f)). Kept for a short operational period and not longer. A failed sign-in is counted for fifteen minutes and then deleted.
• Invoicing and accounting records: legal obligation (art. 6(1)(c)). Kept for the period French commercial law requires, which is ten years.
• Service emails such as a password reset: performance of a contract. No marketing email is sent without separate consent.

Who else touches it

Only the providers needed to run the service, and today there are three.

• Hetzner Online GmbH hosts the server and the database in the European Union.
• Resend (Plus Five Five, Inc., the United States) delivers the emails the site sends (an address confirmation, a password reset, a notice that a trial is ending), so it receives your address and the message. Ours are sent from its Irish region, in the European Union. Resend is based in the United States, and data reaches it under the EU-U.S. Data Privacy Framework, under which it is certified, and the European Commission’s Standard Contractual Clauses.
• Stripe (Stripe Payments Europe, Limited, Ireland) takes the payment if you subscribe. Your card details go to Stripe and never reach us. Stripe transfers data to the United States under the EU-U.S. Data Privacy Framework and the Standard Contractual Clauses, and for some purposes of its own (detecting fraud, meeting its legal obligations) it decides how your data is used, under its own privacy policy (stripe.com/privacy).

Your rights

You may ask for access to your data, its correction, its erasure, its portability, or a restriction of processing, and you may object to processing. We answer within one month. Write to contact@tailmypicks.com.

You may also lodge a complaint with the CNIL (cnil.fr) or with the supervisory authority in your own country.

Security

Passwords are stored only as an argon2id hash, a function chosen because it is deliberately slow and memory-hungry, which is what makes a stolen database expensive rather than merely inconvenient to attack. The database refuses to store a password hashed any other way. What keeps a device signed in is stored as a hash too, so a copy of the database signs nobody in. Traffic is encrypted in transit. Payment details never reach our servers. Only we have access to production data. No system is perfectly secure; in the event of a breach affecting your data we will notify you and the authority as the law requires.