Legal

Privacy Policy

This policy explains how GuildMaster collects, uses, stores, and protects personal data for guild management, integrations, analytics, and Patreon-based paid access.

Data selling
Never
Rights model
GDPR-first
Ads
Consent-gated

GuildMaster does not sell personal data or guild data. The service is designed around EU/GDPR expectations, with guild owners controlling workspace content and users keeping standard privacy rights under applicable law.

1. Controller

GuildMaster controller

GuildMaster is operated by GuildMaster project team. Controller details are listed on the Legal Notice page.

View Legal Notice

Guild-controlled workspace data

Guild owners and managers decide what roster, raid, loot, attendance, Discord, and member data is entered into a workspace and may have independent responsibilities toward their community.

2. Data we collect

Account identity

Supabase user identifiers, BattleTag, region, Battle.net OAuth metadata, Discord account identifiers, sessions, and profile settings.

Guild workspace

Guilds, rosters, characters, roles, raids, loot, attendance, notes, imports, exports, addon data, and integration metadata.

Plans and access

Plan code, trial status, subscription state, founder status, quota enforcement, Patreon tier, membership status, and timestamps.

Technical operation

Security signals, application logs, error information, consented analytics events, performance telemetry, advertising delivery signals, and operational timestamps.

3. Purposes and legal bases

Contract

Used to provide the app, authenticate users, show authorized guild data, apply plan limits, and synchronize access.

Legitimate interest

Used for security, abuse prevention, diagnostics, reliability, and product improvement.

Consent or legal duty

Used where required for optional integrations, communications, future trackers, compliance, or legal claims.

4. Battle.net, Discord, Patreon, and integrations

Battle.net

OAuth login and WoW profile data support verification, imports, and roster linking while avoiding unnecessary long-term character inventory storage.

Discord

Optional linking stores account identifiers, display names, verification timestamps, and guild/player links.

Patreon

When enabled, only the membership data needed to map a Patreon tier to a GuildMaster plan should be stored.

5. Sub-processors

GuildMaster may use these providers to operate the service:

Supabase

Authentication, database, row-level security, and Edge Functions.

Data: Account identifiers, sessions, profiles, guild data, roster data, integration metadata, logs.
Location: Cloud regions selected for the Supabase project; may include processing outside Italy.

Vercel

Application hosting, web analytics, and speed insights.

Data: Technical request data, aggregated analytics, performance telemetry.
Location: Global infrastructure, including possible processing outside the EEA.

Blizzard/Battle.net

OAuth login and World of Warcraft profile, guild, and character imports.

Data: Battle.net identifiers, BattleTag, region, WoW profile and character data returned by the API.
Location: Provider infrastructure according to Blizzard terms and policies.

Discord

Optional account linking and community integration features.

Data: Discord account id, username, display name, linked guild/player metadata.
Location: Provider infrastructure according to Discord terms and policies.

Patreon

Initial paid access, memberships, payments, renewals, cancellations, and receipts.

Data: Creator membership data needed to confirm tier, status, and access entitlement.
Location: Provider infrastructure according to Patreon terms and policies.

Google

Consent-gated advertising through Google AdSense on approved public pages.

Data: Technical request data, consent signals, advertising identifiers where consent allows them, and ad delivery metrics.
Location: Google infrastructure, including possible processing outside the EEA with applicable transfer safeguards.

6. Cookies, storage, analytics, and ads

Essential cookies and browser storage keep authentication and active guild selection working. Vercel Analytics and Speed Insights are used as optional analytics/performance tools and can be controlled from the Cookie Policy.

Google AdSense may be used on approved public pages only after advertising consent. GuildMaster does not load Google advertising scripts in guild data views by default, and does not use Battle.net, character, roster, loot, attendance, or guild workspace data for advertising targeting.

7. Retention

Account and workspace

Kept while the account or guild workspace exists, unless an authorized deletion request is completed.

Backups

Backup copies may remain for up to 30 days after deletion or change.

Security and integrations

Security and integration action logs may be retained up to 180 days; raw provider payloads should be minimized and removed within 30 days unless needed.

Billing and tax records may be retained for the periods required by Italian or other applicable law once paid access is live.

8. International transfers

GuildMaster and its providers may process data outside Italy or the European Economic Area. Where required, we rely on safeguards such as adequacy decisions, standard contractual clauses, or equivalent transfer mechanisms.

9. Your rights

Access
Correction
Deletion
Restriction
Portability
Objection
Withdraw consent
Complain to an authority

To exercise rights, contact privacy@guildmaster.example. We may need to verify your identity and authority over a guild workspace before fulfilling a request. You may also complain to a competent data protection authority.

10. Security

GuildMaster uses authentication, role-based access controls, row-level database policies, logging, operational safeguards, and secret-handling practices to protect data. No online service can guarantee absolute security.

11. Children and minors

GuildMaster is intended for users old enough to manage online accounts and guild communities under applicable law and platform rules. We do not knowingly collect personal data from children where parental consent is required.

12. Changes and contact

Cookie and analytics controls

Review storage and change analytics or advertising consent.

Contact privacy support

Use the privacy channel for GDPR requests or questions.

We may update this policy as GuildMaster evolves, including when Patreon synchronization, direct checkout, analytics, or additional integrations are added.