Singularity is playable without an account. This policy explains what stays on your phone, what our services receive, and how to control collection. Version 2.00 changes our gameplay measurement. Earlier versions are described separately below.
You control collection. Usage statistics contain totals, not a player ID or event history. You can stop them in Settings. Advertising choices are separate: Google manages ad consent, and iOS asks before advertising tracking. Singular install attribution starts only when those advertising permissions allow it.
| Recipient | Information | Purpose |
|---|---|---|
| VRTCL | Daily usage counters, coarse score and progression groups, app version and build. No install, session, run or advertising ID, purchases or ad earnings in this route. | Improve the game. |
| Google AdMob | Ad interaction, device and diagnostic information under Google's policy and the applicable advertising choices. | Show ads and measure their performance. |
| Singular | Advertising ID and technical install information, only after tracking is allowed. We configure install attribution, not gameplay or revenue postbacks. | Measure advertising installs. |
| Unity Ads | Attributed-install postbacks from Singular for our Unity campaign. | Measure campaign delivery. |
| Apple | Purchases, Game Center scores and aggregate SKAdNetwork attribution through Apple's services. | Provide those features. |
Any third party receiving personal information from the app must provide the same or greater protection stated in this policy and required by Apple's App Review Guidelines, including security, limited purposes and respect for your privacy choices. The information each provider receives is described here; their privacy policies explain their processing.
The phone counts activity before sending it. It sends a UTC calendar day, app version, build and a closed set of counters: daily activity, first observation, returns on days 1, 7 and 30, sessions and whole session minutes, runs completed or interrupted, and first onboarding milestones. Scores, levels, run durations and revives are sent only as groups of counts, not exact results or a run history.
The first-observation day used to calculate returns stays on your phone. It is not sent to VRTCL and is not proof of the date you installed the game. It resets on the first use after 365 days. We do not create a persistent statistics identifier or combine this data with advertising data.
Each delivery has a fresh random token so a retry is not counted twice. It identifies only that delivery. VRTCL keeps one-way fingerprints of the token and request until the UTC day ends and the next maintenance step removes them. Different deliveries cannot be joined using those tokens. The payload is added immediately to daily totals, then discarded. We keep no individual payload history.
Internet delivery exposes an IP address while the connection is handled. The statistics route does not retain that address or request access logs, and strips cookies and advertising credentials. Other requests, such as our public update-check page, may have ordinary security logs.
Our reports hide cells below 10 and exclude TestFlight and unclassified builds from public-player metrics. Statistics are partial: players who opt out, or whose queued report expires while offline, are not counted. They do not identify individual journeys or connect a paid install to later play.
For US, UK and French App Store storefronts, statistics start after the notice is shown, subject to any previous refusal. The limited purpose is improving this game. Other or unknown storefronts remain off unless you enable statistics in Settings. The storefront check stays on the phone. We do not treat this configuration as a worldwide exemption from consent requirements.
Settings control: open Privacy & Credits and turn on Stop usage statistics. Collection stops, pending delivery is cancelled where possible, and unsent totals are cleared. Turning the switch off explicitly enables statistics again. Play remains available. Already received aggregate totals cannot be linked back to you or individually removed.
Earlier versions, including build 118, could send events linked to a random install ID, including run and session details, product IDs and ad earnings. Version 2.00 retires that delivery path. If your phone still has its old deletion capability, the game uses it only to request erasure of those records, then retires it. An offline deletion request is retried later. It is not reused as a statistics identifier. Server backups may retain older records until their normal expiry.
Your scores, progress, settings, cosmetics and tutorial state stay on your device. There is no VRTCL player account or cloud progress backup. Deleting the app removes locally stored progress, settings and pending statistics. It does not remove data already held by advertising partners.
Google AdMob provides banners, ads between runs and rewarded ads you choose to watch. Google's consent form appears where required and can be reopened through Manage Ad Consent where Google offers that control. The game also waits for iOS's tracking decision before starting ads. Declining tracking does not prevent play or permit access to your advertising ID.
Google's software can collect identifiers, approximate location, ad and app interactions, and crash or performance diagnostics, according to its configuration and your choices. Contextual ads may still appear after tracking is declined. See Google's partner-site privacy information. Remove Ads stops banners and between-run ads; rewarded ads remain available by choice.
Campaign measurement in version 2.02 (125) is a new, optional scope. This candidate is not the public App Store release. Version 2.01 (122) continues to use the install-attribution behavior described below. TestFlight does not send campaign measurement through this new integration.
The new Share campaign measurements switch starts off, including for players who previously allowed tracking. In an approved App Store release, sharing requires this switch, iOS tracking permission, advertising consent and usage statistics to be enabled while the app is active.
With those permissions, Singular receives launch and session information, device identifiers and network information used for attribution, AdMob impression revenue with currency, placement and precision, and verified Apple purchase transaction and product information. These records can be linked to your device. We do not send your name, email, payment card information or an identifier from anonymous gameplay statistics. We do not join past anonymous history to advertising records.
Turning off Share campaign measurements, stopping usage statistics, withdrawing required advertising consent or revoking iOS tracking permission stops future app-initiated Singular reporting. Historical refused events and purchases are not replayed after permission changes. Play remains available. Apple processes purchases; Singular measures advertising performance. Records already delivered are subject to the provider's retention and deletion process. This does not promise deletion of provider records when a local switch is turned off.
Singular starts only in an App Store build while the game is active, iOS tracking is authorized, and Google's consent permits ads. It is suspended when the game leaves the screen and does not restart after tracking is withdrawn. Clipboard attribution is disabled. We do not send Singular gameplay events, purchases, revenue or VRTCL statistics identifiers. See Singular's privacy policy.
Our Unity campaign is configured for install postbacks from Singular. We do not configure gameplay or revenue postbacks. See Unity's privacy policy. Apple's aggregate SKAdNetwork attribution is separate and does not use your advertising ID.
Versions through 1.99 could send the advertising ID and Apple's signed download record to VRTCL after tracking permission. Version 2.00 does not use that route. Earlier click identifiers are encrypted and expire after 24 hours, with removal on the next maintenance run. The signed record was checked, not retained. A local Apple download check in newer builds is not sent to VRTCL.
Apple processes purchases and the game verifies delivery on your phone. VRTCL does not receive payment details through the statistics route. Financial reports from Apple and Google are separate from gameplay statistics. Game Center receives scores if you use it; your Game Center settings control sharing. VRTCL does not receive your Game Center name or ID through statistics.
Apple may provide crash reports if your iOS developer-analytics setting permits it. AdMob's diagnostic collection is covered by Google's policy. Our public update check sends no player ID.
Aggregate statistics are removed after 365 days. Delivery fingerprints expire at UTC day change on the next maintenance run. Offline queued statistics are discarded at the next UTC day change when the app runs. Advertising partners and Apple apply their own retention policies.
You can stop statistics, change Google's ad consent, or revoke tracking in iOS Settings, Privacy & Security, Tracking. These controls are independent. You may also have rights to access, correct, delete or object to personal information under applicable law. Contact us about those rights or earlier records. We do not request extra identity just to attach it to aggregate totals.
We do not sell usage statistics or export them for advertising audiences. The statistics route excludes contacts, precise location, typed text and raw touch coordinates. Our games are for a general audience and are not directed at children under 13. Contact us if you believe a child supplied personal information. Providers may process information outside your country, including in the United States.
If you email support, we receive the address and information you choose to send. We use it to answer your request and handle follow-up. Our support mailbox uses Google's email service. Please omit passwords and payment details. The public Ask VRTCL form answers from published support information; it does not send questions to an AI model or the company's agents. Ordinary website requests may appear in security logs, as noted above.
VRTCL publishes Singularity. For privacy questions or requests, email VRTCLsports@gmail.com. Apple's Standard EULA governs use for this app.
We update this page and its date when handling changes. Significant changes also trigger a new in-game notice.