Acceptable Use Policy
Use OpenApps to research, compare and cite what AI app stores publish, within your plan's limits. Don't get around limits, resell our data in bulk or attack the service.
Effective October 16, 2026Explains the acceptable use part of the Terms of Service
The short version
- Use OpenApps to research, compare, cite and build on what AI app stores publish.
- Stay within your plan's limits. Don't rotate accounts, keys or IP addresses to get more.
- Use the API or the MCP server for automated access, not automated copying of pages.
- Don't republish or resell our data in bulk without a license.
- Don't attack or overload the service. If you find a vulnerability, tell us and we'll work with you.
- Don't spam or harass developers using details from the catalog.
This summary helps you find your way. The full text below is what applies.
Contents
1.What you're welcome to do
- Read every public page, with or without an account.
- Cite, quote and chart our data with credit: “Source: OpenApps (theopenapps.com)”, with the date the data refers to and a link where the medium allows.
- Use the API and the MCP server within your limits, from your own scripts, tools and AI assistants.
- Connect ChatGPT, Claude or another AI app to your account.
- Use OpenApps for journalism, academic research, market research and client work.
- Tell us when something is wrong, at hello@theopenapps.com.
2.Respect limits and access controls
Don't:
- get around rate limits, row limits, history windows, country limits or Pro-only pages, whether by automated copying, changing requests or any other way;
- create several accounts, or use several keys or IP addresses, to get more than one account's limits;
- share your sign-in, your Pro account or your developer keys with others, or sell access to them;
- access parts of the service that aren't public or aren't yours, such as other people's accounts;
- forge headers, tokens or user agents to pass as a different client or a browser.
The limits for each plan:
| Access | Requests | Data |
|---|---|---|
| No account (per IP address) | 60 a minute | Top 100 rows of each chart, the United States only |
| Free, with a developer key or a connection | 600 a minute | 500 rows of each chart, every country, 30 days of history |
| Pro, with a developer key or a connection | 600 a minute | Every row and the full history, plus Compare, Rank history, Listing changelog and Launch lag |
The Pricing page lists what each plan includes.
3.Automated access
For automated access, use the API, the MCP server or llms.txt. They're built for it and have clear limits.
Search engines and AI assistants that fetch pages to answer people are welcome, as our robots.txt allows. Any bot must identify itself with an honest user agent, follow robots.txt, and make no more than one request a second. Don't use bots to copy data your plan doesn't include.
4.Using our data responsibly
- Credit OpenApps when you quote or chart our data.
- Reusing a substantial part of our data, such as a whole chart or country grid, a feed, raw API output or more than 1,000 rows, needs a written license. Email hello@theopenapps.com.
- Don't copy our data to build a competing database or service, or resell it.
- Don't remove or change the credit, dates or labels on our data.
- Don't present our ranks as installs, usage or revenue. A rank is a listing's position in a store.
5.Security
Don't probe, scan or test the service for vulnerabilities, run load tests against it, or try to break or bypass sign-in or other security measures, except under the security research rules below. Don't upload malware, overload the service, or interfere with other people's use of it.
Security research
We welcome reports of security problems. If you find one, email hello@theopenapps.com with “Security” in the subject. If you act in good faith, only access what you need to show the problem, leave other people's data alone, don't disrupt the service, and give us 90 days to fix it before telling anyone else, we won't take legal action against you, and we'll credit you publicly if you'd like.
6.People in our data
The catalog includes names, websites and contact details that developers publish in their store listings. Don't use them to send spam or unsolicited bulk messages, to harass or expose anyone, or to build profiles of individuals. If you contact a developer, follow the anti-spam and privacy laws that apply to you, such as CAN-SPAM, the GDPR and the UK's PECR.
7.Honesty and representation
- Don't pretend to be OpenApps, or suggest that we endorse you, your app or your product.
- Don't alter screenshots of OpenApps to show ranks or dates we didn't publish.
- Don't use OpenApps to coordinate manipulation of store rankings, such as fake reviews, installs or listings.
8.Lawful use
Follow the laws that apply to you, including sanctions and export laws. Don't use OpenApps to break the law, to infringe anyone's intellectual property or privacy, or to help anyone else do so.
9.Reporting abuse
If you see someone misusing OpenApps or our data, email hello@theopenapps.com with what you saw and any links. We review every report.
10.What happens if you break this policy
We respond in proportion to the problem. Depending on what happened, we may:
- contact you and ask you to stop;
- slow down or block requests from a key, account or IP address;
- revoke developer keys or connected apps;
- suspend or close your account;
- take legal action in serious cases.
Usually we'll contact you first. If there's an attack, a legal risk or harm to others, we may act straight away and explain afterwards. If you think we got it wrong, reply to our message or email hello@theopenapps.com, and a person will review it.
11.Changes to this policy
This policy explains the acceptable use part of our Terms of Service. We update this page when it changes, and the date at the top shows the current version.
12.Contact
Questions, abuse reports and license requests: hello@theopenapps.com.