# Protoboard Privacy Notice

- Last updated: 27 October 2026
- Related: the
  [Protoboard Terms of Service](https://protoboard-cloud.web.app/terms)

## 1. Who we are

1.1. Delta Robotics, Inc., a Texas corporation ("Delta", "we"), runs Protoboard's hosted service:
the part library and its API, the sign-in pages and the downloads site (the
"Service"). This notice says what the Service receives about you and what
happens to it.

1.2. The Protoboard tools (the command-line tools and the VS Code extension)
run on your machine. They contain no analytics or telemetry. They contact
the Service only when you use the library or sign in.

## 2. What we collect

2.1. **Your account.** When you create an account or sign in, our sign-in
provider (Firebase Authentication) keeps: your e-mail address and whether it
is verified, your user id, your display name if your sign-in method gives
one, the sign-in method (Google, or e-mail and password; the password is
stored only as a hash by Firebase), and when the account was created and
last signed in. On your first sign-in we ask for, and keep in your
account's profile:

- your first and last name, and a display name if you give one: to address
  you, and to know who we are helping when you contact us;
- your company or organization: to know who uses Protoboard and to support
  teams;
- the editor and the AI agent you use with Protoboard: to support you, and
  to decide which editors and agents to support first;
- whether you want product e-mails (off unless you tick it): to send them
  only if you asked;
- when you answered and when you accepted the Terms and this notice: to
  show that you did.

This profile is the same record Delta's earlier Protoboard web app keeps
for the same account, so an answer given in either app is used by both. You
can see and change it on your
[account page](https://protoboard-cloud.web.app/account).

2.2. **What the Service sees with each request.** Each request you make to
the library carries a sign-in token. From it the Service reads your user id,
e-mail address, whether it is verified, and your display name, to decide
what you may use: the whole library for Delta's team and publishers, or,
for any other account with a verified e-mail address, the parts of it that
Delta may give out to users. Apart from the sign-in records in 2.11, it
does not store them in its own records.

2.3. **Library use.** For each read of the library (a search, a part, a
file) the Service writes one log line with: a keyed hash of your user id
(not your e-mail address), which of those two parts of the library your
account reads, the request method, and the path, which names the part and
revision you read. It does not write your e-mail address, your
token, your IP address or your search words in this line.

2.4. **Usage counts.** When a part is downloaded the Service counts it per
part, revision and day. These counts do not name anyone. To count an
account only once a day, the Service keeps a one-way keyed hash of the day,
account, part and revision for that day only, then deletes it. Simply
looking at a part is counted too, without any hash of who looked. Nobody,
Delta included, can ask the Service who added a part.

2.5. **Request logs.** Our cloud provider logs each request to the Service:
your IP address, the time, the address requested (which may include search
words), the response, its size and your browser's or tool's user agent. They
do not include your sign-in token.

2.6. **Request caps.** To stop abuse the Service counts requests per IP
address and per account, in memory, for a minute and a day. These counts are
not written anywhere.

2.7. **Device sign-in.** When you sign in a terminal or agent with a device
code, the Service keeps the code you type, a label it sets itself (such as
"Protoboard CLI on Linux"), the times, and the user id of the account that
approved it.

2.8. **In your browser and on your machine.** The sign-in pages keep you
signed in with Firebase's storage in your browser, and remember your light
or dark theme. `protoboard login` keeps your sign-in on your own machine
(in the system's secret store, or a file only you can read). We do not use
advertising or analytics cookies.

2.9. **What we do not collect.** The Protoboard tools do not send us your
projects, designs, bills of materials, project names or files from your
machine. A part reaches us only when a publisher deliberately publishes it.
Features that send part or project data, when we offer them, will say what
is sent and how it is used before you use them, and we will update this
notice before they launch.

2.10. **Parts you submit and feedback.** The Service has no way yet for
users to submit parts or send feedback. If you write to us by e-mail, we
keep your message and your address to answer you.

2.11. **Your sign-ins.** For each sign-in that uses the Service (a browser,
a terminal, an agent or an editor), the Service keeps your user id, when the
sign-in was made, how it was made (the sign-in method, or for a device code
the label the Service set, such as "Protoboard CLI on Linux"), and when it
was last used. It never keeps the sign-in's token. Your account page lists
them, so you can see where your account is signed in and end those
sign-ins.

## 3. Why we use it

3.1. To run the Service: sign you in, decide what your account may use,
serve the library, and keep you signed in.

3.2. To protect it: enforce request caps, the limits of your account and the
[Library Terms](https://protoboard-cloud.web.app/library-terms), spot an
account copying the library, revoke sign-ins, and investigate problems.

3.3. To improve the library: usage counts help rank parts by how often they
are used.

3.4. To contact you about your account and the Service, for example to
verify your e-mail address or to tell you about a change to our terms.

3.5. We do not sell your personal information, and we do not use it for
advertising.

## 4. Who processes it for us

4.1. **Google Cloud** (Google LLC) hosts the Service and stores its data and
logs in the United States.

4.2. **Firebase** (Google LLC) signs you in, hosts the website and sends
account e-mail.

4.3. **Google and GitHub as sign-in methods.** If you sign in with Google
(or with GitHub, if it is offered), that provider tells Firebase who you are.
Its own privacy policy applies to that sign-in.

4.4. **Resend** sends account and Service e-mail for us. It receives your
e-mail address and the message, to send it.

4.5. The Service is operated from the United States, and your information
is processed there, wherever you use the Service from.

4.6. We may disclose information if the law requires it, to protect the
Service or its users, or as part of a sale or reorganisation of Delta's
business.

## 5. How long we keep it

| Data | Kept |
|---|---|
| Your account (2.1) | Until the account is deleted |
| Your profile (2.1) | Until the account is deleted |
| Library read log lines (2.3) and request logs (2.5) | 30 days |
| Usage counts (2.4) | Indefinitely; they name nobody |
| The one-day hash in usage counts (2.4) | Until shortly after the end of its day |
| Request caps (2.6) | In memory, at most a day |
| Device sign-in records (2.7) | Until the code is used; an unused code expires after ten minutes |
| Sign-in records (2.11) | 90 days after the sign-in was last used, or until you sign out everywhere or delete the account |

## 6. Your choices and rights

6.1. **See, correct, copy or delete.** Wherever you live, you can ask us to
show you the information we hold about you, to correct it, to give you a
copy of it, or to delete it: write to legalteam@protoboard.ai. We answer
within 30 days. You can also see your account's e-mail address and status
with `protoboard whoami`.

6.2. **Sign out and revoke.** `protoboard logout` removes your sign-in from
your machine. **Sign out everywhere** on your account page ends every
sign-in of your account, including ones you approved for agents; the
Service refuses them within five minutes. You can also write to
legalteam@protoboard.ai and we will do it for you.

6.3. **Delete your account.** On your
[account page](https://protoboard-cloud.web.app/account), choose **Delete
account**, sign in again and type your e-mail address: the account, its
profile and its sign-in records are deleted at once. You can also write to
legalteam@protoboard.ai from your account's e-mail address and we will
delete the account within 60 days. Log lines already written are kept until
they expire (section 5). Your projects are on your own machine and are not
affected. Your Protoboard account is also your account for Delta's earlier
Protoboard web app; deleting it removes both.

6.4. The law where you live may give you more rights. To use them, write to
legalteam@protoboard.ai.

6.5. The Service is not meant for anyone under 18, and we do not knowingly
collect their information.

## 7. Security

7.1. Access to the Service needs a verified account; sign-in tokens are
checked on every request and can be revoked; the logs name accounts only by
a keyed hash. No system is perfectly secure; tell us at
security@protoboard.ai if you find a problem.

## 8. Changes

8.1. We will publish changes to this notice here with a new date, and tell
you in advance of a material change, as the Terms of Service (section 14)
say.

## 9. Contact

Questions and requests about your information: legalteam@protoboard.ai

By post: Delta Robotics, Inc., 2912 Valencia Ave, Lubbock, TX 79407, United
States
