Privacy
Last updated: November 20, 2026
Grand Theft Buddy is a fan-made project and is not affiliated with, endorsed by, or sponsored by Rockstar Games or Take-Two Interactive.
This page describes what Grand Theft Buddy actually collects, why we collect it, and who else handles it. Grand Theft Buddy is a fan-made project and is not affiliated with, endorsed by, or sponsored by Rockstar Games or Take-Two Interactive. Questions about this page go to support@grandtheftbuddy.com.
Account data, through Supabase
Creating an account sends your email address to Supabase Auth. If you set a password, Supabase stores it. We do not keep a separate copy of it. We store a profile on that account: display name, platform (PlayStation 5 or Xbox Series X|S), edition, character focus, story chapter number (blank if you are not sure), story-progress bucket, play styles, help topics, beginner mode, whether you opted into spoilers, and whether you want a shareable player card.
We also store the plan, whether the free allowance is unlocked, a referral code, and the referral code you arrived with if the link included one. Supabase hosts this data. Its session cookies keep you signed in.
Phone number, for the one free allowance
The free allowance asks for a mobile number when you create an account. We do not send a text code, and we do not send the number to an SMS provider. We check the number's format, then discard the raw number.
For the one-allowance limit we store a SHA-256 hash of the number in international form, mixed with a secret pepper, and the last four digits. Our tables keep that hash, not the raw number, so the same number cannot unlock a second free allowance. We store the same kind of hash of your normalized email on that claim.
Device fingerprint and IP, for abuse limits
To stop repeat free allowances we create a random device id in your browser. It is saved in local storage and in a cookie named gtb_device that lasts about a year. We also run the open-source FingerprintJS library in your browser. It calculates a visitor id from this browser's characteristics on your device. We send the device id and the visitor id to our server and store only peppered SHA-256 hashes of them on the free-allowance claim.
When you sign up, we read the IP address on the request (the first address in the forwarding header, when one is present). We store a peppered hash of that address, not the raw address, and use the hash to limit how many accounts one network can create in a set window. We apply the same kind of limit to the peppered hash of the device fingerprint when the browser provides one. If the hashing secret is not configured, that limit stays in the memory of the server process and is not written to the database. If a bot check is configured, the sign-up form loads Cloudflare Turnstile and our server checks the result with Cloudflare. When those keys are unset, the check is skipped.
Questions, screenshots, and xAI
When you use the coach, we send your question, a short slice of the recent conversation in that request, a preface from your profile (so the answer can follow your progress and spoiler setting), and any screenshot you attach to xAI. xAI uses that content to generate the reply. If xAI is not configured and an Anthropic key is configured instead, the same content goes to Anthropic. We do not save the screenshot file in our database. For a signed-in account we store the chat so you can open it again. Only that account can read those rows. We do not use the chat to improve answers unless you turn that switch on, and the switch stays off until you turn it on.
We do store an AI usage log: your account, plan, whether the call was a question or a mission debrief, the model name, token counts, whether an image was included, and the estimated and actual cost in dollars. That log is how we watch the site-wide kill switch and the shared free pool. It is not a per-member dollar allowance. Mission debrief notes are sent to the model with the question. The current app does not write those notes into a saved debrief archive.
Checklist check-offs are stored for a signed-in account, and a copy is kept in local storage in this browser.
Tips, contact messages, and the player card
If you submit a tip, we store the text, tags, the spoiler ceiling you picked, your account id, and the moderation status. An approved tip can be shown to other players inside the coach. The contact form stores your name, email, and message so we can reply. A Founding member's message can be flagged for priority.
Generating a player card sends the profile on the card to our server so we can draw the image. We return the image to your browser. We do not save the image. The card shows the display name, platform, progress, character focus, play style, and a founder badge if you have one. It does not include a Rockstar account.
Payments, through Stripe
Checkout is handled by Stripe. We send Stripe your email, our account id, the plan, and a referral code if we have one. Stripe processes the card. We store Stripe's customer id, subscription id, price id, and subscription status. We also store Stripe event ids so a webhook is applied once. We do not store your card number, CVC, or full card details.
Cookies, local storage, and logs
We use these cookies:
- Supabase auth cookies, so you stay signed in.
- gtb_device, the device id described above, for about a year.
- gtb_ref, a referral code from a ?ref= link, for about 60 days.
- gtb_demo, an httpOnly cookie used only when Supabase is not connected. It holds a demo email and usage counters so that browser session can continue.
Local storage holds the device id, a copy of your profile, checklist ticks, and, in demo mode, tips you submitted in that browser. We do not run a third-party analytics or advertising cookie.
The site is hosted on Vercel. The host may keep ordinary technical logs, such as the time, the URL, and the IP address, to run and protect the service. Those logs are not a product analytics profile.
How long we keep it, and what you can ask
We keep account, billing, phone-hash, and usage records while the account is open, and as long as we need them for the seat cap, abuse limits, and payment records. Phone hashes may stay after a deletion request so a closed account cannot be used to claim a second free allowance. Stripe keeps payment records under Stripe's own policy.
Email support@grandtheftbuddy.com to ask for a copy of the account data we store, to correct your profile, or to delete the account data we control. You can cancel a subscription in the customer portal without deleting the account. Clearing cookies and local storage in your browser signs you out and removes the local device id. Hashes already stored for a free allowance stay in place.
The site is for people playing a mature-rated game. We do not knowingly collect information from children. If you believe a child has given us personal information, write to support@grandtheftbuddy.com and we will delete the account data we control.
Goals, affiliates, referrals, and age
These notes are effective November 20, 2026. They describe what this version of the app is built to store.
Goals and progress. If you set a gamer tag, goals, or a progress update, we store the tag, the goal title and type, the numbers you enter, the status (active, completed, or abandoned), optional notes up to 280 characters, and a streak counted from the days you log progress. We do not read your game save. Those numbers are whatever you type. A short summary of your active goals can be sent to the AI coach with a question so the answer can follow them. It is capped in length.
Age. The account form asks you to confirm that you are 13 or older. We store the time of that confirmation. We do not ask for a date of birth. Affiliate applications ask for a separate confirmation that the applicant is 18 or older, and we store that confirmation with the application.
Affiliate applications. The apply form can be used without an account. We store the name, email, a peppered hash of the phone number in E.164 form, the last four digits, how the person says they will market Grand Theft Buddy, the social links they paste, the 18+ confirmation, the disclosure confirmation, and the terms version they checked. We do not store the raw phone number, and we do not send a text message. If an application is approved, we create a sign-in by email or link the application to an account that already uses that email or phone hash. Affiliates can save a PayPal email for a manual payout. We store commission rows, click counts, and payout references.
Referral cookie. A link such as /r/code sets a first-party cookie named gtb_ref for about 60 days when that cookie is not already set. We do not replace it on a later link. At sign-up and at checkout we read that code. Checkout sends our account id to Stripe as client_reference_id, and the referral code in Stripe metadata comes from our database. We store a row that ties the new account to the code. Click logs store a peppered hash of the IP address and the code, not the raw IP, when the phone-hash pepper is configured. The same phone hash cannot collect a second referral bonus. A person cannot earn a referral from their own phone hash or email.
Announcements. The owner can publish an in-app notice, including a start and end time and a plan it applies to. If you dismiss it, we store that dismissal. Email broadcasts are behind a switch that is off. They are not sent, because a postal address for CAN-SPAM is not configured. This app does not send SMS.
Chargebacks. If Stripe reports an open card dispute, we pause the account until that dispute is closed. Commission rows for that charge are held, and a lost dispute reverses the commission.
Coach search, citations, and feedback
Effective November 20, 2026. It describes the coach search, citations, answer cache, and feedback added in this version.
What we send to xAI. When you ask the coach, we send your question, a short slice of the recent conversation in that request, notes from your profile (display name, platform, edition, character focus, story chapter, progress, play style, help topics, beginner mode, and spoiler setting), any screenshot you attach, and, when the question is about something current, the live search queries xAI runs on the web and on X. xAI uses that material to write the reply. We ask xAI not to keep that response for later retrieval. xAI says it does not train on API inputs or outputs without explicit permission. xAI says that, by default, it stores API requests and responses encrypted for 30 days to audit abuse, and then deletes them. A test call on this project used that default retention, not zero-data retention. We do not sell your chats. If xAI is not configured and an Anthropic key is configured instead, the question, conversation slice, profile notes, and screenshot go to Anthropic, and live search stays off.
Live search and links. For questions about today's changes, patches, events, prices, or other time-sensitive topics, xAI may search the open web and X. On X, official Rockstar accounts are preferred for announcements, and credible GTA community posts otherwise. We prefer public pages from reddit.com (including r/GTA6, r/GTAOnline, and r/GTA), gta.fandom.com, gta.wiki and other GTA wikis, guide sites such as IGN, GameSpot, Polygon, PCGamesN, and Eurogamer, and YouTube titles and descriptions. We do not copy those pages into our database. The reply is written in our own words and can show the title and link of a source the search returned. Free accounts do not get live search.
Our notes and embeddings. We can store short notes we write ourselves and match a question to them. We do not store articles from GTA Wiki, Fandom, or Rockstar or Take-Two pages in that collection. If an OpenAI key is configured, the question text is sent to OpenAI's text-embedding-3-small model so we can search those notes and a short-lived answer cache. We do not send your screenshot or your profile to OpenAI for that step. If the OpenAI key is not set, we skip it and answer without that search.
Answer cache. We may reuse a recent answer for a similar question that does not mention personal details such as your goals, your screenshot, or your name. A reused answer still counts as one of your questions. Answers about current topics are kept for a shorter time.
Feedback. Each answer has a thumbs up and a thumbs down. If you vote, we store your account id, the answer id, the vote, an optional reason (wrong, outdated, spoiler, not helpful, or other), and an optional note of up to 280 characters.
Use my chats to improve answers. This switch is in account settings. It is off unless you turn it on. While it is off, we do not use your chats to propose new knowledge. A signed-in account's chat is stored so that account can open it again. Only that account can read those rows. We still store the usage log (plan, token counts, search counts, cost, and a short excerpt of the question) so the spend limits can work. Turning the switch on saves your choice. It does not, by itself, start a new use of your chats in this version.
Grand Theft Buddy is fan-made. It is not affiliated with, endorsed by, or sponsored by Rockstar Games or Take-Two Interactive.
Changes
If this policy changes, the date at the top of this page changes with it.
Contact support@grandtheftbuddy.com
