Privacy Policy
Last updated November 20, 2026
1. The short version
MartLLM is operated by AL Global LLC, a Wyoming limited liability company (ID 2025-001810253), 30 N Gould St, Ste R, Sheridan, WY 82801, USA.
MartLLM (formerly UberLLM): the service was called UberLLM until November 2026. The new name does not change your account, credit, API keys or this policy.
We save every request you send to the API and the answer you got back, for 90 days, then delete them. You can turn this saving off for any API key in your dashboard. We use them to fix failed requests, answer your support questions and stop abuse. We keep what we need to bill you (model, tokens, cost and time) for as long as your bill needs it. We do not sell your data and do not use it to train models.
2. What we keep
Account: your email address, the time you signed up, and the IP address a sign-in code was requested from (used to stop one person opening many accounts).
Requests: for each request, the full request you sent, the answer exactly as we sent it back, which providers we tried and what each one replied, the model, the token counts, the cost, how long it took, whether it succeeded, the IP address it came from and the app name your software sends. Very large requests or answers (over 4 MB, such as big uploaded pictures) are saved only in part.
Turning saving off: each API key has a setting, “Do not save my requests and answers” (Dashboard → API keys, when you create or edit a key). For calls made with a key that has it on, we do not keep the request you sent or the answer we sent back. We still keep the rest of the record above: which providers we tried and any error each one returned, the model, the token counts, the cost, how long it took, whether it succeeded, the size of the request and answer, the IP address and the app name. We then cannot look into a wrong answer for you. Video and music jobs are the exception: each job keeps its request, so a job a provider drops can be started again. The provider that serves a request still receives it either way.
Generated files: pictures, video and audio a model makes are kept only so you can download them, then deleted: video and music about 3 hours after the job ends, image links about 15 minutes, and files you upload 24 hours.
Payments: the amount, status and payment id from our payment processor. Your card details go to the processor, never to us.
API keys are stored as one-way hashes; we cannot read them back.
Savings cards: when you press Share, we save that card’s numbers (what you paid, the list-price value, how many calls, the period) and up to three model names. Anyone with the link can see them, along with your referral code. The card has no name, email or prompts. If you turn on your public savings page, the same kind of numbers for your last 30 days are shown at one link until you turn it off. If we send you the monthly savings email, we make one card for that month so the email can show it; nobody else gets its link unless you share it. Every such email has a link that stops them.
Affiliate Program: when you sign up through someone’s link or savings card, we record who referred you. If that person is an approved affiliate, they earn a commission on the credit you buy in your first 30 days. They see your email only partly hidden (like jo***@gmail.com), when you signed up, whether you have bought credit, and the amounts. They never see your requests.
To stop people referring themselves, we compare a fingerprint of the card or PayPal account you pay with to the ones used on the affiliate’s own account. We use it only for that check, and we never show it to anyone.
If you apply to be an affiliate, we keep what you send us (your channels, links, plan, contact, notes and the screenshot) to review your application and run the program. Your payout address (a PayPal email or a wallet address) is used only to pay you.
3. Who sees your requests
To answer a request we send it to a third-party model provider (directly or through a marketplace of providers). That provider receives what you sent and handles it under its own terms and privacy policy. Pick a provider in your request if you need a specific one.
A provider may let the owner of its account read what it receives (some let the owner turn on prompt logging), so the seller that serves a request may be able to read it. To limit this, before a text request leaves MartLLM we replace the API keys, passwords, tokens and private keys we can recognise in it with tags such as [SECRET_3f9a2c1b], for every API key, and put the real values back in the answer before you get it. Each API key also has a setting, “Hide personal data from providers” (Dashboard → API keys, on by default for new keys), that does the same for email addresses, phone numbers, card numbers and public IP addresses. Names, street addresses, other free text, anything inside pictures, files or audio, and prompts for video, image and music generation are not hidden. Requests sent with your own provider key go to your own provider account unchanged.
Inside MartLLM, saved requests and answers can be read only by the small team that runs the service, and only to fix problems, answer support questions and stop abuse. They are kept apart from our other data.
4. Who else we share data with
Only the services we need to run MartLLM: our payment processors (Whop and PayPal, and Stripe for earlier purchases), our hosting and network providers (Amazon Web Services, Cloudflare), and our email sender for sign-in codes. We share data with authorities only when the law requires it.
Advertising: to show our ads to people who are likely to use MartLLM, and to stop showing them to people who already have an account, we may send Google a one-way hash of your email address (never the address itself, and never your requests or answers). Google uses it only to match it to its own accounts. To opt out, email [email protected] and we stop including you.
5. Cookies
The dashboard uses a sign-in token stored in your browser so you stay signed in.
Our pages also load measurement tags from Google, Meta (Facebook and Instagram), X and Whop. They set cookies so these services can tell us which ad or link led to a sign-up or a top-up. They see that a visit, a sign-up or a top-up happened, not your requests or answers.
6. How long we keep it
Saved requests and answers: 90 days, then deleted automatically. Calls made with an API key that has “Do not save my requests and answers” turned on are not saved in the first place. Account and billing records are kept while your account is open, and billing records for as long as tax and accounting law requires after that. The billing line of each request (model, tokens, cost, time) follows the same rule because it is your bill.
7. Your rights
You can ask for a copy of your data, ask us to correct it, ask us to delete your saved requests and answers before the 90 days are up, or ask us to delete your account. Email [email protected] from the address on your account. We answer within 30 days. Billing records we must keep by law are kept until that duty ends.
8. The MartLLM Chrome extension
The extension collects nothing about you. It has no analytics, no account and no tracking, and all of its code ships inside it.
It acts only on the pricing pages of OpenAI (openai.com, developers.openai.com) and Anthropic (claude.com, platform.claude.com) and on openrouter.ai. It is loaded on the other public pages of those sites too, because a click through to the pricing page does not reload the page; there it reads nothing, sends nothing and shows nothing. On the OpenAI and Anthropic pricing pages it reads the first line of headings, of the first cell of table rows and of code names, to find model names. On OpenRouter it reads link addresses such as /openai/gpt-4o and no text, and acts only on the model list and on model pages. Anything that is not a model MartLLM lists is dropped at once. Nothing read from a page is stored or sent anywhere.
The only request it makes is for our public price list, at most once every 30 minutes (every 5 minutes while the list cannot be reached). The request has no cookie, no key and no information about you or the page you are on. Like any web request, it reaches our server from your IP address.
It stores two things, in your browser only: a copy of the price list (used for up to 6 hours) and which sites you turned it off for. Removing the extension deletes both.
A link from the extension to our site is tagged as coming from the extension and from which of the three sites, so we can count those visits. The tag does not identify you.
9. Changes
If we change this policy in a way that matters, we will post it here and on the changelog first.
10. Contact
Privacy questions: [email protected].