Privacy Policy

When you sign in with Google, we receive your name, email address, and profile picture URL from Google/Firebase Authentication, plus a stable account identifier. We don't see or store your Google password.

Beyond that, we collect what you do inside 12tester itself:

• Groups you join or create, and when you joined them.
• Apps and campaigns you create, and their API keys (visible only to you as the owner).
• Testing activity: which campaigns you joined, days you were credited, your credit balance and history.
• Your chosen display language.
• A push-notification device token, if you allow notifications.

When you test someone else's app through 12tester, that app's integration of our SDK reports back to us: your tester code, the app's package name and version, your device platform (Android/iOS), and a timestamp — enough to confirm a real test session happened and to credit it. If that app's developer calls an optional log/achieved event with their own data attached (for example, which screen you reached), that data is stored too, scoped to that campaign.

Developers can optionally call an identify() function in their own app to attach their own internal user id to these events — that id comes from the developer's app, not from your 12tester account, and is only used to help that developer correlate their own logs.

Other 12tester members can see a limited public profile: your name, avatar, member-since date, current testing streak, total days tested, and how many groups/campaigns you've joined. We don't show your email, credit balance, or anything from a specific campaign's private data to other testers.

If a campaign owner turns on that campaign's tester badge, a tester currently testing their app can be shown (inside that developer's own app) with their name, avatar, and day-by-day progress for that campaign only.

• Google Sign-In / Firebase Authentication — to sign you in.
• Firebase Cloud Messaging — to deliver push notifications, if enabled.
• Firebase Analytics, Crashlytics, and Performance Monitoring — to understand crashes and app performance, not to build advertising profiles.
• Google Play's Install Referrer API — to automatically recognize a tester code when you install an app you're testing, entirely on-device.

We don't sell your data, and we don't share it with advertisers.

Deleting your account anonymizes your name, avatar, email, and sign-in identifier, and removes your ability to sign back in with that account. Apps and campaigns you created keep running for their existing testers, but you lose access to manage them. Credit and activity history tied to your (now-anonymized) account is kept for the integrity of other members' testing records — for example, a campaign you tested for still shows it was tested, without your identity attached.

Your chosen display language is stored against your account so notifications and the SDK's tester dialog render correctly wherever you're testing — this is a preference, not a location or tracking signal.

Questions about this policy or your data — email support@playtesters.dev.