Privacy policy
Effective October 7, 2026 · Updated October 20, 2026 (Google user data)
crbcut is operated by CRBCUT LLC ("crbcut", "we", "us"). It is a beta tool for finding EV charging sites, drawing concept layouts and taking them through licensed-engineer review. This policy explains what we collect when you use crbcut.com, why, who we share it with, how long we keep it, and the choices you have. Questions go to privacy@crbcut.com.
- We collect what the tool needs to work: your sign-in details, the sites and projects you work on, and, for engineers, your license details and copies.
- We don't sell your information, don't show ads, and don't use advertising or analytics trackers.
- Some services we rely on see parts of your data to do their job: hosting, sign-in, email, maps and AI.
- You can ask us to see, correct or delete your information at any time.
- What we collect
- How we use it
- Engineer license verification
- Who we share it with
- Google user data
- Cookies and browser storage
- How long we keep it
- Your choices and rights
- Security
- Children
- Changes and contact
1. What we collect
When you sign in
- Your name and email address, and an identifier from the sign-in method you choose (Microsoft, Google, or a one-time email code). We never receive your Microsoft or Google password.
- Optionally, a job title and phone number you add to your profile.
If you join as an engineer or firm
- Your firm's name, address, phone and website, and the people you invite (name and email).
- For each license or firm registration: the state, number, discipline, expiration date and the name as it appears on it, plus the copy you upload (PDF or image).
- The results of our checks against state board records, our reviewers' decisions and notes, and the statement you confirm when you submit.
When you use the tool
- The addresses, zip codes and map locations you search, and the sites, layouts, equipment choices and drawings you create.
- Files you upload: equipment cut sheets, electric bills and utility letters. Bills are read for their usage numbers only; the bill files themselves are not stored, and we don't ask for or keep names, addresses or account numbers from them.
- In the engineer workspace: every review decision, redline, check and seal, recorded with who did it and when.
- Feedback you send us, with the name you give, if any.
Automatically
- A random identifier stored in a cookie in your browser (not linked to your name unless you sign in), used to count plan and AI usage.
- A log of actions such as pages opened, searches, layouts, exports and AI requests (with their cost to us), linked to your account when you're signed in, with what was searched and whether it worked, so we can measure and fix the tool. It stays on our server; we use no outside analytics service.
- Feedback you send from the app, with the page you sent it from and your account if you're signed in.
- Standard server logs, which can include your IP address, browser type and the pages requested.
2. How we use it
- To run crbcut: find and score sites, draw layouts, generate drawings and calculations, and move projects through engineer review.
- To sign you in and keep you signed in, and to send sign-in codes, invitations and verification results by email.
- To verify engineers' licenses and firm registrations, and to keep checking that they stay active.
- To keep an accurate record of engineering review and sealing, which the engineer of record and their firm rely on.
- To apply plan limits, prevent abuse and keep the service secure.
- To understand what works and improve the tool.
We don't sell or rent your personal information, and we don't use it for advertising.
3. Engineer license verification
When you add a PE license or firm registration, we compare it with the licensing board's public records. Today that happens automatically for Texas, Colorado, Connecticut and Illinois, using data those boards publish. In other states a reviewer checks the board's own lookup page. A crbcut reviewer compares the board record with the copy you uploaded before anything counts as verified. We re-check records in the automated states regularly, and a license the board later shows as inactive or expired stops counting until it's resolved.
Your uploaded copies can be seen only by you, your firm's admin and crbcut's reviewers. Within your firm, the firm admin can see the team's licenses and their status. On a project, the firm and the engineer of record can see that project and its review record.
4. Who we share it with
We share information only as needed to provide crbcut, with the service providers below, or when the law requires it.
| Who | What they receive | Why |
|---|---|---|
| Hetzner Online (hosting; data center in Ashburn, Virginia, USA) | Everything stored by crbcut | Runs our servers and backups |
| Microsoft and Google | Your sign-in, only if you choose them | They confirm who you are and tell us your name and email |
| Resend | Your email address and the message | Delivers sign-in codes, invitations and review results |
| Anthropic (Claude AI) | Aerial images and site details for AI layouts; electric bills and utility letters you upload for reading | Suggests layouts and reads documents. Anthropic's commercial terms say it doesn't train its models on this data. |
| Map, imagery and address services (Esri, Google, Mapbox, Nearmap, OpenStreetMap, U.S. Census Bureau, USGS) | Addresses you search and map locations | Find addresses and show aerial imagery and maps |
| Parcel and public-data sources (Regrid, county and state GIS, the U.S. DOE Alternative Fuels Data Center, state traffic data) | Map locations of the sites you look at | Parcel lines, chargers nearby, traffic and other site factors |
| State licensing boards' public data | License and registration numbers you enter | Engineer verification (section 3) |
| Code libraries served from jsdelivr.net | Your IP address, when your browser loads the map scripts | The coverage map and the AR view |
Some public data we show, such as a parcel's owner of record, comes from public records. We may also disclose information if required by law, to protect someone's safety, or as part of a sale or reorganization of crbcut, in which case this policy continues to apply.
5. Google user data
If you choose "Continue with Google", we ask Google only for the basic sign-in scopes: openid,
email and profile. We don't request access to Gmail, Drive, Calendar, contacts or any other Google data.
- What we receive: your Google account identifier, your email address, whether Google has verified that address, and your name.
- How we use it: only to sign you in, to find or create your crbcut account, and to show your name in the app and on documents you make. We don't use it for advertising, and we don't use it to train AI models.
- How we store it: the identifier, email and name are kept with your account on our server in the United States. We don't keep Google access or refresh tokens; the sign-in token is checked once and discarded.
- Who we share it with: no one, except the providers that run crbcut for us: our hosting provider (Hetzner), which stores it, and our email provider (Resend), which receives your email address to send sign-in and account messages. We never sell it.
- Deleting it: email privacy@crbcut.com to delete your account and the Google data with it. You can also remove crbcut's access at any time from your Google Account (Security, then Third-party apps & services).
crbcut's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
6. Cookies and browser storage
We use only the cookies crbcut needs to work. There are no advertising or analytics cookies.
| Name | Purpose | Lasts |
|---|---|---|
cc_session | Keeps you signed in | 30 days, or until you sign out |
cc_oidc | Protects a Microsoft or Google sign-in while it's in progress | 10 minutes |
petool_uid | Random identifier for plan and AI usage limits | About 13 months |
cc_admin | Reviewer access (crbcut staff only) | 90 days |
Your browser also keeps your current project draft and display preferences (such as Guided or Pro mode) in its local storage. That stays on your device; clearing your browser's site data removes it.
7. How long we keep it
- Accounts, firms and license records: while your account is open. After you ask us to delete it, we delete or anonymize it, except as below.
- Engineering review records: the review and audit record of a CD100 project, including sealed drawing sets, is the record of professional engineering work. We keep it as long as the firm and engineer of record may need it, or as the law requires, even after an account closes.
- Uploaded cut sheets: deleted after 30 days. Electric bills: not stored; only the usage numbers read from them are kept with your project.
- Sign-in codes expire after 10 minutes; sign-in sessions after 30 days.
- Action logs and server logs: kept only as long as they're useful for running and improving the service.
8. Your choices and rights
Email privacy@crbcut.com to:
- get a copy of the personal information we hold about you;
- correct it (you can also edit your profile and firm details yourself in For engineers);
- delete your account and personal information, subject to the engineering-record exception in section 6;
- ask any question about how your information is used.
We'll confirm who you are before acting, and reply within 30 days. Some U.S. states, such as California, give residents specific privacy rights. We honor these requests wherever you live, and we won't treat you differently for making one.
You can also block or clear cookies in your browser, though signing in needs cc_session.
9. Security
crbcut is served only over HTTPS. Sign-in sessions and one-time codes are stored in a form that can't be read back. Uploaded license copies are kept out of public file paths and shown only to the people listed in section 3. Changes to engineering records are written to an audit log. No system is perfectly secure, so if we learn of a breach that affects your information, we'll tell you as the law requires.
10. Children
crbcut is a professional tool and isn't intended for anyone under 16. We don't knowingly collect information from children. If you believe a child has given us information, contact us and we'll delete it.
11. Changes and contact
If we change this policy, we'll post the new version here with a new effective date. If a change materially affects how we use your information, we'll also email signed-up users before it takes effect.
Contact: privacy@crbcut.com