1. Scope
This statement describes the Bell2go public website, demo and contact forms, website assistant, and Parent App preview. A school production deployment may require an additional school-specific notice that explains the school’s role, local requirements, configured integrations, and approved retention periods.
2. Information we collect
Public website
When you request a demo or contact us, we collect the business contact fields you choose to submit, such as your name, work email, organization, role, phone, scheduling preference, topic, and message. Do not submit student or active pickup information.
Website assistant
We process the questions you send, your selected audience, a random session identifier stored for the browser session, and limited technical request information needed for security and delivery. Do not send student names, pickup codes, account secrets, license plates, medical details, addresses, or live location.
Parent App first release
The current Parent App experience is a preview and uses fictional demo data. If real school pilots are activated, account and service data may include an adult’s name, email, verified phone number, authentication and MFA state, school-approved pickup relationships, notification preferences, device and diagnostic information, and trip-scoped arrival signals. Optional vehicle or camera evidence must never be the sole authority to release a student.
3. How we use information
We use submitted information to answer business inquiries, schedule demonstrations, operate and secure the website, respond to privacy requests, improve accessibility and reliability, and—only in an approved production pilot—coordinate the school-defined dismissal workflow. Identity alone does not authorize pickup. A school must separately approve the relationship and active pickup context.
5. Retention and security
Demo and contact submissions are configured to expire from the website request table after 180 days. Account-deletion request records are configured to expire after 90 days. Expiration may occur asynchronously after the stated period. Operational records for a future school deployment will use documented, school-approved schedules based on purpose, safety, legal, and contractual needs. Bell2go uses HTTPS, private object storage, encryption at rest, least-privilege roles, rate limits, MFA requirements, and audit-oriented controls in its production design; no system can promise absolute security.
6. Your choices
You may choose not to submit a public form or use the website assistant. You can ask us about, correct, or request deletion of information associated with your Bell2go account, subject to identity verification and records that must be retained for security, legal, or school obligations. Submit an account-deletion request. A request receipt is not confirmation that deletion is complete.
7. Children and schools
The public website and business forms are intended for adults and school personnel, not children. Never submit student information through public forms or chat. In a future production deployment, the participating school controls student authorization and provides families with its applicable notice and policies.
8. Questions and updates
Use the Contact Us form and select “Security or privacy” for questions about this statement. We may update this page as the product moves from prototype to approved pilots. Material changes will be identified by the date at the top.