Privacy

When you choose to sign in with Google, LearnzyGo receives your Google account identifier, email address, name, and profile image when supplied by Google. We use this information to identify you, create or link your LearnzyGo account, and authenticate your login.

Account and authentication information, including provider-issued tokens and their available expiry and permission details, is stored in LearnzyGo's application database. Google sign-in requests basic identity permissions; it does not request access to your YouTube channel, videos, Gmail messages, or Google Drive files.

You can revoke LearnzyGo's Google access through your Google Account's third-party connections settings. Revoking access does not itself delete an existing LearnzyGo account or learning history. Contact hello@learnzygo.com for account or data-removal requests.

Separately from customer sign-in, an authorized LearnzyGo operator connects LearnzyGo's own YouTube channel for channel and video checks and approved video uploads. The connection uses YouTube account-read and video-upload permissions. Parents and learners are not asked to connect their own YouTube accounts.

The operator tools access channel and video information, such as channel identifiers, titles, descriptions, video identifiers, and publication status. Approved uploads send their video files and associated titles, descriptions, and visibility settings to YouTube. This workflow does not use customer or learner records as content.

The channel refresh credential is held in a restricted local configuration file. Operational records retain publication identifiers and verification results. The operator can revoke the connection in Google Account settings and remove its local credential; deleting or changing videos already on YouTube is a separate channel action.

LearnzyGo's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. For questions about these connections, contact hello@learnzygo.com.

Google identity data is used to provide account creation, account linking, sign-in, and account security. YouTube channel and video data is used to identify the connected channel, check publication results, and carry out explicitly approved uploads. These Google API data are not sold, used for advertising or audience targeting, or supplied for training AI models.

Google receives authorization requests and the information needed to authenticate the connection. YouTube receives approved video files, titles, descriptions, tags, and visibility settings. A video's visibility on YouTube follows the selected publication setting; private review uploads are not public posts.

LearnzyGo's authorized operators and the infrastructure service providers that host and back up the application may process stored Google identity and authentication data to operate and secure the service. Operator YouTube credentials are restricted to the local operator environment. We do not give advertisers, data brokers, or AI providers access to these Google API data. Information may also be disclosed when required by law. Optional website analytics is a separate, consent-controlled activity described below.

The public website uses HTTPS, and Google API requests use HTTPS. Account data is accessed through authenticated application sessions and server-side access checks. Authentication cookies use HttpOnly and Secure protections in production. Server configuration and local operator credentials use operating-system file permissions to restrict access; credentials are not included in public pages, source-control commits, or demonstration recordings.

Local marketing database backups are encrypted using AES-256-GCM. Website Google authentication records are stored in the application database; we do not claim that each token in that database is separately encrypted. Access is limited through application, database, and server access controls.

Google identity and linked authentication records are retained while the LearnzyGo account and Google connection are maintained. The operator's YouTube refresh credential is retained while that connection is needed. Channel and publication identifiers and verification records are retained for operational reconciliation and audit; these records currently have no automatic age-based deletion schedule.

To request removal of Google identity or authentication data, or stored YouTube connection metadata, email hello@learnzygo.com. We verify the requester's authority and handle removal manually. Removing Google sign-in data can prevent further Google login until the account is linked again. Records needed to meet legal obligations or investigate security issues may be retained for that purpose. Restricted backup copies are managed separately and are not immediately erased by a live-data deletion request.

You can revoke Google access at Google Account connections. Revocation prevents further authorized API access but does not itself delete LearnzyGo's existing records. Removing a local credential does not delete videos already uploaded to YouTube; the channel owner can manage or delete those videos in YouTube Studio.

A separate, access-controlled interface lets authorized reviewers connect a YouTube test channel they control, read its channel and video status, and explicitly approve a fixed private test upload. It has no access to family records or the production operator's YouTube credential. It uses the same upload implementation as the operator tooling and performs authenticated channel and video reads.

Review authorization tokens and channel results are held only in server memory for at most one hour. Disconnecting or signing out removes them sooner, and a service restart also clears them. Review tokens are not written to the application database, backup files, or access logs. Uploaded test videos remain in the connected YouTube channel until its owner removes them in YouTube Studio.

A parent may invite one email address to a learner profile. We use that address only for the invitation, authentication, security, and service messages. Invitations do not include the learner's name, age, photo, answers, or progress.

A learner login can access and edit only its linked profile. It cannot see siblings, Parent Area, family settings, billing, or subscription information. The parent can revoke the login while preserving the profile and learning history.

Visitors may submit a display name, email address, and plain-text comment on an article. Comments remain private until a LearnzyGo content administrator approves them; approved display names and comments become public.

LearnzyGo does not expose submitted email addresses. The email and request IP address are converted into keyed hashes and used to limit spam and abuse. Administrators can edit, approve, reject, and reply to comments during moderation.

Visitors and signed-in parents may voluntarily provide an email address for the three-part Calm Maths Starter and weekly parent toolkit. LearnzyGo sends a confirmation link first and does not add the address to promotional delivery until that link is confirmed.

We record the consent-text version, confirmation and withdrawal times, the signup placement, and bounded campaign values such as UTM source, medium, campaign, and content. We do not store the raw signup URL, and newsletter segmentation does not use child profiles, learning answers, scores, photos, or practice history.

Every promotional email includes a signed unsubscribe link. Unsubscribing stops the starter course, weekly toolkit, and other promotional email without affecting account, security, billing, or service messages. Invalid addresses and delivery complaints may be retained in a suppression record so they are not contacted again.

With a parent or visitor's permission, LearnzyGo uses Google Tag Manager and Google Analytics 4 to measure public page visits, the parent signup and trial journey, plan and checkout activity, and coarse milestones such as creating a learner profile or starting and completing a quest.

We do not send Google names, email addresses, child details, ages, profile or practice-session identifiers, answers, scores, photos, authentication tokens, or unrestricted URL query parameters. Campaign parameters such as UTM values and Google click identifiers may be used for attribution when consent is granted.

Google Ads may receive imported signup and subscription conversion events from Google Analytics. LearnzyGo does not enable personalized advertising based on a child's learning activity.

Optional Google tags remain disabled until consent is granted. The consent preference is stored in a first-party cookie for up to 180 days. Analytics event retention follows the configured settings in LearnzyGo's Google Analytics property.

Optional analytics and advertising are disabled on learner authentication pages and throughout a direct learner session, even when the shared browser previously stored a parent consent choice.

Consent can be changed or withdrawn at any time through the Cookie settings link in the site footer or signed-in app. Withdrawing consent prevents future optional events from being sent from that browser.