Privacy
Abstract
acceptodds stores what it needs to run accounts, and little else. It sets no advertising or tracking cookies, sells nothing, and counts visits without knowing who made them. This page lists what is stored, why, who else handles it, and how to have it changed or removed.
Who is responsible
acceptodds is run by the people behind it, reachable at [email protected]. Write there with any question about your data, or to use any of the rights in §6.
Your account
When you sign up and use the site, we store:
- your email address and any further institutional addresses you confirm, and the institutions they belong to, to sign you in and to show your institution;
- your display name, your handle and, if you set one, a hash of your password (never the password);
- sign-in sessions (not the network address or browser they came from), and a hash of each API key you create;
- the papers you follow, the comments you post, the emoji reactions you add, the reading groups you are in and what you add to them or mark as read: the site itself. Trades, positions and comments made on the market edition of acceptodds are still held, and shown nowhere here.
The legal basis is the contract you enter by signing up (GDPR Art. 6(1)(b)). It is kept while your account exists. A sign-up whose address is never confirmed is deleted after a week.
To delete your account, write to [email protected] from the address you signed up with.
What is public
Comments are shown under a random alias per paper, never your name, and reactions only as a count per emoji. Your display name, handle and institutions are shown to the members of reading groups you join, and with the group’s page to anyone who has its link. Your email address is never shown to anyone else.
We send only the mail the site needs: confirmation codes, sign-in links and password resets. Mail is delivered by Resend, which handles your address for that purpose only.
Visits, analytics and cookies
- Analytics. We count page views, a few product events (such as “a paper was followed”) and how fast pages load (load and response times, layout shift) with Umami, run on our own server. It sets no cookies and stores no IP address; addresses are used only in passing, to tell visits apart and to find a country. Page addresses are stripped of anything personal before they are sent, and events never carry an email, name, handle or amount.
- Paper views. A paper’s view count counts each visitor once a day. A visitor is your account when signed in, otherwise your network address; what is stored is a keyed hash of it and the day, deleted after two days. Which paper was read after which is kept only as a total per pair of papers.
- Activity log. We log which pages signed-in accounts look at, to run and improve the site. The log holds no content of what you did, only that it happened.
- Cloudflare sits in front of the site, protects it from abuse and so sees every visitor’s network address.
- Cookies and browser storage are only functional: the sign-in session, whether you have gone past the first page (the way into the safe for work edition), whether you have seen the welcome page, which venue you last picked, which home-page sections you left open and which announcements you dismissed. Your browser’s own storage remembers a pending confirmation, the last paper you read and, for each tab, your last home-page search. None of it tracks you elsewhere.
The basis for all of this is our legitimate interest in running a secure, working site and knowing how it is used (GDPR Art. 6(1)(f)).
Research
We may study how the site is used (which papers are read, followed and listed together) and publish what we find, in a blog post or a scientific paper. Anything published is aggregated or anonymised: never an email address, and never a name or handle tied to what someone did.
The basis is our legitimate interest in research (GDPR Art. 6(1)(f) and Art. 89; Swiss FADP Art. 31(2)(e)). You may object to it, as below.
Your rights
You may ask for a copy of what we hold about you, have it corrected or deleted, restrict or object to its use, and take it with you. Write to [email protected]. You may also complain to a data-protection authority: in Switzerland the FDPIC, in the EU the one where you live.