Privacy Policy

---

1 · Who is responsible

The controller of your personal data is:

Builds is a Digital One product. There is no separate Builds company. The company is Irish, with people in Dublin and Budapest. The GDPR and Ireland's Data Protection Act 2018 apply.

Data Protection Officer. We have not appointed one: the GDPR requires one only for large-scale monitoring or large-scale special-category data (Art. 37), and Builds does neither. Write to info@digital1.one and a person who can answer reads it.

Teams. If your organisation uses Builds, for the organisation's own data (what its members do on the organisation's machines, its keys, its knowledge) the organisation decides and we act for it. See §9.

---

2 · The short version

• We never receive your AI credentials. You sign in to Claude, ChatGPT/Codex, Grok and the rest on your own machine, with the vendor's own tool. API keys are stored on that machine, encrypted; one you type in the app is sealed to that machine on your phone, and our server cannot open it.
• We do not store your conversations. They live on your machine. While you watch one from the app, it passes through app.builds.one on its way to you and is not written to our disk. Section 4 lists the small exceptions (a notification's first words, a document's title, your own instructions).
• Your prompts and code go from your machine straight to the AI vendor you chose, under your account and that vendor's terms. We are not in that path (except for a team's own key, §9).
• We keep: who you are (Digital One account id and email), your devices and machines, your settings, and counts of use.
• Crash reports and usage counts go to PostHog in the EU only if you say yes. They never carry a message's words, a file's name or a path.
• We do not sell data, show ads, or train any model on your data.

---

3 · Where your data lives

Said plainly: our server can reach your linked machines. A machine you link to your account does what comes over that link from your account (start a turn, answer a question, make a desk). We use that path only to carry what you do in the app, and we never read your machine's files on our own initiative. But the possibility exists, so we say it, and the security page says how we guard it. To close it for a machine, unlink it; Builds keeps working there from the terminal.

---

4 · What we process, why, on what basis, and for how long

The bases are Article 6(1) GDPR: (b) to provide the service you asked for (our contract with you), (c) a legal obligation, (f) our legitimate interests (named in the row), (a) your consent.

What we do not have. Your code, your files, your conversation history, your AI credentials or API keys, your payment details. Builds itself has no payment: a DispatChai residence is paid through DispatChai, under DispatChai's own terms and privacy policy.

Do you have to give us this? Your Digital One account id and email are needed to use Builds: we cannot tell your machines apart from anyone else's without them. Everything else is created by using the product. Crash reports and usage counts are optional: we ask first, and saying no changes nothing else.

Automated decisions. We make none that have legal or similarly significant effects on you. Some checks are automatic: a pairing code typed wrong too often locks for 15 minutes; a spending cap stops a turn; an invitation is refused over a daily limit. Write to us and a person looks.

---

5 · Crash reports and usage counts

The app (iPhone, iPad, Android preview, web) can send crash reports and usage counts to PostHog, in PostHog's EU region (Frankfurt, Germany). It asks you first, on each device. Until you say yes, it sends nothing to PostHog and keeps no PostHog id on your device. Saying no changes nothing else in the app.

What goes, if you said yes: a random id made on your device (not your account), the app's version and platform, the screens you open by their shape (/s/:id, never the conversation's id or name), the app's start and stop, errors and crash reports with the program's own stack (component and file names of our code). On the web it goes through app.builds.one, which passes on your network address as a direct call would; PostHog discards it (our project's "Discard client IP data" setting is on).

What never goes: a message's words, a file's name, a path, a machine's or desk's name, your email, your account id. We do not create a profile of you in PostHog and we do not link its events to your account.

Changing your mind: Settings → This device → Share crash reports and usage counts. It is off until you say yes, and you can switch it off, or on again, at any time. Switching it off stops anything more being sent and removes PostHog's id from the device.

---

6 · Who else receives data

We keep the list short, and every recipient is named on the sub-processor list with what it gets and where.

We disclose personal data to anyone else only when the law requires it (a valid order from a court or authority), or to establish or defend a legal claim.

Transfers outside the EEA. Two of our processors are US companies that handle data outside the EU: Resend (stores invitation mail in the US) and Cloudflare (in front of the sign-in). Both are certified under the EU–US Data Privacy Framework, which the European Commission found adequate on 10 July 2023 (Decision (EU) 2023/1795); their contracts with us also include the Commission's Standard Contractual Clauses. PostHog's EU region keeps the data in the EU, and PostHog's contract with us includes the Standard Contractual Clauses for any access from the US. Write to us for a copy of the safeguards.

---

7 · The AI vendors: what leaves your machine

When an agent works, your machine sends your prompt and the code it reads to the vendor that runs the model: Anthropic (Claude), OpenAI (Codex), xAI (Grok), Google, Mistral, or whoever you pick. That is what a coding agent is.

• You sign in on your machine with the vendor's own tool (claude, codex, grok) or add your own API key. Builds uses a subscription only through the vendor's official tool.
• The vendor is not our processor. It processes your data under your agreement with it, as a controller in its own right (or as your processor, on a business or API plan). Its terms decide retention and whether your data trains its models. Read them; some let you switch training off.
• We are not affiliated with those vendors, and we do not see what passes between your machine and them.
• If your code contains other people's personal data, sending it to a vendor is your processing decision.

Where each vendor says what it keeps and whether it trains on it (as read on 2026-10-04; check them, they change):

---

8 · How long, in one place

The "How long" column of §4 is the rule. In short: most of it while you have an account, plus at most 7 days in our backups after you delete it. A few things follow their own clock, and §4 says which: usage totals (24 months, and gone with your account), the records of removed machines, invitations and organisation events (12 months after the event, with your address removed when you delete your account), invitation emails at Resend (30 days), and your messages to us (2 years after the last one). What we must keep by law (for example a record of a legal request) is kept as long as that law says.

---

9 · Teams (organisations)

• An organisation is created in Builds and kept in Digital One's suite, which Gateward and SkilledMind share.
• On an organisation's machine, each member gets a separate space (a separate Unix user). Other members cannot read it. The machine's administrator can: whoever runs a machine can read everything on it. The app says so, with the administrator's address, before you make your space.
• An organisation's key (through Gateward, a Digital One product): a desk you put on it sends its prompts through Gateward to the model vendor under the organisation's account, and Gateward records the use and cost for the organisation's caps.
• An organisation's knowledge (SkilledMind, a Digital One product): if the organisation turned it on, a desk can read the organisation's shared knowledge, and, where its "learn" switch is on, send a summary of a finished conversation into it, where the organisation's members can find it.
• For these, the organisation decides and we act on its behalf, under a data processing agreement we offer every organisation (Terms §12). Its own policies apply to you as a member; ask its administrator.
• The organisation's owners and admins see the members, their roles, the seats (whose, state, number of desks) and the log of organisation events. They do not see your conversations.

---

10 · Your rights

You have the right to:

• access your data and get a copy;
• correct it;
• delete it (§11 says how, from the app);
• restrict our processing while a question is settled;
• portability: the data you gave us, in a machine-readable file;
• object to processing based on our legitimate interests, and to any direct marketing (we send none);
• withdraw consent at any time where we rely on it (crash reports and usage counts: Settings → This device → Share crash reports and usage counts; the sign-in page's own analytics: Analytics settings on that page), without affecting what was done before.

How: write to info@digital1.one from your account's address, or use the app (Settings → Delete account). We answer within one month (two more for a complex request, and we tell you why). It is free. We may ask you to confirm it is you; signing in is usually enough.

Complaints. Tell us first, please. You can also complain to a data protection authority:

• Ireland (our lead authority): Data Protection Commission, 6 Pembroke Row, Dublin 2, D02 X963, Ireland · +353 1 765 0100 · complaints in writing at forms.dataprotection.ie/contact · www.dataprotection.ie
• Hungary: Nemzeti Adatvédelmi és Információszabadság Hatóság (NAIH), 1055 Budapest, Falk Miksa utca 9-11 (post: 1363 Budapest, Pf. 9.) · +36 1 391 1400 · ugyfelszolgalat@naih.hu · cases are started at naih.hu/online-ugyinditas, not by email · www.naih.hu
• or the authority where you live or work, or where you think the breach happened (Art. 77 GDPR).

You may also go to court (Art. 79 GDPR): in Ireland, or in the country where you live (in Hungary, the regional court — törvényszék — for where you live).

---

11 · Deleting your account

From the app: Settings → Delete account. The full description of what is removed and what stays is on the account deletion page. In short:

• your Builds account, and what §4 lists about you, goes from app.builds.one at once, and every device is signed out; the records other people keep stay as theirs (an invitation someone sent you keeps the address they sent it to; an organisation's log names your account id, not your email) until each is deleted 12 months after the event;
• backups age out within 7 days;
• your machines keep their own data, which only you can remove;
• a free DispatChai residence you got by invitation ends: it is stopped, kept 7 days, then removed; a paid one is closed in DispatChai;
• if you are the only owner of an organisation, or you linked an organisation's machine that other people work on, the app asks you to hand it over first;
• your Digital One account stays. It is the sign-in Digital One's other products share. Delete it at digital1.one, or write to info@digital1.one.

---

12 · Security

The server holds no AI credential. Secrets it must hold (a linked DispatChai sign-in, a FrontierScore key) are encrypted with a key kept outside the data. Device tokens and machine credentials are kept only as hashes. Risky actions ask for Face ID or a second press. Everything travels over TLS. More on the security page, and how to report a weakness.

If a breach puts your rights at risk, we tell the Data Protection Commission within 72 hours and you without undue delay where the risk to you is high.

---

13 · Children

Builds is not for children. You must be at least 18 to use it. We do not knowingly collect data from anyone younger; if you think we have, tell us and we delete it.

---

14 · Changes

When we change this policy, we update this page and its date. If a change matters to how your data is used, we tell you in the app or by email before it takes effect. Earlier versions are available on request.

---

15 · Contact

info@digital1.one · Digital One Technology Consulting Limited, 6-9 Trinity Street, Dublin 2, D02 EY47, Ireland.