Security by design

Trust requires clear controls, not vague promises.

Opiny architecture protects access, collection and circulation of your customer signals.

Organization isolation

Every authenticated query validates active membership and organization scope before accessing surveys, responses or settings.

Token rotation

Short-lived access tokens and rotating refresh tokens reduce credential reuse risk.

Allowed domains

Each survey can restrict which domains may load the widget and submit responses.

Verifiable webhooks

Events use HMAC SHA-256 signatures so destinations can verify origin and integrity.

Encrypted secrets

Sensitive V2 integration URLs are protected with AES-256-GCM before storage.

Role-based permissions

Owner, administrator and member roles delimit administrative and operational actions.

Transparency

What is implemented today.

This page describes controls that exist in the product. Certifications and additional enterprise requirements should be assessed during procurement.

Can Opiny access data from other organizations?

No. Authenticated endpoints validate the user membership against the requested organization and deny requests outside that scope.

How do I validate an Opiny webhook?

Compute the request body HMAC SHA-256 using your organization secret and compare it with the X-Opiny-Signature header.

Can I restrict the widget to my domain?

Yes. Surveys accept an allowed-domain list and reject widget loads and submissions from other origins.