Your Pipeline Records,Kept Safe and Yours.
What a utility IT reviewer or a pipeline security lead needs to know: where the data lives, how it is protected, who can see it, what the AI sees, and how you get all of it back.
- TLSEncrypted in transit
- AES-256Encrypted at rest
- USStored in the United States
- 2-STEPAuthenticator app sign-in
- ROLESOwner, admin, editor, viewer
- LOCKFinished records locked
- HISTORYWho changed what, and when
- EXPORTDownload everything, any day
- NO TRAININGYour data never trains AI
- NO SCADANever connects to field equipment
On Cloudflare, in the United States, Encrypted Both Ways.
X3 Pipeline runs on Cloudflare. Your company's records are kept in X3 Pipeline's own database and file store, separate from every other X3 product.
Location
Customer records are stored on Cloudflare infrastructure in the United States: the database on Cloudflare D1 and documents and photos on Cloudflare R2.
In transit
Every page and every request is served over HTTPS (TLS). Browsers are told to use HTTPS only (HSTS), and pages cannot be framed by other sites.
At rest
Cloudflare encrypts D1 databases and R2 files at rest with AES-256.
Company boundary
Every record belongs to one company. Every read and write on the server is checked against the signed-in person’s company, so one customer can never see another’s records.
Field equipment
X3 never connects to, reads from or controls SCADA, valves, rectifiers, pumps or any other equipment. Readings are what your people enter or import.
Backups
Cloudflare D1 keeps a point-in-time history of the database, so it can be restored to an earlier minute after a mistake or a failure.
Sign-In, Roles and a Record of Every Change.
Passwords
Stored only as salted PBKDF2-SHA256 hashes, never in plain text. After repeated failed sign-ins, the account and the address they came from are blocked for 15 minutes.
Two-step sign-in
Anyone can turn on two-step sign-in with an authenticator app, with one-time recovery codes. The account owner can require it for the whole company.
Sessions
A random sign-in token kept in a secure, HTTP-only cookie. The server stores only a hash of it, and signing out ends it.
Roles
Owner, admin, editor and viewer. Viewers can read but not change. A person can be limited to some products. The server enforces both on every request.
Change history
Every save records who made it and when. Finished records can be locked: changing a locked record asks for a reason, and the server keeps a copy of the record before and after. Worked records are voided with a reason rather than deleted.
Documents and photos
Only allowed file types up to 25 MB each. Files are kept per company and served only to signed-in people who can open that product.
Take All of It With You, Any Day.
The owner or an admin can use Download everything in Account to get one file with every product’s records and settings, company setup, the save history, the change history of finished records and an index of every document and photo, as JSON plus one spreadsheet per record list. Tables also export to .csv as you work. When an account closes, you can ask for an export for 30 days.
Ask X3: What Is Sent, and What Never Is.
- Questions about your own work send the question, a short summary of the records on screen (system names, types, states and miles; people counts; up to a few dozen open items with title, due date, severity, system and owner’s name) and matching regulation text to Anthropic’s Claude model through OpenRouter.
- Questions about what the rules say send only the question, with no company records, to the X3 knowledge service at x3api.com, which looks up the regulation text and answers through OpenRouter.
- Never sent: documents, photos, attachments or whole record lists.
- No training on your data. OpenRouter’s privacy policy says it does not train on inputs or outputs, and Anthropic says it does not train on inputs or outputs from its commercial API by default. X3 does not opt in to training.
- Your people decide. Ask X3 explains and points to the regulation. Due dates and intervals are fixed rules from the regulation text, not AI guesses, and X3 never files a report or calls an agency.
Full details are in section 4 of the Privacy Policy.
The Services That Handle Your Data for Us.
Each works under its own security program and contract. We will update this list before adding a new one.
| Company | What it does for X3 Pipeline | What it sees |
|---|---|---|
| Cloudflare | Hosting, the database (D1), document and photo storage (R2), email routing and network protection | Every request and every saved record |
| Stripe | Card payments, invoices and the billing portal | Billing contact and payment details. X3 never sees full card numbers |
| Resend | Account email such as password resets and notices | Name and email address of the person the message is for |
| OpenRouter | Routes Ask X3 questions to the AI model | The question, the short records summary described below and matching regulation text |
| Anthropic | The Claude model that writes Ask X3 answers | The same, passed on by OpenRouter |
Found a Security Issue? Tell Us.
Write to [email protected] with what you found and how to reproduce it. A person reads every report and answers. Please give us a reasonable time to fix an issue before you share it, and do not access, change or delete other customers’ data while testing. If we learn of a breach that affects your data, we tell you without undue delay and as the law requires. Security questionnaires go to [email protected].
Walk Through the Real Screens First.
The tour opens the command center and all nine dashboards with an example company. Nothing to sign up for, and nothing you click is saved.