Privacy notice
What happens with your data on Splivex, in the order the GDPR asks for it. Every entry describes something the service actually does.
Last updated: 28 September 2026
1. Who is responsible
Controller under Art. 4 no. 7 GDPR:
Noah Maximilian Janko St. Veiterstraße 92 8046 Graz Austria
Email: splivex.support@gmail.com
2. What Splivex is
Splivex connects two people who hold opposite positions on a question for a video conversation of up to twenty minutes. Afterwards each person is asked once whether their view changed.
Understanding that shapes everything below: most of what is processed here is not a by-product of the service, it is the service. Positions are what matching works from; without them there is no opposite to find.
3. What is processed, why, and on what basis
Almost nothing here runs on consent. Account, positions, matching and the conversation itself are the service somebody signed up for — Art. 6(1)(b) GDPR, performance of a contract. Consent is needed for what is not part of the service, and that is listed separately in section 9.
| Data | Purpose | Legal basis | Kept |
|---|---|---|---|
| Email address, password | sign-in, confirmation, notices | Art. 6(1)(b) | until deletion |
| Username, display name, bio, profile picture | profile, being recognisable to the other person | Art. 6(1)(b) | until deletion |
| Date of birth (accounts only) | age check, 18 and over | Art. 6(1)(b) | until deletion |
| Your confirmation that you are 18 or over (trial only) | age check, 18 and over | Art. 6(1)(b) | until deletion |
| Positions on questions | matching people who disagree | Art. 6(1)(b) | until deletion |
| Conversations: question, participants, language, start, end, duration | history, statistics, moderation | Art. 6(1)(b) | until deletion |
| Whether your view changed | your own statistics | Art. 6(1)(b) | until deletion |
| Video and audio | the conversation itself | Art. 6(1)(b) | not stored — see section 4 |
| Still frame from a report | moderation, protecting other users | Art. 6(1)(f) | 30 days after the case is closed |
| Reports: reason, description, who reported whom | moderation | Art. 6(1)(f) | until deletion |
| Statements on questions, replies, marks | published to everybody who has answered that question | Art. 6(1)(b) | until you delete it, or the account |
| Messages you send us through the feedback box | answering you, and finding faults | Art. 6(1)(f) | until dealt with |
| Follows, blocks, invitations | the social side of the service | Art. 6(1)(b) | until deletion |
| Daily counters, queue entries, sessions | limits, matching | Art. 6(1)(b) | minutes to one day, see section 7 |
| Your IP address, to the person you are talking to | establishing the direct connection — see section 4 | Art. 6(1)(b) | not stored by us |
| IP address and browser identification on admin access | security of the administration area | Art. 6(1)(f) | until revoked |
| Your IP address and the email address you enter, both only as a one-way hash, when you sign in, register, enter a code, ask for a reset or start the trial | counting attempts, so passwords and codes cannot be guessed and accounts cannot be created in bulk | Art. 6(1)(f) | 1 day |
| Whether you asked for live-hour reminders, when the last one was sent, and a random code for the unsubscribe link; your email address is read from your account to send them | an email before a live hour, every few days at most, only if you ticked the box — never when you have been on Splivex recently | Art. 6(1)(a) — your consent, which you can withdraw at any time in settings or with the link in every reminder | until you switch reminders off or delete your account |
Legitimate interests, spelled out
The rows above marked Art. 6(1)(f) rest on a legitimate interest, and the interest has to be named rather than asserted.
Reports and the still frame: without a picture, moderation cannot decide a report about behaviour on camera — and without moderation the platform is unsafe for everyone else. The frame is a single image, captured in the reporting person’s browser at the moment they submit, and visible only to moderation.
Counting attempts: a six-digit code can be guessed by anybody willing to try often enough, and so can a weak password. The only defence is to count attempts — per network address and per account — and stop counting attempts that come too fast. The address and the email are turned into a one-way hash before they are stored: the counter only needs to recognise “the same one again”, not who it is. The records are deleted after a day.
Admin access records: if somebody gets into the administration area, every account on the platform is affected. Recording which account entered, from which address and which browser, is what makes that noticeable and reversible.
4. What you write on a question
Statements are published, and they stay until you remove them.
Everything else here happens between two people and is gone when the conversation ends. What you write on a question is different: it is shown to everybody who has answered that question, under your username, and it remains readable until you delete it or your account.
You can delete your own statements at any time, individually or by deleting the account. Moderation can remove one that breaks the house rules.
When somebody reports a statement, the text is copied into the report so that it can be reviewed even if it is deleted in the meantime. That copy is kept as long as the report is.
Reading requires a position of your own on that question, so the audience is limited to people who have answered it — but it is not a private space, and it is not encrypted. Write accordingly.
5. Video and audio
We do not record conversations.
Participants may record or stream one between themselves if both agree, and that agreement has to be given before it starts. Anything made that way is theirs, not ours — we neither hold it nor have access to it.
A conversation goes directly from one browser to the other. It does not pass through a server of ours, and it is stored nowhere.
What a direct connection means for your IP address
On a direct connection, your browser and the other person’s browser exchange their IP addresses with each other.
This is how a direct connection is established — there is no way to connect two browsers without each learning where to send the data. It happens for roughly four out of five conversations. We do not store those addresses and never see them, but the other participant’s device receives yours, and a person who knows how to read it can approximately infer your region and your internet provider.
The alternative would be to route every conversation through a relay of ours, which would mean we receive the addresses instead of the other participant. We consider the direct connection the better trade — but it is your data, so it is written here rather than left to be discovered.
About one connection in five cannot go direct — a company firewall, a restrictive mobile network. In that case a relay server forwards the data stream. It is encrypted between the two participants; the relay passes the packets on and cannot read them. On those connections the other participant does not learn your address; the relay operator named in section 6 receives it.
Camera and microphone are required to take part. You can switch either off during a conversation.
6. Who else receives data
These are processors under Art. 28 GDPR, acting on instructions. A data processing agreement has to be in place with each of them.
| Service | What it does | Data | Location |
|---|---|---|---|
| Supabase | database, sign-in, file storage, live signalling | all account and usage data, profile pictures, report images | eu-central-1, Frankfurt |
| Vercel | running the application | all requests, including IP address and browser identification | fra1, Frankfurt |
| Cloudflare | address lookup and relay for video connections | IP addresses; the encrypted stream when relaying is needed | worldwide |
| Resend | sending emails | recipient address, content of the message | USA |
Beyond these, nothing. Splivex uses no analytics service, no error tracking, no external fonts, no maps, no advertising network and no payment provider — there is nothing to pay for.
7. Transfers outside the EU
The database, the file storage and the application itself run in Frankfurt. Account data, profile pictures, statements and report images do not leave the EU in normal operation.
Two services can process data outside it, and each is named with what reaches it:
- Cloudflare — IP addresses during connection setup, and the encrypted stream on the roughly one connection in five that cannot go direct. Cloudflare operates a worldwide network, so the relay used is whichever is nearest.
- Resend (USA) — the recipient address and the content of emails we send you.
These transfers rest on the standard contractual clauses adopted by the European Commission, agreed as part of each provider’s data processing terms, and where the provider is certified, additionally on the EU-US Data Privacy Framework.
8. How long data is kept
Most data stays until the account is deleted. Some is removed automatically, and those periods run as scheduled jobs rather than as intentions:
| Data | Removed after |
|---|---|
| Report images | 30 days after the case is closed |
| Trial accounts without registration | 7 days after last use |
| Queue entries, session records | minutes to two hours |
| Rate limiting records | 1 day |
There are no billing records: Splivex takes no payments, so no statutory retention period applies to anything here.
9. Your rights
You have the right to information (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and objection (Art. 21).
You can delete your account yourself at any time under Settings. That removes your profile, your positions, your conversation history and your reports.
For anything else, write to splivex.support@gmail.com.
Right to complain
You can complain to a supervisory authority, in Austria the Datenschutzbehörde, Barichgasse 40–42, 1030 Vienna, dsb@dsb.gv.at.
10. Cookies and consent
Splivex sets three cookies, and none of them is for tracking:
| Cookie | Purpose | Duration |
|---|---|---|
| Sign-in session | keeps you signed in | until sign-out |
| splivex_device | recognises a device for the administration area, so an unfamiliar sign-in there raises an alert. Stored as a hash | 2 years |
| splivex_trial | a random value, so a browser gets the trial once. Only its hash is stored, and a hash cannot be turned back into the value — the record answers “has this browser had its trial” and nothing else | 1 year |
Both are technically necessary, so no consent banner is required and none is shown. Splivex stores nothing in local storage.
What you did consent to
At registration four points are confirmed: this privacy notice, the house rules, the use of camera and microphone, and the terms of service. The trial adds two — that you are 18 or over, which it asks for separately, and what the trial is. Which points were confirmed, and when, is recorded against the account rather than assumed from a list.
If something changes that requires agreement again, you are asked once the next time you open Splivex, with a summary of what changed.
11. Automated decisions
There are none in the sense of Art. 22 GDPR. Matching is a database query over the positions you gave: it looks for somebody who answered a question the other way, in your language, whom you have not just spoken to.
Splivex uses no AI to analyse, summarise or evaluate conversations. What you say is not processed, not transcribed and not scored.
12. Is providing data required
To use Splivex, yes. An account needs an email address, a username and a date of birth; a conversation needs camera and microphone. Without them the service cannot be provided. Nothing beyond that is required — display name, bio and profile picture are optional.
13. Changes to this notice
If Splivex changes in a way that affects this notice, it is updated beforehand. Where a change needs your agreement again, you are asked the next time you open Splivex rather than being told afterwards.