Revenium meters usage metadata, not payloads. Compliance artifacts, encryption, data handling, subprocessors and platform controls are documented below.
Most AI observability tools sit in the request path and read everything that passes through. Revenium is built the other way around. The platform captures usage metadata only.
Payload capture is a per-organization opt-in, gated three ways: team admin enablement, per-user view access, and dedicated data contexts. When enabled, payload data is encrypted at rest.
All customer data is encrypted at rest using AES-256. Data in transit is encrypted with TLS 1.2 or higher, including across public networks. Credentials are stored hashed and are not retrievable by Revenium personnel.
Customer data is processed and stored in US-based cloud infrastructure by default. An EU region is available on Enterprise plans.
Retention is configurable on Enterprise plans. On written request or on termination we provide a copy of your data and securely destroy our own copies, other than data we are legally required to retain and copies in backups until overwritten in the normal cycle.
A Revenium account holds a business email address used as the username, an optional display name, role and permission assignment, authentication metadata, and IP addresses in access and audit logs. Authentication is delegated to Clerk, Inc. Revenium personnel cannot view credentials.
We notify affected customers by email without undue delay and within 72 hours of becoming aware of a breach, as committed in our published Data Processing Agreement.
Before any employee or contractor receives access to customer data, we run a background check covering criminal history over the prior five years and verification of employment and education history over the prior five years.
Buyers running AI risk assessments ask the same six questions. Here they are, answered.
Metering, cost calculation, attribution and billing are deterministic. Their accuracy does not vary with model performance, so there is no model accuracy figure to report for the core use case.
Large language models are used for summarization and insight generation on top of already-computed data. Model providers are Anthropic and OpenAI, both listed on our public subprocessor page.
Our model providers are contractually prohibited from using data processed through Revenium’s insight layer to train, fine-tune or improve their models.
AI-generated insights trace back to the underlying metered transaction records. You can drill from a recommendation into the raw usage and cost data that produced it, so conclusions can be verified against source data rather than taken on trust.
Revenium's AI use has been reviewed under enterprise AI model impact assessment processes, including automated approval through OneTrust. Use of the AI layer is reassessed every six months.
Policy enforcement runs only where you configure a rule. Nothing is blocked, rewritten or intercepted unless you have asked for it.
Fourteen subprocessors span cloud infrastructure, authentication, payments, monitoring and engineering support.
The published list names each one with its purpose and processing region.
We give 30 days notice before adding or replacing a subprocessor. Customers may object on reasonable data protection grounds within 15 days of notice. List Available Under NDA
Controls available to administrators in the product.
SOC 2 Type II report · penetration test summary · architecture and data-flow diagram · subprocessor list · Data Processing Agreement
Our published SLA commits to 99.99% monthly availability, with service credits below 99.95%.
Current and historical uptime is published continuously, not summarized once a quarter.
Availability controls were assessed under the SOC 2 availability criterion as part of our Type II audit.
Incident response was in scope for our SOC 2 Type II audit.
SDK metering runs on a background thread after your model call returns. It never blocks the provider call and adds no measurable latency.
The only synchronous path is an optional pre-call guardrail check, which runs only when you configure an enforcement rule.
Third-party open-source components in the platform and in published SDKs are tracked and scanned. A software bill of materials for published SDK packages is available on request.
A CISA Secure Software Development self-attestation covering published SDK packages is available on request.
Yes. Revenium holds a SOC 2 Type II report, issued after an independent audit against the AICPA Trust Services Criteria for security, availability and confidentiality. The report is available under NDA.
Not today. SOC 2 Type II is our current attestation. We publish what we hold and what we do not.
Not by default. Revenium meters usage metadata only: tokens, cost, model, provider, latency, duration and attribution fields. Payload capture is a per-organization opt-in. When enabled, payload data is encrypted at rest and gated at the team, user and data-context level.
Yes. All customer data is encrypted at rest using AES-256, and in transit using TLS 1.2 or higher.
In US-based cloud infrastructure by default. An EU region is available on Enterprise plans.
That is your choice. Attribution fields are populated by you, and we do not require individual identifiers. If you use pseudonymous values such as team or cost center, no personal data enters the platform through attribution. Platform accounts themselves hold a business email address, role and authentication metadata for each user you invite.
Fourteen, published with purpose and processing region. We give 30 days notice before any change and you may object within 15 days.
Yes. Our DPA is public, incorporates the EU Standard Contractual Clauses and the UK International Data Transfer Addendum, and includes CCPA service-provider terms.
Within 72 hours of becoming aware, by email, as committed in our DPA.
On request or on termination we provide a copy and securely destroy our copies, other than data we are legally required to retain and copies in backups until they are overwritten in the normal cycle.
No. SDK metering runs on a background thread after your model call returns. It adds no measurable latency and never blocks the provider call. The only synchronous step is an optional pre-call guardrail check, which runs only when you configure an enforcement rule.
Yes. SAML 2.0 and OpenID Connect / OAuth 2.0, alongside role-based access control and audit logging.
Request the security package on this page. Access is granted after a clickthrough NDA and domain verification.
SOC 2 report, penetration test summary, architecture diagram, DPA and subprocessor list, in one download.
See what the SDK sends, field by field, in the documentation.
Revenium gives engineering and finance teams control over AI spend without taking custody of your content.