Privacy Policy
Last updated: November 15, 2026
RollCamp (“the App”, “the Service”, “we”) is a tool for creating Dungeons & Dragons characters and for running campaigns and live game sessions. This policy explains what personal data we process, why, who else gets to see it, and what you can ask us to do with it, in accordance with Regulation (EU) 2016/679 (“GDPR”).
In short: we process what an account needs, what you choose to create, and what the Service technically needs in order to run. We keep anonymous usage statistics on our own server, without cookies and without ever identifying you; we do not profile you, and we do not sell your data. Our ads are measured only if you want them to be: with a yes in the cookie banner, and never without one, a visit to a public page and the creation of your account reach Meta and TikTok (§2), and the yes is withdrawn with one click. Beyond that, only one thing leaves that perimeter, and it has a section of its own, written to be read before you create the account: voice transcription (§6), which goes to a United States provider that uses that audio to train its own models, with no possibility of opting out. You consent to it by registering the account, and it cannot be fully called back: that section says exactly how far we can go.
1. Who is responsible for your data
The data controller is Giuseppe Gioi, sole trader, Italian VAT number 01776480053, reachable at hello@rollcamp.com. No Data Protection Officer has been appointed: for anything concerning your data, write to that address.
2. What we process
Not everything below applies to everyone: what we hold depends on how you sign in and on what you create.
Account and profile
- Sign-up with email and password: your name, your email address, and your password stored only as a salted scrypt hash. We never see and never store passwords in readable form.
- Sign in with Google: your name, your email address and, where available, your profile picture. We don’t keep the tokens Google gives us when you sign in, and we never receive your Google password.
- Link Discord: if you link your Discord account from your Profile, we keep your Discord account’s id and your Discord username, which we update every time you link it. Discord only links your account: you can’t log in to RollCamp with Discord. We don’t keep the tokens Discord gives us, we never receive your Discord password, and we don’t take your Discord profile picture. We also keep whether your notifications on Discord are on, and since when, and whether the last message failed to arrive, with the reason when Discord gives one.
- Profile: the display name you are known by at the table and, if you upload one, a profile picture. Your username — your “RollCamp ID” in your Profile —, which we give you based on your display name and which you can change once every 30 days, and the ones you have left, while they stay reserved (§7). And, if you choose them, your bio, how you sit “At the table” — GM, player or both — and the languages you play in; until you choose your languages, we show your account’s language.
- Verification: whether your address has been confirmed, and the short-lived tokens used to verify it or to reset your password.
The content you create
- Characters: the sheet itself (class, species, background, ability scores, spells, equipment, coins, hit points), the portrait you upload, and any free text you write — appearance, personality, notes. If you turn on a sheet’s link, we also keep the code that opens it, until you turn it off.
- Campaigns: name, description, invite link, background image, the date of the next session, and the state of the game board.
- Membership: which campaigns you belong to, and with which role — Dungeon Master or player.
- Campaign chat: the messages and images you send in a campaign’s chat and the emoji reactions you add to them, with their date and your name, and when you last read it, which is how we point out new messages.
- Chat with friends: the messages you write to a friend and the emoji reactions you add to them, with their date and your name, and when you last read the conversation, which is how we point out new messages.
- Notifications: what the bell tells you. It can be a message in your campaigns’ chat, the table opening, a chapter being published, someone joining or leaving one of your campaigns, a campaign that its Game Master concludes, a comment or an upvote on something you wrote, the outcome of your request, offer or listing, someone booking a seat in your listing, a listing that opens and suits you, a Game Master calling you, how many players are waiting for a listing if you run a campaign with no players, replies still waiting for your decision when your listing is about to expire, your table closing by itself, a Compatibility Pack you unlocked that we withdraw, a friend request you receive or that is accepted, a post from RollCamp. For each one we keep who did it (except for upvotes, which stay anonymous), when, and whether you have read it. When a notification is about something that no longer exists, such as a deleted campaign, we keep its name. Notifications are not sent by email.
- Your creations: tactical maps and the tokens on them, homebrew monsters, NPCs.
- Campaign Archive: the images, soundtracks and documents you upload, together with the sharing choices attached to each of them.
- Notes and tags: the personal notes you write in the App and the labels you organise them with.
- Board: the posts and comments you publish, with the language you write them in and, when you reply to a comment, which one, the upvotes you cast on posts and comments, the posts you save, and the character or Compendium references you choose to link. Posts, comments, display name and profile picture are publicly visible. The author of a post or comment sees how many upvotes it has, never whose. If you delete a comment of yours that others have replied to, or close your account, “Comment deleted” stays in its place, with no text, name, picture or upvotes, so the replies don’t lose their thread; it goes entirely with the last reply. When you tag one of your characters, the post carries its shared sheet’s link while that is on; once it is off, the post shows only the name. Saves are visible only to you.
- Friends: the friend requests you send and receive, with who sends them, to whom, when, their status and when they were decided; and your friends. Only you see your Friends and your requests.
- Find a group: the listings you write — the title, the text, the language and whether beginners are welcome or you are one; for “Looking for players”, how many seats, the campaign you are looking for them from and when it plays; for “Looking for a group”, the days and times you can play (the afternoon or evening of each day of the week) with your device’s time zone, the shared sheet you choose to attach, when we last wrote to tell you about a listing that suits you and whether you have turned those emails off — and the bookings, requests and offers you send or receive, with their status. An open or completed “Looking for players” listing is publicly visible, with your display name and profile picture, and also shows the campaign’s name, subtitle, description and background, how many players it has and when it plays, but never its invite link. A “Looking for a group” listing isn’t public on RollCamp: only people signed in to RollCamp see it, with your display name, your profile picture and everything you wrote, so that a Game Master can offer you a seat or call you; people who aren’t signed in only see how many there are. Unless you have turned off “Publish listings” in your Profile, each of your listings also goes to the RollCamp Discord, with your display name and profile picture and, for a “Looking for a group”, the shared sheet you attached (§4): of its post we keep the reference and the status it shows, to keep it in step with the listing; if you have turned it off, we keep that choice. A booking is seen by the listing’s Game Master, with your display name and profile picture. A request or an offer is seen only by whoever sends it and whoever wrote the listing: the display name, the profile picture, the message and, if you attach it, the shared sheet. Nobody sees your email address. Whoever books a seat, or has a request or an offer accepted, becomes a member of the campaign, as with an invite.
- Reports: if you report a shared sheet, a post, a comment, a listing or a person’s profile, we keep what you reported (for a profile, also the username it had at that moment), the reason you write, the page’s language, the date and, if you leave them, your name and email address, which we use only to answer you. You don’t need an account, and the report is not tied to yours if you have one. We hold your IP address in memory for an hour, to stop anyone sending too many, and we never write it down. Reports are read only by administrators.
- Expansions and Packs: which Expansions and which Compatibility Packs you have unlocked, and when. It is how their content appears in your Compendium and among the choices of your characters and campaigns. If an Expansion’s author asks, we tell them only how many people have unlocked it, never who.
Preferences
Your 3D dice style and the language you chose for the interface.
Technical data
- A strictly necessary session cookie, which is what keeps you signed in.
- For every session we store its token and expiry, the IP address and the browser user agent it was opened from. This is how we keep sessions valid and how we spot abuse. Signing out deletes the record; an expired session no longer gives access, and its record goes with your account.
- The server logs that normal operation produces.
Usage statistics
We count page views with Umami, which runs on our own server: for each visit it records the page, where you arrived from and, if the address carries it, the campaign you came from (the utm parameters), your browser, operating system, device type, screen size and language, and roughly where you are connecting from — country, and the region and city your network is attributed to. It sets no cookies, it does not follow you across other websites, and none of it reaches a third party — the statistics never leave the machine that already runs the App. It also records a few actions without knowing who performs them: for example that an account was created, and which campaign the visit came from.
A returning visit is recognised only through a one-way hash that mixes your IP address and browser with a secret of ours that changes every month. The IP address itself is never stored, and once that secret rotates, older visits can no longer be tied to anyone at all.
Our ads, only with your yes
We advertise RollCamp on Instagram, Facebook and TikTok, and to know whether it works we tell Meta and TikTok who arrives on the site and who signs up. We tell them only if you consent in the cookie banner (§9), and it is our server that tells them: no Meta or TikTok script runs on the site. For a visit we send the page — only a public page, such as the Landing, the Compendium, the Blog, sign-in or sign-up, and of its address only a campaign’s parameters (utm) —, your IP address, your browser (the user agent), a random code this device keeps in a cookie and, if you arrive from one of their ads, the identifier of that click. About private pages — the Home, characters, campaigns, the live table, the editors — we say nothing.
When you create your account we also send the “account created” event, with the same data and a fingerprint of your email: a SHA-256 hash, which cannot be turned back into an address but which Meta and TikTok compare with the fingerprints of their own users, to recognise who signed up after seeing an ad. Meta and TikTok also use what they receive for their own purposes, including the ads they show you: their privacy policies say how.
Storage
For each file you upload we record its size and kind, which is how the gauge in your profile knows how much of your allowance you are using.
Live game sessions
- While a session is running we handle in real time presence and “ready” status, dice rolls, chat messages, pings and reactions, token movements, and the values that change during play: hit points, coins, spell slots, inventory. Two things out of that traffic remain: the character’s values, which are written onto their sheet — it is the sheet that changes, not an archive of the evening — and the notable facts, which become the campaign’s chronicle (below). The rest — presence, pings, token movements — simply passes through.
- Webcam and microphone go through a server of ours, which forwards them to the other participants (an SFU: each person sends their own stream once, and the server delivers it to everyone). It is our own machine, inside the European Union, and the streams are not stored. Until 24 August 2026 those streams travelled straight between the participants’ browsers; from that date they no longer do. Voice transcription is a different thing again and does not capture this stream but your own microphone inside your own browser: it is all in §6.
- For that server to forward anything, your IP address reaches it — no longer the other participants, as it did with a direct connection. The machine is ours and sits in the European Union; if a direct connection to it cannot be established, the traffic goes through a TURN relay, also ours. If you would rather avoid all of this, leave camera and microphone off: switched off, they publish nothing.
- The chat and the dice on screen are ephemeral: whoever joins later does not see what came before, and closing the room leaves nothing to reopen. What is written down from a game night are its notable facts, which make up the campaign’s chronicle: dice rolls with their label and result, chat messages, the start and end of a fight, tokens and maps brought into the scene, who went down, and the name of whoever did each of these. Token movements are not.
3. Why we process it, and on what legal basis
- Running the Service — your account, your saved characters and campaigns, the live table, Friends: performance of a contract (Art. 6(1)(b) GDPR).
- Sending transactional email — address verification, password reset and “Find a group” notices: when someone books a seat in your listing, when a request or an offer arrives, is still waiting for your decision as your listing is about to expire, is accepted, is declined or closes, and, if you have written a “Looking for a group” listing, when a listing that suits you opens (at most one email every three days, and each one turns them off in one click, without closing your listing) or when a Game Master calls you to theirs: performance of a contract and pre-contractual steps. At most once a month, if you run a campaign with no players and no open listing, we write to tell you how many players are waiting for a listing in your account’s language (and each one has a link to stop receiving them): legitimate interest (Art. 6(1)(f)) in bringing together the people who use the Service. Confirming a report to whoever sent it: legal obligation (Art. 16 of the Digital Services Act).
- Sending you on Discord, in a message from the RollCamp bot, the notifications from your Campaigns and “Find a group”, alongside the bell and the emails: performance of a contract (Art. 6(1)(b)), like the bell. They turn on when you link Discord, as the sentence at the top of the Discord card in your Profile says, and you turn them off whenever you like with “Notifications”. On Discord we never send you news or advertising.
- Publishing your “Find a group” listings on the RollCamp Discord too (§4): legitimate interest (Art. 6(1)(f)) in getting them found by more people. You can object whenever you like (Art. 21), even without linking Discord: turning off “Publish listings” in your Profile removes the posts of your open listings from there, and from then on we publish no more.
- Showing your public page to people with an account (§4), so that whoever plays with you, or meets you on the Board or in “Find a group”, knows who you are: legitimate interest (Art. 6(1)(f)) in letting the people who use the Service get to know each other. You can object whenever you like (Art. 21): your bio and “At the table” appear only if you fill them in, you can remove your languages, and for the rest write to us and we will look at your situation.
- Authentication, security, the storage allowance and abuse prevention, including stopping an account closed for a breach of the Terms from signing up again: legitimate interest (Art. 6(1)(f)) in keeping the Service working and available to everyone.
- Counting page views, to know which parts of the Service are used and which are not: legitimate interest (Art. 6(1)(f)) in improving it. The measurement is anonymous and sets no cookies, which is why it does not rest on consent — §2 says exactly what it records.
- Measuring our ads and showing them to people who already know RollCamp (§2): your consent (Art. 6(1)(a)), which you give or refuse in the cookie banner and withdraw whenever you like, without changing anything the Service offers you.
- Answering what you write to us, including requests about your own data: legitimate interest and legal obligation.
- Transcribing the voice during a game night and writing the Recap from it: consent (Art. 6(1)(a) GDPR), given when the account is registered, together with accepting the Terms. It is the only basis this rests on. See §6, which describes the processing in full.
We do not profile you, and no decision that affects you is taken by automated means. What Meta and TikTok do with the data they receive with your yes (§2) is up to them, and their own privacy policies say so.
4. Who else can see your content
RollCamp is a shared tool, so part of what you create is meant to be seen by other people. These are the rules:
- Besides you, your character sheets are read by the Dungeon Master of the campaign they belong to, who also sees the sheet’s Notes, and by the other players at that table, without the Notes or the counters.
- If you turn on a sheet’s link, anyone who has it can open it, without an account and without you knowing who: they see the card as it is at that moment, with your name, but not the Notes or the counters. The link can only be turned on for a sheet whose species, background, subclass, feats and spells all come from the SRD 5.2.1; if the sheet stops being so, the link stops opening it. Anyone with an account can also copy it to their characters, build, text and portrait included: that copy is theirs, and it stays even if you turn the link off or close your account. When the link lands in a chat, services like Discord or WhatsApp fetch its name, portrait and class to show a preview, and may keep them after you have turned it off: those copies are not ours to control. Once off, the link opens nothing, and a Board post that tags the sheet shows only its name; turned back on, a new one is created.
- Archive media uploaded by the Dungeon Master are shared as they decide: with the whole table, or only with the players they pick one by one.
- Your personal notes are always private. Nobody else sees them — not the other players, not the Dungeon Master — and the tags you file them under are yours alone.
- Maps, homebrew monsters and NPCs are the Dungeon Master’s material: players see them only once they are put in play.
- Messages in the campaign chat are read by every member of that campaign, including whoever joins after you wrote them. The Dungeon Master can delete them; you can edit and delete your own. Everyone in the campaign also sees who reacted to a message, and with which emoji.
- Messages in the chat with friends are read only by you and the friend you write to, and each of you can edit and delete your own. You can only write to someone who is your friend: if the friendship ends, the conversation stays readable for both of you, but no one can write in it anymore.
- When you do something that concerns other people, your name and profile picture appear in their notifications. That happens when you write in a campaign’s chat or to a friend, comment on a post or reply to a comment, join or leave a campaign, reply to a listing, book a seat or decide on a reply, send a friend request or accept one, call someone who is waiting to one of your listings. They go to the campaign’s members, the friend you write to, the author of the post or comment, the other side of the listing, whoever you called: people who can already see what you did, and whom the notification tells sooner. A friend request carries your name and picture to someone who may not know you yet: the person you send it to. Your upvotes, however, never carry your name to anyone.
- During a live session, what you write in chat, the dice you roll, and your camera and microphone if you switch them on are visible to everyone in the room.
- A game night’s Recap starts as the Dungeon Master’s private draft, which they can correct; once they publish it, the whole table of that campaign can read it.
- Your display name and profile picture are seen by the other members of the campaigns you join and, on your public page, by anyone with an account (below). If you link Discord, the members of your campaigns also see your Discord username, on the Campaign page; it never appears on “Find a group” cards or on your public page.
- You have a public page, at rollcamp.com/u/ followed by your username. Anyone with a RollCamp account can open it, including people you don’t know: they find your display name, your profile picture, your username, since when you have been on RollCamp, your bio, how you sit “At the table” and the languages you play in — your account’s language, until you choose them — and, gathered in one place, your Board posts and comments and your open “Find a group” listings. Your campaigns, characters, creations, saved posts and the replies to your listings never appear there. We ask search engines not to show it. People without an account can’t open it: to see it they have to sign in to RollCamp, and the preview of its link in chats is the site’s generic one.
- Your “Find a group” listings also go to the RollCamp Discord, which anyone can join, one post per listing, unless you have turned off “Publish listings” in your Profile. The post carries the text, the language and whether beginners are welcome or you are one; for “Looking for players” also the campaign’s name, background and free seats and when it plays, for “Looking for a group” the days and times you can play, with your time zone. It also carries your RollCamp display name and your profile picture, and for a “Looking for a group” the shared sheet you attached, if its link opens it: the character’s name, the portrait and the link to the sheet. If you have linked Discord, every post carries your Discord account, in both directions, so that whoever reads it can message you there too. Replies to a listing go through RollCamp only.
- The RollCamp bot’s commands on Discord keep nothing about whoever uses them. They answer in the channel where you use them, and whoever is there sees the answer, unless you choose to see it on your own. /lfg shows open listings, with “Looking for a group” listings carrying no name and no sheet. /character can only be used by people who have linked Discord, on their own characters, and shows only those whose species, background, subclass, feats and spells all come from the SRD 5.2.1: name, level, classes, species and portrait, and the link to the sheet only if you have turned it on. Asked for a character that isn’t, it tells only you that it isn’t shown.
5. Where your data lives, and who we share it with
The application and the database run on a virtual server operated by IONOS in the European Union. The database is not reachable from the internet, and its backups are kept in a separate, private storage bucket.
To provide the Service we also rely on the providers below. They process data on our instructions (processors), except where stated otherwise:
- IONOS — the servers that run the application, the database and the forwarding of live-session webcam and microphone (EU).
- Cloudflare (R2) — storing and delivering the files you upload.
- Resend — transactional email: address verification, password reset, “Find a group” notices and reports, to whoever sends them and to us. Established in the United States.
- Google — “Sign in with Google”, if you use it.
- Discord — “Link Discord”, if you use it; and the RollCamp bot, which posts “Find a group” listings and our news on the RollCamp Discord, answers commands wherever it is used on Discord, and sends you notifications on Discord, as long as you keep them on. For people living in the EEA the controller of data on Discord is Discord Netherlands BV; for everyone else it is Discord Inc., in the United States. What we publish on Discord is also processed by Discord, under its own rules: its terms and its privacy policy say how.
- Meta Platforms Ireland — the visits and sign-ups of §2, only with your yes. For collecting and sending that data we are joint controllers with Meta (Art. 26 GDPR, on the terms Meta sets for those who use its tools); for what it does with it afterwards Meta is the controller, and you can exercise your rights with Meta too.
- TikTok Technology Limited (Ireland) — the same visits and sign-ups, only with your yes, and with the same split: joint controllers for collecting and sending, TikTok the controller for what it does afterwards.
- Modulate — voice transcription during game nights. Established in the United States, where the audio is also stored, and it uses that audio to train its own models: it is all in §6, which is worth reading before you sign up.
- Anthropic — the language model that writes a game night’s Recap. Established in the United States; it receives the night’s facts and, where there is one, the Transcript, and does not use them to train its own models.
Some of these providers may process data outside the EU/EEA, for instance in the United States. Where that happens the transfer rests on the safeguards the GDPR allows — Standard Contractual Clauses or an adequacy decision — except for voice transcription, which rests on the consent given at registration and has a section of its own, §6. We do not sell your data, and for advertising we share only what §2 describes: only with Meta and TikTok, and only with your yes.
6. Your voice, and what we do with it
RollCamp transcribes what is said during a game night and turns it into a Recap, the story of how the evening went. Consent to this processing is given by registering an account, together with accepting the Terms: it is not asked a second time, and there is no switch that takes it away. This section tells you in full what happens to your voice, unpleasant parts included — it is written to be read before you create the account, because that is where the choice is made.
How it is captured
The recorder is your own browser, and only your own microphone: there is no central recorder collecting everybody’s voice. The control you keep follows from that, and it is a real one: with your microphone off you produce no audio at all — it is not filtered out afterwards, it is never produced. You can switch it off whenever you like, without asking anyone; the Dungeon Master can additionally pause recording for the whole table.
Who processes it, and where
The audio is sent to Modulate, Inc., which transcribes it on our behalf. Processing and storage take place in the United States: fragments of your voice leave the European Economic Area and remain on the provider’s systems, which it states keeps them for 35 days and then deletes them. The provider also states that audio may undergo automated analysis estimating the speaker’s age and gender: it is not something we ask for, nor is it returned to us, but it happens on its systems and it belongs here. For this transfer we hold no safeguards equivalent to the European ones: it rests on your explicit consent (Art. 49(1)(a) GDPR), given after being informed of that risk.
It is used to train the provider’s models
This is the part you need before you decide, so we write it out in full. On the plan we use, Modulate enrols its customers in its own model-improvement programme as a condition of using the platform: the audio we send and the text drawn from it also serve to train its speech-recognition systems, and opting out is not possible — there is no setting to switch off, not on your side and not on ours. We chose this provider knowing that, and telling you is the only thing we can put in place of a switch that does not exist. If that is not acceptable to you, the only way to withhold consent is not to create the account: it is part of registration, and there is no box to leave unticked. If you already have an account, what remains in your hands is the microphone — switched off it produces no fragment at all, and that is a real control because the recording is done by your own browser — and closing the account.
The Transcript lasts only as long as it is needed
The Transcript — the text of what was said — exists only for as long as it takes to write that night’s Recap, and is then deleted. While it exists it is readable by nobody, the Dungeon Master included: it is not the record of the evening, it is the scaffolding used to build one. The audio, for its part, never enters our storage and is discarded as soon as it has been transcribed.
The Recap, by contrast, stays
The Recap is drawn from the facts the night produces on its own — dice rolls, chat messages, tokens brought into the scene — and, where there is one, from the Transcript. It is written by a language model from Anthropic (United States), which receives that material in order to generate it and does not use it to train its own models. It starts as the Dungeon Master’s private draft, which they can correct and choose to publish to the table; from then on it is part of the campaign’s chronicle, and it lives as long as the campaign does.
What you can stop, and what does not come back
There is no per-person withdrawal: consent is part of registering the account, and the only way to take it back entirely is to close the account. What you can stop at any time, without asking anyone, is your microphone: switched off it produces nothing, and it is a real control because the recorder is your own browser. Two things do not come back either way: Recaps already written stay — they are the campaign’s shared story and they concern the other people at the table too — and audio already sent to Modulate has already entered its training and cannot be recalled.
7. How long we keep it
- Account and content: for as long as your account exists.
- Usernames: when you change your username, the previous one stays reserved for you for 30 days: only you can take it back, and its link leads to your page. Then it is released. If you close your account, your username stays taken for 30 days, no longer leading to you, and is then released. A username we remove after a report (§9 of the Terms), instead, goes into a list of banned names, with no link to the account that had it, and stays there: nobody can take it again.
- Sessions: a session record lasts until you sign out; once expired it gives no access, and it is deleted with your account. Verification and password-reset tokens expire within hours.
- Live sessions: video and audio do not become an archive of the evening: our server forwards them and does not keep them. What does remain are a game night’s notable facts — dice rolls, chat messages, the start and end of fights, tokens and maps brought into the scene, who went down, with the name of whoever did each of them — because they are the campaign’s chronicle: they live as long as the campaign, and go with it.
- Voice, Transcript and Recap: the audio never enters our storage and is discarded as soon as it has been transcribed; the Transcript is deleted as soon as the Recap is written. The Recap stays for as long as the campaign does. On its own side the provider states that it keeps the audio for 35 days — see §6, which also covers what it does with it in the meantime.
- Reports: for as long as what was reported exists — the sheet, the post, the comment, the listing or the account of the reported profile —; they go with it. The email that reaches us with the report stays in our inbox, because that is where we write the decision to the reporter and the statement of reasons to the author.
- Campaign chat: unlike the live table’s chat, messages stay until you or the Dungeon Master delete them, for as long as the campaign exists, or until you close your account, which takes them with it.
- Chat with friends: messages stay until whoever wrote them deletes them, or until one of you closes their account, which takes the whole conversation with it.
- Notifications: a read notification stays for 30 days, an unread one for 90. It goes sooner if what it is about goes, such as a deleted post or comment. When you close your account, your notifications go, and your name leaves everyone else’s.
- Friends: a friendship stays until one of you removes it or closes their account. A friend request stays until you accept or decline it, or its sender cancels it; a declined one stays until the person who declined it sends a request themselves, or one of you closes their account.
- “Find a group” listings: until you delete them, or we remove them after a report. A closed or expired listing leaves the list but stays with you; a completed one (one that found what it was looking for) stays in the list until it expires, among the recently completed; a “Looking for a group” listing completes itself when you book a seat or accept an offer. Bookings, requests and offers live as long as their listing, and everything goes with the account.
- Discord: your Discord account’s id and your username stay until you unlink Discord — with “Unlink” in your Profile, or by removing RollCamp from your Discord account’s authorised apps, which unlinks it here too — or until you close your account. Unlinking turns off notifications on Discord, and rewrites the posts of your still-open listings without your Discord account. A post on the RollCamp Discord follows its listing: if the listing is completed, closed or expires, the post stays there, closed and showing its status; if the listing goes, including because you close your account, the post goes with it. If you turn off “Publish listings” in your Profile, the posts of your open listings go; those already finished stay closed until you delete the listing.
- Ads: your choice in the banner lasts six months, then we ask again; the device code and the identifier of a click on a Meta ad stay 90 days, a TikTok one 30, and with a “no” they go at once. We keep no copy of the events we send; how long Meta and TikTok keep them, their privacy policies say.
- Accounts closed for a breach of the Terms: we keep the email address they were registered with, and one line on why, to stop them signing up again (§13 of the Terms). Nothing else from that account is kept. The address stays as long as the closure stands: if you ask us to review it and we lift it, it goes with it.
- Backups: database copies rotate and are overwritten, so what you delete from the live database also leaves the backups within the rotation window.
When you delete your account, everything attached to it goes with it and the files you uploaded are removed from storage. The copies others have made of your shared sheets don’t go: they are theirs, as §4 says. One thing is a real exception, and we say so here rather than let you find out: Recaps already published stay, because they are the campaign’s shared chronicle. Read the Terms of Service first: deleting your account also deletes the campaigns you own, and their other members lose access to them.
8. Your rights
You have the right to access your data, to rectify it, to erase it (“right to be forgotten”), to restrict its processing, to object to processing based on legitimate interest, and to receive your data in a portable format. You can withdraw your consent to ads whenever you like from “Cookie preferences”, at the bottom of every page: from then on nothing more is sent, what was sent before stays lawful, and for that you can also turn to Meta and TikTok (§5).
Some of these you exercise yourself, without asking us: from your profile you can change your name, username (your “RollCamp ID”), picture and password, write or clear your bio, “At the table” and the languages you play in, and you can delete your account together with everything attached to it.
For anything else, write to hello@rollcamp.com: we reply within one month. You also have the right to lodge a complaint with a supervisory authority — in Italy, the Garante per la protezione dei dati personali.
9. Cookies
The strictly necessary cookies are always there: the one that keeps you signed in, the one that remembers the language you picked and the one that remembers your choice about ads. The usage statistics of §2 set none. The others — the device code and the identifier of a click on a Meta or TikTok ad — we set only if you say yes in the banner, which appears on public pages with “Reject” and “Accept” on equal terms: closing it with the × counts as “Reject”, and browsing on counts as nothing. You reopen it from “Cookie preferences”, at the bottom of every page, whenever you want to change your mind. They are our own cookies: Meta and TikTok set none on the site, and they receive their values only from our server, as §2 says. One thing sits outside our doors: a Blog Article may embed a YouTube video, and nothing at all is requested from YouTube until you press play — from that moment on, YouTube may set its own cookies, which we neither read nor control.
Your browser also keeps a few interface preferences locally; they never leave your device.
10. Security
We take reasonable technical and organisational measures: passwords stored as a salted scrypt hash, encrypted connections (HTTPS), a database unreachable from the internet, real-time access authorised by short-lived signed tokens, permission checks on every operation, and regular backups.
No system is completely secure and we cannot promise otherwise. Should a breach occur that is likely to result in a high risk to your rights, we will tell you, as Art. 34 GDPR requires.
11. Children
The Service is not intended for anyone under 16, and you must be 16 to sign up: the Terms say so, and whoever signs up confirms it. We don’t ask for your date of birth. If we learn that an account belongs to someone under 16, we close it and delete its data, without keeping its email address: at 16 you can sign up.
12. Changes to this policy
We may update this policy as the Service grows. The date at the top of the page always tells you which version you are reading; if a change materially affects how we use your data, we will tell you by email or with a notice in the App.
13. Contact
For anything about your privacy — a request, a doubt, a complaint — write to hello@rollcamp.com. See also our Terms of Service.