Privacy policy

• Account information: your email address, and the display name and avatar that come from the Google account you sign in with, along with account identifiers and session information.
• Prompts and reference images: the text you type and any image you upload to generate a build, along with the settings for the run.
• Builds and generated output: the generated models, voxel data, block palettes, thumbnails, titles, descriptions and tags for builds you save, plus the previous revision of a build you have edited.
• Generation records: for each run, metadata such as the timestamp, the mode, its status, and the generations it reserved and settled.
• Billing records: the customer and checkout identifiers issued by our payment provider, which pack was bought, and the resulting balance and slot changes. Our payment provider is the merchant of record for the sale, so it is that provider — not us — that holds the billing and tax details you enter at checkout. We never see or store full card numbers.
• Usage and device data: IP address, browser type, pages viewed, referring URLs, approximate location derived from IP, timestamps, feature usage and diagnostics.
• View and download counts: when a build is viewed or downloaded we record the event against the build. To count each visitor once per hour without keeping a log of who visited what, the visitor is reduced to a salted, server-side hash. If you are signed in the event is also associated with your account.
• Support communications: emails, bug reports and other correspondence you send us.

• Provide, operate, maintain and secure the Services.
• Create and manage accounts, authenticate you, and keep you signed in.
• Run generations, store the results, and publish or withhold them according to the visibility you chose.
• Screen prompts and published build metadata for content that our policies prohibit.
• Meter generations, maintain balances and slots, reconcile payments, and detect abuse or anomalous usage.
• Analyse usage, diagnose errors, and improve the product.
• Communicate with you about service issues, support, security and administrative matters.
• Enforce our Terms of Service, investigate fraud, and comply with legal obligations.

Generating a build sends your prompt, and any reference image you uploaded, to our 3D generation provider and to the model provider behind AI building and content screening. Those providers process the content to produce or screen a result and are bound by their own terms and privacy policies. Do not put anything in a prompt that you would not want processed by a third-party model provider.

Generated models, voxel data and thumbnails are stored on our infrastructure so they can be shown, downloaded and re-edited. Work you only open in the studio without saving stays in your browser.

Builds you save are public by default: they appear in the community gallery with their title, description, tags, thumbnail and your display name, and anyone can view, download or remix them. A build only appears in the gallery once it has been reviewed. Private builds, up to the number of slots your packs have added, are not visible to other users. Prompts, billing records and account details are never published.

Our moderators can view any build, including private ones, so that we can act on reports and keep prohibited content off the service. We only do so for moderation, safety and support.

If you are in the United Kingdom or the European Economic Area, we rely on the following bases under the UK and EU GDPR:

• Performance of a contract: creating and maintaining your account, running and delivering generations, storing your builds, and metering the packs you have bought.
• Legitimate interests: keeping the Services secure, preventing fraud and abuse, screening content, measuring traffic and feature usage, diagnosing errors and improving the product. We balance these against your rights.
• Consent: where we ask for it, such as optional communications. You can withdraw consent at any time, without affecting processing carried out beforehand.
• Legal obligation: retaining billing records and meeting tax, accounting and other regulatory requirements.

We use cookies and local storage to keep you signed in and to remember your preferences. We do not use them to track you for advertising, and we do not set advertising identifiers on your device.

We use a third-party analytics provider to measure traffic and understand how the Services are used. It is configured with memory-only persistence, so it does not write a cookie or a local-storage identifier that would follow you between visits.

• Service providers: the vendors that run the Services for us — authentication and database hosting, file storage and delivery, payment processing, 3D generation, the models behind AI building and content screening, and analytics. Each processes information only to provide its part of the Services. We will name the providers we currently use if you ask us at structmatic@gmail.com.
• Public and user-directed sharing: content you publish is visible to other users and the public.
• Legal and safety disclosures: to comply with the law, respond to lawful requests, protect rights and safety, investigate misuse, or enforce our agreements.
• Business transfers: information may transfer as part of a merger, acquisition, financing, reorganisation or sale of assets.

We do not sell personal information.

We keep information for as long as reasonably necessary to provide the Services, resolve disputes, enforce agreements and meet legal obligations. Builds, prompts and generation records are kept while your account is open; billing records are kept for as long as tax and accounting rules require. Deleting a build removes it and its stored files. To delete your account and the content attached to it, email structmatic@gmail.com — account deletion is handled manually.

We and our providers may process information in countries other than the one you live in. By using the Services you understand that your information may be transferred to and processed in jurisdictions with different data-protection laws.

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or port your personal information. To make a request, contact structmatic@gmail.com. We may need to verify your identity first.

If you are in the United Kingdom or the European Economic Area you also have the right to complain to your local data-protection authority — in the UK, the Information Commissioner’s Office (ico.org.uk). We would appreciate the chance to put things right first.

The Services are not directed to children under 13, we do not permit them to create an account, and we do not knowingly collect personal information from them. Where the law where you live sets a higher minimum age for consenting to online services — parts of the European Economic Area set it as high as 16 — that higher age applies instead.

If you are under 18, you may use the Services only with the permission and supervision of a parent or guardian, and packs may only be bought by someone aged 18 or over. Generating a build sends your prompt and any reference image to third-party AI providers, whose own terms may set their own age limits.

If you believe a child has given us personal information, contact structmatic@gmail.com and we will delete the account and the information attached to it.

We use reasonable administrative, technical and organisational measures to protect information, but no method of transmission or storage is completely secure. You are responsible for protecting your credentials and your devices.

We may update this policy from time to time. The updated version is posted here with a revised “Last updated” date, and continuing to use the Services after it takes effect means the updated policy applies.

Questions or requests about this policy or our data practices go to structmatic@gmail.com.