RPM Engine Simulator
Privacy Policy
Last updated: 12 November 2026
RPM Engine Simulator is built to work without knowing who you are. There is no account, no sign-in, no profile, no backend, no analytics and no crash reporting. Your garage, your tunes, your settings and your career live only on your device, and nothing you do in the app is sent to us — because there is no “us” on the other end of a server to send it to. This policy describes what the app stores on your device, what little network activity it can initiate, and what third parties are involved in advertising. Nothing more.
1. No account, no identity
RPM Engine Simulator does not ask for your name, email address, phone number or password, and it creates no user account. It has no identity to attach to your activity. There is no sign-in screen, no account store, no credential field and no user profile of any kind. The app cannot recognise you across devices, because it never learns who you are on any device.
There is also no first-party backend: the app makes no app-level network request to any server operated by the developer, and there is no game server, no cloud save and no sync service. The app works fully offline.
2. What the app stores on your device
All game state is stored only in the app's on-device web storage (localStorage), under roughly 70 keys. Nothing in this list leaves the device. The stored data includes:
- Your garage and engines — saved vehicles, custom vehicles and custom engines, the last vehicle used, and the career-mode garage kept separately from free play.
- Favourites — catalogue favourites stored as vehicle codes, and infinite-generator favourites stored separately.
- Career progress — the credits balance, used-vehicle market picks, and career save slots.
- Driving records and journal — recorded timings, drive entries and dyno bench runs.
- Settings — language, volume, sound style, graphics quality, units, kilometre tracking, HUD and input preferences, and the first-run language-onboarding marker.
No database is created by the app, and no native preferences store holds game or settings state. The app does not upload, back up to a server, or synchronise any of this data. There is no export, import or cloud-backup feature in this version, so your saves exist only on the device where you created them.
3. What the app does not collect
The app itself collects no personal data. In particular, it does not collect, access or transmit:
- Your name, email address, phone number or any contact information;
- Your location — the app requests no location permission and has no location feature;
- Your contacts, calendar, photos, files or other on-device content;
- Camera or microphone input — the app requests neither permission;
- Precise device identifiers — the app reads no IMEI, serial number or similar identifier;
- Usage analytics or diagnostics — no analytics SDK and no crash-reporting SDK is bundled or initialised, and no telemetry event is emitted;
- Push-notification data — the app includes no push notifications and no messaging registration;
- Payment or purchase data — the app contains no in-app purchase, subscription or payment flow of any kind.
The app includes no Firebase project and no Firebase SDK initialisation. The only identifier-related processing that can occur is the advertising processing described in section 5, performed by Google's advertising services, not by this app.
4. Network activity and permissions
The app declares exactly two Android permissions, and requests no runtime permission on first launch or at any other time:
| Permission | Why |
|---|---|
| Internet access | Required only so that advertising services can load ads when the advertising integration is active. The app itself makes no app-level network request. |
| View network connections | Lets the app and advertising services tell whether a network connection is available, so the app can fail open gracefully when there is none. |
The app declares no billing permission (there is no purchase), no location, storage, camera, microphone or notification permission, and no advertising-identifier permission in this version. It defines no custom URL scheme and no deep links, and it exposes no bridge between the web content and native code.
Web addresses that appear inside the app (for example links to policy pages) are links only: the app does not call them. The only network endpoints the app can reach in practice are Google's advertising and Play infrastructure, as described in section 5, and only once the advertising integration is active.
5. Advertising (Google AdMob)
RPM Engine Simulator is free and supported by advertising. The app's advertising approach is a single interstitial placement, served through Google AdMob:
- An interstitial may appear only when you return to a menu — never while driving, never in a pause, never in settings, and never during first-run onboarding.
- Frequency is capped at most one interstitial per three minutes, the first menu shown at launch is always spared, and no ad is attached to a button you just tapped.
- There is no banner ad and no rewarded ad. No ad gates, unlocks, refills or accelerates any feature, vehicle, credit or content.
- If an ad fails or is unavailable — for example with no network — the game continues normally, with no error shown.
The advertising integration in the current version is being completed; until it is active, no ads are served and no advertising data is processed. When advertising is active, Google AdMob may collect and process information as described in Google's own privacy policy, which can include device information and advertising identifiers used to serve and measure ads. That processing is performed by Google, under Google's policies, not by this app:
- Google Privacy Policy: policies.google.com/privacy
- Google Ads Settings (ad personalisation controls): adssettings.google.com
You can reset your device's advertising ID, or limit ad personalisation, in your Android device settings under Google → Ads. Where the law requires consent for advertising processing, consent choices will be presented through Google's consent flow when the advertising integration is active; until then, no consent dialog is presented, because no advertising data is processed.
6. Children's privacy
RPM Engine Simulator is a general-audience driving and engine simulator. The app does not knowingly collect personal information from children under 13, and it does not knowingly collect personal information from anyone — the app itself collects nothing, as described in sections 1–3. Advertising, when active, is served by Google under Google's policies for the audience the app declares on Google Play.
If you are a parent or guardian and you believe the app or its advertising has collected information from your child that concerns you, please contact us at the address in section 11 and we will respond to your concern.
7. Retention and deletion
Everything the app stores lives only on your device, so retention is entirely in your hands:
- Your garage, settings, favourites, records, journal and career data remain on the device until you delete them — through the app's own reset controls, by clearing the app's data in Android settings, or by uninstalling the app.
- Clearing the app's data or uninstalling the app can erase all saved progress. This version has no export, import or cloud backup, so erased saves cannot be recovered by us — we hold no copy.
- Because the app sends nothing to a server, there is no server-side copy of your data to request access to or deletion of. A request sent to the contact in section 11 about data held on our servers will be answered by explaining that no such data exists.
8. Security
The app's security posture follows from its design: the less data moves, the less there is to protect. All game state stays in the app's private on-device storage; the app makes no first-party network call; it exposes a single app screen component and no bridge between its web content and native code; and it contains no credential, API key or secret of any kind.
No method of storage is completely secure, and the app makes no durability promise for saves across uninstall, app-data clearing, or device restore. Keeping your device's operating system and Google Play services up to date is the most effective step you can take to protect the data on it.
9. Third-party links and services
The app and this site link to third-party services, principally Google Play (distribution) and Google AdMob (advertising, when active). Those services operate under their own privacy policies, and this policy does not cover their processing. We encourage you to read the privacy policies of any third-party service you use through links in the app.
10. Changes to this policy
We may update this policy from time to time — for example when the advertising integration becomes active, or when the app gains a feature that changes how data is handled. When we do, we will update the “Last updated” date at the top of this page and publish the revised policy here. Material changes will be described in the app's store listing update notes. Your continued use of the app after a change means you accept the revised policy.
11. Contact us
If you have questions about this policy, or about how RPM Engine Simulator handles data, contact us at: support@enginesim.app. Please include “Privacy” in the subject line so your message reaches the right place.