User Guide

Compliance & Filings

LMU AI compliance: AI service filing, ICP filing, account data stored within China, no persisted request content, contracts, VAT invoices and DPA.

When a company procures an AI API service, legal, finance, and security each bring their own checklist. This page gathers the compliance-relevant facts about LMU AI in one place so you can check them off item by item; every entry links to a way to verify it yourself or to the detailed documentation.

Compliance at a glance

ItemStatusVerify / details
ICP filingPrimary domain lmuai.com: 京ICP备2020034311号-7MIIT filing system
Public-security filing京公网安备11010602202500号MPS filing lookup
AI service filingBeijing-LMUAI-20251201S0138Registration announcement
Account-data residencyEmail, phone number, orders and API keys stored only within ChinaData & privacy
Request-content retentionPrompts / responses never persisted; call metadata kept 90 daysData & privacy
Contracts & invoicesEnterprise tiers support procurement contracts and VAT invoicesEnterprise plans
DPAEnterprise tiers support signing a data processing agreementBusiness contact
Audit logsOptional for enterprise tiers; encrypted, access controlled by your adminsEnterprise plans
Availability commitmentEnterprise tiers: 99.5% availability target + monthly reportReliability

Filings

LMU AI holds the following filings:

Data residency and retention

The three principles that matter most to enterprises (full details in Data & privacy):

  • Account data never leaves China: email, phone number, orders, API keys and other account data are stored only within China, with no cross-border transfer
  • Request content is never persisted: prompts and model responses are released from memory once forwarding completes — never written to any database or file
  • Metadata kept for 90 days: call time, model, and token usage needed for billing and troubleshooting are retained for 90 days, stored within China

Honest disclosure on cross-border channels

Upstream model providers (Claude, GPT, etc.) run their servers overseas, so request and response bodies pass through overseas channels in transit — the necessary technical path for reaching overseas LLMs. The channels persist no data, carry no account identity, and are TLS-encrypted end to end. Do not send state secrets, trade secrets, national ID numbers, or other highly sensitive content through the API; if you have such requirements, discuss a private gateway with the business team.

Procurement and finance

  • Contracts: enterprise tiers support signing a procurement contract
  • Invoices: VAT invoices supported; submit the invoice title and tax ID when ordering or during the business contact
  • Reconciliation: the console provides usage detail, and the usage-export API enables automated reconciliation

Enterprise compliance support

The following are arranged through the business channel (email business@lmuai.com, WeChat 18599001010):

  • Data processing agreement (DPA) signing
  • Custom log-retention policies and optional audit logs
  • Private gateway deployment (request content bypasses shared channels)
  • Supporting materials for MLPS (等保), GDPR, and SOC 2 compliance inquiries

How we word this page

This page lists only items that are verified, externally checkable, or contractually committable today. For certifications or qualifications not covered here, please confirm through the business contact; the contract governs.

Getting started

Once your compliance review passes, onboarding takes three steps: create an account → choose a plan (for enterprise needs see Enterprise plans) → follow Getting started to create an API key and start calling. Pricing is per the official pricing page.

Last updated:

On this page