Legal
Terms of Service
The terms that govern your use of the MobileAiProxy hosted AI proxy, the limits the policy engine enforces, and how billing works.
Last updated June 22, 2026
The service
MobileAiProxy is a hosted, OpenAI-compatible proxy that sits between your app and the AI model providers you choose. It verifies your end users with their own auth provider (Firebase or Supabase), keeps your provider keys server-side, routes traffic through our hosted gateway, and records usage and cost per app, user, and entitlement.
These Terms of Service form a binding agreement between you (the account holder operating one or more apps) and MobileAiProxy. By creating an account, adding a provider key, or sending a request through the proxy, you accept these terms.
Accounts and your end users
You are responsible for the security of your account, your dashboard credentials, and any provider keys you add. You confirm that you are authorized to use each provider key you upload and that doing so does not breach your agreement with that model provider.
Your app end users are your users, not ours. The proxy verifies their tokens and enforces the limits you configure, but you remain responsible for your relationship with them, including obtaining any consent required to send their content to AI model providers.
Acceptable use
You may not use the proxy to send content that is unlawful, that infringes the rights of others, or that violates the usage policies of the underlying model providers your traffic is routed to. Provider policies apply on top of these terms because requests are forwarded to those providers.
You may not attempt to bypass the policy engine, exfiltrate other tenants' data, probe for vulnerabilities without authorization, or use the proxy to resell raw model access in a way that circumvents provider terms.
Policy engine and limits
Each app defines model policies per user category and endpoint. The policy engine evaluates every request before any provider spend starts and can block it for an unallowed model, a disabled policy, a per-request token cap, a daily or monthly request limit, or a daily or monthly cost budget.
Quota errors return HTTP 429 with standard RateLimit headers, and other policy errors return HTTP 403. These limits are a feature you configure to protect your own spend; they are not a guarantee of provider availability, latency, or output quality.
Billing and plans
Subscription plans are billed through Dodo Payments, our merchant of record. Plan tier governs app count and control surface, including whether per-app provider key overrides are available. Model provider usage itself is billed by those providers against the keys you supply; MobileAiProxy does not resell model tokens.
Fees are charged in advance for the billing period and are non-refundable except where required by law. We may change plan pricing on a going-forward basis with notice through the dashboard or by email.
Disclaimers and liability
The service is provided on an as-is and as-available basis. We do not warrant that the proxy or any upstream model provider will be uninterrupted, error-free, or fit for a particular purpose. AI outputs are generated by third-party models and may be inaccurate; you are responsible for how you use them.
To the maximum extent permitted by law, MobileAiProxy is not liable for indirect, incidental, or consequential damages, and our total liability for any claim is limited to the fees you paid for the service in the three months before the event giving rise to the claim. We may suspend or terminate accounts that breach these terms.
Questions about these terms? See our Privacy Policy and Security pages.