Legal

Privacy Policy.

What we collect, how we use it, and how you control it.

Last updated: September 2026

Your privacy is very important to us. This Privacy Policy explains what information we collect when you use our applications, how we use it, and how we protect it.

1. Information We Collect Automatically

Our applications do not collect personal information directly or store data on our own servers, except for the contributions of public store metadata described in the app-specific terms (see TrackPulse, section 9). However, we use third-party services that may automatically collect technical and behavioral data for analytics, performance improvement, and advertising.

Some applications (such as MindCards) may allow users to upload documents. These documents may contain personal data depending on the content provided by the user.

These services include:

2. Use of Information

The data is used to improve performance, analyze user behavior, serve personalized ads, and detect fraud. We do not access or store this data directly.

3. Third-Party Services

Read their privacy policies for more information:

4. Data Control and Deletion

We do not manage or store personal data directly. To limit or delete data collection:

5. Children’s Privacy

Our applications are not intended for children under 13 (or the minimum legal age in your country).

6. EEA Users

If you are in the EEA, we ensure our use of services is GDPR-compliant. Data is processed based on legitimate interest or explicit consent, which you may withdraw at any time.

7. Consent

We request your consent before collecting data for analytics or ads. You can change this setting from your app or system settings.

8. Additional Terms for MindCards

Google Sign-In: MindCards may allow users to authenticate using Google OAuth. Basic profile information may be used only for authentication purposes.

AI Processing: Uploaded documents are processed using artificial intelligence to generate questions. This processing is performed solely to provide app functionality.

Public Content: Questions generated from user documents may be publicly visible within the app. Users are responsible for the content they upload and should avoid including personal or sensitive information.

Data Removal: Users may request the removal of their content.

9. Additional Terms for TrackPulse

What TrackPulse reads: TrackPulse reads the public Google Play details page of the apps you choose to follow (title, developer, icon, rating, number of ratings, installs bucket, version, update date and the published changelog). That information is stored on your device so you can see the history of those apps.

Shared history contributions: to build the shared history that other users see, TrackPulse sends that same public store metadata — plus technical metadata about the collection itself (contract and parser versions, collection profile and fetch timestamp) — to our own history service. The contribution is authenticated with a Firebase anonymous account: it carries no name, email, phone number or profile, and no device or installation identifier.

What TrackPulse does not send: your identity or account details, your contacts, your list of installed apps, your location, or anything you type or paste in the app (the package name you enter is used only on your device to look the app up on Google Play).

Your watchlist stays local: the list of apps you follow lives only on your device.

Server logs: our service receives the source IP address at transport level, as any web service does. We do not store the raw IP in the snapshot tables and keep access logs to a minimum with short retention.

Ads and consent: TrackPulse serves ads through Google AdMob and asks for your consent before using data for ads or analytics. You can review or change that choice at any time from the app menu → Privacy Options.

Stopping the contribution: uninstalling TrackPulse stops every future contribution. Contributions already sent are anonymous public metadata and are not linked to your identity; the only personal data involved in this flow is the source IP address in our short-retention access logs. You can also write to us (section 10) for any privacy request.

10. Contact

For any questions about this policy, please contact us via the email listed in our Google Play developer account.