Privacy Policy
Last updated: 3 November 2026
Autowala: Auto Rickshaw Taxi ("the game") is a driving game published by Spintech Studio. This policy explains what the game collects, why, and who it is shared with.
Contact: spintechstudio@gmail.com. You can open this policy at any time from Privacy policy in the game's Settings.
The short version
Autowala has no accounts of its own and never asks for your name, email address or phone number. Your progress stays on your phone, and if you choose to sign in with Google Play Games, a copy is kept in your Play Games account so it comes back on a new phone. The game uses Google Firebase to report crashes, so we can fix them, and, outside the European Economic Area, the United Kingdom and Switzerland, to understand how the game is played. It uses Google AdMob to show ads. Everything it sends goes to Google's services over encrypted connections; we run no servers of our own. It has no in-app purchases.
Data stored on your phone
Your save is kept in the game's private storage on your phone. The save itself is never sent to us: it leaves your phone only as a backup copy, through Android's backup (below) and, if you sign in, Google Play Games. Some details from it, such as your level or the vehicle you are driving, are also part of the game events and crash reports described further down. The save holds:
- Your level, money, trips, records, achievements, daily jobs and streak
- Your vehicles, upgrades, paint colour, stickers and other styling, and how dented your auto is
- Your settings: language, steering, layout, volumes, graphics and camera view
If backup is turned on in your phone's settings, Android copies this save to your own Google account, so your progress comes back when you reinstall the game or move to a new phone. That copy is handled by Google under your account; we cannot see it. If backup is off, uninstalling the game deletes the save for good, apart from any copy in your Play Games account (see below).
Data collected by Google services
Google Play Games (optional)
Signing in is your choice: the game offers it on the title screen and in Settings, and plays the same without it. If your phone is already signed in to Play Games, the game may sign you in on its own when it starts, as Play Games games do. Once you are signed in, Google gives the game your Play Games player ID and gamer name; the game shows the name in Settings and keeps neither anywhere else. The game then stores a copy of the save listed above as a saved game in your Play Games account, and updates it while you play (at most once a minute). Google keeps this copy with your account; Spintech Studio cannot see it. You can delete it at any time from your Google Play Games profile settings, which also removes the game's other Play Games data. Google's Play Games software in the game also sends Google its own usage and diagnostic data, to keep Play Games working and improve it.
While you are signed in, the game also unlocks your Play Games achievements and sends two scores to Play Games leaderboards: your best day's fares and your most trips in a day. Other players can see your gamer name and these scores on the leaderboards, depending on the visibility you choose in your Play Games profile.
Google Analytics for Firebase
Collects game events, for example a trip completed (with its fare, stars, distance and type of fare), a level reached, an achievement unlocked, something bought with in-game rupees, a traffic fine or the tutorial finished, together with your device model, operating system version, app version, language, approximate location (city, region and country, which Google works out from your IP address) and a randomly generated app instance ID. If your phone allows it, Analytics also reads your device's advertising ID to count where installs come from. We use this to understand which parts of the game people enjoy and where they get stuck, so we can improve it. You can reset or delete your advertising ID in Android Settings → Google → Ads.
In the European Economic Area, the United Kingdom and Switzerland, where Google's consent form applies, the game does not use Analytics at all: it stays switched off there, and no game events are sent to Analytics (a crash report still carries a log of the game's events; see Crashlytics below). The game checks this each time it starts, and Analytics stays off until it has.
Firebase Crashlytics
When the game crashes or hits a serious error, Crashlytics sends a crash report: the technical stack trace; details of your device, such as its model, operating system version, free memory and storage, and graphics chip and driver version; the game's state at that moment (your level, the vehicle you were driving and the graphics setting); a log of the game events from that session (the same kinds of events as under Analytics, such as trips, fines, things bought and ads watched); and a random installation ID. We use it only to find and fix bugs. Crash reports are sent in every country, because they are how we find and fix crashes.
Google AdMob
The game shows rewarded videos that you choose to watch for a bonus (a bigger fare, a free repair, a bigger rocket tank, or the police wheel lock taken off), and, from level 3 on, now and then a full-screen ad when you go on to the next level, never while you are driving. AdMob collects your device's advertising ID and app set ID, your IP address (from which Google may estimate your general location, never your exact one), your interactions with ads and with the game (such as app launches, taps and videos watched) and diagnostic information, for advertising, analytics and fraud prevention, and may use them to show personalised ads. To fill an ad, Google may pass some of this data, such as the advertising ID and your approximate location, to the advertisers and ad partners that bid for the space; in the European Economic Area, the United Kingdom and Switzerland, the consent message lists those partners. Where the law requires it (the European Economic Area, the United Kingdom and Switzerland), the game asks for your consent first and shows no ads until you have answered, and you can change your choice at any time from Privacy choices in the game's Settings. In US states with their own privacy laws, Privacy choices also lets you opt out of the sale or sharing of your data for personalised ads. You can reset or delete your advertising ID in Android Settings → Google → Ads.
Google's handling of this data is governed by the Google Privacy Policy. More on how Google uses data from apps that use its services: policies.google.com/technologies/partner-sites.
Rating and sharing
Now and then, after you finish a level, the game may show Google Play's own rating card (at most three times, weeks apart). Whatever you write there goes to Google Play under your Google account, as any Play review does; the game never sees it. The SHARE buttons make a picture of your day or your level on your phone and hand it to Android's share menu: only the app you choose receives the picture, and the picture never reaches us. Outside the European Economic Area, the United Kingdom and Switzerland, Firebase Analytics records that you shared, with your level.
Reminders
If you allow notifications, the game sets its own reminders on your phone: one a day at the time you last opened the game (your daily bonus, new jobs, the evening rush or a festival in Kochi), for up to 30 days, and one when a police wheel lock comes off. They are made and scheduled on your phone, and no server sends them. Outside the European Economic Area, the United Kingdom and Switzerland, Firebase Analytics (as above) records whether you allowed notifications when Android asked and, when you tap a reminder, which kind it was (for example "daily bonus"). You can turn reminders off in Android's notification settings for the game.
What we do not collect
- No name, email address, phone number or postal address (the only name the game ever sees is your Play Games gamer name, if you sign in)
- No location from your phone's location services
- No contacts, photos, files, microphone or camera access
- No payment information: the game has no purchases
How the data is protected
The game sends data only to Google's services (Firebase, AdMob and Play Games), and always over encrypted connections (HTTPS with TLS). Spintech Studio runs no servers of its own: the game events and crash reports described above are stored by Google in our Firebase project, and our own Firebase database is closed and stores nothing about players. Access to the game's Firebase and AdMob consoles is limited to Spintech Studio's own Google account.
Permissions and why they exist
INTERNETandACCESS_NETWORK_STATE: load ads, and send game events and crash reports to FirebaseAD_IDand theACCESS_ADSERVICESpermissions: added by the Google Mobile Ads SDK and Firebase Analytics to serve and measure ads and installsWAKE_LOCK: added by Google's Firebase SDKs and Android's WorkManager library for their own short background work- The install referrer (
BIND_GET_INSTALL_REFERRER_SERVICE): added by Firebase Analytics to learn from Google Play which link or ad led to the install FOREGROUND_SERVICE: added by Android's WorkManager library, which Google's SDKs use for short background tasks; the game runs no foreground service of its ownREAD_BASIC_PHONE_STATE: added by the Google Mobile Ads SDK; the game itself does not use it, and it gives no access to your phone number, calls or contactsPOST_NOTIFICATIONS: show the game's reminders (Android asks you first; see Reminders above)RECEIVE_BOOT_COMPLETED: set the reminders again after your phone restarts, which clears them
Tilt steering, if you turn it on, reads your phone's motion sensor inside the game only; nothing about it is stored or sent.
Children
Autowala is not directed at children under 13, and we do not knowingly collect personal information from them.
Keeping and deleting your data
Firebase Crashlytics keeps crash reports for 90 days, then deletes them. Google Analytics deletes game events after at most 14 months; only totals for all players together (for example, trips driven per day) stay in our reports, and these cannot identify anyone. Game events and crash reports are tied to random IDs (the app instance ID and the crash-reporting installation IDs) and, for Analytics, to your advertising ID if your phone allows it, never to your name or email address. Uninstalling the game or clearing its data resets the random IDs; you can reset or delete the advertising ID yourself (below). Ad data is held by Google under its own rules (how Google retains data).
You can delete your data yourself at any time:
- On your phone: uninstall the game, or clear its data in Android's app settings.
- Your Play Games copy of the save, achievements and scores: from your Google Play Games profile settings.
- Your advertising ID: reset or delete it in Android Settings → Google → Ads.
For any question or request about your data, email spintechstudio@gmail.com and we will answer within 30 days.
Your rights
In the European Economic Area, the United Kingdom and Switzerland, you have the right to access, correct, delete, restrict or move your data, to object to our use of it, and to complain to your data protection authority. We collect crash reports on the basis of our legitimate interest in keeping the game working; for ads, we rely on the consent you give or refuse in the consent message, which you can change at any time from Privacy choices. Google may process this data in the United States and other countries, with the safeguards described in the Google Privacy Policy. Because the game has no accounts and does not show its random IDs, we usually cannot pick out your game events or crash reports from anyone else's: uninstalling the game or clearing its data cuts them off from you, and Google deletes them when the times above are up.
Changes
If this policy changes in a material way, for example when a version adds online features, we will update the date at the top and publish the new version at this address before that version is released.