Your data
Privacy policy
Last updated:
This notice covers Droid Tycoon Companion, an independent, unofficial fan project operated by DeityOfDanger (online handle), not affiliated with Epic Games. Contact privacy@dod.me.uk.
Privacy at a glance
Use local tracking without an account, or choose Epic sign-in and cloud saves when those features are available. Visiting the site alone does not create an account or upload your progress. We do not sell your information or use advertising trackers.
Progress stored on your device
Browser local storage holds your manually entered droid ownership, rebirths, upgrades, layouts, collection, game statistics, and save revisions. In local-only mode, progress and imported files stay on your device. People sharing your browser profile share this data.Profile provides JSON export/import and reset controls.
Optional Epic Games accounts
Epic authenticates you; Supabase links a generated companion user ID to your Epic identity. Basic Profile permission can provide your Epic ID and display name. Authentication also processes session tokens, timestamps, and security records. These identifiers are personal data, not anonymous data. We do not request email, friends, or presence through Epic, collect your Epic password, or retrieve your Fortnite island progress.
Optional cloud saves
If you choose cloud saving, Supabase stores your tracked game progress and preferences against your companion user ID, with revision information and timestamps. This enables save/load across devices. Imported progress can be included in cloud saves; background uploads apply only if you enable a synchronization feature. We do not publish player saves.
Use Delete companion account in Profile to remove the companion account and its cloud save. Your Epic account, local progress, and downloaded backups remain. Signing out or resetting local progress alone does not delete server records.
Hosting, access protection, and cookies
Cloudflare processes IP addresses, browser/request information, and security logs to deliver and protect the site. Restricted areas may use Cloudflare Access, whose email PIN login processes your supplied email and access events. Necessary session/security cookies and browser storage support these services and Supabase sign-in. The app has no analytics SDK or tracking pixels; fonts and icons are hosted with the site.
Why we use data
We use data to provide requested features, secure the service, troubleshoot problems, and answer enquiries. Under UK/EU data protection law, we rely on our legitimate interests in operating this companion and supporting its users, or consent where required. There are no automated decisions with legal or similarly significant effects.
Our providers are Cloudflare,Epic Games, andSupabase, plus our email service for correspondence. Their linked notices explain their processing and safeguards for transfers outside the UK/EEA. Information may also be disclosed where legally required.
How long data stays
Local progress stays until reset, browser-data removal, or browser eviction. Account records and cloud saves stay while needed to provide your account, or until deletion. Correspondence is kept only as needed to resolve requests and meet legal obligations. Necessary security records follow provider retention settings and legal requirements. We will specify retention before enabling operator-run recovery backups; backup copies would expire separately from live data.
Your choices and rights
Depending on applicable law, you may access, correct, delete, or receive a copy of your data, restrict or object to processing, and withdraw consent without affecting earlier lawful processing. Use Profile's controls or contact privacy@dod.me.uk. We may verify ownership, but never ask for passwords or tokens. You may complain to your local regulator, including the UK's ICO.
Parents and guardians can contact us about a child's information. Epic's age restrictions and consent requirements still apply. External sites have their own privacy practices.
Changes to this notice
We will update this notice when data handling changes, explain material changes before they apply, and obtain consent where required.