Platform legal documents for website, admin, driver, and parent access

These Terms of Service govern access to and use of the VANGERY website, admin platform, driver PWA or app, parent-facing tools, APIs, and related services. By signing in, activating an account, accepting an invitation, or using any part of the service, the user accepts these terms. If a user acts on behalf of an organization, that user represents that they are authorized to bind the organization to these terms.

Eligibility and account responsibility

• Users must provide accurate information and keep credentials confidential.
• Organizations are responsible for accounts they create, invite, or enable.
• Users must report suspected unauthorized access or security incidents promptly.
• Staff and drivers must follow their organization’s operational and safety rules.

Service description and operational scope

VANGERY provides software for school transportation operations, including user roles, route planning, vehicle and driver management, parent portal features, reports, live operational visibility, notifications, and subscription billing. Availability of features may depend on plan level, customer configuration, third-party providers, or product status.

Customer responsibilities

• Customers are responsible for the lawfulness, accuracy, and ongoing maintenance of the data they load into the service.
• Customers remain responsible for route review, dispatch decisions, and real-world operational judgment.
• VANGERY supports operations but does not replace supervision, on-site verification, or customer-specific regulatory compliance.

No emergency service

VANGERY is not a 911, ambulance, police, medical, or life-monitoring service. ETA, tracking, route, and alert information can be delayed, incomplete, or unavailable because of connectivity, GPS limitations, device settings, traffic conditions, or provider outages. In a real emergency, users must contact the appropriate emergency services immediately.

Location, maps, documents, and signatures

• Route, ETA, geolocation, and optimization outputs are operational aids and are not guaranteed to be perfectly accurate.
• Document, signature, initials, receipt, and photo workflows depend on customer configuration and may require additional retention, policy, or regulatory review by the customer.
• Parent-facing status, acknowledgements, and delivery confirmations are operational records and may include supporting metadata.

Billing and suspension

Subscription charges, add-ons, payment failures, and suspension rules may be managed through Stripe or another authorized billing channel. Access to some administrative functions may be limited if a subscription lapses or if a trial ends without payment.

Prohibited use

Users may not misuse the platform, attempt to bypass access controls, export or exploit data outside permitted workflows, upload malware or fraudulent content, or use student, family, or location data for unauthorized surveillance, advertising, or unrelated commercial purposes. The Acceptable Use Policy below is incorporated by reference into these terms.

Availability, warranties, and limitation themes

The service is provided on an operational, evolving basis. VANGERY works to maintain security and reliability, but uptime, perfect accuracy, and uninterrupted availability are not guaranteed. To the maximum extent permitted by applicable law and any signed customer agreement, indirect, incidental, special, and consequential damages are disclaimed.

This Privacy Policy explains how VANGERY handles information collected through the website, administrative platform, driver tools, parent-facing features, support, and billing workflows. Depending on context, VANGERY may act as a direct operator for its own business data or as a service provider acting on behalf of a transportation organization or school customer.

Information categories

• Account data such as usernames, email addresses, phone numbers, roles, and authentication records.
• Customer organization details such as billing status, operational settings, and account contacts.
• Driver, vehicle, and route data, including route assignments and operational telemetry when enabled.
• Parent and family data, including membership, notifications, acknowledgements, signatures, and uploads.
• Student-related operational data entered by the customer, such as names, addresses, school or center links, service windows, transport status, ETA context, and delivery confirmation records.
• Technical, security, and audit data such as IP addresses, session events, usage metadata, and logs.

How information is used

• To create and secure accounts and enforce role-based access.
• To operate routes, ETAs, alerts, parent-facing features, and driver workflows.
• To deliver invitations, password recovery, SMS verification, and service notifications.
• To process subscription payments, prevent abuse, troubleshoot issues, and improve reliability.
• To comply with legal, contractual, safety, audit, and security obligations.

School and student context

VANGERY is designed for organizations managing school or family transportation. In that context, customers control what student or family data they provide to the platform and are responsible for the notices, permissions, and legal authority required to share and use those records. VANGERY does not sell student data and does not use student data for third-party behavioral advertising.

Location and sensitive operational data

The platform may process precise driver location and pickup or delivery addresses in order to support transportation operations, ETA visibility, operational audits, routing, and incident review. VANGERY does not authorize use of precise operational location data for unrelated advertising or data broker activities.

Sharing and subprocessors

Information may be shared with authorized users of the customer organization, with linked parents or guardians based on customer permissions, and with service providers that help operate hosting, communications, mapping, authentication, monitoring, and billing infrastructure. Information may also be disclosed when required by law, to respond to valid legal process, or to protect people, rights, and system integrity.

Retention and rights

VANGERY keeps information for as long as reasonably necessary to provide the service, comply with customer instructions, maintain security and audit records, support billing, and meet legal or contractual obligations. Depending on the legal context and the role of the customer organization, some privacy requests may need to be directed first to the organization that controls the underlying school or operational records.

Security

VANGERY applies administrative, technical, and organizational safeguards designed to protect the confidentiality, integrity, and availability of the service. No system is perfectly immune to risk, so users should protect credentials, use strong passwords, and report suspicious activity immediately.

VANGERY uses cookies and similar browser storage technologies primarily to keep users signed in, preserve basic interface state, support security, and maintain reliable operation of the product.

What is used

• Session cookies that help authenticate users and maintain secure access.
• Browser storage used to preserve interface preferences or limited session state.
• Technical storage that supports product functionality and security safeguards.

What the policy does not imply

This document does not promise a full advertising or analytics consent framework, and it should be read together with the actual technologies the product is using in production. If VANGERY adds non-essential cookies or similar technologies in the future, additional consent or preference controls may be introduced where required.

User choices

Users can usually manage cookies through browser settings. However, disabling essential session cookies or required storage may affect login, route access, and other platform functions.

VANGERY may support account, security, invitation, verification, route, ETA, incident, and support communications through SMS, email, push notifications, or similar channels. Some of these communications may be sent by or on behalf of a customer organization.

Typical message categories

• Invitation and account activation messages.
• OTP or verification messages for account access and security.
• Password recovery or account validation flows.
• Operational alerts, route changes, ETA updates, and delivery confirmations.
• Support and account notices, and marketing communications only where legally permitted.

Consent and carrier terms

By providing a phone number and using a text-enabled flow, a user confirms that they are the subscriber or authorized user of that number and authorizes service-related messages connected to the requested workflow. Message and data rates may apply. Delivery is not guaranteed and can be affected by carriers, device settings, coverage, regional limits, or provider restrictions.

STOP, HELP, and START

Where supported by the configured channel, standard keywords such as STOP, HELP, and START may be available for managing SMS campaigns or transactional programs. Availability can depend on number type, carrier behavior, and messaging provider configuration.

Customer responsibility

Organizations using VANGERY communications are responsible for having the authority, notices, and consent required by applicable law, and for respecting opt-outs, quiet hours, and prohibited content rules.

This notice applies to drivers, operators, and field staff who use the VANGERY driver PWA or app. Depending on customer settings and device capabilities, VANGERY may request access to precise location, notifications, camera or photo access, and related device permissions.

How location may be used

• Live operational visibility and route tracking.
• ETA calculations and route progress monitoring.
• Operational event validation, audit history, and incident investigation.
• Support for check-in, check-out, or route status workflows when enabled.

When collection may occur

• While the app is open and actively being used.
• In some workflows, while the app is in the background if the operating system, customer configuration, and granted permissions allow it.
• At intervals or trigger points defined by the operational logic of the product.

Important limitations

GPS, connectivity, battery settings, browser behavior, and operating system rules can affect accuracy and background delivery. Disabling permissions or force-closing the app may reduce visibility, delay ETA updates, or prevent certain route workflows from working correctly.

Driver responsibility

Drivers are expected to use only their assigned account, keep required permissions enabled when route duties depend on tracking, avoid manipulating route or location data, and report device loss, access issues, or unexpected behavior promptly.

VANGERY may only be used for lawful, authorized, and service-related purposes. This policy applies to customer organizations, staff, drivers, parents, guardians, and any other authorized users.

Prohibited activity

• Sharing accounts or credentials without authorization.
• Attempting to bypass authentication, permissions, MFA, rate limits, or tenant boundaries.
• Accessing data belonging to another organization, family, or student without authorization.
• Exporting, reselling, or disclosing platform data for unrelated or unauthorized purposes.
• Uploading malware, harmful scripts, fraudulent content, or illegal material.
• Using location, student, family, photo, or document data for targeted advertising or improper surveillance.
• Sending spam, deceptive messages, harassment, or abusive communications.
• Falsifying route events, signatures, status updates, deliveries, or location records.

Enforcement

VANGERY may warn, suspend, restrict, remove content, terminate access, or report abuse when reasonably necessary to protect the service, people, customer data, or legal compliance obligations.

Some documents from the VANGERY legal pack are not best placed in the day-to-day product footer or the first-login acceptance flow. They are typically shared during onboarding, procurement, district review, or enterprise contracting instead.