Privacy Policy

Last updated 3 October 2026

This page describes what Machinae Build collects, why it is collected, who it is shared with, and how to have it removed. It is written to match what the software actually does rather than to cover every eventuality.

1. Who we are

Machinae Build is developed and operated by Elena Denezhkina, who holds the copyright in it. We are the data controller for the information described here.

2. What we collect

Information you give us

• Email address — required to create an account and to send you your designs.
• Phone number — required before generating a design, so that a supplier or our sales team can reach you about a quote.
• Name and company — optional, used to address you properly.
• Your building descriptions and designs — the text you type and the specifications produced from it, so you can return to them later.
• A record of each generation, for 90 days — separately from any design you choose to save, we keep what was asked for and what the software made of it, so that a building that comes out wrong can be diagnosed and the fault fixed. Contact details are stripped out of the description before it is stored: an email address, a phone number, a street address, a postcode or a web address is replaced by a marker. Sizes, materials and colours are kept, because they are the thing being checked. After 90 days the description and the design are deleted and only counts and error signatures remain, which name no request and no person.
• Password — if you sign up with email and password, it is stored only as a salted hash. If you sign in with Google or GitHub, we never see a password at all.

Information collected automatically

• IP address and browser user-agent — recorded with your signup, to attribute the lead and to detect abuse of the free tier.
• Server and request logs — including crawler visits, kept for diagnostics.
• Which site sent you — if you arrive from a search engine or an AI assistant, we record the site's name only: google.com, claude.ai, chatgpt.com. We deliberately do not keep the rest of that address, because it often contains the words you typed into the search box or the identifier of your conversation. We store which door you came through, not what you asked to get here.
• A session cookie (better-auth.session_token) — strictly necessary to keep you signed in. It is HTTP-only and same-site.
• A free-tier cookie (anon_id) — a random identifier, set before you have an account, so the five free designs are counted against somebody. It is not linked to a name or an email, because at that point we have neither. It lasts a year.
• Approximate location from your IP — only if you allow it. The configurator can ask a third-party service (ipapi.co) roughly where you are, to prefill the build site on a quote. It is off unless you say yes, and saying no changes nothing else.
• Which pages you visited — only if you allow it. Google Analytics counts page views: the page, the time, the approximate region, and the site or search that sent you. It is sent to Google, who set two _ga cookies for it, and your IP is truncated before it is stored. It is off unless you say yes — the tag is not fetched at all — and it is used to decide which pages are worth keeping, never for advertising.

We do not use advertising cookies, we do not sell or share personal information, and the site loads no fonts, stylesheets or images from anyone else's servers. Exactly two requests can leave for a third party — the location lookup and the analytics tag — and both are off until you say yes, which is why they are the two things you are asked about. The cookie page lists every cookie and every stored value in full, with where to click to see and delete them yourself.

3. Why we use it

• To provide the design and code-checking service you asked for (performance of a contract).
• To contact you about a design or a quote you initiated (legitimate interest, and consent where required).
• To enforce the free-design allowance and prevent abuse (legitimate interest).
• To keep the service secure and diagnose faults (legitimate interest).
• To find out why a design came out wrong and to correct the software (legitimate interest). This is the 90-day generation record above. It is not used to build a profile of you, and it is not shared.

We do not sell your personal information, and we do not share it for cross-context behavioural advertising.

4. Who it is shared with

• Our AI model provider. The text you type to describe a building is sent to the model provider that generates the design. It is processed to return your result. Your email, phone number and password are never sent as part of that request. The provider is named, with everyone else who processes data on our behalf, on Sub-processors.
• Our CRM, if enabled. Where a deployment has CRM delivery switched on, your contact details and design interest are forwarded to that system so that sales can follow up. An enquiry made inside a builder's embedded configurator is the exception: it is theirs, it is never sent to our CRM, and it is kept and deleted on their instruction.
• Authentication providers you choose. If you sign in with Google or GitHub, that provider confirms your identity to us.
• Nobody else, except where we are legally required to disclose, or as part of a business transfer in which this policy continues to apply.

5. How long it is kept

Account details and saved designs are kept for as long as your account exists, and removed when you ask us to delete it. Server logs are kept for operational diagnostics and rotated. If you ask us to delete your account we remove your personal information; anonymous, aggregated counts that cannot identify you may remain.

The generation record described in section 2 is kept for 90 days and then emptied automatically: the description and the design are deleted, and what remains is the outcome, the timestamp and a one-way fingerprint of the description, which cannot be turned back into what was typed. The one exception is a record somebody here has reviewed by hand and corrected, in order to stop the same fault happening again; those are kept until the fault is fixed, and only ever in the redacted form. You can ask us to delete yours sooner using the contact page.

If you used the configurator embedded on somebody else's website, the words you typed are not stored by us at all — only their length and a one-way fingerprint. That business is the data controller for their own enquiries; see section 4.

6. Your rights

Depending on where you live — in particular under the UK GDPR, the EU GDPR and the CCPA/CPRA — you may have the right to access a copy of your data, to correct it, to delete it, to restrict or object to its processing, to portability, and not to be discriminated against for exercising any of them.

To exercise any of these, use the contact page. We will respond within the period the applicable law allows. You also have the right to complain to your data protection authority.

7. Security

Passwords are stored hashed, never in the clear. Session cookies are HTTP-only, same-site, and marked secure in production. Administrative surfaces answer 404 rather than 403 to anyone not entitled to them, so their existence is not confirmed to a stranger. No system is perfectly secure, and we do not claim otherwise.

8. Children

This is a tool for commercial construction buyers. It is not directed at children, and we do not knowingly collect information from anyone under 16.

9. International transfers

Our service providers may process data outside your country. Where that happens we rely on the transfer mechanisms the applicable law provides.

10. Changes

If this policy changes materially we will update the date at the top and, where the change affects you, tell you directly.

11. Governing law

This policy is governed by the law of the State of Delaware, United States.

One thing that clause cannot do, and it is worth saying rather than leaving you to assume it: a privacy statute applies because of who we are, where we are and how much data we handle, not because a policy named a State. Your own law may give you rights this policy does not name; it still gives them to you.

We are established in Mexico, in the State of Jalisco, and post reaches us at Colonias 362, Guadalajara, Jalisco, Mexico. The service runs in the United States.