Privacy Policy
1. Who we are and this policy
Easyparser App Store is operated by the Easyparser team. This policy explains information processed through public marketplace browsing, developer services, hosted review and payment sessions, and payout workflows.
An independent developer may operate the app you open from a listing. That developer is responsible for its own product privacy notice and data practices. Review those materials before using an app or giving it personal information.
2. Information we process
Public browsing information can include marketplace pages viewed, searches, filters, app views, outbound clicks, browser and device data, IP-derived technical information, and optional marketplace analytics. Optional analytics are enabled only after a visitor makes an analytics choice.
Developer and listing information can include profile, contact, app listing, integration, configuration, and support information. Developer services use the main Easyparser account system.
Hosted review sessions can include a session token, app-scoped user details supplied by a developer backend, rating, comment, review status, and return URL. Public review display masks reviewer last names.
Hosted payment and payout workflows can include session and invoice records, payment outcomes, payout requests, verification status, recipient details, bank-account details, and records needed for accounting, fraud prevention, disputes, and compliance.
3. How we use information
We use information to operate public listings, developer integrations, moderation, hosted review and payment sessions, earnings records, payout workflows, customer support, security, fraud prevention, and legal or financial controls.
When optional analytics are allowed, we use aggregated and event-level marketplace information to understand feature use, diagnose performance, and improve the service. We also use information to respond to requests and enforce our terms and policies.
4. Service providers and sharing
We use service providers that support the App Store. Depending on the workflow, these can include Stripe for hosted checkout, Stripe Identity or another supported identity-verification provider for payout verification, Mercury for supported payout recipient operations, DigitalOcean Spaces for listing media, hosting and database providers, and the main Easyparser account service.
We share information with a developer only to the extent needed to operate that developer's app integration, review session, payment session, webhook, or configured return flow. We may also disclose information when required to protect users, prevent fraud, comply with law, or handle a valid legal request.
5. Cookies and browser storage
Public browsing does not require a sign-in cookie. We store an optional analytics choice in browser local storage. If analytics are allowed, a session-scoped marketplace identifier can be stored in browser session storage.
Hosted checkout and other third-party services can use their own cookies or similar technologies under their own policies. Your browser settings may allow you to manage cookies, although doing so can affect some features.
6. Retention and security
We retain information for the time needed to operate the service, maintain security, resolve requests and transactions, manage refunds or disputes, meet financial and legal obligations, and enforce our terms. Retention varies by information type and workflow.
We use reasonable technical and organizational measures designed to protect information. No online system can promise absolute security. Developers are responsible for protecting their own API keys, webhooks, app environments, and product data.
7. Your choices and requests
You can contact [email protected] to ask about access to, correction of, or deletion of your information. We handle requests subject to applicable law and our security, financial, transaction, and recordkeeping obligations.
A review, payment, or payout request may require us to retain some information while a session, transaction, dispute, verification, or accounting obligation remains open.
8. Changes to this policy
We may update this policy as the App Store, providers, or legal requirements change. The date above identifies the current version. Material changes may be communicated through the service or another appropriate channel.