Account use involves server-stored account details, password verification data, preferences, saved lists, collections, battles and content you upload or share. Depending on enabled features, the service also processes profile images, invitations, interactions and support messages. Privacy requests submitted by accounts or guests are stored on the server with their account or browser identity, request text, status and replies; only the requester and site owner can view them. When required at registration, Terms acceptance and Privacy Policy acknowledgement are recorded with the policy revision and timestamp. Technical and security records may include IP addresses, request details and account activity.
Unregistered lists, collections, local battles and preferences are stored in your browser. Device-picture libraries are kept on your device or in folders you explicitly link. Browser storage, IndexedDB and cookies support saves, preferences, sessions and the choice to continue without an account. Clearing them can remove saves or access. Registering does not automatically import browser saves; the app offers an import choice.
When enabled, unregistered synced battles and copies of selected lists are stored on the server. A signed browser-identity cookie lets the browser reconnect to its shared battles; it is not a registered account. Other participants can see shared battle data and selected lists. Spectator settings and public sharing can make content visible more widely. Treat invite codes as private until used.
Information is used to operate accounts and requested features, save and synchronise content, apply access settings, maintain security and respond to support requests. The operator must identify and publish the lawful bases, any optional analytics or tracking, and any additional purposes relevant to this deployment. No consent to unrelated marketing is implied by using the app.
The server operator and hosting, proxy or tunnel providers may process traffic and technical data. Their identities, processing locations, international-transfer safeguards and any other recipients must be completed by the operator. Public or shared content can be retained independently by people who view or export it.
Browser-only records remain until removed from that browser. Server retention depends on account-deletion settings, backups, logs and the operator's policies. Battle invite codes become unusable after one use or 48 hours; this does not itself delete the battle or selected-list copies. The operator must state retention periods for shared guest battles, uploaded files, logs and backups. Security measures reduce risk but cannot guarantee absolute protection.
Preferences > Account provides available export and deletion controls. Guest browser-data deletion does not delete server-stored synced battles, and device pictures have separate management and export controls. Clearing cookies can prevent reconnecting to shared guest battles. Contact the operator before clearing site data if you need help with those records. Depending on applicable law, you may have rights to access, correction, deletion, restriction, portability or complaint to a regulator; the operator must provide the relevant process and regulator details.