Legal

Privacy Policy

What the site stores, where it lives and what you can ask us to do with it. The short answer: almost everything stays in your own browser.

Last updated 21 November 2026.

  1. 1. Who we are and what this covers
  2. 2. The short version: what is stored where
  3. 3. What stays in your browser
  4. 4. What we do not collect
  5. 5. What any web server sees
  6. 6. The admin cookie (site operators only)
  7. 7. Contributions
  8. 8. The community poll
  9. 9. Removal requests
  10. 10. How long we keep things
  11. 11. Your rights
  12. 12. Children
  13. 13. Changes to this policy
  14. 14. Contact

Section 1Who we are and what this covers

This policy explains what information gtamapfinder (the “site”) handles when you use it, where that information lives and what you can ask us to do with it. The site is run by gtamapfinder (“we”): [operator name], [country]. For the purposes of data-protection law, the operator is the controller of the information described in sections 6, 7, 8 and 9.

It covers the public site and its contribute form. It does not cover other websites we link to, such as the wikis and open-source projects on Credits or GitHub, which have their own policies.

Section 2The short version: what is stored where

WhatWhere it livesWho can see it
Your tracker progress, playthroughs, route and notesYour browser’s local storage, on your deviceOnly you. It is never sent to us.
Whether you dismissed the storage notice, and your sound settingsYour browser’s local storageOnly you.
A contribution you send through the formThe site’s database, and possibly a private GitHub issueThe site operators who review it; the credit name becomes public if accepted.
A forum post you writeThe site’s database, with your account id and the timeEveryone: forum posts are public and show your account’s display name.
Your vote in the community poll, if you cast oneThe site’s database (the vote, a salted hash of your IP address, your browser type and a random browser id); the id also in a cookie, and your choice in local storageThe site operators. Only the totals per game are public.
The admin session cookieOnly in a site operator’s browserVisitors never receive it.

There are no user accounts and no advertising. Visitor counts may come from Cloudflare Web Analytics, which sets no cookies, and more detailed statistics (Google Analytics 4) run only if you allow them; section 4 says what each collects.

Section 3What stays in your browser

The tracker works without an account because everything you do in it is saved by your browser, on your device, using a standard feature called local storage. The site reads those values back when you return on the same browser. They are not sent to our servers, we cannot see them, and they do not follow you to another browser or device unless you export a playthrough as a file and import it yourself.

The values are named with a gmf: prefix:

KeyWhat it holds
gmf:progress:<game>:<playthrough>The items you ticked in one playthrough of one game.
gmf:profiles:<game>Your list of playthroughs for a game and which one is active.
gmf:route:<game>The route you chose (story, story and side, 100%).
gmf:notes:<game>The notes you typed on spots.
gmf:sound, gmf:fullscreenWhether sound effects are muted, and whether a map page fills the whole window.
gmf:<game>:basemap, gmf:gta6:iconpackThe base map and the GTA VI icon pack you picked.
gmf:analyticsYour yes or no to Google Analytics. Nothing from Google loads until it says yes.
gmf:noticeThat you dismissed the small storage notice, so it does not show again.

You can delete all of it at any time: delete a playthrough from the Playthrough menu on a game page, or clear the site’s data in your browser settings. The Cookie and Local Storage Policy has the steps. If you clear it, your progress is gone; export a playthrough first if you want to keep it.

Section 4What we do not collect

  • No email addresses unless you choose to give one: the contribute form does not ask for one, and only email sign-in (section 7) and removal requests ask for it.
  • No advertising and no social-media buttons or pixels. Visitor statistics are off unless the operator turns them on (below).
  • No advertising or cross-site tracking cookies. Besides the analytics cookies below, when analytics is on, the only cookies the site can set are its operators’ login (section 6) and, if you vote, the poll’s random browser id (section 8).
  • No reading of your game saves or your game platform. Progress is only what you tick.

Analytics (Google Analytics 4). Visitor statistics run only when the site operator has set a Google Analytics 4 measurement id; without one, no analytics code is loaded at all. When it is on, you are asked first in the corner card (Allow or No thanks), and nothing from Google loads before Allow; after Allow, each page loads Google’s tag, which sets first-party cookies (_ga and _ga_<id>, up to two years) holding a random visitor id, and sends Google the pages you view, the page you came from, your device, browser and screen size, an approximate location worked out from your IP address (Google says GA4 does not store the address itself) and interactions such as link clicks. We only look at the totals, to see which pages and games are used. Google handles this data for us under its own privacy terms. Your tracker progress, notes and playthroughs are never sent to it.

Cloudflare (delivery and visitor counts). Every request to gtamapfinder.com passes through Cloudflare, which protects and speeds up the site; like any web server, it sees your IP address and browser details to deliver the page, under Cloudflare’s own privacy terms. When the site operator switches it on, Cloudflare Web Analytics counts visits. It sets no cookies, stores nothing in your browser and does not fingerprint you from your IP address or browser. It reports the page you view, the page you came from, your browser and device type, your country and how fast the page loaded, and we only see totals. Because it keeps nothing on your device and does not identify you, it runs without the Allow question.

Our product plan includes optional sign-in (Google, Steam) and verified progress read from Steam later. None of that exists on the site today; if it arrives, this policy is updated first and you will see what each option stores before you turn it on.

Section 5What any web server sees

Like every website, the servers that deliver our pages, data files and images receive the technical details of each request in order to answer it: your IP address, the address of the page or file you asked for, the date and time and your browser’s identification string. Our hosting provider handles these requests on our behalf and may keep short-lived technical logs for security and to keep the service running; we do not use them to build profiles or to track you across sites.

The map images themselves are Rockstar Games’ map tiles, loaded straight from Rockstar’s own servers the same way any image on a web page is loaded. Those servers therefore see the same technical request details for the tiles. That is outside our control and Take-Two Interactive’s privacy policy applies to it. Fonts, icons and reference photos are served by us, so no other third party is contacted when a page loads.

Section 6The admin cookie (site operators only)

The site has a private admin area where contributions are reviewed. Signing in there sets one cookie, gmf_admin: a random session identifier that lasts seven days, is marked HttpOnly, SameSite and (in production) Secure, and is deleted on logout. It is strictly necessary for the admin area to work. Visitors never receive this cookie; it only exists in the browsers of the people who run the site.

To slow down password guessing, the admin login also records a salted one-way hash of the address each attempt came from; entries older than the ten-minute window are cleaned out at the next sign-in. The address itself is not stored.

Section 7Contributions

When you send something through the contribute form we store what the form sends: the contribution type, the game, the title, the description, the optional location and map coordinates, up to five screenshot links, an optional reference link, the optional credit name and the time it was received. Alongside it, for abuse prevention, we store a salted one-way hash of your IP address (so repeated submissions from the same address can be spotted without keeping the address) and your browser’s identification string (user agent). The form also uses a hidden anti-bot field and a timer; a submission caught by them is not stored at all. To limit each address to five submissions per ten minutes, the server holds the address itself in memory for those ten minutes only; it is never written to the database or the logs.

The submission is saved in the site’s database and may also be mirrored as a private issue in the project’s code repository on GitHub, where the reviewers work; that copy holds the form fields, not the hashed address or the user agent. GitHub’s privacy terms apply to that copy.

The credit name is the only part meant to be public. If your contribution is accepted, the name you chose may appear on Contributors, next to the data it changed and in the site’s data files, under the CC BY 4.0 licence described in the Terms of Use. If you leave the name empty, the contribution is anonymous. Please do not put personal details about yourself or anyone else in the title, description or links; the review may remove them.

Our legal basis for keeping this information (where the law asks for one) is our legitimate interest in running a community-maintained map, keeping it free of spam and abuse, and crediting the people who help.

Forum posts and reports

When you post in the forums we store your account id, what you wrote (and the title, when you start a thread), the board and the time. Posts are public: anyone can read them, with your account’s display name. A post or thread that a moderator hides stays in the database, where only the site operators can see it.

If you report a post, we store your account id, which post it is, the reason you picked, anything you add and the time. Only the site operators see reports.

To stop flooding, posting and reporting are rate limited per account, so each post or report also records your account id and the time in the rate-limit table. Our legal basis, where the law asks for one, is our legitimate interest in running the forums and keeping them free of spam and abuse.

If you sign in with email, we store your email address with your account and, for each sign-in code we send, a one-way hash of the code (never the code itself), the time it was sent, its expiry, how many times it was tried and a salted one-way hash of your IP address; a code expires after ten minutes and expired codes are deleted the next time anyone asks for one. The code is emailed through our email provider, Resend. Your account’s display name starts as the part of the address before the @, and shows on your forum posts; otherwise the address is used only to sign you in.

Section 8The community poll

The home page has a vote on which game we should map next. You can vote without an account, once per browser. When you vote we store: the poll and the game you picked, the time, a salted one-way hash of your IP address, your browser’s identification string (user agent) and a random browser id. The browser id is also set in your browser as the cookie gmf_vid (HttpOnly, SameSite=Lax, Secure in production, one year, sent only to the poll’s own address); it holds nothing about you and only lets us tell that this browser has already voted. The hashed address limits how many votes one connection can cast (a few, so a shared household or office still can), and with the user agent helps us spot scripted voting. Your choice is also kept in your browser’s local storage (gmf:poll:<poll>) so the page shows the results right away; that copy never leaves your device. A rate limit of ten votes per ten minutes per connection uses the same hash, held in server memory for those ten minutes; the address itself is not stored.

Only the totals per game are shown publicly, on the home page. The individual votes are seen by the site operators, who can reset the poll. We keep the vote rows until the poll closes; then we keep only the totals per game and delete the rows, with their hashed address, user agent and browser id. Our legal basis, where the law asks for one, is our legitimate interest in running a fair vote that is hard to stuff. You can ask us to delete your vote at any time (section 11); the cookie expires after a year, or clear it yourself in your browser settings.

Section 9Removal requests

Rights holders, and anyone a page is about, can ask us to remove media or data with the form on Credits. When you send it we store: your name, your email address, your organisation if you give one, what you want removed, the page address or item, your description, the time, a salted one-way hash of your IP address and your browser’s identification string (user agent), plus the request’s status and our note on how it was handled. The email address is used only to answer the request; we never add it to a list or use it for anything else. The hashed address limits each connection to five requests an hour and, with the user agent, helps us spot abuse.

Only the site operators see removal requests. We keep each one for two years from when it arrives, as a record of what was asked and what we did, then delete it. Our legal basis, where the law asks for one, is our legitimate interest in handling rights and takedown requests, and keeping a record of them.

Section 10How long we keep things

  • Local storage: stays in your browser until you delete a playthrough or clear the site’s data. We never hold a copy.
  • Contributions: kept, together with the hashed address and user agent, until you ask us to remove them, or until we remove them ourselves (for example when a rejected or spam submission is cleaned out). A contribution that has been placed on the map stays in the data files with its credit name; on request we remove or anonymise the name.
  • GitHub mirror issues: closed when reviewed and deleted when the matching contribution is removed on request.
  • Poll votes: until the poll closes, then reduced to the totals per game; the row with its hashed address, user agent and browser id is deleted. The gmf_vid cookie lasts one year in your browser.
  • Removal requests: two years from when they arrive, with the name, email address, hashed address and user agent, then deleted.
  • Rate-limit addresses: ten minutes, in server memory only. Admin login hashes: the ten-minute window, cleaned out at the next sign-in. Admin sessions: seven days or until logout.

Section 11Your rights

Depending on where you live (for example under the GDPR in the EU and UK, or the CCPA and similar laws in US states) you have rights over information about you. We give them to everyone, wherever you are:

  • Know and access: ask what we hold about you and get a copy.
  • Correct: have something wrong put right, including your credit name.
  • Delete: have your contribution, your credit name or both removed.
  • Object or restrict: ask us to stop using something while we look into a concern.
  • Complain: to the data-protection authority where you live, if you think we handled your information wrongly.

Because the form does not collect an email address, we can only match a request to a submission from what you tell us: the credit name, the title or the time you sent it. Use one of the ways in section 14; we answer within one month. We do not sell personal information and have never done so, and we do not share it with anyone except the hosting and repository services that store it for us.

Your tracker progress is yours already: it is in your browser, and you can see, export and delete it there without asking us.

Section 12Children

The site is for people aged 13 and over and we do not knowingly collect information from anyone younger. If you are a parent or guardian and believe a child under 13 has sent us a contribution, contact us and we will remove it.

Section 13Changes to this policy

We will update this page when the site starts storing something new (accounts, verified progress and forums are all on the roadmap and none is live). The date at the top shows the last change; for material changes we also say so on the site.

Section 14Contact

To ask a question, exercise a right or ask for a contribution to be removed, reach us through