Annex I — Parties, Description of Transfer, Competent Supervisory Authority
Attaches to Module 2 of the Standard Contractual Clauses (Decision (EU) 2021/914), entered into by accepting the Data Processing Addendum in the AgoraBot dashboard (DPA §7).
Version: 2026-10-27
A. LIST OF PARTIES
Module 2 — Controller to Processor
Data exporter (controller)
| Field | Value |
|---|---|
| Name | The legal entity or person that controls the Discord server on which the Service is installed, as named at DPA acceptance |
| Address | As given at DPA acceptance |
| Contact person | Name, email address and, where given, position, as stated at DPA acceptance |
| Activities relevant to the transfer | Operating a Discord community and instructing AgoraBot to measure member activity and drive roles and elections within it |
| Role | Controller |
| Signature and date | Recorded electronically at DPA acceptance |
The exporter's details differ for each customer. They are recorded, with the date and time, when the exporter accepts the Data Processing Addendum in the dashboard, and that record completes this Part for that customer.
Data importer (processor)
| Field | Value |
|---|---|
| Name | Nikita Zotov, Individual Entrepreneur (Republic of Armenia), trading as AgoraBot |
| Address | Aygedzor Street 78/1, apt. 16, Arabkir, Yerevan 0019, Republic of Armenia |
| IE State registration No. | 286.1582507 |
| TIN | 20292885 |
| Contact person | [email protected] |
| Activities relevant to the transfer | Providing the AgoraBot Discord governance service — ingesting activity signals, computing standing, driving role assignment and elections — on the exporter's documented instructions |
| Role | Processor |
Module 3 — Processor to Processor
Not executed with any current sub-processor. Each non-EEA sub-processor's own data processing terms, which incorporate the Standard Contractual Clauses, govern its leg; see Annex III.
B. DESCRIPTION OF TRANSFER
B.1 Categories of data subjects
- Members of Discord servers on which the Service is installed
- Administrators and delegated managers of those servers
- Holders of an AgoraBot dashboard account (Discord OAuth2 login)
- Persons who contact the operator's support or privacy addresses
B.2 Categories of personal data
| Category | Detail |
|---|---|
| Identifiers | Discord user, guild, role and channel IDs (snowflakes); username and avatar hash; optional email address where the account holder grants the email OAuth scope |
| Behavioural / activity metadata | Message word counts (never message content), reaction counts, voice-channel seconds, join and leave events, invite attribution, presence-derived game and music-listening activity |
| Derived data | Standing score, season score archive, archetype labels, advisory abuse flags (young-account, join-burst) |
| Self-published profile fields | Birthday, country, Steam handle, administrator-defined custom fields — all set by the member themselves |
| Governance records | Election candidacies, ballots, and audit entries recording that a member voted (never their choices) |
| Moderation records | Target ID, moderator ID, action, reason |
| Billing state | Guild ID, plan, status, provider subscription ID |
| Correspondence | Email address, message content, and any personal data the sender chooses to include |
Message content is never stored. Only per-message word counts are retained.
B.3 Sensitive data
None. No special-category data within the meaning of Art. 9 GDPR, and no criminal-offence data under Art. 10, is intentionally collected or processed.
Two residual points are disclosed rather than suppressed:
- Presence-derived activity (games played, music listened to) is metadata Discord already broadcasts to the server. At the margin, listening or play patterns could correlate to inferences about a person. It is stored as names and durations only, is descriptive and never scored into standing, and is covered by the member opt-out (suppressed at both ingest and resync) and by erasure. Who it is surfaced to is bounded: per-member rankings (which member plays or listens to what) are visible to the guild's owner and delegated managers only and cannot be made visible to members; the aggregate topcharts may additionally be made visible to a guild's own members where that guild's controller instructs it, in which case rows counting fewer than three distinct members are suppressed and any member who has asked not to be named is omitted. No presence data is surfaced outside the guild it came from, ever.
- Self-published profile fields are free-text or member-selected. A member could volunteer sensitive information into a custom field. The field schema is administrator- defined, values are member-set, and the whole store is erasable on request.
No additional restrictions under Clause 8.7 (Module 2) / 8.8 (Module 3) are stipulated beyond the measures in Annex II. Sensitive data is not collected or sought, but — as noted above — cannot be structurally excluded from self-set fields and presence, so the general measures are what protects it.
B.4 Frequency of the transfer
Continuous. The operator has administrative access to the production systems on an ongoing basis; activity ingestion is event-driven and continuous while the Service is installed.
B.5 Nature and subject matter of the processing
Ingestion of Discord activity signals; aggregation into daily per-source rollups; automated computation of an earned-standing score; reconciliation of Discord roles against administrator-configured score thresholds; operation of standing-gated elections; advisory abuse flagging; administrator dashboard and reporting; support and billing administration.
B.6 Purpose of the transfer and further processing
To provide, maintain, secure and support the Service on the exporter's documented instructions, and to enable the operator — the sole person maintaining the system — to administer, debug and secure it from the Republic of Armenia. No further processing for the operator's own purposes takes place in respect of data processed under Module 2.
B.7 Retention period
| Data | Period |
|---|---|
| Raw activity events | ≤ 90 days, enforced at startup by configuration validation; a shorter window may be configured |
| Derived state (daily rollups, standing, tenure, invite attribution, scales) | While the Service is installed, bounded by the departed-member TTL worker |
| Presence event logs (game, music) | Pruned past the ingest watermark — transient |
| Election records | Per election, retained for audit |
| Moderation records | Retained for audit; anonymised, not deleted, on member erasure; fully purged on guild erasure |
Erasure evidence (erasure_log) and withdrawal-consent evidence | Retained as accountability and legal-obligation evidence; intentionally excluded from erasure |
| All guild data after uninstall | Deleted or anonymised within 30 days of removal, including backup copies (DPA §10) |
| Correspondence | Deleted when no longer needed for the request and any legal record |
Transfers to subprocessors are for the duration of the subprocessing arrangement; see Annex III.
B.8 Subject matter, nature and duration of subprocessor processing
Per subprocessor, see Annex III.
C. COMPETENT SUPERVISORY AUTHORITY
Module 2. Determined under Clause 13(a) by reference to the data exporter. Where the exporting server administrator is a controller established in an EEA member state, the competent authority is the supervisory authority competent for that controller. Where the exporter is not established in the EEA but falls within the territorial scope of the GDPR under Art. 3(2) and has appointed an Art. 27 representative, the competent authority is that of the member state in which the representative is established.