Privacy policy

What this policy covers

It covers the website and the hosted app at infill.build, including the MCP server your coding agent connects to. It doesn't cover copies of Infill that someone else runs: Infill is open source, and if you or your company host it yourselves, whoever runs that copy is responsible for the data in it. A self-hosted copy sends nothing to us.

What we collect

Your account

Your name, email address and password, which we store only as a secure hash. If you sign in with GitHub or Google, we receive your name and email address from them, and we don't get your password for those services.

Your projects

Everything you or your agent create in Infill: model files, every saved version, renders, exports, printer profiles, and links you make to parts of a model. We store this so we can build, show and export your projects for you.

What your agent does

When you connect a coding agent, it signs in as you, and we keep a record of the tools it calls on each project and what they did, so it can catch up on what changed and you can see what it did. We don't see your conversation with your agent, only the calls it makes to Infill. We also store the sign-in tokens your agent uses.

Technical data

Like most websites, our servers log requests: your IP address, browser, the page or API called, and when. We use these logs to keep the service running and secure.

Visits to our website

We count visits to the public pages of infill.build with Umami, an analytics tool we run on our own servers. It records the page and its title, the site you came from, your browser, operating system, device type, screen size and language, and your approximate location, worked out from your IP address. It sets no cookies, doesn't keep your IP address in its records, isn't linked to your account, and doesn't run in the app.

What we don't do

• We don't sell your personal information or share it for advertising.
• We don't use advertising trackers, or analytics in the app.
• We don't sell your designs or publish your private projects.
• Running Infill doesn't involve sending your designs to AI providers. Your coding agent reads and writes your projects through our MCP server; what your agent does with them is covered by your agreement with its provider.

Cookies and storage in your browser

We set one cookie when you sign in, to keep you signed in. The app also stores a few interface preferences in your browser, such as whether panels are open. Neither is used for tracking, and our website analytics use no cookies.

How we use your information

• To run Infill: sign you in, build, render and export your projects, and connect your agent.
• To keep it secure, prevent abuse, and fix problems.
• To improve and develop Infill, including training and improving AI models, using your projects and the record of what your agent does. This is part of using Infill and can't be turned off; see our terms. If you don't want your designs used this way, you can run Infill yourself: it's open source, and a copy you host sends nothing to us.
• To contact you about your account or important changes to the service.
• To meet legal obligations.

Who we share it with

• The companies that host our servers and store our backups, only so they can provide that service to us.
• E2B, whose isolated sandboxes run your model code and hold your model files, to build and export your projects.
• Cloudflare, which sits in front of infill.build and passes along everything sent to and from it, to deliver and protect the service.
• Companies that help us train or run AI models, only to do that work for us and not for their own purposes.
• GitHub or Google, if you choose to sign in with them.
• The coding agent you connect, which reads and changes your projects because you asked it to.
• Anyone you give an export link to. Export links contain a random token, need no sign-in, and stop working after 24 hours.
• Authorities, when the law requires it, and a buyer or successor if Infill or its operator is ever sold or reorganized.

How long we keep it

We keep your account and projects until you delete them or ask us to. Server logs are kept for a limited time and then deleted. We delete a project's sandbox when you delete the project, and otherwise within about a week of its last use. Backups can hold deleted data for a short while longer before they're replaced. Deleting your data doesn't undo improvements or AI models we've already built with it.

Your choices and rights

You can export your designs from the app at any time. To get a copy of your data, correct it, or delete your account and everything in it, email [email protected] from the address on your account. Depending on where you live, for example in California, the EU or the UK, you may have further rights, such as to object to how we process your data or to complain to a data protection authority. We'll answer within 30 days.

Do Not Track

Since we don't track you across sites, there's nothing for a Do Not Track signal to switch off.

Children

Infill isn't meant for children under 13, and we don't knowingly collect their information. If you think a child has signed up, tell us.

Where your data is

Infill is run from the United States, and your data is stored there.

Security

We protect your data with encryption in transit, hashed passwords and limited access. No service is perfectly secure; if something goes wrong that affects your data, we'll tell you.

Changes

If we change this policy, we'll update the date at the top. If a change matters, for example new kinds of data or new places we send it, we'll tell signed-in users before it takes effect.

Contact

Questions about privacy: [email protected]. See also our terms of service.