Privacy Policy

Last updated: 25 September 2026

This policy explains how we handle personal data when you visit appsqeez.com, use the AppSqeez desktop application, purchase a subscription, or contact us. It covers our own processing; services you connect have their own privacy policies.

At a glance

• AppSqeez stores your workspace on your device. Online features still send the data needed to provide those features.
• Our backend processes installation and license identifiers, ASO requests, and shared store observations.
• Polar handles checkout and payments. We do not receive your full payment card details.
• AI, translation and connected agents can receive project content when you use those integrations.
• We do not sell your personal data or use it for targeted advertising.

1. Who is responsible

The controller for the personal data described in this policy is:

2. Data on your device

AppSqeez stores tracked apps, keyword lists, ranking history, competitors, listing drafts, screenshot projects, preferences and configured credentials in local application storage. You do not need a separate AppSqeez user account to start using the application. Local storage is not an AppSqeez cloud backup or synchronization service.

A local workspace does not mean every operation stays offline. Store lookups, shared ASO features, licensing, AI, translations and integrations involve network requests as described below. Files or logs you choose to send to support also leave your device. Backups and exports you create are stored wherever you choose; any device or cloud backup service you use is governed by its own settings and policy.

3. Data processed by our services

Installation and licensing

The app registers with our backend and receives an installation identifier and authentication token. Registration can include the app version and platform. When you activate, validate, deactivate or manage a license, the app sends the license key and, where applicable, an activation identifier to our backend, which communicates with Polar. License status and validation records help us provide paid features and prevent misuse. Validation takes place at startup and periodically while the app is running.

These identifiers are pseudonymous, not necessarily anonymous: they distinguish an installation and can be associated with a license or purchase. The current installation registration does not send a hardware fingerprint. Network requests also expose an IP address and technical request information to the receiving service.

Shared ASO data

AppSqeez requests and contributes store data through our backend. This can include searched keywords, app and store identifiers, country and language selections, ranking results, collection times, leaderboard positions, and public store metadata such as titles, descriptions, icons and screenshot URLs. Apple Ads popularity lookups also send the keyword, app identifier and selected storefront or market needed for the lookup.

We use these requests and observations to supply shared caches, ranking history, leaderboards and keyword suggestions, including suggestions for other AppSqeez users. A keyword you research and the public results associated with it may therefore contribute to shared features. This is not an upload of your complete private workspace. However, requests authenticated by an installation token are not treated as inherently anonymous. Avoid entering personal or confidential information into keyword searches.

Public store listings can contain personal data, such as an individual developer's name or contact information. Its source is the relevant Apple App Store or Google Play listing, including observations submitted by AppSqeez installations. Public availability does not remove applicable data protection rights.

Purchases and support

Polar collects checkout information such as your email, billing name and address, tax information and payment details. We can receive the customer, order, subscription and license information needed to deliver your purchase, handle support and refunds, and keep business records. Full card numbers and card security codes are handled by the payment providers, not by AppSqeez.

If you contact us, we process your email address, correspondence and any attachments or diagnostics you provide. Please remove passwords, API keys and unrelated personal data before sending a support message or log file.

4. AI, translations, store connections and MCP

• AI providers. When you use AI features, prompts, conversation context and relevant app data, listing text, keywords or images may be sent to your selected provider. Supported configurations include OpenAI, Anthropic, Google Gemini, OpenRouter, local models and compatible endpoints. Your configured API key authenticates requests to that provider. A locally running connector can still use a cloud model.
• Translation. DeepL, Langbly or your selected AI provider receives the text and language information needed to translate keywords or listings when you use that feature.
• Store connections. If you configure App Store Connect or Google Play access, the relevant provider receives authentication requests and the data required for the actions you initiate, such as retrieving or updating listing information.
• MCP and external agents. Enabling the local Model Context Protocol (MCP) server lets connected software access supported AppSqeez tools. Tools can read tracked apps, keywords, rankings and ratings, add apps or keywords, run store searches and request AI suggestions. An agent may send tool results to its own cloud service. Disable the server in Settings to stop new connections.

Integration credentials are configured on your device and used with the corresponding service; they are not needed for our shared ASO collection. External providers determine their own retention, model-training and account policies. Review those policies and your provider settings before sending sensitive content. AppSqeez cannot delete copies held independently by a provider or agent you choose to use.

5. Website, cookies and downloads

Serving the website and backend involves processing technical information such as IP addresses, requested URLs, timestamps, browser information and response or error details. Hosting and network services may keep access and security logs. The website's own code does not include advertising pixels. It reads browser platform information locally to highlight a suitable download.

Website analytics. We use Umami Cloud, a privacy-focused analytics service provided by Umami Software, Inc. (United States), to understand how the website is used and to improve it. Umami's script records general usage information such as the pages you view, the referring page, and your browser, operating system, device type and country. Umami states that its tracking code does not use cookies and that the data it collects is anonymized and contains no personally identifiable information. Umami processes this data on our behalf; see Umami's Privacy Policy.

When you start checkout through our backend, the website creates a checkout installation identifier using the platform and version value “web”, then requests a Polar checkout session. The token is used during that flow; the website does not persist it in browser local storage. Polar's checkout and customer portal have their own cookies and privacy practices. Downloads and release pages hosted on GitHub are also subject to GitHub's privacy practices. Browser controls let you manage third-party cookies and site data.

If we introduce optional tracking that requires consent, we will request it before that tracking begins and update this policy.

6. Why we process personal data

Under the General Data Protection Regulation (GDPR), we rely on the following grounds where they apply:

• Contract and steps you request before a contract (Article 6(1)(b)). Providing requested online features, checkout, license activation, subscription management and purchase support.
• Legitimate interests (Article 6(1)(f)). Operating a secure and reliable service, preventing abuse, answering general enquiries, understanding and improving how the website is used through cookie-free analytics, maintaining useful shared public-store datasets and handling legal claims. We weigh these interests against individuals' rights, including where a business customer's representative uses the service.
• Legal obligations (Article 6(1)(c)). Required accounting, tax, consumer-protection and lawful disclosure obligations.
• Consent (Article 6(1)(a)). Where we specifically ask for it, for example before introducing optional tracking requiring consent. You may withdraw consent without affecting earlier lawful processing.

Accepting our Terms or reading this policy is not blanket consent to personal data processing. You can decline optional integrations. Without the identifiers and purchase information necessary for licensing or checkout, we cannot provide the corresponding paid service.

7. Who receives data

We share data only as needed with hosting, infrastructure, email and support providers; Umami for website analytics; Polar for billing and licensing; professional advisers for business and legal obligations; and authorities where disclosure is legally required. Service providers acting on our behalf may process data only for the services they provide to us, subject to applicable obligations.

Polar also processes data for its own payment, tax and compliance purposes; see Polar's Privacy Policy. Providers you connect and GitHub may act independently under their own policies. Other AppSqeez users can receive shared store data and keyword suggestions as explained above, rather than your billing details or private workspace files.

8. International transfers

We are based in Slovakia. External services may process data outside the European Economic Area (EEA), including in the United States, where Umami Software, Inc. (website analytics) is based. Polar describes its international processing and safeguards in its privacy policy; destinations for optional AI and other integrations depend on the provider you select.

Transfers for which we are responsible must meet GDPR requirements. Depending on the recipient, this requires an applicable adequacy decision or appropriate safeguards such as the European Commission's Standard Contractual Clauses, with additional measures where necessary. Contact us for information about the recipients and safeguards applicable to your data, or to request a copy of relevant safeguards.

9. How long data is kept

• Local workspaces and exports: remain on your device or chosen backup location until you delete them. Uninstalling may leave application data or separate backups behind.
• Installation and license records: retained while needed to provide and validate access, resolve activation issues and prevent abuse. After access ends, retention depends on outstanding disputes, fraud-prevention needs and legal obligations.
• Purchase records: kept for the applicable accounting and tax retention requirements and for resolving payment claims. Polar applies its own retention obligations.
• Support and technical logs: kept as needed to resolve the enquiry, diagnose operational issues or investigate security incidents; relevant records may be retained longer for an unresolved claim or legal obligation.
• Shared store data: kept while useful for historical rankings and shared ASO features. Data that contains personal information remains subject to applicable rights and retention limits; truly anonymous statistics may be retained without identifying you.

Cancellation does not automatically erase backend records, your local workspace or copies held by third parties. We assess deletion requests against the purposes and legal requirements above and explain any records that must be retained.

10. Your rights and choices

Subject to applicable conditions, you can request access, correction, erasure, restriction of processing and portability of your personal data. You can object to processing based on legitimate interests and withdraw any consent you have given. You may also ask us to review a license or access decision you believe is incorrect. License validation automates feature access based on license status; we do not use personal profiling to make decisions with legal or similarly significant effects about you.

Email support@appsqeez.com to exercise your rights. Include enough information to locate the relevant records, such as your purchase email or installation identifier; do not send passwords or API keys. We may request proportionate identity verification. We normally respond within one month. If a permitted extension is necessary, we will explain it within that first month.

You may complain to the Office for Personal Data Protection of the Slovak Republic, or the competent supervisory authority where you live, work or believe an infringement occurred. You do not have to contact us first. You can remove local files yourself and disable optional integrations in Settings. Some in-app editing and deletion controls depend on your plan; those product limits do not restrict your statutory privacy rights.

11. Security

We use measures appropriate to the data and processing risks, including authenticated backend access. No storage or transmission method is completely secure. Protect your device, license key and integration credentials, and keep backups in a trusted location. Local storage should not be understood as a guarantee that every file or export is encrypted.

12. Children

AppSqeez is a professional tool intended for adults, not children under 18. If you believe a child has provided personal data to us, contact us so we can investigate and take appropriate action.

13. Changes and contact

We will update the date above when this policy changes. For material changes, we will provide a prominent website or in-app notice, or contact affected users where appropriate. If a change requires consent, we will request it separately. Questions can be sent to support@appsqeez.com or our postal address above. Subscription and usage conditions are set out in our Terms of Service.