Drunken Seer Privacy Policy
Last updated: 29 October 2026 · Effective from: 29 October 2026
This policy explains how we use personal data when you visit Drunken Seer, use an account, subscribe or contact us.
At a glance:
- We use your account details and campaign content to provide Drunken Seer.
- Paddle handles subscriptions and payments. We do not receive your full card details.
- Account-linked analytics is optional. Limited visit measurement currently continues after you decline; section 4 explains this.
- We do not sell personal data or use your campaigns for advertising or to train AI models.
- You can delete your account in your account settings and contact us to exercise your privacy rights.
1. Who is responsible
The controller is André Kleinhaus, trading as Petite Maison, operator of Drunken Seer:
c/o IP-Management (974672634)
Ludwig-Erhard-Str. 18
20459 Hamburg, Germany
Email: support@contact.drunkenseer.com
You can also contact us through Feedback & Support in the app, or with the contact form in our Legal notice.
2. What we use and why
We collect data from you, automatically when you use the website, and from Paddle when it sends subscription updates.
| Purpose | Data used | Legal basis |
|---|---|---|
| PurposeCreate and run your account | Data usedEmail address, password hash, internal account ID, role and registration date; sign-in sessions and password-reset details | Legal basisContract |
| PurposeSave and display your campaigns | Data usedMaps, uploaded images, characters, tables, notes and other content you create | Legal basisContract for your own data; legitimate interests for other people's information you write down (section 3) |
| PurposeManage your subscription | Data usedEmail address, account ID, Paddle customer and subscription IDs, plan, subscription status, renewal date and scheduled changes received from Paddle; temporary billing-verification codes | Legal basisContract; legitimate interests in preventing unauthorised billing access |
| PurposeAnswer support requests | Data usedEmail address, account reference, message, attachment names, replies and dates | Legal basisContract for account support or steps you request before subscribing; legitimate interests in answering other enquiries |
| PurposeDeliver and secure the website | Data usedIP address, browser information, requested page, time, response status and short-lived abuse-prevention counters | Legal basisLegitimate interests in operating the service and preventing abuse |
| PurposeFind and fix faults | Data usedError details, page address without its query string, browser, operating system, app version and approximate location; relevant internal IDs for billing or deletion faults | Legal basisLegitimate interests in maintaining a working service |
| PurposeShow local prices | Data usedCountry derived from your IP address; connection details received by Paddle's price script | Legal basisLegitimate interests in displaying local prices (section 5) |
| PurposeUnderstand how the service is used | Data usedPage visits, interactions, technical and referral information; with consent, a browser identifier and your internal account ID | Legal basisConsent for account-linked analytics; the separate limited measurement after refusal is described in section 4 |
“Contract” means Article 6(1)(b) GDPR. “Legitimate interests” means Article 6(1)(f); the interests are identified above. “Consent” means Article 6(1)(a). Where disclosure or retention is required by law, we rely on Article 6(1)(c).
An email address and password are required to create an account. Without subscription information, we cannot provide paid access. Campaign content, support messages and consent to account-linked analytics are optional.
We store passwords as hashes. To check for breached passwords, our server sends only the first five characters of a password hash to Have I Been Pwned, operated in Australia. It does not receive your password, full hash or email address.
Sentry receives the connection's IP address when an error report is sent and derives an approximate location. It is configured not to retain the address.
3. Your campaigns
Your campaigns are not published or shared with other users. Authorised staff may access content when needed to help you, investigate a fault or address misuse. Our hosting and database providers process it to deliver the service.
Uploaded map images can be opened by anyone who has their URL, without signing in. The URLs contain a long random element, but the images are not protected by account authentication. Cached copies may remain briefly after deletion.
Use only the personal information your game needs. Avoid sensitive information about real people, such as health details or religious beliefs. If someone else's information appears in a campaign and they contact us, we handle their request while protecting other people's rights and privacy.
If you write about other people in a campaign, such as your players, we store that information for you as part of the service. We are responsible for it as controller and rely on legitimate interests (Article 6(1)(f) GDPR): yours and ours in letting you prepare and run your games with the notes you choose to keep. It stays private to your account, is used only as this section describes, and is deleted with the campaign or your account (section 7). Because we normally cannot know or reach the people mentioned, we inform them through this policy (Article 14(5)(b) GDPR).
4. Usage statistics and your choice
We use PostHog to understand which pages and features people use, how they find Drunken Seer and where performance needs improving. No analytics events are sent before you answer the consent card.
If you accept, PostHog receives page visits, public-page button and link interactions, click positions, scrolling and loading times. It also receives browser, operating system, device and screen information, language, time zone, referral information and campaign tags from incoming links. Page addresses are stripped of query strings and internal IDs. A random identifier is stored in your browser. When you sign in, this data is linked to your internal account ID.
We filter analytics to exclude email addresses and campaign content. We do not record screens or keystrokes, or capture button and link interactions inside campaigns. Raw IP addresses are not retained in our analytics events.
If you decline, your browser still sends page visits, public-page button and link interactions, browser and device information, and referral information to PostHog. PostHog uses the connection's IP address and browser information to generate a daily identifier. This mode uses no analytics storage on your device, is not linked to your account and does not retain your raw IP address. It remains a form of visit measurement.
You can change your choice through Cookie settings in the website footer. The current Realm view has no footer; open another page to access it. Withdrawing consent stops future account-linked analytics and removes its browser identifiers. It does not affect processing that was lawful before withdrawal. Under the current configuration, limited visit measurement continues after withdrawal, as described above.
We disable both modes when your browser sends Global Privacy Control or Do Not Track. Declining account-linked analytics does not limit the app's features.
5. Cookies, browser storage and payments
We use cookies for sign-in and security, returning you to the right page after sign-in, and remembering a dismissed subscription notice.
| Storage | Purpose | Lifetime |
|---|---|---|
| StorageSign-in cookie | PurposeKeep you signed in | LifetimeUp to 30 days |
| StorageSign-in security and return-page cookies | PurposeProtect sign-in and remember where to return you | LifetimeBrowser session |
| StorageSubscription-notice cookie | PurposeRemember that you dismissed a notice | Lifetime2 days |
| StorageLocal browser storage | PurposeRemember workspace settings, searches, recent rolls, colours and your analytics choice | LifetimeUntil cleared in your browser |
| StoragePostHog local and session storage, after consent | PurposeRecognise visits for account-linked analytics | LifetimeUntil withdrawal or clearing site data; session storage also ends with the browser session |
Storage strictly necessary to provide a function you request is used under § 25(2)(2) TDDDG. Optional analytics storage and access require consent under § 25(1) TDDDG. Clearing site data removes local settings and may cause us to ask for your choice again.
Paddle sells the subscription and handles checkout, payments, invoices, tax and refunds as an independent controller. When you start checkout, we send your email address and account ID so your purchase can be connected to your account. Paddle returns the subscription information listed in section 2. Changing your account email also updates the email held by Paddle.
Paddle's price script also loads on the landing, pricing and registration pages, before checkout. This gives Paddle your IP address and browser information; we also send your country code. Paddle may use its own cookies or similar technologies. Its privacy notice explains its processing, international transfers and retention. The Paddle seller is identified at checkout.
6. Who receives data and where
We use the following providers for the purposes shown. Providers processing on our instructions must be covered by data processing agreements. Paddle processes payment data independently.
| Provider | Service | Location and transfer arrangement |
|---|---|---|
| ProviderVercel Inc. | ServiceWebsite hosting, request logs and uploaded map images | Location and transfer arrangementUS company; our server functions run in Dublin, Ireland, with worldwide delivery of pages and images. EU–US Data Privacy Framework (DPF) |
| ProviderTurso / ChiselStrike Inc. | ServiceDatabase for accounts, campaigns, support and subscription records | Location and transfer arrangementUS company; our database is stored in Ireland. Standard contractual clauses (SCCs) |
| ProviderUpstash Inc. | ServiceAbuse-prevention counters with pseudonymous identifiers | Location and transfer arrangementUS company; our database is stored in Frankfurt, Germany. DPF |
| ProviderResend Inc. | ServiceSending and receiving service emails | Location and transfer arrangementUS processing and storage. An EU sending region controls routing, not storage location. SCCs and DPF |
| ProviderFunctional Software, Inc. (Sentry) | ServiceFiltered error reports | Location and transfer arrangementUS company; our selected EU storage region is Germany. DPF |
| ProviderPostHog, Inc. | ServiceUsage statistics | Location and transfer arrangementUS company; our selected EU storage region is Frankfurt, Germany. SCCs |
| ProviderPaddle | ServiceSubscription sales and payment administration | Location and transfer arrangementRelevant entities in the UK, Ireland, US or Canada; see Paddle's notice above |
An EU storage region does not rule out access or processing elsewhere. Transfers covered by an applicable European Commission adequacy decision rely on Article 45 GDPR. This includes the UK and US recipients covered by the DPF. Where SCCs are used, they provide safeguards under Article 46 GDPR, with additional measures where necessary. Contact us for a copy or details of applicable safeguards.
Authorised staff access data as needed for their duties. We may disclose relevant data to authorities or professional advisers where required by law or necessary for legal claims. We do not sell personal data or share it for advertising.
7. How long we keep data
| Data | Retention |
|---|---|
| DataAccount and campaign data, including our subscription records | RetentionUntil you delete the relevant content or account; expiry or cancellation of a subscription does not itself delete campaigns |
| DataPassword-reset tokens | RetentionValid for 1 hour; deleted when used or replaced, and at the latest with the account |
| DataBilling-verification codes | RetentionValid for 15 minutes; deleted when used or replaced, and at the latest with the account |
| DataAbuse-prevention counters | RetentionUp to 2 hours |
| DataHosting and request logs | RetentionUp to 1 day |
| DataSentry error reports | Retention30 days |
| DataPostHog usage statistics | Retention1 year; we also request deletion of data linked to an account when that account is deleted |
| DataEmail and delivery logs at Resend | Retention30 days in normal operation; Resend's separate backup retention is 7 days |
| DataSupport conversations | Retention1 year after the last message in the conversation, or earlier when you delete your account or we delete the conversation |
| DataRecovery backups | RetentionUp to 30 days |
Deleting an account removes its account and campaign data from the live service. Backup copies, error reports and email copies follow the separate limits above. PostHog event deletion is processed separately and is not necessarily immediate. Copies of images in delivery caches may also take time to expire.
We retain specific records for longer only where a legal obligation or an identified legal claim requires it, and restrict their use accordingly. Paddle retains its own billing records under its legal obligations after a Drunken Seer account is deleted.
8. Your rights
Subject to the GDPR's conditions, you can request access to and a copy of your personal data, correction, deletion, restriction of processing and portability of data you provided in a commonly used, machine-readable format.
You can object to processing based on legitimate interests for reasons relating to your particular situation. We will stop that processing unless we demonstrate compelling overriding grounds or need it for legal claims. You can withdraw analytics consent at any time as described in section 4.
Contact support@contact.drunkenseer.com or use Feedback & Support. Requests are normally free. We respond without undue delay and within one month. If the GDPR allows an extension, we explain why within that month. We may ask for proportionate information to confirm your identity where necessary.
You can complain to a data protection authority, including in the country where you live or work, or where you believe an infringement occurred. You do not have to contact us first. Our supervisory authority is the Berlin Commissioner for Data Protection and Freedom of Information (Berliner Beauftragte für Datenschutz und Informationsfreiheit), Alt-Moabit 59–61, 10555 Berlin, Germany: contact and complaint options.
We do not use personal data for solely automated decisions producing legal or similarly significant effects about you.
9. Security, age limits and updates
We use HTTPS, hashed passwords and restricted administrative access to protect data. Access to campaigns is checked against the account requesting them; uploaded image URLs have the separate limitation explained in section 3.
Drunken Seer is intended for people aged 16 and over. Contact us if you believe a child under 16 has an account so we can investigate and remove it.
We update this policy when our processing changes and show the revision date above. We inform you in advance of material changes to how we use your data and obtain consent where required.