Privacy Policy

Last updated: August 2026

1. Who we are

Everygrid is made by an independent developer, Business ID 3496856-2.

You can reach us at support@everygrid.app.

2. What Everygrid stores on your device

Everything the app needs to work is stored locally on the device you are using:

• the habits you create — their names, colours, icons, and target settings;
• which days you marked, and any partial credit;
• anything you write in a day's note. A note is free text of up to 2,000 characters attached to one date on one habit — a dated journal entry, not a label on a habit. It is the most personal thing Everygrid holds, and it is stored as ordinary text (§3.2 says where it goes if you turn sync on);
• your reminder times;
• your app settings, including which theme you chose;
• if you have connected Google Drive: the sync bookkeeping described in §3, and the email address of the Google account you connected — the app keeps it on the device so Settings can show you which account sync is signed in to.

Your phone's own backup treats this differently on the two platforms, and on iPhone it takes in more than you might expect. On Android, Everygrid keeps its local data out of Google's cloud backup and out of device-to-device transfer, so none of it leaves the phone that way. On iPhone and iPad it is the other way round: the app's settings file is part of your ordinary iCloud or computer device backup — that is Apple's documented behaviour for the file every app keeps its preferences in, and Everygrid does not opt out of it. That file holds the random device identifier (§3.3), the sync bookkeeping flags, and the Sync log (§7.2), which can still be holding note text that one of your devices replaced. So a backup made before you cleared a note can hold that text until that backup is replaced: clearing a note removes it from the app, and no app can reach inside a backup that has already been taken. We could exclude that file from the backup, and we have deliberately chosen not to — excluding it would also drop the device identifier and the flag that records that you once removed a marked day, so a restored iPhone would register as a brand-new device and the app would go back to saying it had never removed anything. That is a worse outcome for you than the one it would fix, so we are telling you instead. §8 says what the same asymmetry means when you change phones.

None of your habits, and nothing you wrote in a note, is sent anywhere unless you turn sync on. With sync off, Everygrid makes no network request that carries anything you typed. The one thing that reaches a network with sync off is a purchase, and that is a transaction between you and your app store (§3.5).

3. What leaves your device

Two things can send anything off your device, and you choose both: turning sync on (§3.1–§3.4) and buying the paid tier (§3.5). Nothing else in the app makes a network request that carries your data.

Sync is off by default. Nothing in §3.1–§3.4 happens unless you go to Settings and connect Google Drive.

3.1 What we ask Google for

Everygrid asks for one Google permission, called drive.file.

Google classifies drive.file as non-sensitive, and Google's own description of it is that it lets an app see, edit, create and delete only the specific Google Drive files it opened or created itself.

In plain terms: Everygrid sees the files Everygrid made, and that is the whole of its reach into your Drive. Your documents, your photos and other apps' files sit outside it.

drive.file is the only permission Everygrid asks for, on either platform.

Signing in does tell the app which Google account you chose, and that account's email address. Everygrid keeps it on your device so that Settings can show you the account sync is connected to, and so it can tell you if you later sign in with a different one. It stays on the device.

3.2 What Everygrid writes, and where

Everygrid creates a folder called Everygrid in your Google Drive and writes files into it, including:

These files are ordinary JSON text, and they are not encrypted. That is a deliberate choice, and the trade-off is stated plainly because you should be able to judge it:

• What you get: you can open these files yourself, read them, copy them, back them up, move them, and delete them, with no tool from us and no permission from us. That includes anything you write in a day's note. If Everygrid disappears tomorrow, your record is still a file you own in a format you can read.
• What you give up: they are readable by anything that can read your Drive — which means Google can read them, and so can any other app you grant access to that folder. We cannot, because they never reach us. Read that with your notes in mind: the same sentence that covers a habit called "Read" also covers whatever you wrote about the day you had. If a particular thought is not one you want sitting in plain text in your Drive, do not write it here — or leave sync off, in which case it never leaves the device at all.

We do not claim this is end-to-end encrypted, and we do not claim we cannot read it in some clever way. It is a plain file in your Drive.

3.3 The device identifier

Each installation of Everygrid generates a random identifier for itself the first time it syncs, and stores it in everygrid_meta.json so that your devices can tell each other apart and merge edits correctly.

It is a randomly generated value. It is not derived from your hardware, your phone number, your advertising identifier, or anything else about you or your device, and it is not shared with anyone. It exists only inside your own Drive file.

Next to it, the same file stores a readable name for each device — usually the name your phone already has, such as "iPhone 15" or "Pixel 8" — because a list of random identifiers would tell you nothing when you look at which devices are syncing. That name is in your own Drive file too, and nowhere else. Anything that can read your Drive can read it (§3.2).

3.4 Who the data goes to

Google — and only Google — for anything to do with your habits. Your habit files go from your device to your own Google account, and Google's handling of them is governed by your agreement with Google, not by ours. Your Google Account settings and Google's own privacy policy apply to them.

The only other party anywhere in this document is your app store, and only if you buy the paid tier (§3.5). It receives a payment, never a habit.

Your Google account is the single destination for anything you record in Everygrid. The app carries the code to reach that one place, and that is the whole of its network behaviour where your habits are concerned.

3.5 If you buy the paid tier

Everygrid's paid tiers are sold by Apple and by Google, through the App Store and Google Play, because their rules require it. The purchase is a transaction between you and the store:

• We never see your card details, your billing address, or your name. The store collects those directly from you, under your agreement with the store.
• We keep no purchase record of our own. There is no server of ours for one to sit on. The app asks the store, on the device, whether this device is entitled to the paid features, and that answer stays on the device.
• No habit data is involved in a purchase. The two never touch.

What we do receive is what every developer receives, in the stores' own dashboards and never through the app. There are two kinds of it, and they behave differently:

• Sales figures. The App Store and Google Play tell us how many purchases were made, in which country, on which day, and what we were paid. Those are counts and totals for the app, not facts about a person, and they do not tell us who you are.
• Usage and crash statistics — only from people who chose to share them. Apple states that its analytics "only include data from users who have agreed to share their diagnostics and usage information with app developers". Google states that the crash statistics it shows developers come "from Android devices whose users have opted in to automatically share their usage and diagnostics data". That choice is one you make with Apple or Google, in your device's settings, not with us.

Both kinds are Apple's and Google's own measurement, not ours, and neither carries anything you typed into Everygrid.

4. What Everygrid does not do

These are all verifiable in the app's behaviour, and they are the same answers we filed with Apple and Google:

• No advertising. No ad SDK is in the app.
• No analytics in the app. Everygrid contains no analytics SDK and measures nothing. We do not know how many habits you have, whether you opened the app today, or whether you kept a streak. The only usage figures that exist anywhere are the aggregate ones Apple and Google show every developer in their own dashboards (§3.5) — never anything you typed, and never tied to you.
• No crash reporting in the app. Everygrid contains no crash-reporting SDK and sends no crash or diagnostic report anywhere. If your Android phone is set to share usage and diagnostics with Google, Google's own crash statistics for this app may appear in our Play Console — that is Google's collection, made under your Android settings and not by our code, and it carries none of your habit data.
• No tracking. Everygrid does not track you across apps or websites, does not link anything to third-party data for advertising, and shows no App Tracking Transparency prompt because there is nothing to prompt about.
• No location. Everygrid requests no location permission of any kind.
• No health or fitness data. Everygrid does not connect to Apple Health, Health Connect, a wearable, or any other health source. Habits you type are habits you typed; nothing is imported.
• No contacts, no calendar, no photos, no microphone, no camera.
• No fingerprint or face check. Everygrid contains no biometric code and calls no biometric API. Two Android permissions with those words in their names — use biometric hardware and use fingerprint hardware — are nonetheless in the Android build's permission list, which Google Play can show you: they arrive inside Google's own sign-in library, not from anything we wrote, and nothing in Everygrid asks for them or uses them. We would rather name them here than have you find them and wonder.
• No selling or sharing of your data, which would in any case require having it.

Everygrid is not a medical device. It does not diagnose, treat, cure or prevent any medical condition.

5. Children

Everygrid is intended for adults, and we declare an adult audience to both app stores. It is not directed at children, and we do not knowingly collect anything from children. We hold nothing that identifies anyone: no name, no email address, no account of ours. (If you connect Drive, the app itself knows the email address of the Google account you chose and keeps it on your device — §3.1 — and your Drive files carry a random per-install identifier and a device name — §3.3. None of that reaches us.)

6. What we filed with the app stores

We publish this so that our store filings and this page cannot quietly diverge.

On "collected". Apple and Google define that word differently, and we answered each on its own terms. Data does leave your device when you sync, so we answered yes rather than argue a technicality — even though the destination is your own Google account and we ourselves have no way to reach it.

We have not been independently security-audited. We say so here because we said so on the form.

7. Your controls

This section is the page Google Play's data-deletion requirement points at. Everything here is a control inside the app; none of it requires emailing us, and none of it requires our permission.

7.1 Stop syncing on this device

Settings → About my data, under "Removing it" — the first of the two actions there. (About my data is reachable straight from Settings, or through Settings → Sync.)

Stops syncing on that device only.

• Nothing in your Drive is deleted. Every file stays. The app makes one small edit to the bookkeeping file (everygrid_meta.json) to take this device out of the device list, and nothing else — no habit file is created, changed or deleted. If even that edit fails, the app carries on and tells you the device may keep appearing in the list until another device syncs.
• Your habits on that device are untouched. The app keeps working offline.
• Your other devices are unaffected and keep syncing normally.

7.2 Delete my Drive data

Settings → About my data, under "Removing it" — the second action, and it is confirmed on a screen of its own.

Deletes the habit files Everygrid created in your Google Drive. The app names every file it deleted — and the one file it kept — on screen, as it does it.

It also clears one thing on the phone you use it from, and the app says so on screen while it does it: the Sync log. That is Everygrid's own list of what each merge changed when two of your devices had edited the same thing, and it is the only place a note's replaced text is ever kept. The app's wording for it is:

"Also cleared on this phone: the Sync log — the list of what merges changed — including anything it was still holding so you could undo it."

Stop syncing on this device (§7.1) leaves the Sync log where it is, deliberately: it is that device's own account of what sync did to that device's data, and it is the thing to read when you think something went wrong. Text you erased is not what it is left holding — that is removed when the erasure arrives, not when sync stops.

Two things are deliberately kept, and we would rather you hear it here than discover it later:

The Everygrid folder and the everygrid_meta.json file inside it are kept. After a deletion that file is about 200 bytes and contains no habit data — a schema version, and a note that sync was turned off, carrying the date and the name of the device you did it from. It is kept so that your other devices can be told that you turned sync off, rather than reporting that your folder has mysteriously gone missing. If you do this more than once, each of those notes is kept, for the same reason: a device that was switched off across two of them still has to be able to find out what happened.

The app tells you this before it does anything, and then offers deleting the now-empty folder as a separate, separately confirmed step. If you take that step, your other devices will report the folder as missing instead of being told sync was turned off. Their own habit data is still untouched.

What "Delete my Drive data" does not do: it does not touch the habits, the days you marked or the notes stored on your device, or on any other device — the one local thing it clears is the Sync log described above. No device ever deletes your local habits because of something another device did. Only you, on that device, can clear that device.

What happens to note text your devices disagreed about, and to a note you cleared. The Sync log is the only place inside Everygrid where anything is kept on a clock. It is not the only place that text can be, so this takes three sentences rather than one, and the third is the price of the second being true. These are the same three sentences, word for word, that the in-app About my data screen carries:

"When two of your devices write different text on the same day's note, the device that merges them keeps the replaced text on itself — never uploaded — for up to 90 days, so you can put it back; if both devices sync, each keeps its own copy for that time. When you clear a note, Everygrid keeps no copy of the text: it goes from the device you cleared it on straight away, and from every other device as soon as that device syncs. Two things outside the app can still hold it for a while: Google Drive keeps its own earlier versions of the files we write, typically for about 30 days, and on iPhone and iPad a device backup made before you cleared the note holds whatever was on the device at the time, until that backup is replaced."

If a partial failure means some file could not be deleted, Everygrid stops, changes nothing else, and tells you exactly which files are still there — rather than reporting a success it did not achieve.

7.3 Withdraw Everygrid's access at Google

You can revoke the permission from your Google Account at any time, independently of us, at myaccount.google.com/linkedapps.

Note what this does and does not do. Google's own wording: "If you delete a link, Google stops automatic sign-in to the app. This doesn't delete your data on the app." Revoking access stops Everygrid reaching your Drive; it leaves the files in your Drive. To remove them, use §7.2 or delete the Everygrid folder yourself in Drive.

7.4 Delete the files yourself

They are your files, in your Drive. Open Drive, open the Everygrid folder, and delete what you like — you do not need the app to do it, and you do not need us. Three things decide whether the deletion actually removes what you meant to remove, and we would rather tell you than let you find out.

1. Know which file holds what. Deleting the wrong file removes nothing you were trying to remove:

2. Turn sync off first, or the app will put it back. A device that still holds your habits and still has sync switched on re-writes the full contents of these files on its next sync. It is not ignoring you: that is the same mechanism that repairs a file left half-written by a failed upload, and it cannot tell your deletion apart from that damage. So either

• use §7.1 on every device that syncs this account (or sign out, or uninstall) before you delete anything in Drive; or
• use §7.2 "Delete my Drive data" instead, which is built for exactly this: the app deletes the files itself and leaves a note in the bookkeeping file that tells your other devices sync was turned off, so none of them uploads it all again.

If you delete the whole Everygrid folder while a device is still syncing, that device will not silently re-create it. It stops, tells you it cannot find your folder, and asks you what to do — and one of the choices it offers is to upload everything from that device again, which would put your notes back. If you meant the data to be gone, choose the option that turns sync off.

3. Deleted in Drive is not deleted yet. Google puts deleted files in your Drive Trash first, where they remain readable by anything that could read them before — Google's own page states that "Files you move to the Trash are deleted forever after 30 days" and that emptying the Trash is what deletes them now. Empty the Trash, or delete the files from it individually, if you want them gone rather than pending. (Everygrid itself looks in your Trash before it concludes a folder is missing, and offers to restore it — so a folder sitting in the Trash is still a folder the app can bring back.)

None of this touches the copy on your device: deleting files in Drive never deletes your local habits or notes (§7.2), and no device ever deletes local data because of something another device did.

7.5 Getting a copy of your data

You are never required to pay to get your own data out. What that means in this version depends on whether you use sync:

• With sync on, your data is already a file you own. Settings → About my data → Open in Drive takes you to the Everygrid folder, and the files there are plain JSON you can read, download or copy anywhere — no tool from us, no paid tier, no permission from us (§3.2).
• A dedicated "Export a copy" — one file written to a destination you pick, without turning sync on — is planned and is not in this version. We would rather tell you that here than let you discover it.

7.6 Deleting the app

Uninstalling Everygrid does not delete your Drive files — it removes the app and the copy on that device. If you want the Drive files gone, use §7.2 or §7.4 before you uninstall.

7.7 If you are in the EU, the UK, or a US state with a privacy law

Everygrid runs on your device and in your own Google Drive, so everything about you sits in one of those two places. A request to us to access, correct, export or delete your data would therefore point at the controls above, which are already in your hands and act immediately.

If you have data in your Google Drive, that data is in your Google account, and your rights over it run against Google under your agreement with them.

If you would like to ask us something anyway, write to the address in §1 and we will answer.

8. Data retention

Everything Everygrid holds is held by you, in the two places §3 describes: your device, and your own Google Drive.

Your habit files stay in your Google Drive until you delete them, exactly like any other file you own. Local app data stays on your device until you delete it or uninstall the app.

One thing on your device is kept on a clock rather than until you delete it, and it is the only one. The Sync log (§7.2) records what each merge changed and holds it for 90 days — and that includes note text one of your devices replaced with a different edit. It is kept by the device that merged the two versions, which can be the device whose own text won; if both of your devices sync, each of them ends up holding a copy for that time. It is never uploaded to your Drive.

A note you clear is not kept by Everygrid — and two things outside Everygrid can still hold it for a while. Google Drive keeps its own earlier versions of the files we write, typically for about 30 days. And on iPhone and iPad, a device backup made before you cleared the note holds whatever was on the device at the time, until that backup is replaced (§2 says why, and what is in that backup).

Your device's own backups behave differently on the two platforms, and we would rather say so than let you find out during a phone upgrade. On Android, Everygrid keeps its local data out of Google's cloud backup and out of device-to-device transfer, so a new Android phone starts empty unless you had sync switched on. On iPhone and iPad, the app's local data rides your own device backup like most apps' data, so restoring a backup brings your habits back — and, as §2 sets out, the app's settings file with it, the Sync log included. Either copy belongs to you or to your platform. Neither belongs to us.

Your copies are the copies. When you delete them, that is the end of them.

9. If Everygrid is ever sold

We are telling you this at the start rather than at the point it happens.

Google's rules for apps using Drive permissions (the Limited Use requirements) allow data obtained through the Google API to be transferred as part of a merger, acquisition or sale of assets only after obtaining explicit prior consent from the user. Any buyer of Everygrid inherits that condition.

In practice, the data in question is already in your own Drive and never in ours — but the commitment stands, and we would ask you before anything of the kind happened.

The same rules bind us permanently in three other ways worth stating: data obtained through the Google API may be used only to provide or improve features that are visible to you in the app; humans are not allowed to read it without your affirmative agreement; and it may never be transferred or sold to advertising platforms, data brokers or information resellers, or used to serve ads. This applies to anything derived or aggregated from it too, which is a second and independent reason there will be no analytics on your habits.

10. Security, described honestly

• Everything Everygrid sends travels over HTTPS. The only destinations are Google's sign-in and Drive endpoints, and the app store you bought the app from.
• The permission we hold is the narrowest one Google offers for this job, and it reaches only files Everygrid itself created.
• Your Google sign-in token is held in the platform's own protected storage (the iOS Keychain, Android's equivalent), not in ordinary app files.
• The habit files in your Drive are plain, unencrypted JSON (§3.2), and the local database on your device is not encrypted either.
• We have not been independently security-audited, and we do not claim to have been.

11. Changes to this policy

If we change this page we will change the "Last updated" date at the top. If a change actually alters what the app does with your data — as opposed to making the wording clearer — we will say so in the app's release notes as well, so that you find out from the app and not only from a web page you were not looking at.

12. Contact

support@everygrid.app