Privacy Policy — Hold the Sky: Peregrine
1. Who we are
Hold the Sky: Peregrine is an outdoor augmented-reality (AR) sky-defense awareness game owned and operated by Clear Skies.
By playing the Game—including guest play and signed-in play—you agree that Clear Skies may access and process game and operator data as described in this Privacy Policy, including to develop, improve, and refine the Game and related Clear Skies products and services.
Privacy contact: support@holdtheskygame.com
Legal pages:
Privacy ·
Terms
2. Scope
This Policy applies to the Game, related websites, and backend services we use to run the Game (together, the “Services”). It does not cover third-party sites or services that have their own policies (for example Google, Meta/Facebook, or weather providers), except to describe what we receive when you use those features. The providers that receive data from the Game, and what each one receives, are listed in Section 6.1.
3. Short summary
| Topic | What we do |
|---|---|
| Camera | Used on your device for AR gameplay. We design the Game so raw camera images and video are not uploaded to Clear Skies. |
| Location | Used for weather, to name your place, and to build the mission map. The coordinates of the mission area (your location in AR mode, or the place you choose in 3D mode) are sent to Clear Skies servers to generate terrain, scenery and imagery for that area. We do not collect continuous GPS tracks. |
| Accounts | Guest (device-local) or optional Google / Facebook sign-in. |
| Age | Birthday is used only to check eligibility. We store a coarse age band and eligibility receipt—not your full date of birth. |
| Gameplay data | Scores, progress, session/track/gameplay events, and similar data may be processed to run and improve the Game. |
| Optional research | Off by default; only if you opt in while signed in. |
| Sale of personal data | We do not sell your personal information. |
| Kids | Not directed to children under 13. |
4. Information we collect
4.1 Information you provide or create while playing
- Account and profile: display name (from you or your sign-in provider), preferences, onboarding state.
- Age eligibility receipt: after you enter a birthday on the age gate, we do not store the full date of birth. We store only that you are eligible, a coarse age band (for example 13–15, 16–17, or 18+), the age-policy version, and when you accepted it.
- Gameplay content: saves/progress, training or operation results, scores, and similar game records when cloud features are used.
- Support messages: if you email us, the content of your message and contact details.
4.2 Sign-in providers (optional)
If you choose Sign in with Google or Sign in with Facebook, we receive identity information needed to create or restore your account (typically via Firebase Authentication): a stable subject identifier and display name; depending on provider settings it may also include an email address. We map that identity to a Clear Skies operator account ID used as your authoritative cloud identity for the Game. Meta Login receives the information its own login flow sends. The Android build turns off automatic Facebook app-event logging and advertiser-ID collection, so the Game does not send Meta analytics events.
4.3 Guest play
Play as Guest uses a stable identifier stored on your device so local progress can continue. Guest mode is designed as local solo play. Cloud progression, statistics, and cooperative features require sign-in.
4.4 Device, sensors, camera, and AR
To provide AR outdoor play, the Game may access:
- Camera (live AR view)
- Motion / orientation / AR session sensors
- Location (for local weather, a place label and the mission map of that area)
- Network connectivity and ordinary device/app diagnostics
Design commitments:
- Raw camera frames, photos, and video are processed on your device for gameplay and are not uploaded to Clear Skies servers.
- Continuous high-frequency device pose dumps are not uploaded as a product feature.
- We do not use the advertising identifier as a product analytics channel.
4.5 Location and weather
- On device, location may be used to request local weather from Open-Meteo and to derive a place label through BigDataCloud. Both requests are sent directly from your device, so those providers see your IP address. Device-location coordinates are rounded before they are sent; coordinates of a selected remote mission area may be sent at full precision (see Section 6.1).
- To build a mission, the Game sends the latitude and longitude of the mission area to Clear Skies servers, which generate the terrain, scenery and map imagery for that area. Generated map data for an area may be cached so later missions there load faster. Mission-area coordinates are also used by our servers to request map, terrain and satellite data from the providers listed in Section 6.1. When you start a mission in a place that has no generated plate yet, the Game sends the municipality name, a coarse map-cell identifier and the country and subdivision codes to Clear Skies, and our servers send that place information to OpenAI to generate the plate. These requests carry no account identifier. We do not collect street addresses or continuous GPS tracks.
- Precise AR pose used for aiming and rendering is intended to remain on device.
4.6 Gameplay, operator, and product-improvement data
When you use signed-in / cloud features, we may process game and operator data, including for example:
- session start/end and participation in an operational session
- virtual track / threat lifecycle events (spawn, claim, intercept, recovery)
- angles, tracks, outcomes, scores, and similar gameplay events
- coarse cell presence where relevant
- minimized product telemetry such as screen views, UI actions, operation summaries, and performance metrics
By playing, you agree that Clear Skies may use this information to operate, secure, develop, improve, and refine the Game and related products and services.
Optional research samples are a separate preference, default off, and are not sent for guests.
4.7 Technical and log data
When the app or website contacts our servers, we and our hosting providers may process IP address, timestamps, request metadata, authentication tokens, app/version identifiers, and server logs needed for security, abuse prevention, reliability, and debugging.
4.8 Optional team radio
Where an eligible team session is available, Team Radio is optional. Its preference is stored on your device and is off until you enable it. Enabling Team Radio allows the Game to request microphone permission. If you join an eligible team session, enable Team Radio, grant microphone permission, and the configured voice service connects, your microphone audio is transmitted through Unity Vivox to other participants in that session. Vivox also processes the account and channel identifiers needed to connect the session. If microphone permission is denied, an available session can operate in listen-only mode. You can turn Team Radio off to disconnect the voice session.
5. How we use information
- Provide the Game (accounts, saves, sessions, AR gameplay)
- Authenticate you and maintain your operator account
- Personalize lightly (name, progress, settings)
- Safety, integrity, and abuse prevention
- Product development and improvement using game/operator telemetry and, if you opt in, research samples
- Comply with law and enforce our Terms
- Communicate about support, security, or material Service changes
We do not sell your personal information.
6. How we share information
| Recipient | Why |
|---|---|
| Service providers | Hosting, databases, logging/monitoring acting on our instructions. |
| Identity providers | Google, Meta/Facebook, and Firebase Authentication when you choose those sign-in methods. |
| Optional voice provider | Unity Vivox processes the account/channel identifiers needed for an eligible team-radio session when you enable Team Radio and the configured voice service connects. If you also grant microphone permission, it carries your microphone audio to the session participants. |
| Weather and place-name providers | See Section 6.1: Open-Meteo (weather) and BigDataCloud (place label) receive coordinates directly from the app: rounded for device location, or at full precision for a selected remote mission area. |
| Other participants, when an optional session is available | Limited session state may be shared with participants under feature settings—not your home street address. In an eligible team session, participants also receive your microphone audio when Team Radio is enabled, microphone permission is granted, and the configured voice service connects. |
| Legal / safety | If required by law or to protect users, the public, or Clear Skies. |
| Business transfers | If Clear Skies is involved in a merger, acquisition, or asset transfer under continued privacy protections. |
6.1 Service providers and what they receive
This table lists every service provider that receives data from the Game or from our servers, what it receives, why, and whether the data is linked to your account. "On device" means the app calls the provider directly from your phone, so the provider also sees your IP address. "Server" means only our servers call the provider. No provider receives your password.
| Provider | How it is called | What it receives | Purpose | Linked to your account? |
|---|---|---|---|---|
| Open-Meteo | On device | Device coordinates, rounded to a grid of about 1.1 km when the rounding policy applies, and your IP address. | Current weather and astronomy for the mission area. | No. The request carries no account credential. |
| BigDataCloud | On device | Device coordinates, rounded to three decimal places (about 110 m) when the rounding policy applies, the language setting, and your IP address. | A place label for the menu and mission setup. | No. The request carries no account credential. |
| OpenAI | Server | Only when a mission area has no generated plate yet: the municipality name, a coarse map-cell identifier, country and subdivision codes, approximate coordinates of the plate anchor, names and coordinates of nearby map landmarks, and a terrain summary. The generation and check requests also contain terrain reference images and our instructions. For a phone model that Wikipedia does not answer, the request contains only the manufacturer and model name. OpenAI sees our server's address, not yours. | Generating and checking the shared municipality plate; estimating a phone's physical size when the model is not in our reference table. | No. Plates are shared by all players. The requests carry no account identifier. |
| Wikimedia (Wikipedia and Wikidata) | Server | Phone manufacturer and model name. | Phone size lookup. | No. |
| Mapbox | Server, and a public token issued to the app | Our server requests satellite tiles for the mission area with our Mapbox token. The app receives a public Mapbox token from our server when it needs imagery; when the app calls Mapbox directly, Mapbox sees the tile requested and your IP address. | Satellite imagery for the mission area. | No. The token is not tied to your account. |
| OpenStreetMap (Overpass API) | Server | Bounding boxes of mission areas. No player identity. | Roads, buildings, water and landmarks for mission scenery. | No. |
| Amazon Web Services (S3 delivery of Mapzen Terrarium terrain tiles) | Server | Terrain tile zoom and x/y indices derived from the area used for a shared menu plate, plus our server's IP address and request metadata. The request carries no player or account identifier. AWS sees our server's address, not your phone's. | Terrain heights for location-based menu reference images. | No. |
| Copernicus Data Space and Copernicus GLO-30 elevation data | Server | Bounding boxes of mission areas. No player identity. | Terrain height and satellite vegetation data. | No. |
| Geoapify | Server, where enabled | Coordinates of the place being looked up and, for place names, the language setting. | Elevation and place lookups for the recovery area. | No. |
| Google (Firebase Authentication, Google Sign-In and Firebase Analytics) | On device, then server | Only when you choose Sign in with Google: the Google sign-in result and a Firebase ID token. Our server checks it and links it to your Clear Skies account. When you delete your account, our server also asks Firebase to delete your sign-in record. The Android build includes the Firebase Analytics SDK. If that SDK collects data during operation, this may include an app-instance identifier and device and app information sent to Google. Its presence in the build alone does not establish which data is transmitted during a particular session. We do not use it for advertising. | Sign-in, account deletion and potential app analytics/diagnostics. | Yes for sign-in. The sign-in identity is linked to your Clear Skies account; linkage of any Analytics SDK data has not been verified. |
| Meta (Facebook Login) | On device, then server | Only when you choose Sign in with Facebook: the information Facebook Login sends during the login. The Game does not send Meta analytics events. | Sign-in. | Yes, for sign-in. |
| Unity Vivox | On device | When you enable Team Radio in an eligible team session: your account and channel identifiers, and your microphone audio when permission is granted. | Team voice chat. | Yes, for the voice session. |
| Hetzner (hosting) | Server | Every request to our servers, including IP address, timestamps and request metadata for security and reliability logs. | Hosting the game service and the website. | Logs can be linked to a request; see Section 4.7. |
7. Retention
We keep information only as long as needed for the purposes above:
- Account and profile data while your account is active, then deleted or anonymized after deletion requests (subject to technical delays and legal holds).
- Gameplay results / events for the life of cloud features and product improvement, then purged with the account when operator-linked, or retained only in aggregated form.
- Server logs for short operational windows.
- Shared municipality plates and map-data caches are not linked to an account. They stay in the shared game-asset cache until they are replaced or removed.
- Age receipt while needed to enforce eligibility and policy versions.
- Optional research samples while opted in and for a limited research window.
8. Your choices and rights
- Play as Guest (local) or sign in.
- Grant or deny camera and location permissions in Android settings.
- Control optional research preferences where exposed (default off).
- Sign out and delete account from Settings when signed in.
- Contact us at support@holdtheskygame.com for access, correction, or deletion requests.
Depending on where you live, you may have additional rights under local law (for example GDPR/UK GDPR). You may also lodge a complaint with your local data-protection authority.
9. Children
The Game is not directed to children under 13, and we do not knowingly create cloud accounts for children under 13. Our age gate requires a minimum age of 13. If you believe a child under 13 provided personal information, contact us and we will take appropriate steps to delete it.
10. Security
We use reasonable technical and organizational measures appropriate to the risk, including access controls on servers and minimized telemetry schemas. No method of transmission or storage is 100% secure.
11. International transfers
We may process information on servers outside your country. Where required, we use appropriate safeguards for cross-border transfers.
12. Third-party policies
- Google Privacy Policy
- Meta Privacy Policy
- Firebase / Google Cloud terms as applicable to Authentication
- OpenAI Privacy Policy
- Mapbox Privacy Policy
- AWS Privacy Notice (Amazon S3 terrain delivery)
- Unity Privacy Policy (Vivox voice)
- Wikimedia Privacy Policy
- Open-Meteo, BigDataCloud, OpenStreetMap (Overpass), Copernicus Data Space, Geoapify and Hetzner: their own privacy policies apply to the data described in Section 6.1.
- Weather provider terms as used by the client
13. Changes
We may update this Policy. We will post the new version with a new “Last updated” date and, for material changes, provide additional notice in-app or on our site when appropriate. Continued use after the effective date means you accept the updated Policy.
14. Contact
Privacy questions and requests: support@holdtheskygame.com
Web: Clear Skies
Initial product draft for internal and store review — not legal advice.