Data & Privacy
Privacy Policy
How account, guild, telemetry, and integration data is processed.
Privacy Policy (OMG Project's / OMG Projects Bots, Dashboard, and Tools)
Last Updated: 25 March 2026
This Privacy Policy explains how OMG Project's (also referred to as "OMG Projects", "we", "us", "our") collects, uses, stores, shares, and protects data when you use:
- OMG Project's Discord bots (including Killfeed Bot, Helper Bot, Ark Bot, Utility Bot, and Guild Bot)
- The web dashboard and tools at
https://www.omg-projects.co.uk
By using these services, you agree to this policy.
1) Scope and Roles
This policy covers processing performed by OMG Project's for:
- Bot features, slash commands, automations, moderation actions, and configuration
- Dashboard login, dashboard pages, and tools pages
- Subscription/entitlement workflows (including Patreon linking and activation lifecycle)
Third-party platforms (including Discord, Patreon, Nitrado, hosting providers, and other server providers) process data under their own policies.
2) Data We Collect
A) Discord account and guild data
We may process:
- Discord user IDs, usernames, global/display names, discriminator (where available), avatar URLs
- Guild IDs, role IDs, channel IDs, message IDs, permissions/membership context needed for access control
- Dashboard authorization context (for example, whether your account can access a guild or page)
B) Authentication and session data (dashboard/tools)
We process:
- OAuth state and target cookies for login flow
- Session cookies and session metadata for authenticated access
- Login telemetry used for security/audit (for example masked IP, user-agent, timestamp, target dashboard)
Current implementation includes short-lived OAuth state and target cookies and an authenticated session TTL of approximately 8 hours.
C) Guild and bot configuration data
We store operational configuration such as:
- Module settings (channels, roles, toggles, thresholds, economy settings, logging options, alerts, page access mappings)
- Bot feature JSON/config files and guild-specific settings
- Command/page role-access allocations configured by admins
D) Game/server telemetry and log-derived data
For supported integrations (for example DayZ/ARK workflows and Nitrado-linked server operations), we may process:
- Parsed event logs (kills, deaths, sessions, economy events, positions, alerts, zone events, admin actions)
- Player names/gamertags and account-link mappings
- Aggregated outputs (leaderboards, timelines, metrics, map/tracker summaries)
E) Integration credentials and identifiers
Where required by enabled features, we may process:
- API/service identifiers and tokens provided by admins
- Provider account/service identifiers (including Nitrado service references where configured)
- File access credentials required for server file operations (for example provider/API-returned FTP details)
F) Patreon and subscription data
When Patreon integration is used, we may process and store:
- Discord ID to Patreon account link
- Patreon user ID and Patreon member ID
- Patreon patron status and tier/entitlement mapping
- Grace-period state and grace expiry timestamps
- Renewal markers used to prevent duplicate cycle extensions
- OAuth access/refresh tokens and token expiry used to refresh Patreon identity
- Billing/subscription metadata returned by Patreon identity payload when available, including fields such as pledge start date, last charge date/status, next charge date, entitlement amount, will-pay amount, and lifetime support
- Patreon profile metadata returned by Patreon identity payload when available, including fields such as name, email, vanity, and profile URL
G) Operational, audit, and error logs
We maintain technical logs to:
- Diagnose failures and reliability incidents
- Track sensitive actions and access events
- Detect abuse, misuse, and security anomalies
We do not intentionally collect special-category personal data.
3) How We Use Data
We use data to:
- Deliver requested bot and dashboard functionality
- Authenticate users and enforce guild/page/command access controls
- Operate subscriptions, activations, trials, renewals, grace periods, and entitlement checks
- Generate dashboards, analytics, status pages, and game/server insights
- Send alerts/notifications configured by guild admins
- Troubleshoot incidents and improve reliability
- Prevent abuse, unauthorized access, and fraud
- Comply with legal obligations
4) Legal Bases (where applicable)
Depending on your location, we rely on one or more of:
- Contractual necessity: to provide requested bot/dashboard/subscription functionality
- Legitimate interests: service security, abuse prevention, diagnostics, and operational integrity
- Consent: where a feature requires optional linking/authorization (for example OAuth linking flows)
- Legal obligation: where disclosure or retention is required by law
5) Automated Decisions and Access Enforcement
The service performs automated entitlement checks and access enforcement, including:
- Determining whether a guild/code remains active based on subscription state
- Applying grace windows and expirations
- Restricting dashboard/bot access where entitlement is inactive or expired
These checks are operational controls for service licensing and security.
6) Data Sharing
We do not sell personal data.
We may share limited data with processors/services required to operate features, including:
- Discord (OAuth, guild/member/context APIs)
- Patreon (OAuth and identity/subscription APIs)
- Nitrado (where server integration features use Nitrado APIs/service metadata)
- Hosting/infrastructure providers
- Game/server integration providers used by enabled features
We may also disclose information where required by law or to investigate abuse/security threats.
7) International Processing
Data may be processed in countries where our infrastructure or third-party providers operate. By using the service, you acknowledge this cross-border processing.
8) Retention
We retain data only as long as needed for service operation, licensing, security, and legal compliance.
Examples:
- OAuth state entries are short-lived and expire quickly
- Auth sessions expire automatically (current target approximately 8 hours)
- Patreon link and entitlement records are retained while needed to manage active/previous subscription lifecycle, audits, and dispute handling
- Guild configuration and operational data are retained while the guild uses the service, unless deleted earlier
- Audit/error/security logs may be retained longer for abuse prevention and incident investigation
When deletion is requested and validated, we remove or de-identify data unless legal or security retention requirements apply.
9) Security Measures
We use reasonable technical and operational safeguards, including:
- Access controls and permission checks
- Session handling controls
- Logging and monitoring for abnormal activity
- Operational restrictions around sensitive actions
No internet service can guarantee absolute security. Admins are responsible for securing their Discord accounts, server permissions, and any credentials they submit.
10) Your Rights
Depending on your jurisdiction, you may request:
- Access to your data
- Correction of inaccurate data
- Deletion of data (subject to legal/security exceptions)
- Restriction or objection to certain processing
To process a request, provide:
- Discord user ID
- Guild ID(s)
- Relevant bot/service context
11) Children's Privacy
Services are not directed to children. Users must satisfy Discord's minimum age and platform requirements.
12) Policy Changes
We may update this policy at any time. We will update the "Last Updated" date when changes are made. Continued use after updates means you accept the revised policy.
13) Contact
For privacy or data requests, contact us via:
- Support Discord:
https://discord.gg/YvPu5ck6GE