Flag Spin Royale Privacy Policy

Last updated: October 26, 2026

Last updated: October 26, 2026
App: Flag Spin Royale (com.asiansparrow.flagspinroyale)
Publisher: Asian Sparrow LLC

This policy explains what Flag Spin Royale stores on your device, what its advertising and purchase services receive, and how optional live-chat connections, local blocking and user-submitted safety reports work.

Privacy Policy · Terms & Conditions

The short version

  • No in-game account registration. Progress, coins, settings, stats and Name Picker entries are saved locally. Google Play manages purchase ownership, and RevenueCat uses an anonymous SDK App User ID to manage entitlements.
  • Ads come from Google AdMob. Google may collect identifiers, IP address, approximate location, device information and app/ad interactions. The app uses Google’s consent service for applicable ad choices; declining personalized ads does not necessarily eliminate all service data processing.
  • Two independent one-time purchases. Remove Ads removes automatic interstitials; optional rewarded ads remain. Stream Mode unlocks Android streaming features separately. RevenueCat receives purchase identifiers/history and technical service data. We do not receive your card or bank details.
  • Stream Mode is optional and paid. Ordinary chat is processed in session memory. Live moderation lets you hide content and block users locally. If you explicitly submit a report to an available reporting service, selected message/user evidence goes to Asian Sparrow’s private safety queue. Your chosen platform, relay and screen-sharing service have their own data handling, and viewers can see anything you broadcast.
  • No separate general-purpose analytics SDK is configured. Advertising and purchase SDKs still process service data. The app does not request precise location, camera, microphone or contacts access.
  • The game is for ages 13 and up. We do not sell your personal information for money.

Where each kind of information goes.

Progress, coins, XP, unlocks, settings, stats

Where it goes: Your device only

Why: To run the game and remember your progress

Names and items typed into Name Picker

Where it goes: Your device only

Why: To run Name Picker

Twitch channel, YouTube API key/video and relay endpoint

Where it goes: Saved locally; connection/request details go to the selected service

Why: To connect the creator-selected chat source

Live chat messages (usernames and text)

Where it goes: Session memory and on-screen display; your screen-sharing service may broadcast them

Why: To show messages and apply in-game effects

Local blocked users and hide-feed preference

Where it goes: Your device; local records include platform/scoped user identifiers, a user-key hash and display label

Why: To remember and apply your moderation choices

A report you choose to submit

Where it goes: Asian Sparrow’s private WordPress operator queue and its hosting/database providers

Why: To assess a selected content/user concern and take an explicit safety action where appropriate

Publisher block hashes and rate-limit buckets

Where it goes: Publisher block hashes are public to app clients; keyed network buckets remain private to the reporting service

Why: To enforce publisher blocks and limit report abuse; hashes are not a guarantee of anonymity

Advertising ID, IP address, approximate location, device info, ad interactions

Where it goes: Google (AdMob)

Why: Ads, ad measurement and fraud prevention

RevenueCat SDK App User ID, purchase records and technical request data

Where it goes: RevenueCat; Google Play processes store transactions

Why: To deliver, verify and restore purchases and operate the service

Payment details

Where it goes: Google Play only

Why: To take payment. We never receive them.

Who we are

Flag Spin Royale is a physics game for Android made by Asian Sparrow LLC, a creative digital studio based in Fair Oaks, California, USA (“Asian Sparrow”, “we”, “us”). We are responsible for the limited personal information described in this policy (under European law, we are the “controller”).

This policy covers the Flag Spin Royale app only. The third-party services described below (Google, RevenueCat, Twitch and YouTube) have their own privacy policies, which we link to so you can read them.

What stays on your device

Flag Spin Royale has no in-game registration or developer-operated progress cloud. Android automatic app backup is disabled in the app manifest. The game saves the following in local WebView storage:

  • your game progress, tournament history, XP and level;
  • your virtual coin balance and unlocked cosmetic arenas and trails;
  • your daily prize spin timer and your stats;
  • game settings and your acceptance of our Terms; Google’s consent service separately manages its consent state;
  • names or items you type into Name Picker;
  • if you use Stream Mode, the Twitch channel, YouTube Data API key and video ID or URL, relay address and stream preferences you enter;
  • your local blocked-user list (platform, scoped user identifier, display label and hashed user key) and whether you hide the live feed.

Game code does not upload your progress or Name Picker list to an Asian Sparrow server. Creator connection details are sent to the selected service when you connect; the app does not include configured API keys, relay/video URLs or settings in a safety report. In normal play, Reset progress clears local progress and creator settings while preserving the recorded Terms acceptance and moderation preferences, including local blocks. Manage individual blocks in Live moderation, or clear Android app storage to remove local moderation records. In a temporary review or unconfirmed session, Reset and moderation changes affect only the temporary copy. Reset does not delete Google consent state, RevenueCat SDK identity/cache, provider-held transactions or previously submitted reports. Clearing Android app storage or uninstalling removes the app’s local data; it does not delete provider-held purchase records or reports already received by the safety service. We cannot restore a deleted local progress save.

Ads (Google AdMob)

Regular game modes are free to play. Without verified Remove Ads ownership, each unique completed regular game, including Name Picker, creates one automatic full-screen interstitial opportunity at the result break. Demo matches do not. Consent eligibility, configuration, connectivity, availability and SDK success determine actual display. Optional rewarded ads can grant in-game rewards when Google confirms the reward was earned and the ad closes. Remove Ads suppresses automatic interstitials only; optional rewarded ads remain.

What Google may collect

When the Google Mobile Ads SDK is initialized, requests an ad or shows an ad, it may collect:

  • device identifiers, including your Android advertising ID, app set ID and, where applicable, other device/account-related identifiers;
  • your IP address, and an approximate location derived from it (not your precise GPS location);
  • device information, such as device model, Android version, language and screen size;
  • app/ad interaction data, such as app launches, taps, video views, which ads were shown, and whether a rewarded ad was completed;
  • technical, diagnostic and performance data used to operate and troubleshoot the ad service.

Google uses this information to deliver ads, measure how ads perform, limit how often you see the same ad, detect and prevent fraud and abuse, and, if you allow it, show ads that are personalized to your interests. Google handles this information under its own policies. To learn more, see How Google uses information from sites or apps that use our services.

Consent and personalized ads

The app uses Google’s User Messaging Platform to request current consent information and show an available required message. Game code initializes the Google Mobile Ads SDK and explicitly prepares or shows ads only after that service confirms ads may be requested. The consent service itself can process information needed to obtain and manage your choices. Available choices and ad treatment depend on region, age/audience settings and the configured message. Declining personalized ads does not necessarily eliminate all ads or all service data processing.

Use Settings → Ad privacy choices to request the Google privacy-options form when available. If it cannot open, try again or contact support. Android also provides advertising-ID and privacy controls; names and availability vary by device.

Purchases (Google Play & RevenueCat)

The current app offers two independent one-time products when configured and available: Remove Ads and Stream Mode. Remove Ads removes automatic interstitials only; Stream Mode unlocks integrated streaming in the Android app. There are no app subscriptions or coin packs. Google Play processes payment and shows localized prices. We do not receive card or bank details, but may access limited order information for support, accounting and tax through Google Play.

We use RevenueCat, Inc. to verify the two entitlements independently and support Restore. The SDK can connect when initialized, before a purchase, and on purchase, Restore or refresh. It processes:

  • an SDK-generated anonymous App User ID, a persistent purchase-management identifier; the app does not set a customer name/email or create a game login, but the identifier can be associated with transaction history and is not a guarantee of legal anonymity;
  • purchase and transaction records, such as the product ID, purchase token, price, currency and purchase dates;
  • basic technical details needed to handle the request, such as app version and Android version. As with any internet service, RevenueCat’s servers also see your IP address when the app connects.

RevenueCat provides purchase-management services on our behalf. See the RevenueCat Privacy Policy. Access requires the active matching verified entitlement; pending/cancelled payments do not unlock a feature. Settings → Purchases & Restore uses the native store flow. Reset progress does not revoke a purchase or delete provider-held transaction records.

Stream Mode & creator connections

Stream Mode requires its separate one-time Android purchase and verified ownership, except for an explicitly authorized temporary review session described below. The creator selects Simulator, Twitch, YouTube or Relay and can end Stream Mode. Desktop OBS/browser access is unavailable. The Game does not capture or upload your screen, microphone or camera; screen sharing is controlled by the broadcasting app you choose.

Twitch

If you enter a Twitch channel name, the app connects to Twitch’s public chat for that channel in read-only, anonymous mode. It does not sign in to any Twitch account and cannot post messages. It receives the same public chat messages (usernames and message text) that any viewer of that channel can see. Twitch’s Terms of Service and Privacy Notice apply to Twitch and its content.

YouTube

If you choose YouTube, you supply your own YouTube Data API key and the ID or URL of a live broadcast. The app uses YouTube API Services to read the public live chat messages of that broadcast. It does not sign in to your Google or YouTube account and does not access any private account data.

Your API key and video ID are stored locally on your device and are sent to Google as part of requests to the YouTube API over HTTPS. The key starts hidden in the setup form; Show key deliberately reveals it and Hide key masks it again. Masking does not encrypt the stored key. Google may log requests, including your IP address, under its own policies, and requests count toward your key’s quota. Keep the key hidden while screen sharing.

YouTube API Services

By using the YouTube feature of Flag Spin Royale, you agree to be bound by the YouTube Terms of Service. The Google Privacy Policy applies to information processed through YouTube API Services.

How chat messages are handled

Chat usernames/text, source user/message identifiers and Viewer Draw names are processed in bounded session memory to apply effects, display content and provide moderation controls. External tips, gifts, memberships and subscriptions receive the same gameplay treatment as ordinary chat; they do not buy stronger boosts, shorter cooldowns or extra draw entries. The app does not continuously upload chat to Asian Sparrow or save a full chat transcript. A selected report you explicitly submit is the limited exception described below. The selected platform/relay may retain data under its own policies. If you screen-share, your broadcasting service and viewers can receive the displayed content.

Remember that a broadcast is public. Anything on your screen while you stream, including chat messages and names you type into Name Picker, is visible to your viewers and is subject to the rules of the platform you stream on.

To remove your normal saved channel name or API key, use Reset progress outside a temporary review/unconfirmed session, clear the app’s storage in Android settings, or uninstall the app.

Relay and creator controls

Relay connects to the endpoint and bridge software you supply. A remote endpoint must use wss://. Unencrypted ws:// is accepted only for an explicit same-device localhost, 127.0.0.1 or [::1] address; localhost is pinned to 127.0.0.1. This local hop stays on the device. The bridge operator controls any separate external connections, can receive connection metadata and handles the chat data sent by its bridge. Relay URLs containing embedded credentials, query strings or fragments are rejected. Review the relay’s privacy, access and moderation settings. The creator controls source selection, when to stop streaming and screen sharing.

When Relay supplies no valid user identifier, the app uses a weaker name-derived identifier scoped to that relay. A changed name can change that fallback identity, and matching names do not prove the same real person. Reporting and blocking do not independently verify someone’s identity.

Live moderation provides separate Hide, Block user, Report content and Report user actions, a hide-feed choice, local block management and Stop stream. Local blocks suppress that scoped user’s content and participation on your device; they do not block the person on Twitch, YouTube or another platform. Removing an entrant or cached name can reset the current Viewer Draw. Use your source platform’s moderation tools as well and end the stream if unsuitable content appears. The app does not promise to detect every objectionable message or name.

Reports and publisher safety controls

Opening a report form does not send a report. If you choose Submit while the reporting service is available, the app sends only the selected content/user snapshot: report kind, platform, scoped user and message identifiers, display name, selected message text, your chosen reason and optional details, app version, and a random client report UUID used to recognize retries. A Relay report uses a hash of the relay scope, not its configured endpoint. Display names are limited to 80 characters, selected text and details to 500 characters each, and the whole JSON report to 4096 bytes. No full chat history, purchase receipt, private review credential, configured API key, relay/video URL or app settings are included automatically. Do not type passwords, API keys or other sensitive information into optional details.

A valid service acknowledgment displays a report receipt. The same unchanged report UUID can be retried without creating another record while the original remains retained. A timeout, offline error or unconfirmed response does not prove receipt; keep the same report unchanged when retrying. The reporting flow does not send an email automatically or require an Asian Sparrow game account. Simulator submissions are labelled test reports.

Accepted reports are stored in a private WordPress queue accessible to authorized publisher operators and the hosting/database administrators who operate that service. No report text, display names or raw user identifiers are readable through the public safety feed. An operator can review a report and explicitly add or remove its hashed user key from a publisher block list; an anonymous report does not automatically ban anyone. Apps obtain that public list of hashes to apply publisher blocks. A hash can still relate to an identifiable platform user and is not a guarantee of anonymity. This does not change the user’s upstream platform account or purchase ownership.

The reporting server necessarily receives connection metadata. The reporting plugin uses a time-windowed keyed hash of the connecting network address for rate limiting and stores no raw IP address in its report records or rate-bucket data. A later report request in a new 10-minute window replaces the prior bucket state; the last window can remain until the next request. Shared networks or proxies can group unrelated users under one limit. The website host, CDN or other infrastructure may keep separate connection/access logs under its applicable configuration. We do not describe those independent logs as erased by the plugin.

Reporting may be unavailable because of connectivity, storage capacity or rate limits. External live sources require a successful current safety-service check; offline Simulator and ordinary games remain available subject to their normal purchase rules. Neither a receipt nor these controls promises immediate human review, a specific outcome, continuous monitoring or a complete multilingual filter. Contact support@asiansparrow.com for support or a privacy request; include a report receipt if relevant and only the context needed, without passwords, API keys or private review credentials.

Temporary review sessions

An explicitly authorized Play reviewer can request a temporary native review session. The private review credential is checked on the device; game code does not upload it or return it to the web interface. The review license is separate from Google Play purchase ownership. A visible banner identifies temporary progress, and the app disables new ad requests, purchases and Restore actions during the restricted session. Temporary progress and settings use an in-memory copy and do not overwrite the normal save. If native review state cannot be confirmed, progress remains temporary and review-only Stream access stays locked until it is confirmed. Exit, or recreation of the native app/renderer, ends the review session; merely putting the app in the background does not necessarily end it. These controls do not erase information that third-party services processed earlier.

What we don’t collect

  • No account, name, email address or phone number is needed to play.
  • No separate general-purpose analytics SDK is configured. Google ads/consent and RevenueCat purchase services can still process the data described above.
  • No precise location. The app does not ask for location permission.
  • No access to your camera, microphone, contacts, photos or files.

Permissions

The app uses internet access for ads, purchases, live chat, safety checks and reports you submit. The Google libraries it includes also add standard permissions to check network status, read the advertising ID and use Google Play Billing.

Crash reports from Google Play

Google Play may make crash and performance diagnostics available to developers under Google’s services and the applicable device settings, for example crash rates, device model and Android version. This is separate from the advertising and purchase services described above. Do not include private keys or sensitive personal information in support messages or diagnostic material you choose to send us.

If you email us

If you contact support, we receive your email address and whatever you choose to include. We use it only to answer you and keep a record of the request.

How information is used and shared

We use the limited information described above to run the game, show ads that fund it, deliver and restore purchases, assess safety reports and enforce explicit publisher blocks, prevent fraud and report abuse, keep financial records and answer support requests. Information is disclosed only:

  • with Google, for ads (AdMob) and payments (Google Play), as described above;
  • with RevenueCat, our service provider for purchase management;
  • with Twitch, Google (YouTube) or the relay you select when you connect Stream Mode, as needed for that connection; your separate broadcasting service also receives anything you choose to screen-share;
  • with authorized Asian Sparrow reporting operators and hosting/database providers to store and assess reports you submit; publisher block hashes are made available to app clients, without publishing the private report;
  • if required by law, or to protect the rights, safety or property of our users, ourselves or others;
  • with a successor business if Asian Sparrow or the game is sold, merged or transferred, in which case this policy, or one at least as protective, will continue to apply.

We do not sell personal information for money. See California & other US states for how ad-related data use is treated under some US laws.

Your choices and controls

  • Personalized ads: change your choice in the app’s privacy options, or reset or delete your advertising ID in Android settings.
  • Stream Mode: do not connect, stop the stream, hide the feed or use Live moderation to hide messages, block/unblock local users and choose whether to submit a selected report. The app keeps no full chat transcript; submitted report snapshots, third-party platforms, relays and broadcasts have the separate retention described here.
  • Your local data: in normal play, Reset progress clears progress/creator settings and retains Terms acceptance and moderation preferences. A temporary session resets only its temporary copy. Unblock users through Live moderation, or clear Android app storage/uninstall to remove local records. These steps do not clear consent-service, purchase-provider or received reporting-service records.
  • Received reports and publisher blocks: email support with the receipt or limited relevant context to request access, correction, review or deletion. We may need information to locate and verify a request. A local unblock does not remove a publisher block, and clearing the app does not withdraw an accepted report. Safety, legal and backup-retention obligations can affect what can be deleted.
  • Provider-held purchase records: email support with a Google Play order number if you need access/deletion assistance. We may need additional information to locate and verify a request; do not send passwords, API keys or raw purchase tokens. Legal, accounting, fraud-prevention and store obligations can limit deletion. A request does not itself cancel or refund a purchase.

How long data is kept

  • Game progress/creator settings: until reset, cleared or uninstalled. Terms acceptance and moderation preferences survive Reset progress; SDK consent and purchase caches are managed separately.
  • Local moderation: local blocked-user records remain until you unblock them, clear app storage or uninstall; the hide-feed preference also remains until changed or local data is removed. Temporary review-session changes do not replace your normal saved preferences.
  • Live chat messages: game code does not save a full chat transcript; live display/moderation data is held in bounded session memory. Platforms, relays and any recording/broadcast can retain their own copies.
  • Received safety reports: the reporting plugin schedules removal of report records older than 30 days, in bounded batches when website activity runs its scheduled work. This is a retention target, not a guarantee of deletion at exactly 30 days; delays, inactive service or a backlog can extend it. Independent hosting/database backups may retain copies under their own schedules.
  • Publisher blocks and operator history: block hashes persist until an authorized operator removes them, including after a related report expires. A bounded private history of the latest 200 operator actions can outlast the report and records operator identifiers, action times and hashed user keys.
  • Keyed rate-limit buckets: the prior window’s state is replaced when a later report request enters a new 10-minute window. This plugin does not store raw IP addresses in those buckets; independent infrastructure logs have their own retention.
  • Temporary review progress: kept in memory for the restricted session and discarded when the normal save is reloaded. It does not replace normal saved progress.
  • Purchase records (RevenueCat and Google Play): retained under the providers’ policies and applicable service, fraud-prevention, tax/accounting and legal obligations. Contact support about a specific access or deletion request; a local reset does not erase these records.
  • Ad data: kept by Google under its own retention policies.
  • Support emails: for as long as needed to resolve your request and keep reasonable business records.

International transfers

Asian Sparrow is based in the United States. Google, RevenueCat and any platform/relay you select may process information in other countries. Their policies describe processing locations and applicable transfer safeguards. Contact us about the safeguards applicable to a specific request. A link to a provider’s policy does not by itself establish that a particular transfer framework applies to every service or transfer.

Security

Game data is kept in app-local storage under Android’s application protections; the app does not separately encrypt a saved YouTube API key, even when the input is masked. Twitch connects over WSS and YouTube over HTTPS. The app uses fixed HTTPS destinations for its publisher safety check and report submission. Report text is private to the operator queue and is escaped for display; storage encoding and hashed keys do not by themselves guarantee encryption or anonymity. Remote relays require WSS; the only accepted unencrypted WS connections are explicit same-device loopback addresses. A local bridge controls its separate external connections. Ad and purchase SDKs use their own service transports. These app controls do not guarantee every provider or creator-controlled transfer is encrypted or secure.

No system is perfectly secure, so please keep your device protected. Treat your YouTube API key like a password: keep it off-screen while you stream, and consider restricting it to the YouTube Data API in your Google Cloud settings.

Children

Flag Spin Royale is intended for players 13 and older and is not directed to children under 13. We do not knowingly collect personal information from children under 13, as defined by the US Children’s Online Privacy Protection Act (COPPA) and similar laws.

If you are under the age of digital consent where you live (up to 16 in some European countries), please ask a parent or guardian before agreeing to personalized ads or making purchases.

For parents and guardians

If you believe a child under 13 has used the app and provided personal information, email support@asiansparrow.com. We will review the request, seek to locate the relevant records and address deletion subject to applicable legal and provider requirements. Uninstalling removes app-local data, not Google Play or RevenueCat server records. For an unauthorized purchase, you can also contact Google Play about a refund and enable its purchase-authentication controls.

EEA, UK & Swiss residents

If the EU General Data Protection Regulation (GDPR), the UK GDPR or the Swiss Federal Act on Data Protection applies to you, this section applies too.

Legal bases

Personalized ads, and storing or reading identifiers on your device for ads where consent is required

Legal basis: Consent. You can withdraw it at any time in the app’s privacy options.

Processing purchases and delivering and restoring what you bought

Legal basis: Contract. We need it to provide what you paid for.

Security, fraud prevention, ad measurement, and non-personalized or limited ads that keep the game free

Legal basis: Legitimate interests, and consent where the law requires it.

Keeping transaction records for tax and accounting

Legal basis: Legal obligation.

Answering support emails

Legal basis: Legitimate interests (or contract, if it is about a purchase).

Ordinary Live Stream chat is processed on your device at your request. If you submit a report, we receive only the selected report snapshot described above and process it for safety, abuse prevention and the feature you requested, relying on the applicable legal bases described here. Local moderation records are not uploaded as a whole block list. Publisher enforcement hashes are distributed to app clients.

Your rights

You have the right to access, correct or delete your personal information; to restrict or object to processing (including processing based on legitimate interests); to data portability; and to withdraw consent at any time without affecting earlier processing. You also have the right to complain to your local data protection authority, such as your EU member state’s supervisory authority, the UK Information Commissioner’s Office (ICO) or the Swiss Federal Data Protection and Information Commissioner (FDPIC).

To make a request, email us. Because purchase services use SDK-generated identifiers rather than a game login, we may need your Google Play order number or other limited information to locate and verify a request. We respond within the applicable legal deadline, generally one month for requests under the GDPR/UK GDPR, subject to lawful verification and any permitted extension or exception. We will explain an extension where required.

California & other US states

California (CCPA, as amended by the CPRA)

The categories described in this policy that may be processed when the corresponding services are used include:

Identifiers

Examples: Advertising ID, anonymous app user ID, IP address; your email if you contact us; selected reported user/message identifiers, client report UUID and publisher block hashes

Disclosed to: Google (ads); RevenueCat (service provider); authorized publisher reporting operators and hosting/database providers; publisher block hashes to app clients

Commercial information

Examples: Records of in-app purchases

Disclosed to: Google Play; RevenueCat (service provider)

Internet or other electronic network activity

Examples: Ad views, taps and completions

Disclosed to: Google (ads)

Geolocation data

Examples: Approximate location from IP address (not precise location)

Disclosed to: Google (ads)

User-submitted report content

Examples: Selected public display name/message, report kind/reason, optional details and app version

Disclosed to: Authorized publisher reporting operators and hosting/database providers; private report content is not published in the safety feed

This information comes from your device and use of the corresponding services, for the purposes described above. The game does not request sensitive personal information; avoid entering it into names, chat or connection fields.

Sale and sharing. We do not sell personal information for money. Google’s use of identifiers and ad data for personalized cross-context advertising may count as “selling” or “sharing” under applicable law. Use the app’s ad privacy choices or Android advertising controls to manage available options. The app’s 13+ confirmation is not independent verification of a player’s age. Available ad treatment and choices depend on the configured audience and regional advertising restrictions.

Your rights. Subject to applicable law, you can ask to know how personal information is processed, request correction/deletion and opt out of sale/sharing or targeted advertising. We will not discriminate for exercising these rights. Regular gameplay does not require personalized advertising; actual ad availability and treatment depend on the configured service and your choices.

How to ask. Email us. We may need to verify your request, for example with your Google Play order number. You can use an authorized agent, who must show us your written permission. Where the CCPA applies, requests to know, correct or delete are handled within its applicable deadlines, generally 45 calendar days for a substantive response, with any permitted extension and required notice. Other rights can have different deadlines.

Other US states

If you live in a state with a comprehensive privacy law (such as Colorado, Connecticut, Virginia, Utah, Texas or Oregon), you have similar rights to access, correct and delete your information and to opt out of targeted advertising. Use the in-app privacy options or email us. If we decline your request, you can appeal by replying with the subject line “Privacy appeal”. If you are not satisfied with the outcome, you can contact your state attorney general.

Changes to this policy

We may update this policy as the game or the law changes. We will post the new version on this page and update the “Last updated” date. If a change is significant, we will also tell you in the app and, where required, ask for your consent again.

Contact us

Questions or requests about privacy in Flag Spin Royale:

Asian Sparrow LLC
Fair Oaks, California, USA
Email: support@asiansparrow.com (please put “Flag Spin Royale privacy” in the subject line)
Website: asiansparrow.com

See also the Flag Spin Royale Terms & Conditions.