Voyager is School of Humanity’s learning management platform for middle- and high-school project-based learning. It supports learning units and projects, learning-outcome and credit tracking, sessions and attendance, communications, evaluations, admissions, reports and role-specific portals.
Humanity Education Ventures, trading as School of Humanity (“School of Humanity”, “we”, “us” or “our”), is responsible for the personal information described in this notice except where another organisation tells you that it is responsible. Our registered address is 7901 4th St N STE 300, St Petersburg Florida, 33702.
This notice applies to learners, applicants, parents and guardians, facilitators, pathway advisers, mentors, evaluators, school staff, contractors and other authorised users of the Online School and Voyager. It also applies when a person interacts with admissions forms, booking links, school email, video sessions, public portfolios or support channels connected to Voyager.
| Category | Examples |
|---|---|
| Identity and profile | Name, preferred name, date of birth or age where collected, photograph/avatar, internal identifiers, programme, cohort, grade, roles and account status. |
| Contact and family | Email, phone number, address where required, parent/guardian relationships, emergency or authorised contacts and communication preferences. |
| Admissions and enrolment | Applications, inquiry history, interview or call records, form responses, prior education, enrolment decisions, financial-aid information, agreements and supporting documents. |
| Learning and education records | Units, modules, projects, submissions, feedback, learning outcomes, credits, grades, GPA, progress, reports, transcripts, portfolios and external links or files submitted for learning. |
| Sessions and attendance | Schedules, calendar invitations, Zoom meeting identifiers, participant names, join/leave times, attendance status, absence reasons and evidence, recordings or transcripts where enabled. |
| Communications and community | Announcements, channel posts, direct messages, attachments, email history, mentoring or advising notes, notifications and moderation or safeguarding records. |
| Evaluation, wellbeing and support | 360 evaluations, concerns, support and accommodations information, special learning-difference documents, evidence and follow-up records. These may include health or other sensitive information where relevant. |
| Technical and security | Authentication records, device/browser and network information available to service providers, audit and event logs, timestamps, error information, access activity and security investigations. |
| Operational and contractual | Staff assignments, permissions, service correspondence, consent records, terms acceptance and records needed for compliance, complaints or disputes. |
We receive information directly from the person concerned; from a parent or guardian; from authorised school staff, mentors or evaluators; from a prior or partner school where authorised; from forms and files the person submits; and from services connected to Voyager, including Zoom, Google Workspace, Fillout, Calendly, Airtable and Slack. Voyager also creates records from activity in the service, such as progress calculations, attendance and audit timestamps.
| Purpose | What this includes | Typical basis |
|---|---|---|
| Provide the Online School and Voyager | Operate accounts, learning, assessment, reports, portfolios, communications, sessions, attendance, advising and support. | Performance of a contract; steps before a contract; legitimate interests; and education-law grounds where applicable. |
| Admissions and enrolment | Manage inquiries, applications, interviews, eligibility, offers, financial aid and onboarding. | Steps before a contract; legitimate interests; legal obligations; consent where required. |
| Safety, safeguarding and inclusion | Protect learners and the community, investigate concerns, provide support or accommodations and respond to emergencies. | Legal obligations; vital interests; substantial public-interest or education grounds; legitimate interests; explicit consent where required. |
| Communications and administration | Send service notices, invitations, reports, reminders, family communications and operational messages. | Contract; legal obligations; legitimate interests; consent for optional marketing where required. |
| Security and integrity | Authenticate users, enforce permissions and policies, maintain logs, detect misuse, prevent fraud and preserve service reliability. | Legitimate interests; contract; legal obligations. |
| Legal and organisational needs | Keep required records, respond to rights requests, complaints, regulators or legal process, and establish or defend legal claims. | Legal obligations; legitimate interests; legal claims. |
| Public portfolio or optional publicity | Publish selected learner profile and portfolio material or use optional media. | Consent or another publication basis approved for the learner’s jurisdiction; withdrawal applies prospectively. |
Where data-protection law applies, School of Humanity processes personal information only where it has a lawful basis to do so. Depending on the relevant purpose, relationship, and applicable law, this may include performing or preparing for an education or service agreement; complying with a legal obligation; protecting vital interests; carrying out a task in the public interest where applicable; pursuing legitimate interests that are not overridden by an individual’s rights; or obtaining consent where consent is the appropriate basis.
Where we process sensitive information, including information about health, learning support, safeguarding, or wellbeing, we apply any additional condition required by applicable law.
Where consent is used, it may be withdrawn at any time. Withdrawal does not affect processing carried out lawfully before it was withdrawn.
Voyager is designed for middle- and high-school education and therefore deliberately handles information about children. We seek parent or guardian involvement and consent where applicable law or the enrolment relationship requires it, while recognising any rights a learner can exercise directly because of age or capacity.
Sensitive information may include health, disability, special learning difference, wellbeing, safeguarding, financial-aid or other protected information. We limit collection to what is relevant, apply tighter permissions and use it only on a suitable legal basis. Users should not place unnecessary sensitive information in general channels, direct messages, free-text fields or public portfolios.
Voyager schedules live sessions and may connect to Zoom and Google Calendar. We may receive meeting identifiers, participant names, email addresses and join/leave events to operate sessions and calculate attendance. If a session will be recorded or transcribed, the organiser must give any notice or obtain any consent required by local law and School policy. Recording settings and access should be restricted to approved educational purposes.
Announcements, channel posts and direct messages may be stored and may be reviewed by authorised personnel for education, administration, moderation, safeguarding, support, security, legal compliance or investigation of reported concerns. Users should report urgent safeguarding matters through the School’s designated safeguarding route, not rely only on Voyager messaging.
A public Voyager portfolio can be reached through a shareable link when publication is enabled. The current public endpoint can return the learner’s full name, programme, grade level, avatar, cohort name and selected published portfolio content. It does not currently return the learner’s email address. Public content can be copied, indexed or reshared by others, so the School should use separate, informed publication permission and avoid unnecessary personal or sensitive details.
Some profile images and announcement-board attachments are stored in public storage locations to make authorised app functions work. Users and staff must not upload confidential evidence, identity documents, safeguarding material, health records or other sensitive content to a public-facing field or general announcement attachment. Voyager uses separate private storage for absence evidence, special learning-difference documents and concern evidence.
Scope and status. This register identifies third-party services Voyager is configured to use in connection with School of Humanity workflows as of September 1 2026. Actual production use varies by enabled workflow. Inactive legacy integrations are excluded. Former providers remain documented in the School’s internal vendor and retention records until data deletion, account closure, and any required retention obligations have been confirmed.
| Provider | Voyager use | Information involved | Location / transfer note | Official record |
|---|---|---|---|---|
| Supabase Pte. Ltd. | Core hosted database, authentication, file storage, realtime events, server-side functions, and scheduled processing. | Most Voyager account, learning, communications, admissions, and operational records. Voyager account credentials are handled through Supabase Auth. | Primary project data is stored in the configured Supabase project region. Supporting services and subprocessors may process data internationally; applicable transfer terms are set out in Supabase’s DPA. | Supabase DPA |
| Zoom Communications, Inc. | Live sessions, meeting scheduling, participant/attendance events, and recordings or transcripts where enabled. | Names, email addresses, meeting IDs, session metadata, join/leave events, and audio, video, chat, shared content, recordings, or transcripts where those features are enabled. | Processing and storage depend on the School’s Zoom account configuration and Zoom’s published infrastructure and subprocessors. | Zoom subprocessors |
| Google LLC / Google Workspace | Gmail delivery and history; Google Calendar invitations; and Google Drive storage and sharing for reports, transcripts, enrolment letters, and related school documents. | Identity and contact details, calendar data, email content, and educational documents used in the relevant workflow. | Processing is subject to the School’s Workspace configuration, agreement, and applicable Google data-processing terms. | Google Workspace subprocessors |
| Plus Five Five, Inc. (Resend) | Transactional, onboarding, reminder, report, mentor, and other school email delivery. | Recipient names and email addresses, message content, and email-delivery metadata. | The current public subprocessor list identifies its listed providers as US-based. Resend’s DPA contains its applicable transfer terms. | Resend subprocessors |
| Slack Technologies, LLC / Salesforce | School operational notifications, channel synchronisation, and staff-onboarding workflows. | Names, email addresses, Slack IDs, channel or membership information, and notification or workflow content sent to Slack. | By default, Slack stores data in the US. Eligible customers may select a data-residency region for specified data at rest; some data may still be processed or stored outside that region. | Slack data residency |
| Restly, Inc. (Fillout, by Zite) | Admissions and other form-submission retrieval and webhook processing, where enabled. | Form responses, identifiers, contact and application data, and uploads included in configured forms. | Fillout offers US hosting and EU submission hosting for eligible customers. The actual hosting choice must be verified in the School’s Fillout account. | Fillout subprocessors |
| Formagrid Inc. (Airtable) | Admissions, application, and financial-aid import or source workflows, where enabled. | Applicant and contact details, application data, financial-aid records, and supporting material held in configured bases. | US hosting applies by default. European or Australian data residency is available only where purchased and configured; verify the School’s actual account setting. | Airtable subprocessors |
| Calendly LLC | Admissions call or interview scheduling and booking webhooks, where enabled. | Names, email addresses, booking and event metadata, and answers supplied during scheduling. | Calendly and its subprocessors may process data internationally under the applicable agreement and DPA. | Calendly subprocessors |
| browserless.io, Inc. | Headless-browser PDF rendering for approved transcripts and enrolment letters. | HTML and document content sent for rendering, which may include identity, enrolment, and academic information. | Browserless states that customer data is primarily stored in the United States. Its privacy policy says it does not retain page/session content, but it processes limited session metrics for service quality and analytics. | Browserless privacy policy |
Voyager’s users and providers may be in different countries. Where information is transferred from a jurisdiction that restricts international transfers, we use an approved mechanism where required, such as an adequacy decision, Standard Contractual Clauses, the UK Addendum, an applicable Data Privacy Framework certification or another lawful safeguard. Provider location can also depend on the account region selected by School of Humanity. Contact us for information about the safeguard relevant to your data.
We retain personal information only for as long as necessary for the purposes described in this notice. The period depends on the type of record, the purpose for which it was collected, whether the person remains connected with the School, and applicable education, safeguarding, accreditation, contractual, tax, dispute-resolution, and legal requirements.
Some information, including core academic records and records needed to meet safeguarding or legal obligations, may need to be retained for longer than operational records such as recordings, working files, or routine communications. We do not retain recordings indefinitely as a matter of course.
When personal information is no longer required, we delete it, anonymise it, or archive it with restricted access, unless a legal hold or another overriding requirement applies. Information may remain in secure backups for a limited period after deletion from active systems.
We are developing a record-retention schedule that will set out the retention periods and review arrangements for the categories of information we hold. You may contact [email protected] if you have questions about the retention of your information.
We use role-based access, database row-level security, authenticated sessions, private storage for designated sensitive evidence, encryption provided by our hosting and communications providers, access controls for integration credentials, logging and operational review. We also expect users to protect credentials, use approved devices and channels, and report suspected compromise promptly. No system is risk-free; if a breach is likely to create legal notification duties, we will investigate and notify affected people and authorities as required.
Voyager automates routine administrative operations, including progress and credit calculations, attendance processing, scheduling, notifications, and report generation. These automated operations may support staff work, but authorised School staff remain responsible for material admissions, assessment, progression, safeguarding, and disciplinary decisions and can review and correct relevant records.
Voyager does not currently use artificial intelligence to process learner work, learner data, or other personal data in its live service. Voyager does not make decisions producing legal or similarly significant effects solely by automated means.
Voyager uses essential browser-storage and authentication technologies, including local storage and session storage, to sign users in, maintain sessions, secure the service, and remember essential settings. We do not currently use Voyager-wide advertising or non-essential analytics cookies.
Some Voyager pages may display third-party content or services selected for a learning or school workflow, such as embedded Fillout forms, videos, or other externally hosted resources. When that content is loaded, the relevant third party may set or access cookies or similar technologies under its own privacy and cookie practices.
If School of Humanity introduces non-essential analytics, advertising technologies, or new embedded services requiring consent, it will provide the notice and choices required by applicable law before those technologies are enabled.
Depending on applicable law, where you live, and your relationship with the School, you may have rights to request access to your personal information; correction of inaccurate information; erasure; restriction of processing; objection to certain processing; data portability; withdrawal of consent where processing relies on consent; and information about recipients, international transfers, or certain automated decision-making.
These rights are not absolute. Education, safeguarding, accreditation, legal, and record-keeping obligations may limit a request, including where information concerns another person or the School must retain a record.
To make a request or ask a question about your personal information, contact us at [email protected]. We may need to verify your identity and authority to make the request, including a parent or guardian’s relationship to a learner. A learner may be able to exercise rights directly depending on their age, capacity, and applicable law.
Where applicable, you may also complain to the data-protection authority responsible for the School or in the country or region where you live, work, or believe an infringement occurred.
We may update this notice when Voyager, our service providers, or legal requirements change. We will publish the current version and provide additional notice where a change materially affects people’s rights or expectations.
For questions, requests, or concerns about this notice or the School’s handling of personal information, contact:
Privacy enquiries
School of Humanity
Email: [email protected]
Postal address:
Humanity Education Ventures
7901 4th St N STE 300, St Petersburg Florida, 33702
Effective date: September 1, 2026
Version: 1.0
Supabase DPA: Open official source
Zoom subprocessors: Open official source
Google Workspace subprocessors: Open official source
Resend DPA: Open official source
Resend subprocessors: Open official source