Privacy Policy

Last updated: June 2026

1. What We Collect

When you use DYMOL, we process the following data on your behalf:

End-user identifiers — user_id values you send via the API (reactions, promo code claims, counter increments, death coordinates).
Gameplay event data — reaction types, counter names and amounts, death coordinates and causes, promo code redemptions.
Developer account data — email address, name (via Clerk OAuth), project names, API usage metrics.
Usage metadata — API request counts per project, aggregated for billing and rate limiting.

2. How We Use Your Data

To provide the DYMOL service — aggregating reactions, validating promo codes, incrementing counters, storing death coordinates.
To display analytics in your dashboard — reaction distribution, counter trends, death heatmaps.
To enforce rate limits and plan quotas.
To improve the service — we may analyze aggregated, anonymized usage patterns.

We do not sell your data or your players' data to third parties.

3. Data Retention

Death telemetry: Automatically deleted after 180 days.
Reactions, counters, promo codes, API usage: Retained until project deletion or upon request.
Account data: Retained while your account is active. Deleted upon account closure.

4. Your Rights

As a DYMOL account holder, you have the right to:

Access your data — request an export of all data associated with your projects.
Delete your data — request deletion of your account and all associated project data.
Object to processing — contact us to discuss specific concerns.

To exercise these rights, email [email protected]. We respond within 30 days.

5. Third-Party Services

DYMOL uses the following third-party services that may process your data:

Clerk — authentication (email, Google OAuth). Clerk Privacy Policy
Unkey — API key verification and rate limiting. Unkey Privacy Policy
Cloudflare — hosting and database (Workers, D1, Pages). Cloudflare Privacy Policy

6. Security

All data is transmitted over HTTPS. API keys are stored encrypted at rest. We apply rate limiting and input validation to protect against abuse. If you suspect a security issue, contact [email protected].

7. Contact

For privacy-related inquiries: [email protected]