Privacy Policy
Version privacy-2026-11-14. Effective on publication.
This policy explains what Oneline.build (“we”) collects when you use the website at oneline.build and the tool at app.oneline.build, why, where it is kept, and how to have it removed.
1. What we collect
| What | Where it comes from | Why |
|---|---|---|
| Account data: your name, e-mail address, sign-in identifiers, and the organization you belong to | Our authentication provider, when you sign up and sign in | To sign you in and keep your workspace separate from everyone else’s |
| Projects: the electrical models, drawings, revisions and schedules you create, and the PDF and CSV exports you generate | What you enter in the tool | To run the tool, save your work and give it back to you |
| Quote requests: the contact details you type (name, e-mail, phone, company), the site address, your notes, and a snapshot of the project you attach | The “Request a quote” form | To prepare and send you a quote for engineering services |
| Website quote form: what you type (contact and project details), how you reached the site (campaign tags, landing page, referring page), your IP address, your approximate location derived from it, and your browser type | The form on oneline.build, automatically when you submit it | To answer your request, to know which outreach reached you, and to stop spam |
| Drawings made without an account: nothing is stored on our server. The drawing stays in your browser. Exporting a PDF or CSV or running the preliminary fault current needs an account | The editor at app.oneline.build/draw | To keep your drawing available while you work |
| Product usage events: which steps in the tool you take (for example opening the editor, being asked to sign up, signing up, exporting a PDF, running the preliminary fault current or opening a quote request), the time, a random identifier your browser makes for itself, the campaign tag of the link you arrived by, and your account and workspace once you are signed in. Never the contents of your drawings: at most a count, such as how many buses a calculation covered | Automatically, as you use the tool | To learn which features are used and whether people go on to sign up or request a quote |
| Server logs: your IP address, the pages and requests you made, timestamps and errors; and an audit record of important actions in your workspace (for example a project created or deleted, a quote request made) | Automatically, as the service runs | To keep the service running and secure, and to investigate problems |
We use no advertising trackers. We record which product steps people use (for example, opening the editor or exporting a PDF), without cookies and without the contents of your drawings. The only cookies we set are the ones that keep you signed in. Your browser’s local storage holds your account-free drawing, a random identifier the tool uses to count those steps, and, on the website, how you reached the site. All three stay in your browser until you clear them; the identifier is sent with the product usage events, and how you reached the site is sent only if you submit the quote form. The quote form also runs an automated bot check from our network and security provider, which processes your IP address and browser details for that check.
2. Where it lives
- The application and database run on one server at our hosting provider’s data center in Ashburn, Virginia, United States.
- Backups of the database are copied nightly to an object-storage provider’s bucket in Eastern North America.
- Sign-in data is held by our authentication provider in the United States.
- Our network and security provider runs our DNS and sits in front of the website and the app, so your traffic passes through it and it sees your IP address and request details. It also hosts the website, and stores website quote requests in its object storage.
- Quote-request e-mails go to our own mailbox through our e-mail provider. The e-mail contains your contact and project details but never the model snapshot.
We describe our providers by what they do (hosting, authentication, object storage, network and security, e-mail) and do not name them.
3. Who sees it
The people who run Oneline.build, and only when needed: to prepare a quote you requested, to answer a support question, or to keep the service running. Our providers above process data on our behalf to host, sign in, back up, carry and protect traffic, and send e-mail; they do not use it for their own purposes. We do not sell your data and we do not share it with other users or with advertisers. We disclose data only if the law requires it.
4. How long we keep it
| Data | Kept |
|---|---|
| Account and projects | As long as your account exists |
| A project you delete | Marked deleted at once and no longer shown. It stays marked deleted in the database until you ask us to remove it (section 5); once removed, the copies in backups expire on the schedule below |
| Revisions of a project | With the project |
| Exports (PDF, CSV) | At least 7 days. After 7 days an export is removed at the next clean-up, which runs once a day. Until then it stays in the database and in the nightly backups. Once it is removed from the database, the copies in backups expire on the backup schedule below |
| Database backups | 14 days on the server, 30 days off-site |
| A drawing made without an account | In your browser until you clear it or create an account and bring it across. We hold no copy and cannot recover it |
| Quote requests (from the app or the website) and any snapshot | As long as we need them to honor the quote, then 3 years, or until you ask us to delete them, including after the project is deleted, unless the law requires us to keep them |
| Product usage events | Events not linked to an account are deleted automatically after 180 days. Events linked to your account are deleted automatically after 13 months, or earlier when your account is deleted (section 5), and the copies in backups expire on the schedule above. The events not linked to an account are tied to you only by the random identifier your browser made |
| Server logs | Capped by size and overwritten, in practice a matter of days to weeks |
| Audit records | With the workspace |
5. Deleting your data
Write to privacy@oneline.build from the e-mail address on your account. We will delete your account and your projects within 30 days, and the copies in backups expire on the schedule above. Quote requests may be kept where we need them to honor a quote or where the law requires it; we will tell you if so.
You can also export your drawings (PDF) and schedules (CSV) yourself at any time, and you can ask us for a copy of your project data in a machine-readable form.
6. Your rights
You may ask what we hold about you, have it corrected, have it deleted, or object to how we use it. Use the address above. If you are in a place whose law gives you further rights, those apply too.
7. Security
Traffic is encrypted in transit; each organization’s data is separated from every other’s by the application; access to the server is limited to the people who run Oneline.build and logged. No system is perfectly secure, and we cannot promise that; if we learn of a breach that affects you we will tell you.
8. Children
The tool is for businesses and is not meant for anyone under 18.
9. Changes
When this policy changes we publish a new version with a new date. The current version is always at oneline.build/privacy.
10. Contact
privacy@oneline.build