Privacy

What I collect, why, where it lives and how to delete it. Written in plain English, because a policy nobody can read protects nobody.

Last updated: 5 August 2026 · Fablepost is in closed beta

The short version

Who handles the data

The data controller is Lorenzo Corrias, who builds Fablepost as a personal project. For anything about your data, write to lorenzocorrias.w@gmail.com — you get me, not a desk.

The site

This site is static pages. It uses no cookies, has no analytics, and loads no fonts, images or scripts from other domains: everything you see is served from here.

There is no cookie banner because there would be nothing to ask. If I ever add an analytics tool, this page will change before that happens, and then there will be a banner.

The site is hosted on Cloudflare Pages, which keeps short-lived technical request logs — IP address included — to make the network work. I don't read them and I do nothing with them.

The app

Your account

You sign in with Google. Sign-in is handled by Clerk, which keeps what Google hands over: name, email address and profile picture. I don't copy any of that into my own database — what I store is an identifier for your account, and nothing more.

On your phone, the app keeps you signed in using the system's secure storage — the iOS keychain or its Android equivalent. That is not a cookie and it doesn't follow you around: it only saves you signing in every time.

What you create while playing

WhatWhich means
CampaignsName, description, cover image, invite code, who is in them
CharactersName, bio, attributes, traits, items, portrait
MessagesThe text you write in the chats, with its emotion and the character it belongs to
Dice rollsFormula, result, outcome. Dice are rolled on the server, so nobody can cheat
ImagesPictures you upload for campaigns and characters

All of it is tied to your account identifier, not to your name. The people in the same campaign can see it, and so can I if I have to act on a report or fix something that broke.

What isn't there

No advertising trackers, no behavioural profile, no location, no contacts. There aren't even usage statistics: right now I couldn't tell you which screen you look at most.

Why I process it

Who else sees it

Nobody I sell it to: only the providers I need to run the service, each for their own part.

WhoFor what
ClerkSign-in and account details
NeonThe database holding campaigns, characters and messages
ImageKitThe images you upload
Expo (EAS)Hosts the app's server side
CloudflareHosts this site
AppleTestFlight, to distribute the beta on iPhone

Where it lives

The database sits in a United States region (Virginia), and the other providers may process data outside the European Union too. Those transfers rely on the European Commission's standard contractual clauses, which are part of the agreements with these providers.

I'm telling you because it's true and it matters, not as a footnote: if you'd rather your data never left the EU, Fablepost isn't for you right now.

How long

As long as you keep the account. If you delete it, what follows below happens. Providers' backups roll over on their own within a few weeks.

If you delete your account

You do it from the app, in your profile. No need to write to me. The moment you do:

If you want those gone too, write to the address above and I'll remove them by hand.

Your rights

You can ask me to show you the data I hold about you, to correct it, to delete it, to hand you a copy in a readable format, or to restrict how it's used. You can also object to the processing based on legitimate interest.

Write to the address above: I answer within a month. If you think I'm getting it wrong, you can go to the Italian data protection authority, the Garante per la protezione dei dati personali (garanteprivacy.it), or to the authority in the country where you live.

Young players

Fablepost isn't meant for anyone under 16. If I find an account below that age, I delete it.

If something changes

I update this page and change the date at the top. If the change is one that actually matters — new data collected, new providers, analytics — I'll tell you inside the app before it happens, not after.