Speedvideodating

Privacy

This site does not keep any information about you once the session ends. That is not a promise about our intentions — it is how the database is built, and this page shows you the row counts as they are right now.

What is in the database at this moment

TableRowsWhat happens to it
ban_owner_ips 1 kept (no personal data)
ban_strikes 513 kept (no personal data)
bans 171 kept (no personal data)
blocks 0 kept (no personal data)
bookings 1 kept (no personal data)
credits 0 kept (no personal data)
daters 0 purged at close
decisions 0 purged at close
exchanges 0 purged at close
hall_events 0 kept (no personal data)
halls 2 kept (no personal data)
host_events 0 kept (no personal data)
hosts 0 kept (no personal data)
meta 6 kept (no personal data)
notices 2 kept (no personal data)
optouts 0 purged at close
pairs 0 purged at close
payouts 0 kept (no personal data)
promo_knocks 7 UNCLASSIFIED
promo_matches 332 UNCLASSIFIED
promo_rooms 60 UNCLASSIFIED
promo_seats 1102 UNCLASSIFIED
promo_users 240 UNCLASSIFIED
push_subs 0 kept (no personal data)
rematch_asks 0 kept (no personal data)
reports 0 purged at close
room_state 16 kept (no personal data)
share_comments 0 purged at close
share_likes 0 purged at close
share_posts 0 purged at close
share_reactions 0 purged at close
signals 0 purged at close
stats 47 kept (no personal data)
suggestion_votes 0 kept (no personal data)
suggestions 0 kept (no personal data)
tickets 0 purged at close
time_requests 0 kept (no personal data)
visits 207 purged at close
waiting 0 kept (no personal data)
welcome_acks 7 UNCLASSIFIED

These tables are not yet classified: promo_knocks, promo_matches, promo_rooms, promo_seats, promo_users, welcome_acks. That is a bug and we would rather show it than hide it.

Database file: 744.0 KB. Last cleared: new day (2026-10-25 -> 2026-10-26). Rows marked purged at close are deleted at 21:00 and the file is then vacuumed, so the data is not simply left in free pages.

What we ask for

  • A wallet public key — because that is the login. No email, no password, no phone number.
  • Your age, how you describe yourself, who you want to meet, and what you are here for.
  • Your country and the city or town you are near, and the region you are willing to meet people in. A city, never an address and never coordinates — it is used to work out who can be matched with you, and to refuse countries we do not serve.
  • Optionally a line and a short bio, which are scrubbed of anything that looks like contact details.

What we never ask for

Your name. Your photograph. Your street address or GPS position. Your phone number. Your email address. Your social handles. Your payment card. None of these exist as fields anywhere in this application, which is a stronger guarantee than a policy saying we will not misuse them.

We ask which country and city you are near, and we take your word for it — we do not geolocate you and we do not look up your IP. A town is not a location in the sense people worry about, and it dies with everything else when the session ends.

What outlives a session

Being honest about the exceptions is the only way the rest of this page means anything.

1. Blocks. When you block someone we store a single one-way fingerprint of the two of you together — a hash, computed with a secret key, which cannot be turned back into either wallet. It lets us never pair you again without remembering who either of you was. There is no way to ask this table who blocked whom, including by us.

2. Counters. How many people came, how many rounds ran, how much was taken. Integers with no person inside them.

3. Notification subscriptions, if you switch them on. When you allow notifications your browser issues an address for that one device — not for you, and not readable as a name — and we store it so we can reach it later. It is filed under the same one-way hash as your bookings, so this table cannot be asked whose device it is. Every message we send is encrypted to that device, which means Google, Apple or Mozilla carry it without being able to read a word of it. Turn notifications off and the row is deleted immediately; so is any device that stops answering, and any device with no booking left waiting on it.

Bookings, session requests and suggestions also persist, because a booking for Friday would be useless if it were deleted on Tuesday. They are stored under the same kind of one-way hash and never contain a wallet — see the table above, where they are counted like everything else.

Video calls

Video and audio go directly between the two browsers using WebRTC. Our server passes the few kilobytes needed to introduce the two devices to each other and nothing else. The media never reaches us, so there is nothing for us to record, store, hand over or lose. This is a statement about what the system can do, not about what we intend to do.

Cookies and your browser

  • One session cookie, so the site knows which signed-in person you are. It expires by itself.
  • A little localStorage for your own appearance settings and your video preferences. That never leaves your device.
  • The offline shell caches only pages that contain nobody — never the lobby, a call, your matches or your inbox.
  • No third-party analytics, no advertising pixels, no trackers. We do keep a short, bounded log of page requests to spot abuse, and it is purged with everything else.

Payments

Tickets are paid in USDT on Solana. We hold no private keys and take no custody of anyone's funds. A payment is matched to your ticket by a random reference with no owner. The Solana blockchain is public and permanent, and that is outside our control — if that matters to you, use a wallet you are comfortable being seen.

Your rights, and why they are quick here

You can ask for a copy of your data, or ask us to delete it. Both are unusually easy: during a session, everything we hold about you is on your own profile page, and after it there is nothing to give you or delete. You can also leave at any moment and everything about you goes at the next close. There is no account to close, because there was never an account.

Changes, and children

This site is for adults only and is not directed at anyone under 25.

If this policy changes we will say so on this page. Because nothing is retained, a change can only ever apply to sessions after it is published.

Independently run. Questions about privacy can be raised through the suggestions board.