Privacy Policy

Effective Date: 2026-10-17

Groundcode (the "Operator") explains below how information is processed in the Kickflip Simulator Toss mini app, the iOS and Android apps distributed through the App Store and Google Play (the "store apps"), and the introductory website kickflipsimulator.com. This policy is available at kickflipsimulator.com/privacy.

1. Account Registration and Device Storage

You can use the Toss mini app and the store apps without creating a separate account or logging in. We do not collect your name, phone number, or email address in the apps, and we do not request device permissions for contacts, photos, location, microphone, or camera. However, versions of the iOS store app that show a bottom banner ad may ask for App Tracking Transparency (ATT) permission for personalized ads (see Section 4). Processing when you contact us by email is explained separately in Section 7.

Your sound on/off setting and the number of completed flights on this device are stored in your device storage. The flight count is used to determine whether to show control guides during your first few flights and, if you have not manually changed the playback speed, to start the airborne phase at a slow speed during your first two flights. These two stored values are not transmitted to the Operator's servers.

The Toss mini app uses the storage provided by the Toss app first, and falls back to the on-device WebView storage if there is an issue connecting to that storage. The store apps use the WebView storage inside the app. Deleting the stored data for the app or WebView, or deleting a store app, also deletes your settings and flight count. Because this information stays on your device, the Operator cannot view or delete it remotely.

The public website provides an introduction to the service and policy information. The website does not have a feature that stores simulator sound settings or flight counts.

2. Toss Mini App Usage Logs

To improve the service, the production version of the Toss mini app sends the following usage logs to the Toss analytics SDK:

• Entering the simulator screen
• Flight start, retry, replay, and the flight count range for the current session (1, 2–4, 5–9, 10 or more)
• Selected starting position when restarting (ramp end or ramp entry)
• Touchdown result type, outcome category, inside/outside the landing zone, and the time range for when the car comes upright (under 1s, 1–2s, 2–4s, 4s or more, did not come upright)
• Descent speed range right before touchdown (under 1m/s, 1–2, 2–3, 3–4, 4–6, 6 or more, no touchdown)
• Playback speed change, pause, sound setting change, and opening the control guide

Values added directly by the app are limited to predefined types, ranges, and on/off values. The app does not add arbitrary text, custom user identifiers, URL query strings, frame-by-frame control or position values, or exact timestamps and dates to event values.

Separately, the Toss SDK adds the URL query string, referral information, deployment identifier, and deployment timestamp, and also includes the document title in screen entry logs. The SDK documentation states that an anonymous identifier key (anonymous_key) is automatically included. This default SDK information is distinct from the event values added directly by the app.

The Operator does not store these logs on a separate API server. Information processed and retained by the Toss platform and related user rights are governed by the Toss Privacy Policy and the Toss mini app terms.

The store apps do not send these usage logs to the Operator or to an analytics service. Versions of the store apps without a bottom banner ad do not collect information about you or send it off your device. For versions that show a banner ad, information processed by the advertising SDK is described in Section 4.

3. Advertising, Payments, and Error Diagnostics

Currently, the Toss mini app and the store apps have no in-app purchases, and do not provide cash-equivalent rewards or Toss Points. In the current release versions, Sentry error diagnostics are disabled, and error information is not sent to Sentry.

Versions of the Toss mini app that support banner advertising display a footer banner through the Toss in-app advertising SDK. The SDK handles ad requests, display, impressions and clicks. The app does not additionally send ad click or impression records to a separate server operated by Groundcode. Information processing by the Toss platform is described in the Toss Privacy Policy.

Banner advertising in store app versions is described in Section 4. If we introduce payments or external error diagnostics in the future, we will update this policy to reflect actual processing and provide the necessary notice. Separate policies of the respective service apply to the YouTube video embedded on the website.

4. Advertising in the Store Apps (Google AdMob)

This section applies to versions of the store apps that show a bottom banner ad. Versions without a bottom banner ad do not request ads, and none of the processing in this section takes place. Store app versions that support banner advertising show a Google AdMob banner in a separate area at the bottom of the screen. Ads are requested only in portrait orientation when the screen is tall enough, and they do not cover the simulator controls. You can use the simulator without tapping any ad.

For ad delivery and measurement, analytics, and fraud prevention, AdMob may collect or share IP addresses and approximate location inferred from them, device identifiers such as advertising identifiers (the IDFA on iOS when you allow tracking, and the Android advertising ID), app and device information, ad interactions such as impressions and clicks, and crash and performance diagnostics. Google's User Messaging Platform (UMP), used to manage ad consent, also processes the information needed to provide consent choices, such as device and consent status. This processing follows the Google Privacy Policy and how Google uses information from sites or apps that use its services.

In regions where consent is required, such as the European Economic Area (EEA) and the United Kingdom, the app presents ad privacy choices through Google UMP when it starts, and requests ads only when ads may be requested. When your choices can be changed again, an "Ad privacy settings" button appears in the app's controls guide. Depending on your consent status and the SDK's response, non-personalized or limited ads may be shown, or no ads may be shown. Declining consent does not prevent you from using the simulator.

In iPhone and iPad app versions that support banner advertising, the app may ask for App Tracking Transparency (ATT) permission when needed. If you do not allow tracking, the IDFA is not used; allowing tracking does not guarantee personalized ads. You can change tracking permission in your device's Settings app.

On Android, you can reset or delete your advertising ID in your device's ad settings and, depending on the device, opt out of personalized ads.

Advertising information is transmitted over encrypted connections. The apps do not additionally send ad impression or click records to the Operator's servers, and the Operator does not run a separate server storing advertising data. Retention, deletion, and privacy choices for information processed by Google follow the Google policies above and Google's account and device controls. If the store apps start processing additional information, we will update this policy and show a new effective date before the change takes effect.

5. Introductory Website Access and Visit Analytics

The website is served through Cloudflare infrastructure. For page delivery, service stability, and security, access information such as IP addresses, request timestamps, and browser information may be processed by Cloudflare. This infrastructure processing is distinct from the visit analytics described below. Processing and retention standards are detailed in the Cloudflare Privacy Policy.

The website uses Cloudflare Web Analytics to understand page usage and performance. It processes statistics such as page paths, referrers, country, device/browser/OS types, page views, and loading performance. This analytics script may be automatically included in website responses.

Cloudflare states that Web Analytics does not use cookies or localStorage for analytics and does not combine IP addresses or other data to create fingerprints for tracking individuals. It explains that IP addresses received while processing RUM analytics requests are discarded at a nearby data center and are not stored in core databases or logs. This does not mean that other infrastructure access logs required for website delivery and security are not processed at all. Web Analytics Overview, RUM Processing Guide

According to Cloudflare's documentation, statistics available for viewing in Web Analytics cover the past 6 months. You can restrict the execution of this analytics script using browser settings or content-blocking tools, but blocking the network connections required to deliver the website itself may limit your ability to use the page. Web Analytics FAQ

6. Embedded YouTube Video and External Services

The website embeds a motion reference video using YouTube Privacy-Enhanced Mode (youtube-nocookie.com). Autoplay is not used; when the player loads or when you play the video, your browser communicates with Google and YouTube servers. During this process, information such as your IP address, browser and device details, referring page, and video usage information may be processed under the applicable service policies.

YouTube states that watching a video in this mode is not used to personalize your subsequent YouTube browsing experience or personalized ads outside the website. Privacy-Enhanced Mode does not eliminate all network communication or information processing. If you click a link that takes you to YouTube, the policies of that destination service apply. YouTube Privacy-Enhanced Mode Help, Google Privacy Policy

You can restrict connections to the YouTube player using your browser's external content-blocking features. Doing so may prevent you from viewing the embedded video, but it does not affect your use of the simulation in the Toss mini app or the store apps.

7. Retention Period and Deletion

When the Operator receives an email inquiry, we use the sender's email address, inquiry content, and any attachments provided by the user to respond and handle the request. Information that no longer needs to be retained once the inquiry has been resolved is deleted without delay. Where retention is required by law, we retain the information solely for the applicable legal purpose and period.

For deletion, after confirming that the inquiry has been resolved and no further retention is required, the Operator deletes the electronic copies of the relevant emails and attachments in its possession. Sound settings and flight counts stored only on your device can be removed using the device data deletion method described in Section 1.

Information processed by the Toss platform, Cloudflare infrastructure and analytics, and Google (AdMob, UMP, and YouTube) is subject to each provider's respective processing and retention policies. If you send a request regarding such information to the contact address below, the Operator will check the scope within which we can assist and guide you accordingly.

8. Roles of External Providers and Information Protection

External providers process information through their respective service infrastructures, which may involve overseas servers. Processing locations, retention standards, and procedures for exercising rights with Cloudflare and Google are explained in the policies linked above. Inquiries handled directly by the Operator and requests regarding device-stored information can be sent to the contact address below.

The app does not request unnecessary device permissions, stores sound settings and the flight count used for initial control guides and playback speed settings on your device, and limits the values the Toss mini app adds for analytics to predefined categories. The public website is served over HTTPS. The current release versions do not operate a separate member database or external error diagnostic collection.

9. User Rights and Contact Information

You may submit requests regarding access, correction, deletion, or suspension of processing of personal information by email. Please provide enough context to identify what you are requesting and how it relates to the information in question. You do not need to send sensitive information or copies of identification documents that are unrelated to your inquiry.

After verifying to the necessary extent that the request concerns your information, the Operator will handle it without delay. If a request cannot be fulfilled immediately due to legal restrictions or because the Operator does not hold the information, we will explain the reason and any available options.

• Operator: Groundcode
• Privacy Officer: 배기열
• Contact: hello@groundcode.io

10. Changes to This Policy

If we update this policy, we will post the changes and the effective date on the Privacy Policy page.