Privacy and Storage Policy

What BuildEx collects, why, who else can see it, and how to get it changed or deleted.

Version 2.11Effective November 11, 2026

01What is collected

When you sign in with Google or Discord, BuildEx receives an account identifier, your email address, and the display name and picture attached to that account. It does not receive your password.

When you sign in with an email code instead, BuildEx keeps the email address you enter as your account's address. See "Signing in with an email code" below.

If you publish a builder profile, BuildEx stores what you enter: your handle, display name, description, styles and build types, the contact links you choose to publish, your avatar and banner, and your portfolio images.

BuildEx also stores the messages you send through the site, the briefs you send and the orders you agree in a chat (what was asked for, the agreed price and deadline, and when each step happened), the 3D previews you send (see "3D previews" below), the requests you post on "Looking for a builder" and the responses you send to them, the builds you post to the Showcase (their photos and caption) and the works and posts you save, the files you share in the Library and who downloaded them, the contests you announce, the messages you write in the global chat, the discussion topics and replies you post and the ones you mark helpful or save, the reports you send about public content, the builders you favourite, reports you submit, notifications generated for you, your email-notification setting and preferred language, and a timestamp of when you were last active, which is what drives the online indicator. Ordinary technical logs are produced by our hosting and database providers. Page visits are counted without cookies — see "Visitor statistics" below — and BuildEx records which site or link each visit and each new account came from — see "Where visitors come from".

02Google user data

If you choose to sign in with Google, BuildEx requests only the basic scopes openid, email and profile. From Google it receives your Google account identifier, your email address, your name and your profile picture. BuildEx does not request access to Gmail, Google Drive, Google Calendar, your contacts or any other Google service, and it never sees your Google password.

This data is used only to sign you in, to keep your BuildEx account linked to your Google account, to pre-fill the display name and picture on your account (which you can change), to email you when a message sent to you on BuildEx goes unread (which you can turn off — see "Message emails" below), and to contact you about your account or a moderation matter. Your Google email address is never shown on your public profile.

Google user data is not sold, is not used for advertising, is not used to build user profiles for anyone else, and is not used to develop, improve or train artificial-intelligence or machine-learning models. It is not shared with anyone except Supabase, which stores it for us to run sign-in, Resend, which receives your email address only to deliver sign-in codes and message emails, and where the law requires disclosure.

BuildEx's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

The data is kept while your BuildEx account exists and is deleted when you delete your account from the account page. You can also revoke BuildEx's access at any time at myaccount.google.com/permissions, or ask for deletion by writing to mcbuildex@gmail.com.

03Why it is used

To create and run your account, to publish your profile if you have one, to deliver your messages and notifications, to show accurate online status, to enforce the Terms of Use and moderate abuse, to understand which sites, searches and links bring people to BuildEx, and to keep the service working and secure.

Depending on where you live, the legal basis for this is the contract between you and BuildEx, our legitimate interest in running a safe directory, your consent where you chose to publish something, or a legal obligation.

BuildEx does not sell personal data and does not use it for advertising or profiling.

04Signing in with an email code

Instead of Google or Discord, you can sign in with your email address. BuildEx emails that address a six-digit code; typing it on the login page signs you in, or creates your account if you are new. A code works once and expires after ten minutes. BuildEx has no passwords, so the code is the only way into an account that uses email sign-in.

BuildEx keeps the address you enter as your account's email address and uses it as described in this policy. It is not shown on your profile, and BuildEx does not derive your handle or display name from it. If the address already belongs to an account you created with Google or Discord, the code signs you in to that same account.

The codes are delivered by Resend, which receives your email address and the email for that purpose. A sign-in email contains only the code; it carries no marketing and no open or click tracking.

05Bot check on the login page

To stop automated sign-ups and abuse of the code emails, the login page uses Cloudflare Turnstile, a bot check run by Cloudflare. While you are on that page, Turnstile reads technical signals from your browser and connection — such as your IP address and browser characteristics — and Cloudflare uses them to tell people from automated traffic. Usually this needs nothing from you; occasionally it asks for a click.

BuildEx only learns whether the check was passed. Turnstile runs only on the login page, in a frame served by Cloudflare, and Cloudflare processes this data under its own privacy policy and says it does not use it for advertising. The legal basis is our legitimate interest in keeping sign-in secure.

06Community

The Showcase holds the builds people choose to post to the community: the photos you upload for a post and its caption. A post is public to anyone on the internet, with your display name and avatar, and stays until you edit it or a moderator hides it. The photos are stored in a public bucket under your account and are deleted with your account. Works and posts you save are private to you.

Discussion topics and replies are public, with your display name and avatar, and stay until you or a moderator remove them. Marking something helpful and saving a topic are not shown to others, except as a count. When someone replies to your topic, BuildEx tells you in the notifications.

A request you post on "Looking for a builder" is public: anyone can read it, with your display name and avatar, for 30 days or until you close it, and moderators can hide it. When a builder responds, BuildEx opens a chat between you and puts the request there; who responded is visible only to you and to moderators.

A file you share in the Library, its photos and description, and a contest you announce are public, with your display name and avatar, and stay until you or a moderator remove them. Library files and photos are stored in public buckets under your account and are deleted with your account. When you download a Library file while signed in, BuildEx records that you did, once, to count downloads; who downloaded is not shown to anyone.

Messages in the global chat are public: anyone can read them, with your display name and avatar, and they stay until a moderator hides them or your account is deleted. Moderators can hide messages and pause an account from writing in the chat for a while.

073D previews

When you send a 3D preview in a chat, your browser reads the schematic or world file on your own device. The file itself is not uploaded. What is uploaded is a compact preview — the positions and colours of the outer blocks only, which cannot be turned back into a usable schematic — and a small picture of it.

The preview and the picture are stored like chat photos: under a random address that only the people in the conversation are given, and visible to BuildEx moderators. They are deleted with your account.

08Message emails

BuildEx uses the email address on your account to tell you about messages you have not read. If someone messages you and the message is still unread about ten minutes later, BuildEx sends one email with the sender's name, a short preview of the message (a photo is described, not attached) and a link back to the conversation. It does not email you about that conversation again until you have opened it, and it limits how many of these emails anyone receives in an hour and in a day.

These emails are on for every account by default, because they are part of how messaging works. You can turn them off at any time with the unsubscribe link at the bottom of any of them — no sign-in needed — or under Account → Email notifications. Turning them off does not affect your messages, which stay in BuildEx. Emails are written in the language you last chose on the site.

The emails are delivered by Resend, which receives your email address and the content of each email for that purpose. BuildEx does not use them for marketing and does not turn on open or click tracking for them. A record of each one — when it was due, whether it was sent, and the preview it carried — is kept for up to 30 days to enforce the limits and to investigate delivery problems.

09Works, likes, views and reviews

If you are a builder, BuildEx stores the works you publish (their photos, titles, descriptions, version, size and duration, and the people you credit as co-authors), your price list and the year you started building. These are public, like the rest of your profile.

When you like a work, BuildEx stores that your account liked it. Who liked what is not shown to anyone; the builder and visitors see only the total.

When a work is opened, BuildEx counts one view per viewer per work per day. A signed-in viewer is counted by account. For a visitor who is not signed in, the database computes a one-way hash of the visitor's IP address, the date and a secret value, and keeps only that hash; the IP address itself is not stored. The hashes change every day, cannot be turned back into an IP address, and are deleted within two days — only the total number of views is kept. The builder's own views are not counted. Your browser also remembers, for the length of the tab, which works it has already reported, so they are not reported twice. The legal basis is our legitimate interest in showing builders and visitors how much a work is seen, while preventing inflated counts.

A review you write is public, together with your display name and avatar, and stays until you delete it or a moderator hides it. To decide whether you may review a builder, BuildEx checks whether you have confirmed an order with them as complete, or counts the messages each of you has sent in your conversation and checks when it started; it does not read their content for this. A review written after an order is linked to that order. A builder's typical reply time is calculated from the timestamps of messages in their conversations and shown on their profile as a single figure.

10What is public

A builder profile is public to anyone on the internet: handle, display name, description, styles, build types, avatar, banner, portfolio images, the contact links you published, and whether you were recently active.

Publishing a Discord handle, Telegram username or any other contact link makes it public. Only publish contact details you are willing for strangers to see and use.

Messages, briefs and orders are visible to the people in that conversation and to BuildEx moderators. A moderator reads a conversation when it is reported, and may also read conversations that nobody reported, to look for scams, spam, harassment and other breaches of the Terms of Use or the Community Policy. Every time a moderator opens a conversation, BuildEx records who opened it and when. Messages are not used for advertising or for anything other than running and moderating the service.

Your email address is not shown on your profile.

11Who else handles it

Supabase hosts the database, authentication and file storage. Google and Discord provide sign-in. Resend delivers sign-in codes and message emails. Cloudflare provides visitor statistics and the bot check on the login page. The site is served by our web host. These providers process data on our behalf, may do so in other countries, and have their own privacy policies.

Data may also be disclosed where the law requires it, or where it is necessary to investigate abuse or protect someone's safety.

12Keeping and deleting

Account and profile data is kept while the account exists. Deleting your account from the account page removes your profile, your portfolio images and your uploaded files, and is not reversible.

Messages you have already sent stay in the recipient's conversation. Moderation records, reports and the record of moderators opening conversations may be kept for as long as needed to deal with repeat abuse and to comply with the law. Backups are overwritten on an ordinary schedule.

Records of legal acceptances — which version of these documents an account accepted, and when — are kept as evidence that consent was given.

13Your choices

You can edit or delete your profile and its images at any time from your account page, and delete your account there too. You can turn message emails off from the account page or with the link in any of them.

Subject to local law, you may also ask for access to your data, correction, a copy, deletion, restriction, or to object to processing, by writing to mcbuildex@gmail.com. We may need to confirm who you are first. You can complain to your local data-protection authority.

Nothing in this document removes a right or remedy that applicable law does not allow to be removed.

14Visitor statistics

BuildEx uses Cloudflare Web Analytics to count visits and to see which pages are used and how quickly they load. When you open a page, a small script sends Cloudflare the page's address, the address of the page you came from, your browser, operating system and device type, and how long the page took to load; Cloudflare works out your approximate country from the connection. Pages whose address carries a sign-in code or an unsubscribe link are not counted.

This uses no cookies or other browser storage, does not recognise you from one visit to the next or across other websites, and is not linked to your BuildEx account. Like any connection, it reaches Cloudflare from your IP address, which Cloudflare says it does not use to identify or track visitors. BuildEx sees only totals — for example how many visits a page had, or from which countries — never a record of one person's visit. The legal basis is our legitimate interest in knowing how the site is used.

15Where visitors come from

Separately from the statistics above, BuildEx records where visits come from. When you open the site in a new browser tab, the site works out how you arrived: the kind of source (a search engine, a social network, another website, a tagged link, or none), its name, any campaign label in the link you followed (such as ?ref= or utm_ tags), the domain of the site you came from, the first page you opened, whether you are on a phone, tablet or computer, and your browser's language. This is stored as one visit record with no IP address, no account and no other identifier. Moving between pages in the same tab is not a new visit.

So that the counts cannot be inflated, the database computes a one-way hash of your IP address, the date and a secret value, the same way it counts work views. The hash is kept apart from the visit records, changes every day, cannot be turned back into an IP address and is deleted within two days.

Your browser keeps a note of the most recent source that was not a direct visit, and the tab remembers that its visit was counted. If you then create an account, that source and the time of that visit are stored with your new account, so BuildEx can see which sites and links bring people who sign up. Only BuildEx moderators can see it; it is not shown on your profile and is deleted with your account. Signing in to an account you already have records nothing.

The legal basis is our legitimate interest in knowing which sites, searches and advertising bring people to BuildEx. You can remove the note at any time by clearing this site's data in your browser.

16Cookies and security

BuildEx uses browser storage for things the site needs to work — your sign-in session, your light or dark theme choice and a few interface preferences — and for the note of how you arrived described in "Where visitors come from". There are no advertising cookies, and the Cloudflare visitor statistics use no cookies or browser storage at all. The bot check on the login page runs in Cloudflare's frame under Cloudflare's own terms. If that ever changes, a consent control will be added where the law requires one.

BuildEx stores no passwords: you sign in through Google, Discord or a one-time code sent to your email. Access to data is restricted at the database level so that users can only read and change what is theirs, and public profiles are the only thing served publicly. No system is perfectly secure; if you think an account or the service has been compromised, write to mcbuildex@gmail.com.

Questions about this document?

Ask us and we will explain how it applies.

mcbuildex@gmail.com