Privacy Policy
Effective August 13, 2026
Logist Group, Inc. (“we”, “us”) operates Logist at logist.live. This policy explains what we collect, why, who else sees it, and what you can do about it.
Contact: support@logist.live
The short version
- We do not record your calls. Video and audio travel directly between you and the person you are matched with, encrypted end to end. They do not pass through our servers and we do not store them. Nobody at Logist can watch a call, live or later.
- The person you are matched with never sees your IP address. Calls go through a relay so neither of you learns the other’s. Section 4 is exact about what that does and does not hide.
- We keep your email, the display name you choose, and a record of what you answered and when you debated.
- Your real name is never shown to other users. Only the display name you choose.
- Most behavioural data is de-identified after 90 days.
- We do not sell your personal information.
1. What we collect
Information you give us
| What | Where it comes from |
|---|---|
| Email address | From your Google account, or typed in by you if you sign in with an email link |
| Account identifier | Your email address is the account. It is what recognises you on return and what makes a ban hold |
| Sign-in link records | Only if you sign in with an email link: a one-way hash of the link, the address it went to, when it was issued and used, and the IP address that asked for it |
| Display name | Chosen by you; shown to the people you debate |
| Age confirmation | The checkbox you tick before your first debate |
| Access code | If you join during an invite-only period |
| Report details | The category you pick and anything you write when you report someone |
| Debate ratings and feedback | The score out of five, and anything you write, when you answer the survey after a debate. The survey is optional and can always be skipped. Skipping records nothing at all |
There are two ways to sign in, and there is no password either way.
With Google, we receive your email address and an account identifier. We do not receive your Google password, and we do not display your Google profile name to other users.
With an email link, you give us the address and we send a link to it. Nothing is shared with us by anyone else. So that each link works exactly once, we store a one-way hash of it — never the link itself — with the address, the times it was issued and used, and the IP address that requested it. That last one is what lets us stop a single address being flooded with links by someone who does not own it.
Both routes reach the same account. Your account is your email address, so signing in the other way with the same address puts you back into the same account, with the same history and the same enforcement record. A different address is a different account.
Information generated by using the Service
| What | Why we have it |
|---|---|
| When you joined the queue, and how long you waited | To measure whether matching works |
| Who you were matched with, and when | Safety, and to avoid re-matching people after a report |
| Your Yes / No / Skip answers | To match you, and to work out which statements produce good debates |
| Which statement triggered a debate | The same |
| Whether the call connected, how, and for how long | To find and fix connection failures |
| Whether the debate was extended | To understand which debates people want to continue |
| How the session ended | Safety and diagnostics |
| Account status, and any warnings, suspensions, or bans, with the reason | To enforce our rules |
| When someone tells you that you changed their mind, and which statement you were debating | To show you your own count, and to work out which statements actually change minds |
Technical information
Standard server and network logs, including IP address, browser and device information, and timestamps. Our hosting and infrastructure providers process these on our behalf.
What we do not collect
- The content of your calls. No video, no audio, no transcripts.
- Screenshots or frames from your call. We do not currently capture any image from a call. If that ever changes, we will update this policy and tell you before it takes effect.
- Precise geolocation.
- Payment or financial information.
- Special-category data such as health, biometrics, or political opinions — except to the extent your answers to statements reveal an opinion, which we store as an answer to a statement and nothing more.
2. How we use it
- To run the Service: sign you in, put you in the queue, match you, and connect the call.
- To keep people safe: handle reports, apply and enforce warnings, suspensions and bans, and stop people we have removed from coming back.
- To understand and improve the product: which statements produce real debates, how long people wait, whether calls connect, whether people return, and how people rate their debates when they choose to tell us.
- To communicate with you about your account, a report, or a change to the Service.
- To comply with law, respond to lawful requests, and establish or defend legal claims.
We do not sell your personal information, and we do not use it for advertising. We do not use third-party analytics or advertising trackers. The analytics described here are our own and stay in our own database.
3. Legal bases (UK and EEA)
| Purpose | Basis |
|---|---|
| Providing the Service you asked for | Performance of a contract |
| Safety, moderation, and preventing abuse | Legitimate interests |
| Product analytics and improvement | Legitimate interests |
| Meeting legal obligations | Legal obligation |
| Anything else we ask you to agree to | Consent |
4. How video calls work, and what that means for your privacy
This section matters more than the rest, so it is written plainly.
When you and another person are put into a debate, your browsers connect directly to each other using WebRTC. Video and audio are encrypted in transit (DTLS-SRTP) and travel between the two of you. They never reach our servers, and we never store them.
Calls are routed through a relay so that neither of you learns the other’s IP address. Connecting two browsers directly — which is how WebRTC normally works, and how most browser video products work — requires each side to know the other’s address. An IP address can indicate an approximate region and an internet provider, which in a product that puts strangers on camera is a way to find somebody afterwards. So we send every call through a TURN server operated by Cloudflare instead. The person you are debating sees the relay’s address, never yours.
Relayed traffic stays encrypted end to end and is not readable by Cloudflare or by us. We record only that a relay was used, and how much data passed, for cost and reliability purposes.
To be exact about what this does and does not hide: Cloudflare, as the relay, handles the traffic and sees the network addresses of both participants. Our servers see your address when your browser connects to be matched, as any website does. What this prevents is the person you are matched with learning it, which is the one that can be used to find you.
Because we hold no recording, we cannot show anyone what happened in your call. That protects you, and it also limits what we can prove when you report someone.
5. Who else sees your information
We do not sell your data. We share it with service providers who process it on our behalf, under contract:
| Provider | What they process | Where |
|---|---|---|
| Sign-in, where we receive your email and an account identifier; and delivery of sign-in links to your inbox | US | |
| Vercel | Hosts the website; processes request logs | US |
| Fly.io | Runs the realtime matching server | US (Virginia) |
| Neon | Hosts our database | US (AWS us-east-1) |
| Cloudflare | Relays call traffic when a direct connection fails | Global |
Operator notifications. When someone files a report, a notification is sent to an internal messaging channel used by our team so a human sees it quickly. That notification contains display names and the reported reason. It does not contain call content, because none exists.
We may also disclose information when we believe in good faith that it is necessary to comply with law or a valid legal request, to enforce our Terms, to investigate suspected fraud or abuse, to protect the rights, property, or safety of any person, or in connection with a merger, acquisition, or sale of assets (in which case we will tell you).
Child safety. If we become aware of content involving the sexual exploitation of a minor, we will preserve the relevant records and report to the National Center for Missing & Exploited Children and to law enforcement as required by law.
6. How long we keep things
- Behavioural data — your answers to statements, queue activity, session records, and any debate ratings or feedback you gave — is de-identified after 90 days. The rows survive so we can still see how the product performs over time, but the link to you is removed and cannot be restored. A rating and its comment are kept; who wrote them is not.
- Your account — email, account identifier, display name, status — is kept while your account exists.
- Sign-in link records — the hash of a link, the address it was sent to, and the IP address that asked for it — are deleted a day after the link expires. Links expire fifteen minutes after they are issued.
- Minds changed — the count of people who have told you that you changed their mind is kept while your account exists, because it is a number we show you about yourself. Which debates you said it in is behavioural, and is de-identified after 90 days like everything else. Nobody but you ever sees your count, and you never see anybody else’s.
- Safety records — reports, moderation decisions, and the reasons for them — are kept for as long as we need them to enforce our rules and to keep a record of the decisions we have made, which is longer than 90 days. If we deleted them on schedule, a banned person could return by waiting.
- Administrative access logs — a record of which member of our team viewed or acted on what, and when — are kept as an accountability measure.
- Backups may hold data for a period after deletion, and are overwritten on a rolling basis.
7. Your rights
Depending on where you live, you may have the right to access, correct, delete, port, restrict, or object to our processing of your personal information, and to withdraw consent.
To exercise any of these, write to support@logist.live from the email address on your account. We will respond within the time the law requires.
- Deletion. We will delete your account and personal information. We may keep a minimal record — for example, the account identifier associated with a ban — where we have a legal basis, so that an enforcement decision is not undone by deleting an account. We will tell you if we do.
- California residents. We do not sell or share personal information as those terms are defined under the CCPA and CPRA. You have the right to know, delete, and correct, and not to be discriminated against for exercising those rights.
- UK and EEA residents. You may complain to your local supervisory authority.
8. International transfers
We are based in the United States and our providers are primarily located there. If you use the Service from outside the US, your information will be transferred to and processed in the US, which may not offer the same protections as your home country.
9. Cookies and local storage
We do not use advertising or analytics cookies. We use:
| What | Purpose | Type |
|---|---|---|
| Session cookie | Keeps you signed in; HttpOnly | Strictly necessary |
| Per-tab identifier in session storage | Lets the server recognise your connection if it drops mid-debate | Strictly necessary |
| Age confirmation flag | Saves you re-confirming every visit | Functional |
| Access code | Saves you re-entering it during invite-only periods | Functional |
10. Security
Traffic is encrypted in transit. Database connections use verified TLS. Access to the administrative console is restricted to a named list of company email addresses, protected by Google sign-in, and every action taken there is recorded against the individual who took it.
No system is perfectly secure. If we become aware of a breach affecting your personal information, we will notify you and the relevant regulators as required by law.
11. Children
The Service is for adults. It is not directed at children, and we do not knowingly collect personal information from anyone under 18. If you believe a minor is using the Service, write to support@logist.live immediately and we will act.
12. Changes
We may update this policy. If a change is material — particularly any change to what we collect during a call — we will give notice before it takes effect, by email or in the Service.
13. Contact
Logist Group, Inc. — support@logist.live
Questions about this page? support@logist.live
Logist Group, Inc.