Browser protections
Repository-configured response headers restrict content sources, prevent framing, reduce MIME-type confusion and limit access to selected browser capabilities.
Security at Verri
Practical controls. Honest boundaries.
Verri uses layered safeguards for the current account, workspace, billing and support experience while being clear that security risk cannot be eliminated completely.
Security boundary
Security information, not a guarantee.
The practices described here are based on the current implementation. Verri does not claim guaranteed security, zero breach risk, certification or an independent audit.
Current controls
Layered safeguards around the current service.
Verri applies technical and organisational controls proportionate to the current service. These controls reduce risk, but no online service can guarantee absolute security.
Account and data access
Authenticated operations use server-verified identity. Account-linked conversations, requests and support records use ownership and access controls designed to keep one user from reading another user’s records.
Paid subscriptions
For paid subscriptions, payment-card entry and subscription management use Stripe-hosted flows. Verri receives billing and payment-event information needed to operate subscriptions, not full card numbers. Planned alpha access is separate and will not require payment details.
Deletion and retention
Permanent account deletion requires authenticated owner confirmation. Limited billing, dispute, fraud-prevention and security evidence may be retained where needed or required by law.
Operational records
Diagnostic, support and privacy-minimised product records are restricted to their operational purpose. Current product analytics do not store prompt or response content.
Provider processing
A selected AI provider processes the request needed to return an answer. Review the Privacy Policy for the current provider and service-processor boundary.
Read the Privacy PolicyReport a concern
A public route for security reports.
Security concerns can be reported through the monitored temporary legal and privacy contact without signing in. Describe the affected page or service and the observed issue, but do not include passwords, authentication codes, exploit data containing personal information or full payment-card details.
Unauthenticated security reports
Use this public email route if you do not have a Verri account or the issue affects authentication. Verri will review the report, but this is not a promise of a particular response time or outcome.
Email a security reportAccount-specific support
When you can sign in and the issue concerns your account or private workspace, use authenticated support so ownership and replies remain together.
Visit SupportImportant limitations
Clear security boundaries, without guarantees.
This page describes current practices. It is not a certification, independent security audit or promise that incidents cannot occur.
No certification claim
Verri does not currently claim a security certification, completed independent audit or regulatory-compliance certification.
No end-to-end encryption claim
Do not treat Verri as an end-to-end encrypted messaging service. Requests must be processed by the selected provider to produce a response.
Individual access only
The current service provides an individual account and workspace. Organisation-level administration, shared projects, team permissions and enterprise security controls are not currently available.
Protect important information
Do not submit passwords, authentication codes, full payment-card details or information you are not authorised to share. Verify important AI output before relying on it.