エンジンシミュレーター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 apps do not send the complete settings or pass documents to our server or sync them across devices. Optional usage statistics are described in section 2. 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
Toss analytics SDK
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.
Optional engine usage statistics
In supported versions, ‘Share usage statistics’ is off by default. Collection and transmission start only after you read the notice and explicitly choose to turn it on. Your choice does not affect the app’s features or cost, and you can change it at any time in app settings. This choice does not change the separate processing by the Toss analytics SDK, error diagnostics or advertising services.
We use these statistics to improve the app by measuring engine and option use, active time and collection quality. They include a new random session ID, random event IDs, app version and build, statistics format versions, app surface and operating-system type (iOS or Android), event type, reason, sequence and delivery attempt, engine and effective options, occurrence times rounded to seconds, active elapsed intervals, and collection or delivery quality categories and affected amounts. They are sent over encrypted connections to Cloudflare, Inc.’s Analytics Engine. Options include transmission, drive, clutch, exhaust, sound tune, tuning parts, visual effects, view, background, sound settings and the operating state of the recording feature. Time spent with default settings is included. The current session ID is not restored on the next app launch or linked to account, installation or advertising IDs. We do not use these statistics for advertising, personalized recommendations or linking with records from other services. These records do not establish successful audio playback or whether someone heard the sound.
Usage statistics exclude names, contact details, free text, location, account, installation and advertising IDs, complete saved settings or passes, full URLs, filenames, audio, video, microphone data and hardware volume. Connection information may be processed by infrastructure for security, but IP addresses and request bodies or headers are not copied into the app’s AE usage fields. Analytics Engine statistics are retained for up to three months and unsent device records for up to seven days, subject to earlier removal at size limits. Only records from people who opt in are included. Network loss and sampling mean the results are usage estimates rather than exact user counts or a representative measure of all users.
Turning off ‘Share usage statistics’ in app settings stops new collection and new requests and deletes pending device records. A request started before the change may still reach the server. Because delivered records are not linked back to an account or installation ID, identifying and deleting one person’s statistics individually is limited. If saving the preference fails, collection stays off for the current run and the app shows the failure. Turning it back on starts a new session. Cloudflare’s privacy contact is dpo@cloudflare.com. See also the Cloudflare Privacy Policy. Cloudflare is a global provider that processes information in multiple regions; this notice does not promise storage in a single country. Where a separate notice or consent for overseas processing is required, optional collection will not start before that notice and the required procedures are completed.
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.
Starting with version 1.2.3 on each store, the Google Play and App Store apps use Sentry to diagnose app errors and advertising failures. Reports include permitted information such as error types and messages, code locations, occurrence time, app and operating-system versions, and device model. Ad failures may also include the failure stage, error codes, elapsed time, the advertising SDK version, and a reference for that ad attempt. Android reports also include Android System WebView and Google Play services versions. The reference identifies an individual attempt, not an account or device.
These reports are sent over encrypted connections to Sentry’s US processing region and retained for up to 90 days. Ad failure reports do not include advertising identifiers, consent choices, raw advertising SDK responses, user identity, attachments, session recordings, performance traces, general logs or interaction history. The app removes identifying fields and sensitive request information; server-side filtering also removes IP addresses and approximate location from stored error reports. Google’s separate processing for advertising is described in section 6.
Starting with version 1.2.3, the store apps keep a limited local diagnostic record for up to seven days. Automatic ad failure reports are limited to one report per error signature per hour and five reports per device in a rolling 24-hour period. You can preview the record in ‘Share ad diagnostics’, choose a sharing app and send it yourself. The app does not send email to the operator automatically. Records and contact information you share for support are handled under section 7.
Sentry error reporting remains disabled on the website and in App Store versions 1.2.2 and earlier.
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.
- UMP presents privacy choices depending on your region and consent status. When those choices can be reopened, a privacy-options item appears in the app’s configuration screen. Depending on consent and the SDK’s response, non-personalized or limited ads may appear, or ads may be unavailable. Declining consent does not prevent use of the default engine.
- On iPhone, the app may ask for ATT permission when needed. If you decline, 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 using your device’s advertising settings.
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.
- Privacy officer: 배기열 (Giyeol Bae)
- Contact: hello@groundcode.io
8. Changes to this policy
We publish changes and their effective date on this website.