SECURITY & DATA USE

Clear controls. Honest limits.

Security is handled as operating work: use less access, isolate each workspace, verify important events, and keep a person in control.

Current security postureHTTPS, encrypted integration tokens, row-level database controls, signed Stripe webhooks, rate limits, and audit events are implemented. Independent security certification has not yet been completed.

Human approval by default

ORPA can organize and draft. Customer-facing messages, bookings, invoices, and charges stay under an authorized person’s control.

Minimum necessary access

Gmail uses read-only permission. ORPA cannot send, delete, archive, relabel, or mark Gmail messages as read.

Protected credentials

OAuth tokens are encrypted before storage. Stripe, Google, database, and AI secrets remain on the server and are not shipped to the browser.

Workspace separation

Supabase row-level access rules scope business records to the signed-in workspace. Server-only token vaults do not expose browser access policies.

Verified external events

Stripe webhook signatures are checked before billing or payment records are changed. Sensitive routes also verify the request origin.

Auditable actions

Important integration, review, scheduling, and payment events are recorded so the workspace has a trace of what happened.

CONNECTED SERVICES

What ORPA can access

Connecting a service does not give ORPA unlimited control. Each integration has a specific job and permission level.

GmailMessage text and basic message detailsRead-only import; ORPA cannot send or modify mail

Google CalendarBusy times and ORPA-created appointment eventsORPA does not delete unrelated events

StripeSubscription and payment statusCard details are collected and hosted by Stripe

AI reviewThe email or job text needed for the requested analysisNo automatic customer response is sent

Operational safeguards

Authentication sessions use secure server-managed cookies.
Administrative actions are restricted by workspace role.
Public and AI-heavy routes use rate limits.
Payment links use long random tokens instead of sequential IDs.
Secrets are configured in the deployment environment, not committed to GitHub.

Control of your data

Google and Stripe connections can be disconnected.
Disconnecting Google removes ORPA’s stored integration token.
Customer-facing actions remain reviewable before use.
Account and business-data deletion requests are covered by the published data-deletion process.
Users should remove access immediately if a device or account is compromised.

No invented certification claimsORPA CLOUD is an early-stage product. HTTPS and application controls materially reduce risk, but no online service can promise absolute security. ORPA does not claim SOC 2, ISO 27001, a completed penetration test, or another audit until that work is actually finished.