Privacy Policy
Last updated: October 5, 2026
This policy explains what RPGme ("RPGme", "we", "us") collects when you buy and build a personalized game, why we need it, who helps us process it, and what you can ask us to do with it.
1. Who we are
RPGme makes personalized, giftable retro games.
[Owner to confirm: legal business name and postal address]
Questions about privacy: support@rpgme.ai
2. What we collect and why
Your email address. When you buy a game or sign in, your email is stored with our account provider (Supabase Auth). We use it to send sign-in links, your receipt, and the email that tells you your game is ready.
Payment details. Payments are handled by Stripe on Stripe's own checkout page. We never see or store your card number. Stripe tells us the email used, the amount, and whether the payment succeeded, refunded or was disputed.
Your questionnaire answers. To write the story we ask about the people in the game: names, pronouns, interests, memories and inside jokes. These answers are stored with your game and sent to the AI services listed below to write and check the story.
Photos. Photos you upload or take of the people in the game are stored in a private storage area that is not publicly accessible. Before a photo is used, an automated check (Google Gemini) confirms it is suitable for an avatar. Our art service then turns it into pixel-art portraits and in-game characters. Please only upload photos you have the right to use.
Instagram handle (optional). If you give us a public Instagram handle, we fetch that account's public profile and its most recent public posts through a third-party data provider (FlashAPI, via RapidAPI). We use Google Gemini to suggest draft answers that you can edit or ignore, and we look through the photos for pictures of the same person. Copies of the images we use are kept in our private storage. We never post to, follow or message the account. For private accounts we only read the public profile.
Your finished game. The story, characters and pixel art we create are stored in our cloud storage (Supabase Storage) at an address that is hard to guess. Anyone who has the link to your game can open and play it, so share it only with people you want to.
Bug reports. If you report a problem from inside the game, we store your note, a screenshot of the game and technical details about what the game was doing. Bug reports are visible only to the RPGme team, who use them to fix the game.
Mailing list (optional). If you enter your email in our sign-up popup, we store it and add it to our mailing list with Klaviyo. Every email has an unsubscribe link.
Analytics, advertising and technical data. Our website can load Google Tag Manager, which loads Google Analytics (to count visits and see how people use the site), the Meta (Facebook) Pixel (to measure our ads) and Hotjar (to see how pages are used, such as clicks and scrolling; Hotjar can also record what a visit looked like on screen). These tools set cookies and receive details about your device and the pages you view. If you visit from the UK, the European Economic Area, Switzerland, Brazil or Quebec, or we cannot tell where you are, none of them load unless you accept them in our cookie banner. Elsewhere they load by default, and you can turn them off below. If your browser sends Global Privacy Control, they never load. When product analytics (PostHog) is switched on, it follows the same choice and records which steps of the game builder were used, never the text of your answers or your photos. Our hosting providers keep standard request logs (such as IP address, browser type and the page requested) for security and troubleshooting.
3. Who processes your data for us
We do not sell your personal information. We share it only with the service providers that run RPGme for us, each for the purpose described above:
- Stripe: payments.
- Supabase: accounts, database and file storage.
- Vercel: hosting for this website and the game player.
- Railway: hosting for our game generator, art service and 3D gift box service.
- Google (Gemini): photo checks, writing the story, wizard replies and Instagram draft answers. Google Tag Manager and Google Analytics: visit statistics.
- Meta (Facebook Pixel): measuring our advertising.
- Hotjar: understanding how our pages are used.
- Anthropic (Claude): helping us investigate bug reports you send from inside the game.
- TypeSafe: checking AI-written wizard replies before they are shown.
- FlashAPI (via RapidAPI): public Instagram profile lookups, only if you give a handle.
- Resend: sending our emails.
- Klaviyo: our mailing list, only if you join it.
- PostHog: product analytics, only when it is switched on.
These providers process data under their own terms and security practices. We may also disclose information if the law requires it.
4. Cookies and local storage
We use cookies to keep you signed in. Your browser also stores your progress in the game builder and saves inside the game itself, so you can pick up where you left off. A cookie called rpgme_consent remembers your analytics choice for a year. When they are allowed, Google Analytics, the Meta Pixel and Hotjar set their own cookies. You can block or delete cookies in your browser settings.
5. How long we keep it
We do not yet delete data automatically on a schedule. We keep your account, answers, photos and game for as long as your account exists, so that your game keeps working. When you ask us to delete them, we delete them. Stripe keeps payment records for as long as financial law requires.
6. Your choices
You can ask us for a copy of your data, ask us to correct it, or ask us to delete your account, photos and games by emailing support@rpgme.ai from the email address you used with us. Depending on where you live, you may have further rights under local law; contact us and we will help.
Analytics and advertising. You can switch Google Analytics, the Meta Pixel, Hotjar and PostHog off (or back on) for this browser here:
Checking your analytics setting...
7. Children
RPGme is not directed to children under 13, and we do not knowingly collect personal information from them.
8. Changes
If we change this policy, we will update this page and the date at the top. See also our Terms and Conditions and Refund Policy.