Trust

Security & AI Transparency

What Commerce Brain™ can do, what it will never do, and the controls that keep your business data safe.

Last updated · August 20, 2026Reading time · 1 min read

How Commerce Brain™ works

Commerce Brain™ is a reasoning engine. It reads signals from your connected Shopify store, cross-references them against your Decision Memory (private layer), and produces ranked decisions with the evidence behind them.

Evidence-based
Every recommendation cites the signals behind it.
Never autonomous
Financially material actions always require a human.
No invented data
Brain refuses to guess when evidence is insufficient.

What Commerce Brain™ never does

  • It never invents financial numbers, KPIs, or historical facts.
  • It never executes financially material actions without human approval.
  • It never blends your Decision Memory (private layer) with another business's data.
  • It never trains third-party foundation models on your identifiable business data.

Encryption

In transit
TLS in transit, provided by our hosting platform.
At rest
Encryption at rest, provided by our hosting platform.

Compliance & Certifications

Row-level security
Workspace data is scoped per organization by row-level security.
GDPR
All three of Shopify's privacy webhooks are signature-verified and acted on: shop and customer erasure delete on receipt, and an access request is queued with the records we hold and delivered to the merchant inside their 30-day deadline. Account deletion on request and a data export from the Security Center.
CCPA
California residents can request access to their data and its deletion.

Secure Authentication

  • Industry-standard password hashing (bcrypt).
  • Optional two-factor authentication with an authenticator app (TOTP).
  • Session revocation on password reset and suspicious login.

Audit Logging

Every action OCCEAN takes in your store is recorded with the actor, the timestamp, the target it touched and the outcome — including failures. An undo is written as a new entry rather than removing the original, so the sequence of what happened stays readable.

Action log
Actor, time, target and outcome on every store action.

Role Permissions

A workspace has four roles: Owner, Executive, Analyst and Viewer. Owner and Executive boundaries are enforced in the database itself, through row-level security that checks organization ownership and membership, so they hold even if a request bypasses the interface. The distinction between Analyst and Viewer is presentational today — both see the same workspace data, and we are moving those checks into the database next. Enterprise: contact us for custom security requirements.

RBAC
Four roles. Owner and Executive boundaries enforced in the database.

Backups

Managed backups
Database backups are provided and managed by our hosting platform.

Incident Response

Confirmed incidents affecting customer data are investigated promptly and affected customers are notified without undue delay.

Data Isolation

Decision Memory™

Decision Memory (private layer) is row-scoped per tenant by row-level security, and is never mixed with another business's data.

Contact & Vulnerability Disclosure

Report vulnerabilities responsibly to success@occean.app. We aim to acknowledge reports promptly and coordinate disclosure with researchers.