VVenuvero

Trust center

Security at Venuvero

A plain-language overview of the technical and organizational controls currently used to protect Venuvero workspaces and connected-provider data.

Effective October 31, 2026

Access and tenant isolation

Venuvero uses server-managed, HttpOnly, Secure session cookies. Session and reset tokens are stored as one-way hashes. Authenticated requests are bound to one organization, and workspace queries include that organization identifier. Administrative data export and deletion require the owner's current password.

Connected account protection

OAuth uses authorization code flow, one-time state, ten-minute expiration, and PKCE S256. Access and refresh tokens are encrypted at rest with AES-256-GCM and are never returned to the browser or included in an account export. Apple Calendar uses an Apple-generated app-specific password over HTTPS CalDAV; that credential receives the same encryption and export protections, and the primary Apple password is never requested. Venuvero asks for delegated, feature-specific access and fails closed if the provider does not grant it. Disconnecting immediately erases the encrypted credential and attempts Google-side revocation where available.

Stored email and event content

Email and event records, review messages, private workspace state, reminder text, file metadata, and connection configuration are encrypted before database storage using AES-256-GCM. Each workspace has a random data key; only its encrypted form is stored in the database, with the wrapping key supplied separately through deployment secrets. Authorized users can still read their messages, and the application decrypts content for permitted viewing and processing. This is server-side encryption, not end-to-end encryption: it does not hide the original message from an email-routing provider or prevent an operator controlling the running application from accessing plaintext.

Application and network controls

Production traffic uses HTTPS. The API enforces an origin allowlist, cross-site mutation checks, request-size limits, validated request schemas, endpoint rate limits, redacted request logging, timeouts for outbound calls, and restrictive browser security headers. Public URL collection rejects credentials, private-network destinations, unsafe redirects, oversized responses, and disallowed robots instructions.

Payments, AI, and third parties

Stripe-hosted Checkout handles payment details, and Stripe webhook signatures are verified before billing state changes. AI requests use the minimum content needed for the selected feature and disable response storage where supported. Provider data is not used for ads or generalized AI training. Current service-provider categories and data uses are listed in the Privacy Policy.

Account access and human access

Workspace roles limit administrative settings to owners and admins. Production owners and admins must enroll an authenticator and verify their sign-in before protected workspace APIs can be used. Other members can enable MFA in Account. Authenticator secrets are encrypted; recovery codes are hashed, single use, and shown once. Successful MFA sign-ins expire after twelve hours. Verification rejects reused codes and pauses after repeated failures. Replacing an authenticator requires the current password and a verified session and revokes other sessions.

The operator's infrastructure access can technically expose readable data. Human access to private communications is limited by policy to explicitly requested support, abuse or security investigations, and legal obligations. Venuvero does not claim that customer-held keys prevent operator access. Cloudflare, hosting, and database administrator accounts have their own access and MFA settings, separate from Venuvero sign-in.

Monitoring and response

Venuvero records security-relevant integration events without recording provider tokens. Suspected credential exposure is handled by revoking the affected secret or token, investigating scope, restoring from known-good code, and notifying affected users when required. Dependencies and production configuration are reviewed before releases. Application request logs omit query values, customer link tokens, message bodies, and raw provider errors. Worker invocation logging is disabled in deployment configuration to reduce email-subject and private-URL retention; Cloudflare Email Routing activity and previously retained provider logs have their own controls and retention.

Report a vulnerability

Please do not test against customer data, degrade availability, or access information that is not yours. Send a concise report with reproduction steps and impact through the contact channel below. Good-faith reports will be acknowledged and investigated.

Contact Venuvero through the support channel inside your account or email hello@venuvero.com.