What Ork Meter collects, and what it never does.
Ork Meter measures the AI usage your tools consume. This policy describes the data the service actually handles today. Where a capability is not yet enabled, this policy says "when enabled" rather than describing it as if it were live.
1. Who we are
Ork Meter, Ork Meter Plus and Ork Bot for Discord are products of Enterprise DevOps Solutions LLC, a United States company. Contact us about privacy at edos-labs@edos.io. For usage metadata you send about other people (for example an organisation's developers), you are responsible for that data and we process it on your behalf; a data processing addendum is available on request.
2. What we never collect
- Prompts, responses or transcripts. Inference traffic stays between you and your provider. The helper sends allow-listed usage metadata only: source, request ID, model, timestamp, token counts by category, any provider-reported charge, and the attribution labels on the helper credential. Prompt content has no field in that schema and never enters the usage ledger.
- Source code or commit messages. Optional work records carry an opaque repository reference, a commit identifier, numeric diff statistics and effort assumptions you supply. Nothing else.
- Your provider credentials. The helper never reads Anthropic API keys, OAuth tokens or Claude Code credential stores. It uses only its own Ork Meter helper credential.
- Your name or email address from sign-in. We keep a hashed sign-in identifier, not your profile. We hold no sign-in provider access or refresh tokens.
- Payment card data. When paid plans are enabled, Stripe's hosted checkout collects card details and billing address; they never reach our systems.
- Discord message content. Ork Bot uses slash commands only, requests no permissions and no privileged intents, and cannot read messages.
- Identity attributes from telemetry. Claude Code capture discards user email, organisation and account identifiers, session identifiers and every non-token metric before anything leaves your machine.
- Analytics trackers. orkmeter.com loads no third-party scripts, fonts, pixels or analytics.
3. What we collect when you use Ork Meter
| Data | Why | Where it comes from |
|---|---|---|
| Sign-in identity: your GitHub numeric user ID, stored as a hash with its issuer | To recognise your account. Provider access tokens and profile data are discarded after the identity is verified. | Your GitHub sign-in |
Account and eligibility: random account and workspace IDs, signup time, free-period clocks, plan status, and your US-adult acknowledgment (version us-adult-v1, no date of birth or documents) | To run your workspace and apply the free period, free tier and any paid plan. | You and the service |
| Sessions and security: session records, CSRF tokens, request-admission counters | To keep you signed in for a bounded period and protect the service from abuse. Only hashes of session secrets are stored. Shared admission counters contain no identifiers; per-session counters hold a hash and expire within two hours. | Your browser; service operation |
| Preferences: your selected clients, setup choices, free-tier client selection, and Plus preferences (work area, optimisation goal, quality policy, confidence threshold, allowed task categories, consent state and revision) | To remember what you chose to measure and how Plus should behave. No prompts or biography. | Your choices on orkmeter.com |
| Helper pairing records and helper credential hashes | To let a helper you approved send usage metadata, and to let you revoke it. Credentials are stored only as hashes. | Pairing on orkmeter.com |
| Usage metadata events, daily aggregates and optional work records | To report measured usage, token estimates and reported charges, each kept distinct. | Your helper |
| Native usage counters (for example Claude Code token counters) | To report usage from tools that export counters. Each feed keeps only its latest export, which expires after one year. | Your helper, after your explicit telemetry confirmation |
| Billing identifiers (when paid plans are enabled): plan, period, and Stripe customer, subscription and invoice references | To apply the plan you bought. We store references, not card numbers, billing addresses or raw invoices. | Stripe |
| Deletion records: a job with your account and workspace IDs, request time and state, and a restore-journal entry holding a hash of that request | To complete your deletion within its deadline and to re-apply it if a backup is ever restored. | Your deletion request |
| Support correspondence | To answer you. | What you send us |
Prompt text is not processed. No shipped version of Ork Meter sends the text of your prompts anywhere. If Plus classification is enabled in future, it will require your explicit consent on a separate screen and a privacy screen before any external processing, and this policy will be updated to name the processor and its retention terms before any prompt is sent.
4. Ork Bot for Discord
Ork Bot is a public Discord application that answers the /ork about, /ork signup and /ork help commands. Every reply is visible only to the person who ran the command.
- What it receives. Discord sends each command to Ork Meter with the fields Discord includes in an interaction. Ork Bot reads only the interaction type and the command name. It does not read, use or store your Discord user ID, username, server ID, channel ID, member list or any message.
- What it stores. Nothing about you or your server. The only record of a command is a shared per-minute admission counter that contains no Discord identifiers, and a log line naming the interaction type and the command name.
- What it never does. It sends no direct messages, requests no permissions, uses no privileged intents, and never uses Discord data to train or improve any AI or machine-learning model. It never runs code, agents or tools on anyone's behalf.
- Future features. Linking a Discord user to an Ork Meter account is planned. Before that launches, this policy will describe exactly what is stored (we expect a Discord user ID mapped to your account, which you could remove at any time) and how to delete it.
- Deletion requests. Because Ork Bot stores no Discord data today, there is nothing to delete. If you believe we hold Discord data about you, email edos-labs@edos.io and we will respond.
5. How we use data
We use account data to authenticate you, operate your workspace, show your usage reports, enforce plan and free-tier limits, process payments when enabled, provide support, secure the service and comply with law. We do not sell personal information, broker it, or share it with third parties for their own purposes. We do not use your data to train AI models.
6. Who else processes data (subprocessors)
We share data only with the providers below, each for the purpose stated, and when the law requires it. We have no other subprocessors. If we add one, we update this table before it processes your data.
| Provider | Purpose | Location | Status |
|---|---|---|---|
| Amazon Web Services, Inc. | Hosting: database, compute, API gateway, encryption keys, secrets, logs, scheduling | United States (us-west-2) | In use |
| GitHub, Inc. | Sign-in. GitHub verifies your identity under its own privacy policy and gives us your numeric user ID. | United States | In use |
| Discord Inc. | Delivers slash commands to Ork Bot and shows you its replies, under Discord's own privacy policy | United States | In use |
| Stripe, Inc. | Payments for paid plans: hosted checkout, card details, billing address, tax calculation, invoices | United States | When paid plans are enabled |
Sign-in through Google is supported by the software but is not offered on orkmeter.com today; if we enable it, Google LLC will be listed here first.
7. Where data is stored and how it is protected
Ork Meter runs on Amazon Web Services in the United States (us-west-2). Stored data is encrypted at rest with AWS-managed keys and in transit with TLS. Each workspace is isolated by the application within a shared database; we do not claim per-customer keys. Helper and session credentials are stored only as hashes, request bodies are not logged, and point-in-time backups are kept for 35 days. We have not obtained a SOC 2 report.
8. Retention and deletion
| Data | Kept for |
|---|---|
| Usage metadata, aggregates and work records | While your account exists. We do not currently apply a fixed expiry to usage records; if we introduce rolling retention, we will announce it here first. |
| Native usage counters | Latest export per feed, expiring one year after receipt |
| Sessions, sign-in flows, pairing tickets, admission counters | Removed automatically when they expire: browser sessions after 15 minutes, sign-in flows and pairing tickets after 10 minutes, admission counters within three days |
| Helper credentials | Until you revoke them, and at most 30 days from issue |
| Account deletion request | Access is revoked immediately. Active data is purged on a schedule within 7 days. The completed job record expires 36 days later. |
| Backups | Expire within 35 days. Deleted data may persist in backups until then; deletion is not immediate removal from backups. A journal entry holding a hash of your deletion request is kept so the deletion can be re-applied after any restore. |
| Billing records (when paid plans are enabled) | Plan, period and Stripe references are retained after account deletion as accounting records, separately from your workspace data |
| Prompts | Never stored |
Deleting your account cancels any subscription immediately, without an automatic refund.
9. Your choices
- See and export. Your dashboard shows your usage and offers a usage export and a workspace snapshot. These are your reporting data, not a complete archive of every record.
- Revoke a helper from your account at any time; it stops sending usage.
- Delete your account from your dashboard. You re-verify your sign-in, confirm, and the deletion proceeds as described in section 8. You can check its status afterwards.
- Remove Ork Bot from your Discord account or server through Discord's settings.
- Ask us at edos-labs@edos.io for a copy of your data, for deletion, or with any question about this policy. We respond to every request and do not treat you differently for making one.
10. Children
Ork Meter and Ork Bot are not directed at children. You must be at least 18 to create an account, and Discord requires its users to be at least 13. We do not knowingly collect data from children; tell us if you believe we have.
11. Changes and contact
We will post changes here with a new date. Changes that affect Ork Bot are reflected in the Discord developer portal link to this page. Questions: Enterprise DevOps Solutions LLC · edos-labs@edos.io · orkmeter.com/support.
This policy may be revised; material changes are announced on this page.