Privacy Policy for TestPls
This Policy explains what data is processed when using TestPls, why it is needed, who it may be shared with, how it is stored, and how the user may request deletion or correction.
1. General provisions
The Developer of TestPls acts as the operator of data processed for the service, client software, web interfaces, and server-side features. This Policy is prepared with regard to Russian Federal Law No. 152-FZ "On Personal Data".
The service processes only the data needed for sign-in, app catalog operation, internal token accounting, action verification, paid features, user support, security, and legal compliance.
2. Data processed
When signing in through VK ID or Yandex ID, the service may receive and store the user's email, technical provider account identifier, name, and avatar link if such data is provided by the sign-in service under the user's permissions.
When listing an app, the user submits a title, package name, Google Play link, description, logo, and additional instructions. A logo is usually not personal data by itself, but it may become personal data if it contains a person's image or other identifying information.
During testing, TestPls may process the installation or removal status of a specific app, launch event, date and time, review, screenshots, and the connection of these actions to the user's account.
When paying for paid features, the amount, currency, date, status, payment identifier, selected feature, email, electronic receipt details, and data needed for refunds or payment support may be processed. Full bank card details and other full payment instrument details are processed by the payment provider and are not stored by the Developer.
Support requests may include the request text, app or service page, client version, sign-in provider, user-agent, and request date.
3. Purposes
Data is used to sign users in, show the profile, operate the app catalog, publish app cards, verify installation and launch of a specific app, credit and spend internal tokens, operate boost, process payments, account for paid features, send electronic receipts, process refunds, show feedback to the app owner, prevent abuse, diagnose errors, and answer user requests.
Anonymized or aggregated data may be used to analyze stability, improve features, and plan load.
4. Installed app checks
TestPls does not obtain the full list of installed apps on the device. For installed-app sections and rewards, the service client checks only the specific package name from an app card and only whether Android can launch that app.
The server receives events needed for the service: installation, removal, launch, and related date, user, and app. These events are used for rewards, statistics, duplicate reward prevention, and dispute resolution.
5. Sharing data
Data may be shared with third parties only to the extent necessary for service operation, legal compliance, or protection of the Developer's and users' rights.
Such third parties may include VK ID and Yandex ID, Google Play and Google Groups, payment providers, fiscal data operators, hosting providers, file storage services, support email services, app stores, and public authorities where required by law.
The Developer does not sell users' personal data.
6. Storage and retention
Email, technical sign-in identifiers, and profile data are stored while the account is used and are deleted or anonymized within 30 days after a confirmed deletion request, unless longer storage is required by law, security, or dispute resolution.
App cards, including logos, are stored while the app is published or available to the owner in the profile. After deleting the card, the logo and related public materials are removed from active storage within 30 days and from backups within 90 days.
Reviews, screenshots, installation, removal, and launch events are usually stored for up to 12 months if needed for reward history, app statistics, abuse prevention, security, or dispute resolution.
Payment, receipt, and refund information is stored for the periods needed for legal compliance, accounting and tax records, payment confirmation, refunds, and dispute resolution. Such information may usually be stored for up to 5 years unless a longer period is required by law or a dispute.
Support requests are usually stored for up to 12 months after closure. Technical logs and diagnostic data are usually stored for up to 12 months unless a longer period is needed for security, incident investigation, or legal compliance.
7. Protection
The Developer takes reasonable organizational and technical measures to protect data from unauthorized access, alteration, disclosure, or destruction.
Some data is stored locally on the user's device, including settings, interface language, and session data. Removing client software deletes local data but does not always delete data previously sent to the server.
8. User rights
The user may request information about processing, correction, deletion, restriction of processing, or withdrawal of consent where provided by law.
The user may contact the Developer through the "Report a problem" form in the service profile or by email at testpls@photonius.ru. To protect data, the Developer may request information needed to verify the user's connection to the relevant account or materials.
Deletion or withdrawal of consent may make some features or the entire service unavailable if processing is required for them to work.
9. Third-party data
The user must not submit third-party personal data without a lawful basis and required consent.
If a logo, screenshot, review, or description contains information about third parties, the user is responsible for the lawfulness of that submission.