Privacy notice

Version: 2026-11-15Plain text

The operator's contact details and the imprint will be published here before paid plans go on sale. Until then no plan can be bought.

What Verity stores about whom, why, for how long, and what rights you have. In short: no ads, no tracking, no analytics cookies, no stored IP addresses.

1. Who is responsible

Responsible for this website, the dashboard, billing and requests to us is the operator of Verity (name and postal address: see the imprint), reachable through the contact details in the imprint. We are not required to appoint a data protection officer.

For the data of a Discord server's members (entries, answers, checks) the server's team that uses Verity there is responsible. It decides which giveaways run, which questions are asked and when data is deleted. We process this data only on its behalf (data processing agreement, Art. 28 GDPR). Please ask the server's team first; we pass on requests that reach us.

2. Visiting the website

The home page and these legal texts set no cookies and load nothing from other servers (not even fonts). To deliver the page, our hosting provider technically processes your IP address and the requested address for the duration of the connection. We do not store IP addresses; our logs contain time, path, status code and duration of a request so we can find errors, and are overwritten by size. To slow down attacks, the sign-in and the cancel and withdraw forms count requests per IP address in memory for a few minutes; this is not stored. The legal basis is Art. 6(1)(f) GDPR (secure, working operation).

Hosting: our hosting provider in the EU (named here before the first sale). All pages are reached through Cloudflare's network (Cloudflare, Inc., USA; forwarding and protection against attacks), which processes your IP address and the request for this as our processor; Cloudflare is certified under the EU-US Data Privacy Framework.

3. Signing in to the dashboard

You sign in with Discord (OAuth2, scopes “identify” and “guilds”). We receive your Discord ID, your name, your avatar identifier and the list of your servers with your permissions there. This decides which servers you may manage. We never see your Discord password.

CookiePurposeLifetime
__Host-gp_oauthProtects the sign-in (random value)10 minutes
__Host-gp_sessionKeeps you signed in (random value, no data in the cookie)2 hours or until you sign out

Both cookies are strictly necessary for the service you asked for (§ 25(2) no. 2 TDDDG) and need no consent. The session is kept in memory only; when it ends it is gone. Legal basis: Art. 6(1)(b) GDPR.

In the dashboard your browser loads avatars and server icons directly from Discord (cdn.discordapp.com). Discord receives your IP address and learns from the image address which image is loaded. This is the only request to another server in the dashboard; the legal basis is Art. 6(1)(f) GDPR (showing your servers the way you know them).

What you change in the dashboard is recorded with your Discord ID and the time in the server's history (audit log), so the team can see who did what. Legal basis: Art. 6(1)(f) GDPR. The history is kept with the server's data until the server's data is deleted.

4. Data of a server's members

We process this data on behalf of the server's team (see section 1). Depending on the team's settings:

DataWhat forHow long
Discord ID, name at the time of entering, avatar identifier (not the picture), date of joining the server, time and weight of the entryEntering, rules (e.g. minimum time in the server), fair draw, hints at alt accounts (same picture)Until the team deletes them; name and avatar identifier are cleared when a member is erased
Answers to the team's questions (optional; depending on the setting stored encrypted, only as a keyed match value, or not at all)What the team asks, e.g. a payout addressUntil the team deletes them
Network code of the human check (keyed hash of the network, not the IP address itself) and whether the network is on a VPN/proxy listSpotting one person verifying many accounts; only a hint for the team, never an automatic decisionDeleted automatically after the period set by the operator (default 90 days, at most 180), earlier on request
Link between two accounts that verified from the same network (two Discord IDs, kind, time)Hint at alt accounts for the teamUntil either member is erased
Check status (Discord ID, time, which check)Give the “verified” role, no need to repeat the checkUntil the team erases the member; interim states after one day
Exclusion list (Discord ID, note, who, when)Leave members out of draws; excluded entrants are named in the public proofUntil the team removes the entry
Public proof of a draw (Discord IDs and names of entrants and winners)Anyone can check that the draw was fairWith the giveaway
Support tickets, if the server uses them: who opened and closed the ticket, when, and the messages in the ticket channel (author, time, text encrypted, number of attachments)The team can read requests again later in the dashboard; every read is recorded in the historyAutomatically 30 days after the last message in the ticket (the team can set 7 to 90 days), earlier when the team deletes the ticket

We read and store messages only in ticket channels; the first message there says what is stored. Pictures and files from tickets are not stored. The bot reads no other message on the server. We store no IP addresses and no device fingerprints. The network code is made on the check page with a secret key that is kept only there and replaced every 30 days; the database alone cannot turn it back into an address. Whether an address belongs to a VPN is checked by the check page on our own server against public lists; the address is sent to nobody for this.

The server's team chooses the legal basis; usually it is its legitimate interest in fair giveaways without alt accounts (Art. 6(1)(f) GDPR). When the bot is removed all processing stops; the data stays for a new invitation and is deleted when the team asks for it.

5. Human check with Cloudflare Turnstile

If a server chooses the captcha, the check page uses Cloudflare Turnstile (Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA). Your browser loads a script from Cloudflare for this; Cloudflare receives your IP address and technical features of the browser to detect automated access and partly processes them as a controller of its own. We only receive “passed” or “failed”. The legal basis is Art. 6(1)(f) GDPR (protection against bots); reading the browser is strictly necessary for the check you asked for (§ 25(2) no. 2 TDDDG). Cloudflare is certified under the EU-US Data Privacy Framework (Art. 45 GDPR). More: Cloudflare privacy policy.

The check page itself sets no cookies. The link to the check is single-use and expires after 15 minutes.

6. Buying a plan

Payment is made through Stripe (Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Dublin 2, Ireland). You enter payment details directly with Stripe; we do not see them. Stripe is itself responsible for processing payments, fraud checks and legal duties; data may go to Stripe, Inc. in the USA (EU-US Data Privacy Framework, standard contractual clauses). More: Stripe privacy policy.

For the subscription we store: the Stripe customer ID, the buyer's Discord ID, the server, plan, term and payment status. Your email address and your confirmation of the immediate start are kept with the subscription at Stripe; we also store the buyer's Discord ID and the server ID there, so payment and plan match. After the payment Stripe gives us your email address so we can send you the contract confirmation (§ 312f BGB); we do not store it in our database. If a plan is bought through Discord, Discord handles the payment as a controller of its own; we only learn that the server has a plan and until when. Legal bases: Art. 6(1)(b) GDPR (contract) and (c) (retention duties). We keep accounting records and invoices for 8 years, books for 10 years and business letters for 6 years (§ 147 AO, § 257 HGB); then they are deleted.

7. Cancellation, withdrawal and emails

When you make a declaration with “Cancel contracts here” or “Withdraw from contract”, we store name, email address, server ID, kind of declaration, any reason and desired date, and the time of receipt, match them with the subscription and send you a confirmation. Legal bases: Art. 6(1)(c) GDPR for processing and confirming (§§ 312k, 356a BGB), (f) for keeping it as proof. We keep the declaration for three years from the end of the year (limitation, § 195 BGB).

We send emails (confirmations, notes about the subscription) through our email provider (named here before the first sale). If you write to us, we use your details only to answer (Art. 6(1)(b) or (f) GDPR) and delete them once the matter is closed and no retention duty applies.

8. Recipients and third countries

  • Hosting: our hosting provider in the EU (named here before the first sale) (processor)
  • Email delivery: our email provider (named here before the first sale) (processor)
  • Stripe (payments, controller of its own)
  • Cloudflare (network and forwarding: processor; captcha: partly controller of its own)
  • Discord Inc., USA: the bot works through Discord and the dashboard loads images from Discord; what you do on Discord is governed by Discord's own privacy policy.

We do not sell data or pass it on for advertising. Authorities receive data only where we are legally required to provide it.

9. Your rights

You have the right of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and to object to processing based on legitimate interests (Art. 21 GDPR). Write to us through the contact details in the imprint. For a server's data, please contact its team; it can find and delete your answers and data in the dashboard.

Right to object (Art. 21 GDPR): where we process data based on legitimate interests (Art. 6(1)(f) GDPR), you can object at any time on grounds relating to your particular situation. We then stop processing the data unless we demonstrate compelling legitimate grounds or the processing serves the establishment, exercise or defence of legal claims.

You can complain to a data protection supervisory authority, e.g. the one where you live or the one responsible for us.

There is no automated decision with legal effect (Art. 22 GDPR): the draw is chance under fixed rules, and hints at alt accounts are only hints for humans.

Providing data is not required by law or contract. Without signing in with Discord you cannot use the dashboard, and without entering you cannot win.

10. Security and changes

Connections are encrypted (HTTPS). Each server's data is separated in the database (row-level security), readable answers are stored encrypted, internal services talk only with signed requests, and the pages load no third-party scripts (except Turnstile on the check page).

If the processing changes, we update this notice. The date at the top of the page shows the version.