Back to Auth
Guildify Privacy

Privacy Policy

This policy describes what information Guildify collects, how that information is used and shared (including for plan-limit and abuse enforcement), the legal bases for processing, your rights by region, and how we protect your data.

Last updated: September 29, 2026

Section 01

Introduction and Data Controller

This Privacy Policy describes how Guildify ('we', 'us', or 'our') collects, uses, shares, and protects personal information when you use the Guildify platform (the 'Service').

Guildify is the data controller responsible for your personal information. For data protection inquiries, contact us at [email protected].

Section 02

Information We Collect

Account and Discord information: when you sign in with Discord, we receive your Discord user ID, username, avatar, and the guild (server) memberships you choose to share, together with any email address you authorize.

Community and guild data: the communities, guilds, members, events, rosters, applications, and records you create or manage on the platform.

Subscription and billing information: payments are processed by Polar; we receive transaction status and plan details but do not store full payment card numbers.

Technical and usage data: IP address, browser and device type, operating system, logs, pages visited, and usage analytics, collected through cookies and similar technologies.

Metering, audit and security data: counts and timestamps of feature usage and quota consumption (for example, how many events, auctions, or quests you have created in a period), records of automated requests made through our Discord bot and MCP server, and audit logs of actions that affect your community.

Section 03

How We Use Information

We use personal information to provide and operate the Service, authenticate users via Discord, manage communities and events, process subscriptions and purchases, provide support, secure the platform against abuse, and comply with legal obligations.

We also use usage, metering, and log data to verify compliance with the plan limits that apply to your account or community, to detect and prevent circumvention of those limits, fraud, and other misuse of the Service, and to enforce our Terms of Service, including by throttling, restricting, or suspending activity where necessary.

We may also use aggregated or de-identified data for analytics and product improvement where permitted by law.

Section 04

Legal Bases for Processing (EEA and UK)

For users in the European Economic Area and the United Kingdom, we process personal information on the following lawful bases under the GDPR and UK GDPR: performance of a contract (providing the Service), our legitimate interests (security, fraud and abuse prevention, enforcement of the plan limits and fair-use rules that fund the Service, and product improvement), your consent (for optional cookies and marketing, where applicable), and compliance with legal obligations.

Where processing is based on consent, you may withdraw it at any time without affecting the lawfulness of processing carried out before withdrawal.

Section 05

Cookies and Similar Technologies

We use strictly necessary cookies to keep the Service secure, maintain sessions, and remember core preferences. Optional analytics and third-party services are only activated after you grant consent.

Detailed information about the cookies we use, their purposes, and how to manage them is available in our Cookie Policy. You can update your preferences at any time through the cookie manager.

Section 06

Optional Features You Control

Some Guildify features process additional data. They are never a condition of using the Service: a community administrator decides whether to enable a feature for the community, and you can switch each purpose off for yourself at any time with the /privacy command in Discord or under Settings → Data & Privacy on the website. Withdrawing consent stops all further processing for that purpose and does not affect processing carried out before withdrawal.

Live Raid Radar (presence data). When you are signed up to a guild event, Guildify can read your Discord online status (online, idle, do-not-disturb, offline) and the name of the game you are currently playing, in order to show raid leads who is actually in game and in voice. This requires your explicit consent, only runs while an event window is active, is sampled at most once every five minutes, is never shared with third parties, and is deleted after 30 days.

Game catalogue (anonymous presence shapes). Independently of any event, while the bot is installed in a server it records the shape of the Discord Rich Presence activities it can see: the activity or game name, the activity type, the application identifier, and a truncated, link-stripped copy of the presence fields the game itself publishes (which can include a character name, zone or lobby). These rows are aggregated across members per game and activity type, are never linked to a person, and do not contain your Discord user ID, username, avatar or any per-person timestamp. They are used to keep an accurate list of real games and applications and to build game-specific parsing for the presence features described above. If you switch presence processing off with /privacy disable presence_radar, your presence is excluded from this catalogue as well.

Engagement, XP and attendance. When you use the bot or the website, we record which commands, buttons, selects and reactions you used, how long you were in event voice channels, and which events you attended. This is used to calculate guild XP, contribution scores, leaderboards and reward or loot priority. We never read or store your message content for this purpose. The lawful basis is our legitimate interest in operating community management features; you may object at any time with /privacy disable xp_system or /privacy disable engagement_index, and voice-join timestamps are kept for 365 days.

Message-based features. Some features read message content, but only when you are explicitly addressing the bot or writing inside a surface the bot itself created for that purpose: mentioning the bot, an AI thread opened by a bot command, or the bid thread of an auction. Message content is never used to train machine-learning models, is never used for advertising, and is never scanned across channels.

A full, per-purpose list with the exact data categories, legal basis and retention period for your account is available under Settings → Data & Privacy, and you can request a copy or deletion of your data there or with /privacy data.

Section 07

How We Share Information

We share personal information only as necessary: with service providers (such as Supabase for infrastructure, Polar for payments, and Discord for authentication); with other members of your community as part of the Service's features; and where required by law or to protect rights and safety.

We do not sell your personal information. Where we share data, we do so under contractual obligations requiring confidentiality and appropriate security.

Section 08

International Data Transfers

Our primary data hosting is located in the European Economic Area. Some of our service providers may process data in other countries, including the United States.

Where personal information is transferred outside the EEA, the UK, or other jurisdictions with equivalent protection, we rely on appropriate safeguards such as Standard Contractual Clauses or an adequacy decision.

Section 09

Data Retention

We retain personal information only as long as reasonably necessary to provide the Service, comply with legal obligations, resolve disputes, and enforce our agreements.

Retention periods vary by data type and account status. When data is no longer needed, we delete or anonymize it in accordance with our retention schedule.

Usage metering, security, and audit records (including records of plan-limit consumption and of enforcement actions taken against an account) may be retained for longer than the related account data where necessary to detect and prevent further abuse, to detect fraud, and to establish, exercise, or defend legal claims.

Section 10

Data Security

We implement reasonable technical and organizational measures to protect personal information, including encryption in transit and at rest and access controls. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

You also play a role in protecting your account by safeguarding your Discord credentials.

Section 11

Your Privacy Rights by Region

EEA and UK (GDPR / UK GDPR): you have the right to access, rectify, erase, restrict, and port your personal data, to object to processing, and to lodge a complaint with your supervisory authority.

California (CCPA / CPRA): California residents have the right to know what personal information we collect, to request deletion, to correct inaccurate data, to opt out of the 'sale' or 'sharing' of personal information (we do not sell personal information), and to non-discrimination for exercising these rights.

Türkiye (KVKK): under Law No. 6698, you have rights including access to your data, rectification, deletion, and objection to certain processing.

Brazil (LGPD): under the Lei Geral de Proteção de Dados, you have rights including confirmation, access, correction, anonymization, portability, and information about shared data.

Other jurisdictions (for example, PIPEDA in Canada and PIPL in China): you may have similar access, correction, and deletion rights. To exercise any of these rights, contact [email protected].

Section 12

Children's Privacy

Guildify is intended for users aged 18 and over. We do not knowingly collect personal information from children.

If you believe a child has provided us with personal information, contact us and we will take steps to delete it.

Section 13

Global Privacy Control and Do Not Track

We honor the Global Privacy Control (GPC) signal where required by law, treating it as a request to opt out of the sale or sharing of personal information and of non-essential cookies.

Some browsers offer a 'Do Not Track' setting. Because there is no consistent industry standard, our Service currently responds primarily to consent choices made through our cookie manager and GPC.

Section 14

Data Breach Notification

In the event of a personal data breach that poses a risk to your rights and freedoms, we will notify affected individuals and relevant authorities as required by applicable law.

Section 15

Changes to This Policy

We may update this Privacy Policy from time to time. Material changes will be communicated through the Service before they take effect.

Your continued use of the Service after changes take effect constitutes acceptance of the revised policy.

Section 16

Contact and Complaints

For privacy questions or to exercise your rights, contact [email protected]. If you are in the EEA or the UK, you may also lodge a complaint with your local data protection authority.