WingsuitSign in

Safeguarding statement

Last updated 20 September 2026

Wingsuit is a whiteboard for teachers. Students never hold an account and never put anything into it; they open a link and watch. This page sets out exactly what that means, in the terms a designated safeguarding lead will expect, so that a school can assess Wingsuit without having to take anything on trust.

Wingsuit is not a filtering or monitoring system and does not replace one. Statutory responsibility for safeguarding and promoting the welfare of children rests with the school or college, under Keeping children safe in education.

Purpose and scope

This statement covers the Wingsuit website at usewingsuit.co.uk and the Wingsuit app for iOS, iPadOS and Android. It is written for designated safeguarding leads, online safety leads and IT staff carrying out due diligence on a supplier.

It describes the product as it is built, not as it is intended. Every claim on this page is one that can be checked in Wingsuit’s own code, and the page is changed when the code changes. Data protection is dealt with separately in the privacy policy and the data processing agreement.

How students meet Wingsuit

A teacher shares a board in one of three ways: a view-only link, a persistent room link posted somewhere like Google Classroom, or a temporary session. In every case the student opens the link and sees the board. That is the whole of the student experience.

  • Students do not have accounts. There is no sign-up, no sign-in and no student login of any kind.
  • Students are not asked for a name, an email address, a school or anything else. Nothing identifies them.
  • A viewer is an anonymous connection held in the server’s memory and counted, so the teacher can see how many people are watching. Nothing about a viewer is written to the database.
  • There are no student profiles, no accounts to manage and therefore nothing to delete afterwards.

Hosting infrastructure necessarily sees a viewer’s IP address in transit, as it does for any website. Wingsuit does not record it.

Data protection and the Children’s code

Safeguarding and data protection overlap here, so it is worth being precise about what Wingsuit knows about a student: nothing. There are no student accounts and nothing about a viewer is stored. There is no chat, no comments, no messaging and no way for a student to send anything to a teacher through Wingsuit, so the product offers no channel through which a student could be contacted, or could disclose. Disclosures remain a matter for the school’s own procedures.

Wingsuit designs to the ICO’s Children’s code (the Age Appropriate Design Code) and to the children’s protection duty in Article 25 of the UK GDPR, in force since 5 February 2026. It does not claim the ICO’s exemption for edtech supplied only on a school’s instructions: teachers can sign up directly here or in the App Store, so the code is treated as applying. It is met by collecting nothing from students: no student accounts, no profiling, no advertising, no location data, no nudges towards sharing more, and sharing that is off until a teacher turns it on. That assessment is written down and reviewed when the product changes.

The one place student personal data can appear is on a board, put there by a teacher. A view-only link is unlisted but not secret: anyone holding it can watch until sharing is turned off.

Online safety: the four Cs

Keeping children safe in education groups online risk into content, contact, conduct and commerce. Each is addressed below as it applies to Wingsuit.

Content

The only thing a student can see in Wingsuit is the board their teacher is showing them, at the moment they are showing it. Wingsuit has no public gallery, no browse or discovery surface and no search across boards: there is no route in the product by which anyone can reach another person’s board, and nothing is public unless its owner has shared it. A board can only be opened with the unguessable link the teacher chose to give out.

Wingsuit publishes no content of its own onto a board and shows no third-party content, no recommendations and no embedded media from elsewhere. What is on the board is what the teacher put there.

Contact

Wingsuit has no chat, no messaging, no comments, no reactions and no forum. There is no mechanism anywhere in the product by which one viewer can reach another, by which a viewer can reach the teacher, or by which anyone, including Wingsuit itself, can contact a student through the service. Viewers cannot see each other and are not shown to each other; the teacher sees a count and nothing more.

The support system, through which a user can message Wingsuit, is available only to signed-in teachers. It is not reachable from a share, room or session link.

Conduct

Students cannot write, draw, upload, edit or delete anything. Viewing is read-only and that is enforced by the server, not just hidden in the interface: a viewer’s connection may send only a keep-alive, and anything else closes it. A viewer connection is additionally treated as having no user attached, so no change arriving on it could be applied to the board even if one were sent.

Because students produce nothing, there is no student-generated content to moderate, and no peer-to-peer surface on which bullying or harassment could take place within Wingsuit.

Commerce

Wingsuit carries no advertising anywhere, and no analytics, tracking or profiling of any kind. The student view contains no marketing, no upgrade prompts and no way to buy anything: subscriptions exist only inside a signed-in teacher’s account. Nothing a student sees is commercial.

Filtering and monitoring

Wingsuit is not a filtering or monitoring provider, and it does not filter or monitor what a teacher draws or uploads. No system scans, classifies or moderates board content automatically. A school’s own filtering and monitoring systems remain entirely in place and are unaffected by Wingsuit; they should be managed and reviewed as the filtering and monitoring standards for schools and colleges require.

For a network allow-list, Wingsuit needs one domain:

  • usewingsuit.co.uk, including its subdomains, for the site, the app and the live board connection.

All traffic is encrypted: pages and files over HTTPS, live board updates over WSS on the same origin. Wingsuit opens no other connections from a student’s device: no content delivery network, no third-party fonts or scripts, and no analytics.

What teachers are responsible for

Wingsuit gives a teacher a blank board and a link. Everything that follows is the teacher’s professional judgement, exercised under their institution’s policies and their designated safeguarding lead’s direction.

  • What goes on the board. A board can show anything a teacher draws, types, photographs or imports, including personal data about students if they put it there. Wingsuit does not need student personal data and asks that it not be placed on a board unless the school’s policies allow it.
  • Who gets the link. Anyone holding a share or room link can open it while it is active, so links should be posted where only the intended class can see them.
  • Checking what is visible before broadcasting, exactly as with a projector. Anything on the board is on the board.
  • Reporting anything of concern about a child to their designated safeguarding lead, in line with the school’s child protection policy.

One thing is handled for the teacher: when a PowerPoint file is imported, its speaker notes are stored separately from the board and are never sent to viewers. Students see the slides and nothing more. The notes can only be read back by the signed-in account that owns them.

  • A broadcast to a room lapses automatically at the next midnight, UK time. After that the room link shows nothing until the teacher broadcasts again, so a link posted in Google Classroom cannot quietly keep showing a board the next day.
  • Turning off sharing takes effect immediately. Existing viewers’ connections are closed at once, not at the end of a session.
  • Deleting a board turns its sharing off and disconnects viewers at the same moment.
  • Temporary whiteboard sessions expire eight hours after their last change.

Revoking a link stops access through it. It cannot remove a copy or screenshot somebody already took, any more than it could for a projected slide.

Staff

Wingsuit is operated by A2x Development Ltd, which has one director, Alex Colville, and no other staff. The director of A2x Development Ltd, the only person with administrative access to Wingsuit, holds an enhanced DBS check.

Nobody at Wingsuit has any contact with students through the service. There is no mechanism for it, as set out above. Administrative access to accounts is limited to Alex Colville, and sensitive administrative actions, including signing in as another user for support, are recorded in an audit log.

Reporting a concern

To report something about Wingsuit itself (content on a board that should not be there, a link that is being misused, or an account being used improperly), email support@usewingsuit.co.uk. Reports are acted on: sharing can be revoked and an account can be suspended.

A concern about a child is not for Wingsuit to handle. Report it to the designated safeguarding lead at the school or college concerned, following their child protection procedures. If a child is in immediate danger, call 999.

Review

This statement is reviewed at least annually, and sooner if Wingsuit changes in a way that affects anything on it. It was last reviewed on 19 September 2026; the next review is due in September 2027. See also the accessibility statement and the rest of the compliance documents.