Effective 1 July 2026
Privacy notice
Written to be read once, by a person who has a meeting in ten minutes. Live audio and video are relayed, not stored. Nothing here is sold, and no recording, transcript or caption trains anything of ours.
Version 4
In force since 1 July 2026. Nothing in this version widened what we collect.
Where your data sits — and whose law applies
Where the bytes are
Your organisation picks one when it signs up. Recordings, transcripts, chat and files are stored only in that region, and live media is relayed through it. Moving region moves everything, and takes a scheduled window.
Whose law applies
We are PT Sapa Team Teknologi, a perseroan terbatas.
Awaiting sign-off
Operating entity and governing-law sentence pending confirmation from the company. Held here deliberately rather than drafted — this paragraph is the one thing on the page we cannot write ourselves.
Choosing a region is a promise about where the bytes sit. It is not a promise about which country’s law governs this notice or your contract — those are two different questions, and a region badge answers only the first. The governing law, and the company you are contracting with, are named here so the two are never read as one.
Everything we hold
| What | Why we have it | How long |
|---|---|---|
| Your accountName, email, provider | To sign you in and show other people who is in the room | While the account exists, then 30 days |
| Live audio and videoThe meeting itself | To pass it to the other people in the meeting | Not stored — relayed and gone |
| Recordings, transcripts, captionsOnly when a host records | Because someone in the meeting started a recording and everyone was told | Set by the organisation that made it — not by us |
| Your answer to a consent requestYes, and no | A consent that leaves no record is not a consent. A refusal is recorded for the same reason | As long as the recording it belongs to |
| Chat and shared filesIncluding snapshots to chat | To deliver them to the meeting and to the people who missed it | With the meeting; deleted with it |
| Connection and device diagnosticsNo media, ever | To tell you why a call was bad, and to answer you when you write to Support | 30 days, then counted and dropped |
| Where you are signed inDevices and sessions | So you can see a shared machine you forgot, and end it from anywhere | 90 days after the session ends |
Joining as a guest holds the first, fifth and sixth rows only, and drops the name you typed when the meeting ends. Nothing in this table is sold, and nothing in it trains a model of ours.
What you can ask for
A copy of everything in the table above, a correction to any of it, deletion of your account, and an end to every session it has open. Ask from Settings if you have an account, or by writing to us if you do not — a guest can ask, and we will answer.
Thirty days to answer, where the GDPR applies to your data. One thing is not ours to delete, and section 4 says which.
Where deletion stops
You can ask us for a copy of everything above, ask us to correct it, and ask us to delete your account. One thing you cannot ask us to delete is a recording of a meeting you were in: it belongs to the organisation whose host made it, the same way a photograph belongs to the person who took it. We will tell you who to ask, and we will pass the request on. We will not pretend the button is ours.
Who else touches it
A short list of sub-processors, each named with the single thing it touches and the region it runs in. It is the same list an assessor is given — kept in one place so the two can never disagree — and it is published rather than available on request.
Getting in touch
Ask us anything about this notice, or exercise any of the rights in section 3, without an account and without signing in. A person answers; where the GDPR applies to your data, the thirty days in section 3 is the outside limit, not the target.