Privacy policy
Last updated 17 October 2026
log8 is a scorebook for games you play with people you know. This policy explains exactly what it stores, who it is shared with, how long it is kept, and how to get rid of it.
Who is responsible
The controller of your personal data is log8, a partnership firm in India (office: Najafgarh, New Delhi 110043, India). You can reach us at admin@log8.in about anything in this policy, including a request to exercise your rights.
Grievance Officer. Vipul Dalal, admin@log8.in, at the office address above. Write to the Grievance Officer with any complaint about log8, its content or how we handle your data.
Where log8 is offered. log8 is not offered in the European Union, the European Economic Area, the United Kingdom or Switzerland.
What log8 collects
Everything below is collected because a feature needs it, and some of it is also used, under a scrambled code instead of your name, to measure how log8 is used (see how we measure use). There is no advertising identifier, no analytics SDK, no access to your device contacts, no background location, and no tracking across other apps or websites. Location is collected only if you choose to add a place, as described below.
| Data | Why |
|---|---|
| Google or Apple account identifier, name, email | To create and authenticate your account. |
| log8 ID (derived from the part of your email before the @) and display name | So friends can find you and results can name you. Other people can also find you by your exact log8 ID or name, and by your exact email address unless you turn off Let people find me by email in Settings, Privacy. |
| Profile photo from your sign-in provider, or one you upload | To show who is who. |
| Optional: date of birth, gender, height, weight, and a short bio | Profile detail you choose to add. Each has its own visibility control, and all may be left blank. |
| Friends, rooms, and group membership | To decide who can see and approve what. Counted, without names, when we measure use. |
| Matches, tournaments, invites, badges and statistics | The record itself: the purpose of the app. Counted, without names, when we measure use. |
| Activity records: when you sign in, when the app checks in to keep notifications working (which shows the app was opened), what you do in it (logging, approving, adding friends, posting photos, comments and reactions), and the invite or referral link you joined through | To keep your account secure, deliver notifications and run invite links, and to measure how log8 is used. See how we measure use. |
| Invites you send or answer: games, time, place, spots, note, your reply (In, Maybe, Out or waitlist) and who else replied | To run the invite and tell the right people. See invites. |
| Precise location (optional): your phone’s position when you tap Use my location, or when you add a place and location is already allowed, and the area name worked out from it | To show where you played or where an invite is, and to open it in Maps. Read once, only while the app is open. See your location and places. |
| The place you add to a match, tournament or invite: an area name you can rename, plus a map pin if it came from your phone | Shown with the record it belongs to. |
| Photos, captions, comments and reactions you post | Shared with the people who can see the match or room they are attached to. |
| Chat messages | Room and direct messages, and the invite cards sent in them. See security for how these are protected. Message contents are never used to measure use. |
| Notification device token | Registered when you sign in, so notifications can reach this phone once you allow them, and only the kinds you leave on in Settings. Removed when you sign out or delete your account. |
| Reports and support requests: what you reported, the reason and any note, and emails you send to admin@log8.in | So we can review them, reply and act. See support and reports. |
| Crash reports: what went wrong in the app (crashes and some errors that did not close it), and your phone model and system version | So we can find and fix the bug. On by default; you can turn it off in Settings › Privacy. Any web link that shows up in a report is cut down to the site name, so the private part of a link is not sent. See security. |
| Operational logs and audit records | Security, abuse investigation, and debugging. |
Guests
You can record a result against somebody who is not on log8 by adding them as a guest, which stores the name you type and optionally an email. Only add somebody else’s details if you are comfortable doing so; you are responsible for what you enter about other people.
How we measure use
What. log8 measures how the app is used from records it already keeps to run the service: sign-ins, app opens, results logged, approved and played, friend requests, groups, tournaments, badges, photos, comments and reactions, and which invite or referral link people joined through. There is no analytics SDK in the app; the measurement happens on our own servers.
How it is kept apart from you. Each account appears in our internal dashboards as a scrambled code made from its account ID, never as a name, username, email or photo. Message contents, notes, captions, bios and report details are never read for it. Because the code comes from your account, this is still personal data about you, and we treat it that way.
Why. To understand which features are used, how many people play and keep playing, and what to build or fix next. It is never used for advertising, never sold, never combined with data from other companies, and never shared outside the log8 team.
Guests are never named in it: they appear in totals and, for badges, under a scrambled code.
How long. The figures are worked out from the records themselves, so a record that is removed drops out. Deleted accounts are left out of the per-person figures; a match you played with others stays in the game totals, without your name or code. What people did, under a code, goes back 90 days at most.
Your choice. We rely on our legitimate interest in running and improving log8. You can turn this off at any time in the app under Settings, Privacy, Count my use, and your account is left out from then on. You can also object by writing to admin@log8.in.
Support and reports
When you report somebody or something, or email admin@log8.in, we keep what you send, your account and the thing it is about, so we can reply, act and keep a record of safety decisions. The person you report is not told who reported them.
Your location and places
What. log8 only reads your location if you tap Use my location, or add a place while location is already allowed. It reads it once, while the app is open. It saves an area name (for example “Koramangala, Bengaluru”, never a street address) and a map pin. It never tracks you in the background and keeps no history of where you have been.
Why. To show where a match, tournament or invite was, and to let people open it in Maps. It is optional everywhere; you can type a place or leave it blank.
Who sees it. The people who can see the match, tournament or invite it is attached to: the players, and the room if it was shared with one. If you create a share link, anyone with the link sees the place name only, never the pin. Pictures you share (stories) show the area name only. Invites show the place to everyone in the room or chat they were sent to.
Place lookup. Turning coordinates into an area name is done by your phone’s own service (Google on Android, Apple on iPhone). log8 does not send your location to anyone else.
How long. A place is kept with the match, tournament or invite it was added to. Recent places are kept only on your phone.
Removing it. Tap the × on the Location row, or remove it in the Location sheet, before you send. Clear recent places in the Location sheet. Turn location off for log8 in your phone settings at any time. After a match or tournament is logged its place is part of the record and can’t be edited in the app; email admin@log8.in and we will remove it within 30 days. Deleting your account does not remove places from matches, tournaments or past invites that other people share, because they are part of those records too; the same email removes them.
Invites
An invite stores its games, time, place, spots, note, who it was sent to, and each person’s reply. It is shown to the room or chat it was sent to and to anyone you add. When an invite changes or is cancelled, the people who replied are notified. Reminders before an invite are scheduled on your phone; nothing about them is sent to us.
If you reply Accept, the other people who accepted can add you to a match or tournament created from that invite, even if you are not friends yet. Results still need everyone’s approval. Cancelled and past invites stay visible as shared history, like matches do. If you delete your account, your replies and invitations on upcoming invites are removed and the upcoming invites you sent are cancelled.
How it is protected
- Room and direct messages are encrypted where they are stored, with a key held outside the database, so a copy of the database alone cannot be read. log8 holds that key and can read messages, so this is not end-to-end encryption. Your history stays with your account and opens on any phone you sign in on.
- A room message or a direct conversation can be reported, and we read the reported messages in order to act on them.
- Earlier versions of the app encrypted direct messages on the phone. Those messages have been converted on our servers to the protection described above, and the chat keys that were stored for them have been deleted.
- Traffic is encrypted in transit. Photos are stored in object storage and served through short-lived signed links.
- Photos are cleaned before they leave your phone. log8 removes the hidden details a photo carries, including where it was taken and what camera took it, before uploading it. A photo that can’t be cleaned is not uploaded.
- Crash reports can be switched off. Go to Settings › Privacy and turn off Share crash reports. It is on by default. Turning it off also deletes any report saved on your phone that has not been sent yet. Web links inside a report are cut down to the site name.
- Signing out ends your session on our servers, so the sign-in on that phone stops working at once rather than waiting to expire. If your phone can’t reach us when you sign out, it is still signed out on the phone, and the old sign-in stops working by itself after 7 days. Deleting your account ends all of your sessions.
- Photos posted to rooms and matches are scanned automatically for unsafe content and removed if flagged.
Who it is shared with
log8 does not sell personal data and does not share it for advertising. Data is shared with other users exactly as the app describes (the people in a match, room or thread) and with the following processors who run the service on our behalf:
| Processor | Purpose |
|---|---|
| Google Cloud (Cloud Run) | Application hosting |
| Supabase | Managed PostgreSQL database |
| Cloudflare R2 | Photo storage |
| Google Firebase Cloud Messaging | Push notifications |
| Google Firebase Crashlytics | Crash reporting |
| Your phone’s place lookup (Google on Android, Apple on iPhone) | Turns coordinates into an area name, on your device |
| Google Sign-In / Apple Sign In | Authentication |
| Vercel | Hosting for this website |
| Google Analytics | Visit statistics for this website, only if you allow it (see This website) |
We may also disclose data where we are legally required to, or where it is necessary to investigate abuse or protect someone’s safety.
This website
The app has no analytics SDK. This website, log8.in, can use Google Analytics 4 to count visits and see which pages are useful, but only if you tap Allow when it asks. Until then nothing is loaded from Google and no analytics cookie is set. If your browser sends Global Privacy Control, we treat that as no and do not ask.
If you allow it, Google Analytics sets first-party cookies (_ga and _ga_KX77CXNEG7) and receives the pages you visit, the page you came from, your browser and device type, and an approximate location derived from your IP address. Google Analytics 4 does not log or store IP addresses. Google signals and advertising features are off, and nothing is shared for advertising. Google LLC processes this data as our processor and may process it outside India.
Your choice is stored in your browser. Change it at any time with Cookie settings in the footer of every page; saying no removes the analytics cookies.
Where it is stored
log8’s servers and database are hosted in India (Google Cloud asia-south1 and Supabase ap-south-1, both in Mumbai). Some processors listed above may process data in other countries. Where data leaves the country it was collected in, we rely on the processor’s standard contractual clauses or equivalent safeguards.
How long it is kept
- While your account is open: for as long as you keep it.
- When you delete your account: your personal details are removed immediately; see deleting your account for the exact list.
- Shared history is kept permanently. Matches, tournaments, rooms, comments, photos and group messages you took part in belong to the other participants as much as to you, so they remain, shown as “Deleted player” instead of your name. Your name, photo, username, email, sign-in identities and profile details are removed, and the account can’t be searched for, messaged or added as a friend. Direct (one-to-one) chats are deleted for both people. Guests you added stay, so that person can still claim their games.
- Usage measurement is worked out from the records above, so it follows them; see how we measure use.
- Reports and support requests are kept for as long as we need them to deal with the request and to keep a record of safety decisions.
- Operational logs are kept for a limited period for security and debugging, then discarded.
- Website analytics, if you allowed it: the cookies last up to two years, and Google keeps the visit data for the retention period set in our account, at most 14 months.
Your rights
Depending on where you live, including under India’s Digital Personal Data Protection Act, you may have the right to access your data, correct it, delete it, object to or restrict processing, and to data portability. You can delete your account yourself in the app at any time. In the app, under Settings › Privacy, you can download a copy of your data and send us a privacy request. You can turn location off for log8 in your phone settings, and you can remove a place before you send it. For anything else, or if you cannot use the app, write to admin@log8.in and we will respond within 30 days.
Where we rely on consent (notifications, location, the optional profile fields, and analytics on this website), you may withdraw it at any time without affecting what came before. Our other processing is carried out to perform our contract with you, or in our legitimate interest in running a safe and working service, answering support requests, and measuring how log8 is used so we can improve it.
If you are not satisfied with our answer, you can write to the Grievance Officer, and you may also complain to the data protection authority where you live.
Children
log8 accounts are not for children under 13, and a child under 13 may not create one. If you believe a child under 13 has created an account, contact admin@log8.in and we will remove it.
Changes
If this policy changes materially we will update the date at the top and, where the change is significant, tell you in the app.