Privacy

SeeUAll is operated from Montréal, Québec, Canada. It is sold to organisations — companies, universities, colleges and schools — and used by the people who work or study in them.

That relationship shapes everything below. Your organisation decides which meetings exist, who may attend them, whether they are recorded, and how long records are kept. We act on those instructions and do not make those decisions independently. In the language of privacy law, the organisation is the controller of that information and we process it on their behalf, under a written agreement with them.

If you are a participant or a member of staff and you want something changed or removed, your institution is the right first stop — they can act immediately, and we will support whatever they ask for. If they cannot help you, write to us at privacy@seeuall.com and we will.

Account and roster information. Names, organisational email addresses, role (participant, host, administrator), meeting membership and, where your organisation uses our scheduling integration, timetable data. This is supplied by your organisation’s systems. Nobody creates an account here by themselves.

Live meeting audio and video. Carried through our own media server so that participants can see and hear each other. It is not written to disk unless a recording is running. When no one is recording, the audio and video of a meeting exist only for as long as it takes to deliver them.

Recordings, when a meeting is recorded. See §4 — they are stored in your organisation’s Google Drive, not ours.

Live captions and transcripts. Captions are produced on our own servers (see §5) and disappear as the meeting moves on. A written transcript is kept only when the person hosting has turned that on for that meeting.

Things typed and drawn in the meeting — chat messages, whiteboard content, annotations on a shared screen, hands raised, poll and quiz answers where those are used.

Attendance. When somebody joined and left a meeting. Where your organisation has connected its learning platform, that record is sent back to it — which is usually the point of the integration.

Technical records. Sign-in events, the browser or app version, device and network diagnostics used to work out why a call sounded bad, and an audit log of moderation actions — who muted whom, who removed whom, who started a recording, who was given control of a screen. These exist so that a consequential action in a meeting can be accounted for afterwards.

Background effects. If you blur or replace your background, that processing happens inside your own browser, on your own machine. The video we receive is the one you chose to send. No image of you is analysed on our servers to do it.

The application, the database and the media server all run on machines in Montréal, Québec, Canada. Meeting media is not routed through another country to get between two people in the same room.

Each organisation’s data is separated at the database level, not merely by a filter in application code: queries run under a role that is only permitted to see the organisation they are scoped to. Traffic between you and the service is encrypted in transit.

When a meeting is recorded, the finished file is uploaded to a Google Drive account that your organisation connects and controls. We keep a reference to it — enough to list it, show who may watch it, and hand out a link — but the file itself is theirs, in their account, subject to their retention rules.

The permission we ask Google for is drive.file, the narrowest one available: it grants access only to files this application itself created. SeeUAll cannot see, list, open or delete anything else in that Drive, and that is enforced by Google rather than promised by us.

A recording is never silent. Everybody in the room sees an indicator for as long as one is running, and where a meeting is set to record itself, that is said in the lobby before anybody joins.

A short list, and it is short deliberately. There is no advertising network, no analytics broker, and no data sold to anybody, ever.

Google Drive — only where your organisation has connected it, and only for recordings, under the narrow permission described in §4.

Live captions are not sent anywhere. Speech is transcribed by software running on our own servers in Montréal, Québec, Canada. This is unusual and it is deliberate: the alternative is streaming every word spoken in a meeting to a third-party speech service.

AI features are opt-in and narrow. Where a meeting keeps a transcript, an institution may also turn on written recaps or an in-meeting assistant. Those features send transcript text to an AI provider to produce the summary or the answer. If a meeting has no transcript, nothing is sent — there is nothing to send. Providers are used under terms that do not permit them to train models on this material.

Email and notifications. Invitations and reminders are sent through the mail provider your organisation configures — commonly their own Google Workspace or Microsoft 365 — so those messages come from them. Browser push notifications, if you enable them, pass through your browser vendor’s notification service, which is how push works on every website.

Our hosting provider operates the physical machines. They have no access to the contents of the service in the ordinary course.

Sharing a screen shows the people in the meeting whatever you have chosen to share. Choose a single window rather than a whole screen if the rest of your desktop is private.

Take control goes further, and is worth reading twice. Using our desktop app, you may allow another participant to move your pointer and type on your computer. It only happens when you are asked and you agree; it is confined to the screen or window you are already sharing; a red strip stays on top of everything naming the person driving; and it ends the moment you press the shortcut on that strip, stop sharing, or leave.

We do not record what is typed or clicked during such a session. What we do record is that it happened: who was given control, by whom, and when. Whoever you hand control to can see and do whatever your computer lets them, so hand it to people you trust, and end it when you are done.

Account and roster records last as long as your organisation keeps you on the roster. Attendance and audit records are kept for as long as the organisation’s own policy requires, because they exist to answer questions about a meeting months later.

Recordings are kept in your organisation’s Drive until your organisation deletes them. Chat, whiteboard content and transcripts belong to the meeting and are removed with it.

When an organisation ends its agreement with us, its data is deleted from our systems on the schedule set out in that agreement. Backups age out on their own cycle, after which nothing remains.

Depending on where you live, you may have the right to ask what information is held about you, to have it corrected, to have it deleted, to withdraw a consent you gave, and to complain to a regulator. In Canada that includes federal privacy law and the privacy law of your province; people in other countries may have equivalent rights.

Because your institution decides what is kept, requests are quickest through them. If you would rather ask us, write to privacy@seeuall.com. We will confirm your request, forward it to the organisation where the decision is properly theirs, and answer within the time the law allows.

Where the service is used in a school, accounts are created by the school for its pupils and the school is responsible for the consents that requires under the law that applies to it. We do not create accounts for children directly, we do not advertise to anybody, and we do not build profiles of participants for any purpose other than running the room and reporting attendance to the school.

When this document changes in substance, the date at the top changes with it and organisations are told in advance. Corrections to wording that do not change meaning are made without notice. Previous versions are available on request.

SeeUAll, Montréal, Québec, Canada. Privacy enquiries: privacy@seeuall.com. Everything else: hello@seeuall.com.

The terms of service set out the rules for using SeeUAll, including what we are and are not responsible for.