Privacy Policy

1. Scope, identity and roles

EasyKids2Go is the child transportation management platform comprising the website, business dashboard, adult-user applications and related services. The identified operator is EASYKIDS2GO LLC. Its software business relationship is with customer organizations, including transportation companies, schools and daycares; parents, guardians, drivers and administrators use features appropriate to their roles.

The organization identified in each family's transportation agreement provides transportation and manages its operations and authorized users. BabyBus, where applicable, is one such transportation company, not the default operator of EasyKids. The transportation company's agreement, charges, custody authorizations and responsibilities remain separate from the software Terms and this notice. This separation does not remove either party's own duties.

EasyKids processes information to administer its business accounts, billing, security and support. It also facilitates processing of records supplied by the customer and its users to manage transportation. For entrusted processing, it will follow the customer's valid documented instructions and the applicable DPA; it does not claim to be a processor for every use. Each party's legal role depends on its activities, data, applicable law and actual agreements. A customer does not acquire absolute ownership of personal records or universal authority over a family by subscribing to the software.

This document is a notice. Receiving or opening it, or using the Platform, does not constitute universal consent. Acceptance of Terms, device permissions and any required specific consents are handled separately. The DPA is for the authorized business representative; it is not an agreement for every parent or driver to accept indiscriminately.

2. Data and sources

Information depends on the features used and on what adults, customers and providers supply. A field's availability does not mean every person must complete it. Only information necessary for authorized purposes is to be retained, under the applicable purposes and restrictions.

Payment credentials are processed directly by the payment processor; the Platform does not store full payment card numbers or CVV security codes. Do not send passwords, full card details, pickup codes or unnecessary sensitive records in a support request.

A child's QR code encodes a reference, not the child's complete descriptive data; that reference still needs protection if it can be linked to the child. A driver-handover QR code can include the handover code and transferred children's names. Not all QR codes should be treated as anonymous.

3. Location and offline operation

Operational GPS covers the driver's online shift, including intervals between trips or without an active trip. It starts when the driver goes online, and the shift flow is designed to stop when the driver goes off shift. Location can be collected in the background with the corresponding permissions. Being “online for the shift” describes the work status in the app and does not guarantee a constant internet connection.

Driver location may include position, speed, heading, accuracy and event/receipt times. Collection and transmission vary with movement, active feature, app version, permissions, signal, battery and operating-system suspension. The server filters samples, including stale or near-duplicate points; not every captured or transmitted sample becomes a stored location. Continuous capture, delivery or a fixed interval is not guaranteed.

Authorized office staff can consult live location throughout the online shift and retained history, including the day's last recorded position. Parents and guardians can see the vehicle while it serves their child's trip and replay the part of a completed trip that served the child while points remain available. A last stored location does not establish the current position.

Without internet, some features use prepared data and events awaiting synchronization. Complete information, always-available navigation, immediate alerts and continuous transmission are not guaranteed; later synchronization must distinguish event time from receipt time. A successful route-continuity test does not demonstrate operation under every suspension, device or scenario. The transportation company must maintain contingency and custody-verification arrangements.

During turn-by-turn navigation, the device’s mapping provider (Google Maps / Navigation SDK or Apple Maps, depending on device and feature) processes device location and route geometry under that provider’s technical service. Separately from operational shift GPS, the mobile welcome screen may send an approximate location rounded to one decimal of a degree (approximately 10 km, varying by latitude) directly from the device to the U.S. National Weather Service (api.weather.gov) to display local weather without passing through EasyKids servers or being stored as shift tracking.

4. Purposes and excluded uses

We process information to manage accounts and routes; supervise fleets during online shifts; support navigation, estimates, absences and notices; verify pickups, drop-offs and handovers; facilitate conversations and support; administer documents; bill for software; diagnose faults, protect accounts and prevent fraud; handle requests and comply with applicable obligations. Relevant records may also be preserved for specific disputes as described in section 9. Product improvement does not authorize unrestricted secondary use of children's records.

The Platform does not incorporate automated artificial-intelligence profiling or automated decision-making features that evaluate users or children, and does not transmit Customer Data or child records to external AI model-training services. Internal software engineering tools are prohibited from receiving real customer or child records. Any future feature involving new categories of processing would require prior privacy review, minimization, contract updates and required notices or consents before activation.

EasyKids does not sell personal information or share personal information for cross-context behavioral advertising, third-party advertising cookies or cross-site behavioral tracking. Legal definitions of “sale” or “sharing” are applied according to the governing statutory regime and actual data flows.

5. Access and disclosures

5.1 Participants and personnel

Parents and guardians: can access information linked to their child and authorized for their role, including trip status, assigned driver/vehicle information and live or replay vehicle location within section 3’s scope. In-app messaging between parents and drivers does not disclose the driver’s personal email, personal telephone number or home address to the parent. A technical account link does not by itself establish legal guardianship or override court custody restrictions.

Drivers: receive information for children assigned to their routes, including child name, the primary adult’s photo, stop addresses, reported absence reasons and notes, and pickup/drop-off verification details. Handoff may show the guardian’s name and phone; chat and assistance may provide guardian name, photo, email, phone and addresses. Driver permissions also cover age, school, grade, transportation-related medical notes, allergies, disability or assistance needs and emergency contacts; visibility depends on the authorized workflow. Drivers do not receive the child’s date of birth or internal student link code. They can view incidents they submitted. Each field remains subject to section 7’s necessity and minimization rules; field availability is not permission for unrelated use.

Customer office: authorized administrators and office staff manage their organization’s users, children, routes, schedules and compliance documents; consult live and retained shift location history, incidents, absences and authorized adults; and can review driver-parent operational conversations (including attachments and voice notes) for safety, quality and dispute resolution. The standard self-service company data export currently generates one JSON file in an AES-256 encrypted ZIP archive, containing structured records, message text and incident metadata; binary media files (such as chat attachments, voice notes and incident photos/videos) and raw GPS point tables require separate assisted retrieval through a separately coordinated secure process.

Documents and EasyKids personnel: access controls enforce tenant isolation by company and role: administrators access their organization’s documents, drivers access their own profile credentials, and parents access their own and linked-child documents where authorized. Authorized EasyKids personnel access minimum necessary records only for support, security, maintenance and billing administration, without unrestricted cross-company browsing.

5.2 Other circumstances

We may disclose the minimum information necessary where there is a valid basis to comply with an obligation or legal process, protect a person's safety, or investigate fraud or incidents. Requests are assessed for authority, scope and applicable restrictions; an informal request does not automatically grant access. Disclosure will be limited and notice provided when required and permitted.

A reorganization or business transfer may require evaluation of access to or transfer of certain records, with confidentiality, compatible purposes and required notices or authorizations. It is not permission to sell personal records or withdraw historical commitments. A change of entity or an edit to this policy does not prove a transfer has occurred.

6. Services and providers

The following services support the described functions, subject to their actual use. Contracted processors acting on our behalf must be distinguished from services that determine their own purposes. This functional inventory is not a certification of each provider’s contractual role or processing locations. Dashboard and public-site fonts are served from EasyKids resources; those font loads do not request Google Fonts.

The DPA details the rule for planned subprocessor changes: valid notice at least 30 calendar days before new processing, 15 days for a reasoned objection, resolution or exit from the affected service with return of unused prepaid fees; the corresponding subscription as a whole if inseparable. A documented emergency permits shorter notice only where law and contract allow, with protection and notice as soon as possible. These terms do not themselves establish completed notices, agreements or transfers. They do not reduce legal rights or turn silence into consent to new uses.

7. Children, health and authority

The Platform is intended for adults; there is no account role intended for direct use by children. Information about children is supplied by adults and organizations. If it becomes known that a child is using an adult account or directly providing data, the facts and required safeguards must be assessed. Adult accounts do not by themselves certify COPPA compliance; that law's application depends on the service and actual collection. See the FTC's guidance, section A.

A student code links an account to a record; it does not prove guardianship, pickup authority, authority to authorize others or verifiable parental consent where required. These powers must be distinguished from viewing location or information and verified with regard to custody restrictions and other people's rights. The customer must maintain lawful, current instructions; EasyKids retains its own access, security and processing obligations.

Minimization: request and show information necessary for transportation, such as relevant allergies, assistance or mobility needs, emergency contacts and authorized plans needed during the ride. Do not request a complete medical record by default. Specific documents require a justified need or applicable obligation. Driver: necessary information for children on the driver's route; office: authorized personnel who need it; parents/guardians: verified authority and custody restrictions. The fields and access described in section 5 remain subject to this minimization rule.

Parents and guardians may request review, correction or deletion of the child's information, or limit collection based on their consent, according to their authority and applicable rights. Identity and authority will be verified with proportionate information. If a restriction affects a necessary service feature, its effect will be explained and a safe exit coordinated with the transportation company, without automatically canceling transportation or deleting custody evidence.

School, health and transportation data require classification by customer and processing activity. FERPA, HIPAA or state rules neither apply nor become inapplicable solely because a service is called a “school,” “daycare” or “transportation” service. Notices, school agreements or BAAs will be assessed when appropriate before offering the affected processing; a general DPA or a parent's acceptance does not replace them. The Platform does not diagnose or provide medical treatment.

Registration and acceptance flows may record an adult’s own declaration of guardianship or authority to represent an organization, together with account links and the time of the declaration. These are declarations by that adult, not independent certification of guardianship, a court order or corporate powers; their presence cannot be assumed for every historical account.

8. Security and incidents

EasyKids maintains technical, physical and administrative security controls designed to protect personal information in accordance with applicable data-security laws (including Massachusetts 201 CMR 17.00 and M.G.L. c. 93H where applicable). Active technical safeguards include TLS/HTTPS encryption in transit, cryptographic password hashing, role-based access controls, multi-tenant logical separation between customer organizations, session and token revocation, automated rate limiting, and security/activity logging. Selected sensitive fields, exported archives and off-site Backblaze B2 backups are encrypted prior to storage or transfer; this does not represent full-disk or full-database encryption of every active table at rest.

EasyKids must maintain safeguards proportionate to its processing and comply with applicable duties, including establishing, implementing and maintaining a written information security program (WISP) where 201 CMR 17.00 applies. This notice is not a certification, security audit or representation that every administrative control is complete. No transmission or storage method guarantees immunity from every attack or error; that limit does not reduce enforceable duties.

Incident response: assess signals, contain affected access or systems, preserve relevant evidence and document decisions, while coordinating safe continuity with the transportation company. Do not retain compromised access merely because a trip is active. A routine failure or rejected attempt does not itself establish compromise; certain duties may arise before final confirmation.

When the relevant contractual or legal trigger occurs, EasyKids will notify the affected customer's authorized contact without undue delay, with available information, measures and next steps, and provide updates. It will not await a definitive report where earlier notice is required. The parties will coordinate communications to individuals and authorities according to their roles, data and jurisdiction; EasyKids' own duty will not depend on customer permission. No universal 72-hour deadline is promised. As a conditional reference, Massachusetts c.93H §3 distinguishes roles and notification circumstances.

Critical reports and after-hours alert receipt are distinct from continuous monitoring or response. Ordinary support hours do not defer incident obligations to the next business day. Section 14 describes contact and support scope.

Coordination: business liability calculations, costs and continuity after cancellation/reactivation are set out in Terms §11 and DPA §15. They do not turn this notice into contractual acceptance or automatically limit individuals’ rights. Canceling, renaming or reactivating a subscription does not authorize mixing companies, indefinite retention or new processing without the corresponding basis.

9. Retention, deletion and exit

Retention principle: retain by category, purpose and necessity; review and effectively delete or anonymize when the purpose ends and there is no valid basis for retention. The abstract possibility of a claim does not justify keeping everything indefinitely. A specific legal hold must document reason, scope, restricted access, review and end. A record that still allows identification is not described as anonymous.

Deleting an adult account, closing a company, canceling renewal, returning information and deleting children’s records are different processes. Existing rights and applicable commitments remain enforceable; this text does not withdraw or silently extend them.

Where a request cannot be fully honored because of another person's rights, a valid instruction or a specific preservation duty, its scope and basis will be explained as appropriate, use/access limited and review maintained. A generic indefinite reservation will not be invoked because a schedule is missing.

Business exit: one standard export at no additional charge, requested before or within 30 calendar days after the effective end of service, for a verified representative and data within their authority. It includes usable structured records (CSV/JSON according to type), documents and signatures in their retained format with necessary relationships, dates and authorship; it excludes other companies, secrets, passwords and code. Delivery target: 10 business days from a complete verified request, with delay information and compliance with binding deadlines. Correcting our own defects does not consume another paid export; extras require a quotation and acceptance. The DPA details this service.

The 30 days are a request window, not an automatic deletion date, download deadline, renewal or free operational access. A valid pending request can be completed later; closure or debt does not justify improperly withholding data. Individual rights in section 10 have their own rules.

10. Rights and requests

We preserve the historical ability for all users to request access and a copy, correction, deletion review and portability of their information, and withdrawal of consent where consent is the basis for processing. Withdrawal does not make prior valid processing unlawful. The existence, scope and exceptions of additional legal rights—including limits concerning sensitive data, objections to certain uses, appeals or representation—depend on jurisdiction, activities and data; nationwide application of a state law is not presumed.

Where relevant, requests can include categories and specific information, sources, purposes and recipients. A guardian must act within their authority; an organization must distinguish its records from individuals' rights. EasyKids will cooperate with the customer for entrusted processing, without disregarding requests concerning its own roles or unduly delaying handling through repeated referrals.

1. Contact the channel identified in section 14, identifying your request, relevant account or relationship, and a safe way to respond. Do not send a complete identity or medical record by default.
2. We will proportionately verify identity, authority and, where a representative acts, their powers. We will request only necessary information and protect it; a simple account association will not justify disclosure of other guardians', children's or companies' records.
3. We will confirm scope and status, coordinate as needed with the responsible entity, and explain the decision, exceptions and appeal or complaint routes where applicable. Additional information will be requested without undue delay; irrelevant requests will not restart deadlines.

Requests will be handled according to applicable deadlines and conditions, with identity and authority verified before disclosure or modification of protected records. Verification does not automatically permit delaying the start of a deadline. Any permitted extension needs its corresponding basis and notice; an initial response will not be confused with completed deletion or delivery.

A person will not be discriminated against for exercising privacy rights. If honoring a request prevents a feature that needs those data, the objective consequences and safe alternatives will be explained, without penalizing the exercise of a right. Waiving a right is not a condition of requesting review. Where law provides an appeal, authorized representative or complaint to a competent authority, corresponding instructions will be provided.

Where an earlier applicable Privacy notice promises a response to requests or inquiries within 30 days of receipt, that commitment is preserved, together with any shorter mandatory deadline. A longer statutory maximum does not replace it. A response does not by itself establish completed deletion or delivery.

11. Devices, cookies and communications

The Platform uses session and security technologies and local storage for preferences, tokens and data prepared for offline features. Users can control cookies through their browser; blocking necessary cookies can prevent features from working. Device copies need protection and handling consistent with section 9.

The website, business dashboard and mobile applications do not use third-party advertising cookies, cross-site tracking pixels or behavioral analytics trackers. Operational server logs, Firebase Crashlytics diagnostics and transactional email delivery metadata are used strictly for service reliability and security. Adding any future analytics tool would require prior privacy review and updated notice before deployment.

Firebase Cloud Messaging, and Apple on iPhone, deliver notices using tokens and trip, message and alert content. In the app, parents can disable trip, message and payment push notifications; in-app notices remain. Critical child-safety, emergency and account-security alerts do not have a disable option within the service. The operating system may prevent push delivery; generating an alert does not prove receipt, reading or attention.

Disabling permissions can affect location, notifications or other features; it does not mean canceling transportation, deleting history or withdrawing every consent for another purpose. Unsubscribing from commercial communications is handled separately from necessary security, account or service notices. Waitlist communications provide an unsubscribe option; withdrawing communications and requesting erasure are separate actions.

For optional office announcement emails, a disabled email preference is checked again when queued messages are dispatched, as well as when future sends are scheduled. This preference governs that email channel; it does not remove in-app notices or necessary account, custody, security and service notices. A message already dispatched cannot be recalled by changing the preference.

12. Processing locations

The principal infrastructure is in the United States and the intended market is nationwide. This does not establish that every provider, backup or support access remains exclusively there. The DPA's provider annex must identify actual entities, services, locations and access.

If the Platform is accessed from another country, necessary data may be processed in the United States. Differences in law will be assessed for the circumstances. Where a particular transfer mechanism, notice or consent is required, it must be satisfied before the corresponding processing; Platform use does not establish that by itself. This notice does not claim automatic GDPR application or worldwide compliance.

13. Changes and notices

Changes require identification of affected practices, exact version and text, summary and effective date, while honoring prior commitments and enforceable rights. The notice rule is: at least 30 calendar days' notice of material changes by email and persistent app/dashboard notice, where that rule governs the change. Commercial terms for paid subscriptions will ordinarily apply from a renewal following valid notice under the Terms.

That period does not justify keeping inaccurate privacy information or delaying a required correction or action. A legal or security urgency permits shorter notice only where allowed, limited to necessity and communicated as soon as possible; it is not an exception for commercial advantages. A new use requiring specific consent does not begin merely because a page is published or a notice period expires.

Notices to affected parents/guardians and renewed consents will be addressed where required. Historical documents and receipts will be preserved without reassignment to this version. Sending, recipient-server acceptance, opening, screen presentation and legal acceptance are different events. Available evidence of each will be recorded and bounces addressed; receipt or consent is not fabricated from silence.

The acceptance flow will be presented at a safe time, preserving routes, custody and pending synchronization. Privacy remains a notice; required specific consents and contractual acceptance are separate.

14. Contact and support

EASYKIDS2GO LLC · EasyKids2Go · 82 Wendell Ave., Ste 100, Pittsfield, MA 01201, United States.

Contact easykids2go@gmail.com for support, privacy, legal notices and billing, or write to EASYKIDS2GO LLC, 82 Wendell Ave., Ste 100, Pittsfield, MA 01201, United States. A different functional address applies only after it has been designated and communicated through a verified channel, with continuity for pending requests. A valid request does not need to be repeated to multiple mailboxes. The accepted service order identifies each party’s contractual, privacy and critical-incident contacts. Receipt and support follow the applicable notice rules and ordinary hours; this is not continuous human monitoring.

We respond to privacy and deletion inquiries within 30 calendar days of receipt or a shorter applicable deadline. Identity and authority are verified before protected records are disclosed or changed; verification does not arbitrarily restart the clock. A response is distinct from completed execution. Do not send passwords or unnecessary sensitive records.

Ordinary support hours are Monday through Friday, 09:00–18:00, America/New_York, except U.S. federal holidays. After-hours alert receipt is not 24/7 support or continuous human monitoring; ordinary support hours do not postpone applicable data-incident or legal notice duties. Transportation emergencies must be directed immediately to the carrier or 911 / emergency services.