ASO.dev Terms of Service: Subscriptions, API, and Usage Rules
Definitions
Section titled “Definitions”“Application” means the ASO.dev application and related services.
“Subscription” means the paid features of the Application.
“Fees” means the charges associated with a Subscription.
“Company” means ASO.dev LLP.
“API” means the ASO.dev application programming interface, which may be made available to users, teams, or partners for automation, integrations, and access to ASO.dev data under these Terms and any additional access rules.
“API Credits” means units of API usage that may be consumed when requests are made to the ASO.dev API.
Payment Terms
Section titled “Payment Terms”The Application offers products and services for purchase, including Subscriptions. You agree to pay all Fees associated with your Subscription according to the payment terms and pricing policy in effect at the time of purchase.
Payment Processing
Section titled “Payment Processing”We use third-party payment processors to handle payments made through the Application. By making a payment, you agree to provide accurate payment information and authorize the payment processor to charge your payment method for the full amount of the Fees. We are not responsible for errors or issues that occur during payment processing.
Automatic Renewal
Section titled “Automatic Renewal”Your Subscription automatically renews at the end of the current subscription period for the same term and at the then-current price, unless you cancel before the end of the current period. You authorize us to charge your payment method for renewal Fees.
Cancellation and Refunds 🔄 (Updated 2024/12/07)
Section titled “Cancellation and Refunds 🔄 (Updated 2024/12/07)”You may cancel your Subscription at any time by contacting our support team. After cancellation, access to paid features remains active until the end of the paid period. Please note that we do not provide refunds for already paid Subscriptions.
A free trial is available only once. We reserve the right to deny a free trial without explanation. If you attempt to reuse a free trial, we may reject the attempt and charge the Subscription fee to your payment method.
User and Application Blocking 🔄 (Updated 2024/12/07)
Section titled “User and Application Blocking 🔄 (Updated 2024/12/07)”We reserve the right to permanently block a user and any associated applications if these Terms are violated or for any other reason determined by our team.
We also reserve the right to deny access to the service without providing an explanation.
Use of the ASO.dev API 🔄 (Added 2026/05/01)
Section titled “Use of the ASO.dev API 🔄 (Added 2026/05/01)”The ASO.dev API is an additional service capability. It does not replace an ASO.dev Subscription, user seats, the product interface, projects, reports, settings, or other features intended for users working inside the service.
API access may be provided only with an active ASO.dev Subscription and only under terms determined by the Company. The Company may decide which plans, users, teams, partners, regions, and use cases are eligible for API access.
API Beta and Availability
Section titled “API Beta and Availability”The API may be provided in beta, test mode, or limited access mode. During beta, the API may be unstable, temporarily unavailable, return errors, or be subject to limits on speed, request volume, methods, data scope, and available functionality.
The Company does not guarantee continuous API availability, uninterrupted operation, error-free performance, backward compatibility, unchanged methods, response formats, limits, prices, billing rules, or access terms. During beta, the Company does not provide a public SLA, guaranteed response time, guaranteed recovery time, or guaranteed API availability level.
The Company may change, limit, suspend, or discontinue individual API methods at any time, change request and response structures, introduce new limits, change request costs, change how API Credits are consumed, and modify API access terms.
API Tokens and User Responsibility
Section titled “API Tokens and User Responsibility”API access is authorized with API tokens. Each user may have their own API token for authorizing requests. The user is responsible for the security, storage, and use of their API tokens, and for all actions performed with them.
The user agrees not to share API tokens with third parties, publish them publicly, place them in public repositories, use them in insecure environments, or delay notifying the Company about a possible leak or unauthorized use of an API token.
The Company may revoke, block, or replace an API token if there is reason to believe that the token has been compromised, is being used in violation of these Terms, creates excessive load, threatens service security, or violates the rights of the Company, users, partners, or third parties.
API Credits, Expiration, and Refunds
Section titled “API Credits, Expiration, and Refunds”API requests may consume API Credits. API Credits may be provided or purchased in packages for a defined period, such as one month, one year, or another period determined by the Company.
Unused API Credits expire when the relevant package period ends, unless an individual agreement or written confirmation from the Company explicitly states otherwise. Refunds are not provided for unused, expired, blocked, or cancelled API Credits.
If API access is limited, suspended, or terminated because of a violation of these Terms, API abuse, suspicious activity, attempts to bypass restrictions, use of the API outside its intended purpose, or other unfair behavior, unused API Credits will not be compensated or refunded.
The Company may change the price of API Credits, credit packages, consumption rules, expiration periods, limits, available methods, and other commercial API terms. These changes may apply to future purchases, renewals, new packages, or, when required for service security, stability, or economics, current API usage.
Allowed and Prohibited API Use
Section titled “Allowed and Prohibited API Use”The API is intended for automating the user’s or team’s own workflows, integrating ASO.dev with internal tools, reporting, analytics, agents, AI scenarios, and other agreed use cases.
You may not use the API, ASO.dev data, or API results to create, develop, support, train, enrich, or promote a competing service, data marketplace, database, analytics platform, ASO tool, app monitoring tool, or any product that reproduces, replaces, or competes with ASO.dev functionality.
You also may not:
- resell, sublicense, publish, mass distribute, or transfer ASO.dev data to third parties without the Company’s written consent;
- bypass API limits, restrictions, authorization, billing, or technical protection mechanisms;
- use the API for scraping, bulk copying, database reconstruction, service mirroring, or data extraction outside the agreed use case;
- create excessive, harmful, unstable, or disproportionate load on ASO.dev infrastructure;
- use the API in violation of applicable law, third-party rights, app store rules, platform terms, or these Terms.
If the Company detects or reasonably suspects prohibited API use, the Company may, without prior notice, limit, suspend, or terminate API access, block API tokens, cancel API Credits, deny future API access, and/or block the user’s account or related applications.
Partner Integrations and Source Attribution
Section titled “Partner Integrations and Source Attribution”The Partner API and external integrations may be provided only by separate agreement between the Company and the partner. The terms of such integration, including data scope, limits, cost, minimum payment, test run, support requirements, and the format for presenting ASO.dev as a data source or technology partner, are agreed separately.
The Company may require that users of a partner integration can understand that the data, functionality, or part of the functionality is provided using ASO.dev. The exact format is agreed based on the integration scenario, partner interface, and the parties’ agreement.
Limitation of Liability for API Use
Section titled “Limitation of Liability for API Use”The user understands and agrees that the API may be temporarily unavailable, delayed, changed, return incomplete or incorrect data, be limited, or be discontinued. The user uses the API at their own risk and is solely responsible for their integrations, internal processes, automation, reports, decisions, actions, and omissions based on API data or results.
To the maximum extent permitted by law, the Company is not liable for any damages, costs, losses, penalties, lost profits, data loss, business process failures, downtime, missed deadlines, integration errors, user or third-party decisions, or any direct, indirect, incidental, special, punitive, or consequential damages arising from or related to API use, inability to use the API, temporary API unavailability, API changes, API discontinuation, API errors, changes to limits, prices, methods, response formats, or access rules.
The user is responsible for maintaining fallback processes, error handling, limit control, integration monitoring, data verification, API token protection, and measures for temporary API unavailability.
Intellectual Property
Section titled “Intellectual Property”All content and materials provided through the Application, including text, graphics, logos, images, and software, are owned by us or our licensors and are protected by copyright, trademark, and other intellectual property laws. You may not reproduce, modify, distribute, or create derivative works based on any content or materials provided through the Application without our prior written consent.
Limited Liability
Section titled “Limited Liability”To the maximum extent permitted by law, we and our affiliates, officers, employees, and agents are not liable for any direct, indirect, incidental, consequential, or punitive damages arising from or related to your use of, or inability to use, the Application, even if we have been advised of the possibility of such damages. Our total liability to you for all damages, losses, and causes of action will not exceed the amount of six monthly payments made by you to access or use the Application.
Indemnification
Section titled “Indemnification”You agree to indemnify and hold us, our affiliates, officers, employees, and agents harmless from any claims, damages, liabilities, and expenses, including reasonable attorneys’ fees, arising from your use of the Application or your violation of these Terms.
Governing Law and Jurisdiction
Section titled “Governing Law and Jurisdiction”These Terms are governed by and construed in accordance with the laws of the jurisdiction where the Company is located. Any legal action or proceeding arising from or related to these Terms will be brought exclusively in the courts of that jurisdiction.
Entire Agreement
Section titled “Entire Agreement”These Terms constitute the entire agreement between you and the Company regarding the Application and supersede any prior agreements or understandings related to the subject matter of these Terms.
Changes to These Terms
Section titled “Changes to These Terms”We may modify these Terms at any time, so please review them periodically. If we make material changes, we may notify you by email or by posting a notice in the Application. Your continued use of the Application after changes to the Terms means that you accept the updated Terms.
Severability
Section titled “Severability”If any provision of these Terms is found to be invalid or unenforceable, the remaining provisions will remain in full force and effect.
Waiver
Section titled “Waiver”Our failure to enforce any right or provision of these Terms will not be considered a waiver of those rights.
License Limitations and Device Usage 🔄 (Added 2025/04/24)
Section titled “License Limitations and Device Usage 🔄 (Added 2025/04/24)”An ASO.dev Subscription is provided on a seat-based model, meaning a license for one user. This model allows use on multiple devices, but the Company reserves the right to limit the number of devices on which one Subscription may be used simultaneously.
Device Limitations
Section titled “Device Limitations”- The Company may introduce a “1 user - 1 device” limitation for any Subscription at any time.
- If such limitations are introduced, the user will be able to rebind the license to another device.
- The number of rebindings may be limited, but will not be less than one rebinding per calendar month.
License Rebinding
Section titled “License Rebinding”- License rebinding to a new device will be available through the user’s account or by contacting support.
- After the license is rebound to a new device, access from the previous device will be terminated.
- Frequent rebindings may be treated as an attempt to bypass license restrictions and may result in temporary or permanent account blocking.
Subscription Sharing
Section titled “Subscription Sharing”- Sharing one Subscription between multiple users is prohibited and constitutes a violation of these Terms.
- The Company may monitor suspicious activity indicating Subscription sharing and take appropriate measures.
We work to provide a strong service at an attractive price and appreciate your understanding. Our goal is to make ASO.dev tools accessible while maintaining service quality and fair pricing.
For additional information about license limitations or questions about using a Subscription on multiple devices, please contact support at info@aso.dev.
Contact Us
Section titled “Contact Us”If you have any questions or concerns about these Terms, please contact us at info@aso.dev.
Effective Date
Section titled “Effective Date”These Terms, as updated on 2026/05/01, are effective from the moment they are published.