Privacy Policy

Last updated: 4 September 2026

Not yet complete. Everything below describes what the software actually does, and is accurate. What it does not yet contain is your legal identity, your jurisdiction, and a contact route for data-subject requests — all marked [TO COMPLETE]. This document has not been reviewed by a lawyer. Fill in the placeholders and have it checked before you take real users.

BeCloser lets viewers speak live during a stream. This policy explains exactly what we collect when you do, why, and how long we keep it.

We do not record your audio. Your microphone is relayed live to the host and is never written to disk or stored by BeCloser. The host, however, is almost certainly recording or broadcasting their stream — so assume anything you say is public and permanent. That is the point of the product.

1. Who is responsible

The data controller is [TO COMPLETE: legal entity name], [TO COMPLETE: registered address]. For anything in this policy, including requests to see or delete your data, contact contact@becloser.live.

2. What we collect

If you sign in with Twitch or YouTube

We receive, and store, only what identifies you as a possible guest:

Your account ID on that platform, and your handle
Your display name and avatar image URL
The date and time you last signed in

We do not receive your password. We do not post on your behalf, read your messages, or access anything beyond your public profile. For YouTube we additionally request read access to your channel, solely to read your @handle so we can check it against the host's guest list.

If you sign in with an event username and password

The username the organiser issued you, and the display name they gave it
A cryptographic hash of your password — never the password itself
The date and time you last signed in

When you reserve a seat

Which event, which seat and which zone
A random token that acts as your microphone link
The time of the reservation

Automatically

Your IP address, in our server logs. Used to keep the service up — rate limiting and abuse prevention — and for nothing else.
A session cookie (bc_session) so you stay signed in. It holds a random identifier, nothing about you. There are no advertising or analytics cookies on this site.

3. Why we collect it, and on what legal basis

Data	Purpose	Basis (GDPR Art. 6)
Account identity	Check you are on the host's guest list; show the host who is speaking	Contract — you cannot be given a seat without it
Session cookie	Keep you signed in between pages	Strictly necessary — no consent banner required
Reservation	Hold your seat and issue your microphone link	Contract
IP address in logs	Rate limiting, abuse prevention, diagnosing faults	Legitimate interest — keeping the service available

4. What we never do

Sell or rent your data
Share it with advertisers, or run advertising or analytics trackers
Record, store or transcribe your microphone audio
Build a profile of you across events beyond your seat history
Email you anything you did not ask for

5. Who else is involved

Your data passes through these providers, and no others:

Amazon Web Services — runs the audio relay [TO COMPLETE: region]
IONOS — hosts the website and the database [TO COMPLETE: region]
Twitch and Google/YouTube — only if you choose to sign in with them, under their own privacy policies
Google Fonts — serves the typeface, and receives your IP address when a page loads

[TO COMPLETE: if any provider is outside the EEA/UK, name the safeguard relied on — Standard Contractual Clauses or an adequacy decision.]

6. How long we keep it

Data	Kept for
Session cookie	30 days, or until you sign out
Reservation and microphone token	Until the event ends; the link stops working then
Account record	[TO COMPLETE: choose a period — 12 months after your last sign-in is a defensible default]
Server logs with IP addresses	[TO COMPLETE: 30–90 days is typical]

7. Your rights

If you are in the EU, EEA or UK, you have the right to access your data, correct it, have it deleted, restrict or object to how we use it, and receive a copy in a portable format. You may withdraw consent at any time, and you may complain to your national data protection authority.

Ask by emailing contact@becloser.live. We will respond within one month.

8. Children

BeCloser is not intended for anyone under [TO COMPLETE: 13, or 16 in some EU states]. We do not knowingly collect their data. If you believe a child has given us data, tell us and we will delete it.

9. Security

Traffic is encrypted in transit (HTTPS/WSS). Passwords are stored only as salted scrypt hashes. Session cookies are HttpOnly and Secure. Access to the host tools requires a separate key.

No system is perfectly secure. If you find a vulnerability, please report it to contact@becloser.live rather than disclosing it publicly.

10. Changes

We will update the date at the top when this policy changes. If a change is significant, we will say so on the site before it takes effect.