Goalora Privacy Policy

Goalora ("Goalora," "we," "us," or "our") provides the Goalora English-learning application for Android, package name com.goalora.englishlearning (the "App"). This policy explains what information the current App collects, where it is processed, why it is used, and the choices available to users.

1. Information the App Collects

1.1 Account and authentication data

• Email-and-password accounts: an email address and password are required when this sign-in method is selected. Firebase Authentication processes the password; the App does not write the password to Cloud Firestore.
• Google Sign-In: this is an optional alternative to email and password. If selected, Google provides identity information needed to sign in, including a Google account identifier, name, and email address. Goalora does not request Google contacts, Google Photos, or Google Drive data.
• User ID and timestamps: Firebase creates a unique account ID. Cloud Firestore records profile creation and update timestamps.

1.2 Required profile data

After account creation, the App requires:

• full name;
• English proficiency level (beginner, intermediate, or advanced); and
• preferred learning language (Hindi or Marathi).

1.3 Optional profile and reminder data

Users may choose to provide:

• education level;
• up to three topics of interest;
• a practice goal; and
• preferred practice-reminder times.

These fields are optional. They are used to personalize practice content and configure reminders when selected.

1.4 Learning progress

When a practice session is finished, Goalora records the identifiers of questions that were attempted, answered correctly, or answered incorrectly. This allows the App to show or select suitable practice material and avoid unnecessary repetition.

1.5 Practice answers

Words arranged as an answer during a practice session are checked on the device. The current App does not upload or persist the full answer text. It uploads only the related question identifiers and whether they were answered correctly or incorrectly.

1.6 Technical information processed by service providers

Firebase and Google services may automatically process technical information needed to provide and protect their services. Depending on the service, this can include IP address, user-agent information, operating-system and device metadata, App and SDK versions, the Firebase App ID, and a per-installation identifier. Firebase Authentication uses IP address and user-agent information for authentication security and abuse prevention.

2. Where Information Is Stored

2.1 Information sent to Google/Firebase

The following information leaves the device and is processed using Google services:

• account credentials and account identifiers through Firebase Authentication and, when chosen, Google Sign-In;
• name, email, proficiency, learning-language preference, optional profile choices, reminder preferences, and learning-progress question IDs in Cloud Firestore; and
• the technical service information described above.

2.2 Information kept on the device

• The device timezone identifier is read to schedule reminders at the correct local time. Goalora's App code does not upload that identifier to Firestore.
• Reminder notifications and their schedules are created locally through the device notification system. Preferred reminder times are also saved to Firestore as part of the user's profile.
• Firebase Authentication keeps local sign-in state to support the user's session. Goalora disables Firestore's persistent disk cache; Firestore data may be held in memory while the App is running but is not kept in Firestore's offline disk cache.
• Practice answers are held in memory for the current practice session.

The App does not implement SharedPreferences, Android DataStore, Hive, SQLite, or a separate app-managed local database.

3. How Information Is Used

• Account management: create accounts, sign users in, maintain sessions, and reset passwords.
• App functionality: load English-learning questions and record practice results.
• Personalization: select material using language, proficiency, education level, interests, and past results.
• Local reminders: schedule optional practice notifications at times chosen by the user.
• Security and service reliability: authenticate requests, prevent abuse, and operate Firebase services.
• Support and rights requests: respond to messages sent to Goalora's contact email.

4. Service Providers and SDKs

4.1 Firebase Authentication and Cloud Firestore

Goalora uses Firebase Authentication for email/password and Google authentication and Cloud Firestore to store profile and progress data and provide practice questions. Google processes this information as Goalora's service provider. Firebase Authentication may process data in the United States, while Cloud Firestore may process data in the configured Google Cloud location and on Google's infrastructure.

4.2 Google Sign-In and Google Play services

Google Sign-In is used only when a user chooses that option. Google Play services and Android credential components support the sign-in process. The App does not use phone calls, SMS messages, contacts, or call logs to verify accounts.

4.3 On-device utility SDKs

Goalora uses Flutter packages for local notifications, timezone lookup, Android permission handling, vibration feedback, and temporary on-screen messages. The App uses these features on the device and does not integrate them with a separate advertising or analytics service.

See Google's Privacy Policy, Privacy and Security in Firebase, and Firebase Terms for more information about Google's processing.

5. Services Goalora Does Not Currently Use

The current App code does not include or use:

• Firebase Cloud Messaging (FCM) or server-sent push messaging;
• Firebase Analytics or another analytics SDK;
• Firebase Crashlytics or another crash-reporting SDK;
• advertising, advertising identifiers, or attribution SDKs;
• a third-party artificial-intelligence service or generative-AI API;
• anonymous chat, random chat, or user-to-user messaging; or
• sale of personal information.

Text in development documentation about possible future AI or push-notification features does not describe functionality in the current App. This policy will be updated before any materially different data practice is introduced.

6. Device Permissions

The Android App declares permissions for:

• Internet and network state: connect to Firebase and Google services;
• Notifications: show optional local practice reminders on supported Android versions;
• Vibration: provide feedback and support notification behavior;
• Boot completion: allow the notification component to restore scheduled reminders after restart or app update; and
• Inexact alarm scheduling: support scheduled local reminders without requesting Android's restricted exact-alarm permission.

Users can deny or disable notification permission in Android settings. Core learning and account features remain available without enabling reminder notifications.

Goalora does not request SMS, READ_CALL_LOG, location, contacts, camera, or microphone permission. Google credential libraries may contribute biometric-related permission declarations to the merged Android manifest, but Goalora's App code does not request, receive, or store biometric templates.

7. Sharing and Disclosure

Goalora does not sell or rent personal information. Information is disclosed in these limited circumstances:

• Service providers: Google/Firebase processes information to provide authentication, database, and sign-in services. This processing is not described as a sale of data.
• Legal and safety reasons: Goalora may disclose information when required by applicable law or valid legal process, or when reasonably necessary to protect users, Goalora, or the public.

8. Data Retention

• Firebase Authentication account data and identifiable Firestore profile/progress fields are retained while the account remains active. Account deletion removes the Authentication user and anonymizes the old Firestore document as described below; the App does not otherwise apply an automatic expiry period.
• Firebase states that authentication IP logs are generally retained for a few weeks. After the developer initiates deletion of a Firebase Authentication user, other Auth information is removed from live and backup systems within 180 days.
• Firebase states that, after a Firebase installation ID is deleted through the applicable API, information tied to that ID is removed from live and backup systems within 180 days. The current App does not automatically make that deletion request.
• Local reminders remain until they are cancelled, the user signs out, or the App is removed. Goalora cancels reminders and clears its in-memory user state after a confirmed deletion, and Firebase Authentication sign-out clears the local session.
• Goalora has not established a separate fixed retention period for support or deletion-request emails. Such messages are retained only as needed to handle the request, protect the account, and meet applicable legal obligations.

9. Access, Correction, and Account Deletion

Users can review and edit supported profile fields in the App. A signed-in user can delete an account by opening My Profile, scrolling to Account, selecting Delete account, reviewing the permanent-deletion notice, and confirming the request. Email/password users must enter their current password, and Google users must complete a fresh Google Sign-In. Goalora does not receive or store the password entered for reauthentication.

After reauthentication, the App uses the currently authenticated Firebase UID to update only that user's Firestore users/{uid} document. It marks the document deleted, records a server deletion timestamp, changes profile-name fields to "Deleted User," and removes email, profile choices, reminder preferences, and stored progress. The UID remains as the document key and any role field is not changed. Firestore rules prevent a user from updating another UID or changing the uid or role field.

After the Firestore anonymization succeeds, the App deletes the current Firebase Authentication user. If that Auth operation fails, the App attempts to restore the original Firestore values, keeps the user signed in, and does not report success. On success, it cancels local reminders, clears in-memory profile and question state, clears local Firebase and Google sessions, and returns to the sign-in screen. This process does not use a Cloud Function or Firebase Admin SDK.

If the user cannot access the App, the public Goalora account-deletion page provides an alternative request method. A user may email goalora2026@gmail.com from the address associated with the account. Include "Goalora account deletion request" in the subject. Goalora may request reasonable verification before acting to protect the account from unauthorized deletion.

A verified deletion request covers, as applicable:

• the Firebase Authentication account;
• identifying fields in the old Cloud Firestore user document;
• learning preferences, reminder preferences, and stored progress question IDs;
• the old Firestore document remains only as a soft-deletion record containing its UID, deletion marker and timestamp, "Deleted User" name, creation timestamp where present, and any unchanged role field;
• local reminder schedules and in-memory account state on the device used to delete the account.

If the App is closed or the network connection is interrupted before completion, the App does not display a success message. The user should sign in again and retry or contact Goalora for assistance.

Signing out or uninstalling the App does not by itself delete the Firebase account or Firestore data. Users may also withdraw optional notification permission in Android settings and can remove optional profile choices in the App where supported.

After deletion, the same email address or Google account may be used to register again. Firebase creates a new UID and Goalora creates a new profile. The new account is separate, and deleted preferences and learning progress are not restored. Deleting Goalora does not delete or revoke the user's underlying Google account.

10. Children's Privacy and Intended Audience

Goalora may be useful to school students, college students, graduates, postgraduates, and adults. Describing someone as a "student" does not mean that person is a child. The App is not directed to children under 13, and a person under 13 must not create or use a Goalora account.

Goalora does not currently provide an age-screening flow, a parent account, parent controls, or a mechanism for obtaining verifiable parental consent. Ordinary account registration, Google Sign-In, or acceptance of this policy is not treated as parental consent. If local law sets a higher minimum age for a person to consent to data processing, the higher age applies.

If you believe a child below the applicable minimum age has provided personal information, contact goalora2026@gmail.com. Goalora will investigate and take appropriate steps, including deletion where required.

11. Security

Goalora uses Firebase Authentication, HTTPS connections provided by Firebase SDKs, and Firestore access rules intended to limit each signed-in user to their own user document. Firebase states that Authentication and Cloud Firestore data are encrypted in transit and at rest. No system can guarantee absolute security, and Goalora does not make such a guarantee. Users should protect their password and contact Goalora if they suspect unauthorized account access.

12. User Choices and Rights

Depending on applicable law, users may have rights to:

• request access to personal information;
• correct inaccurate information;
• request deletion of the account and associated data;
• object to or restrict certain processing;
• withdraw a permission or consent where processing is based on it; and
• request a portable copy where required by law.

Withdrawing notification permission stops reminder notifications but does not delete the account. To exercise privacy rights, use the contact details below.

13. Changes to This Policy

Goalora may update this policy when the App, its service providers, or legal requirements change. The effective date at the top of this page will be updated when material changes are published. Where required, Goalora will provide an additional notice or request a new choice before beginning materially different processing. Continued use alone is not treated as parental consent or as consent where applicable law requires an affirmative choice.

14. Contact Goalora

For privacy questions, account requests, or concerns, contact: