Last updated 12 November 2026.
This says what Daedal keeps about you, where it is kept, who else sees it and what you can do about it. It describes what the product does today. Questions: contact@daedal.build.
Personal details such as addresses stay out of your project files: a build names an address only by its label. We do not hold your card number.
On servers run by Amazon Web Services: your builds and folder are on a disk (EFS) that belongs to your account's folder, sign-in is handled by AWS Cognito, and email goes out through Amazon SES. Server logs are kept for 7 days and disk snapshots for 35 days. A nightly copy of the service’s data is kept for up to 65 days. Everything you do is also in the journal of the build you did it in.
Only when you, or Ariane on your behalf, run something that needs it:
| Who | What | Why |
|---|---|---|
| Amazon Web Services | everything stored on the service, and your email address and each email we send | hosting, sign-in, backups, email |
| Anthropic | your conversation with Ariane, the build's requirements, and the results of the tools Ariane runs, including file contents; photos and PDFs you use to list your parts | the model behind Ariane |
| Mistral | the audio of a recording you make to list your parts; not kept by Daedal | turning speech into text, only if you use it |
| Stripe | the amount and a description; your card goes to Stripe's own page | taking payment when payments are on |
| Cloudflare | the messages you send to contact@daedal.build, and notes from the "Tell us what you think" box, which also go to that address | our domain, and forwarding that address to the mailbox of the people who run Daedal |
| Makers and suppliers you order from | the design files, quantity and options; for an order you approve, your ship-to address and email | making and delivering your order |
| Parts shops | the part searched for; for store stock, your ZIP code | "Where can I get it now?" |
We only send what a job needs. The companies above act on our instructions and under their own terms. Your own board or printer gets commands and files from you directly, over your own network.
Ariane reads your build to help with it. Data goes to the model provider only while Ariane works on your request. We do not use your builds to train models, and we do not ask the providers to.
A build, your portfolio and your posts are public only when you publish them, and then anyone with the link can open the page, signed in or not. Published photos have their location data removed. A shared build's "Make one like this" recipe holds the idea, approved requirements and designs, never addresses, ZIP codes, measurements of your spaces, the journal or evidence. Unpublish at any time.
Emails about your own orders, receipts and what waits for you come because they are part of the build. "Mentions and remixes" can be turned off; the weekly summary is off unless you turn it on. Both have one-click unsubscribe. We keep a one-way hash of addresses that bounced for good or reported spam, so nothing is sent to them again.
Daedal is for people 13 and older. Under 18 you need a parent or guardian's permission to use it, and a parent decides about any payment. If we learn that a child under 13 has an account, we delete it. If you are a parent and think this has happened, write to contact@daedal.build.
One cookie keeps you signed in (signed, with your id and sign-in time) and short-lived cookies carry the sign-in itself. We use no cookies for tracking or advertising.
Access tokens and device tokens are stored only as hashes, passwords are never seen by us (the sign-in provider holds them), and approvals for orders and machine jobs can only be given by you. No system is perfectly safe. If something that affects you goes wrong, we will tell you.
If this changes in a way that matters, we will say so in the app or by email, and the date at the top changes.