Engine Simulator
Sprache · Deutsch

Datenschutzerklärung

Gültig ab

Maßgeblich ist die koreanische Originalfassung dieses Dokuments.

Der folgende Richtlinientext ist auf Englisch verfügbar. Eine Übersetzung in die gewählte Sprache liegt noch nicht vor. English

Groundcode (그라운드코드, the “operator”) provides Engine Simulator and engine-simulator.com (the “service”). This policy describes the information processed by the service under applicable privacy laws, including Korea’s Personal Information Protection Act.

1. Accounts, device permissions and local settings

You can use the service without creating an account or signing in with Toss. We do not request access to your contacts, photos, location or microphone. The App Store version may ask for App Tracking Transparency (ATT) permission; see section 6. The last selected engine, sound settings and expiry times of engine-specific 24-hour rewarded passes are stored on your device. The native store apps do not send these values to our server or sync them across devices. Each pass lasts 24 hours from the time its reward is confirmed. You can remove local settings using your operating system’s app-data controls. Passes are not guaranteed to survive app removal or a backup and restore. The Toss mini-app also stores the first-use date and last-visit date locally. Section 2 describes usage information sent separately.

2. Usage information

Production versions of the Toss mini-app use Toss’s analytics SDK to improve the service. Events cover opening the screen, starting and stopping the engine, choosing an engine, transmission, exhaust or tune, changing sound settings, advertising results and ad flow, whether the app had been used before visit history was first created, and a time-since-first-use category such as the first or following day. Fields added by the app are limited to predefined options and result categories. They do not include free text, user identifiers, ad-group IDs, per-frame RPM values or exact dates.

The Toss SDK may add screen paths, referral information and deployment identifiers. Information handled by the Toss mini-app platform is subject to Toss’s privacy policy and mini-app terms.

3. Advertising in the Toss mini-app

The Toss mini-app includes a bottom banner. When choosing another non-default engine, you can choose to watch a rewarded ad. Toss and its advertising providers handle device and advertising information under their policies. Rewards only provide access to an engine inside the app; they do not pay cash or Toss points. Advertising in the native store apps is described in section 6.

4. Error diagnostics

Toss mini-app versions with error reporting enabled use Sentry (Functional Software, Inc.) to diagnose failures. Reports include error types and messages, code locations, app version, occurrence time, browser and operating-system details. Error reports are sent over encrypted connections to Sentry’s US processing region and retained for up to 90 days.

The app removes user identifiers, email, IP address, cookies, request and response headers and bodies, and URL query strings from diagnostic events. It also removes email addresses and URL query strings from error messages. Session recording, performance tracing, general logs and interaction history collection are not enabled. Sentry error reporting is disabled on the website and in the current native store release. Before enabling native error reporting, we will update this policy with the data, processing location and retention period.

Contact details for access and deletion requests are in section 7. See Sentry’s privacy policy and its retention information for details.

5. Website access information

The website provides static product and policy pages without creating accounts or setting cookies. It is served through Cloudflare, which may process IP addresses, request times and browser information to provide and secure the service. Cloudflare Web Analytics measures aggregate visits using page URLs, referrals, browser and device types, and country-level location. It does not set cookies or create user-identifying values. Cloudflare’s privacy policy governs this processing.

6. Advertising in the App Store and Google Play apps

The native apps include Google AdMob bottom banners. The default inline-six engine is available without watching an ad. For another engine, you can choose to watch a rewarded ad. A confirmed reward lets you select that engine again for 24 hours without another rewarded ad. This pass does not remove banners. 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 Android advertising ID or iOS IDFA, app and device information, app and ad interactions, and crash and performance diagnostics. Google’s User Messaging Platform (UMP) also processes information needed to manage consent, including device and consent status. See Google’s privacy policy and how Google uses information from partner sites and apps.

Advertising information is transmitted over encrypted connections. Retention, deletion and privacy choices for information handled by Google follow the policies above and Google’s account and device controls. Deleting a local engine pass does not delete all information already processed by an ad provider. The operator does not run a separate server storing advertising data. If the native apps process additional information, we will update this policy and its effective date before the change takes effect.

7. Your rights and contact information

You may contact us about privacy or request access, correction or deletion. We will review and handle requests without undue delay. Email addresses and messages received for support are used only to handle the request and are deleted without undue delay after it is resolved.

8. Changes to this policy

We publish changes and their effective date on this website.