Data processing agreement

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.

Between the team that uses Verity on a Discord server (controller, “customer”) and the operator of Verity (name and postal address: see the imprint) (processor, “we”). The agreement applies once Verity is used on a server and supplements the terms.

1. Subject and duration

We process personal data of the server's members to run giveaways for the customer, check entrants, draw winners, publish proofs and provide the server management tools. The agreement runs as long as Verity is used on the server or data of the server is stored.

2. Types of data and data subjects

Data subjects: members of the server who enter giveaways or take the check, and team members.

  • Discord IDs, names, avatar identifiers, date of joining the server
  • Entries, weights, draw results, exclusions
  • Answers to questions the customer defines
  • Check results, network codes (keyed hashes), links between accounts
  • History of changes by the team (audit log)

The customer does not ask for passwords, recovery phrases, private keys, access codes, card data or special categories of data (Art. 9 GDPR). The software reminds the customer of this when a question is added.

3. Instructions

We process the data only on the customer's documented instructions, including for transfers to third countries, unless the law requires us to process it; then we say so beforehand where the law allows. Instructions are the settings and actions in the dashboard and through bot commands (e.g. creating questions, deleting answers or members) and instructions in text form to our email address.

If we think an instruction is unlawful, we say so without delay and may suspend it until it is clarified.

4. Customer's duties

The customer is responsible for the lawfulness of the processing, chooses the legal basis, informs the members (Art. 13 GDPR, e.g. in the entry conditions) and answers requests from data subjects. It decides which questions are asked and when data is deleted.

5. Confidentiality

People with access to the data at our end are bound to confidentiality. We only look at answers when the operation or a request by the customer requires it.

6. Sub-processors

The customer approves the following sub-processors:

ProviderServiceLocation
Hosting provider in the EU (named here before the first sale)Servers and databasesee provider
Email provider (named here before the first sale)Sending emails to buyers (no member data)see provider
Cloudflare, Inc.Network and forwarding of all pages; captcha on the check page (only if the customer chooses it)USA, EU-US Data Privacy Framework

Discord is not a sub-processor: the customer uses Discord itself, and the bot works on the platform the customer chose. Stripe processes only buyers' data as a controller of its own.

We announce new or changed sub-processors at least 14 days in advance on this page and by email to buyers of paid plans. The customer may object for good cause; it can then end the contract without notice. We bind every sub-processor by contract to the same data protection duties.

7. Technical and organisational measures (Art. 32 GDPR)

  • Separation: each server is separated from the others in the database by row-level security; database roles have only the rights they need.
  • Encryption: connections over HTTPS; stored answers encrypted; network codes as keyed hashes with a key replaced every 30 days.
  • Data minimisation: no IP addresses, no message content, no device fingerprints; the bot reads no messages.
  • Access: team sign-in only through Discord with a check of server permissions; the operator's console is separate and protected by a second factor; internal services talk only with signed requests.
  • Accountability: changes by the team are recorded in the server's history.
  • Web security: strict security headers, no third-party scripts except the captcha, no cookies except for signing in.

We adapt the measures to the state of the art without lowering the level of protection.

8. Assistance and notifications

The dashboard gives the customer tools to find, reset and delete a member's answers and data (Art. 15 to 21 GDPR). Beyond that we help to a reasonable extent with data subject requests, data protection impact assessments and consultations of the authority.

We report a breach of the security of the customer's data without delay, if possible within 24 hours of becoming aware of it, to the buyer's email address or through the bot to the server, with the information under Art. 33(3) GDPR as far as known.

9. Deletion and return

The customer can delete data in the dashboard at any time. After the end of the agreement we delete the server's data at the customer's request within 30 days, unless a legal duty to keep it applies. Public proofs of finished giveaways are included. Before that the customer gets a copy in a common machine-readable format (e.g. JSON), which we prepare on request.

10. Evidence and audits

We provide the customer with the information needed to show compliance with this agreement and allow audits by the customer or an auditor it appoints who is bound to confidentiality, after timely notice, usually in writing.

11. Final provisions

Liability is governed by Art. 82 GDPR; otherwise the terms apply. In case of conflict this agreement prevails over the terms in matters of data protection. German law applies.