1. Scope and contact
This policy covers the Explain AI website, mobile app, and related support and testing communications (together, the “Service”). “We” refers to the operator of Explain AI. Legal operator: [confirm]. Privacy contact: [provide email or request form]. Before final publication, these details and the disclosures below must match the actual app and its Google Play Data safety answers.
2. What the website handles
The public website does not have a site account or an on-site tester registration form. The three-step onboarding guide saves the step you select in your browser’s local storage on that device. This helps you return to the same instruction after visiting Google Group or Google Play. You can remove it by clearing this site’s browser storage. That step is self-reported and is not proof of test enrollment.
When your browser loads the website, the hosting service necessarily receives technical request information such as an IP address and browser request details to deliver the page. The page also loads fonts from Google Fonts, which receives a request from your browser. Confirm the hosting provider’s log retention and any additional analytics before finalizing this policy. The site code currently does not include an advertising or analytics service.
Buttons for the tester group and app test open Google Groups and Google Play in a separate tab. Those services handle information under their own policies. The website does not read your Google password or verify your Google Group membership.
3. Information in the mobile app
Explain AI has account features and study tools. Based on its functionality, data categories to review include account identifiers, the questions or study material you submit, generated explanations, flashcards and collections, study progress, purchase or Pro status, and technical diagnostics. Confirm precisely which categories are collected or stored, whether any are optional, and whether the app accesses device identifiers or permissions. This draft does not claim that every item in that list is collected.
Complete before final publication: list every category of user and device data actually accessed or collected by the app, whether it is linked to an account, its source, and whether data is sent to an AI provider. The policy must also cover any data collected by embedded SDKs.
4. How information is used
The website uses the locally saved step only to resume the onboarding guide. The app uses information needed to provide the features you choose, such as account access and study tools. Confirm any additional uses, including analytics, support, fraud prevention, product improvement, model training, personalization, and marketing. If a use does not occur, it should not be listed in the final version.
6. Retention
The website’s onboarding step remains in local storage until you clear it or your browser removes it. App retention periods are not yet confirmed. The final policy must explain how long account data, study content, logs, backups, and purchase records are retained, what happens after deletion, and whether any data is kept for legal or security reasons.
7. Your choices, access, and account deletion
You can avoid the website’s saved onboarding step by clearing this site’s browser storage. You can leave the Google Play test using Google’s enrollment controls. App account access, correction, export, and deletion instructions must be confirmed and added here.
The Explain AI app supports account creation. The final policy must provide an in-app deletion route and a working public web route where someone can request deletion without reinstalling the app. [Add the actual request link or support email and expected process.]
8. Children and student use
Explain AI is intended for students, but the app’s approved age audience and approach to users under 13 have not been confirmed. Confirm the minimum age, whether the Service is directed to children under 13, and any parental consent or child-data practices before publishing a final policy. If you believe a child’s information has been provided contrary to the final policy, use the privacy contact once listed above.
9. Security
We should describe the actual administrative and technical safeguards used to protect account and study information. No system is perfectly secure. Confirm the app’s security measures, access controls, and incident contact procedure before making specific security promises here.
10. International use
Depending on where the Service and its providers operate, information may be processed in a different country from yours. Confirm provider locations and any international transfer practices before final publication. Privacy rights can vary by location; the final policy should describe applicable request methods.
11. Updates and questions
We will update this page when the Service or its data practices change and show the revision date above. If a change requires separate notice or consent, we will provide it as applicable. For privacy questions or requests, contact [privacy contact to be added].