Privacy Policy
1.The short version
- To use the builder you create an account. We store your email address, your name if you give one, your password as a one-way hash we can’t read, and when you agreed to our terms.
- The builder runs in your browser. Your personal workflows, run history and API keys stay on your device. Business agent configuration is stored on our server and shared with current members.
- Calls using your own Connection keys go directly from your browser to the services you choose. Enabled calls on Breadboard-funded AI go through our server, and business calls are attributed to the requesting member.
- If you join the waitlist or the email list on our free tools, we store your email address and the page you joined from. We use it to tell you when paid plans open and to send occasional updates about new templates, prompts, tools and models, no more than once a month. Reply to any email, or write to us, and we take you off the list.
- If you create an account through someone’s invite link, we record which link you used, so the person who shared it can see how many people joined through it. They see a number, not who you are.
- Our free tools (the token counter, model picker and others) run in your browser. What you type into them is not sent to us.
- We do not sell your personal information, and we do not use advertising trackers.
2.Who is responsible
Breadboard Studio is run by Cohen Michael Gleason Stewart, a sole proprietor in Wichita, Kansas, USA, doing business as Breadboard Studio, who is responsible for the personal information described here. Contact: breadboardstudio@gmail.com.
3.What stays on your device
Personal and business workspaces. Personal boards stay on your device. A business workspace on a server-confirmed Studio or Agency account stores shared agents, instructions, notes, wiring and project definitions in our Cloudflare D1 database so current members can see and edit them. Personal agents are copied there only when you choose to share a separate copy. Connection keys, pinned data, run contents and memories are not synchronized to teammates. Known embedded keys and authentication headers are rejected, but you must still keep secrets out of free-text instructions. Essential browser caches are separated by signed-in account and workspace. A teammate's changed board asks you to review and trust it before execution.
Your browser keeps local copies of these; only business configuration is also synchronized as described above:
- your workflows and their settings;
- run history, including what went into and came out of each part;
- API keys you add on the Connections page;
- your name, if you enter one, and preferences such as light or dark mode.
We cannot recover personal browser-only records. Clearing browser data removes local copies, not shared server records. The personal workspace reset applies only to that account on this device. Business agents are removed separately; backups exclude Connection keys.
Share links. When you share a board, its parts, wires and notes are packed into the link itself, after the # in the address. Browsers don’t send that part of an address to our server, so we don’t receive the board. Anyone you give the link to can read everything typed into the board’s parts. Keys saved on the Connections page, run history and pinned data are left out of the link.
4.What your workflows send to others
When you run a workflow, your browser sends requests straight to the services it calls, such as an AI provider, a data API or an MCP server, along with any keys and data the workflow includes. Those services receive that data under their own privacy policies, not this one. Check them before sending anything sensitive.
5.What we collect
Business records. We store the business name, owner and member IDs, roles and join times; invitation email addresses, expiry and acceptance/revocation records; shared agent configuration, creator/editor IDs, revision numbers and timestamps; and action-only audit metadata. Invitation tokens are hashed; links expire after seven days and are shown once. No invitation email is sent automatically.
Funded AI usage. When enabled, calls on Breadboard's own keys go through our server to the configured AI provider. We retain model/tool, time, input/output token counts when provided, status, allowance cost or a reservation hold, and the requesting member, business and shared agent IDs. Reports use these records and make no AI call. The owner can see members' business usage by person, agent and model, including names and email addresses. Personal agent content and personal usage rows are not exposed in the business report. Owner personal funded calls and business calls use the same existing funding ceiling, so private owner spending can affect the business's remaining allowance. Samples and calls on a member's own key are excluded from funded reports.
- Your account. Your email address; your name, if you give one; your password, stored only as a salted one-way hash, so we never see it; which version of the Terms and this policy you agreed to, and when; and your sign-ins (a hashed sign-in code and when it expires). When a log-in fails, we record the email address tried and the time, to slow down password guessing.
- Waitlist. Your email address, the page you signed up from, and when you signed up.
- Server logs. Our hosting provider records basic request data, such as IP address, browser type and the pages requested, to keep the site running and secure.
- Emails you send us. Whatever you choose to include.
When paid plans launch, we will also collect billing information through our payment provider, and we will update this policy before that happens.
6.How we use it
- to create and run your account, keep you signed in, and protect accounts from password guessing;
- to tell waitlist members when paid plans open, and about the waitlist discount, and to send list members the occasional updates they signed up for;
- to count signups that came through each invite link;
- to run, secure and fix the website;
- to answer you when you contact us;
- to meet legal obligations.
Where laws such as the GDPR apply, our legal bases are performing our agreement with you (your account), your consent (waitlist), our legitimate interests (running and securing the site) and legal obligation.
7.Who we share it with
We share personal information only with providers that help us run the Service, under agreements that limit their use of it:
- Cloudflare hosts the website and our database, which holds accounts, the waitlist and the business/usage records described here.
- Google Fonts serves the site's fonts, so your browser requests them from Google, which receives your IP address.
The site has no configured email-sending provider. Any provider added to send waitlist emails will be identified here before receiving those addresses.
We may also disclose information when the law requires it, or as part of a merger or sale of the business, in which case this policy continues to apply.
8.Cookies
We use one strictly necessary cookie, to keep you signed in, and your browser’s local storage for the builder data described above and to remember your theme. We do not use advertising, analytics or tracking cookies. Our Cookie Policy lists each one.
9.How long we keep it
Business retention is an owner-review item. Shared boards removed in the app are soft-deleted for operator recovery. Membership, invitation, audit, policy-acceptance and funded-usage records do not yet have automatic retention cleanup or a business-deletion worker. The operator must set and implement reviewed periods and handle database backups and independent provider records before enabling business workspaces publicly. Removing a member ends server access; it cannot erase information already downloaded to that member's device.
Account details are kept while your account is open, and deleted within 30 days after you ask us to delete the account. Sign-ins expire after 30 days, or when you log out. Failed log-in records are deleted after a day. Waitlist emails are kept until paid plans launch and for up to 12 months after, or until you ask us to delete them. Server logs are kept for a short period set by our hosting provider.
10.Your choices and rights
You can ask us to access, correct or delete your personal information, or to stop emailing you, by writing to breadboardstudio@gmail.com. Every email we send has an unsubscribe link. Depending on where you live, for example in the EU, UK or California, you may have further rights, including the right to complain to your data protection authority. We will not treat you differently for using your rights.
11.Security
We use HTTPS for the whole site, store passwords only as salted hashes, keep the sign-in cookie out of reach of page scripts, and limit access to our database. No system is perfectly secure. Because API keys are stored in your browser, only add them on a device you trust.
12.Children
The Service is not meant for children under 16, and we do not knowingly collect their information. If you believe a child has given us personal information, contact us and we will delete it.
13.International transfers
Our providers may process data in the United States and other countries. Where required, we rely on safeguards such as standard contractual clauses.
14.Changes
We will update this policy as the Service changes, especially before billing launches. We will change the date at the top and tell waitlist members and account holders about significant changes.