Back to home

PrimeBlocks

Privacy policy

Find out what data we process when you use PrimeBlocks, why we need it and what rights you have.

Updated:

Who is responsible for your data

The controller responsible for the processing described in this notice is Prime Codes GmbH, Pappelallee 78/79, 10437 Berlin, Germany. For privacy questions or to exercise your rights, contact us at [email protected].

What this notice covers

This privacy notice explains what personal data we process when you visit our website and use the wiki, shop, contact options and application forms. The data involved depends on which features you use.

When you pay through Tebex, load YouTube or Twitch content or visit linked services, the relevant provider’s privacy notice also applies. Using our website does not automatically sign you in to those services. The game server and app also process data from their own use; information about Fishing Anti-Cheat for the fishing system appears below.

Hosting, page visits and security logs

Prime Codes GmbH operates the website and team dashboard. The data we host for these services is stored in Germany. This does not automatically apply to separate processing by external providers such as Tebex, YouTube or Twitch.

When you visit our website, we process technical connection data, including your IP address, the requested address, the time of access and browser information. We need this data to deliver pages, investigate errors and detect attacks or misuse.

Access and security logs are normally retained for 30 to 90 days for operational and security monitoring purposes. The legal basis is Article 6(1)(f) GDPR: our legitimate interest in a secure, functioning website.

Cookies and settings on your device

We use cookies and browser storage to save your language choice, privacy preferences and the local features you use. We do not use our own analytics or advertising trackers on this website. On your first visit, YouTube and Twitch are off; optional content loads only after you explicitly allow it. “Accept all” allows both services. “Customize” opens the separate choices for YouTube and Twitch. Opening these settings alone does not change your permissions.

You can change your YouTube and Twitch preferences separately at any time through “Cookie settings”. Choose your options and confirm with “Save choices”. “Turn off optional content” disables both optional services immediately. Essential features remain available. Withdrawing consent prevents further requests for the content you have blocked, but does not delete data already sent to external providers or existing browser data.

Storage or access that is strictly necessary for a service you expressly request is based on Section 25(2), no. 2 of the German TDDDG. Where personal data is processed to provide the feature, we rely on Article 6(1)(f) GDPR. We load optional media with your consent under Article 6(1)(a) GDPR and, where required, Section 25(1) TDDDG.

Language

The primeplots-locale cookie stores your explicitly chosen language for up to 365 days. The language menu offers German and English. Without a saved choice, we first consider your browser language, then available country information derived from your IP address by our web server. French and Spanish can therefore be displayed automatically. If neither provides a match, we use English. No additional language cookie is set automatically. You can delete or block the cookie in your browser.

Privacy preferences

primeplots-media-consent-v1 stores your decisions to allow or reject YouTube and Twitch separately in local browser storage. The entry contains a version number and a permission for each service, with no user identifier. Earlier consent for YouTube does not allow Twitch content. The entry has no fixed expiry date and remains until you change your choice or clear your browser data. Your saved choices also apply on later visits. If storage is blocked, your choice applies only to the open page.

Scroll position when changing language

primeplots-language-scroll briefly stores the target language and your scroll position in session storage. The entry is removed when read; at the latest, it is removed when that browser session ends.

Entrance animation

Briefly animates the homepage introduction. With your permission, we store a 20-minute pause in this browser. Without permission or with reduced motion, the page stays static. “Accept all” also enables the optional entrance animation with a locally stored 20-minute pause. You can turn it off separately under “Customize”. primeblocks-entrance-consent-v1 stores your separate choice without a fixed expiry until you change it or clear browser data. Existing media permissions do not automatically enable this feature. Only after permission do we read and write primeblocks-entrance-until-v1: solely the time when the animation may appear again, without a user identifier or transmission to a provider. The pause lasts 20 minutes from the last animation, applies across languages on this website, and is not extended by further visits. Expired entries are replaced on the next eligible visit; the browser does not delete them automatically. Turning the feature off in cookie settings removes the timestamp. Blocked storage disables animation. This optional storage requires consent under section 25(1) TDDDG.

Welcome gift

The technically necessary HttpOnly cookie primeblocks-welcome-gift is set only when you claim the 350-gem gift. It contains only a random reservation identifier, is sent only with gift requests to our website and expires after 7 days and 15 minutes. You can delete it in your browser; the website will then no longer show your reservation after a reload.

Order status

The technically necessary HttpOnly cookie primeblocks-checkout is set when you continue to payment in the shop. It contains a random order reference, the recipient's Minecraft name and the time, is sent only with shop requests to our website and expires after 6 hours.

Your PrimeBlocks account (sign-in)

Signing in or registering on this website runs through primeplatform, the central PrimeBlocks account service for players. An account is created with a registration code you get in-game via /register, and is permanently linked to your Minecraft account. We store your Minecraft name and Minecraft UUID, your password (only as a hash, never in plain text), your optional email address and its verification status, your rank, and, if you enable it, a two-factor authentication secret plus one-time-use recovery codes.

Signing in sets the technically necessary primeplots-platform-session cookie (HttpOnly, valid for 30 days). It only contains a session token and exists solely to recognize that you're signed in; it is not used for advertising or analytics.

For the protected administration area, we verify your session and account access permissions on the server through PrimePlatform. We use your account ID, Minecraft UUID and administrator permission for this purpose. When administration changes are made, we record the responsible account ID in the change history. No additional cookie is set for this.

You can optionally add passkeys and use them to sign in. PrimePlatform stores the passkey identifier and public key, its association with your account, your chosen name, creation and last-use times, and a technical signature counter. Private keys and biometric data are not transmitted to us; the private key stays on your device or in the passkey storage you use. For sign-in or setup, we set the necessary HttpOnly cookie primeblocks-passkey-request containing a random request identifier, valid for at most five minutes. It is removed when the request is completed; the single-use server request also expires after five minutes. Passkey records remain until you remove the passkey or delete your account. Removing a passkey here does not delete its copy on your device or with your passkey provider.

With two-factor authentication enabled, you can generate new backup codes after confirming with your password or a passkey, plus a valid authenticator code or an unused backup code. The new set replaces all previous backup codes; we store only hashes and usage status. Newly generated codes are shown once. You can download them as a PDF with the PrimeBlocks logo. The PDF is created on your device using locally hosted fonts; no codes are sent to a PDF service for this. The downloaded file remains with you until you delete it. You can also end all account sessions, including your current session, at once. OAuth app connections are managed separately. Profile images in OAuth responses use the PrimeBlocks head-image API at app-api.primeblocks.net with your Minecraft name.

Under Account → Sessions you can see every active sign-in with its device, approximate location and time, and end any of them individually. For the approximate location (city/country) we look up your IP address with the external service ip-api.com; private or local IP addresses are not looked up. If you keep it enabled in your notification settings, we also email you about new sign-ins.

So that this overview shows your actual device and approximate location, the website passes your IP address and browser identifier (user agent) to PrimePlatform when you sign in, register or use other account functions. This transfer is protected by a key known only to the website and PrimePlatform. For each session we store the IP address, browser identifier, approximate location (city/country), creation time and last activity. We use the same details for emails about new sign-ins. Session data is deleted automatically when the session expires, at the latest 30 days after sign-in; sessions you end early also remain stored until then. The ip-api.com lookup uses your IP address and returns only city and country.

We also email you when your password or email address is changed, two-factor authentication is turned on or off, new backup codes are generated, or a passkey is added or removed. When your email address changes, the notice goes to your previous confirmed address. These notices are sent only to confirmed addresses and contain the type of change and the time. You can turn off each type of notification under Account → Profile → Email notifications; we store this setting with your account until you change it or delete your account. Confirmation and password-reset emails are sent regardless.

Other PrimeBlocks products can ask you, through "Sign in with PrimeBlocks", for permission to access basic details such as username, rank and avatar, and optionally your email address. You can see every app connected this way under Account → Connected apps and revoke access there at any time.

You can change your password at any time and permanently delete your account under Account → Delete account after confirming with your password or a passkey. This deletion affects your PrimeBlocks account; it does not delete data the game server itself processes independently.

You can confirm changes to your email address or password, account deletion, disabling two-factor authentication and backup-code regeneration with a registered passkey instead of your current password. A fresh device verification is required. The single-use confirmation is bound to your account, current session and chosen action and expires after two minutes. The underlying request expires after five minutes. The confirmation remains temporarily in browser memory and on the server; it is not stored in localStorage. Backup-code regeneration still requires a valid authenticator code or unused backup code. The app authorization screen shows your Minecraft profile, the requesting application, its destination and the permissions to be shared. Profile heads use app-api.primeblocks.net through the website’s image service; a registered application logo may load from its configured host. This host receives the image request, but we do not send the authorization page URL as a referrer. Permissions are granted only after you choose Allow.

Under Account → Support you can see your Discord support tickets. PrimePlatform retrieves them from our moderation service using your Minecraft name; the website does not store them. When you open a transcript, your browser loads profile pictures, embedded images and attachments directly from the servers hosting them, such as the Discord CDN (cdn.discordapp.com) or our file storage. These providers receive your IP address and standard browser information.

Wiki contributions and local editing

Wiki editing is currently unavailable. The login entry does not collect credentials.

Previously saved local wiki content may still be displayed in this browser. The content library is stored under primeplots-wiki-library-v1; reading it does not send it to our team. It remains until local data is reset or browser data is cleared. Previously saved role selections are no longer read and grant no access rights.

Images in wiki guides may show example player names, avatars and views from the game or app.

The illustrated lobby guides in the wiki also include example game views with visible player names and avatars.

A profile example in the wiki also shows a Discord name, clan, playtime, join date and in-game balance as part of a supplied screenshot.

The shop guides also show static examples containing player names, ranks, chat messages, last-online times and item signatures.

Search, images and other website features

Searches in the wiki and server rules process your search terms in your browser. We do not send them to a search provider. For wiki searches, the search terms and selected result may appear in the part of the address after #. This part is not sent with the HTTP request, but may appear in your browser history and shared links. Clearing the current search does not delete earlier history entries or copies of a link.

Fonts and our own images are served through our website. When you copy the server address or click a creator’s profile image to copy their creator code, the website writes the displayed address or code to your clipboard only after your click. It does not read existing clipboard content to do this. The copy feature does not add cookies or entries to browser local or session storage. These features support the way you choose to use the website.

Our own wiki videos and their preview images are served directly by this website. Video files load when you play them; preview images may load when you open the page. This creates the usual requests to our web server. No external video service is involved, and no additional cookies or browser-storage entries are created.

While the website is open, it periodically checks with our own server which website features are currently available. These requests do not send account data to external services or store an additional identifier, cookies or entries in local or session storage. They generate the technical connection data described above. Turning off a feature does not mean that previously processed data is deleted; your privacy rights remain unaffected.

YouTube videos

Wiki articles may contain YouTube videos. Without your permission, neither external YouTube thumbnails nor the player will load. You can allow an individual video or allow YouTube through the cookie settings. If you have saved your consent, thumbnails load automatically; the player starts only when clicked.

Standard thumbnails are loaded from i.ytimg.com and players from youtube-nocookie.com. YouTube/Google receives data including your IP address, browser information and the video ID; the player may also receive the referring website. YouTube may store or read further information on your device. Privacy-enhanced mode does not mean that no data is sent to Google.

According to Google’s privacy notice, Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland, is generally responsible for users habitually resident in the European Economic Area or Switzerland. Data may also be processed outside the EU. Details of the relevant Google companies, transfer mechanisms, retention periods and your rights are available in Google’s privacy notice.

Permission for an individual video applies to its current display. Saved YouTube consent remains until you change your cookie settings or clear your browser data. When you withdraw consent, active players are removed and further automatic requests are blocked. The legal basis is your consent under Article 6(1)(a) GDPR and, where required, Section 25(1) TDDDG.

Google and YouTube

Google privacy notice

Contact, support and reports

When you contact us by email or through our Discord support, we process your contact details, the content of your message and any account, order or error information you provide so we can handle your request. Send only necessary information, without passwords or full payment details. This also applies to security reports and the bug bounty program.

The anonymous report form sends your entry — the player name you give, your text and any files you select — through our website server to our separate moderation system; we do not pass your IP address on to the moderation system, without needing a PrimeBlocks account or sign-in. We deliberately don't ask for your name, email address or any contact details there; please also avoid personal details in your text and attachments if you want to stay anonymous, since files can keep their original metadata (for example where or when they were taken). Submitted reports are visible only to team members with super-administrator rights; uploaded files get their own address that isn't publicly listed. There is currently no fixed automatic deletion period for reports; hosting and connection logs outside this form follow the "Hosting, page visits and security logs" section.

For contract-related inquiries, the legal basis is Article 6(1)(b) GDPR. We handle other inquiries under Article 6(1)(f) GDPR; our interest is in being accessible, resolving problems and preventing misuse. Where we have a legal obligation, Article 6(1)(c) GDPR applies.

We retain correspondence for as long as it is needed to handle the matter and maintain necessary records. It is then deleted unless statutory retention duties require otherwise. When you open Discord, you leave our website. Discord processes data under its own privacy notice; a Discord player or chat is not loaded automatically on our website.

Applying to join our team

Supporter applications require you to sign in with your PrimeBlocks account. We verify the account on the server and associate the application with its account ID, Minecraft UUID and Minecraft name. You can apply as a Developer without an account. Applications are sent through our website server to the PrimeModeration service. The website only displays your own status and messages addressed to you; internal team notes and moderation information are not included.

If you are signed in, we prefill the application email field with your account email address. You can change it before submitting. Prefilling alone does not submit the application.

To submit and retrieve a team application, we store a random access key in the necessary cookie primeblocks-team-application for up to 90 days. It is not readable by website JavaScript. The service stores only a hash of that key. For a Developer application without an account, the key allows this browser to retrieve its status. Clearing the cookie removes this browser’s access but does not delete the application. The cookie’s lifetime does not extend the application retention periods described below.

When you apply as a Supporter or Developer, we use your information to assess your suitability, communicate with you and handle your application. This includes your chosen role, Minecraft name, age, email address, Discord contact, answers and application letter. For Supporters, it also includes CityBuild, Java or Bedrock edition, support experience, strengths, weaknesses and motivation. For Developers, it includes selected technologies with self-assessments, project descriptions, your greatest weakness and an optional GitHub profile link.

While you fill in the form, your entries stay in the memory of the open form. Entering information alone does not submit an application. The form identifies optional and required information. Without the required information, we cannot fully assess your application. Share only public project information or information you have permission to disclose. A GitHub link is treated as part of your application; entering it does not cause the form to load profiles or repositories automatically.

Supporters apply for a volunteer role. Applications are assessed under Article 6(1)(f) GDPR; our legitimate interest is in selecting suitable people to support and look after our community. Developer applications are for paid employment. Processing necessary to decide whether to enter into an employment relationship is based on Section 26(1), first sentence, of the German Federal Data Protection Act (BDSG). Acknowledging this privacy notice confirms that you have read it; it is not blanket consent to other processing.

Applications we receive are handled exclusively by the responsible team lead through our team dashboard, operated by Prime Codes GmbH in Germany. Within our team, only that team lead has access. The status of a received application and questions addressed to you keep you informed about its progress.

Accepted applications are stored for documentation for 90 days from the date of acceptance, then deleted. Rejected applications are automatically and irreversibly deleted no later than 14 days after rejection. These periods apply to the application documents. The 14-day waiting period before applying again does not extend the deletion deadline.

The Supporter age guideline of 16 is an application criterion. It does not replace any required permission from a parent or legal guardian and does not establish a general age threshold for data protection consent.

Creator and JrCreator applications

A partner application contains your chosen role, Minecraft name, email address, Discord contact, the social media profiles you provide, your application letter and the form acknowledgements. For a JrCreator application, this also includes your confirmation that you meet the minimum requirements. An optional Tebex Wallet ID is used to match your wallet for a Creator Code. Do not provide wallet login details, passwords or confidential information about other people.

While you complete the form, your entries remain in the memory of the open page. Typing alone does not submit an application or load external profiles. We use submitted information to assess the proposed partnership, contact you and keep you informed about the application status and any follow-up questions.

We assess and manage partner applications under Article 6(1)(f) GDPR; our interest is selecting and supporting suitable creators for our community. Where steps towards a contractual partnership are taken at your request, Article 6(1)(b) GDPR applies. The privacy acknowledgement confirms that you have read the notice; it is not blanket consent.

Submitted partner applications are handled exclusively by the responsible team lead through the team dashboard hosted by Prime Codes GmbH in Germany. Within our team, only that team lead may view them.

Accepted partner applications are retained for documentation for 90 days from the date of acceptance and then deleted. Rejected partner applications are automatically and irreversibly deleted no later than 14 days after rejection. These periods apply to the application documents. The 14-day waiting period before reapplying does not extend the deletion deadline.

When you submit, our website forwards your Minecraft name, Discord contact, email address, optional Tebex Wallet ID, Twitch/YouTube links, application text and acceptance of the server rules to our PrimeAnalytics application service. The privacy acknowledgement and JrCreator confirmation are checked before forwarding; they are not saved as separate fields by that service. Status updates and follow-up communication use your email address.

After submission, the technically necessary primeblocks-partner-status cookie stores a private status token for up to 90 days. It is HttpOnly, uses SameSite=Strict and is Secure on HTTPS in production. It lets this browser retrieve your application status without signing in and is not used for advertising or analytics. Deleting the cookie removes this browser’s saved access, not your application. You can also open the status link from your email. The status page shows the role, decision, timestamps and the team’s message; anyone with that link can view these status details. While visible, the page checks the status every 30 seconds.

Shop, regional prices and payments

When you select products, we process the products, quantities and variants you choose, the Minecraft recipient name you enter and any optional discount or credit codes. The basket stays in memory during the shop session. The shop does not set an additional cookie or create a persistent browser storage entry for this. Reloading or leaving the shop may discard your selection.

For regional prices, our server sends your IP address to Tebex. The country may also be used for the initial language; your manual language choice takes priority and does not change the pricing region. Product images are served through our website and its image optimization. Simply viewing products does not create a Tebex basket.

When you request checkout preparation, our server sends the Minecraft recipient name, product identifiers and quantities, any codes entered and your IP address to Tebex. Tebex checks prices, the basket and codes. A basket may be created before any payment; Tebex may also retain abandoned transactions. Closing our page does not delete this data.

To protect against abusive requests, we use temporary request counters and an identifier derived cryptographically from the IP address. These entries are valid for ten minutes. Similar checkout requests associated with the same buyer, as verified by the server, may be combined for up to two minutes. These are validity limits; technical cleanup occurs on later requests or when the server process ends.

Payment takes place through the checkout provided by Tebex Limited, which processes personal data there under its own privacy notice. This may include contact, billing, order, payment and fraud prevention data. Our website does not receive payment card details through this checkout integration. Details of recipients, international transfers, retention periods and rights are available in Tebex’s privacy notice.

Processing needed for the purchase you request is based on Article 6(1)(b) GDPR. Abuse prevention and secure shop operation are based on Article 6(1)(f) GDPR. Our interest is in preventing unauthorized or duplicate requests and providing a reliable purchase process.

“Cancel subscription” takes you to Tebex’s payment and subscription management. The Tebex page is loaded only when you open this external link. Sign-in and cancellation take place there; our website does not ask for your Tebex credentials.

When your account is connected, we can display the confirmed status and end of the current term of your Gem Pass subscription. This information is used to show the appropriate subscription controls and is refreshed regularly while the store is open.

Gifts and basket links

For a gift, we use the Minecraft name you provide to assign the selected products to the intended recipient. Your own purchases and gifts are kept separate during the shop session. Share only the information needed for the gift.

When you open a basket link, its identifier may be sent to our server for validation. The identifier may appear in your browser history, copied links or technical request logs. Removing it from the current address does not delete these copies. A basket link does not sign you in to another person’s website account.

Team directory and Minecraft images

Our team directory displays Minecraft names, team roles and the corresponding Minecraft heads. Our server loads this information from the team interface and caches the team directory and displayed player count for up to 60 seconds. Technical identifiers and absence information from the team interface are not displayed on the page.

When you enter a Minecraft name in a valid format in the shop, the corresponding head image may be requested after a short pause in typing. Images are served through our website. The name entered is sent to the image service for this purpose and may appear in image addresses, caches and technical logs. A head image does not confirm your identity or ownership of an account.

Our server makes requests to the team, player count and image interfaces. Your browser does not contact these interfaces directly, and we do not forward visitors’ cookies or IP addresses to them for these requests. This processing is used to display the team and clearly identify recipients in the shop, based on Article 6(1)(f) GDPR.

The wiki also displays current team members by rank from the same team service. The list refreshes regularly while the page is open; it is not saved as a manually maintained list of names in the wiki.

Creator directory and linked profiles

Our partner directory displays published creator names, optional Minecraft names and matching Minecraft heads, their Creator or JrCreator role, public creator codes and provided social media links. We use this information to introduce our partners and help you find their content. The legal basis is Article 6(1)(f) GDPR; our legitimate interest is presenting and supporting our creator community. The Minecraft images use the image delivery process described in the team directory section.

Our server retrieves publicly released profiles from analytics.primeblocks.net without forwarding your IP address or browser cookies. Profiles may include cached public channel figures such as subscriber, follower and view counts. PrimeAnalytics retrieves these figures through Metrika (metrika.run), submitting platform identifiers and channel names. The website reads the stored figures and does not contact Metrika from your browser. Earlier figures may remain visible while an update is pending. Displaying profiles and figures creates no additional browser cookies.

Our server checks the listed Twitch channels for active streams through the status service analytics.primeblocks.net and provides public stream details for the live display. The channel details are sent to that service; your IP address and browser cookies are not forwarded. Displaying live status does not itself load a Twitch player or chat in your browser.

The social media links are ordinary external links. Displaying them does not load embedded TikTok, Instagram or YouTube profiles. Opening a link takes you to the relevant service, whose privacy notice then applies. The following section covers embedded Twitch streams.

Twitch streams and chat

When a creator is live, you can watch the stream on our website. Without your Twitch permission, we load neither the Twitch player and chat nor external Twitch thumbnails. You can allow Twitch at the stream, through its individual option in Cookie settings, or together with YouTube by choosing “Accept all”.

With Twitch permission saved, the player and visible chat load automatically for displayed livestreams on later visits too, without another permission request at the stream. Automatic video playback remains off. If the available space is too narrow for the player, we show a link to Twitch instead.

After you allow Twitch, its player and chat can load. Twitch receives information including your IP address, browser details, the channel requested and the embedding website. Twitch may use cookies or other storage technologies and process usage data. If you are signed in to Twitch or interact there, Twitch may associate this use with your account.

The provider is Twitch Interactive, Inc. Data may also be processed in the United States and other countries. The legal basis for loading this optional content is your consent under Article 6(1)(a) GDPR and, where required, Section 25(1) TDDDG. Twitch’s privacy notice explains its processing, recipients, transfers, retention and your rights.

Your Twitch choice remains saved in your browser until you change it or clear your browser data. You can withdraw it at any time in Cookie settings. Active Twitch embeds are then removed and further automatic requests are blocked. This does not delete data already sent to Twitch or cookies it has stored.

Fishing Anti-Cheat in the game

When you use the fishing system on our game server, Fishing Anti-Cheat (FAC) checks internally collected and verified game data for repeated behavior patterns, plausibility and technical context. This helps detect automated interference and protect fair play and the server economy.

The system can issue automated bans and automatically correct incorrect assessments. Regular game support does not manually lift FAC bans. Your statutory rights to access, complain and, where applicable, request a review remain unaffected. You can send questions about this processing or the review of a decision affecting you to [email protected].

Recipients and processing outside Germany

Only people responsible for the relevant purpose are given access to personal data. Applications are subject to the stricter restriction that only the responsible team lead has access. Data may also be shared with technical service providers we use, the providers named in this notice or public authorities where necessary for the relevant purpose or required by law.

Our website and team dashboard operate with data stored in Germany. External services such as Tebex, YouTube, Twitch and Discord may also process data in other countries. The relevant sections describe the providers involved and the data they receive.

Where we transfer personal data to countries outside the European Economic Area, the requirements of Articles 44 onward of the GDPR must be met. Depending on the recipient, an applicable adequacy decision or appropriate safeguards such as standard contractual clauses may be used. To request information about the safeguards applicable to a specific transfer and a copy of them, contact [email protected].

Data retention and protection

We retain personal data only for as long as needed for the relevant purpose or required by statutory retention duties. Specific periods for logs, browser storage and applications are given in the relevant sections. Data processed independently by Tebex, Google, Twitch or Discord is also subject to their own retention and deletion rules.

Statutory retention duties for business and tax records apply to the specific documents required, not to all usage data as a whole. The relevant data is deleted when the applicable periods expire. We protect personal data through access rights limited to the relevant purpose and technical safeguards. Do not send us login credentials or unnecessary confidential information.

Your data protection rights

Subject to the legal requirements, you can request access to your personal data, correction of inaccurate information, erasure, restriction of processing and data portability. Where we process data based on legitimate interests, you may object on grounds relating to your particular situation. You may object to direct marketing at any time.

You may withdraw consent at any time with effect for the future. This does not affect the lawfulness of processing before withdrawal. You can change your preferences for optional YouTube and Twitch content directly through “Cookie settings”.

For privacy requests, write to [email protected]. If needed, we will ask for appropriate information to verify your identity. Under the GDPR, we generally respond within one month; if a legally permitted extension is needed, we will explain it within that period.

You may lodge a complaint with the Berlin Commissioner for Data Protection and Freedom of Information or another competent supervisory authority. You do not have to contact us first. You may have additional statutory rights depending on where you live and the specific processing; the website language you select does not limit your rights.

Children and young people

Our community includes younger players. Provide only the data needed for the feature you want to use. If you are unsure about an application, purchase or permission to load external content, involve a parent or legal guardian.

Where a parent’s or legal guardian’s permission is legally required for specific processing, it must be obtained. Entering an age in a form or agreeing to the server rules does not replace this permission. Consent under data protection law and the ability to enter into a purchase are separate matters.

If you are a parent or legal guardian with questions about the processing of your child’s data or suspect unlawful processing, contact us at [email protected].

Changes to this privacy notice

We update this privacy notice when our services or the processing of personal data change. The date above shows when this version was issued. If a change requires new consent, we will obtain it before starting the relevant processing.

Updates and roadmap

Our server retrieves the public roadmap board through the PrimeBlocks team API for the Updates page. We display published tasks, descriptions, labels and their development stage. Your browser loads updates from our website and does not connect directly to the team API. We do not forward visitor IP addresses, cookies or account details to the team API. This feature sets no additional cookies and does not save roadmap data in browser storage.

Fundraiser in the wiki archive

The wiki archive includes a supplied record of the 2025 fundraiser transfer showing the amount, date, recipient, recipient bank details and payment reference. The sender’s account is blacked out. The record and donation QR code are hosted locally; any transfer takes place solely through your own banking app. Reading the page does not connect you to a bank or external image host.

App stores and ratings

These notices apply to app links and rating displays where they are offered on this website.

Download buttons link to the Apple App Store or Google Play. Your browser connects to the provider only when you open the link; its privacy notice then applies. Our server retrieves public aggregate ratings from the German App Store and caches them for up to 24 hours. Your IP address, cookies and other visitor data are not forwarded to Apple. Google Play figures are maintained editorially. The ratings display sets no cookies.

Join tutorial videos

In the homepage join guide and on the welcome bonus page, tutorial videos load from static.primeblocks.net. The media server receives technical connection data such as your IP address. The selected video plays muted on a loop and can be paused. With reduced motion enabled, playback starts only when you choose to play.

Managing website content

When authorized team members edit website content, drafts, published text and up to 20 published versions per language are stored on the website server. Version history includes the publication time and the responsible team member’s identifier. This makes changes traceable and allows earlier content to be restored.

Unsaved edits remain only in the open editor’s memory. The content editor does not create additional cookies or persistent browser data for this purpose.

Access to unpublished content and editing is restricted to signed-in team members with an explicitly assigned administration permission.

350-Gems gift and order status

The Allay on the homepage and shop is an image served by our website. When you claim the gift, the website sends the Minecraft name you entered to PrimePlatform, our account service. It creates a reservation for 350 gems for that name with the name, status and times. Your input, dialogs and timers stay in browser memory during your visit. To prevent mass reservations, we count new reservations per IP address for one hour and one day; these counters are deleted automatically at the end of each period.

So that the website can find your reservation again after a reload, we set the technically necessary cookie primeblocks-welcome-gift (HttpOnly, only for the gift requests, valid for up to 7 days and 15 minutes). It contains only a random reservation identifier. If you are signed in, we also check with your account's Minecraft UUID whether you have already received the gift.

The gift is paid out only if you join the server with that name within 10 minutes. The game server then sends your Minecraft UUID and name to PrimePlatform, credits the gems to your game account and confirms the payout. So that each person receives the gift only once, we permanently store your Minecraft UUID, name, the reservation identifier and the time after the payout. If you do not join in time, the reservation lapses; you can try again after 7 days, after which the lapsed reservation is deleted automatically.

The homepage and shop may request the gift status. After you return from checkout, the website may request your order status. These requests go to our website. The displayed time is an estimate; delivery is shown only after a confirmed status update.

If you enter a valid Minecraft name in the gift dialog, the matching head image may load after a short typing pause. The name is sent through our website to the existing image service. A displayed head image does not verify your identity or account ownership.

When you continue to payment in the shop, we give the Tebex basket a random order reference. So that the website can show the right status after you return, we set the technically necessary HttpOnly cookie primeblocks-checkout (only for shop requests to our website, valid for 6 hours). It contains this reference, the recipient's Minecraft name and the time. PrimePlatform matches the reference to Tebex's signed payment notifications and shows whether the payment is pending, confirmed, declined or refunded. The reference is stored with the payment notifications only as a non-reversible lookup key.

Website sounds

Short interface and confirmation sounds are loaded from our website after an interaction. You can turn them off using the sound control in the footer. This setting lasts only for the current visit and is not saved in cookies or persistent browser storage. No external audio service is embedded for these sounds.

Back to top