Privacy notice
What we collect, and who can see it.
AppFledge coordinates Android closed testing between app developers and testers. This notice explains the personal data needed to run that exchange, including your Google Play email, device details, region and testing screenshots.
Last updated 15 September 2026
The short version
We use your information to operate the testing network. We do not sell your personal data or use testing content for advertising. Your Google Play email is shared with the developer of an app only after you agree to that sharing for the specific test.
Data we collect and why
| Data | Why we use it | Who can see it |
|---|---|---|
| Account details | Sign-in email, name, account ID and workspace preferences are used to create, secure and support your account. | You and authorised AppFledge administrators. Authentication is provided through Supabase. |
| Google Play email | The Google account used on your testing device lets an app developer add you to their Play Console closed-test list. | You, authorised administrators, and the developer of each test you consent to join. It can be downloaded by that developer as a tester-list file. |
| Device and region | Your device model, Android version and optional broad region help match coverage and describe the test results. | You, authorised administrators, and developers whose tests you join. Reports use these details to summarise coverage. |
| Testing activity | Tests joined, Play opt-in confirmation, task progress, daily check-ins, notes, reminder choices, timestamps and credit entries coordinate and evidence participation. | You, the relevant app developer and authorised administrators, subject to account and campaign access controls. |
| Feedback and screenshots | Your updates, category, rating, app build and optional check-in screenshots help the developer understand what was tested. | You, the relevant app developer and authorised administrators. Check-in screenshots are stored in a private bucket with account and campaign access controls. |
| Developer and app data | App details, Play testing links, tasks, readiness answers, test counts and production-access outcome run and report a campaign. | The app owner, participating testers where needed to perform the test, and authorised administrators. |
| Waitlist data | Your email, name, planning answers, comments and consent record are used only when you choose to join the paid waitlist. | Authorised administrators and Brevo, our email delivery provider. |
Please do not upload passwords, payment details, private messages, government identifiers, health information or unrelated personal data in feedback, notes or screenshots. Review a screenshot before uploading it and crop or redact anything the developer does not need.
Google Play email consent
Joining a test requires a separate checkbox confirming that your Google Play email may be shared with that app's developer. We record the time of consent. Without it, you cannot join and your email is not included in that developer's tester-list export.
If you withdraw, your email is excluded from future AppFledge exports for that test. Withdrawal cannot recall a file the developer already downloaded or remove an address they already added in Google Play Console. Ask that developer to remove it there if needed.
Service providers and other disclosures
- Supabase provides authentication, database, server functions and private file storage.
- Brevo delivers opted-in waitlist messages and testing reminders. Reminder preferences can be changed while a test is active; marketing messages include an unsubscribe option.
- PostHog may process page views, selected product events, a user identifier and basic browser data when analytics is enabled. The site uses browser storage and a cookie for this purpose; automatic click and form capture is disabled.
- We may disclose information when reasonably necessary to comply with law, protect people, investigate abuse or secure the service.
These providers may process data in countries outside your own. Their handling of data is governed by their own terms and privacy documentation.
How long we keep data
The beta does not currently apply one automatic deletion deadline to every record. Account and tester profile data is normally kept while the account is active. Campaign history, consent timestamps, participation, feedback and credit-ledger entries are kept with the related account or campaign so results, rewards, disputes and abuse checks remain auditable. Check-in screenshots are kept with their related check-in record.
Waitlist data is kept until you unsubscribe, ask for removal or the waitlist is retired. Service logs, backups, analytics and email-delivery records may follow the provider's own retention settings and can remain for a limited period after deletion from the live product. We may keep a record longer where law, security, fraud prevention or an unresolved dispute requires it.
How we protect data
Access is restricted by authenticated account and campaign relationships. Database row-level security limits who can read each record, and check-in screenshots are stored in a private bucket rather than at public URLs. No online service can promise absolute security.
Your choices and requests
- Edit your name and tester device details from your account.
- Choose whether to add a region and whether to upload a check-in screenshot.
- Turn testing reminders on or off while your participation is active.
- Withdraw from a test to stop future participation and tester-list exports for it.
- Unsubscribe from waitlist marketing using the link in the message.
- Request access, correction or deletion of personal data, subject to records we must retain.
Send a privacy request to khury.slm@gmail.com. Include your account email and the request; we may need to verify that the account belongs to you.
Google Play is separate
AppFledge is not affiliated with Google and does not read your Google account password or automatically verify Play Console activity. Once you follow a Google Play link or a developer adds your email to Play Console, Google's own terms and privacy policy apply to that activity.
Changes to this notice
We will update the date above when this notice changes. If a change materially affects how already-collected data is used or shared, we will provide an appropriate in-product or email notice before applying it where required.