Draft for review. Legal operator disclosures, tax treatment and retention details remain under review. Paid checkout is disabled until publication.
Scope and operator
This draft describes how M82 Router, offered under the M82 Labs brand, handles personal information. The responsible legal operator, contact address and effective date must be completed before publication.
Information we process
We process account identifiers, email and membership information; phone verification status, a protected phone digest and declared age band; API key identifiers and protected key hashes; request identifiers, model choices, usage, costs, timestamps and security outcomes; and payment amounts, fees, credits and provider references. Raw date of birth is discarded after age classification. A phone digest and age band can still be personal information.
Prompt and response processing
To run inference, your prompts and relevant request content are processed by M82, third-party routing providers and the selected model provider. A third-party moderation provider separately receives supported input and output content for safety screening, even when another provider supplies the model. Do not submit personal or confidential information unless you have permission and have reviewed the applicable data-processing disclosures.
Purposes
We use information to authenticate accounts, route and bill requests, verify payments, operate support, investigate abuse, maintain reliable service and meet legal obligations. We do not treat a financial purchase or security verification as consent to marketing.
Service providers and international processing
We use third-party service providers for authentication and databases, SMS phone verification, hosting, rate controls, payment processing, AI routing, model inference and content moderation. We share information needed for these functions, including supported request and response content with routing, model and moderation providers. Processing may take place outside Nepal. Provider retention and training practices vary by model, account settings and contract; we do not promise universal zero retention or no training.
Retention
M82 safety-event metadata is configured for a 30-day retention window; those records are designed not to contain raw prompts or responses. Operational logs, account and payment records have separate purposes and retention requirements. Financial records and policy acceptance snapshots may be retained to meet accounting, dispute and legal obligations. Exact financial and account retention periods must be approved before publication. Upstream providers have their own retention rules.
Security and disclosure
We restrict database and credential access, verify payment notifications server-side and apply rate and abuse controls. No system is completely secure. We may disclose relevant information to service providers, competent authorities where legally required, or to investigate fraud and security incidents. Access logs and account records help investigations but do not guarantee identification of a real-world person.
Your choices and rights
Contact support to request access, correction, account deletion or review of a restriction. We may verify your identity before responding and retain records where legally required or necessary for unresolved transactions. Review model-provider settings before sending sensitive content. Essential authentication cookies support account access. Additional analytics or marketing features require a separate disclosure and any consent required by law.
Public usage statistics
We record request metadata, including the selected model, token counts and timing, for billing, operating and securing M82 Router. When you use the service, these metadata may also contribute to combined statistics across accounts, including public model rankings, token totals, request counts, speed summaries and prompt-size ranges. This does not require a separate analytics opt-in. Public statistics do not include prompts, responses, names, contact details, account or API key identifiers, individual request records, or private billing details. We publish only rounded aggregate figures for groups meeting a minimum number of distinct accounts, and withhold smaller groups. These safeguards reduce the risk of revealing individual usage, but comparisons between overlapping time periods may still allow approximate inferences. Your account-level usage and billing records remain private and are used as described in this policy.
Updates and contact
Material privacy changes will be communicated as appropriate. The published version must identify the responsible operator, privacy contact and effective date.