Ork Meter Enterprise · Data principles

Data governance

Clear reporting starts with clear responsibilities. Understand what OME stores, who can see it, and how your deployment governs it.

Updated November 9, 2026 · Enterprise DevOps Solutions LLC (EDOS)

Scope of this statement

This statement describes the current OME governance console and the EDOS-hosted Labs demonstration. Customer deployments may be self-hosted or operated as a managed service. Their agreed configuration, service agreement, and data processing addendum define the applicable responsibilities and commitments. This page does not establish a production SLA or replace those agreements.

Data we handle

OME brings imported usage reports together with the organizational information your administrators provide. The current console receives monthly report imports; direct plugin ingestion into customer-hosted OME is not yet connected.

Organization and member records: Organization names; member names and work email addresses; active status and roles; department, team, project group, and cost-center assignments; opaque reporting references; and WorkOS user identifiers when SSO is configured. These are identifiable business records, not anonymous telemetry.
Usage and budgets: Monthly member-level token and event totals, estimated costs, provider-reported charges, allocations, unpriced-event counts, import identifiers, and token or USD budgets. Reports associate these figures with your organizational structure.
Administrative history: Changes recorded with their time, actor, action, and target. This history supports accountability; it is not a complete access log or an independently tamper-proof archive.
Authentication and operation: Hashed access keys, temporary sessions and sign-in flows, and WorkOS identity and session references. Hosting and identity providers also process network and operational information needed to deliver and secure their services. Operator logs and backups are part of the deployment’s data inventory.

The reporting model has no fields for prompts, responses, conversation transcripts, source code, or AI-provider credentials. OME does not proxy inference requests or require your OpenAI or Anthropic API keys. Keep secrets, conversation content, and unnecessary personal information out of names, labels, imports, and support requests. Free-text administrative fields are not a content-redaction service.

Purpose and ownership

Your organization retains ownership of its reporting data. OME processes it to show usage, allocate costs, compare budgets, manage access, and maintain administrative history. EDOS uses data entrusted to it to operate and support the agreed service, address security issues, and meet legal obligations. EDOS does not sell or rent personal information, share it for third-party advertising, or use OME workspace data to train AI models.

The organization decides whose usage to measure and is responsible for lawful collection, appropriate workplace notices, and any required consent. Usage totals are not a measure of individual performance or the quality of someone’s work. In a managed deployment, the respective controller and processor responsibilities should be recorded in the customer’s data processing agreement. In a self-hosted deployment, the customer operates the data store and controls operator access.

Access and identity

OME supports owner, administrator, finance, and viewer roles. Access is organization-wide. Department, team, project, and cost-center assignments organize reports; they do not restrict which rows a member can see. An authorized viewer can access organization reporting and member information. Administrators should grant access on that basis.

WorkOS AuthKit handles sign-in using the methods enabled for the installation. Enterprise SSO can additionally connect an organization’s identity provider when configured. OME keeps the member’s name, email, and stable identity mapping; it does not adopt consumer Ork Meter’s pseudonymous sign-in model. Explicit bindings and, where configured, restricted-domain provisioning determine local membership. Domain provisioning is limited to verified enterprise SSO; new domain-provisioned members receive viewer access. Other AuthKit sign-ins require an explicit administrator-approved WorkOS user ID binding. SCIM provisioning is not implemented.

Protected AuthKit requests check provider membership and session status as well as local active status. Owners retain recovery-key access. Suspending a member revokes local access but does not erase their records or usage history.

OME uses essential cookies for sign-in: enterprise_session lasts up to eight hours and enterprise_sso_flow up to ten minutes. Sessions are held in process memory and end on restart. HTTPS deployments use Secure, HttpOnly cookies with SameSite protections. The OME site serves its fonts locally and includes no advertising pixels or third-party analytics scripts. WorkOS and your identity provider apply their own cookie and privacy practices during sign-in.

Hosting and service providers

Labs demonstration. EDOS operates this instance on Amazon Web Services in the United States, in the Oregon region (us-west-2). HTTPS protects browser traffic, and the persistent EBS data volume is encrypted at rest. Authorized infrastructure operators can administer the host, state, logs, and backups. The demo is a single-instance proof of concept; use synthetic reporting data when evaluating it.

AWS: compute, storage, infrastructure operation, and deployment services for the Labs instance.
WorkOS: hosted authentication, optional SSO brokering, identity and organization membership, and session validation. Identity information is processed separately from the workspace report store.
Your identity provider: authentication and the identity attributes released to WorkOS. The configured provider depends on the enabled sign-in method.

The AWS region describes the demo’s workspace storage, not a guarantee that every identity-provider or support process occurs in that region. Review provider terms, processing locations, and transfer requirements for your deployment. See AWS privacy, WorkOS privacy, and Google privacy.

Customer deployments. Self-hosted and managed-service installation paths support planning for AWS and internal environments. Other cloud, hybrid, and on-premises deployments require environment-specific integration and qualification. Hosting location, encryption, operator access, backup protection, subprocessors, incident response, and recovery objectives must be agreed and validated for each installation. Installing OME does not by itself establish regulatory compliance, a security certification, or production readiness.

Retention, export, and deletion

The current console has no automatic expiry for workspace records and no self-service workspace deletion. Member records, usage, budgets, import references, and administrative history persist in the installation’s state until an authorized operator removes or changes them. Suspending a user is an access action, not deletion.

Authorized users can export the available reporting CSV. It is a report, not a complete personal-data archive or backup. For a broader copy, correction, or deletion request, contact your organization’s administrator. For the EDOS-hosted demo, contact EDOS using the details below.

Deletion requires an operator to address active state, exported copies, logs, and backups, with any legally required records handled separately. Backup retention and removal are operator-managed; the Labs demo does not promise a fixed automated purge deadline. A restore must account for earlier deletion requests. Consumer Ork Meter’s seven-day active-data deletion and 35-day backup schedule do not apply to OME.

Before using real customer reporting data, establish a documented retention schedule, a verified deletion procedure, backup expiry, and restore testing for that deployment. Identity-provider records are subject to their own retention and deletion processes; deleting OME records alone does not remove them.

Reporting boundaries

Observed tokens, list-price estimates, provider-reported charges, and allocations remain distinct. Reports do not reconcile provider invoices; discounts, credits, taxes, subscriptions, and missing or overlapping feeds can change the interpretation. No measured savings or return on investment is implied.

Budgets are advisory. Their thresholds do not stop provider requests or enforce spending limits. Monthly reimports replace the relevant imported snapshot; administrators should review source coverage and assignments before relying on a report.

The existing Ork Meter plugins are consumed unchanged and retain their own service boundaries. If you also use the consumer service, its Privacy Policy and Terms of Service apply to that use. Those documents guided this statement but do not automatically extend consumer billing, retention, or service commitments to an OME installation.

Requests and contact

Start with your organization’s administrator for access, corrections, exports, retention, or deletion. For the EDOS-hosted demo, managed-service inquiries, privacy questions, or a data processing addendum, email edos-labs@edos.io. We may verify your identity and authority before disclosing or changing organizational data.

Report suspected vulnerabilities or unauthorized access to security@edos.io. Include enough context to investigate, but do not send access keys, provider tokens, or confidential report contents in an initial message.

Enterprise DevOps Solutions LLC · Boise, Idaho, United States. We will update this page and its date when OME’s data handling changes. Customer-specific contractual notices and obligations remain governed by the applicable agreement.