Privacy Policy — PhysicsLab

Effective date: 2026-09-19
Publisher: Hoang Van Kieu
Contact: support.hvk@gmail.com

1. Scope and plain-language summary

PhysicsLab is an educational physics app with guided lessons, scientific datasets, quizzes, virtual experiments, measurement tools and quantum/modern physics playgrounds. Onboarding can be previewed without an account, but a Firebase email/password account is required to enter the main learning workspace and use the app's learning features.

In short: PhysicsLab does not sell personal information, show behavioural advertising or use tracking for advertising. The app does not request access to your camera, microphone, contacts, photos or location.

2. Information we process

CategoryExamplesWhy it is usedAccount linked?
Account informationEmail address, display name and Firebase user identifierRegistration, sign-in, password reset, session security and account managementYes
Local app settingsOnboarding completion flag and settings stored on the deviceRemembering that onboarding was completed and keeping the app experience consistentNo
Learning contentPhysics lessons, questions, datasets and experiment instructionsDelivering public educational content from the app bundle or Cloud FirestoreNo
Community contentPosts, comments, likes, topic memberships and reportsRunning topic discussions, displaying community activity and moderating contentYes for account actions
Service and network dataTechnical information that Firebase or the operating system may process when a secure request is madeAuthentication, security, connectivity and reliable service operationMay be associated by the service provider

Account information

If you register, Firebase Authentication processes the email address, optional display name and Firebase user identifier. Passwords are handled by Firebase Authentication. PhysicsLab does not read, display or store your password in Cloud Firestore, local app content or support requests.

Local settings and learning activity

The current app stores a small onboarding setting locally with the device preferences system. It does not currently upload personal learning progress, experiment notes, measurement trials or quiz answers to Cloud Firestore. The virtual labs calculate results on the device for the current session.

Content service data

PhysicsLab may read public educational documents from Cloud Firestore, including physics topics, experiments and practice questions. These documents are content, not a personal profile. If the network or Firebase is unavailable, the app uses its bundled educational fallback content where available.

Community data

The optional Community Physics feature lets signed-in users join topic groups, publish a discussion title and message, like posts, write comments and report content. Community posts and comments are visible to other users in the relevant topic. The display name shown with a post or comment is the Firebase display name, or a shortened account email name when no display name has been set.

Likes and topic memberships are stored to provide the requested community features. Reports contain the reported target, selected reason, reporter account identifier and timestamp so the publisher can review abuse, spam, harassment or dangerous misinformation. Reports are not public to other community users. The optional block control stores blocked author IDs locally on the user's device so that the user can hide that author's community content; this blocklist is not uploaded as public profile data.

3. How we use information

We do not use account data to sell products, build advertising profiles or deliver targeted advertising. We do not use Firebase Analytics, Crashlytics, advertising SDKs or App Tracking Transparency in the current app.

4. Onboarding access and consent

Onboarding content can be viewed before authentication. To enter the core learning, quiz and virtual-lab experience, you must sign in or create an account. When you authenticate, the app sends the information required for authentication to Firebase Authentication.

5. Service providers and sharing

PhysicsLab uses Google Firebase Authentication and Cloud Firestore as service providers. Firebase may process account and technical information as necessary to provide authentication, secure network requests and database access. We do not sell or rent personal information and do not share account information with advertising networks.

For more information, review the Firebase Privacy and Security information and the Google Privacy Policy.

6. Retention

Account information is retained by Firebase Authentication while the account remains active, or until deletion is requested, subject to applicable legal, security and fraud-prevention requirements. The publisher does not keep a separate password database.

Community posts, comments, likes and memberships are retained while the associated account and content remain active. Users can delete their own posts and comments from the community screens. When an account is deleted through the app, PhysicsLab attempts to remove the account's community posts, comments, likes, memberships and reports as part of the deletion flow. Limited moderation or security records may be retained only where legally required.

Local onboarding data remains on the device until it is cleared from the app or the app is removed. Public learning content may remain in the app bundle or content database because it is not personal account data.

7. Account and local data deletion

To delete an account, open Profile → Delete Firebase account. PhysicsLab asks for the current password to re-authenticate the account holder, then requests permanent deletion from Firebase Authentication. Deleting an account signs the user out and removes the Firebase account record managed by this app.

To remove local app data, open Profile → Delete data on this device. Removing the app from the device also removes its local preferences according to the operating system. Account deletion does not automatically remove unrelated data that a user may have submitted directly to a third party.

8. Your choices and rights

You may preview onboarding, request a password reset, delete your account in the app, clear local data, or contact the publisher with a privacy question. Depending on your location, you may also have rights to access, correct, restrict or object to processing of personal information. Contact us using the address below so we can handle a request and verify account ownership where necessary.

9. Security

PhysicsLab relies on Firebase Authentication and secure network connections provided by the platform and Firebase. We limit database writes in the current Firestore rules because the current app reads public educational content and does not sync personal progress. No internet transmission or storage system can be guaranteed to be completely secure, so do not send passwords or sensitive information in support messages.

10. Privacy rules and commitments

The following rules describe how the current PhysicsLab release handles privacy. They are written as practical commitments so users, parents, teachers and App Review can understand what the app will and will not do.

  1. Data minimization: we request and process only the information needed for authentication, account security, content delivery and support.
  2. Account gate: onboarding is previewable without an account, while the main lessons, quizzes, datasets and virtual labs require a valid authenticated session.
  3. Purpose limitation: account information is used for sign-in, password reset, session management, security, deletion and account-related support, not for unrelated profiling.
  4. No password storage by PhysicsLab: passwords are entered into Firebase Authentication flows and are not displayed, logged or stored in the app's Firestore content collections.
  5. No sale of personal information: we do not sell, rent or trade account information.
  6. No behavioural advertising: we do not use account data, learning activity or technical data to build advertising profiles or deliver targeted ads.
  7. No cross-app tracking: the current release does not use an advertising identifier, Firebase Analytics, Crashlytics or App Tracking Transparency.
  8. No unnecessary device access: the current app does not request camera, microphone, contacts, photos, location, Bluetooth, health or notification permissions.
  9. Educational content separation: public physics lessons, experiment instructions, datasets and questions are content, not a personal profile or a record of a user's identity.
  10. Community choice: joining a topic, publishing, liking, commenting and reporting are optional after sign-in; the main app account gate applies before community access.
  11. Public discussion awareness: users should assume that a community post or comment can be read by other users and should not include private contact information, credentials or sensitive personal details.
  12. Community identity: posts and comments are associated with the account that created them and display the user's chosen display name or a shortened email name when no display name exists.
  13. Moderation reports: users can report spam, inappropriate content, dangerous misinformation or harassment. Reports are private moderation records and are not shown as public posts.
  14. Own-content control: users can delete their own community posts and comments; users cannot edit or delete another person's content.
  15. Community account deletion: account deletion also attempts to remove the user's community posts, comments, likes, memberships and reports before the Firebase account is deleted.
  16. Local block control: users can hide another author's posts and comments on their device; the local blocklist is stored locally and can be changed by clearing app data.
  17. No personal progress sync in the current release: measurement trials, quiz answers, experiment notes and personal learning progress are calculated or displayed locally and are not currently uploaded to Firestore.
  18. Local control: users can clear the onboarding setting and other local app data through Profile → Delete data on this device.
  19. Account deletion: users can initiate permanent Firebase account deletion inside the app through Profile → Delete Firebase account; sending an email is not required to start the deletion flow.
  20. Intentional deletion: the app may request the current password to re-authenticate the account holder before deletion, which helps prevent an unauthorized deletion request.
  21. Support data minimization: support messages should contain only the information needed to reproduce a problem. We ask users not to send passwords, authentication codes, private keys or payment details.
  22. Limited service-provider access: Firebase Authentication and Cloud Firestore are used as service providers for the functions described in this policy. We do not add advertising or analytics partners to the current release.
  23. Public content protection: the current Firestore rules allow read access only for intended public educational collections and deny client writes to those collections.
  24. Retention limitation: account information is kept while the account is active or as needed for legal, security or fraud-prevention obligations; local settings remain until cleared or removed from the device.
  25. Security by default: authentication and database traffic use the security controls provided by the operating system, Firebase and encrypted network connections. Users should still protect their device and credentials.
  26. No automated eligibility decisions: PhysicsLab does not use personal information to make decisions about a user's credit, employment, insurance, health treatment or access to essential services.
  27. Children and guardians: account creation and educational use should follow the age and parental-consent rules that apply where the user lives. Parents or guardians may contact us about a child's data.
  28. Rights requests: users may contact the publisher to ask about account-related data, correction, deletion or privacy questions. We may verify account ownership before disclosing or deleting information.
  29. Change notification: if a future release adds analytics, advertising, payments, new permissions, additional user-generated content or cloud-synced progress, we will update this policy and the App Store privacy answers before the changed practice is used.
  30. Accurate support contact: privacy and deletion requests must be sent to the monitored support address listed on this page. We will not ask users to send their password by email.

11. Children and educational use

PhysicsLab is an educational app and is not designed to collect personal information from children. Where local law requires parental or guardian involvement for an account, a parent or guardian should supervise registration and use. If you believe a child has provided personal information improperly, contact us so we can review the request.

12. Permissions and tracking

The current app does not request camera, microphone, contacts, photos, location, health data, Bluetooth or push-notification permissions. It does not use an advertising identifier or track users across apps and websites. Physics illustrations that use a camera-shaped icon are content labels only and do not access the device camera.

13. International processing

Firebase and other platform services may process information in countries where Google or its service providers operate. Their processing is governed by their applicable terms and privacy documentation. By using the authenticated learning workspace, you acknowledge that the account service may involve this type of processing.

14. Changes to this policy

We may update this policy when the app, data practices or legal requirements change. We will update the effective date above and publish material changes before they take effect where required. The in-app Privacy Policy screen links to this page so users can review the current version.

15. Contact

For privacy questions, account deletion assistance or data requests, contact the publisher at support.hvk@gmail.com. Please include enough information for us to understand the request, but never include your password, authentication codes or payment information.