Security

Orishare runs on Google Cloud in us-central1 behind Cloudflare. This page describes what is built into the platform today; it is not a certification claim.

Tenancy

Every operational row carries an environment id and a runtime class. Every query is scoped to one environment; test and live environments of the same project never share rows. Test and live runtimes use separate database roles that can only see their own environments.

Credentials

  • Secret keys (osk_), publishable keys (opk_), personal and AI access keys (opat_), AI connection tokens (oat_, ort_) and browser sessions (oses_) are random, stored hashed, shown once, scoped, and revocable individually.
  • Publishable keys can only act for one signed-in player, through a short-lived customer session your server creates, and only send events an editor has allowed from the client.
  • Sign-in is a one-time emailed link or Google; sessions live server-side in our database and can be revoked at any time. Orishare never stores passwords.
  • Webhooks are signed (HMAC-SHA256 over timestamp and body) with per-endpoint secrets that rotate with a 24-hour overlap.

Determinism and audit

Rules are immutable versions. The same event, customer state and ruleset always produce the same effects, and every evaluation keeps its plan and trace. Every configuration change writes an audit entry with actor, before and after. Staff access to customer organizations goes through an audited support console that requires a reason for every request.

Personal data

Customer attributes flagged as personal data are excluded from AI drafting context. Deleting a customer redacts attributes and events, removes aliases and keeps only the financial ledger history. A per-customer data export returns everything held about a person in one document. Test data is retained 30 days, live data 90 days in the hot store with history in an archive you can query.

AI

AI never runs on the event path: rules decide every reward. The built-in assistant and AI tools you connect (over MCP or an AI access key) can set up and run your program, within the permissions you grant. In a live environment you choose how much they may do alone; anything beyond that waits for a person to approve it in the dashboard. Every AI action is recorded in the audit log.

Reporting

Report vulnerabilities to support@orishare.com. We acknowledge within two business days.