Security
What protects your data today.
This page lists what is implemented in OpsIntel now, and what is not. If you are running a review, start here and ask us for anything it does not cover.
The short version
Four things to know.
Your organization’s data is kept apart.
Every signed-in request is tied on the server to the organization its member belongs to before any data is returned. Automated tests check that one organization cannot reach another’s data.
Only the people you invite get in.
You sign in with your Google account. Invitations are tied to one email address, expire after 24 hours and can be revoked. Two roles, Owner and Admin, decide who holds billing and settings.
Connections only read.
OpsIntel reads your reporting and cannot change orders, prices, schedules or records. Xero and QuickBooks are read-only: it cannot post, edit or pay anything.
Credentials encrypted, traffic over HTTPS.
Credentials for newly connected systems are encrypted with AES-256-GCM before they are stored. OpsIntel is served over HTTPS and checks your reporting source’s certificate.
The details
What is implemented, control by control.
For a security review: what is in place today, in plain words, and what is not.
Signing in and access.
| Control | What is implemented |
|---|---|
| Sign-in | You sign in with your Google account. There is no separate OpsIntel password. Any two-step verification you set on your Google account applies. |
| Joining an organization | By invitation only. An invitation is tied to one email address, expires after 24 hours and can be revoked. |
| Roles | Two roles in the current release, Owner and Admin. Both see all of your organization’s stores. People you invite join as Admins. Billing and some organization settings are reserved for the Owner. |
| Every request | Signed-in requests are checked with the authentication service on the server and tied to an organization the member belongs to before any data is returned. |
| Activity record | Sign-ins and administrative actions such as invitations, role changes, integration changes and billing actions are recorded on the server with the time and the acting user. |
Where your data sits.
| Control | What is implemented |
|---|---|
| Your organization’s data | Organizations share one database. The application server ties each request to the member’s organization. On proposed code changes, automated tests check that one organization cannot reach another’s data. |
| Your reporting connection | Each organization connects with its own credential, limited to its own stores. Credentials for newly connected systems are encrypted with AES-256-GCM before they are stored. |
| In transit | OpsIntel is served over HTTPS. It connects to your reporting source only over HTTPS and verifies its certificate. |
| Database access | The database’s privileged key is used only on the server and is never sent to the browser. |
| OpsIntel staff | Named OpsIntel staff with internal admin access can reach customer data to support the service. That console is limited to named staff accounts. |
Your source systems.
| Control | What is implemented |
|---|---|
| Your reporting system | OpsIntel reads reporting data. It has no feature that changes orders, prices, schedules or records in your point-of-sale system. |
| Which stores | Reporting queries are built from your organization’s registered store list. |
| Accounting | The accounting integration reads Xero or QuickBooks with read-only access. It cannot post, edit or pay anything. |
| Payment cards | OpsIntel does not collect or store payment card numbers. |
AI features.
| Question | Answer |
|---|---|
| What is sent | AI features inside the product send figures OpsIntel holds for your organization to our AI model provider, Anthropic. Today these are the question box, which also sends your question; written summaries and analysis of your stores’ plan and variance figures, where a plan has been set up for your organization; and the Explain these results button on marketplace statements, which sends totals from those statements. |
| What is kept | Questions and answers are stored with your organization’s account, and may be processed again by the AI provider to keep a memory of your organization’s context. |
| How answers are built | Answers are built from figures the server retrieves for your organization. The model is instructed to state the figures and period it used and to say when a figure is missing. That is an instruction to the model, and it can still be wrong. |
| This website | The question box on this website is a fixed list of answers. It has no connection to customer data. |
Who else handles it.
The vendors that store or process data on OpsIntel’s behalf.
| Vendor | What it does |
|---|---|
| Supabase | Database and authentication. |
| Railway | Application hosting. |
| Sign-in. | |
| Anthropic | AI model, for the AI features only. |
| Resend | Email delivery, including the alerts and the weekly review our system sends. |
| Stripe | Billing and payment, when your organization sets up a subscription. |
Not yet
Not in place today.
- Single sign-on beyond Google sign-in, and any multi-factor setting managed inside OpsIntel.
- Store-level or regional permissions. Everyone you invite can see all of your stores.
- An activity log customers can read themselves, or a record of who viewed which figure.
- A SOC 2 or ISO 27001 report, or an independent penetration test.
- Self-serve export or deletion of your data. When an organization is offboarded its members lose access and its stored records are retained; talk to us about removal.
Running a security review?
Send us your questionnaire. Someone who works on the product answers it.