Privacy Policy

TestLoop helps software developers, Android developers, indie developers, startup founders, and development teams create testing campaigns, accept other developers’ testing requests, and coordinate Google Play testing participation. TestLoop is a network connecting developers. It is not a public tester marketplace for consumers, and it is not Google, Google Play, or a Google Play Console substitute.

For privacy questions, contact shahnawaz@sustainablesolution360.com.

We collect information that you provide, information we receive from Google when you sign in, and information created by your use of the platform. We do not ask for, and do not store, your Google password.

Google account information used for authentication. When you choose Continue with Google, Google may share the Google account email address, name, and profile photo associated with the account you select. TestLoop uses this information to create and maintain your developer account. We do not use Google Sign-In to read your Gmail inbox, contacts, or Drive.

Developer profile information. After sign-in you may provide a full name, developer or company name, country, city, developer type, years of experience, platforms, technologies, website, GitHub, LinkedIn, bio, profile photo, and an optional Google Play testing Gmail. Incomplete profiles cannot create testing campaigns or accept tests.

Application information. If you add an Android app, TestLoop stores details you submit such as app name, package name, Google Play Store URL, optional testing or opt-in URL, icon, description, testing track or type, tester targets, and related configuration. TestLoop does not create fake app records and does not treat a Play Store listing URL as a testing opt-in URL.

Testing campaign information. Campaign records may include the selected app, testing type, target tester count, duration, description, testing instructions, publication status, the Google Play testing track you select, and campaign progress derived from recorded platform activity.

Tester participation information. If you accept another developer’s testing request, TestLoop records the participation and its status. Your Google Play testing email is collected only after you explicitly confirm and consent to share it with that campaign’s owner. Other developers do not see your Google email on public profiles or the request feed. Campaign owners can see a consented testing email so they can add you as a tester.

Google Play and testing-related integrations. If you choose to connect your Play Console with Google sign-in or a service-account key, optional Gmail sending, or another supported integration, TestLoop stores the credentials and connection status you provide so the integration can run for your account. Play service-account keys and OAuth refresh tokens are encrypted at rest and are never returned to the browser. Connecting an integration is optional. If an official API cannot complete an action, TestLoop reports the failure or the exact manual step. It does not invent a successful Google Play result.

Messages, feedback, reports, and activity. TestLoop stores developer-to-developer messages you send, testing feedback you submit, in-app notifications, reports or blocks you file, and activity logs needed to operate campaigns and support trust and safety.

Optional in-app telemetry. If a developer’s own application is configured to call TestLoop’s telemetry endpoint, TestLoop may store a campaign token, an anonymous tester identifier, optional app version, optional platform, and timestamps. This is an activity signal from that app. It is not a Google Play per-account download confirmation.

Technical information. When you visit TestLoop, our hosting and infrastructure providers may process standard request data such as IP address, browser type, device or user-agent information, and timestamps in order to operate, secure, and diagnose the service. TestLoop does not currently operate a separate advertising pixel or third-party marketing analytics product on these pages.

We use the information described above to:

• authenticate developers with Google Sign-In and maintain developer accounts;
• display developer profiles, apps, and published testing requests to other signed-in developers;
• operate testing campaigns, accept/consent flows, reciprocal requests, and participation status;
• share a testing Gmail with a campaign owner only after the tester’s explicit confirmation;
• attempt the Google Play actions you authorize, or show an honest manual fallback;
• calculate reputation and match scores from recorded platform activity;
• send in-app notifications you have not disabled in Settings;
• protect the service against spam, abuse, fraud, and unauthorized access; and
• comply with law and enforce these terms where applicable.

TestLoop does not sell your personal information. TestLoop does not use Google Sign-In data to place advertisements.

Account, profile, app, campaign, participation, message, and integration records are stored in TestLoop’s application database. Integration credentials such as Play service-account material are encrypted before storage. Session authentication uses a signed session cookie rather than storing your Google password. No security measure is perfect. You should use a Google account you control, grant integrations only the access you intend, and disconnect credentials you no longer need.

We may share information:

• with other developers, limited to what the product is designed to show — for example public developer profile fields, published campaign details, and a testing Gmail after you consent;
• with Google or other providers when you connect an official integration and TestLoop calls that API on your behalf;
• with infrastructure providers that host the website, database, and application runtime;
• if we believe disclosure is required by law, legal process, or to protect developers and the platform; and
• in connection with a genuine business transfer, if one occurs, subject to this policy or successor notice.

TestLoop is multi-tenant. Private developer information is associated with the owning account. Developer A must not be able to access Developer B’s Google Play credentials, private tester emails, private campaign management tools, or private Play Console data except where the product’s intended workflow explicitly shares information — for example after a tester consents to provide a Gmail to a campaign owner. Public profiles and the testing-request feed are not intended to display Google emails, API credentials, or service-account private keys.

You can update developer profile fields, manage apps and campaigns, disconnect supported integrations, and adjust certain notification preferences while signed in. Settings currently include an export of certain tester, campaign, app, and related records associated with your account.

To request deletion of your TestLoop account and associated personal data, email shahnawaz@sustainablesolution360.com. We may retain limited records where we have a legitimate need, such as security, dispute resolution, or legal compliance. Disconnecting Google access in your Google Account settings will stop future Google Sign-In from that authorization; you may also need to contact us to delete the TestLoop account itself. If you connected Play or other credentials, disconnect them in TestLoop and revoke them in the relevant Google Cloud or Play Console settings.

We retain account, campaign, participation, and related records for as long as the account remains active and as reasonably needed to operate the network, resolve disputes, and maintain security logs. Optional telemetry events are retained in connection with the relevant campaign. When an account is deleted upon request, we delete or de-identify personal data we no longer need, except for information we must keep for legal or security reasons.

TestLoop uses cookies and similar technologies that are necessary to keep you signed in, protect authentication flows (including OAuth state), and operate the website. These include session cookies used by Google Sign-In. TestLoop does not currently use those session cookies to run a separate advertising profile. If you block cookies, sign-in and other authenticated features may not work.

TestLoop relies on third parties to provide the product, including Google Sign-In / Google Identity, Google Play Developer API and related Google APIs when you connect them, optional Gmail sending via official Google OAuth, optional Meta/Facebook connections if you enable them, and the hosting, database, and deployment providers that run the application. Those providers process information according to their own policies. TestLoop is not responsible for third-party sites or consoles you open from testing links, Play Store URLs, or Play Console pages.

Continue with Google uses Google’s official OAuth process. TestLoop requests identity information needed to create a developer account. We do not request your Google password. Google user data received through Sign-In is used to authenticate you, display your account identity, and operate your TestLoop developer profile. Testing Gmail used for Google Play closed testing is a separate, explicit consent step after you accept a campaign; it is not silently taken from Google Sign-In without that confirmation.

TestLoop uses authenticated sessions, authorization checks that scope records to the owning developer, encrypted storage for integration credentials, and HTTPS in production deployments. We do not claim ISO, SOC, or other third-party security certifications in this policy. You remain responsible for the security of your Google account, Play Console access, and any service-account keys you upload.

TestLoop is intended for developers and other adults who can form a binding contract and who are permitted to use Google Play developer and testing features. It is not directed to children under 13, and we do not knowingly collect personal information from children. If you believe a child has provided personal information, contact shahnawaz@sustainablesolution360.com so we can take appropriate steps.

We may update this Privacy Policy as TestLoop changes. The “Last updated” date at the top of this page will change when we do. Continued use of TestLoop after an update means you should review the revised policy. If a change is material, we may provide additional notice through the service where reasonable.

Privacy requests, including access or deletion requests, can be sent to shahnawaz@sustainablesolution360.com. You can also return to the main TestLoop website at https://www.testloop.org.