Legal
Privacy Policy
This Privacy Policy explains how TestMyApps handles information when you visit testmyapps.app, create an account, use managed Android testing or our community testing features, make a purchase, or contact support.
1. Information you provide
The information we process depends on the features you use.
- Account information: your name, email address, sign-in provider, account role, and profile details. Email/password and Google sign-in are handled through Firebase Authentication.
- Testing requests: app name, version, package or store details, closed-test opt-in links, access instructions, test-account credentials you choose to provide, and the package or testing scope you select.
- Testing records: assignments, participation confirmations, device details supplied by testers, feedback, issue descriptions, screenshots, uploaded files, and closeout or functionality reports.
- Community features: apps you post, testing-circle memberships, participation records, feedback, and messages you share through those features.
- Support and billing: enquiries, chat messages, attachments, order and payment identifiers, purchased credits, transaction status, and refund correspondence. Checkout providers collect payment and billing details directly; we do not store full card numbers or card security codes.
2. Information collected through the service
Our systems and integrated services also process technical information.
- Sign-in and security records can include IP address, browser or device information, session identifiers, and timestamps.
- Public-site measurement can include pages visited, referral and campaign information, advertising click identifiers, browser identifiers, and interactions such as plan selections and support-link clicks.
- Where enabled, purchase measurement can include order value, currency, package details, attribution identifiers, and a hashed email address used to match a conversion. Hashing does not make this information anonymous.
- The companion Android app can register a notification token and device label to deliver notifications. You can control notification permission in your device settings.
3. How we use information
We use information to deliver the services you request and operate the platform.
- Create and secure accounts; authenticate users; manage sessions and permissions.
- Arrange tester access, coordinate testing runs, monitor participation, investigate issues, and deliver feedback and reports.
- Operate community testing, messages, and relevant notifications.
- Process orders, allocate credits, reconcile payments, handle retest and refund requests, and maintain necessary transaction records.
- Respond to support requests, send account and service emails, prevent abuse, troubleshoot the service, and meet applicable legal obligations.
- Understand website usage and measure advertising and purchases through the analytics and advertising integrations described below. Where applicable law requires a legal basis, the relevant basis depends on the activity, including providing the requested service, legal obligations, legitimate operational interests where permitted, or consent where required.
4. Cookies, browser storage, and advertising measurement
The website uses cookies and similar browser storage for sign-in, preferences, chat sessions, and measurement. Different tools have different purposes.
- Essential account features use session cookies and Firebase sign-in persistence. Preference storage can remember settings such as language or theme. Blocking this storage can prevent sign-in or other requested features from working.
- Google Analytics and Google Ads integrations, when configured on the live website, measure public-site visits and campaign performance. They can process cookie identifiers, IP and device information, referral data, and advertising click IDs. The public-page tracker excludes private workspace routes; purchase and attribution records can still be processed separately.
- Meta Pixel (Facebook/Instagram ads), when configured on the live website, measures public-site visits and Meta campaign performance. It can process cookie or device identifiers, IP and browser information, pages viewed, and Meta advertising click identifiers (including from Facebook and Instagram ads). The public-page tracker excludes private workspace routes. Meta may use this information to deliver, measure, and improve ads under Meta’s own policies.
- Crisp powers live chat and can initialize when the page loads, before you open a conversation. Its session cookies and technical information support chat continuity and security. See the Crisp cookie policy.
- You can block or clear cookies through your browser; manage Google advertising preferences through My Ad Center; and manage Meta advertising preferences through Meta’s Ad Preferences or your Facebook/Instagram settings. The Google Analytics opt-out add-on is another available control. These controls have different scopes and do not necessarily stop all processing or remove existing records.
- For details about information Google receives, see How Google uses information from sites and apps. For Meta, see Meta’s Privacy Policy and Cookies Policy. This policy describes data handling; it is not a substitute for any consent that applicable law requires.
5. Who receives information
We share information needed to operate the service, fulfil your requests, and meet applicable obligations. We do not sell your submitted apps, testing reports, or support messages.
- Assigned testers and authorized staff receive app access instructions, relevant test credentials, tasks, and testing records needed for their work. Developers receive participation information, feedback, and reports relevant to their testing runs.
- Information you post in a community area is visible to the participants that feature allows. Avoid posting private credentials, personal user records, or confidential material in community listings or public support channels.
- Google/Firebase supports authentication and app notifications; Google Analytics and Google Ads support measurement where enabled. See Firebase privacy information and Google’s Privacy Policy.
- Meta Platforms supports Meta Pixel advertising measurement where enabled on the public website. See Meta’s Privacy Policy.
- Dodo Payments handles checkout and payment-related processing, including transaction, fraud, and tax functions. Its own terms and privacy policy apply to information it collects.
- Cloudflare R2 stores uploaded testing files and reports. Hosting, database, and transactional email providers process information needed to run the platform. Email delivery may use Resend or the configured email provider.
- Crisp processes live-chat information. If you contact us through WhatsApp, Telegram, or email, the provider of that channel also processes your messages and contact details under its own policies.
- We may disclose relevant records when required by law or necessary to address fraud, abuse, disputes, or security incidents.
6. App access and test data
Use dedicated test accounts and sample data wherever possible. Do not send your personal Google account password, Play Console owner credentials, payment-card details, or unnecessary personal information about your app’s users.
- You remain responsible for your app’s own privacy notice, permissions, and collection of data from testers. Our policy covers TestMyApps; it does not replace the privacy policy for an app submitted for testing.
- If you provide access credentials, limit their permissions to the testing task and revoke or rotate them after the run. Testers need sufficient access to perform the agreed testing.
7. Storage locations and security
We use authentication, access permissions, HTTPS, and controlled file access to protect information. No internet service or storage system is completely secure.
- Our providers and authorized participants may process information in countries other than your own. Provider locations and the services used can affect where information is handled; we do not promise storage exclusively in India.
- Where applicable law requires safeguards for an international transfer, the relevant transfer arrangements must meet those requirements. Contact us if you need information about the handling of a particular category of data.
8. Retention and account deletion
We retain information for the purposes described here, taking account of active accounts and testing runs, support needs, transaction obligations, security, and disputes. Different records and providers can have different retention periods.
- You can request account deletion through our account-deletion page, including without signing in or reinstalling the app. Send the request from the email connected to your account; if you cannot access it, explain this so support can verify ownership another way.
- As described on that page, verified requests are normally completed within 7 days. The request covers your account and associated profile, testing, community, message, and uploaded data, subject to limited records that must be retained.
- Limited transaction, fraud-prevention, security, or legal records may remain where required or needed for an active dispute. Backup copies and records held by independent providers may not disappear at the same time as your active account. Contact support about a specific file, conversation, or provider record you want removed.
9. Your choices and privacy requests
Contact support@testmyapps.app to ask about your information, request access or correction, or request deletion. We may verify your identity before acting.
- Depending on the laws that apply to you, you may also have rights to restrict or object to processing, obtain a portable copy of information, withdraw consent where processing relies on it, or complain to the relevant authority.
- Tell us which account and information your request concerns. We will explain any applicable limits, such as records needed for legal obligations or an unresolved transaction.
- You can manage app notifications through device settings and browser storage through browser settings. Withdrawing consent does not affect processing already lawfully carried out.
10. Children
TestMyApps accounts and testing services are intended for adults aged 18 or older. If you believe a child has provided personal information to us, contact support so we can investigate and address it.
11. Changes to this policy
We will update the date above when this policy changes and provide notice of material changes through an appropriate service or account communication where required. A policy update does not replace consent where new processing requires it.
12. Contact
For privacy questions or complaints, email support@testmyapps.app or use our contact page. For account removal, use the account-deletion instructions.
Questions about policy or terms?
If you need clarification on data handling, billing, or platform usage, reach out and we'll point you to the right answer quickly.
Contact support