What Bloxstack collects, why, who else sees it, and how to get it deleted.
This policy explains how Bloxstack ("Bloxstack", "we", "us") handles personal data on bloxstack.app. It forms part of our Terms of Service.
A2Z Labs Inc., a Delaware C corporation, operates Bloxstack and is the controller of the data described here. For anything in this document, including a request to access or delete your data, write to legal@bloxstack.app.
The sections below cover account data, payment and verification records, optional connected services and advertising measurement.
1.1This policy covers the Bloxstack website and the services we operate on it, for members and for signed-out visitors.
1.2It does not cover Roblox. Your Roblox account is governed by Roblox’s Privacy Policy, and Roblox decides what it does and does not tell us about you. It also does not cover a third-party site you reach from a link on Bloxstack, including a link another member posts.
2.1Everything we hold about you falls into one of these rows.
| Data | Where it comes from |
|---|---|
| Roblox user id, username, display name, avatar image | Roblox, at sign-in, from the `openid profile` scope you approve. The user id is the permanent anchor of your account; the rest refreshes when you sign in again. |
| Roblox access and refresh tokens | Roblox, at sign-in. Held encrypted so we can refresh your linked identity. See §11. |
| Roblox public data and connected games | Public Roblox APIs provide profile and game metadata, creator and group information, public friend and follower counts, and available activity signals. Staff can also view the recent average price (RAP) total of a linked account’s public collectible inventory; private inventories are not accessed. Inventory totals are cached briefly, without keeping an item-level history. If you separately connect an experience, we record the game identifiers and ownership permission you approve. |
| Optional Studio analytics | Roblox, after a Studio manager separately authorises analytics access. We store encrypted connection tokens and the permitted game identifiers, and use them to retrieve metrics for authorised Studio members. A manager can disconnect the integration in Studio. |
| Your profile | You. Handle, display name, headline, bio, crafts, rates, availability, showcase, banner, theme, and layout choices. |
| What you publish | You. Listings, briefs, applications, forum posts, comments, reviews, and endorsements. |
| Private messages | You and the members you talk to. Messaging is an adult-only surface; conversations are stored so both sides can read them. |
| Deal records | You and the other member. What was agreed, what was delivered, and the state of the engagement. |
| Sessions | Automatically, when you sign in: a session record with its IP address, browser user agent, and timestamps. You can see and revoke your active sessions in Settings. |
| Abuse and rate-limit counters | Automatically. Keyed by a keyed hash of the IP address rather than the address itself, so the counter works without our storing a readable IP for it. |
| Payment records | Stripe, when you buy or sell. Customer, checkout, subscription, and connected-account identifiers, plus amounts, balance entries, rewards, refunds, disputes and operational records used to reconcile payments. We do not store full card numbers. |
| Age and balance eligibility | Your selected age range and country, guardian readiness, and Stripe verification reference, status and adult result. We do not store identity-document images or a date of birth. |
| Recovery email address | You, and only if you choose to add one in Settings. A Roblox sign-in gives us no email, so an account created that way starts with a placeholder address that cannot receive mail. |
| Email address, for the founding cohort | You, if you sign in at /waitlist with an emailed link. Or Google, if you sign in with Google, in which case Google also tells us your name, your profile picture, and that the address is verified. See §3.5. |
| Your waitlist record | Your email address, the name you gave, when you joined, whether your account has claimed the spot, and whether you have unsubscribed. It includes people who joined the earlier Bloxstack waitlist before this version of the site existed. |
| Announcement mail records | Automatically, one row per announcement we send you, so the same message is never sent twice. It records the address it went to, whether it was delivered, and any error. |
| Notification preferences | You. Which notifications you want, whether you want them by email, and your selected time zone, quiet hours, digest hour and optional-email pause. |
| Invite attribution | A first-party cookie set when you arrive through another member’s invite link, so their invite count is correct after you sign up. |
| Reports, appeals, and support messages | You, or the member reporting something, along with our moderation notes about the outcome. |
| Optional Discord connection and support tickets | If you connect Discord, its immutable user ID, username, display name, avatar reference and verification time. The connection requests identify only; OAuth tokens are discarded before storage. If you open a Discord support ticket, we retain its conversation text, message and channel identifiers, edit history, and attachment filename, size and type. Files stay in Discord; onsite links open the original private message. |
| Live view quality | Automatically, while you watch a hosted Studio on the web or in the app: how long the picture took to appear, how long you watched, how often it froze, its round-trip time and frame count, whether it fell back from video to pictures, and the kind of connection it used. Each report is added to daily counts by app or browser and connection type; your account is checked to limit how often reports arrive and is not stored with them. |
| Server logs | Automatically. Ordinary web-server and application logs used to keep the site running and to investigate faults and abuse. |
3.1Roblox sign-in asks for `openid` and `profile`: your account identifier, username, display name and avatar. Connecting an experience is a separate permission request on Roblox.
3.2Roblox sign-in does not give us your password, email address, date of birth, Robux balance or private messages. Public Roblox data and separately approved game connections are described in §2.
3.3The sign-in connection does not let us change your Roblox account. An experience ownership check records the game identifiers you authorise and requests revocation of its temporary token. Optional Studio analytics uses a separate, encrypted connection that remains available until disconnected or revoked.
3.4You can disconnect Bloxstack from your Roblox account at any time from Roblox’s own authorised-applications settings. Doing so stops the connection; it does not by itself delete your Bloxstack account, which you can ask us to do under §10.
3.5Roblox is not the only door, and the exception is where an email address enters the picture. The founding-cohort page at /waitlist also accepts an emailed sign-in link, which gives us the address you type and nothing else, or a Google sign-in, in which case Google tells us your email address, your name, your profile picture, and that Google has verified the address. We ask Google for nothing beyond that, and we never receive your Google password. That address is what we use to match you to your waitlist spot and to send you the announcements described in §4.
4.1We use the data in §2 for these purposes and no others.
4.2Where the GDPR or a similar law applies to you, our legal bases are: performance of our contract with you (running your account, deals, and purchases); our legitimate interests (security, abuse prevention, keeping invite attribution honest, and improving the product); compliance with a legal obligation (tax, accounting, and lawful requests); and your consent, where we ask for it, which today means optional email notifications and the founding-cohort announcements as well as any other consent requested for a specific feature. Where we rely on legitimate interests, you may object under §10, and you can withdraw consent to the announcements from any one of them without contacting us at all.
7.1Bloxstack is operated from servers in Canada, and the providers in §6 operate in Canada, the United States, and the European Union. Using the Service therefore involves transferring your data across borders.
7.2Where a transfer is subject to the GDPR or United Kingdom data protection law, we rely on the European Commission’s Standard Contractual Clauses (with the UK Addendum where applicable) or on an adequacy decision, as offered by the provider concerned.
8.1Your account, profile, and published content are kept while your account exists.
| Data | Retention |
|---|---|
| Account, profile, posts, listings, messages | Until you delete them, or until your account is deleted. Erased from live systems within 30 days. |
| Sessions | Until they expire or you revoke them. |
| Discord connection | Until disconnected or your account is deleted. Disconnecting does not remove an existing support conversation. A portfolio link may remain as an ordinary unverified link until you remove it. You can also revoke BloxStack in Discord’s Authorized Apps. |
| Support tickets and Discord copies | Kept while needed to provide support and review its outcome; solved tickets are not automatically deleted. Confirmed account erasure removes account-linked support records and queues removal of the corresponding private Discord channel. Unlinked Discord tickets require an ownership-verified support request. Failed remote cleanup remains in a retry queue for review. Staff edit history follows the ticket’s retention. |
| Waitlist record and announcement-mail rows | Removed with account deletion when linked to your account or matched to your verified email. For another address, request removal through support so we can verify ownership. |
| Rate-limit counters | Minutes to hours. They expire on their own. |
| Payment and transaction records | Kept for as long as tax and accounting law requires, typically seven years, even after account deletion. Stripe keeps its own records under its own policy. |
| Moderation records | Kept while needed to enforce a suspension or ban and to handle an appeal or a legal claim. |
| Browser diagnostic references | 14 days. These contain a random report reference, broad site area, error category and optional script filename; no account identifier, page URL, error text or form content. |
| Aggregate browser performance ratings | 90 days, grouped by day, broad site area and metric. |
| Aggregate live view quality | 90 days, grouped by day, app or browser, and connection type; counts and timing ranges only, with no account identifier. |
| Queued optional and security email | Up to 30 days; optional content expires before delivery when it is no longer timely, and queued content is removed with account deletion. |
| Server logs | Rotated on a short cycle in the ordinary course. |
8.2Database backups may contain deleted data until they rotate out; verified local backups rotate after 14 days, and encrypted copies in private Cloudflare R2 storage expire after 30 days. Backups are excluded from ordinary use, and erasures must be reapplied before a restored database returns to service. Minimal account identifiers and keyed email hashes are retained to prevent deleted data from reappearing through event or email-provider retries.
9.1Bloxstack is a professional network for people who make things, and it is not directed to children under 13. You must be at least 13 to hold an account.
9.2If we learn that an account belongs to someone under 13, we delete the account and the data attached to it. A parent or guardian who believes a child under 13 has given us data should write to legal@bloxstack.app and we will act on it promptly.
9.3Roblox sign-in does not provide your date of birth, and we do not ask for it to use the Service or a balance. If you give an age range or a billing country, we store it. A Stripe Identity check gives us a verified adult result, its source and verification reference. Stripe supplies the date of birth for that check; we reduce it to the age result and do not store the date of birth in Bloxstack.
9.4Not every member has verified their age, and most never need to. We check age only when money is withdrawn, where Stripe verifies an adult payout account or, for ages 13 to 17, a parent or guardian on it, and before a venture stake, which is limited to members 18 or over. Public participation does not itself confirm anyone’s age.
9.5We use age results and reports to restrict access where required by the Terms. Contact support about an underage account or inappropriate contact. Payment verification does not remove the age restrictions on private messaging.
9.6Because public pages are public, the safest posture for a younger member is the ordinary one: publish your work, never your contact details.
10.1Depending on where you live, you have some or all of these rights: to know what we hold about you and get a copy; to correct it; to have it deleted; to restrict or object to how we use it; to receive it in a portable format; and to withdraw a consent you gave us. Exercising a right never costs you anything and never worsens the service you get.
10.2Some of this is self-service today: your profile is editable in Settings, you can revoke sessions there, you can turn off email notifications there, and you can delete individual posts and listings yourself.
10.3You can delete your account or request removal of specific information in Settings → Privacy & safety. Deletion requires a recent sign-in and confirmation. Account and personal-content rows are removed from the live database immediately; uploaded files and provider contacts are processed by a retrying cleanup job after existing upload links expire. Shared studios, payment obligations, and moderation records require support review: use the erasure-request option rather than abandoning your request. You can also email legal@bloxstack.app or use the support desk, including if you cannot sign in. We respond without undue delay and within one calendar month, explain any lawful retention or refusal, and notify you within that month if a permitted extension is necessary. You can also prepare a single-use account-record download from Settings → Privacy. It requires a recent sign-in, expires after one hour, and contains account details, authored text, listing records, purchases and email preferences. Uploaded file bytes, private content authored by others and staff notes are excluded; contact support for additional records. The same support channels handle access, correction, portability, restriction, and objection requests.
10.4We verify a request by requiring it to come from your signed-in account or from the recovery address on file. The alternative, handing your data to whoever asks, is worse than the friction.
10.5If you are in the European Economic Area or the United Kingdom you may complain to your local supervisory authority. If you are in California you may exercise your rights through an authorised agent. We would rather hear from you first, and usually resolve it faster.
11.1The site is served over HTTPS only. Session cookies are HTTP-only, and sensitive actions require a recent sign-in before they will run.
11.2The Roblox tokens we hold are encrypted before they are written, with the key held outside the database, so a database copy alone does not yield a usable token. We do not store passwords for the Service at all, because there are none.
11.3You can add two-factor authentication and review your active sessions in Settings. Because a Bloxstack profile is reached through the account that signs into it, securing that account (your Roblox account, or the Google account or mailbox you used at /waitlist) is the most important thing you can do for your Bloxstack account.
11.4Uploaded files live in private storage and are reachable only through short-lived signed links. No storage bucket is publicly listable.
11.5No system is perfectly secure. If we become aware of a breach affecting your personal data we will notify you and the relevant authorities as the law requires. If you find a vulnerability, report it to legal@bloxstack.app rather than exploiting it, and we will not pursue you for a good-faith report.
12.1Ordering on Bloxstack is automated and, at the moment, plain: search results are ranked by how well the text of your profile matches the query, then by recency; directories and listings are ordered by recency or by the sort you pick. Endorsements and delivery record are shown on a profile, but they do not currently move you up a results page. Ordering affects visibility, not rights, and it is not a decision with a legal or similarly significant effect on you.
12.2Enforcement decisions that do affect your account (removal, suspension, termination) are made or confirmed by a person, and are appealable under the Terms.
13.1We update this policy when what we do changes. The effective date at the top always tells you which version is current.
13.2If a change materially affects how we use data we already hold, we will give notice before it takes effect, and will ask for consent where the law requires it.
14.1Privacy questions, data requests, and anything else in this document: legal@bloxstack.app.
14.2Account problems, reports, and appeals are handled faster through the support desk, by the same people.