Privacy policy

Effective date: October 28, 2026

This policy explains what information Oilcloth handles, where it goes and what you can do about it. It covers the Oilcloth app on iPhone, iPad and Android, made by KHKikani, an independent developer in India, and this website. We’ve kept it as plain as we can.

1. In short

  • No account. Oilcloth has no sign-in, and the app never sends your name, email address or phone number.
  • Your game stays on your device. Your progress, streak, settings and saved tables are kept on your phone or tablet, not by us.
  • Usage statistics and crash reports go to Google Analytics for Firebase and Firebase Crashlytics, so we can fix problems, improve the game and test how often ads show. Settings > Privacy > Share usage and crash reports turns both off.
  • A privacy check runs every time the app starts or you come back to it, for every player, whether ads are on or off. It tells the app whether privacy laws where you are call for Google’s consent form or for Privacy choices.
  • Ads come from Google. Where ads run, Google’s ads software collects information about your device, including its advertising identifier on Android, and on iPhone and iPad only if you allow tracking.
  • Ads only where your app store’s age range allows them. If your app store reports that you’re under 18, the app never starts ads for you. The app never sends your age range anywhere.
  • This website sets no cookies and runs no scripts, analytics, ads or trackers.

2. Who we are

Oilcloth is made by KHKikani, an independent developer in India, who decides how the information the app sends for us and the messages you send us are used, and is responsible for them. Google decides how it uses the information it collects for ads (section 9).

We release Oilcloth on the App Store and Google Play only in the United States, Canada and Australia (section 19).

3. What stays on your device

The app keeps these in its own storage on your device. We don’t back them up or sync them. Usage statistics (section 5) report some of them, such as a setting you change, or your streak in broad bands:

  • your settings, including the reminder time and your choice about usage and crash reports;
  • your progress: tables cleared, your streak and nights off, tile sets and History;
  • tables in progress, saved so you can carry on;
  • the table codes you’ve played from friends, with any names you gave them;
  • small notes the app needs: whether you’ve played the practice table and seen each one-time tip and offer, which app version last asked your app store for the rating prompt, the first and latest app version you’ve run, how many times you’ve opened the app and when you last left it, which milestones usage statistics have already reported, counters that space out ads after tables, a short log of up to 5 ads shown in the last 30 days (for Report an ad), the ad switches from the last remote settings, and whether ads can show for you, with the date that was checked (section 10).

Other software in the app keeps some things on your device too:

  • Google’s consent software keeps your answers to its consent form, and Apple keeps your answer to the tracking prompt in the Settings app.
  • Firebase keeps random identifiers for usage statistics, crash reports and remote settings, the remote settings it last received, and any crash reports not sent yet.
  • Where ads run, Google’s ads software may store information on your device to show and measure ads.

If your device backs up apps to iCloud or to your Google account, these may be copied into that backup, which Apple or Google keeps under your account. On later launches the app checks your age range with your app store again (section 10).

A few features use your device without sending anything to us:

  • The evening reminder, if you turn it on, is scheduled by the app on your device; no server sends it. The app asks for permission to send notifications only when you turn the reminder on.
  • Sharing a cleared table hands a picture of its result card and one line of text to your device’s share sheet; they go only where you choose, and the app uploads nothing itself. On iPhone and iPad, if you choose to save the picture to Photos, the system asks your permission first.
  • The rating prompt is your app store’s own. The app may ask the store to show it; Apple or Google decides whether it appears and handles any rating you give.

Every time the app starts, and every time you come back to it, it runs a check through Google’s User Messaging Platform, the software behind Google’s consent form. It runs for every player, whether ads are on or off and whatever your age range, because the answer tells the app two things: whether privacy laws where you are call for a consent form, and whether Settings > Privacy should show Privacy choices. The check itself shows nothing on screen.

Like any request over the internet, the check reaches Google from your device’s internet address, and Google works out the answer for your region. Google’s data disclosures for its ads software don’t list what the check sends; it may also carry details about your device and the app, such as the device model, operating system, language and screen size, the app’s name and version, the version of Google’s software and any choices you’ve already made in Google’s form. Google’s privacy declaration for this software on iPhone and iPad lists approximate location, performance data and product interaction, used to make the app work, not linked to your identity and not used for tracking, and lists no device identifier.

What happens next depends on the answer:

  • Where no consent is needed, the app tells Google Analytics that it may use its usual storage (section 5).
  • Where consent is needed, usage statistics stay limited until you give it (section 5). Where ads can run, Google’s consent form asks for your choices at a natural break, never during a table, and your answers then decide what Google Analytics and Google’s ads software may store. The form keeps your answers on your device.
  • Where privacy laws call for it, Settings > Privacy shows Privacy choices, whether ads are on or off. It opens Google’s privacy form, so you can make or change your choices at any time.

The Share usage and crash reports switch doesn’t stop this check, because the app needs its answer to follow privacy laws.

5. Usage statistics

While Share usage and crash reports is on, the app sends usage statistics to Google Analytics for Firebase, so we can fix problems, improve the game and test how often ads show. They include:

  • events such as a table started, cleared or left, a result card left, help used, the practice table opened, finished or skipped, a streak saved or a night off used, a setting changed, a table code entered, the share sheet opened, the app opened from the evening reminder or from a link, the rating prompt requested, Report an ad opened, chances to show an ad, and ads offered, shown or closed;
  • details of those events, such as which table it was (by an internal number), its size, grade and shape, how many hints, undos and shuffles it took, and the new value of a changed setting;
  • the name of each screen you open;
  • a few broad descriptions: your streak and tables cleared in bands, the kind of your first cleared table, your tile size and theme, whether reminders and sound are on, whether the device is a phone or a tablet, and whether ads are switched on in the remote settings;
  • what Google Analytics collects itself, as Google describes it: a random app-instance identifier for this installation of the app; on iPhone and iPad, also the identifier Apple gives all apps from the same developer on your device (Apple’s identifier for vendor); sessions, how long the app is on screen and other app lifecycle events; the app version and the store that installed it; the device model, the operating system and its version, the language, and a coarse location, such as your country or city, which Google works out from a masked form of your device’s internet address. Because the app uses Crashlytics, Google Analytics also records an event when the app crashes.

The app’s own events never include your name, anything you type, the names you give friends’ tables or your age range.

Where ads run, Google’s ads software also adds its own events to these statistics automatically: each ad request, each ad shown and how long it stays on screen, each tap on an ad and each reward given, with an identifier for each ad event.

Google Analytics in this app is set not to collect your device’s advertising identifier: on Android we switch that collection off, and on iPhone and iPad the app is built with the version of Google Analytics that has no access to it. Google signals stays off, and we don’t link Google Analytics to Google Ads or share audiences from it.

How much Google Analytics stores depends on the privacy check (section 4). Until the check answers, the app holds its events, for up to 8 seconds after the check begins. Where no consent is needed, Google Analytics then uses its identifiers as described. Where consent is needed and you haven’t given it, the app keeps analytics storage denied: Google says Google Analytics then won’t read or write app identifiers, and sends events without device or user identifiers, which Google calls cookieless pings: events with coarse details that can’t directly identify you, which may also carry a short description of your device and its system, its screen resolution and its internet address. Google says Google Analytics doesn’t store or log internet addresses. If the check doesn’t answer in time, events go out with storage as it was last set, which on a new installation means denied. Turning off Share usage and crash reports stops even the cookieless pings.

We may copy these statistics to Google BigQuery, Google’s data warehouse, to study them. Section 15 says when any copy is deleted.

6. Crash reports

While Share usage and crash reports is on, the app sends crash reports to Firebase Crashlytics, so we can find and fix problems. When the app crashes or meets an error, a report includes:

  • the error and where in the app it happened, the app’s state, and details about your device at that moment, such as its model and operating system;
  • a random Crashlytics installation identifier, which counts how many players a problem affects, and the Firebase installation identifier;
  • a few notes the app adds itself: the screen you were on, the kind of build, whether ads are switched on in the remote settings, and short fixed messages about the app’s start-up and the screens you opened;
  • with Google Analytics, the usage events from just before the problem.

Crashlytics also uses Firebase sessions, which record app details (such as the operating system, the software versions and the network type), your device’s maker and model, and when the app comes to the foreground or goes to the background, under a random identifier for each session. The notes the app adds never include your name, anything you type or your age range.

7. Share usage and crash reports

Settings > Privacy > Share usage and crash reports is on when you install the app, and its note in the app says what it’s for. The app remembers your choice, and the game works the same either way.

Turning it off:

  • stops usage statistics at once: the app switches Google Analytics off before anything records the change, so even the switch-off isn’t reported, drops any events it’s still holding, and sends no more events, screen names or cookieless pings;
  • stops crash reports: the app stops recording errors at once, switches Crashlytics off and deletes any crash reports waiting on your device; Google says Crashlytics applies a switch-off from the next time the app starts. Firebase sessions stop with Crashlytics.

Turning it back on starts both again. Crash reports from the time it was off are deleted, not sent.

It doesn’t stop:

  • the privacy check each time the app starts (section 4);
  • remote settings, the Firebase installation identifier they use and, possibly, the broad descriptions and first-open time that Remote Config reads from Google Analytics (section 8);
  • ads and the information Google collects for them (section 9): Privacy choices, the tracking setting and your advertising identifier settings cover those (section 17);
  • the age-range check, which stays on your device (section 10);
  • anything your app store, your device’s operating system or its backups collect under their own policies.

8. Remote settings

The app reads remote settings from Firebase Remote Config. They control whether ads are on, which kinds can show, which ad units the app uses and the limits on how often ads show after tables (section 9). They hold nothing about you.

The app fetches them when it starts and when you come back to it, at most once an hour, and while it’s open Firebase can send it a change as soon as we publish one. A change takes effect only when the app starts, when it first reaches Home, or when you come back to it.

To pick the right values, Remote Config receives the Firebase installation identifier, your device’s country, language, time zone and operating system version, the app’s Firebase identifier, its package or bundle name, its version and build number, and the version of Remote Config’s own software, with a short description of your device, its system and the Firebase software. Because the app uses Google Analytics, Google says Remote Config also receives the broad descriptions in section 5 and when the app was first opened. The app itself adds only the kind of build it is, such as a release build.

Remote settings work the same whatever the Share usage and crash reports switch says and whatever your age range, because they control the ads. We may use Firebase A/B Testing to try looser ad limits with some players, always within the floors in section 9, and we read the results from the usage statistics of players who share them. If you’re in a test, Firebase adds which group you’re in to your usage statistics.

9. Ads

Oilcloth is free to play with ads from Google AdMob. There are no in-app purchases.

How ads work

  • An ad you didn’t ask for can show only after you clear a table, when you leave its result card for Home. None shows when you choose Next table or More tables, while a table is in progress, when the app starts, or when you come back to it.
  • With the limits the app starts with, none shows in your first 3 sessions or your first 5 cleared tables. After that, at most one shows for every 2 cleared tables, at least 4 minutes after the last ad of any kind closed, and never in the first 4 minutes of a session. A session starts when you open the app, or when you come back to it after 30 minutes or more.
  • Remote settings can change these limits, but the app accepts looser ones only inside fixed floors, and we loosen them only in Firebase A/B tests: at most one such ad per cleared table, at least 2 minutes after the last ad of any kind and after a session starts, and none in your first 3 cleared tables, though in a test one may show from your first session.
  • During a table, the only ad that can show is one you ask for. Once a table’s free hint, undos or shuffle are used, the app may offer one more for a short ad. If no ad can load, you get the help anyway; if you close the ad early, that help isn’t given. If you miss a night with no night off saved, Home may offer to keep your streak; any ad for it plays only if you tap that offer.
  • There are no banner ads, and the app asks only for ads rated for a general audience.

What Google collects for ads

The app starts Google’s ads software only when ads are switched on, the privacy check allows ads, and your app store’s age range allows them (section 10). Once it runs, Google says it collects:

  • On Android: your device’s internet address, which can show its general location; how you use the app, such as launches, taps and video views; performance information, such as launch time, hang rate and energy use; and identifiers: the Android advertising identifier, the app set identifier and, where they apply, identifiers for accounts signed in on the device. Google says it collects and shares this for advertising, analytics and fraud prevention, and that it’s encrypted in transit.
  • On iPhone and iPad: your device’s internet address, which can show its general location; crash logs not tied to you; performance data, such as launch time, hang rate and energy use, and other diagnostic data; a device identifier, which is the advertising identifier only if you allow tracking (see Tracking on iPhone and iPad below) and otherwise an identifier limited to the app or its developer; the ads you’ve seen; and how you use the app, such as taps and video views. Google’s privacy declaration for this software gives third-party advertising, advertising for the developer and analytics as the uses of most of this data, and lists the general location, the device identifier, the ads you’ve seen and how you use the app as linked to you. Google says it may share some of this with other companies that display ads.

Where no advertising identifier is available, for example when you don’t allow tracking or have deleted your advertising identifier, Google says its ads software can use an identifier of its own, limited to this developer’s apps, to choose more relevant ads; the controls on each ad let you turn that off. On iPhone and iPad, where ads may be personalized, Google may also share Apple’s identifier for vendor with companies bidding to show an ad.

Google may store and read information on your device to show, limit and measure ads. Google controls the information it collects for ads, under its own privacy policy, and How Google uses information from sites or apps that use our services explains more. The app never passes your age range or anything about it to Google, and it sets no age-related value on ad requests.

On Android, one part of Google’s ads software starts with the app every time, for every player, even when ads are off; the app doesn’t start ads or ask for one then, but that part may contact Google on its own. Where your device still offers Android’s Privacy Sandbox, which Google says is now deprecated, Google says its ads software uses the sandbox’s Topics feature (interest groups your device works out) and its attribution reports. Google’s ads software and Google Analytics also declare access to the sandbox’s ad identifier and attribution reports, and Google Analytics declares access to Google Play’s install referrer, which can say what led to the app being installed.

Report an ad, in Settings > Privacy where ads can show, and Report the last ad on the play screen, open an email to us with details of up to 5 recent ads: when each showed, what it was for, the identifier Google gave it, and the app and system versions. It holds no advertising identifier, and nothing is sent until you send it.

Tracking on iPhone and iPad

Google’s ads software can use your device’s advertising identifier to follow activity across other companies’ apps and websites, so the app asks first with Apple’s App Tracking Transparency prompt. It asks once, only when ads are on and your age range allows them, after Google’s consent form if that’s shown, and never during a table or over an ad. If you ask the app not to track, Apple gives it no advertising identifier, and the game works the same. You can change your answer in the Settings app under Privacy & Security > Tracking.

10. Your age range and ads

Ads can show for you only when the age range your app store reports allows them. To check, the app asks your app store for the age range it has for you, if it has one: on iPhone and iPad through Apple’s Declared Age Range, only when Apple says age features apply to you, and on Android through Google Play’s age signals. Either may show a system screen asking whether to share it, never during a table.

The app works out on your device whether the answer allows ads, then discards it. It keeps only that result, ads allowed or not, and the date it checked, on your device. It never stores your age range and never sends it anywhere: not to us, not to Google Analytics, Crashlytics or Remote Config, and not to Google’s consent or ads software. It uses the result for nothing but ads. When the result is that ads can’t show, your usage statistics include no ad events, as for every player when ads are switched off in the remote settings.

  • If your app store reports that you’re under 18, ads never start for you: no ad is requested, Google’s consent form and Apple’s tracking prompt aren’t shown, Report an ad is hidden, and help that would cost an ad is free. If that report arrives while the app is open, ads stop at once.
  • If your app store reports an adult, or no age range, ads can show as section 9 describes.
  • If the check fails and the app has no earlier result, no ad starts for that launch.

Everything else works the same for every player: the privacy check still runs (section 4), Privacy choices still shows where the law calls for it, and usage statistics and crash reports follow the Share usage and crash reports switch.

11. Children

Oilcloth is made for adults and isn’t directed to children. Players the store reports as under 18, including children under 13, never get ads from the app (section 10). For those players, four things still run, for the reasons given above: the privacy check each time the app starts, which the app needs to follow privacy laws; remote settings, which tell the app whether ads are on; on Android, the part of Google’s ads software that starts with the app; and usage statistics and crash reports, which help us fix problems and which Settings > Privacy > Share usage and crash reports turns off. For these players, the identifiers that usage statistics and crash reports use serve only to keep the app working, to understand how it’s used and to fix problems: Google Analytics in this app is set not to collect the advertising identifier, Google signals stays off, Google Analytics isn’t linked to Google Ads, and nothing is used to contact anyone or to build a profile for ads. If you believe a child has used Oilcloth and you want something done about it, please contact us (section 21).

12. When you contact us

If you email or call us, we receive your email address or phone number and what you tell us. Settings > Help > Help and support opens an email that adds the app version and your device’s operating system and version; Report an ad adds the details in section 9. Nothing is sent until you send it yourself. We use what you send only to answer you and to fix problems. Our email is hosted by Google (Gmail).

13. This website

This website sets no cookies and runs no scripts, analytics, ads or trackers, and its fonts and images come from the site itself, so no other site is contacted when you read it. It’s hosted by Google on Firebase Hosting, which keeps the internet address of each visit for a few months, to protect the site and to count visits. Links to other sites, such as Google’s pages and the app stores, lead to pages under those sites’ own policies.

14. Who receives data

  • Google, working for us, runs Firebase (crash reports, remote settings, A/B tests, the installation identifiers they use, and the hosting of this website) and Google BigQuery, where any copy of usage statistics would be kept. For Firebase, Google says it generally acts as our data processor and service provider under Firebase’s data processing terms, and doesn’t pass the data it collects for us to other companies except its own subprocessors or on our instructions.
  • Google, for usage statistics, runs Google Analytics for Firebase, which Google says is a separate service under separate terms. Google Analytics has data sharing settings that can let Google use the statistics for its own products and services; Google says that with all of them off, the statistics are used only to provide and maintain Google Analytics. We keep all of them off.
  • Google, for ads, controls what its ads software collects, under its own privacy policy (section 9). Google also runs the privacy check and its consent form for the app (section 4).
  • Apple and Google, as app stores and operating systems, handle downloads, ratings, the age range, notifications and device backups under their own policies. The stores also give us their own statistics, such as installs, ratings and, from players who allow it in their device settings, crash reports.
  • The law. We’ll disclose information if the law requires it, or to protect the rights, safety or property of players, us or others.
  • A new owner. If someone takes over Oilcloth, the information we hold would pass to them, and they’d be bound by this policy.

Google, which receives data from the app for us and for ads, gives it the same or equal protection as this policy describes: under Firebase’s data processing terms and the Google Analytics terms for the services it runs for us, and under its own privacy policy and its terms with us for ads.

We don’t sell personal information for money. Section 19 explains how ads may still count as sharing under some United States laws.

15. How long data is kept

Data When it’s deleted
What the app keeps on your device When you delete the app or clear its storage; a device backup keeps its copy under your backup settings
Usage statistics Event-level records expire 14 months after they were collected, and records tied to an installation’s identifiers no later than 14 months after that installation was last used; Google removes expired records in a monthly cleanup. The totals in reports carry no identifier
Copies of usage statistics in Google BigQuery 60 days after each day’s copy is made while we use Google’s free sandbox, and never more than 14 months after it’s made if we leave the sandbox
Crash reports After 90 days, when Google starts removing them from its systems
Firebase sessions Google publishes no period for them; new ones stop when you switch off crash reports (section 7)
Firebase installation identifier Kept by Firebase with no set end date: Firebase deletes one only when asked to, the app never asks, and we can’t pick out yours (section 18). Once one is deleted, it’s removed within 180 days
Website visits Google keeps the internet address of each visit for a few months
Emails and calls Up to two years after our last reply, or sooner if you ask us to delete them
What Google collects for ads and for its consent form As Google decides under its own policy; How Google retains data we collect explains it

16. Where data is processed, and how it’s kept safe

We work from India, so your emails and requests are handled there. Google processes Firebase data wherever Google or its agents have facilities, which may be outside your country, and its Firebase privacy and security page describes the safeguards it uses when data crosses borders. Google handles the information it collects for ads under its own privacy policy. While your information is in India, the United States or another country, the courts, law enforcement and national security authorities there may be able to access it under their laws.

Security

What the app sends is encrypted in transit: Google says Firebase encrypts the data it collects for us on the way, and that on Android its ads software and Google Analytics use Transport Layer Security. On your device, the app keeps its data in its own private storage. Only we can sign in to the accounts that hold the data Firebase keeps for us and to our email. No system is perfectly secure, so we can’t promise that information will never be exposed.

17. Your choices

  • Usage statistics and crash reports: Settings > Privacy > Share usage and crash reports (section 7).
  • Ads and your consent: Settings > Privacy > Privacy choices, where privacy laws call for it (section 4).
  • Tracking on iPhone and iPad: the Settings app, then Privacy & Security > Tracking, with Oilcloth off.
  • Your advertising identifier on Android: the Settings app, then Privacy > Ads (the place varies by phone). You can reset it, which gives you a new one not linked to the old, or delete it, so apps receive only zeros.
  • Ads inside the app: the controls on each ad let you turn off ads chosen with Google’s own identifier for this developer’s apps (section 9).
  • Ads across Google: Google’s ad settings let you see and control what Google uses to show you ads.
  • The evening reminder: Settings > Reminder > Evening reminder in the app, and your device’s notification settings.
  • Everything on your device: delete the app, or clear its storage on Android. Your data and how to delete it gives the steps.

18. Your rights

Wherever you live, you can ask us what information we hold about you, and ask us to correct it, delete it or give you a copy. It’s free. Email harshitkikani9081@gmail.com or call +91 95122 03345. We reply within two business days and complete your request within 30 days.

The honest limit

The app has no accounts and never sends your name, email address or phone number. Usage statistics and crash reports are filed under identifiers that the app doesn’t show you: random ones and, for usage statistics on iPhone and iPad, Apple’s identifier for vendor. So a message from you can’t be matched to them. That keeps them apart from your name and contact details, but it also means we can’t pick out your records to show, correct or delete on request. What works instead: switch off Share usage and crash reports, reset or delete your advertising identifier, use Privacy choices and the controls on each ad, or delete the app; and usage statistics and crash reports expire on the schedule in section 15. Write to us anyway: we can delete every email and message you’ve sent us, and tell you exactly what kinds of data the app sends, and where.

19. Your rights where you live

California

We follow the California Consumer Privacy Act, as amended, for every player in California. This is our notice at collection.

Category What it is here Where it comes from Why Who receives it
Identifiers Advertising identifier, app set identifier and other device identifiers used for ads (ads only); app-instance, Firebase installation, Firebase session and Crashlytics installation identifiers; Apple’s identifier for vendor on iPhone and iPad (usage statistics, and ads where they run); your device’s internet address; your email address or phone number if you contact us Your device; you Ads, usage statistics, crash reports, remote settings, answering you Google
Internet or other electronic network activity How you use the app, the ads you see and interact with, and crash and performance data Your device Fixing problems, improving the game, testing ad limits, showing and measuring ads, preventing fraud Google
Geolocation data A general location worked out from your device’s internet address, and your device’s country and time zone; never your precise location Your device The privacy check, remote settings, usage statistics, ads Google
Inferences We don’t build a profile of you; the broad descriptions in section 5 only group how the game is played. Where ads run, Google may use what its ads software collects to infer interests for choosing ads Your device Showing and measuring ads Google

We collect no sensitive personal information. How long each kind is kept is in section 15.

Sale and sharing. We don’t sell personal information for money. When ads run, Google’s ads software collects identifiers, app activity and a general location to choose and measure ads, which California law may treat as a sale or as sharing for cross-context behavioral advertising. We don’t sell or share the personal information of anyone we know to be under 16: when your app store reports that you’re under 18, the app never starts ads or asks for one for you (on Android, section 9 describes the part of Google’s ads software that starts on its own).

Your rights. You can ask to know what personal information we collect, use and disclose; ask us to delete or correct it; opt out of its sale or sharing; and you won’t be treated differently for using any of these rights. To opt out, use Settings > Privacy > Privacy choices where it shows, keep tracking off on iPhone and iPad, delete your advertising identifier on Android, and use the controls on each ad. The app has no account, so these settings, which work on your device, are how an opt-out applies. If you email or call us to opt out, we’ll reply within two business days with the steps for your device.

Making a request. Email or call us (section 2). We reply within two business days and complete your request within 30 days, inside the 45 days the law allows. Someone you authorize can ask for you with your written permission. To protect you, we answer a request about your emails or calls only from the email address or phone number you used, and we may ask you to confirm it. For the data the app sends, we tell you what kinds it sends and where, because we can’t match it to you (section 18).

Global Privacy Control. This website collects nothing to sell or share, so a Global Privacy Control signal from your browser has nothing to switch off here. In the app, use Privacy choices.

Other United States states

If you live in another state with a privacy law, such as Colorado, Connecticut, Oregon, Texas or Virginia, you can ask us to confirm whether we process your personal information and to see it, to correct or delete it, to get a copy, and to opt out of targeted advertising and sale, in the ways described for California, and, where your state’s law gives it, such as in Oregon or Minnesota, to get a list of the specific third parties we’ve disclosed it to, which today is Google. We make no decisions about you by automated means that have legal or similarly significant effects. If we decline your request, you can appeal by replying with the word “Appeal”. We’ll answer within 45 days, and if you’re still not satisfied, you can contact your state’s Attorney General.

Canada

If you live in Canada, the Personal Information Protection and Electronic Documents Act applies and, in Quebec, the Act respecting the protection of personal information in the private sector. You can ask to see and correct the information we hold about you, withdraw your consent with the choices in section 17, and challenge how we follow these rules. In Canada, Google’s consent form isn’t shown, and Share usage and crash reports stays on until you turn it off. KHKikani is the person in charge of protecting personal information for Oilcloth (contact in section 2). If you’re not satisfied with our answer, you can complain to the Office of the Privacy Commissioner of Canada or, in Quebec, the Commission d’accès à l’information du Québec.

Australia

If you live in Australia, we handle personal information in line with the Australian Privacy Principles in the Privacy Act 1988. The information in this policy goes to us in India and to Google, which may process it in countries where it or its agents have facilities, such as the United States (section 16). You can ask to see or correct the information we hold about you, or complain to us: we acknowledge a complaint within two business days and answer it within 30 days. If we don’t resolve your complaint, you can contact the Office of the Australian Information Commissioner.

India

Oilcloth isn’t offered on the App Store or Google Play in India. If you use it there, under India’s Digital Personal Data Protection Act, 2023, you can:

  • ask for a summary of the personal data we process about you, how we process it, and who we’ve shared it with;
  • ask us to correct, complete, update or erase it;
  • withdraw any consent you’ve given, and stop usage statistics and crash reports, at any time, with the choices in section 17;
  • nominate someone to use these rights for you if you die or can’t use them yourself;
  • have a complaint resolved by our Grievance Officer, named in our terms of use, who acknowledges it within two business days and resolves it within one month. If you’re not satisfied, you can then complain to the Data Protection Board of India.

Europe, the United Kingdom and Switzerland

Oilcloth isn’t offered on the App Store or Google Play in the European Economic Area, the United Kingdom or Switzerland, and we have no representative there. If you use the app while you’re there, Google’s consent form (where ads can run) and Privacy choices let you give or refuse consent for ads, and usage statistics stay limited to cookieless pings unless you agree in Google’s form (section 5).

Our legal bases. We rely on your consent, given in Google’s consent form or Privacy choices, for usage statistics that use identifiers and for ads. We rely on our legitimate interests in keeping the app working, safe and lawful for cookieless usage pings, crash reports, remote settings and the privacy check; you can object to the first two at any time with Share usage and crash reports (section 7). We rely on our legitimate interest in answering you for emails and calls. We make no decisions about you by automated means that have legal or similarly significant effects.

Your rights. You can ask us for access to your information, and to correct, delete or restrict it, to give you a portable copy, or to stop using it, as section 18 describes, and you can withdraw your consent at any time with Privacy choices. You can also complain to your data protection authority, listed by the European Data Protection Board, in the United Kingdom to the Information Commissioner’s Office, or in Switzerland to the Federal Data Protection and Information Commissioner.

20. Changes to this policy

If we change this policy, we’ll change the effective date at the top. If a change matters to how your information is handled, we’ll say so on this page and in the app’s release notes before it takes effect, and ask for your consent first where the law requires it.

21. Contact

KHKikani, India

For help with the game, see Support. To delete your data, see Your data and how to delete it. Our terms of use cover the rest. If you’re in India, you can also contact our Grievance Officer.