Privacy policy
Controller: Ollindy, legal entity name and address to be added, hello@ollindy.com. EU/UK representative (if required): to be added.
This draft describes the data flows planned for EMBERIS and for this website. EMBERIS is not released yet. Items marked "later" are plans, not features that exist today.
1. Age and limited mode
EMBERIS is for players aged 16 and over. After your first run, the game asks for your birth year (no default value). If you are under the age limit for your country, the game runs in a limited mode: fully playable offline, with analytics off, no advertising SDK, no online profile or ranking, and no purchases. We store only the resulting age category on your device. We do not use personalised ads for players under the age limit.
2. This website
- Newsletter. If you subscribe, we store your email address, the time you subscribed and the version of this policy you agreed to. We use it only to send EMBERIS news. To limit abuse we also keep a one-way hash of your network address for a short time. You must be 16 or older to subscribe. You can unsubscribe at any time by emailing us.
- Server logs. Our host, Cloudflare, processes technical request data (such as IP address and browser type) to deliver and protect the site.
- We do not use advertising or cross-site tracking cookies on this site.
3. What the game collects
| Data | When | Why |
|---|---|---|
| Game progress and settings, stored on your device | Always | Run the game. Not sent to us unless stated below. |
| Analytics: random analytics id, app version, device model and OS, session counts, game events, Firebase app-instance id | Only after you tap Allow. Off by default. You can withdraw at any time in Settings. | Improve balance and fix problems. Provider: Google Firebase Analytics (Google acts as our processor). |
| Anonymous account id, generated player name, build snapshot, ranking data (later) | When online features such as rankings and guilds are enabled and you are above the age limit | Show your entry in rankings and keep your profile. |
| Crash reports (later, not yet decided) | Only after Allow | Fix crashes. |
| Purchase receipts (later) | When you buy | Apple or Google process payments. We receive a purchase token to grant the item and never see your card. |
| Advertising id and ad interaction data (later, rewarded ads) | Only after you choose to watch an ad. In the EEA, UK and Switzerland, only after you answer the consent form. | Show and measure the ad you chose to watch. |
We do not use data to track you across other companies' apps or sites, we do not sell personal data, and we do not show an App Tracking Transparency prompt.
4. Legal bases (GDPR / UK GDPR)
Consent for the newsletter, analytics and, where required, advertising. Contract for running your profile and purchases. Legitimate interest for security and fraud prevention. Legal review: confirm
5. Sharing and transfers
We share data with Cloudflare (website hosting and newsletter storage), Google (Firebase, and AdMob later), and Apple and Google Play (payments). Data may be processed outside your country, including in the United States, under the providers' standard contractual clauses or equivalent. Legal review: confirm transfer mechanism
6. Retention
Newsletter email: until you unsubscribe. Analytics event data: retention period to be set months. Online profile: until you delete it or to be set months of inactivity. Legal review: confirm
7. Your rights and deletion
You can switch analytics off at any time and delete your data in the game once online features are live, or by email through the support page. Depending on where you live, you may access, correct, port or erase your data, object to processing, or complain to your data protection authority. Contact: hello@ollindy.com.
8. Children
We do not knowingly collect personal data from children below the age limit in section 1. If you believe a child has used online features or subscribed to the newsletter, contact us and we will delete the data.
9. Security and changes
Data is encrypted in transit (HTTPS/TLS). We will post changes here and update the effective date.
Draft. Effective date to be set at publication.