TestTrack Privacy Policy

This policy explains what information TestTrack collects, why, and the choices you have. TestTrack is made by EazyVerse Studio. If you have any questions, email us at hello@eazyverse.com.

The short version

TestTrack asks for two serious permissions, usage access and screen capture, and it is worth knowing exactly what each one does before you install. Usage access is used to read how many seconds one named app in your group was on screen. Screen capture takes one proof shot per app, only during a round you started yourself. Your proofs go to a folder in your own Google Drive. Your name and email address are visible to other signed in testers, because a grid has to show who is who. We show no ads and we never sell your data.

Signing in

Sign-in is Google Sign-In, on Google's own screen. We never see or ask for your password. What we receive is your display name, your email address and a Google account id, which is what lets a fourteen day grid show people by name instead of by id.

Membership of the testers group is confirmed with Google rather than taken from the phone, so joining the group is part of signing in.

Usage access

Play counts an app being used, not an app being launched, and there is no way to measure that from inside TestTrack. When TestTrack asks Android what happened during a visit, Android returns events for every app on the phone during that window. That is how the API works and no app can ask for a narrower slice.

TestTrack walks that stream and keeps one number: the seconds spent in the single package it is checking, which is always one of the apps in your cohort. Every other event is discarded on the spot. Nothing about any other app is stored, sent or remembered.

Screen capture and your proof shots

Capture runs only during a round you start yourself. Android asks you to confirm it, and shows its own indicator that no app can hide for as long as the round lasts. When the round ends, capture stops.

The shot lands at a moment you are not told in advance, because predictable timing would make the proof worthless. Screen capture takes the screen rather than the app, so whatever is on display at that instant is in the picture, including a notification that happens to arrive at the wrong moment. Turning on Do Not Disturb before a round is a good habit.

Proof shots are written to a folder called TestTrack Proofs in your own Google Drive. The files are yours, they count against your storage, and you can delete them at any time. So the developer whose app you tested can see the proof, each file is set to "anyone with the link can view". It is not listed, searchable or indexed, and in practice the link sits in one database record readable by you, that app's owner and an administrator, but treat every proof as something that could be seen and keep private things off your screen while a round runs.

Google Drive access

TestTrack asks for drive.file, the narrowest Drive permission Google publishes. It grants access to files the app itself created and to nothing else: not your documents, not your photos, not your backups, not files another app put there. That boundary is enforced by Google's servers rather than promised by us. You can withdraw the access at any time from your Google account permissions.

Seeing the apps in your cohort

To show a list worth reading, TestTrack asks Android about one specific package name at a time, always one from your cohort, and learns whether it is installed, when it was installed, which store installed it, its name and its icon. It never asks the system for a list of what you have installed, and it deliberately does not hold the permission that would allow that.

What is stored, and who can read it

• Your proof shot and your daily seconds: you, the owner of the app you tested, and an administrator
• Your display name and email address: any signed in TestTrack account
• Which cohorts you are in and how each run ended: you and an administrator
• Your Drive folder: you, plus anyone holding a proof link

The second line is the one to be plain about. Your name and address are readable by other testers because a grid cannot name people otherwise. Your proofs, your times and your history are not part of that.

Records are kept in Google Cloud Firestore, and the rules that decide who may read what are enforced on Google's servers.

Your record stays

Nothing is deleted on a timer. Finished runs, removals and turned down submissions stay on your record, because a group about to trust a stranger with fourteen days of their own deadline has no other way to judge. The same record that shows a removal also shows every run you completed.

Diagnostics

Crash reports go to Firebase Crashlytics, and carry the stack trace and a fixed word naming where it came from, never a message, a value, a package name or anything about you. Alongside them are four counts and nothing more: a round started, a round finished with how many were captured and missed, a proof posted, an app submitted. Numbers only. Neither carries your id, name, address or the identity of any app you are testing, so nothing in them can reconstruct who tested what.

Notifications

The only optional permission. Your phone raises a reminder in the evening if you still owe the group apps for the day, and a notice if something happened to your own app while you were away. These are built on your phone from data it already has. Decline it and everything else works the same.

What TestTrack never does

• Never reads your messages, contacts, photos, location or call history, and holds no permission that would allow it
• Never captures the screen outside a round you started
• Never asks for your Google password
• No advertising, no ad networks, and no third party trackers in the build
• No selling or renting of your personal information

Service providers

Google acts as our service provider for sign-in, the records in Cloud Firestore, diagnostics through Crashlytics, and Drive. Google's handling of that data is described in the Firebase privacy documentation. Your proof shots live in your own Google account, under Google's terms with you rather than with us. Data held by these services may be processed on servers located outside your country.

Your choices

• Delete any proof shot from your own Drive folder at any time
• Revoke the app's Drive access from your Google account permissions
• Turn usage access or notifications off in Android settings, which stops a round from being able to run
• Sign out, or close your account with Delete your TestTrack account

Children

TestTrack is a tool for app developers. It is intended for a general adult audience and is not directed at children under 13.

Changes to this policy

If we make material changes, we will update the date above and, where appropriate, let you know in the app.

Contact

Questions about your privacy or this policy? Email hello@eazyverse.com.

Need to remove your data? See Delete your TestTrack account & data.