English

Zaparo Garrison: Privacy Policy

Last updated 2026-09-26.

Zaparo Garrison collects the following, and nothing else.

WhatSpecificallyWhyShared
App activityA report's reason from a fixed list of six, and a small map of ids the app already has. No free-text field anywhere; A score this user submitted to an app-defined board, when they achieved it, and an optional opaque proof string the app supplies - keyed on their Zaparo ID user id; Every realm's state and history, held under the Zaparo ID that owns it: the town and camps and their map positions, army, stores, works, standing orders, movements, raids resolved by the server, falcon reports and the record beside the rank.; Recorded runs a player uploads through GhostPoolClient: the game, the language and the replay the app recorded (in a word game the word played, each guess and when it was made), keyed on their Zaparo ID user id; Screen views and feature-used events the host app chooses to log; The realm this player built and everything the world does to it: the name they give the realm and its camps, where its town and camps stand on the map, its army, stores, works and research, standing orders, the raids it sent and received, its falcons' reports, and the record beside its rank.; Which applications within this one tenant the account has been seen in. Recorded when an application registers a device or completes a sign-in under its own application id, so `me().apps` can answer it back to the person.Account management, Analytics, App functionality, Fraud prevention, security, and complianceNo
App info and performanceCrash stack traces, ANRs and breadcrumbsAnalytics, Fraud prevention, security, and complianceNo
Device or other IDsAn identifier for the phone, sent with an ad request and with the report that an ad was shown or tapped. It is the advertising identifier only where the app has been declared for it in Play; everywhere else it is an identifier this SDK generates for that install alone, which no other app can read and which dies when the app is removed. Neither is stored as it arrives: the server keeps a keyed hash of it, so the ads cannot be traced back to the identifier.; Crashlytics installation UUID; FCM registration token; Firebase installation ID (app instance ID); The account identifier, and the public half of a key generated in the device key store; The caller's user id and the id of the person being blocked or reportedAccount management, Advertising or marketing, Analytics, App functionality, Fraud prevention, security, and complianceNo
MessagesA name or a message the player typed, sent for a yes-or-no verdict and kept by nobodyApp functionality, Fraud prevention, security, and complianceNo
Personal infoDisplay name - generated by default, editable by the user; Email address, and the name a provider reported, from the sign-in the person chose. Those two and nothing else: a browser provider is asked for `openid email profile` and only the address and the name are read out of what comes back.; The display name and profile picture reference the app writes into a recorded run's label, shown to other players of that app beside the runAccount management, App functionality, PersonalizationNo
Photos and videosProfile photo the user chose to uploadApp functionality, PersonalizationNo

You can ask for your data to be deleted at any time, at the address below.

Contact

Questions about this policy, or a deletion request: privacy@kbsoap.com