Security & Trust

Trust is a feature. We engineer it.

Opal holds the most intimate data in commerce: a client’s face, body, and history. We treat that responsibility as doctrine, not policy.

Consent-first by doctrine

Client data is held under explicit consent, used only to serve that relationship, and never sold. Our commercial model never depends on the resale of consumer identity.

Encrypted in transit & at rest

All traffic is served over TLS. Sensitive records are encrypted at rest. Secrets live only in server-side environment variables, never shipped to the browser.

Least-privilege access

Role-aware views for providers, front desk, and ownership. People see what they need to do their job, and nothing they don’t.

Portable & exportable

The SkinTwin is portable under client consent, and business data is exportable. Trust is a feature, not a lock-in.

No secrets in the repo

.env.local is never committed. Stripe, OpenAI/Anthropic, MongoDB, and Twilio are wired exclusively through environment variables.

Procurement-ready

Enterprise security, privacy, and operational review are designed in. Opal is built to be deployed, not merely demoed.

Practices under the hood.

Payment security

Payments are processed by Stripe. Opal never stores raw card numbers; checkout and webhooks run server-side with signature verification.

Webhook integrity

Stripe webhooks are verified against STRIPE_WEBHOOK_SECRET before any action is taken, preventing forged events.

Graceful degradation

If a key is absent, the affected service safely no-ops or enters demo mode rather than failing open or leaking errors.

Data dignity

Memory is the product, and it belongs to the business that owns the client relationship, not to Opal.

The Moat

Patent Pending · filed with the USPTO.

A U.S. patent application covers autonomous client interaction, scheduling, and operational intelligence, with beauty-native architecture and data dignity by design.

Get Opal