This policy follows information through ArrowGlide in the order it actually moves: where it enters, what it is used for, who else touches it, where it rests, and how it leaves. Reading the stages in sequence gives a complete picture of our practices.

Stage One — Entry Points

Information can enter ArrowGlide through exactly four routes.

Route A: the gameplay loop. Level outcomes, elapsed time per attempt, retry counts, unlocked content, and the balance of any in-game resources are produced as you play.

Route B: the runtime environment. The device model, chipset class, operating system build, application version, screen geometry, locale, and connection type are read so the game can configure itself.

Route C: failure events. An unexpected termination produces a stack trace, a memory summary, and a timestamp.

Route D: you, deliberately. Anything typed into a support message or attached to it — an address to reply to, a description, an image, an order reference.

No fifth route exists. ArrowGlide asks for no location permission, no contact list, no camera or microphone access, and no health or biometric information.

Stage Two — Purpose Assignment

Each entry route is assigned a fixed purpose before anything is stored.

• Gameplay records serve continuity of progress and balancing of level difficulty.
• Runtime readings serve rendering, compatibility, and performance tuning.
• Failure events serve defect diagnosis only.
• Support content serves the resolution of the matter you raised.

Information gathered for one purpose is not quietly repurposed for another. Where a genuinely new purpose arises, this document is amended before the change takes effect.

Stage Three — Onward Flow

Some information leaves our systems and reaches a service provider. The categories of recipient are fixed:

• an analytics provider, which receives event counts and runtime readings
• a crash reporting provider, which receives failure events
• an advertising provider, where ArrowGlide displays advertisements, which receives an advertising identifier and impression counts
• the app marketplace, which handles distribution and purchase validation

Each recipient is contractually limited to the purpose we specify and publishes its own privacy terms. There is no transfer to advertisers for their own independent use, no sale of player records, and no exchange with data brokers.

Beyond that list, disclosure occurs only where a binding legal demand requires it, or where disclosure is necessary to investigate a security incident or protect someone from harm.

Stage Four — Where It Rests

The bulk of your gameplay record rests on your own device, inside the app's private storage area, which the operating system isolates from other applications. Copies held by us or by our providers rest on managed servers, reached over encrypted connections, behind role-based access controls, with administrative access limited to named engineers. Backups are encrypted at rest.

Servers may be located in a country other than your own. Where information moves across a border, we rely on the transfer safeguards recognised in the relevant jurisdiction.

No arrangement of this kind is perfect, and we make no claim that ours is immune to compromise.

Stage Five — Exit

Information leaves in one of four ways.

• Deletion by you. Removing ArrowGlide from the device erases the local record, including your progress. That step cannot be reversed by us.
• Expiry. Failure events are cleared once the associated defect is closed; support threads are cleared once the matter ends.
• Aggregation. Analytics records are folded into totals from which no single installation can be recovered, at which point they are no longer information about you.
• On request. A deletion request submitted through official support removes the record we hold, subject to anything a tax or fraud-prevention rule requires us to keep.

Standing Rights of the Player

Where the law of your country grants them, you may request access to your record, correction of an inaccuracy, erasure, restriction of a particular use, or a machine-readable copy. You may also withdraw a consent you previously gave, which affects processing from that point on and not before. Requests should be sent through official support and should quote the installation identifier displayed in the game's settings screen, since ArrowGlide holds no name by which to find you.

Age Limitation

ArrowGlide is not designed for and is not directed to children under thirteen, and personal information is not knowingly gathered from them. Where we learn that such information has reached us, it is removed. A parent or guardian may raise the matter through official support.

Amendment of This Policy

Amendments follow changes in the game, in our providers, or in applicable law. The amended text takes effect once published through our official channels, and it replaces the previous version in full.

Point of Contact

Enquiries about any stage described above may be directed to the ArrowGlide support team through the official support channels.