AgoraBot
FeaturesPricing

Data Processing Addendum

Version: 2026-10 · Last updated: 30 October 2026

When you accept this DPA in the AgoraBot dashboard we record which version you accepted, by the version number above. If we issue a new version, your acceptance of this one stays on record and we ask you to accept the new text.

This Data Processing Addendum ("DPA") forms part of the Terms of Service between Nikita Zotov, Individual Entrepreneur (Republic of Armenia), of Aygedzor Street 78/1, apt. 16, Arabkir, Yerevan 0019, Republic of Armenia (IE State registration No. 286.1582507, TIN 20292885) ("Processor", "we"), and the server administrator who installs and configures AgoraBot ("Controller", "you"). It governs the processing of community activity data carried out by us on your behalf, and reflects Article 28 GDPR.

1. Roles

For community activity data processed inside a Discord server, you are the controller and we are the processor. We process such data only on your documented instructions, as expressed through your configuration of the Service and these terms, unless required otherwise by law (in which case we will inform you where permitted). For account and billing data, we are the controller, and Freemius, our Merchant of Record, processes it on our behalf — that processing is outside this DPA. Discord operates the platform the Service runs on and is an independent controller of the underlying platform data under its own terms; it is not our sub-processor, and disclosures to it are not onward sub-processor transfers under this DPA.

2. Subject matter, duration, nature and purpose

  • Subject matter / nature: automated collection and processing of Discord activity to provide community-governance features (activity tracking, standing/reputation, role thresholds, elections, moderation tooling, invite attribution, welcome/notification).
  • Purpose: to deliver the Service you configure.
  • Duration: for as long as AgoraBot is installed in your server, subject to the retention terms in the Privacy Policy.

3. Categories of data and data subjects

  • Data subjects: members of your Discord server.
  • Personal data: Discord user/guild/role/channel IDs; message metadata (counts, timestamps — not stored content); reactions; voice participation; presence-derived game activity (which games are played) and music-listening activity (track/artist/album where surfaced by Discord presence, e.g. Spotify); moderation actions; invite attribution; derived standing/reputation/archetype values; self-set profile fields (birthday/country/Steam link and any custom fields the server defines). Message content is processed transiently to derive metrics and is not stored. If you use the optional AI government-setup feature, the free-text description you type is sent to our AI sub-processor (see SUBPROCESSORS) to generate the plan; no member data is included — do not include personal data in the description.

4. Controller obligations

You warrant that you have a lawful basis for the processing, that you have the authority to install AgoraBot in the server, and that members are informed as required by applicable law that an application processes their activity data.

5. Our obligations as processor

We will: (a) process only on your documented instructions; (b) ensure persons authorized to process are bound by confidentiality; (c) implement appropriate technical and organizational security measures (Article 32); (d) assist you, taking into account the nature of processing, in responding to data-subject rights requests and in meeting your obligations under Articles 32–36; (e) make available information necessary to demonstrate compliance.

Unlawful instructions. If we consider that an instruction from you infringes the GDPR or another Union or Member State data-protection provision, we will inform you immediately and may suspend performance of that instruction until you withdraw or confirm it, without that suspension being a breach of the Terms on our part. This reflects Art. 28(3), final paragraph, GDPR.

6. Sub-processors

You give general written authorisation for us to engage the sub-processors listed in SUBPROCESSORS.

How we tell you about changes. Before we add or replace a sub-processor, we email you at the contact address you gave when accepting this DPA, at least 30 days before the change takes effect, and publish the same change in the dated changelog at the bottom of the Sub-processors page. Keep that contact address current by updating your acceptance in the dashboard. You may object on reasonable data-protection grounds by emailing [email protected] within those 30 days; if we cannot resolve your objection, you may terminate the Service for the affected server without penalty, and we will delete the data as set out in Section 10.

Obligations and liability. We engage each sub-processor under a written contract imposing the same data-protection obligations as are set out in this DPA, in particular the obligation to provide sufficient guarantees to implement appropriate technical and organisational measures so that the processing meets the requirements of the GDPR. Where a sub-processor fails to fulfil those obligations, we remain fully liable to you for the performance of that sub-processor's obligations, as required by Art. 28(4) GDPR.

7. International transfers

Where personal data is transferred outside the EEA, we rely on the EU Standard Contractual Clauses (2021/914), Module 2 (Controller → Processor), for transfers from you (the controller) to us. Onward transfers from us to our sub-processors outside the EEA are governed by those sub-processors' own data processing terms, which incorporate the Standard Contractual Clauses; if we engage a sub-processor whose terms do not, we will conclude Module 3 (Processor → Processor) with it before any transfer. The SCCs are completed with Annex I (parties, roles, data categories, purposes, retention, competent supervisory authority), Annex II (technical and organisational security measures), and Annex III (subprocessor list), and are supported by a Transfer Impact Assessment. The Clauses themselves are the unamended official text of Decision (EU) 2021/914, incorporated by reference; only the elective selections below and the Annexes are ours. The Transfer Impact Assessment is available on request from [email protected].

You enter into the Clauses, as data exporter, when you accept this DPA in the AgoraBot dashboard; the details you give there complete Annex I, Part A. The elective selections are:

  • Clause 7 (docking clause): included.
  • Clause 9(a) (sub-processors): Option 2, general written authorisation, with notice at least 30 days before an addition or replacement takes effect, given as Section 6 describes.
  • Clause 11(a): the optional independent dispute resolution body is not included.
  • Clause 13 (supervision): the competent supervisory authority is set out in Annex I, Part C.
  • Clause 17 (governing law): the law of Germany.
  • Clause 18(b) (choice of forum): the courts of Germany. See the Privacy Policy and Subprocessors.

For Annex I, the competent supervisory authority is the data-protection authority of the EEA state in which the relevant controller-exporter is established, determined in accordance with Clause 13 of the SCCs.

Where a data-processing role is engaged for a specific processing purpose, the parties' allocation of controller and processor roles is described in Section 1 and in our Privacy Policy. The parameters by which member standing is calculated are configured by you, the server administrator, per server; we supply changeable default values and suggested presets only. Together with the thresholds and gates you set, this means the criteria applied to your members are determined by you. So that this is a fact rather than a formality, the Service requires you to confirm the weights, thresholds and consequences explicitly, records that confirmation against the configuration in force, and does not apply automatic role changes until you have done so — nor after you change the formula, until you confirm the new one.

8. Data-subject rights and assistance

We provide member self-service export and deletion within the Service covering all personal data we hold about a member, not only activity records, and will assist you with rights requests that require our action.

8a. Automated decisions and human review

The Service scores activity automatically and can act on the result. Because you configure the formula, the thresholds and the gates, you decide what consequences those scores carry in your server, and with that comes the Art. 22 question.

  • Advisory outputs never act on their own. Anti-abuse and Sybil flags are shown to your moderators and never punish, restrict or remove anyone automatically.
  • Consequences we treat as significant. Where an automated value would remove something that materially affects a member's position — a role you have marked significant, any elected role, or access that is not merely cosmetic — the Service is built so that the decision is put to a human before it takes effect, not merely reversible afterwards. Reversal after the fact does not by itself take a decision outside Art. 22.
  • Eligibility gates apply automatically. Standing, activity, tenure, game-time and reputation-scale thresholds decide candidacy, and a standing threshold decides voting, at the moment someone stands or votes, without a prior human decision. In an ordinary server this is internal community mechanics and does not reach the "legal or similarly significant effect" threshold in Art. 22(1). It can reach it if the elected role carries real consequences outside the game — control of money or paid activity, management of significant resources, professional opportunities, or serious reputational effect. If that describes your server, the Art. 22 obligation is yours as controller: an administrator can admit any member to a specific election by hand, and you should do so on request rather than leaving the gate to decide.
  • Contest and correct. A member may contest such an outcome, state their point of view, and ask for the input data to be corrected. The route is /whystanding for the calculation, then you as the administrator, and [email protected] if we hold the error.
  • Your part. If you configure the Service so that an automated value produces a legal or similarly significant effect, you are the controller of that decision and are responsible for meeting Art. 22(3) — human intervention, expression of a point of view, and contestation. We give you the mechanisms above; whether they are enough depends on what you switch on.
  • Explanation. The main factors, their weight, and the consequences are shown to members through /whystanding, which reflects your configured formula, not a generic description of ours.

9. Personal data breach

We will notify you without undue delay after becoming aware of a personal data breach affecting data processed on your behalf, and provide information reasonably available to us to support your notification obligations.

10. Deletion and return

At your choice, on termination of the provision of the Service (including when AgoraBot is removed from your server) or on your request, we will delete or return the personal data processed on your behalf, and delete existing copies, within 30 days (allowing for backup rotation), unless retention is required by law. This reflects Article 28(3)(g) GDPR; the equivalent destruction duty also applies under Armenian Law on Protection of Personal Data (Art. 19(1)).

11. Audit

We will make available information necessary to demonstrate compliance with Article 28 and allow for and contribute to reasonable audits, subject to confidentiality and security constraints.

12. US State Privacy Laws addendum

To the extent US State Privacy Laws (including the California CCPA/CPRA and comparable laws in Virginia, Colorado, Connecticut, Utah, and Texas) apply to your processing, this Section governs and the terms below map onto the roles above:

  • You are the "Business" (or "Controller") and we are the "Service Provider" (or "Processor"/"Contractor") with respect to the community activity data you instruct us to process.
  • We process personal information only on your behalf for the limited, specified business purpose of providing the Service, and only as permitted by the applicable law and these terms.
  • We will not: (a) sell or share personal information (as those terms are defined under US State Privacy Laws); (b) retain, use, or disclose it for any purpose other than the business purpose above, or outside our direct business relationship with you; or (c) combine it with personal information received from other sources, except as permitted for a service provider.
  • We certify that we understand and will comply with these restrictions.
  • We will assist you in responding to verifiable consumer requests, and, on your instruction or on termination, delete or return the personal information as set out in Section 10.
  • If we can no longer meet our obligations under applicable US State Privacy Laws, we will notify you, and you may take reasonable steps to stop and remediate unauthorized use.
© 2026 AgoraBot
Privacy PolicyTerms of ServiceRefund PolicyPricingSub-processorsData Processing AddendumContact