Trust posture

Trust starts at the audit log.

The platform that runs your store should be transparent about what it does with your data, who can see it, and what happens when something breaks. Here is ours — written plainly, no buzzword fog.

A patient's card is checked at the counter and only what your state's rules require is kept, under the state's health-data law.

01

If we go down: your register doesn’t

Most operators who’ve been in this industry a few years have a story about a Saturday POS outage and ringing on paper. Here’s what happens at your store if our platform has an issue — written plainly, no bravado.

  • Per-store database, not multi-tenant. Your Postgres is yours alone. An issue affecting another customer’s DB doesn’t reach yours.
  • Offline cache at the register. The register keeps the last-known cart state, so an in-flight transaction completes even if the connection blips.
  • When a problem of ours reaches your store, we call or email you as soon as we know. A person sends it; nothing alerts you automatically yet.
  • After a problem that stops your register or your state reporting, we write to you. We say what broke, what we fixed, and what we changed so it does not happen again.
  • Direct escalation path: support@cannagent.ai. Not a ticket queue, not a bot. If it’s broken, we want to know first.
Current platform status →
02

Audit log: build-out in progress, compliance events covered today

Not every change in the store app writes to the audit log yet. These already do: ID scans, refused IDs, date-of-birth mismatches, manager overrides, role changes and voids.

  • When a change is saved, an entry is written to the audit log right after it. That is how changes are built here, but not every change does it yet
  • Each entry records who made the change, what they did, which record it touched, and when
  • Admins, general managers and bookkeepers can read the audit log
  • Real-time SMS escalation for critical events (sale-to-minor block, large void) is in design — today these surface in the alerts inbox + manager-on-duty digest
03

Each person’s role sets what they can see and change

Every staff account has a role, and the store app reads that role to decide what the person can see and change.

  • Roles include admin · general manager · manager · inventory manager · purchasing · lead · budtender · bookkeeper · vendor
  • A shared set of role checks answers questions such as: is this person an admin, a manager or above, allowed to see store profit, allowed to see product cost
  • Each staff sign-in carries its role in a signed session. A back-office screen left untouched for an hour signs itself out, and a change to someone’s main role takes effect at their next sign-in
  • Switching between your stores uses a signed hand-off, and at the other store the person gets the role their own account has there
04

Cannabis rules coded into the platform, not bolted on

Cannabis rules are mapped feature by feature, and Washington’s WAC 314-55 family is the reference set. The register refuses a sale to anyone under 21 in code, not by policy. It does not stop a sale by time of day. Washington’s selling hours, 8 a.m. to midnight (WAC 314-55-147), stay with your closing routine.

  • WAC 314-55-079 (retailer privileges): the age-21 restriction in -079(1), enforced at scan time
  • RCW 69.50.535 (cannabis excise tax): the 37% excise math in (1)(a)
  • WAC 314-55-083 (security) — the employee ID badge on record (‑083(1)) is in the hiring flow. CannAgent does not connect to your cameras or alarm, so the 45-day recording rule (‑083(3)) stays on your side
  • WAC 314-55-087 (recordkeeping) — sale records and employee records kept five years on the licensed premises
  • WAC 314-55-155 (advertising) — efficacy and medical-advice claims are blocked at the template layer; there is no override path that publishes one
See the WA compliance rollup →
05

Your data, your database, your own Neon project

Each store gets its own Postgres database. Cross-store reads are explicit and auditable, not implicit and silent.

  • Per-store Neon Postgres — every location gets its own separate, isolated database, never a shared multi-tenant table
  • Each database can be restored to an earlier point within Neon’s restore window. Our hosting plan sets the window; ask us for its current length
  • Customer can request a full SQL export at any time — operator owns their data, no exit penalty
  • TLS in transit, AES-256 at rest, secrets via Vercel encrypted env vars — never committed
06

Proprietary tech held back from public pages — disclosed on demo

Some features ship with their implementation details held back on the public site. The demo shows how each one works.

  • Crown-jewel features marked PROPRIETARY with a black-bar visual treatment + 'proprietary technology' caption
  • When your demo is approved we draft a non-disclosure agreement. We may ask you to sign it before your sandbox opens.
  • Held back here means not printed on a public page. Ask on the demo and we show you.
Read the FAQ on held-back features →
07

When something breaks, we tell you

A person on our team calls or emails you directly. Every 5 minutes, our checks test this site and the services listed on /status.

  • We contact your store ourselves, by phone or email, as soon as we know. Nothing alerts you automatically yet, by email or text
  • After a problem that stops your register or your state reporting, we send you a written account: what broke, what we fixed, what we changed
  • If a problem touches your data, we tell you directly. No ‘no comment’
  • /status shows those checks and each one’s uptime over the last 24 hours, so you can check our story yourself
See current platform status →

Verify our story

Every claim on this page is checkable on a public surface. Don’t take our word for it.

Sub-processors

Vendors that may process your data on our behalf. Listed by name with scope and agreement status — no anonymous “third parties.”

VendorPurposeAgreement
VercelHosting, edge network, web analytics, file storage; AI requests route through its AI Gateway when that is switched onDPA on file
NeonPostgres database and its point-in-time restore historyDPA on file
ClerkSign-in for the customer account portal and adminnot yet confirmed
AnthropicAI features: the website chat assistant, draft replies to support email, demo-request scope summaries, personalised follow-up email, call-transcript summariesDPA on file
ResendTransactional email (demo confirmations, receipts, manager alerts)DPA on file
TwilioPhone-number lookup and a text back to callers on our support line who leave a mobile numberDPA on file
Retell AIAnswers our support phone line (AI voice agent)not yet confirmed
GoDaddy Payments (Poynt)Subscription billing (CannAgent SaaS fees) through hosted pay linksnot yet confirmed
CalendlyDemo booking; it tells us when a demo is booked, attended or missednot yet confirmed
GoogleAd conversion measurement (Google Ads tag) and, when switched on, Google Analytics — on every page except our admin areanot yet confirmed
GoDaddy / CloudflareDNS for store-owned domainsnot required

What gets audited (selected)

Not exhaustive — these are the actions most often asked about after the fact. Each row is written by the server-side action that made the change. None of these rows is pruned, so each period is a floor, not a deletion date.

CategoryActionKept at least
AuthLogin attempt (success or failure)24 months
AuthRole change24 months
AuthManager-PIN override36 months
POSSale to minor block triggered60 months (WA: WSLCB)
POSVoid above $10036 months
POSCash variance > $5 at till close36 months
InventoryManual quantity adjustment60 months (WA: WSLCB)
InventoryCost-basis edit36 months
ComplianceTraceability manifest export60 months
PeopleWrite-up created or edited60 months (WA: WSLCB)
PeopleTermination or hire-date change60 months (WA: WSLCB)

In progress — disclosed honestly

We don’t put “SOC 2 compliant” on the site until the report is in our hand. Here’s what is planned and not yet done.

  • SOC 2 Type I — planned. No auditor is engaged yet; when one is, we will name them and the date here.
  • Penetration test — planned. No vendor is engaged yet; when one is, we will name them and the date here.
  • ISO 27001 — gated on first multi-state customer; not premature

Need security answers for procurement?

The sub-processor list is above and in the privacy policy. Ask on the demo request: a person answers your security questionnaire, and the data-processing terms are agreed with you before anything is signed.