Privacy Policy
GoBak LLC · Last updated: 23/10/2026
Introduction
GoBak LLC (the “Company”) provides Nido, a product of Volantis. This Privacy Policy (the “Policy”) outlines how the Company collects, uses, stores, protects and processes Personal Data provided by its customers and its users (the “Customer”), or by the Company itself, for the performance of Nido (the “Services”).
GoBak LLC is an incorporated company registered in Delaware with file number 3074194, whose address is at 16192 Coastal Hwy, Lewes, Sussex, Delaware, DE 19958. Any queries in relation to this Policy should be addressed to the Data Protection Officer at the above address, by emailing support@volantisedu.com, or through the Support page on Nido.
Data Controller and Data Processor
This Policy applies to all Personal Data collected, used, stored, protected, processed or otherwise handled by the Company, whether it acts as a Data Controller or as a Data Processor on behalf of the Customer, which acts as a controller, within the scope of the Services.
The Company has appointed a Data Protection Officer (“DPO”) who is responsible for overseeing questions in relation to this Privacy Policy. If the Customer has any questions about this Privacy Policy, or wishes to obtain further information regarding the processing of Personal Data, the Customer may contact the DPO at support@volantisedu.com.
The types of Personal Data handled by the Company
Personal Data means any information about an individual from which that person can be identified.
The Company may collect, use, store, transfer and process different kinds of Personal Data which the Company has grouped together as follows:
- Identity Data includes first name, last name, aliases or similar identifiers, and, for Students, date of birth where the Customer provides it.
- Contact Data includes email address.
- Profile Media includes photographs of Teachers and Students.
- Evidence Data includes written evidence, images, videos, audio recordings, and related classroom documentation.
- Usage Data includes sign-in and device session records, locale preference, technical logs needed to operate the Services, and pseudonymous product-usage analytics identifiers and event metadata when the optional analytics configuration is complete.
The Company also collects, uses and shares aggregated data such as statistical or demographic data which is not Personal Data as it does not directly or indirectly reveal any identity.
How the Personal Data is collected
The Company collects Personal Data, either directly or received from the Customer. Both the Company and the Customer are responsible for ensuring that such Personal Data has been lawfully obtained and that all necessary notices and consents have been provided to the Data Subjects.
Where the Company is required to collect Personal Data by law, or in connection with the provision of the Services to the Customer, and the Customer fails to provide such data when requested, the Company may be unable to provide the Services. In such cases, the Company may need to cancel the Services provided to the Customer, but will notify the Customer if this occurs.
How the Personal Data is used
Data Use — The Company uses Personal Data solely to provide and improve its Services, perform analytics, and support the Customer’s operational needs. Personal Data is not used for marketing purposes or shared with third parties except as necessary to deliver the Services or comply with legal obligations.
Research — Personal Data may be pseudonymised and analysed by Company research staff to improve the Services and to study teaching and learning, as described in “Research”.
Data Processing — Personal Data is processed in accordance with General Data Protection Regulation (the “GDPR”) principles and only for the duration necessary to fulfil the purposes outlined in this Policy.
Data Storage — Personal Data is stored in Neon Postgres and Vercel Blob. The application and background work run on Vercel. These providers operate in the United States unless a transfer safeguard applies. Access to Personal Data is limited to authorised personnel only.
When determining the appropriate retention period, the Company considers the amount, nature, and sensitivity of the Personal Data, the potential risk of harm from unauthorised use or disclosure, the purposes for which the Personal Data is processed and whether those purposes can be achieved by other means, and any applicable legal, regulatory, tax, accounting, or other requirements.
Website analytics and privacy choices
If you choose to accept, Nido uses Vercel Web Analytics on the public Privacy, Terms, Support and Changelog pages only. It is cookieless and does not create an account-level profile or use analytics cookies.
The integration is loaded only after you accept analytics. It sends the public page path without query strings and is never loaded on sign-in, password recovery, authenticated workspace, token, MCP, or API routes. The authenticated workspace does not load Vercel Web Analytics. Declining means Nido sends no website analytics requests.
Your accept or decline choice is stored locally in this browser so it persists. Use the Privacy choices control on a public page to change it at any time.
Authenticated product-usage analytics
For authenticated, activated teachers, the Company may conditionally use PostHog as a processor and product-usage analytics recipient. The thirteen categorical version-seven product events are server-delivered. Each server-delivered event attaches the acting staff member’s email address to that staff member’s analytics profile, together with the school’s display name, so that the Company can tell which staff member and school the usage belongs to. If teacher replay is enabled, a local 10% sample of activated teacher workspace sessions may be recorded for product-use analysis. Events and replay are keyed by HMAC-derived staff and school/campus values plus session and release metadata; raw tenant, staff, and campus identifiers are not sent. Because the staff email address is attached to the same HMAC-derived staff value, PostHog can associate a sampled replay with that email address; the email address itself is never placed in the replay recording or sent from the browser.
The version-seven catalog keeps the original five events and adds eight, using only closed properties: workspace surface viewed (surface: home, evidence, students, reading, experiences, school, account—including profile—and snapshots, ask_nido, or essential_skills; navigation_kind: entry or cross_surface; previous_surface: another closed surface or null; view_kind: index or detail); evidence created (capture_method: text, audio_transcript, or image_agent; has_students, has_media, and has_experience booleans; student_scope: none, individual, group, or voice_confirmed; media_kind: none, image, video, other, or mixed; attachment_count_bucket: none, one, or two_plus; visual_anchor_kind: none, person, artifact, or mixed; initial_status: enriching or ready); ask nido turn settled (outcome: completed, failed, or aborted; class_scope: default, all, or class; period_selection: default, twoWeeks, academicYear, or custom; is_regeneration boolean; insights_available boolean; latency_bucket: under_5s, 5_to_15s, 15_to_30s, or 30s_plus; citation_integrity: clean, repaired, or none); experience session scheduled (duration_bucket: under_30m, 30_to_60m, 61_to_120m, or over_120m; lead_time_bucket: past_or_now, within_24h, 24h_to_7d, or later; has_special_activity_note boolean); and portrait authority submitted (intent: reinforce or challenge; mode: authority_only or observed_episode; has_review_conversation boolean; portrait_work_outcome and timeline_work_outcome: enqueued, already_active, or marked_dirty). Every provider payload also carries event_schema_version 7, environment, and scope_access (campus or institution). These values are closed enums, booleans, or coarse buckets.
The catalog adds categorical generated-output feedback as product feedback submitted (artifact: ask_nido, experience_plan, portrait_section, quality_question, class_overview, or learner_reading; sentiment: positive or negative; reason: faithful, useful_insight, too_generic, unsupported, missing_context, useful_question, already_answered, unclear, irrelevant, too_many, helpful, not_helpful, or unspecified; has_comment boolean), plus workflow started (workflow: evidence, ask_nido, experience, or portrait; stage: capture, turn, schedule, or authority) and workflow refused (the same workflow and stage plus refusal_class: permission_denied, invalid_input, not_found, state_conflict, prerequisite_incomplete, empty_input, time_conflict, or temporarily_unavailable). Feedback reasons are refined by artifact and sentiment. Existing generated-output comments remain in Nido; only has_comment crosses into analytics. Analytics-only feedback controls and their endpoint are available only when configuration is ready.
Recaps adds five events: recap template created (source: ask; window_kind: term, this_term, since_year_start, or last_days; language: en or es); recap class run started (source: ask or recaps_page; child_count_bucket: one, 2_to_9, 10_to_24, or 25_plus); recap edited, once per recap the first time it is copied or printed with a teacher edit (edit_size_bucket: small, medium, or rewrite); recap copied or printed (scope: one or run; kind: copy or print); and recap template run again (different_class and later_window booleans, comparing the run with the template’s previous run). edit_size_bucket is worked out on the server from the share of words that differ between Nido’s original and the teacher’s text; neither text, the template, its instructions, the children, the class, the dates, or any recap or run identifier is sent.
Server event properties exclude raw counts, exact dates, times, time zones, MIME values, provider finish reasons, raw IDs, personal names, learner identity, evidence or other content, model prompts or outputs, domain URLs, receipt IDs, raw refusal codes, provider messages, and comment text. citation_integrity records only whether the citations in a stored Ask Nido answer all pointed at evidence Nido retrieved in that conversation (clean), some were removed before storage because they did not (repaired), or the turn left no answer text to check (none); the citations themselves, how many were removed, and any identifiers in the answer are not sent. The only identifying values are the acting staff member’s own email address and the approved client/school display name, both read server-side under tenant scope; neither is sent to replay. Workflow starts count authenticated attempts; Ask stream failures remain settled through ask nido turn settled after persistence rather than becoming workflow refusals. Replay metadata can include its validated session ID, release and environment values, timestamps, layout numbers, and categorical route placeholders; it does not capture classroom content or learner identity. The resulting aggregate signals support product-use insights without exposing classroom content.
When replay is sampled, only fixed navigation, panel, and action labels from a closed English/Spanish list may remain readable. All inputs and private or classroom text are masked. Personal names, media, arbitrary private attributes and styles, network details, and console output are excluded. These replay labels do not change the live UI. Replay is memory-only, creates no analytics cookie, and respects DNT. PostHog project IP capture is discarded and SDK GeoIP processing is disabled. The replay retention is 30 days. These controls describe the processing contract.
Server event delivery is scheduled after the response as bounded best effort, with no retries and a 1.5-second timeout; browser replay transport is optional and does not block domain actions. Analytics is optional: when POSTHOG_PROJECT_TOKEN, POSTHOG_HOST, and POSTHOG_ANALYTICS_SECRET are all absent it is disabled; incomplete or invalid configuration is `invalid` and refuses delivery, including an analytics secret shorter than 32 characters. Analytics failures never change domain commands or receipts. This processing is separate from the consented public Vercel Web Analytics described above.
Purpose for which the Company will use your Personal Data
Personal Data is collected and processed to facilitate the provision of the Services, including evidence capture, generated readings, reporting, and operational views, on the following legal bases:
- Performance to contract: To provide the Services requested by the customers.
- Legitimate interest: For analytics and service improvement, and research using pseudonymised data with the safeguards in Article 89 GDPR, balanced against data subjects’ rights.
- Legal obligation: To comply with applicable laws and regulations.
Research
Company research staff may study pseudonymised data from the Services to improve Nido and to understand teaching and learning. Before any data is used for research, Students, Teachers and classes are replaced with random tokens; names, nicknames, email addresses, school identification numbers and dates of birth are removed (age is kept only in whole months); photographs, audio and video are never included; and names and other identifying details are redacted from evidence text. Evidence flagged by the safety check are excluded.
The link between tokens and real people stays within the production Services and is never part of a research dataset. Research datasets are available only to Company staff bound by confidentiality, are deleted from the Services within 7 days of being produced, and every request and download is logged. The Company does not sell research datasets, share them with third parties, use them to make decisions about individual people, or attempt to re-identify anyone. Results leave the Company only in aggregated form from which no individual can be identified.
Pseudonymised data remains Personal Data, and Data Subjects keep the rights described in this Policy.
Data Security
The Company implements commercially reasonable technical and organisational security measures, including encryption and access controls, to protect Personal Data from unauthorised access, disclosure, alteration, or accidental loss.
Access to Personal Data is limited to employees, agents, contractors, and other third parties who have a legitimate business need to know. Such individuals or entities are permitted to process Personal Data only under the Company’s instructions and are bound by confidentiality obligations.
Data Subject Rights
The Company recognises that the Customer and its authorised users whose Personal Data is collected and processed (the “Data Subjects”) have specific rights under applicable data protection laws. These rights are designed to give Data Subjects control over their Personal Data and to ensure that it is processed fairly, lawfully, and transparently.
Data Subjects have the right to:
- Access their Personal Data and obtain information about how it is processed and with whom it is shared.
- Rectify any inaccurate or incomplete Personal Data.
- Erase their Personal Data, where applicable, including exercising the “right to be forgotten”.
- Restrict the processing of their Personal Data in certain circumstances.
- Object at any time to the processing of their Personal Data for direct marketing purposes (including profiling), and in other situations to the continued processing of their Personal Data where it is based on our legitimate interests, unless we demonstrate compelling legitimate grounds for the processing or the processing is required for the establishment, exercise, or defence of legal claims.
- Receive their Personal Data in a structured, commonly used, and machine-readable format, and transmit that data to another controller (data portability).
- Not be subject to a decision based solely on automated processing (including profiling) that produces legal effects concerning them or similarly significantly affects them.
- Withdraw consent at any time. Withdrawal does not affect the lawfulness of processing carried out before the consent was withdrawn.
To exercise any of these rights, Data Subjects may contact the Company or its DPO using the methods outlined in this Privacy Policy.
Data Transfers
The Company may transfer and process Personal Data in countries outside the European Union (“EU”) and the European Economic Area (“EEA”) whose laws provide an equivalent level of protection to EU or United Kingdom (“UK”) data protection law.
In such cases, the Company ensures that a comparable degree of protection is maintained. This is achieved by implementing safeguards, including the use of Standard Contractual Clauses approved for use in the UK, such as the International Data Transfer Agreement or International Data Transfer Addendum to the European Commission’s Standard Contractual Clauses for international data transfers.
Data Breaches
In the event of a Personal Data Breach likely to result in a risk to individuals’ rights and freedoms, the Company will notify the Information Commissioner’s Office (ICO) within 72 hours of becoming aware of the breach. The Company will also notify affected Data Subjects without undue delay where the breach is likely to result in a high risk to their rights and freedoms.
Disclosure of the Personal Data
The Company will share Personal Data with third parties only as described in this Privacy Policy. The Company does not sell Personal Data to third parties.
The Company may disclose Personal Data to third parties in the following circumstances:
- In the event that the Company sells or acquires any business or assets, Personal Data may be disclosed to the prospective seller or buyer to the extent necessary for the transaction and with the Customer’s prior consent.
- If all of the Company’s assets are acquired by a third party, in which case Personal Data held by the Company about its Customer will be among the transferred assets.
- If the Company is under a duty to disclose or share Personal Data in order to comply with any legal obligation, or to protect the rights, property, or safety of the Company, the Customer, or others.
Processors
The Company uses the following processors to provide Nido. They process Personal Data only on the Company’s instructions and under appropriate contractual safeguards:
- Vercel, which hosts the application, stores files in Vercel Blob, and runs background processing.
- Neon, which hosts the tenant Postgres database.
- Vercel AI Gateway, which routes model requests to downstream model providers.
- Downstream model providers, such as OpenAI and Google Vertex AI, which host configured models and process authorised evidence to produce Generated Readings.
- Resend, which delivers account emails such as invitations and password resets.
- PostHog, conditionally and only when the server-side product-analytics configuration is complete, which receives the product-usage analytics described above, including the staff email address and school display name, on the Company’s instructions.
Third-party sharing
We will only disclose your Personal Data: (i) to successors in title to our business; (ii) to suppliers and external agencies we engage to process data on our behalf; (iii) to necessary third parties in order to meet the purpose of our use of such Personal Data (such as our auditors and other professional advisors); and (iv) where disclosure is required by law or by any regulatory authority.
Third-party links
Our website may include links to third-party websites, plug-ins, and applications. Clicking on those links or enabling those connections may allow third parties to collect or share data about the Customer. The Company does not control these third-party websites and is not responsible for their privacy statements or practices.
Data Retention
The Company will retain Personal Data only for as long as reasonably necessary to fulfil the purposes for which it was collected, including to satisfy any legal, regulatory, tax, accounting, or reporting requirements. Personal Data may be retained for a longer period in the event of a complaint or if the Company reasonably believes there is a prospect of litigation in relation to its relationship with the Customer.
Contact Information
If the Customer has any questions regarding this Privacy Policy, the use of Personal Data, or wishes to exercise their privacy rights, they should contact the Company’s DPO or the Company using the following methods:
- Email: support@volantisedu.com
- Postal: 16192 Coastal Hwy, Lewes, Sussex, Delaware, DE 19958, US
Changes to the Privacy Policy
The Company keeps its Privacy Policy under regular review. This version was last updated on 23/10/2026.
It is important that the Personal Data held by the Company must be accurate and current. Please keep the Company informed if the Personal Data changes during your relationship with the Company.