Privacy

1. Who looks after the data

Each group's data belongs to the group. Under Brazil's General Data Protection Law (LGPD), the innkeeper who contracts the Tavern (the group's admin, usually the game master, or GM) is the controller: they decide who comes in and what gets published. The Tavern is the processor: it stores and handles the data on the group's behalf, only to make the service work.

For requests and questions, talk to your group's innkeeper or write to tavernadodragaodourado@gmail.com.

2. This site

This presentation site uses no cookies, analytics or trackers, and loads no third-party scripts. Fonts and images come from the site itself.

The site is hosted on Vercel, which logs technical data for each visit, such as the IP address, for security and operation. Contact is by email: the site has no form and doesn't keep what you write.

The Journal (the news page) shows the title, the opening of the text, the publisher's name and the link of public posts from each RPG system's official blogs and channels. The author's name appears only as credit, the way the source itself publishes it. The Journal collects no data from its readers.

When you open a video's details in the Journal, the thumbnail comes from YouTube (i.ytimg.com), which receives your browser's IP address, as with any image on the internet. Journal links take you to the publisher's site, which has its own privacy policy. Anyone who publishes on one of these sources and would rather be left out can ask for removal at tavernadodragaodourado@gmail.com.

3. What the app keeps

From your account: name, login, email and, if you want, phone number; the password, stored only as an Argon2id hash; remembered devices and open sessions, stored only as hashes.

From what you do: your answers to session calls and polls, your bet tokens, what you write on the Board, in the Chat, in letters and comments, the images you send in the Chat, your Bookshelf bookmarks and the seat you took at the Table.

And technical records: the notices sent (so nothing goes out twice) and error and access logs, so the tavern works and stays safe.

4. What the app doesn't keep

Voice and video from the Table are never recorded and don't go through the tavern's server. There are no push notifications on the phone, so no device is subscribed to receive notices.

There are no ads, we don't sell or rent data, we don't build advertising profiles and we don't use the group's content to train artificial intelligence.

5. The services the tavern uses

To work, the Tavern uses these services, which receive only what their part needs:

• Vercel: hosts the app and the API, in the São Paulo region (gru1). Vercel Blob stores the Chat images and the copies of the Bookshelf PDFs.
• Neon: the database, in the São Paulo region (sa-east-1).
• Cloudflare: Workers and a Durable Object relay real-time events (a new message, a new vote) without storing their content; Cloudflare Realtime (SFU and TURN) carries the Table's voice, video and screen between browsers, without recording.
• Google: emails go out through the group account's Gmail. With the group's Google account connected, the tavern creates and updates session events in Google Calendar (calendar.events permission) and reads, read-only, the Google Drive folder the innkeeper shared for the Bookshelf.
• Discord: the group's channel gets notices through a webhook, with generic texts and a link; never names, emails or the text written by the GM.
• Upstash QStash: schedules the time of notices (vote reminders, for example).
• GitHub: GitHub Actions runs the code tests and makes a weekly encrypted backup of the database.

Some of these services are outside Brazil. In those cases the transfer follows the safeguards they offer, such as data protection contractual clauses, as the LGPD requires.

6. Google data

The Tavern doesn't read other events, emails, contacts or files outside the shared folder. Access to the Google account is stored encrypted (AES-256-GCM) and can be turned off at any time in the tavern's Settings or at myaccount.google.com/permissions.

The use of data received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.

7. For how long

The sign-in code sent by email lasts 10 minutes. A session lasts 30 days and renews while you use it. Chat images are kept for 30 days. In-app notifications (the bell) disappear after 60 days. A seat at the Table is freed after 6 idle hours.

Other data stays while the account exists. When someone leaves the group, the account and what's linked to it are deleted; when the group ends the service, the group's data is deleted.

8. How we protect it

Everything travels encrypted (https). Passwords are stored with Argon2id and sessions only as hashes. Google access is encrypted with AES-256-GCM. What is secret (a sealed handout, a reply to a letter, the innkeeper's shelf) doesn't even leave the server for those who can't see it.

9. Your rights

Under the LGPD, you may ask for: confirmation that we process your data, access to it, correction, anonymization or deletion of what is unnecessary, portability, information about whom we share it with and deletion of the data, and you may withdraw consent.

Ask your group's innkeeper or write to tavernadodragaodourado@gmail.com. We answer within 15 days.

10. Changes to this policy

If this policy changes, the date at the top changes and each group's innkeeper is notified.