Skip to content
Dream-a-brick
  • Home
  • Styles
  • FAQ
  • Support
Coming soon to iPhone
Menu
  • Home
  • Styles
  • FAQ
  • Support
Coming soon to iPhone

Legal

Privacy policy

What Dream-a-brick collects, why, where it is kept, who helps us run the service, and how to have it deleted.


Draft, not yet reviewed

This page is a working draft. It has not been reviewed yet and may change before Dream-a-brick launches.

Last updated 16 November 2026.

Who we are

Dream-a-brick is an iPhone app that turns your photos into a brick model you can build, with step-by-step instructions and a kit of parts you can order. The controller of your personal data is the operator of Dream-a-brick:

[Legal entity name], [postal address].

You can reach us about anything on this page at support@dreamabrick.com.

This website

This website (dreamabrick.com) sets no cookies, runs no analytics, uses no local storage and loads no third-party scripts, fonts or embeds. It is a set of static pages served by Amazon Web Services (S3 and CloudFront). To deliver a page, the hosting service necessarily processes your IP address and the page you ask for; we have not switched on access logs for the site.

What the app collects, and why

We collect what it takes to make your models, sell you what you buy and deliver your kit. The app has no advertising, no tracking and no analytics or crash-reporting tools, and we do not sell your data or share it with data brokers.

  • Your account. You sign in with Apple, Google or your e-mail address, through Firebase Authentication (Google). We receive your e-mail address, your display name and an account id. We use them to create your account, sign you in and keep your models, purchases and orders together.
  • Your photos. The photos you take or pick for a model are uploaded to our servers and used to make that model: a 3D shape, the brick design, its pictures and a short name for the model. Before we use them, our own servers in the EU check them against our content policy (no nudity, no violence, no hate symbols, nothing that harms children). We also send them once to an AI model run by Anthropic, only to write the model’s short name. For the CubeHead style the service may check that the first photo shows exactly one face. It counts faces; it does not recognise who anyone is.
  • What we make for you. The model’s short name, the 3D brick model, step-by-step instructions, the parts list, files you can download and rendered pictures of the model are stored with your account.
  • What you write in the app. A description of what you want built, instructions for the builder, requests to change the picture we generate from your description, and change requests when you refine a model. We check this text against our content policy on our own servers in the EU, and then send it to the AI designer that builds the model. When you build from a description alone, with no photo, we also generate a picture of what you described. We also keep the title, description and tags of a model you publish; reports you file about other people’s models; and the authors you block.
  • Purchases in the App Store. Designs and the Builder membership are bought through Apple’s In-App Purchase. Apple handles the payment. We receive a signed record of each purchase (the product, transaction ids, the date, and Apple’s price, currency and storefront) and use it to give you what you bought and to keep our accounts.
  • Kit orders. A kit is paid on our payment provider’s secure checkout page (Apple Pay or card). Card details are entered on that page, never in the app, and we do not receive or store card numbers. We keep the order: the parts, the amounts, its status, the payment references, and the name and delivery address you entered. The app also remembers your last delivery address on your phone, and it can be saved with your account.
  • Notifications. If you allow notifications, the app sends us your phone’s push token, the app version and whether it is a test or App Store build. We use them only to tell you when a model is ready, or when a build could not be finished. We also e-mail you about the same events, and we keep a log of each notification we send (without the token or your e-mail address).
  • Support messages. When you write to us, we keep your message and our reply so we can help you.
  • Server logs. Our servers keep operational logs to run and secure the service.

Why we may use it (legal bases)

If you are in the European Economic Area, the UK or Switzerland, we rely on these legal bases:

  • To provide the service you asked for (performance of a contract): your account, photos, models, purchases, kit orders and the notifications about your builds.
  • To meet legal duties (legal obligation): keeping purchase and order records for tax and accounting.
  • Our legitimate interests: keeping the service secure, handling refunds and chargebacks, and moderating content that people publish or report.
  • Your consent: push notifications, which you can switch off at any time in your iPhone’s settings.

Who helps us run the service

We share personal data only with the service providers below, and only as far as each one needs it to do its part. They process it on our behalf.

  • Amazon Web Services, in the Frankfurt region (eu-central-1): our servers, database and file storage (photos, models and instructions), server logs and backups. It also runs the content-policy check of your photos and typed text (Amazon Bedrock Guardrails, in our own AWS account, in Frankfurt).
  • Google (Firebase Authentication): sign-in.
  • Apple: Sign in with Apple, In-App Purchase and push notifications (Apple Push Notification service).
  • Modal (United States): the rented GPU computers that turn your photo into a 3D shape and pictures. They fetch the photo through a short-lived link and send the results back to our storage. For a build from a description alone, an image model that we run ourselves on these computers draws a picture of the subject you described; your text is processed there and not passed to a third-party image service.
  • OpenAI, directly or through Amazon Bedrock: the AI designer that builds the brick model. It receives the cleaned-up photo (the subject cut out of its background) or your description, and the text you type (instructions for the builder and refinement requests), after our content-policy check described under Amazon Web Services. These requests may be processed in the United States.
  • Anthropic (United States), through its API: its Claude Haiku 5.5 AI model receives the photos you upload, once, only to write the model’s short name (for example “Golden Retriever Puppy”). It does not identify people. Under Anthropic’s terms for its API, your photos are not used to train its models, and Anthropic keeps API data only as long as its privacy policy for API users says.
  • Stripe: the payment provider for kit orders (the checkout page).
  • Resend: sending e-mail.
  • BuyMeBricks, our parts supplier: to price a kit and check stock we send the country, postal code and city of the delivery address, and the parts list.

When you publish a model to the community feed, its pictures, model, title, description, tags and your display name become visible to other people in the app. You can take it down again from the Share screen.

Where your data is kept

Our servers and storage are in the Frankfurt region of Amazon Web Services, in the EU. Some of the providers above (Google, Apple, Stripe and Resend) may process data in other countries, including the United States. The content-policy check of your photos and typed text runs in Frankfurt too. Anthropic (which receives photos for the model’s short name only), OpenAI and Modal process data in the United States.

How long we keep it

We keep your data for as long as your account exists. When you delete your account, this is what happens:

  • Your account is anonymised at once: your e-mail address and display name are erased and the sign-in link to your Apple, Google or e-mail identity is removed. Signing in again later creates a new, empty account; it does not bring the old one back.
  • Deleted at once: your saved delivery address, your phones’ push tokens, the authors you blocked and blocks that name you, and every model you published (they leave the community feed).
  • Unpaid kit orders are cancelled and their delivery addresses cleared.
  • Kept: paid kit orders, including those being packed, shipped or refunded, with their delivery address, because a kit on its way still has to arrive and orders are accounting records (tax, refunds and chargebacks). The records of what you bought and our cost records are kept too, linked to the anonymised account.
  • Kept: reports you filed, and reports about your models, as moderation evidence, linked to the anonymised account.
  • Not deleted yet: your photos and generated models. They stay in our storage, no longer linked to your e-mail address or name. An automatic purge of them after a retention period is planned but not built yet.
  • A build that is running when you delete your account finishes; its results are kept the same way.
  • The delivery address of a paid kit stays with the order after it ships. Clearing it some months after shipping is planned but not built yet.
  • Deleting your account does not cancel a subscription. Cancel the Builder membership in your Apple Account settings.

Other retention:

  • Server logs are kept for up to 90 days.
  • Backups: database backups are kept for up to 35 days, and earlier versions of stored files for 30 days, so deleted data can remain in backups for that long.
  • The notification log (which notification went out, when, and whether it was delivered, without a token or address) is kept.
  • Support e-mails: [retention period to be confirmed].

Your rights

Wherever you live, you can ask us for a copy of your data, to correct it or to delete it, and you can delete your account yourself at any time. Many of your files (the instructions, the parts list, the wanted list and the model file) can be downloaded from the app.

In the EEA, the UK and Switzerland you also have the right to restrict or object to our use of your data, to receive the data you gave us in a machine-readable format (portability), to withdraw consent at any time, and to complain to your data protection authority.

In California and other US states with privacy laws, where those laws apply to us, you have the right to know what personal information we collect and how we use it, to access, correct and delete it, and not to be treated differently for using these rights. We do not sell your personal information and do not share it for cross-context behavioural advertising.

To use any of these rights, write to support@dreamabrick.com from the e-mail address on your account, so we can be sure the request is yours. We answer within one month.

Children

Dream-a-brick is not meant for children under 13, or under 16 in the EEA and the UK. We do not knowingly collect personal data from them. If you believe a child has given us personal data, write to us and we will delete it.

Security

Everything travels over encrypted connections. Our database and file storage are encrypted at rest, and the app reads and writes your files only through links that expire after 15 minutes.

Changes to this policy

When we change this policy we update the date at the top of the page. If a change matters to how we use your data, we will tell you in the app or by e-mail before it takes effect.

Contact

[Legal entity name], [postal address] . E-mail: support@dreamabrick.com.

Dream-a-brick

One photo in. A brick model out, with every step it takes to build it.

Product

  • Home
  • Styles
  • FAQ

Help

  • Support
  • Delete your account

Legal

  • Privacy
  • Terms

LEGO® is a trademark of the LEGO Group, which does not sponsor, authorize or endorse this site.

© 2026 Dream-a-brick. All rights reserved.