Android and iOS

Archery Duel privacy policy

Effective and last updated .

Rectfy operates Archery Duel / Rectfy Archery Duel. This policy covers the Android and iOS game with package or bundle ID com.rectfy.archeryduel. It does not cover Dragon Run or other Rectfy apps.

For privacy questions, email teamrectfy@gmail.com.

Guest identity and data on your device

You can play without an email address or password login. The game creates a random guest identity and an authentication secret on your device. It stores these locally, together with your nickname, settings, tutorial progress and records of games against local bots.

The guest identity lets our service recognize a returning player. Server records are linked to a player ID derived from that identity, so these records are not anonymous.

Your nickname may be visible to opponents. Please do not include your real name, email address or other personal information in it.

Online check-in and usage analysis

You can play against bots offline without sending anything to our service. The first time you choose online play, the game explains what online play sends and asks you to choose Continue or Stay offline. Offline play alone does not create a profile on our service.

After you choose Continue, the app checks in with our service after launch, when you return after a long absence, and when you request online play. The check-in sends your derived guest player ID and authentication proof, nickname, platform, app build, time-zone offset and local bot results. We use these to recognize returning players, initialize matchmaking and skill ratings, check supported builds, and analyze activity and player retention.

Our service stores guest player records, activity days, skill ratings and match records in a Postgres database. It also records aggregate player, matchmaking-search and match counts. Rectfy's own service performs this usage analysis.

Online play, IP addresses and sharing

Online matchmaking and friend rooms handle room requests, gameplay inputs, match results, ratings, and diagnostics about connections and game-state desynchronization. Players can send preset emoji reactions. There is no free-text chat.

Our service and game servers receive your IP address to communicate with your device and apply abuse limits. We send player IP addresses to Edgegap to place a nearby match server. An IP address can reveal approximate location. Deployment settings sent to Edgegap also contain player nicknames.

The game does not request GPS location.

Device checks for fair play

After you choose online play, the app may ask Google Play (Play Integrity, on Android) or Apple (App Attest, on iOS) to confirm that it is a genuine copy of the game running on a genuine device. Google or Apple returns a signed result, which our service checks. The request is bound to a one-time challenge from our service and a hash of your guest player ID; the player ID itself is not sent to Google or Apple.

Our service stores the outcome with your guest account: the platform, the result and its time, and on iOS a per-install App Attest public key, its key identifier, a counter and Apple's attestation receipt. The iOS app may also include an Apple DeviceCheck token, which our service does not currently use. We use device checks only for security, fair play and abuse prevention, not for advertising. Deleting your account removes these records from our service.

Service providers and international processing

  • Railway hosts our matchmaking service and player database in Singapore. It processes the service data described above. Read Railway's privacy policy.
  • Edgegap runs match servers and deployment services. Match-server locations vary with placement. It receives player IP addresses and nicknames as described above and processes online-match traffic on its servers. Read the privacy policy in section 14 of Edgegap's terms.
  • Google runs Firebase Crashlytics and Firebase Analytics, which receive the crash reports and usage data described above, and Google Play performs Android device checks. Google also processes email sent to our Gmail support address. If you email us, we receive your email address and the information you include. Read Google's privacy policy.
  • Apple performs iOS device checks through App Attest. Read Apple's privacy policy.

These services can process information outside your country. We do not promise that all data stays in your country.

Advertising, purchases, crash reports and analytics

The game has no ads, no purchases, no advertising identifiers and no advertising or cross-app tracking.

The game uses two Google services, Firebase Crashlytics and Firebase Analytics, to find crashes and to understand how the game is played. They run from launch, whether or not you choose online play.

When the game crashes or hits an error, Crashlytics sends a report. It contains the error and where in the game's code it happened, recent screen changes and the kind of duel in progress, the app build, your device model and operating system version, memory and storage figures, and a random installation identifier. Crash reports are kept for 90 days.

Firebase Analytics records how the game is used:

  • when the app is opened and updated, and how long sessions last;
  • which screens are shown;
  • when duels start and end, with their kind (tutorial, practice, bot, quick match or friend room), arena, result and length.

It uses a random app-instance identifier and a Firebase installation identifier and, on iOS, the identifier for vendor. Google estimates your approximate location (country, region and city) from your IP address. Analytics data is kept for 14 months.

We do not send your player ID, nickname, room codes or match identifiers to Firebase, and Firebase's identifiers are not linked to your guest account. Firebase does not collect your device's advertising identifier, and this data is not used for advertising.

Google processes this data for us as a service provider and may process it outside your country. Read Google's privacy policy and Firebase's privacy information. Advertising and children's disclosures in policies for other Rectfy apps do not apply to Archery Duel.

Security and data in transit

HTTP requests to our service use HTTPS. Real-time UDP gameplay packets are authenticated but are not encrypted. Authentication does not prevent someone who can observe the network traffic from reading those gameplay packets. Not all game data is encrypted in transit.

How long data remains

Guest player rows, activity days, match history and device-check records currently have no verified automatic expiry. They remain in our player database until you delete your account or we remove them.

Firebase crash reports are kept for 90 days and Firebase Analytics data for 14 months.

The match service's round-input log cleanup is configured to prune files older than two days, or sooner if the total files exceed 2 GB. Cleanup runs on a ten-minute cycle. These temporary files can disappear earlier on redeployment.

That cleanup applies only to those round-input files. It is not a two-day deletion guarantee for player database records, infrastructure logs, backups or Edgegap deployment records.

We have not confirmed the specific retention periods that apply to our Railway platform logs and database backups or to Edgegap deployment records. We have also not confirmed a fixed retention period for support email. This policy does not promise exact deletion periods for those records.

Deleting your data and privacy inquiries

In the game, open Settings > Profile > Delete account and data and confirm. This permanently removes your online profile, nickname, rating, activity days, match history and its round files, name overrides, moderation entries and audit entries about your account, and device-check records from our service, and clears the game's local progress and settings on your device. If the request fails, the game keeps your credentials so you can retry, and reports success only after the deletion has finished.

To stop old requests from restoring the account, our service keeps a one-way SHA-256 fingerprint of the deleted guest ID indefinitely. Aggregate counts and other players' own records remain. Railway and Edgegap logs and backups can still contain older data; we have not verified fixed deletion deadlines for them.

Deleting your account does not delete Firebase crash reports or analytics, because they are not linked to your guest account. They expire after 90 days (crash reports) and 14 months (analytics), and uninstalling the game removes the Firebase identifiers from your device.

Uninstalling the game does not delete server records. After deletion, a new guest account is created only if you later choose online play again.

You can also send privacy inquiries, including questions about access or deletion, to teamrectfy@gmail.com. A nickname alone cannot reliably identify or authenticate a guest record, so the in-app deletion is the dependable route. Do not send a password, raw guest secret or authentication proof by email. We do not promise a guaranteed response deadline.

Age and audience

The game's stated audience is players aged 13 and older. A store age rating does not verify a player's age. The current game does not have a verified age gate or parental-consent flow.

If you are a parent or guardian with a concern about a child's information, contact teamrectfy@gmail.com. This contact does not promise an implemented child-data identification or deletion process.

Changes and contact

We will update this page when these disclosures change and show the last updated date above.

Operator: Rectfy. Privacy contact: teamrectfy@gmail.com.

Back to Rectfy privacy policies