← back to the home page · terms of service · English · Italiano

Privacy notice

TirateIniziativa · last updated 16 October 2026

In short: the TirateIniziativa tools run entirely in your browser. What you write into them — parties, encounters, maps, readings — is never sent to any server: it stays on your device. We do not profile you and 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.

What this covers

This notice applies to tirateiniziativa.com and to every tool hosted on its subdomains that run in your browser: the D&D Encounter Balancer, the D&D DM Toolkit, HexJourney and the Curse of Strahd Tarokka Randomizer.

LoreVeil (loreveil.tirateiniziativa.com) is the exception, and this notice does not cover it: it is a shared campaign diary, so it needs an account and keeps the campaign on a server. It has its own privacy notice and its own terms, and what is written here does not apply to it.

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 two entries in the browser's local storage. These are not cookies and are never transmitted.

entry	what it holds	why
one entry per tool, e.g. `balancer.state.v1`	the document you wrote in that tool, with the chosen language and its preferences	so your work is still there after you close the tab: it is the very service you asked for by opening it
`ti.lastVisitDay` and similar	a date, e.g. `2026-09-27`	so the same visit is not counted twice on the same day

The home page can be installed on a phone or computer like an app. To open without a connection it keeps, in the browser’s own cache, a copy of its pages, icons and script — the same files anyone downloads, nothing about you. The Google Drive sign-in is never put there. Uninstalling the app or clearing the site data removes the copy.

You can clear everything at any time, from inside the tool — each has a command that empties the document — or by clearing the site data in your browser. Neither requires telling us, because we know nothing about it.

If you export a JSON file or a link, your browser produces them and they go wherever you send them. In the case of a link, the document travels in the part of the address after the #, which browsers never transmit to a server — not even we can see it.

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 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 pages load two typefaces (Cinzel and EB Garamond) from Google Fonts. To deliver them, your browser contacts Google's servers (fonts.googleapis.com and fonts.gstatic.com), which at that moment receive the request's IP address and your browser's technical information. This is the only third-party connection made when a page opens; Ko-fi, below, is contacted only if you ask for it. See Google's privacy policy.

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.

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;
your email address is never requested, nor is any other profile data. The only thing we read about you is the display name of the account, and only to show you which Drive you are writing into — the same sign-in serves every tool, so it may well be an account you chose somewhere else, and saving into the wrong Drive would otherwise fail silently. That name stays in this browser for the session, is never stored and never reaches us. The email address is not merely ignored: the request we send to Google asks for the name alone, which anyone can verify by looking at the traffic;
documents travel straight from your browser to Google, never through us: we keep no copy and never see them;
the permission Google issues is kept on our server — the 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 a tool needs to reach your Drive, the server uses it to ask Google for a short access token (one hour), which the tool 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 — on every device. In the browser all that stays is the cookie described below and 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.

Donations with Ko-fi

If you choose to support TirateIniziativa, the “Support” button opens Ko-fi’s donation panel (Ko-fi Labs Limited, United Kingdom) in a window over the page. Only from that moment does your browser connect to Ko-fi, which receives your IP address and may use its own cookies. Until you press it, the site loads nothing from Ko-fi — no script, no image, no widget — and Ko-fi does not know you passed by.

The payment is handled by Ko-fi and by PayPal or Stripe, each as an independent controller under its own privacy policy. We never see your payment details: we only receive what Ko-fi tells us about the donation — the name you choose to show, the amount, the message. See Ko-fi’s privacy policy.

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: what you write is on your device and you delete it yourself, and the one thing we hold — the encrypted Drive permission, if you connected it — is deleted by “Disconnect”, with no need to ask us. 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 the pages’ own 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 each tool asks for a fresh permission instead of asking you to sign in again	thirty days, renewed when you come back. Deleted when you 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 by disconnecting.

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 disconnect: it is deleted immediately and the tools go on working exactly as before.