← back to the app · terms of service · English · Italiano

Privacy notice

Curse of Strahd — Tarokka Randomizer · last updated 16 October 2026

In short: the randomizer runs entirely in your browser. The cards you draw and what they mean for your campaign are never sent to any server — they stay on your device. We do not profile you, there is no account to create. The one cookie we set exists only if you connect Google Drive: it keeps you signed in, and the permission it unlocks is kept on our server, encrypted, until you disconnect — the only thing of yours we hold, and only if you ask.

Who is responsible

The data controller is TirateIniziativa, which runs this project as non-commercial fan content. Contact: [email protected].

What stays in your browser

The app saves three entries in the browser's local storage. These are not cookies and are never transmitted.

entry	what it holds	why
`tarokka.state.v1`	the reading on the table: which cards came up in which position, the name you gave it, your language, and your weighting settings	so the reading is still there after you close the tab — it is the very service you asked for by using the app
`tarokka.lastVisitDay`	a date, e.g. `2026-09-28`	so the same visit is not counted twice on the same day
`tarokka.drive.v1`	only if you connect Google Drive: the fact that you said yes, and the identifiers of the two folders	so the folders are not created again at every visit. It never holds the access token, which lives in memory only

You can clear everything at any time, from New reading inside the app or by clearing the site data in your browser. Neither requires telling us, because we know nothing about it.

If you export a Markdown or JSON file, your browser produces it and it goes wherever you send it.

Sharing a reading with your players

When you open a session, the five cards of the reading travel through a Cloudflare Worker so that the people you gave the code to can watch the same table. What travels is only the reading itself: which card is in which position, and the name you gave it. No account, no identity, no address book — whoever holds the six-character code is whoever is at the table. The session is kept for the length of the game and its storage is erased one hour after the last person disconnects.

What reaches us: the visit counter

At the bottom of the page there is a public visit counter. When you open the app, your browser sends our server a request that says only "one more visit". The server keeps monthly totals only — for example 2026-09: 412 — plus the running total. No IP addresses, identifiers, cookies, device or referrer information are stored, and there is no way, not even for us, to trace those numbers back to a person or to know how many pages anyone viewed. The "once a day" de-duplication happens in your browser, using the date described above, and is never sent.

Hosting

The site, the sessions and the counter run on Cloudflare infrastructure (Cloudflare, Inc., United States), acting as data processor. Like any hosting provider, Cloudflare transiently processes the technical data needed to deliver pages and protect the service from abuse, including the request's IP address. See Cloudflare's privacy policy.

Typefaces

The typefaces (Cinzel, EB Garamond and Inter) are served from this site, so opening a page does not contact anyone else. Until 18 October 2026 they came from Google Fonts, which meant your browser sent its IP address to Google's servers to fetch them; it no longer does.

Google Drive, if you connect it

Connecting Google Drive is optional and never automatic: it starts only when you press “Sign in with Google”, and until you do, the site does not contact Google at all: there is no Google script on the page, and the sign-in window opens only when you press the button. When the page opens it asks our own server whether you are signed in; only if you are does it reach Google, to read the account name and your files.

If you do connect it:

one permission is requested, the drive.file scope, which grants access solely to files this app created and to nothing else in your Drive: the rest of your files stay invisible to us;
no name, email address or other profile data is requested. Writing a file into the Drive of whoever authorised it does not require knowing who they are;
readings travel straight from your browser to Google, never through us: we keep no copy and never see them;
the name you give a save is stored in the file description on Drive, next to the file itself, so that the list of your saves can show it without opening any of them;
the permission Google issues is kept on our server — the TirateIniziativa home page’s Worker, on Cloudflare’s infrastructure — encrypted with a key that exists only there, so that one sign-in serves every TirateIniziativa tool for thirty days. When this app needs to reach your Drive, it asks that server for a short access token (one hour), which it keeps in memory only. No name, no email address and no profile are stored with it: it is a permission, not an account;
the sign-in lasts thirty days and starts again from thirty every time you come back with fewer than fifteen left; unused, it expires and is deleted. It is also deleted as soon as Google turns the permission down, and “Disconnect” deletes it at once and revokes the permission at Google — for every tool and every device. Besides the cookie described below, all that stays in the browser is the fact that you said yes, plus the folder identifiers, which open nothing on their own;
files are created in the TirateIniziativa_AppDataStorage folder of your Drive. They are yours: move, rename or delete them whenever you like, and “Disconnect” revokes the permission without touching them.

Use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Transfers, retention, minors

The monthly visit totals contain no personal data and are kept indefinitely, since their purpose is to show how often the tool has been used. A Google Drive sign-in is kept for thirty days from your last visit, or until you disconnect. The data in your browser is kept by you, for as long as you like. The service is not specifically directed at children and does not knowingly collect data about them — it does not knowingly collect data about anyone.

Your rights

Regulation (EU) 2016/679 gives you rights of access, rectification, erasure, restriction, objection and portability. In practice almost no personal data here can be subject to them — the one thing we hold, the encrypted Drive permission if you connected it, is deleted by “Disconnect”, with no need to ask us — and for the rest: what you write is on your device and you delete it yourself. If you think something is wrong you can write to the address above, or lodge a complaint with the Italian Data Protection Authority.

Cookies

One cookie, and only if you connect Google Drive. Until you do, this site sets none at all — neither technical nor profiling, neither first- nor third-party. The local-storage entries described above are not cookies and never leave your device.

cookie	what it holds	why	how long
`ti_session`	a random key that opens your Drive sign-in on our server — not the Google permission, no name, no email address, no profile. It is `HttpOnly`: not even our pages’ scripts can read it	so that one sign-in covers every TirateIniziativa tool: it belongs to `tirateiniziativa.com` and is sent only to its sign-in address (`/api/auth`), where this app asks for a fresh permission instead of asking you to sign in again	thirty days, renewed when you come back. Deleted when you press “Disconnect”, or when Google turns the permission down

It is a strictly necessary cookie: it exists only to deliver the function you asked for by pressing “Sign in with Google”, it is not used to profile you and it is never shared with anyone. That is why no consent banner is shown — connecting Drive is itself the consent, and it can be withdrawn at any time with “Disconnect”.

What it costs, said plainly. Unlike the local-storage entries above, a cookie travels: the browser sends it to our sign-in address whenever a tool asks for a permission. The server keeps only its fingerprint (a SHA-256 hash), never the key itself, so even the stored sessions open nothing on their own — but the cookie does leave your device, which those entries never do. We accepted that because it is the only way a single sign-in can serve every tool. If you would rather it did not exist, do not connect Drive, or press “Disconnect”: it is deleted immediately and the app goes on working exactly as before.