Privacy Policy
Last updated: 13 November 2026
This Privacy Policy explains how Nikita Zotov, Individual Entrepreneur (Republic of Armenia) ("we", "us"), operator of AgoraBot (the "Service"), collects and uses personal data. It applies to our website agorabot.suncake.xyz and to the AgoraBot application on Discord.
1. Who we are / contact
Controller: Nikita Zotov, Aygedzor Street 78/1, apt. 16, Arabkir, Yerevan 0019, Republic of Armenia (IE State registration No. 286.1582507, TIN 20292885). Privacy contact: [email protected].
2. What data we process
Account and billing data. When you subscribe, our Merchant of Record Freemius (Freemius, Inc., United States) collects and processes your payment and billing information. Under its Data Processing Agreement it does so as our processor; see also Freemius's Privacy Policy. We receive limited transaction and subscription data (for example, plan, status, country, and the associated Discord server), not full card details. When you link a purchase to your server, we record each attempt — your Discord user ID, the server, the purchase identifier, and whether it was accepted — so that a purchase cannot be claimed by the wrong server and a disputed one can be settled. The basis is the performance of our contract with you, in binding your purchase to the server you bought it for, and our legitimate interest in preventing that fraud; the record is kept with the billing record it belongs to and is included when you export your data.
Dashboard account data. When you sign in to the admin dashboard with Discord (our only login method), we receive and store your Discord user ID, username, and avatar, and — only if you grant the optional email scope — your email address. We use this solely to authenticate you and operate your account, and we act as the controller for it.
Data Processing Addendum acceptance. When a server owner accepts our Data Processing Addendum, we record the controller's legal name, country and address, and the name, email address and (if given) position of a contact person for the controller, alongside the accepting account and the time. The contact person may be someone other than the owner who accepts; if that is you, the owner gave us your details, and this paragraph is our notice to you. We use them only as the controller's contact under the agreement, including to give the written notice of a change of sub-processor the Standard Contractual Clauses require, and we keep them with the acceptance as evidence of the agreement (Section 5). The legal basis is our legal obligation to evidence the agreement and the performance of our contract with the controller. If you did not accept the addendum yourself — so the record is not in your own export — you can ask for a copy of, correct, or object to it by writing to [email protected].
Discord identifiers. Discord user IDs, server (guild) IDs, and role and channel IDs needed to operate the Service.
Community activity data. To provide its features, AgoraBot processes activity within servers where it is installed. This includes message metadata, reactions given and received, voice-channel activity (participation, duration, and number of participants), moderation actions, and invite attribution (which invite link, and therefore which existing member, a new member joined through). Where a feature requires message content — for example, counting words to score activity — that content is processed transiently to derive the metric and is not stored; we keep only the derived values, never the message text. From this activity we derive standing scores, reputation-scale values, archetypes, and election eligibility.
Presence-derived activity (games and music). Where Discord exposes a member's presence, AgoraBot records which games a member is playing and — where a member listens to music via a connected service such as Spotify shown in their Discord presence (track, artist, and album) — that listening activity. This is used to produce per-server topcharts (most-played games, most-listened artists) and, for games, optional play-time gates on election candidacy. It is descriptive only and never folded into standing scores. These topcharts are visible to your server's owner and managers, and — only if they turn it on — to your server's members in aggregate form (see Section 7). A member who does not wish this collected can opt out (see Section 6).
Profile data (self-set). Members may optionally publish a small profile — built-in fields (birthday, country, Steam link) and any custom fields a server defines. These are set by the member, visible to their server, and cleared at any time. A birthday indicating an age under 13 is refused and never stored (see Section 10).
Support and privacy correspondence. When you email us at [email protected] or [email protected], we receive your email address, your messages, and any personal data you choose to include. These mailboxes are hosted by Zoho (our email sub-processor, see Section 7). We use this correspondence solely to answer you and handle your request.
Website data. Standard server logs (such as IP address and request data) needed to operate and secure the website. Our public hostnames sit behind Cloudflare (our CDN and reverse-proxy sub-processor, see Sections 7 and 8), which handles every request in transit before it reaches our server. We do not use tracking cookies or third-party analytics. To see which pages of our public website are read, we count visits with Umami, an analytics tool we run ourselves on our own server, so the data goes to no one else. For each page view it records the page (without its query string, except any campaign tag a link carries, such as utm_source=reddit, which tells us where we posted the link you followed), the referring site, your browser, operating system, device type, screen size and language, and an approximate location (country, region and city) looked up from your IP address. It also records when the Add to Discord or community-server button is clicked, and which one (for example, the button at the top of the page), with nothing more about you than a page view has. Your IP address itself is not stored. Page views are grouped into a visit by an identifier the server computes from your IP address and browser; it is not a cookie and nothing is stored in your browser. Umami runs on our public website only, not in the dashboard. The only browser storage we use is strictly necessary for the Service to function: a short-lived, one-time security cookie during Discord sign-in (CSRF protection), and local storage in your browser to hold your sign-in session for the dashboard. We consider this storage strictly necessary, which is the basis on which we currently operate without a consent banner; we re-check the cookies and browser storage the site actually sets whenever it changes, and will add a banner if anything non-essential appears.
3. Data roles (controller and processor)
For account and billing data, we are the controller, and Freemius processes payment and billing data on our behalf (see Section 7). For community activity data processed inside a server, the server administrator who installs and configures AgoraBot determines the purposes of processing and acts as the controller; we act as a processor on their behalf, processing data according to their configuration and these terms. A Data Processing Addendum governs this processing and lists our sub-processors.
How scores are calculated is set by your server's administrator. The standing formula — how much a message, a word, a reaction or a minute of voice is worth, how quickly older activity decays, and how activity and tenure are balanced — is per-server configuration set by the administrator, not a fixed rule we impose. We supply suggested starting values and named presets, which an administrator is free to accept, change, or replace at any time. Whatever formula your server is running, /whystanding shows you that formula and your own numbers under it — the breakdown you are shown is always the calculation that produced your score.
4. Why we process it (purposes and legal bases)
- To provide the Service (tracking, standing, roles, elections) — performance of a contract, the legitimate interests of the server administrator in running their community, and/or processing on their instructions as processor.
- To bill and support paid plans — performance of a contract (with Freemius as our Merchant of Record) and our legitimate interest in operating the business.
- To secure the Service and prevent abuse — legitimate interests.
- To understand how our public website is used (which pages are read, where visitors arrive from, and whether they go on to add the bot) — legitimate interests.
- To comply with legal obligations.
Where we rely on consent for any optional feature, you may withdraw it at any time.
5. Data retention
We practice data minimization, and we never retain identifiable data longer than necessary for the purpose:
Message content is never stored — it is processed transiently to derive metrics and then discarded.
Raw activity events (metadata, reaction and voice records) are kept on a rolling window of up to 90 days, after which raw records are automatically purged and only aggregates are retained. This maximum is enforced in our production configuration; raw retention can be set lower but not higher.
Derived data (standing, reputation-scale values, archetypes) is retained while AgoraBot remains installed in your server, as it is the functional state of the Service.
When AgoraBot is removed from your server, the community data we hold for that server is deleted or anonymized within 30 days, allowing for backup rotation. That covers the community data and your server's settings alike. We retain controller instructions that widened or narrowed Chart visibility as evidence of what the controller directed, for the limitation period for related claims. We also retain records the law requires us to keep: billing and tax records, the evidence that a purchase, a refund or a withdrawal happened, the record of a request for constitution setup (what was asked, agreed and charged, whether or not the engagement went ahead), the data-processing terms your server's owner accepted, with the contact details given at acceptance, and our log that an erasure was carried out. These records are kept for their applicable retention periods.
On a valid deletion request, the associated personal data is deleted or anonymized within 30 days. Members can also export or delete their own data at any time through the Service, across all of the data we hold about them — not only activity records.
Support and privacy correspondence is kept for up to 12 months from the end of the exchange, so we can handle follow-ups and show how a request was answered, and is then deleted. Zoho's backups hold deleted mail for up to three months more before it is overwritten.
Website server logs are kept only as long as we need them to operate and secure the site — in practice, to investigate a recent error or a recent attack. Our log store deletes entries automatically after 14 days. Each service also keeps a small buffer of its most recent log lines, limited by size rather than time, which is cleared whenever that service is updated; for a rarely used service it can reach further back than 14 days. Logs stay on our own server; we do not archive them, and we do not use them to build any profile of you.
Website analytics (Umami, see Section 2) are kept for 24 months and then deleted automatically.
Billing records are retained as required by law, by us and by Freemius.
5a. Automated processing and profiling
The Service scores activity automatically — that is what it is for — so you should know exactly how far that goes.
What is automated. From the activity described in Section 2 we automatically derive a standing score, reputation-scale values, and archetypes. Those values can automatically affect your roles in a server (where your administrator has configured score-to-role thresholds) and your eligibility to stand as a candidate or to vote in that server's elections.
Who decides the rules. We do not. The formula, the thresholds, and the eligibility gates are configured by your server's administrator, as described in Section 3. We supply changeable defaults and suggested presets only. Your administrator must explicitly confirm the weights, thresholds and consequences they are applying before AgoraBot changes anyone's roles automatically, and must confirm again whenever they change the formula.
Where the consequence is significant, a human decides — before it takes effect. Most of what the scoring drives is minor: the colour of a name, a badge, access to an ordinary channel. Where an automated value would instead remove something that materially affects your position — a role your administrator has marked significant, any elected role, or access that is not merely cosmetic — the decision is put to your server's administrator for review before it is applied, rather than applied first and reversed later. Your administrator sees the proposal together with the score and the threshold behind it, and decides; until they do, nothing is taken away. Every such decision, and every override, is recorded. Advisory anti-abuse flags (for example, a very new account, or many members joining at once) are only ever shown to moderators and never punish anyone automatically.
Eligibility to stand or vote applies at once. Your administrator can set minimums for standing as a candidate, based on standing, activity, tenure, play time or a reputation scale, and a minimum standing for voting. These are checked at the moment you stand or vote, and no one reviews the check first: if you are below a minimum you are refused, and told why. The one exception is a holder standing to keep their seat in a general election, who is not held to the candidacy minimums. Your administrator can then admit you to that election by hand, or bar you from it, and that decision is recorded. If the role at stake has real consequences outside the server, ask your administrator to review your case.
Election results are decided by votes, not by scores. Who wins an election is decided by the ballots your server's members cast; AgoraBot counts them and applies the result. Where the election is a general one — the default — the role it is held for is given to the winners and removed from anyone who held it and was not elected, including a holder who did not stand. A holder may always stand to keep their seat, whatever their standing. If an election elects nobody, nobody loses the role. Your server's administrator can choose to have AgoraBot announce elections in a Discord channel; a result announcement names the winners and the members who gained or lost the role, and why.
You can contest an outcome, and have the inputs corrected. If you think an automated outcome is wrong, you can say so and have it looked at by a person: /whystanding shows you the formula your server is running and your own numbers under it, your administrator can override the outcome, and you can write to us at [email protected] if the error is in data we hold, in which case we will correct it and the score is recalculated.
What you can see and do. The factors that go into your score, how much each one weighs, and what it leads to are shown to you by /whystanding, for the formula your server is actually running. Where the GDPR applies, you also have the rights in Section 6, including the right to object to processing and — for a decision based solely on automated processing that produces legal or similarly significant effects — to obtain human intervention, express your point of view, and contest the decision.
6. Your rights
Subject to applicable law (including the GDPR for individuals in the EEA), you may request to: access your data; correct it; delete it; export it (portability); restrict or object to processing; and withdraw consent. Members can view their own derived values (such as standing and scale impacts) consistent with our transparency commitments. To exercise rights, contact [email protected]; where activity data is controlled by a server administrator, we may direct or assist your request to that administrator. You may also lodge a complaint with your local data-protection supervisory authority.
Opting out yourself. You do not need to write to us to object to being measured. In any server, the Privacy section of your member dashboard — or /privacy in Discord, which links you there — lets you opt out. AgoraBot then stops counting your activity in that server (messages, reactions, voice, games and music), erases what it already holds about you there, and leaves you out of that server's standing and elections for as long as you stay opted out. We keep the record that you opted out, and when, so that counting does not quietly start again. You can resume at any time; what was erased does not come back.
If you are in Armenia, the same requests are available to you under the Law on Protection of Personal Data — including the right to demand erasure of your data under Art. 15(2) — and your supervisory authority is the Personal Data Protection Agency of the Ministry of Justice of the Republic of Armenia.
6a. Additional notice for US residents (CCPA/CPRA and other US state privacy laws)
This section supplements Section 6 for residents of US states with comprehensive privacy laws (including California's CCPA/CPRA, and comparable laws in Virginia, Colorado, Connecticut, Utah, Texas, and others). Under those laws we act as a "Business" for account/billing data and as a "Service Provider" or "Contractor" for the community activity data a server administrator instructs us to process — in each case only to the extent that status actually applies to the law in question and to the relationship concerned. We comply with applicable US state privacy laws where and to the extent they apply to us; we do not claim to be subject to, or compliant with, every US state privacy law.
- We do not "sell" or "share" personal information, and we do not process it for cross-context behavioural advertising, as those terms are defined under US State Privacy Laws. Once the Service has a full year of operation, we will state our practice for the preceding 12 months here.
- We do not use or disclose sensitive personal information beyond the purposes permitted under those laws. We do not intentionally collect, and do not ask you to provide, sensitive or special-category data (see Section 2). We cannot fully prevent it reaching us: a member may type anything into a self-set profile field, and Discord presence may reveal, for example, what someone is playing or listening to. We do not seek out such data, do not use it to infer sensitive characteristics, and treat anything of that kind that arrives incidentally under the same minimization and deletion rules as everything else.
- Subject to your state's law, you may request to know/access, delete, correct, and port your personal information, and to opt out of any sale, sharing, or targeted advertising and of certain profiling. Because we do not sell, share, or run targeted advertising, no opt-out is necessary for those, but you may still exercise the other rights.
- Non-discrimination: we will not deny service, charge different prices, or provide a different quality of service because you exercised your rights.
- To exercise these rights, contact [email protected]; where the data is controlled by a server administrator, we will direct or assist your request to them. You may appeal a denied request by replying to our response, and, where your state allows, contact your state Attorney General.
7. Sharing, independent controllers, and sub-processors
Inside your server. Some of what AgoraBot measures can be shown to other members of the same server, as charts — for example the most active members, the busiest channels, who has been in the server longest, and (where enabled) the most-played games and most-listened artists. This is off unless your server's administrator turns it on, and it is their decision to make as the controller for your server's activity data; where they do, we record who instructed it and when. These charts are visible to members of that server only — never publicly on the internet, never to search engines, and never to another server.
You can ask not to be named in those charts while still taking part in everything else: your activity keeps counting, your standing, roles and votes are unaffected, and only the rows listing you by name leave you out. Use the Privacy section of your member dashboard, or /privacy in Discord, which links you there. Your administrator cannot see who has chosen this. Charts of games and listening are shown to members only in aggregate — which games and artists, and how many people, never which member plays or listens to what — and only where at least three members are counted, so a chart cannot single anyone out by being nearly empty.
One party we work with is an independent controller — it decides its own purposes and means and acts under its own terms and privacy policy, not on our behalf:
- Discord — the platform the Service runs on and the source of activity data; Discord independently controls the underlying platform data under its own privacy policy.
We also share data with sub-processors that process it on our behalf and on our instructions, under appropriate agreements:
- Hetzner Online GmbH — application and database hosting, within the European Economic Area (Germany).
- Scaleway SAS — offsite storage of our database backups, within the European Economic Area. The backups are encrypted before they leave our server, so Scaleway holds only ciphertext and never the key.
- Zoho (Zoho Corporation B.V.) — email hosting for our support and privacy contact addresses; processes the correspondence you send us and the notices we send you in writing, such as confirming receipt of a withdrawal from a paid plan (see Section 2).
- Freemius, Inc. — payments, tax and invoicing as our Merchant of Record and reseller. It processes buyers' payment and billing data, and no community activity data, on our behalf under its Data Processing Agreement, in the United States.
- Cloudflare, Inc. — content delivery network, reverse proxy and DDoS protection in front of our public hostnames. Cloudflare terminates TLS, which means it handles your requests — including authenticated dashboard traffic — in transit on our behalf (see Section 8).
We do not sell personal data. We keep our list of sub-processors current.
8. International transfers
Our application and database hosting, including our encrypted backups, are located within the European Economic Area (EEA) — data at rest stays in the EEA. Production runs on Hetzner in Germany; offsite backup storage uses Scaleway Object Storage in the selected EEA region and receives only age-encrypted ciphertext, with the decryption key held separately. Some processing nevertheless takes place outside the EEA, as described below. The operator is established in the Republic of Armenia. The EU has not issued an adequacy decision for Armenia, so where the operator accesses EEA members' personal data from Armenia, that export is governed by GDPR Chapter V and relies on appropriate safeguards — the EU Standard Contractual Clauses (2021/914) — as described in our DPA §7, not on adequacy. Separately, under Armenian law the transfer into Armenia is permitted because Armenia recognizes EEA member states as ensuring an adequate level of protection (Armenian Law on Protection of Personal Data, Art. 27). Our email sub-processor Zoho stores the support and privacy mailboxes, and the notices we send you in writing, in its EU data centre. Under Zoho's data processing addendum, Zoho group entities in India may access it for support and debugging, and Zoho's own sub-processors may process it outside the EEA; Zoho is responsible for putting a valid GDPR transfer basis in place for those transfers. Cloudflare, which proxies our public hostnames, operates a global anycast network: routing is determined by that network, so a request may be handled at an edge location inside or outside the EEA, including in the United States. That processing is governed by the Cloudflare Data Processing Addendum, which incorporates the EU Standard Contractual Clauses. Freemius, our Merchant of Record, processes payment and billing data in the United States; its Data Processing Agreement incorporates the EU Standard Contractual Clauses (Module Two) and the UK International Data Transfer Addendum. Discord, an independent controller, may likewise process data outside the EEA under its own safeguards.
9. Security
We use reasonable technical and organizational measures — including encryption in transit, access controls, least-privilege design, and minimal data collection — to protect data. No system is perfectly secure, and we cannot guarantee absolute security.
10. Children
The Service is not directed to children. Consistent with Discord's minimum age, you must be at least 13 years old to be present in a server where AgoraBot operates, or older where the minimum age Discord sets for your country is higher. Separately, GDPR Art. 8 sets the age (between 13 and 16, depending on the EEA state) below which a child's consent to an information-society service must be given or authorised by a parent — it is a rule about consent, not a general minimum age for using the Service, and we do not rely on a child's consent as a legal basis. In the United States, in line with the Children's Online Privacy Protection Act (COPPA), we do not knowingly collect personal information from children under 13. We do not knowingly collect data from anyone below the applicable age. If we learn that a user is under 13, we stop processing their data, cut off their access to the Service, and delete what we hold for them across every server we operate in — and we record the block, so their data is not collected again afterwards. As a further safeguard, the Service refuses to store a self-set birthday that indicates an age under 13. If you believe a child below the applicable age has data with us, contact [email protected].
11. Changes
We may update this Policy; material changes will be posted here with a new "Last updated" date.
12. Contact
Nikita Zotov (Individual Entrepreneur) — [email protected] — Aygedzor Street 78/1, apt. 16, Arabkir, Yerevan 0019, Republic of Armenia (IE State registration No. 286.1582507, TIN 20292885)