Dismissal Manager
Home Privacy Terms Contact
Login Start Setup
Menu
Home Privacy Terms Contact Login Start Setup

Legal

Privacy Policy

This policy explains what information Swifty Schools LLC collects through Dismissal Manager, why we collect it, how it is used and shared, and what choices schools and their users have.

Last updated November 2, 2026

On this page
  1. Overview
  2. Privacy at a Glance
  3. Who we are
  4. Our role and your school's role
  5. Information we collect
  6. Information we do not collect
  7. Dismissal tags, notes, and free text
  8. How we use information
  9. Legal bases
  10. When we share information
  11. Service providers
  12. District visibility
  13. Data retention
  14. Security
  15. International transfers
  16. Your rights and choices
  17. Students and children
  18. Cookies and browser storage
  19. Changes to this policy
  20. Contact us

On this page

  1. Overview
  2. Privacy at a Glance
  3. Who we are
  4. Our role and your school's role
  5. Information we collect
  6. Information we do not collect
  7. Dismissal tags, notes, and free text
  8. How we use information
  9. Legal bases
  10. When we share information
  11. Service providers
  12. District visibility
  13. Data retention
  14. Security
  15. International transfers
  16. Your rights and choices
  17. Students and children
  18. Cookies and browser storage
  19. Changes to this policy
  20. Contact us

Overview

Dismissal Manager is a web-based dismissal coordination service operated by Swifty Schools LLC. Schools and districts use it to organize pickup, request and release students, show vehicle tags on a dismissal board, review dismissal history, and give principals, assistants, and staff role-based access.

This policy applies to the Dismissal Manager website, the public pages, the school and district workspaces, and the operational screens used by school staff. It does not apply to a school's own websites, student information systems, or other services that a school may use separately.

Privacy at a Glance

  • No parent accounts
  • No parent emails or phone numbers
  • No student rosters
  • No grades, schedules, or educational records
  • Stripe handles payment card processing
  • Schools control the information entered into dismissal tags and notes
  • District administrators may access school-level operational information within their district

Who we are

Dismissal Manager is provided by Swifty Schools LLC ("Swifty Schools," "we," "us," or "our"). The product name is Dismissal Manager. Our public support address is support@swiftyschools.com.

Our role and your school's role

Schools and districts decide who gets access to Dismissal Manager and what information their staff enters. In most cases, the school or district is responsible for the information it puts into the service and for providing any notices or obtaining any permissions required by its own policies and local law.

We process that information to operate Dismissal Manager, secure the service, provide support, manage billing, and maintain the records needed to run the product. We also collect and control the account and billing information needed to provide the service directly to a school or district.

Information we collect

Account and sign-in information

We collect names, email addresses, usernames, roles, school and district associations, account status, creation and update times, and related sign-in and account-security records, including email verification, account creation, and last sign-in times. Passwords are managed by our authentication provider; we do not store passwords ourselves.

Shared Staff and Assistant Access accounts sign in with a username rather than a personal email address.

School and district information

We collect school names, district relationships, principal and contact names and emails where provided, school setup and pickup-plan settings, dismissal-board settings, lane configuration, time zone, onboarding and Journey progress, account status, and related operational timestamps. We do not collect a school physical address.

Dismissal operations

We collect dismissal queue records, vehicle tags, queue positions, pickup spots, lane assignments, release and undo-release states, request and recovery-alert timestamps, deleted/restored state, and related operational events. We also store dismissal history records containing dates, start and end times, vehicle and release counts, alert metrics, timing and board-visibility metrics, rainy-day state, lane details, notes, and audit information.

Dismissal tags and free-text notes

Dismissal tags are the identifiers staff use to connect a vehicle or arrival to a pickup request. Tags are free-form text. They may be numeric, alphanumeric, or contain multiple words. We do not require student names, and tags are not checked against a student roster.

Dismissal-history notes are also free text. Schools should not enter student names, parent information, grades, schedules, teacher information, educational records, or other sensitive information into tags or notes unless they have a lawful basis and their own policies permit it.

Billing and subscription information

Stripe handles payment-card entry, checkout, billing portals, invoices, and payment processing. We do not store full card numbers or card security codes. We do store billing-related identifiers and summaries such as the Stripe customer and subscription IDs, membership status, billing interval, renewal and cancellation dates, card brand, last four digits, expiration month and year, last payment date, amount, currency, and pending billing-change details.

Communications and support

We collect the information you include when you contact support or respond to service messages. Account and security emails are currently sent for verification, password reset, recovery notices, password changes, and district administrator invitations. Other service, billing, and membership messages may be sent when those features are enabled.

Device, browser, and session information

The service uses browser storage to keep sessions working and remember local choices such as a remembered username, selected lane, board viewer mode, active school context, verification-email timing, demo-mode state, and form drafts. These values are stored on the device and are not a separate advertising profile.

Security and audit records

We keep security, support, billing, affiliation, participation, onboarding, and audit records needed to operate the service and investigate problems. These records can include user IDs, roles, school and district IDs, timestamps, request IDs, status changes, reasons, and in some cases a copy of a record before or after a change.

Information we do not collect

Dismissal Manager is not a student information system and is not intended to be a system of record for educational records. We do not ask for or maintain structured fields for:

  • Student names
  • Student ID numbers or student records
  • Grade levels
  • Class schedules
  • Teacher names or teacher assignments
  • Parent or guardian accounts
  • Parent or guardian names, email addresses, or phone numbers
  • Student rosters or imported school-directory data
  • Student demographics, grades, transcripts, or educational records

A school could still type information like a student name into a free-text tag or note. When that happens, the information is handled as part of that school's dismissal data even though the product did not ask for it and does not structure it as a student record.

Dismissal tags, notes, and free text

Tags are the core operational identifier in Dismissal Manager. Staff enter a tag when a vehicle arrives, use it to request a student, show it on the dismissal board, and connect it to a release. Tags can be numeric, alphanumeric, or multi-word text.

Because tags and notes are free text, the service cannot guarantee that a school will never put personal information into them. Schools and districts are responsible for deciding what may be entered and for training staff. We recommend using non-identifying vehicle tags or pickup codes rather than student names or other sensitive identifiers.

Please do not use tags or notes as a student record. Do not enter grades, schedules, teacher information, parent contact details, medical information, or other educational-record content unless your school or district has reviewed the legal and privacy requirements for doing so.

How we use information

We use information to:

  • Create and secure accounts, authenticate users, and verify email addresses
  • Provide the school and district workspaces and role-based access
  • Run dismissal operations, including tags, queues, releases, alerts, and board display
  • Create dismissal history, timing, activity, Journey, and Insights features
  • Manage trials, memberships, renewals, billing, and district seat coverage
  • Send account, security, recovery, and administrative emails
  • Provide support and investigate reported problems
  • Maintain audit, security, fraud-prevention, and compliance records
  • Improve reliability and understand product usage at an aggregate operational level

Dismissal Manager does not include advertising networks or third-party analytics tracking. We do not use dismissal data to build an advertising profile.

Legal bases

Where the law requires a legal basis for processing personal information, we rely on the basis that applies to the activity. That may include performing our contract with a school or district, complying with legal obligations, protecting the security and integrity of the service, and our legitimate interests in operating and improving Dismissal Manager. Where consent is required, we will ask for it separately.

When we share information

We share information only in the following circumstances:

  • With the school or district. Authorized school and district administrators can access information for their school or district as described in this policy and in the service's permissions.
  • With service providers. We use providers for hosting, data storage, authentication, server processing, payments, email delivery, fonts, and icons. They process information to provide those services to us.
  • For legal and safety reasons. We may disclose information when required by law or when necessary to protect the rights, safety, and security of users, schools, students, or the service.
  • During a business transaction. If the business is sold, merged, financed, or reorganized, information may be transferred as part of that transaction, subject to appropriate safeguards.

We do not sell personal information. Dismissal Manager does not include advertising or third-party analytics trackers.

Service providers

Dismissal Manager depends on third-party infrastructure and service providers. We use:

  • Google Firebase and Google Cloud for authentication, data storage, server processing, website hosting, email delivery, and related cloud services.
  • Stripe for checkout, billing portals, subscriptions, invoices, payment processing, and billing updates. Stripe receives payment-card information directly. Our systems store only billing summaries and identifiers, not full card numbers.
  • Postmark for transactional email delivery when enabled.
  • Google Fonts for the DM Sans and Manrope web fonts.
  • Font Awesome through cdnjs for interface icons.

These providers may process technical information such as IP addresses, browser details, request metadata, account identifiers, payment instructions, and email delivery data as needed to provide their services.

District visibility

When a school is connected to a district, authorized district administrators can see school-level information for schools in their district. This includes school name, adoption and Journey milestones, setup status, administrator sign-in observations, first and latest dismissal dates, continued-usage indicators, activity counts, participation and seat coverage, and the district billing relationship.

District administrators may also have access to dismissal history and current dismissal queue and event records for schools in their district. Those records can include vehicle tags. The district interface does not display raw tags, but authorized district personnel may still access them, so schools should understand this before using identifying text in a tag.

A school's own principal, assistant administrator, and staff access are limited by their roles. District access does not give a district administrator access to a school's Stripe card details in the school's billing records.

Data retention

We keep information for as long as needed to provide Dismissal Manager, maintain school records, meet legal and accounting obligations, resolve disputes, and protect the service. Retention depends on the type of record:

  • Active dismissal queue: deleted when the dismissal is closed. Soft-deleted tags remain only during the active dismissal and are cleared at closeout.
  • Dismissal event records: the event records used for Dismissal Flow, timing, activity, and Insights are retained without an automatic expiry.
  • Dismissal history: records are kept until a principal archives them and then permanently purges them. A permanent purge deletes the live record but writes a complete copy into the dismissal-history audit trail.
  • Dismissal notes: stored with the history record and may also be preserved in audit copies after a purge.
  • Billing and subscription records: retained in our billing records and by Stripe according to its own terms. We do not currently apply an automatic expiry to our billing records.
  • Accounts: accounts can be deactivated. There is no school or principal self-service account-deletion flow. A district administrator can delete a deactivated district school, which removes the school's user profiles, sign-in accounts, school record, and related onboarding data. That deletion is not designed to automatically remove dismissal history, dismissal events, membership plan, billing, subscription, payment-provider, or audit records.
  • Recovery and invitation records: recovery-email links expire after 24 hours, with a 72-hour hold before recovery becomes active. District invitations expire after 7 days; principal invitations expire after 30 minutes. Related security records do not currently have a scheduled cleanup.

Security

We use access controls, role-based permissions, technical safeguards, and established infrastructure providers to protect the service. Our authentication provider manages account credentials and sign-in, access controls restrict school and district data, and Stripe handles payment-card processing.

No method of transmission or storage is completely secure. If you believe an account or school record has been compromised, contact support@swiftyschools.com promptly.

International transfers

Our service providers operate globally. Information may be processed in the United States and in other countries where Google, Stripe, Postmark, and our other providers operate. Those countries may have different privacy laws from the school's location.

Where required, we rely on the safeguards offered by our providers and any additional contractual measures required by applicable law.

Your rights and choices

Depending on where you live, you may have the right to ask for access to your personal information, correct it, delete it, receive a portable copy, object to or restrict certain processing, withdraw consent where processing is based on consent, or complain to a privacy regulator.

Because most school information belongs to the school or district, requests about dismissal records, team accounts, or school data may need to be directed to the school or district first. We will help route the request where appropriate. Send privacy requests to support@swiftyschools.com.

Provide enough information for us to identify the account, school, or record involved. We may need to verify your identity and authority before acting. Some rights are limited by law, by the rights of others, or by records we must keep.

Students and children

Dismissal Manager is provided to schools and districts for use by authorized staff. It is not directed to students or parents, and students and parents do not create Dismissal Manager accounts. We do not knowingly collect personal information directly from children through the service.

Schools may use tags or free-text notes in ways that involve student information. The school or district is responsible for any notices, consents, and educational-records obligations that apply to that use. If you believe a school has entered a child's personal information in a way that should be removed, contact the school or district, or contact us for help routing the request.

Cookies and browser storage

Dismissal Manager does not use advertising or third-party analytics cookies. It uses browser storage for functional purposes such as keeping a session working, remembering a username, remembering a selected lane or board mode, retaining an active school context, tracking verification-email timing, preserving form drafts, and supporting Demo Mode.

Clearing browser storage may sign you out, reset local preferences, or interrupt a draft flow. Some third-party resources, such as Google Fonts and the Font Awesome CDN, receive standard request information when the page loads those files.

Changes to this policy

We may update this policy as the service or the law changes. The updated version will show a new "Last updated" date. If a change materially affects how information is used or shared, we will provide additional notice where required by law or by our agreements with schools and districts.

Contact us

Questions about this policy or how Dismissal Manager handles information can be sent to support@swiftyschools.com.

Swifty Schools LLC
Florida, United States
support@swiftyschools.com

Privacy questions

Contact support@swiftyschools.com for privacy questions, account requests, or help routing a school or district request.

Privacy Policy • Terms of Service
© 2026 SWIFTY SCHOOLS LLC. All rights reserved. Built for the people who make pickup happen.