Privacy policy

Who runs ASOClimb

ASOClimb is operated by Approtic Solutions Private Limited, H.No. 8-206-138/1680, MC Dowel Colony, Boduppal, Hyderabad, Telangana 500092, India. This policy covers asoclimb.com and the ASOClimb workspace. Questions about it, or any request below, go to support@asoclimb.com.

What we collect

Only what the product needs to work. Advertising measurement is optional and runs only after you allow it.

• Account: the name, email address and profile picture your sign-in provider (Google or Apple) returns when you first sign in. We never receive or store your password.
• Workspace content: the apps, keywords, competitors and storefronts you choose to track, and the settings you save.
• Research history: the ranks, chart positions, suggestions and listing details ASOClimb records for the apps and keywords you track, kept in your workspace so you can see how they change. This is information about apps, not about people.
• Billing: your subscription status and the identifier our payment provider assigns you. Card details are entered on the provider’s own checkout and never reach ASOClimb.
• Connected services: if you connect RevenueCat, the API key you provide (encrypted at rest) and the metrics and purchase events RevenueCat sends us for your project.
• Operational logs: request identifiers, timestamps and error details, used to run and debug the service.

Why we can use it

To provide the service you asked for (performing our contract with you), to keep it secure and working (our legitimate interest), and to meet tax and accounting obligations (legal obligation). We do not rely on consent for any of the processing above, and we do not process special-category data.

Who else sees it

We do not sell your data or use it to train models. The only thing we share with an advertiser is the measurement described in the last entry below, and only if you allow it. We use these processors, and no others:

• Cloudflare and Amazon Web Services — infrastructure providers. Our infrastructure providers receive only storefront queries and the data needed to run the service, never your payment details.
• Dodo Payments — subscription checkout and payments, as merchant of record.
• Resend — delivery of the account, support and alert emails you have enabled.
• Google and Apple — only to authenticate your sign-in, at your request.
• X (Twitter) — advertising measurement, and only if you allow it. Their tag runs in your browser and tells X that you visited ASOClimb, which reveals your IP address and browser to X in the way any request to their servers would. Our servers send X nothing about you.

AI assistants and MCP connections

ASOClimb can be connected to AI assistants such as Claude, ChatGPT, Cursor and Codex through its MCP server. A connection is created only when you approve it on an ASOClimb consent page (or create an API key yourself), and it is scoped to the single workspace you approve it for.

When an assistant calls an ASOClimb tool on your behalf, the data that tool returns — the apps, keywords, ranks, competitors, charts, inspections and usage figures of that workspace — is sent to that assistant. The assistant’s provider handles it under their own privacy policy. ASOClimb receives only the tool call itself (the tool name and its arguments); it does not receive, read or store your conversation, prompts, memories, files or anything else from the assistant.

A connection you approve without write access can only read. With write access the assistant can track or untrack apps and keywords, add competitors, and run inspections, autocomplete and niche analyses that count against your plan’s monthly allowance. Every call is counted and shown under Account → Developer, and you can disconnect any assistant there at any time; its tokens stop working immediately. Access tokens expire after an hour and refresh tokens after 30 days of disuse; only hashes of tokens are stored, never the tokens themselves.

How long we keep it

These windows are enforced automatically; nothing is kept "just in case".

• Store observations and rank history: 400 days.
• Research history (inspections, niche analyses, autocomplete runs): 365 days.
• Analytics and crash events sent by our SDK, if you use it: 180 days.
• Account and workspace records: for as long as your account exists, then deleted within 30 days of your deletion request, except records we must keep for tax purposes.

Your rights

You can ask us for a copy of your data, correct it, delete it, or object to how we use it. Email support@asoclimb.com, or raise a ticket from Support inside the app, and we will respond within 30 days. You can delete your workspace at any time from inside the app, which removes its content on the spot. If you are in the UK, EU or India and are unhappy with our response, you may complain to your data protection authority.

Security

Credentials you give us for connected services are encrypted at rest. Sign-in sessions are protected against tampering, and access to live customer data is limited to the operator. No system is perfectly secure, and we will tell affected users without undue delay if a breach puts their data at risk.

Cookies

We set one cookie to keep you signed in, and one short-lived cookie during the sign-in handshake. Neither can be switched off, because without them you cannot sign in. We run no analytics cookies of any kind.

If you allow advertising measurement, X (Twitter) sets its own cookie through the tag described above. In the EEA, the United Kingdom and Switzerland that tag is not loaded at all until you have said yes — declining means it never runs, rather than running and then stopping. In every country it stays off until you allow it. If your browser sends a Global Privacy Control or Do Not Track signal we treat that as a refusal and do not ask.

Your answer is remembered in this browser for 90 days, after which we ask again. To change it sooner, clear this site’s stored data in your browser and we will ask on your next visit. Declining changes nothing about how the product works.

Changes

If we change this policy in a way that affects you, we will say so in the app before the change takes effect. The date at the top is the last revision.