Privacy Policy

The controller responsible for data processing on this site ("Goha", "we") is the person named in the Impressum. Contact details for privacy requests are listed there.

Goha has no login. When you first open the site, your browser generates a random identifier (a "clientId") that is stored in your browser's local storage and sent with your requests so we can show and manage your keys. Anyone using that browser can see and manage the keys tied to that identifier; clearing your site data removes it.

We process the following, on the legal basis of Art. 6(1)(b) GDPR (performing the service you request) and Art. 6(1)(f) GDPR (our legitimate interest in security and abuse prevention):

• Your clientId and the keys tied to it (creation time, expiry time, optional label).
• A hardware identifier (HWID) that the script sends the first time a key is used, so the key can be locked to that device.
• Script identifiers and Roblox account IDsreported by compatible loaders, together with their binding and last successful validation times, to apply a key's game and account limits and help resolve access problems. These are client-reported identifiers; they are not verified identities or a count of people currently online. We do not collect Roblox passwords or session cookies.
• IP addresses and request metadata, logged for rate limiting, abuse prevention, and security, and recorded on activity events (e.g. key created, key validated). We do not use this for profiling or advertising.
• An admin session cookie — only ever set for the site operator, not for normal visitors.

We use your browser's local storage for the clientId and your key list, and a strictly-necessary cookie during ad-gate verification. These are required for the service to function. The operator's admin panel uses a session cookie. We do not set advertising or analytics cookies ourselves.

Third-party ad providers set their own cookies. Two separate things are involved: the ad-gate providers you are forwarded to when creating a key (work.ink / Linkvertise / LootLabs), and the on-page ads served by Adsterra. The Adsterra scripts are only loaded once you accept the consent banner; the ad-gate step is governed by the provider you choose at the moment you are forwarded there. Both are covered in the sections below.

Your consent choice itself is stored in your browser's local storage so we do not have to ask on every visit.

Creating or extending a key is monetized through an ad-link step. You choose the provider — work.ink, Linkvertise, or LootLabs— and are forwarded to their page. Once there, that provider's own privacy policy governs what they collect (which typically includes device data and advertising cookies). We only receive a confirmation that you completed their flow; we do not receive your activity on their pages.

• work.ink: work.ink/legal/privacy-policy
• Linkvertise: linkvertise.com/privacy
• LootLabs: loot-labs privacy policy

We display ads on this site through Adsterra, in popunder, social bar, and native banner formats. Their scripts are served from effectivecpmnetwork.com and set cookies and similar identifiers on your device to select, deliver, and measure ads.

If you are in the EEA, the UK, or Switzerland, nothing from Adsterra loads until you accept. On your first visit a banner asks for your choice, and the ad scripts are only added to the page if you agree (Art. 6(1)(a) GDPR, § 25(1) TTDSG). If you decline, no ad script is loaded. Either way the key system remains fully usable — we do not gate keys behind accepting ads.

To know whether we have to ask, we read the country your request arrives from via our own CDN (Cloudflare). This is a same-origin lookup — your IP address is not sent to any third-party geolocation service, and the country is kept only in your browser's session storage. Outside those regions, where opt-in consent is not legally required, the ad scripts load without a banner; you can still switch them off at any time via Cookie settings in the footer.

You can change your choice at any time via Cookie settings in the footer. Withdrawing stops any further ad script from loading. Cookies Adsterra has already set live on their own domain, so we cannot delete them for you — please clear them in your browser settings.

For details, see Adsterra's privacy policy.

Our Discord server asks new members to verify on bot.goha.dev/verifybefore they get access. The check keeps out spam accounts and people who come back with a second account after a ban ("alts"). It only runs after you agree to it by clicking the verify link, which says so right next to the button.

When you verify, we store:

• Your Discord user ID, when you verified, and the result.
• A scrambled (hashed) form of your IP address. We never store the IP itself.
• A hashed device summary, made from details your browser reports (screen size, time zone, language, graphics card and a small drawing test).
• A random browser IDthat the page saves in your browser's local storage (goha_vid). We store only a hash of it.

The hashes are made with a secret key, so they cannot be turned back into your IP or device details. They are still personal data. We compare them with other accounts that verified on our servers. If they match, the server staff are told, and the new account may be kept out or banned depending on the server's settings. Only the server owner can look up which accounts are linked.

The page also uses Cloudflare Turnstile to tell people from bots. Cloudflare processes your IP address and browser data for that check, see the Turnstile privacy addendum.

Legal basis: your consent (Art. 6(1)(a) GDPR, and § 25(1) TDDDG for reading device details and saving the browser ID). Without it you cannot verify. You can withdraw it at any time via the contact in the Impressum. We then delete your data, which also removes your verified status.

How long: we keep this data while you are a member of the server, and while a ban on the account lasts. It is deleted 180 days after you leave. Unused verify links are deleted after a day.

Paid keys are sold through our Discord bot. When you buy one, we store your Discord user ID, the plan, the price, the payment status, Stripe's reference numbers for the payment, and which key it created. The key belongs to your Discord account, which is how the bot shows it only to you.

Payment is handled by Stripe on its own checkout page. Stripe collects your payment details and billing information; we never see your card or bank details. See Stripe's privacy policy.

Legal basis: the purchase contract (Art. 6(1)(b) GDPR) and our legal duties for bookkeeping (Art. 6(1)(c) GDPR). Order records are kept as long as tax and accounting law requires, usually up to 10 years.

The website is served through Cloudflare. Our application and our Discord bot run on a server rented from Contabo in the EU, and our database is Supabase(PostgreSQL). They act as processors on our behalf and may process data on servers located outside the EU. Such transfers are safeguarded by the EU Standard Contractual Clauses / the providers' data-processing terms.

Keys are kept until they expire or you delete them. Expired keys are dropped from active queries. Game and account bindings are deleted with their key or when the operator removes the binding. Permanent keys and their bindings remain until removed. Expired keys are purged according to the operator's retention setting. Activity events are retained for up to about 90 days and then automatically deleted. Server logs are kept only as long as needed for security.

Under the GDPR you have the right to access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20), and to object (Art. 21). You may also lodge a complaint with a supervisory authority. To exercise any of these, contact us via the Impressum. Because keys are not tied to a real identity, we may need the clientId or key in question to locate your data.

This service is not directed at children. If you are under the age of digital consent in your country, please do not use it without the involvement of a parent or guardian.

Deleting a key removes it from our database. Clearing your browser's site data removes your local identifier. For anything further, contact the address in the Impressum.