Blockplan
Privacy Terms of Service Refunds Back to the editor

Privacy Policy

Effective 1 October 2026. This policy explains what information Blockplan collects, why, and the choices you have. See also the Terms of Service and Refund Policy.

Contents
  1. 1. Who we are
  2. 2. What we collect
  3. 3. Photos, songs, real places & your build files
  4. 4. Community: builds, posts, comments, likes & pictures
  5. 5. Payments
  6. 6. Service providers
  7. 7. Cookies & local storage
  8. 8. Ads
  9. 9. How we use your information
  10. 10. How long we keep it
  11. 11. Sharing & disclosure
  12. 12. Your rights & deleting your account
  13. 13. Legal bases & international transfers
  14. 14. Children
  15. 15. Security
  16. 16. Changes to this policy
  17. 17. Contact

1. Who we are

Blockplan (blockplan.build) is operated by BlockPlan, based in the Maldives (“we”, “us”). We are responsible for the personal information described in this policy. Contact: blockplan.build@gmail.com. Paid plans are sold through Paddle.com, our reseller and merchant of record (see §5).

2. What we collect

You can use the Blockplan editor without an account: the editor, building tools and local export run in your browser, and your builds stay on your device. We collect the information below only when you create an account or use a feature that needs our servers.

If you create an account

  • Email address — to sign you in, confirm your address, and send account emails such as confirmation codes and password resets.
  • Password — stored only as a salted PBKDF2-SHA256 hash. We never store or log your password itself.
  • Username — optional. It’s the public name shown next to builds, posts and comments you share in Community. You need one only to post or comment.
  • Display name — optional, shown back to you in the app.
  • Age confirmation — at sign-up you confirm you’re at least 13, and we record that you confirmed it and when. We don’t ask for your date of birth.
  • Cloud projects — the builds you choose to save to your account (block positions, layers and names).
  • Saved structures — structures you save to “My Structures” (the design and a small preview picture).
  • Plan and subscription status — which plan you’re on and whether your subscription is active, as reported to us by Paddle.

Collected automatically

  • IP address — used briefly to limit repeated sign-in, sign-up and password-reset attempts. It is converted to a one-way hash before being stored in a short-lived counter; we don’t store your IP address itself or use it to track you.
  • Security events — account actions such as “signed in”, “password reset requested” or “account deleted”, recorded with your account ID, the event and the time. Never your password, session token or IP address.
  • Usage counts — how many times you used features that have plan limits (for example exports per day).
  • Session cookie — see §7.
  • Page counts — when a page opens, the page’s name (for example “Community”) and whether it is the first page in that browser tab are added to daily totals. To count unique visitors per day, a one-way hash of your IP address and browser name, mixed with a random value that changes every day, is kept for that day only and then deleted together with the random value, so it can’t be linked to you or to another day. Nothing is counted when your browser sends Do Not Track or Global Privacy Control. No cookies or identifiers are stored in your browser for this.
  • Activity days — for signed-in accounts, which days the account was used (to see how many people come back), with the account ID and the date only.

Bug reports you send

  • When you use Report a bug, we keep your description, an optional screenshot of the 3D view you chose to attach, and the technical details shown in the form before sending (app version, page, browser and system name, screen size, graphics card name, recent error messages). Emails, web addresses and long codes are removed from the text. If you are signed in, the report is linked to your account ID.

We don’t use third-party analytics or tracking pixels.

3. Photos, songs, real places & your build files

Photo → block art. At the free sizes the image is processed entirely in your browser and never uploaded. For the larger sizes on paid plans, your browser first shrinks the image to the size you chose and sends those pixel colours to our server in small tiles to match them against block colours; the tiles are processed in memory and not stored. Only the resulting blocks become part of your build.

Song → note blocks. The audio or MIDI file is analysed in your browser and never uploaded. Only the resulting notes (pitch, timing and instrument) are sent to our server, which turns them into the note-block build.

Real place → Minecraft. The place you search for is sent to our server, which looks it up with an OpenStreetMap search service. When you generate, our server checks your plan and gives your browser permission for exactly that map area; your browser then downloads that area's map data (OpenFreeMap vector tiles) and elevation (the public Amazon terrain tiles dataset) through our server, which fetches them and passes them on — those services receive our server's request, not your identity. The blocks are worked out in your browser. The map you pan and zoom loads its tiles directly from OpenFreeMap, which receives your IP address to serve them, as any website does. We count how many places you generate each billing month (plan limits); the demo place isn't counted.

Your build files. Design files you open are read in your browser. Nothing is uploaded unless you save to the cloud, save a structure to your account, or share to Community while signed in.

4. Community: builds, posts, comments, likes & pictures

  • Public by your choice. Builds you share (with their name, description, category, the creator name you choose and their pictures), and the posts, comments and pictures you publish, are public. They show your username, never your email address. Like counts are public; who liked something isn’t shown.
  • Pictures. Pictures of a shared build are rendered from your build in your browser, or are pictures you choose to upload. Uploaded pictures are re-saved in your browser before they’re sent, and our server removes any remaining metadata (such as camera details and location) before storing them.
  • Reports and moderation. If you report something, we keep the report (your account ID, the reason and any note) so a moderator can review it. Content reported by several people is hidden until a moderator reviews it, and moderators can remove content that breaks the Community rules.
  • Profile card. Anyone can open your profile card from your name. It shows your username, the display name you chose, the cosmetics you wear, the month you joined, your number of shared builds, posts and likes, and a Gold or Diamond badge if you have a paid plan. It never shows your email address.
  • Friends, chat and gifts. Friend requests, blocks and BP gifts connect two usernames; we keep who is friends with whom, who blocked whom, and a record of each gift (sender, receiver, amount and the short message you add). Global chat messages are public to every signed-in person and show your username and the name style and profile frame you chose. Direct messages are visible to the two people in the chat; we don’t read them, but if either person reports a message, the moderators and the site owner can see the reported message to decide what to do. Messages from someone who isn’t your friend arrive as a request that you accept or decline. You can delete your own messages, and block anyone. A moderator can delete messages and mute accounts that break the Community rules.
  • Events. Diamond members can host events with BP prizes. An event shows the host’s username, its rules and prizes, how many people entered, and the builds ranked by likes; entering shows your username and the build you entered.
  • Your control. You can hide or delete your shared builds and delete your posts and comments at any time; the owner of a build or post can also delete comments on it. Deleting removes the content together with its pictures, likes and comments.

5. Payments

Paid plans (Gold and Diamond) and BlockPoints packs are sold by Paddle.com, which acts as our reseller and merchant of record. When you buy a plan, Paddle collects your payment details, billing address and other information needed to process the payment and calculate tax, under Paddle’s Privacy Notice, as an independent controller of that information. We never see or store your card details. Paddle tells us your subscription status, plan and renewal date, together with the Paddle customer, subscription and transaction identifiers (and refund or chargeback notices) we need to manage your plan and your BlockPoints.

BlockPoints (BP). We keep a record of every change to your BP balance — when, how much, why (for example a daily streak, a purchase or a build sale) and, for build sales, the other account involved — plus the cosmetics you own and wear. Other people can see the cosmetics you wear next to your username; they never see your balance or history.

6. Service providers

We use a small number of service providers to run Blockplan. We don’t sell or rent your information, and each provider receives only what it needs to do its job:

  • Cloudflare — hosting, database, file storage and serverless functions, and Cloudflare Turnstile, which protects sign-up and sign-in forms from automated abuse.
  • Paddle — payments, tax and subscription management (see §5).
  • Resend — sends our account emails. It receives your email address and the content of that email.
  • OpenStreetMap search (place search), OpenFreeMap vector tiles (map data) and the public Amazon terrain tiles dataset — fetched by our server for the Real place tool; they receive the search text or the map tiles requested, not your identity.
  • OpenFreeMap — serves the map tiles shown in the Real place tool.
  • Google AdSense — only if ads are enabled on the site, only on Free pages, and only as described in §8.

Their privacy policies: Cloudflare, Paddle, Resend, OpenStreetMap, Google (ads).

7. Cookies & local storage

Blockplan sets one cookie of its own: bp_session, a random session token that keeps you signed in. It is inaccessible to page scripts (HttpOnly), sent only over HTTPS, limited to our own requests, and removed when you sign out or after 30 days without use. The Paddle checkout and Cloudflare Turnstile may set cookies needed for payment security and abuse prevention.

The app also uses your browser’s local storage for conveniences such as your preferences, favourite blocks, recent structures, your autosaved build and your ad choice (§8). This stays on your device and isn’t sent to us.

8. Ads

  • Where. Only on some Free pages (the home page, Community and tool pages), below the content and clearly labelled “Ad” — never in the editor, never next to buttons such as Delete, Export or Buy, and never on the pricing, checkout or account pages. Paid (Gold and Diamond) accounts never see ads.
  • Reward ads. On the Free plan you can choose to watch an ad for BlockPoints. Before it starts we tell you what you get and that it is an ad from our advertising partner (Google). We give the page a random one-time session number (never your name, email or account id); when the ad provider reports the reward in your browser, our server checks the session, the time, your daily limit and credits the reward once. To spot abuse we keep, for each attempt, a keyed fingerprint of your IP address (not the address itself) and the country your connection comes from. The provider’s script receives what any website visit sends (such as IP address and browser details) and, if you allow personalised ads, may use cookies under its own policy.
  • When. Only if ads are enabled on the site; otherwise no ad code loads at all. The provider’s script loads only when an ad is about to scroll into view.
  • Your choice. The first time an ad would appear, you choose between non-personalised ads (the default) and personalised ads, and you can change this at any time in Settings → Privacy. We don’t send the ad provider any information about you; its script receives what any website visit sends (such as IP address and browser details) and, if you allow personalised ads, may use cookies under its own policy.

9. How we use your information

  • To create and secure your account and sign you in.
  • To store your cloud projects and saved structures and give them back to you.
  • To show what you choose to share in Community, and to keep Community safe (daily limits, reports and moderation).
  • To provide your plan: apply its limits and manage your subscription with Paddle.
  • To send account emails (confirmation codes, password resets and important service or billing notices). We don’t send marketing email.
  • To detect and prevent abuse, fraud and attacks.
  • To meet legal obligations, such as keeping records required for tax.

10. How long we keep it

  • Account, projects and structures — until you delete them or your account.
  • Deleted projects and structures — kept in Trash for 7 days so you can restore them, then permanently erased.
  • Community content — until you delete it or your account, or a moderator removes it. Reports are kept while the content they concern exists.
  • Chat messages — global chat 30 minutes (messages disappear from the chat after 30 minutes and are then deleted), direct messages 90 days (a reported message is kept until a moderator has dealt with the report); chat reports 90 days after they are handled. Friend lists, blocks and gift records — as long as your account exists.
  • Sessions — until you sign out, or 30 days without use.
  • Confirmation codes and reset links — single-use and short-lived; the records are removed 7 days after they expire or are used.
  • Accounts never confirmed by email — removed after 30 days if they hold no projects or payments.
  • Abuse-prevention counters — removed after 2 days.
  • Usage counts — 13 months.
  • Security events — 12 months.
  • Daily page and visitor totals — numbers only, 400 days. The day’s visitor hashes and their random value — deleted when the day is over.
  • Activity days — 400 days.
  • Bug reports (and their screenshots) — 180 days.
  • Payment and subscription records — as long as needed for billing, refunds and disputes, and as required by tax law, including after account deletion.
  • BlockPoints records (balance history, purchases, build sales) — as long as your account exists, and afterwards as long as needed for refunds, disputes and fraud prevention. Reward-ad session and step records — 180 days.

11. Sharing & disclosure

What you share in Community is public by your choice (§4). Otherwise we share information only with the service providers in §6, and only as needed to run Blockplan. We do not sell personal information. We may disclose information if required by law or valid legal process, or where necessary to protect the safety, rights or security of our users, the public or Blockplan.

12. Your rights & deleting your account

You can delete your account at any time in Account → Delete account. When you do:

  • Your cloud projects and saved structures are permanently deleted.
  • Everything you shared in Community — builds, pictures, posts, comments, likes and reports — is deleted, and your username is released.
  • You are signed out everywhere, and your email address and password are removed so the account can never be used again.
  • Payment and subscription records are kept only as required for billing and tax (see §10). If you have an active subscription, cancel it first in Account → Manage billing.

You can also ask us to give you a copy of your information, correct it, delete it, restrict or object to how we use it, or receive it in a portable format. Email blockplan.build@gmail.com from the address on your account; we’ll respond within 30 days. If you’re not satisfied with our response, you may complain to the data protection authority where you live.

13. Legal bases & international transfers

Where the law requires a legal basis for using personal information (for example in the EEA and UK), we rely on: performing our contract with you (your account, cloud storage, Community features and your plan); our legitimate interests (keeping Blockplan secure, preventing abuse and improving the service, balanced against your rights); your consent (personalised ads, which you can withdraw at any time); and legal obligations (such as tax records). Our service providers may process information in countries other than yours, including the United States; where the law requires, these transfers are covered by appropriate safeguards such as the European Commission’s standard contractual clauses provided by those providers.

If you’re in California, you have the right to know what personal information we collect and how we use it, to request its deletion or correction, and not to be discriminated against for using these rights. We don’t sell personal information. Non-personalised ads are the default; you can turn personalised ads off at any time in Settings → Privacy.

14. Children

Blockplan accounts are for people aged 13 and over (or the minimum age for online services where you live, if higher), and sign-up requires confirming this. We don’t knowingly collect personal information from children under 13. If you believe a child under 13 has created an account, contact us and we’ll delete it.

15. Security

We protect your information with measures including hashed passwords, random session tokens, HTTPS for all traffic, optional two-factor authentication, rate limits against automated attacks, and access checks on every request so that one account can only ever read or change its own data. No system is completely secure, but we work to protect your information and will notify you as required by law if a breach affects it.

16. Changes to this policy

We may update this policy from time to time. We’ll change the effective date at the top of this page, and for significant changes we’ll give notice on the site or by email before they take effect.

17. Contact

Questions, requests or concerns about privacy: blockplan.build@gmail.com.

© 2026 BlockPlan. See also the Terms of Service and Refund Policy.