Glifizz · com.glifizz.app

Privacy policy

Effective and last updated: 31 October 2026.

Who operates Glifizz

Rahul Kumar operates Glifizz as an individual. This policy covers the Glifizz Android app (com.glifizz.app), its testing experience, and these support pages. Contact glifizz.app@gmail.com.

Account and preparation data

To register and sign in, you provide an email address and password to our Supabase authentication provider over HTTPS. Supabase manages password hashing, verification, recovery and session tokens. We do not ask you to email your password or verification codes. Your account has a user ID. We store your selected exam and preparation duration in your account profile so they return when you sign in. A profile can contain an optional display name; do not provide sensitive information.

Learning, GLI drafts and files

The current test has interactive Centre of Mass & Collisions lessons. Lesson interactions, answers, hints, drafts and review state are held in the current learning session; durable cloud lesson-progress sync has not been enabled. GLI currently provides session drafts, not live AI responses. Files selected in GLI are local previews; the app does not upload them to an AI service. Closing or losing a session can discard this work.

Device storage and optional platform features

Authentication session tokens are stored in app-private WebView storage to restore sign-in. Account recovery also uses local session state. Android backups are disabled for this build; we do not claim hardware-encrypted token storage. If a browser or keyboard offers dictation and you choose to use it, that platform’s speech service may process audio under its own policy. Availability differs by device; it is not GLI AI tutoring. The app requests no ordinary native permission beyond Internet access.

Providers and network information

Supabase processes account data and profile preferences. Cloudflare hosts these support pages and the separately restricted web preview. Network providers can process IP addresses, browser/client information and request/security logs to deliver and protect their services. Google Play processes installation, tester enrollment and platform diagnostics under Google’s terms. Email providers process messages you choose to send us. Relevant policies: Supabase, Cloudflare, and Google. Processing may occur outside your country.

Purpose and disclosure

We use account and preference data to provide sign-in, account recovery and your preparation settings. We use support messages to respond, verify deletion requests, investigate bugs and operate the test. We do not sell personal data or include advertising or third-party analytics SDKs in this build. These support pages contain no advertising or analytics scripts. We may disclose information when legally required or needed to protect accounts and prevent abuse.

Retention and deletion

Active account and profile data remain until you request deletion or the test service is discontinued. You can request removal of your account and associated saved preferences through our account-deletion page or the app’s profile pathway. This is a manual process: we verify ownership, delete the account and associated active profile data, and confirm completion by email within 30 days of a verified request. A request is not instant deletion. Operational/provider logs may remain under the provider’s retention schedule; legal or security obligations can require limited retention. We will explain any retained information and applicable duration when responding. We do not advertise this test as having a verified backup/recovery service.

Your choices and younger users

Contact us to request account deletion, correction or access to information we hold about you. Glifizz is intended for ages 13–15, 16–17 and adults; it is not directed to children under 13. Where applicable, younger users should involve a parent or guardian. No age-verification or parental-consent system is claimed. If you believe a child under 13 provided account data, contact us so we can investigate and remove it where appropriate. Do not send government identity documents in an initial support request.

Testing and feedback

A testing group and Google Play enrollment are separate. Group membership is not proof of Play opt-in. Feedback should describe app behavior, device/Android version, steps and expected versus actual results. Do not include passwords, email-link tokens, private school information or sensitive screenshots. Account emails and any feedback identifiers are used only to operate testing and respond to you; group members must not be treated as a public marketing list.

Changes

We will update this page when data handling changes. New cloud progress or AI features are not covered as already active by this policy.