Privacy Policy

Hunter Thomas LLC operates VYRDL, including the mobile game, the playable web app and the VYRDL website. This notice describes the current services, including the version 1.0.47 testing edition. Features and purchases can differ by platform and availability.

For privacy requests or help, email chase@hunterthomasllc.com. Visit VYRDL Support.

Information we process

• Accounts and sign-in. Firebase Authentication provides guest and signed-in accounts. We process an account identifier and profile information such as your display name. If you use Google or Apple sign-in, we receive the account information that provider makes available, such as your name and email address. A guest account still has an identifier.
• Sign-in provider data. The Google Sign-In service may process your phone number, approximate location, usage details and other information used to authenticate and protect your account or measure its service. Google processes this data as part of sign-in; VYRDL does not ask for your phone number or access your phone address book. Email/password sign-in sends the credential to Firebase Authentication.
• Play and social features. We store game progress, cloud saves, statistics, daily results, multiplayer games, lobby membership, friend connections, blocks, and other information you submit through available game features. Local preferences and saved games also remain on your device. Other players can see information shared through multiplayer, friend and leaderboard features, such as your display name, game activity and results.
• Analytics and diagnostics. Google Analytics for Firebase measures app and website use, including sessions, game starts, completions and other interactions. Native Firebase Crashlytics receives crash and error reports. These services process app or installation identifiers, device and software information, usage events and diagnostic details. Google Analytics also derives approximate location from IP addresses; this does not require access to your device's location services. We attach your VYRDL account identifier to analytics and native crash reports, so these reports can be associated with your account.
• Purchases and unlocks. Where purchases are available, RevenueCat and the relevant payment provider process purchase and entitlement information associated with your account. Mobile payments use the app store; web checkout uses RevenueCat and Stripe. We store unlock and purchase records to provide and restore access. We do not receive your full payment-card number. The iOS testing edition may show products before purchasing is available.
• Notifications. If you allow notifications, we process a push token and notification preferences to deliver game notifications using Expo and platform notification services. You can turn notifications off in your device settings.
• Feedback and support. When you send feedback, we process your message, an optional screenshot, game and app context, platform, version and account information. Offline feedback can be queued on your device and sent later. Email support includes the information you choose to send. Do not include passwords, payment-card details or other sensitive information in feedback or screenshots.
• Sharing. When you request a share video, the service processes your account identifier, replay content and rendering instructions on its servers and stores the render job and resulting video for delivery. The Share Center then stores downloaded videos on your device or in browser storage. If you choose to export or share content, the destination app or service receives what you share and applies its own privacy practices.
• Website and service requests. Hosting and backend providers receive technical request information, which can include IP addresses, browser or device information, timestamps and requested resources, for delivery, operation, security and troubleshooting. This is separate from saved game data.

Why we use information

We use this information to operate accounts and games, synchronize progress, connect players, provide purchases and notifications, respond to support requests, understand usage, diagnose errors and protect the service. The current app does not display AdMob ads or use an advertising SDK to serve targeted advertisements. Analytics and the partner promotions described below still involve data processing; an absence of ads does not mean an absence of collection or sharing.

Service providers and partner promotions

Providers supporting these features include Google/Firebase for authentication, databases, storage, hosting, backend functions, analytics and native crash reporting; Google and Apple for sign-in and mobile platform services; Expo for push delivery; and RevenueCat, app stores and Stripe for purchases where available. They receive the information needed for those services. See Firebase privacy information, Google's privacy policy, Apple's privacy policy, Expo's privacy policy, RevenueCat's privacy policy and Stripe's privacy policy.

Partner promotions: qualifying partner-code claims can record your name, email address and claim time for the promotion partner. While an associated raffle event is enabled, a verified, non-guest sign-in can also record your name, email and entry time for the partner's eligibility matching, without a separate code redemption. These records can be made available through a partner feed or sent to the partner's configured service. Promotion availability changes; this notice does not mean an event is currently active. Contact us about a promotion record or a request to remove it.

Administrator tools: an optional, restricted theme-generation tool sends the administrator's prompt to Anthropic to create game artwork settings. This is not a general player chat feature and ordinary gameplay is not submitted to that tool. Anthropic privacy information.

We may also disclose information when required by law, to address fraud or security issues, or in connection with a business transfer. Links and sharing destinations outside VYRDL have their own policies.

Cookies and local storage

The website and playable web app use browser storage and Google Analytics. Cookies and similar identifiers can support measurement; local storage and IndexedDB support saved state and other app features. The native app uses local storage and provider-generated identifiers. Browser privacy settings can restrict cookies or storage, but doing so can affect sign-in and saved progress. A browser analytics opt-out does not control native app analytics.

Account deletion and data requests

You can start account deletion from the app's Settings using Delete Account, or request account and data deletion by emailing chase@hunterthomasllc.com. Include “VYRDL deletion request” and the account email or display name needed to identify your account. Do not send your password. We may need to verify that the account belongs to you.

The current in-app flow deletes the sign-in account and attempts to remove the user profile, cloud-save documents and specified local data, and to mark you as departed from multiplayer games. It does not guarantee removal of every stored record. A failed cleanup step can leave data behind even when the sign-in account is deleted. Multiplayer history can retain your display name marked “(left)”. Other records, including friend or lobby records, daily results, push tokens, feedback, promotion claims, share-video jobs, purchases, analytics, diagnostics and service logs, are not all removed by that flow. Email us for review and follow-up removal of remaining personal information.

Updated account-removal service

We are preparing a server-managed removal flow for an updated testing build. It is not included in the existing 1.0.47/build 10 iOS package. When this flow is enabled, it removes attributable account, game, social, notification, feedback, share-render and promotion records from our service, and removes the Firebase sign-in account after the required cleanup succeeds. A failed or incomplete cleanup remains pending and can be retried while the same account's authenticated session is available. If that session is lost or expires and the app cannot resume removal, contact support for help. Shared game records retain other players and non-identifying game state. Older shared records whose account identifier was already removed can retain a display name that we cannot reliably attribute to your account.

Records kept after this updated removal: a restricted account-removal record retains the old account identifier and removal status/times to prevent delayed activity from recreating the deleted account. Restricted purchase-restoration records retain a hashed account identifier, product and store identifiers, content-access grants, ownership status and last event time so that valid purchases can be restored and refunded or transferred purchases are not treated as still owned. These purchase records do not retain your name, email address, payment amount or complete purchase event history. They are pseudonymous, not anonymous: a payment service can supply the old account identifier and allow us to associate its hashed record.

These restricted removal and purchase-restoration records have no automatic expiry. Temporary information needed to complete a pending removal, such as a verified email address or device tokens, is removed from the removal record when cleanup completes. Copies already held by promotion partners, analytics, diagnostic, payment and backup providers require their separate handling; this flow does not erase every external copy. Contact us for help with remaining information. If an account is linked to Apple and the required Apple authorization revocation cannot be completed, the updated flow remains blocked instead of reporting successful removal.

Deleting an account does not itself cancel an app-store or web subscription. Manage a subscription with the provider where you purchased it. Payment providers, other players and recipients of content you shared may hold their own records.

Retention

Retention differs by record and provider. Account and game records can persist until removed; shared game history and the additional records described above may remain after account deletion. Provider-managed analytics, diagnostic, payment and backup records follow their applicable service settings and obligations. We do not promise that account deletion immediately erases all copies or specify an unverified universal retention period. Contact us about retention or deletion of a particular record.

Your choices and privacy requests

You may contact chase@hunterthomasllc.com to request access, correction, a copy, or deletion of your personal information, to withdraw consent where processing relies on consent, or to raise an objection or privacy complaint. Available rights and exceptions depend on your location and applicable law. We will consider requests under the applicable requirements and may verify your identity. You can contact us at the same address to appeal our response or contact the relevant data protection authority.

Age boundary

VYRDL's existing service policy is for adults age 18 and over, or a minor using the service with a parent or guardian's consent. We do not knowingly solicit personal information from children. If you believe a child has provided personal information without appropriate permission, email chase@hunterthomasllc.com so we can investigate and address the account and records. This notice does not represent that the app technically verifies a user's age.

Security and updates

No online transmission or storage system is guaranteed secure. Please protect your sign-in account and avoid sharing sensitive information through game content or support. We may revise this notice as the service changes and will update the date above.

Contact

Hunter Thomas LLC
chase@hunterthomasllc.com
1423 Barberry Drive
Terrebonne, OR 97760, United States