Security & data

Your data stays yours. Here is exactly how.

A dedicated deployment and database for every customer, every write into your systems gated and audited, and no model training on anything you give us.

A deployment of your own

Your own application deployment and your own managed Postgres database, provisioned for you alone at onboarding. Nothing in the data plane is shared with another customer.

Your ERP stays the system of record

Nothing important lives only with us. That is what makes leaving straightforward, and it is the honest answer to what happens if we are not here.

Every write is yours

Purchase orders, keyed invoices, warehouse receipts and captured customer orders are each started by your own people on screen, or by an automation you switched on and can switch off — and each one is previewed or flagged, and recorded. The AI analyst has no write access at all.

The question everyone asks first

Are you SOC 2 certified?

Not yet, and we would rather say so than manage the wording. We are an early-stage vendor. Three things stand in for it today, and you can verify all three.

The architecture removes most of what SOC 2 exists to manage. A great many of those controls address the risks of shared infrastructure — one database holding several customers, one application serving them all. You get your own deployment and your own database, so those risks are designed out rather than monitored.

Every subprocessor underneath us holds SOC 2 Type II. The hosting, the database, the AI model API and the voice platform behind the order desk are all independently audited, and they are named in the security exhibit to our master agreement.

Onboarding is itself an audit. Before go-live your controller reconciles our numbers against your ERP and your own bank statements, line by line. Most vendors ask you to trust a certificate; we ask you to check the output against books you already trust.

Certification is on the roadmap as we scale. If your procurement process requires it before you can sign, tell us early and we will be straight with you about timing rather than let it surface late.

In detail

The answers, in the order they usually get asked.

Where does our data live, and how is it isolated?

Your deployment is a dedicated, single-tenant environment — your own application deployment with its own URL and its own environment, and your own managed Postgres database, provisioned for you alone. Your data never sits in a shared table with another customer’s. Authorisation is enforced server-side on every request against your tenant’s own access list, and the emergency fallback path resolves only to your named users, never to another tenant’s. The application and your database are hosted in Canada; AI and voice processing is done by providers in the United States.

What access do you need to our ERP, and can we revoke it?

You create a connected app in your own Salesforce, Rootstock or QuickBooks environment and grant an integration user least-privilege scopes: read on the objects the analytics need, and create or update only on the objects the transactions below need — purchase orders for procurement; payables and receipts if finance and the warehouse use those screens; the CRM opportunity and one sales-order line field if you run the order desk. You hold the credentials, you set the scopes, and you can revoke access at any time from your own admin console. We never ask for your users’ passwords.

What access do you need to our email?

Only if you use emailed orders, or the payables and receivables inboxes, and only in the mailboxes you name. The software reads the messages and attachments in them, labels the ones it has handled so your team can see that in the inbox, and for the order desk sends the order confirmation from your rep’s own address, in the customer’s thread. Today this runs on Google Workspace through domain-wide delegation: your Workspace administrator authorises our service account for the Gmail permissions these features need, and can withdraw it from your Admin console at any time. On the roadmap: lighter options — forwarding a mailbox to an address of ours, or a grant on a single mailbox — and Microsoft 365, through an app limited to the mailboxes you name.

Can the software change data in our ERP?

Only through transactions your own people start on screen, or automations you have switched on — and each is scoped, previewed or flagged, and audited. What gets written: purchase orders a buyer approved, previewed before anything is sent, scoped so one buyer cannot push a colleague’s work, blocked when the underlying data is critically stale, and logged with who approved, who pushed, when, and the resulting PO number — and closed or reopened when finance presses it. Supplier invoices finance chose to key, staged for a person to post. Warehouse receipts a receiver confirmed against the purchase order. Customer payments your receivables team applied, posted on a person’s press — or automatically for payment types you switch on once they have met a measured accuracy bar. Customer orders the desk captured by phone or email, written to your CRM as a draft flagged as system-captured and released into a live order by a person — or by an automation you switched on for clean orders, which you can switch off at any time. Where the order draws on a rep’s forecast opportunity, that opportunity is reduced by what was ordered, and anything owed later goes on a backorder opportunity. On a released emailed order, the customer’s own item code goes on the sales-order line, so their paperwork and yours agree. Credit settings — limits, terms and holds on customer accounts — are maintained from each customer’s payment record by rules you switch on. And on a schedule, which we switch off on request: supplier lead times are kept current on your product records, and a discontinued product whose stock has run out is retired — its open opportunity lines move to the replacement where the pack matches, and its product record is switched off once none are left. The AI analyst has no write access of any kind. Every write is recorded.

What does the AI see, and is our data used to train models?

No, it is not used for training. Under our AI model provider’s commercial terms, inputs and outputs are not used to train models, and the voice platform behind the order desk is opted out of model training as well. The AI analyst answers only from your own tenant’s computed analytics — the same derived figures your dashboards show — and it shows its working: every answer lists the data tools it used, and every explanation carries a deterministic “how this is calculated” section computed directly from your data. It cannot invent a figure without that being visible. The order desk is different by design: on a call it reads one verified caller’s own account — order history, contract prices, stock at the shipping branch, credit status — and nothing else. Calls are recorded and transcribed. The voice platform keeps its copy for 30 days; the transcript is held in your own deployment for one year as the record of what was said and agreed. Calls your own people handle stay in your own phone system, and their recordings are yours. The document readers see the emails and attachments in the mailboxes you name — orders, supplier invoices, remittances — to capture what they say, and nothing beyond them.

Who can log in, and how is access controlled?

Sign-in is through your own Google Workspace (Microsoft 365 sign-in is on the roadmap), so your password policy, your MFA and your joiner-and-leaver process apply automatically — we are not a second place where accounts live on after someone leaves. Authorisation is a named allowlist with roles, each role seeing its own workspace, and sensitive actions gated further to named owners. Removing someone is one row, effective immediately.

How is data protected in transit and at rest?

All traffic is TLS-encrypted in transit. Data at rest is encrypted by the hosting providers, and the database provider maintains automated backups. Your secrets — your database login, your ERP integration credentials, and the mailbox, AI, voice and telephony accounts your deployment uses — are held as encrypted environment configuration in your own deployment, and no other customer’s deployment holds them.

Who at Marianas can access our data?

Named operations personnel only, for onboarding and support. No offshore teams and no third-party support vendors. Your ERP credentials are scoped by you and revocable by you at any moment.

Do your demos or other customers ever see our data?

No. Demonstrations run on a dedicated environment seeded entirely with synthetic data for a fictional company. The step that seeds it checks every record it writes for real customer names and stops if it finds one. Your data is never used in a demo, in marketing, or in another customer’s deployment. We name you as a reference only with your written approval.

What happens to our data if we leave?

It is yours. On termination we provide a full export of your database on request, then destroy the tenant database, the deployment and the credentials within 30 days, and confirm that in writing. Because your ERP stays the system of record throughout, there is nothing to be locked into: nothing lives here that your ERP does not already hold or that the export does not return.

How do you know the data is current?

An independent monitor checks every data source daily on the recency of its content — not merely whether a job ran — and alerts on staleness. An external heartbeat checks the deployment from outside our own infrastructure, so an outage cannot go unnoticed because the thing reporting it is also down. The application itself shows users how fresh what they are looking at is.

Subprocessors

Every kind of service that touches your data.

Application hostingRuns your deployment, in CanadaSOC 2 Type II
Database hostingYour dedicated database, hosted by us, in CanadaSOC 2 Type II
AI model APIProcesses requests in the United States; no training on your data under commercial termsSOC 2 Type II
Voice platformThe order desk’s voice and call transcription, processed in the United States — order desk only; opted out of model trainingSOC 2 Type II
TelephonyThe order desk’s inbound line, carried by a provider in the United States — order desk onlySOC 2 Type II
Mailbox accessOur service account, working only the mailboxes you name; sign-in stays with your own Google WorkspaceSOC 2 Type II
Your SlackCards, alerts and approvals in your own Slack workspace, only in channels you configureoptional

Each provider is named in the security exhibit to our master agreement — the full Security & Data FAQ — which you see before you sign anything, and we give notice before adding or changing one.

See it running on your own data.

Twenty minutes is usually enough to know whether this is worth going further. We’ll look at your ERP with you — and if the data isn’t ready, we’ll tell you that rather than sell around it.