Skip to content

Privacy Policy

Last updated: November 12, 2026

1. Overview

texturepacks.gg (“we”, “us”, “our”) is a Minecraft resource-pack sharing platform. This Privacy Policy explains what personal data we collect when you use the Service, why we use it, who we share it with, and the rights you have over it.

Who is responsible for your data

texturepacks.gg is run by its two owners and is not a registered company. One owner is based in the United Kingdom and the other in the United States. They decide together how personal data is used and act as joint controllers under the UK GDPR and the EU GDPR. You can use your rights with either of them by contacting privacy@texturepacks.gg.

2. Information We Collect

2.1 Sign-in Provider Data

When you sign in via Discord, GitHub, or Google OAuth, we receive and store the following from the provider you choose:

  • Discord: user ID, username, display name, avatar URL, and email address (if granted in your Discord OAuth scope).
  • GitHub: user ID, username, name, avatar URL, and verified email address.
  • Google: account ID, name, profile picture URL, and email address. Your username is created from your email address.

We never join accounts by email. If a provider's email already belongs to a Packs account, that sign-in is refused, and you can connect the provider from Settings while signed in. We only use a provider's email as your account email when we create a new account with it.

We do not receive or store your Discord, GitHub, or Google password.

If you make a Packs account with an email and password, we store your email address (encrypted) and a one-way hash of your password, never the password itself. When you choose a password, we check it against the Have I Been Pwned list of leaked passwords: only the first five characters of a one-way hash of it leave our server.

If you turn on two-factor authentication, we store its secret encrypted and your backup codes as one-way hashes. If you add a passkey, we store its public key, the name you see in Settings and when it was added and last used. Your fingerprint, face or device PIN never leave your device.

2.2 Your Account and Activity

  • Rewards earnings and payouts: kept while your account exists. Withdrawal records are kept as financial records, so an account with withdrawals is not permanently deleted.
  • Sign-in sessions: the IP address and browser used for each session, so you can review your sessions and we can spot misuse.
  • Activity: packs you like, download, or collect, creators you follow, teams you join, and your settings.
  • Things you post or send us: comments, reports and any files attached to them, support tickets, and your public profile details.
  • Minecraft account: if you link one, your Minecraft username. The link is stored with TierTests (see section 4). Accounts you link in the Packs mod are stored by us (see section 2.6).
  • Launch emails: if you ask to be told about our launch, your email address and Discord name and avatar.
  • Pack Enthusiasts: if you join, your plan, its status and renewal date, the private packs you unlock and how often you download them (to stop shared accounts). If your Discord account is linked, we use your Discord user ID to give you the Pack Enthusiast role in our server. Members of our server who held the OG Enthusiast role are kept on a list of Discord user IDs so their OG packs can be matched to them when they sign in.
  • Pack purchases: if you buy a pack, which pack, the price, when you paid and whether it was refunded, plus Stripe's ids for the payment. We keep this as a payment record, and it is how the pack stays yours.
  • Pack files you download: private and purchased packs are for your own use. A file you download from them may be linked to your account, so that we can look into copies shared without permission.
  • Creator invites: your invite code, which accounts signed up with it, whether their first public pack went live, and the free private pack you took for it. If you sign up through someone's invite link, we keep a cookie with their code for up to 30 days, and once you have an account we record that they invited you.
  • Advertisers: the details and payment status of any ad campaign you create.
  • Rewards program: if you join, the country you live in, your payout method and payout address (stored encrypted), your daily points and earnings, and your withdrawal history. Staff see your full payout address only when they send a payout, and each time is logged.

2.3 Usage Analytics

We collect usage data in order to operate and improve the Service, including:

  • Pack-level metrics: view counts, impression counts, and download counts, associated with individual resource packs.
  • Site activity: the pages you open (the page path only, never what follows a question mark), what you search for and how many results came back, which result, outside link, share button or checkout button you use, and tool runs with how long they took. With each we keep your country, your device type (phone, tablet or desktop), the site language, and the website or campaign link that brought you here. This is tied to your account when you are signed in, and otherwise to a one-way scrambled form of your network address. Your IP address and browser details are not stored with it and no cookie is used for it. Browsers that send a Do Not Track or Global Privacy Control signal are left out.
  • A random visitor identifier in a first-party cookie named tp_vid. We use it only to avoid counting the same view or impression twice. It does not contain your name or email address, but it can still count as personal data.
  • Standard server request logs (IP address, browser user-agent, referrer, timestamp), retained for a limited period for security and abuse-prevention purposes.

2.4 Cookies and Session Data

We use cookies and similar technologies for the following purposes:

  • Session cookie: keeps you signed in across page loads. Cleared when you sign out or the session expires.
  • tp_vid: random visitor identifier used for analytics deduplication, as described above.
  • Preferences: remember your language, your light or dark theme, and how you left the sidebar.

Public pages also show ads from Google AdSense, which uses its own cookies and similar technologies to show, measure and limit ads and to prevent fraud. Visitors in the EEA, the UK and Switzerland are asked for consent before Google uses them for personalized ads. You can turn off personalized ads at any time in Google's Ad Settings (adssettings.google.com).

2.5 User-Uploaded Content

Resource packs and associated metadata (titles, descriptions, screenshots) that you upload are stored on our behalf by Cloudflare R2 / Amazon S3. This content is treated as described in our Terms and Conditions.

2.6 The Packs Mod

Packs has an optional mod for Minecraft: Java Edition. You can browse packs in it without signing in. When you sign in and use it, it sends us the following:

  • Sign-in: your Minecraft UUID and username, plus your Minecraft version, mod loader and operating system. To prove you own the account, the mod asks Mojang to confirm the sign-in and our server checks the answer with Mojang. Your Minecraft password and access token never reach us.
  • Linked accounts: the UUID and username of each Minecraft account you link to your Packs account, and when it was linked and last confirmed.
  • Mod sessions: each signed-in copy of the mod has a session like a browser does, with its IP address and approximate location, the mod and Minecraft version, and a random ID for that copy of the mod. You can see and end these sessions in Settings.
  • Presence while you play: while you are in a world, the mod tells us every 90 seconds that you are playing, so players using the mod can see a Packs icon by your name, along with your membership tier and profile color. If you share the pack you are using, it also sends which Packs pack that is. Anyone who knows your Minecraft UUID can see this until it expires, 3 minutes after the last update. Your Packs username is not part of it.
  • Players around you: to show those icons, the mod sends us the Minecraft UUIDs of players near you and gets back which of them use Packs. We use them only to answer and do not store them.
  • Downloads: packs you get in the mod count toward the same daily limits as the site and show in your download history, recorded as downloaded through the mod.

The mod never sends us the address of the server you play on, your chat or your list of mods. Showing your icon and sharing your pack are on by default. You can turn either off in the mod or in Settings; hiding your icon removes your presence at once. Unlinking an account in Settings signs the mod out on it.

3. How We Use Your Data

We use your data for the purposes below. If you are in the UK or the EEA, each purpose relies on the legal basis shown.

  • To provide the Service you asked for (contract): creating and signing in to your account, showing your username and avatar on your public profile and uploaded packs, keeping your library, likes, and collections, and handling your uploads and support requests.
  • Our legitimate interests: keeping the Service secure, preventing fraud, spam, and abuse, moderating content, counting views and downloads for pack authors and site metrics, and improving the Service. These interests do not override your rights, and you can object to them.
  • Your consent: sending launch emails you asked for. You can withdraw consent at any time.
  • Legal obligations: responding to DMCA notices and other requests the law requires us to handle.

We do not sell your personal data to third parties. Ads are served by Google AdSense as described in section 4; we do not share your account details with Google for advertising.

4. Third-Party Services

The Service integrates with or relies on the following third-party services that may process data:

  • Discord: used for OAuth sign-in. Your interaction with the Discord OAuth flow is subject to Discord's Privacy Policy.
  • GitHub: used for OAuth sign-in. Your interaction with the GitHub OAuth flow is subject to GitHub's Privacy Statement.
  • Google: used for OAuth sign-in. Your interaction with the Google OAuth flow is subject to Google's Privacy Policy.
  • Cloudflare: provides CDN, DDoS protection, and object storage (R2) for uploaded assets, and Turnstile, the security check on our sign-in, sign-up and password reset forms, which looks at your IP address and browser to tell people from bots. Cloudflare may process request data in accordance with their privacy practices.
  • PayPal, Venmo and gift card providers: when we pay a rewards withdrawal, the service you chose receives your payout address and the amount.
  • Stripe: handles Pack Enthusiasts payments and pack purchases. Stripe receives the card, name, email and billing address you enter at checkout, plus your account number on Packs so the payment reaches the right account. We keep only Stripe's customer and subscription ids, your plan and its status; we never see your full card number. Stripe keeps payment records as financial law requires.
  • Resend: sends our emails, such as sign-up links, password resets, security alerts, launch emails and your data exports, so it receives your email address and the message.
  • Have I Been Pwned: checks new passwords against leaked ones. It only receives the first five characters of a one-way hash of the password, so it never learns the password.
  • TierTests: stores the link between your Discord account and your Minecraft account, if you create one.
  • Mojang: Packs downloads Minecraft skins from Mojang on its own server to show players' faces, so your browser never contacts Mojang or a skin service for them. When you sign in to the Packs mod, our server sends Mojang your Minecraft username and a one-time code to confirm the sign-in.
  • Google AdSense: shows the ads on public pages. Google receives your IP address, browser details and the page you are on, and may set cookies, as described in How Google uses information from sites that use its services.
  • YouTube: some pages show thumbnails loaded from YouTube and link to videos there. YouTube may collect data as described in Google's Privacy Policy.

International transfers

Our servers are in the United States, and our owners and some of the services above are based outside the UK and the EEA, so your data may be transferred there. Where the law requires a safeguard for these transfers, we rely on the provider's data protection terms, such as standard contractual clauses.

5. Data Retention

  • Account data and uploads: kept while your account is active. If you delete your account, it and your packs are removed from public view right away and permanently deleted after 30 days.
  • Detailed view, impression, and download events: deleted after 90 days.
  • Site activity records: deleted after 400 days.
  • Sign-in sessions: deleted 7 days after they expire.
  • Linked Minecraft accounts: kept until you unlink them or delete your account.
  • Presence in the Packs mod: deleted 3 minutes after the last update, or at once when you hide your icon.
  • Staff moderation logs: deleted after 400 days.
  • Server request logs: kept for a limited period for security purposes, then deleted.
  • Totals: view and download counts that no longer identify anyone may be kept indefinitely.

6. Your Rights and Data Deletion

If you are in the UK or the EEA, the UK GDPR and the EU GDPR give you the right to:

  • Access your personal data and get a copy of it.
  • Correct data that is wrong or incomplete.
  • Have your data deleted.
  • Restrict how we use your data.
  • Object to uses based on our legitimate interests.
  • Receive your data in a portable format.
  • Withdraw consent at any time, where we rely on it.
  • Complain to a data protection authority, such as the ICO in the UK or the authority where you live.

Depending on where you live, you may have similar rights under other laws. You can export your account data or delete your account yourself in your account settings. For anything else, contact us at:

texturepacks.gg · Privacy Contact
Email: privacy@texturepacks.gg

We respond to requests within one month. Some data may be kept where the law requires it or where we need it to establish or defend legal claims (for example, records needed to process outstanding DMCA claims).

7. Children's Privacy

The Service is not directed to children under 13. We do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided us with personal data, please contact us at privacy@texturepacks.gg and we will delete it.

8. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will update the “Last updated” date at the top of this page. Material changes will be communicated via the Service.

9. Contact

Questions about this Privacy Policy can be directed to privacy@texturepacks.gg.

You may also review our Terms and Conditions.