Privacy policy
This policy describes the invitation-only preview. Invited test accounts can sign in through Google to manage connections and notification preferences. Public registration is not open. Contact luffyzhng@gmail.com for privacy questions or a deletion request.
Who the service is for
SchoolBridge is intended for adult parents, not for children to register or connect their own accounts. School communications may contain children's names, dates, learning information or other sensitive details. Only connect a mailbox you are authorized to use. An adult's consent does not authorize unrelated use of information about other people.
Registration, sign-in and mailbox connections
Website accounts use Google OpenID Connect with only openid and email to verify identity. We store the verified email, Google subject identifier, account creation time and applicable terms-consent record. We do not collect your Google password or persist access/refresh tokens returned by the identity sign-in flow. Website session cookies last seven days. Gmail is separately authorized after sign-in; disconnecting Gmail preserves the website account and other channel links. Deleting the website account removes its associated family and local data. Existing Gmail-verified test accounts are retained through migration and may subsequently sign in with Google identity.
What Gmail access means
Invited adults authorize gmail.readonly with offline access. The current parent connection test reads the Gmail profile to verify account ownership and stores an encrypted refresh token. Signing in alone does not register a watch or read message headers/bodies. Parents may separately enable header-only monitoring: Gmail pushes mailbox-change metadata to our authenticated endpoint, we periodically check history every fifteen minutes, and we renew watches daily. Candidate sender/subject headers are examined, including non-school messages; only exact school-sender matches are saved as encrypted metadata for up to 30 days. No message bodies or AI requests are used in this mode. Monitoring can be paused in the account page. The following sender-filtered processing describes the separately consented backend pilot, not automatic activation from signing in. This Google permission can read email messages and settings across the mailbox. Our application checks sender headers and retrieves full bodies only for exact school sender addresses configured for the preview. This filter is not a restriction enforced by Google on the token.
The backend examines candidate message headers, including sender and subject, even when the message is excluded. Matching messages are limited to those received after connection and within the retention window. We process subject, sender, received time and extracted body text, currently limited to 24,000 characters. Attachment contents are not processed by OCR.
What we collect and why
We store the connected Gmail address, encrypted refresh token, synchronization cursor and status; the family label, timezone, school sender list and consent timestamps; matching source text, AI summaries and evidence; and delivery/job metadata. An optional WhatsApp number and opt-in timestamp are stored only when separately provided with consent. A number entered on the parent page is encrypted and remains unverified until a signed provider callback proves possession; it is not enabled for sending just because it was entered. We use this information to synchronize school messages, prepare review drafts, operate the preview and respond to support or deletion requests. We do not use Gmail data for advertising, resale, credit decisions or unrelated profiling.
AI processing and providers
After separate test-processing consent, new exact-sender emails with subjects starting [SchoolBridge Test] may send body text, subject, sender and received time to Alibaba Cloud Qwen for Chinese or English summaries and source-linked actions. Use fictional content without real child, health or payment data. Other email subjects are not fetched as full bodies in parent test mode. Text is not automatically redacted before the request. The configured inference endpoint is in the United States. The account page can also generate a fictional sample without reading Gmail. Both sample and Gmail test processing use the real provider. Test AI is limited to 20 attempts per family per Beijing day, including failed calls.
We do not intentionally use Gmail data or derived summaries to train a shared or general-purpose AI model. Alibaba Cloud’s published privacy notice states that customer data is not used for model training and that request data is stored under applicable requirements. We have not independently verified the exact account’s retention, logging or human-access boundaries and do not promise zero retention. Real school/child-data processing remains outside this fictional-content test until those safeguards and the required consent are resolved.
The application and active SQLite database run on an Alibaba Cloud server in Singapore. Configuration secrets are stored in restricted server files. Cloudflare provides DNS; a retired D1 database and migration backups are temporarily retained for recovery. Encrypted daily backups are kept on the server, with a migration backup also held on the operator’s local computer. Qwen inference remains configured in the United States. The operator is based in China; cross-border processing and operator access may occur. These locations do not guarantee every provider operation stays in one country.
If optional WhatsApp delivery is enabled in the future, Meta/WhatsApp will receive the recipient's number, summary text and delivery information. Summaries remain source-derived personal data. Sending is currently disabled; separate opt-in, account configuration and approved templates are required.
Optional mainland China SMS preview
SMS delivery is disabled. If this separate channel is activated later, an adult must verify control of a mainland China mobile number and explicitly opt in. The current admin-only pilot records the operator's assertion of verification and consent; it does not offer self-service phone verification. We encrypt the number and retain a keyed identifier for duplicate and quota checks. A configured Alibaba Cloud SMS integration would receive the destination number, an approved fixed-template identifier and an opaque delivery reference, not school email text or AI summaries.
The pilot defaults to at most three submission attempts per family account and per number per Beijing calendar day. Failed or uncertain submissions also consume this allowance. Submission is not proof of delivery or reading; carrier SMS segments and charges can differ from API attempt counts. Contact details remain until unsubscribed or the family is removed. Delivery records are eligible for periodic cleanup after 30 days; keyed daily counters remain for about 31 days even after unsubscribe or account removal to prevent quota resets. You may ask the operator to stop future SMS notifications. SMS activation still requires provider eligibility, approved signature/template and a working private account-viewing flow.
Optional WeChat official-account connection
Invited adults may link their WeChat identity by sending a private, single-use binding command to our official account. The parent can generate the ten-minute command after Google sign-in verifies control of the intended family account; an operator can also issue it after separate ownership verification. We receive WeChat identifiers and message/event metadata through an authenticated, encrypted callback. Stored OpenIDs are encrypted; keyed identifiers route each parent to the correct family. A family may have more than one linked parent; a WeChat identity cannot be silently moved to another family. Unfollowing the account removes that identity's link, and the operator can disconnect all links and pending commands on request.
General inbound chat, school messages and attachments are not retained or forwarded to AI by this integration. Messages are inspected transiently for supported commands. A linked parent can send updates to retrieve the latest family summary by encrypted passive reply, and enable notifications or stop notifications to record or withdraw that identity’s proactive opt-in. Encrypted passive replies, including summaries you request, and deduplication metadata may remain in a replay cache for about 24 hours, including after unlinking or family removal. Expired binding codes are periodically removed. Binding is not permission for proactive notifications. Proactive delivery requires separate opt-in, actual account API permission, AppSecret and an approved configured template; it remains disabled until configured. Receiving callbacks and passive summary replies do not require AppSecret.
Consent and human access
The parent connection test requires an invitation allowlist, a direct Gmail-connection consent checkbox and Google authorization of the intended email. We record that consent timestamp and policy version. Successful authorization creates a seven-day secure, HttpOnly session cookie; a ten-minute browser nonce protects the authorization flow. Neither sign-in nor channel binding activates AI or background synchronization. Existing admin-provisioned processing pilots separately record explicit AI consent and WhatsApp opt-in. Google permission alone is not consent to undisclosed processing.
Authorized operators have technical access to source messages and summary drafts through the admin API. We do not treat general onboarding consent as permission for routine staff reading. Human review of specific content requires your explicit agreement, except where access is necessary for security investigation or legal compliance, or another applicable Google policy exception. Support requests must not include school content unless a specific review has been agreed.
Retention and deletion
Source messages are eligible for periodic deletion when their received timestamp is more than 30 days old; related summaries and drafts are removed with the source. This is a cleanup window, not an exact deletion-time guarantee. Operational metadata, routing details, consent records and tokens may remain while the account is active or until removal. Some job/event metadata is also cleaned periodically.
Account removal deletes the family and associated active database records, including local tokens, messages, summaries and drafts, and attempts to revoke Google authorization. Revocation can fail; you can also remove access in your Google Account. Provider backups, security records and independently delivered copies have separate retention rules; we cannot promise immediate removal from all provider systems or another person's WhatsApp device.
Follow the removal and authorization-revocation instructions. Requests require verification of account control; do not send identity documents, passwords or tokens by email.
Security and cookies
We use HTTPS and context-bound encryption for stored refresh tokens, source content, summaries and drafts. Some routing metadata remains plaintext. Encryption does not eliminate risk, and SchoolBridge has not completed an independent security assessment. These public information pages use no analytics, advertising cookies, external scripts or third-party fonts. The separate sign-in/account pages use essential secure session and anti-forgery cookies and store notification preferences. Login-abuse counters are retained for about one day; expired sessions and authorization attempts are removed periodically. A first-party functional cookie remembers a manually selected language for 90 days. Visiting them does not connect Gmail or authorize AI processing.
Google Limited Use and policy changes
SchoolBridge's use and transfer of information received from Google APIs must comply with the Google API Services User Data Policy, including its Limited Use requirements, and the Google Workspace user data and developer policy. This is a requirement governing the preview, not a claim of completed Google approval.
We will update this page when practices change and obtain renewed consent before materially new processing where required. Contact luffyzhng@gmail.com to exercise data choices or raise a concern.