Privacy policy

1. Who is responsible and how to reach us

The data controller for the processing described here is the operator that provides RaceBroadcast from Türkiye — the same operator that provides QuizBroadcast (quizbroadcast.com) — (the “Operator”, “we”).

You can reach us, including for requests under the KVKK, through the contact form on quizbroadcast.com. RaceBroadcast has no contact form of its own; that one reaches the same Operator.

2. Roles for broadcaster and viewer data

RaceBroadcast processes data in two different roles:

• As data controller: we decide the purposes and means of the data we process to run broadcaster accounts, provide the app and the broadcast screen, keep the service secure and answer messages sent through the contact form.
• As data processor: we process viewers’ usernames, display names, chat messages and gift records from a broadcaster’s LIVE broadcast on that broadcaster’s behalf, to run the races and polls they start. As a rule, the broadcaster who runs them is the data controller for this data.

The broadcaster is responsible for telling the viewers on their broadcast about RaceBroadcast and for settling requests viewers make to them; we carry out the technical steps these requests need at the broadcaster’s request. Data being publicly visible on TikTok does not in itself remove the protection of the KVKK.

3. Your account, shared with the Operator’s other services

RaceBroadcast signs you in with the Operator’s one account: an account created here also signs you in to QuizBroadcast, and an account created on QuizBroadcast signs you in here. The account record, which each of the Operator’s services reads and writes, holds:

• your email address
• a one-way hash of your password; we never store the password itself
• the language you choose, the country you choose when you sign up, and your account plan, which the Operator sets
• your TikTok username, if you enter it
• your logo, if your plan lets you upload one
• when the account was created, and the time of each registration and sign-in, with the Operator’s service it was on and whether it was a single sign-on; no IP address is kept with these
• when you ask for a password reset: only a hash of the reset key, when it was issued, when it expires (60 minutes later) and when it was used
• for single sign-on: a random identifier for each sign-in, shared by the services you reach from it by single sign-on, with when it was created and, to within a day, when it was last used; and, while you pass from one of the Operator’s services to another, only a hash of a one-time code that works for 60 seconds, with the two services it is between and a check value tied to the browser that asked for it

Because the record is shared, a change you make here — to your TikTok username, your language or your logo — is the one every service of the Operator sees, and your plan is the same on all of them. Once you are signed in to one of them, single sign-on (“Continue with …” on another’s sign-in page) signs you in to that other one without your password. A sign-in that single sign-on has carried from one service to another is one sign-in: signing out of any of them ends it on all of them. A password reset, made on any of them, signs your account out of all of them, in every browser.

The password-reset email contains the reset link and a few lines of fixed text, and is sent through Amazon SES.

4. What RaceBroadcast keeps for itself

Everything else RaceBroadcast keeps is its own: the Operator’s other services do not read it. The first time an account signs in to RaceBroadcast, RaceBroadcast opens its own record for it, and keeps:

• the secret key in your broadcast link
• your idle and ticker messages, and the broadcast screen’s design: its accent colour and whether the supporter boards are shown
• the polls you save: the question, the answers, how viewers vote (by typing a letter or by sending gifts) and the timer
• a record of each race: the name you gave it, if any, its status, when it started and ended, and how many chat lines it heard — never the lines themselves
• each broadcast session in which RaceBroadcast was connected to your live chat: the TikTok username it was connected to, the type of connection, when it connected, when it was last seen connected, when it ended and why
• the gift records of your broadcasts, described in section 5

You can delete a saved poll, clear your messages and remove your TikTok username yourself in the app; on a plan that includes the designer you can also remove your logo and reset the design to the default. You can renew the secret key in your broadcast link at any time (“Reset link” on the dashboard).

5. Viewers: chat messages and gifts

In a LIVE broadcast that uses RaceBroadcast, chat and gift events arrive through the connection service Euler Stream. Each carries the viewer’s TikTok username (or, if there is none, their numeric TikTok ID), their display name, the message or the gift, the time, and the address of their TikTok profile picture. Of the broadcast’s events, RaceBroadcast reads only chat messages and gifts.

Chat messages are not saved. While a race is running it counts the chat lines it hears — only the count is saved, with the race — and keeps the latest line (its author’s username and display name, and its text) in the server’s memory for the management screen, until the race leaves that screen: when the next race or poll starts, about five minutes after the race ends, or when the server restarts. Each message heard during a race or a poll is also passed live to the management screen’s chat feed, and kept nowhere else on the server.

During a poll, viewers vote by typing a letter or by sending gifts. Who chose which answer is held only in the server’s memory while the poll is open and is forgotten when it closes; only the totals stay on screen, and no vote is saved. A gift sent as a vote is recorded like any other gift.

What we do save is a record of each gift sent to the broadcaster: the sender’s TikTok username (or numeric TikTok ID) and display name, the gift and its name, how many were sent, the value of one in diamonds as TikTok reports it, when it arrived, the race it arrived during, if any, and an identifier of the gift event, so that it is not counted twice. A gift sent to someone else in the LIVE — the other side of a match, for example — is not recorded.

From these records RaceBroadcast keeps two supporter boards: the biggest gifters of the show in progress, held in the server’s memory until nothing is on air and no gift has arrived for six hours, and the biggest gifters across all of the broadcaster’s broadcasts, read from the saved gift records.

RaceBroadcast never saves the text of a chat message or who wrote it, and it does not download, keep or show viewers’ profile pictures: a picture’s address arrives with each event and is discarded unused. RaceBroadcast does not collect payment for gifts and has no access to viewers’ payment details.

6. What the screens show

The broadcast screen is part of your stream, so everyone watching sees what it shows: the race’s name and its count of chat lines, your messages, your logo on a plan that includes one, and a poll’s question and totals. If your plan includes the designer and you switch the supporter boards on — they are off by default — it also shows the display names and diamond totals of the five biggest gifters of the show in progress while a race is on screen, and of all your broadcasts between races. It never shows a chat message or a viewer’s picture.

The mobile screen, which you share while you go live from a phone, shows the broadcast screen and its own controls, and nothing more from the chat.

Your management screen also shows the latest chat messages and gifts as they arrive, each with its sender’s display name, the supporters of the show in progress, and the race’s latest line. It is yours alone unless you show it to someone.

7. Contact form

RaceBroadcast’s pages have no contact form; the Operator’s is on quizbroadcast.com. When you write to us through it, we save:

• your name, email address and message
• the page language and the time it was sent
• a shortened hash of your IP address made with a secret key; the IP address itself is not kept in this record
• a hash of the message text, to notice when the same message is sent again

We use this data to answer your message and to prevent abuse of the form. We read messages in the Operator’s administration tool and reply by email from the Operator’s Google Workspace account. The contact page itself is part of quizbroadcast.com, which measures its visits with Google Analytics; QuizBroadcast’s privacy policy covers that site.

8. Server logs

For every request, the web server in front of the app and the app itself record the date and time, the address requested — for the broadcast screen, an address that contains the key of your broadcast link — the IP address, details the browser sends such as its type, its language and the page it came from, the response status, size and duration and, when you are signed in, your account number. The app also records events such as sign-ins, password-reset requests and chat connection failures under your account number, never your email address. We use these logs to run the service, find errors and prevent abuse; they are kept in Amazon CloudWatch Logs and deleted automatically after 30 days.

Passwords, session cookies, password-reset keys, single sign-on codes and API keys are kept out of these logs, and so are viewers’ usernames, display names, messages and pictures. For rate limiting, IP addresses are also held in the server’s memory, for an hour at most.

9. Cookies and browser storage

RaceBroadcast uses no advertising or analytics cookies, and none of its pages loads an analytics, advertising or tracking script. What it keeps in your browser, all of it on app.racebroadcast.net, is:

race.sid cookie, strictly necessary

The session cookie, created when you sign in or create an account. Before you sign in, it is created only when a sign-in through another of the Operator’s services begins, and then it expires 10 minutes after its last use unless the sign-in completes. Scripts in the browser cannot read it, it is sent only over encrypted connections, and it expires 30 days after you last use it. The session record it points to on the server holds your account number and what lets a sign-out or a password reset on another of the Operator’s services end it — and, during a single sign-on, the values that check the sign-in comes back to the same browser.

race.locale local storage, preference

The interface language.

race.mobileBg local storage, preference

The mobile screen’s background.

race.ssoPeer local storage, preference

Once you have signed in through another of the Operator’s services, which one, so that the sign-in page can sign you in through it again without asking. It is deleted when you sign out of RaceBroadcast.

race.ssoTried session storage, preference

A note that the open tab has already tried that once.

race.reloadPicks session storage, strictly necessary

When the management or mobile screen, left open for a day, reloads itself to update, the race name in its start box, the poll selected on it and its language, so that they survive the reload. It is read and removed straight after, and ignored once it is five minutes old.

Local storage stays in your browser until you delete it, and session storage until you close the tab. The browser does not send either to the server on its own: a race name reaches the server only when you start that race, and is then kept with it. You can view, delete or block cookies and site data in your browser settings; if you block the race.sid cookie you cannot sign in.

10. Purposes, legal bases and how we collect data

We collect personal data by electronic means: from what you enter in the app and what your browser sends while you use it, and — for viewers — from TikTok LIVE through the connection service. We process it on these legal bases:

• Establishing and performing the contract (KVKK Art. 5/2-c): opening and running your account and signing you in to the Operator’s services with it; keeping your settings, polls and races; connecting to your live chat, counting its lines, recording gifts and keeping the supporter boards; providing the broadcast, management and mobile screens; applying plan features; and sending password-reset emails.
• Legal obligation (KVKK Art. 5/2-ç): responding to requests from competent authorities and answering requests under the KVKK.
• Establishing, exercising or defending a right (KVKK Art. 5/2-e): reviewing and preserving records in disputes and cases of abuse.
• Legitimate interest (KVKK Art. 5/2-f): keeping the service and accounts secure, preventing automated attacks and abuse of the contact form, finding errors, and answering messages sent through the contact form.

For viewer data we process on a broadcaster’s behalf, the broadcaster who runs the race or poll determines the legal basis. Your right to object to processing based on legitimate interest is described in section 17.

11. Who we share data with

We do not sell personal data or use it for advertising. We share data only as far as the service requires, with:

• Amazon Web Services (AWS): the server, the encrypted disk the databases are kept on, backups (Amazon S3), server logs (Amazon CloudWatch Logs) and password-reset emails (Amazon SES), all in the Frankfurt region in Germany.
• Euler Stream: the intermediary service that connects to TikTok LIVE chat. To connect, it receives the broadcaster’s TikTok username, and it passes us the chat and gift events of the broadcast, with the viewer information described in section 5.
• TikTok: RaceBroadcast sends TikTok nothing itself; Euler Stream connects to your LIVE on our behalf. Your broadcast, its chat and its gifts are TikTok’s service, covered by TikTok’s own terms and privacy policy.
• The Operator’s other services: the shared account record described in section 3, which QuizBroadcast uses as RaceBroadcast does.
• Viewers of your broadcast: what the broadcast screen shows, as described in section 6.
• Google: only if you use the contact form, as described in section 7.
• Competent persons and authorities: courts, law enforcement and regulators, where a legal obligation, a lawful request or the defence of a right requires it.
• An acquirer: if the service is transferred or reorganised, under a duty of confidentiality and only as needed; we will inform you if a transfer happens.

12. Transfers outside Türkiye

RaceBroadcast is run from Türkiye, but its data is hosted outside Türkiye: the databases, server logs, backups and password-reset email are in AWS’s Frankfurt (Germany) region. Euler Stream may process data outside Türkiye, in other countries including the United States, and so may Google if you use the contact form.

These transfers fall under Article 9 of the KVKK. You can ask through the contact form which provider data is transferred to, to which country and on which transfer basis.

13. How long we keep data

• Session cookie and the server’s session record: 30 days from last use, or 10 minutes for one opened to begin a single sign-on; expired sessions are deleted automatically.
• Account record, sign-in records, RaceBroadcast’s own record, race records and broadcast sessions: for as long as the account is open.
• Saved polls, messages, logo and design: until you delete them or the account is closed.
• Password-reset records: a reset link works for 60 minutes, and its record is deleted automatically once it has expired, the next time a reset is asked for.
• Single sign-on records: a sign-in’s identifier until you sign out, reset your password or leave it unused for 32 days; one-time codes are deleted automatically after they expire.
• Chat messages: not saved. The latest line of a race is held in memory until the race leaves the management screen, as section 5 describes.
• Poll votes: held in memory until the poll closes.
• Supporters of the show in progress: held in memory until nothing is on air and no gift has arrived for six hours.
• Gift records: there is currently no automatic deletion period; they are kept until they are deleted on request or the broadcaster’s account is closed.
• Contact form messages: after they are answered, until the Operator deletes them.
• Server logs: 30 days.
• Backups: the databases — RaceBroadcast’s and the shared account file, but not the session records — are backed up every night, and a backup is kept for about 120 days at most; deleted data can remain in older backups until that period ends.

Where there is a legal retention obligation, an ongoing investigation or a legal claim, the relevant data may be kept for as long as needed with access restricted. A deletion on TikTok does not by itself remove a record that had already reached RaceBroadcast.

14. Security

We apply technical and organisational measures in proportion to the risk:

• all connections to the app are encrypted with TLS
• passwords are hashed one way; password-reset keys and single sign-on codes are stored only as hashes, and reach the server only in the body of a request, never in a web address it records
• a password-reset link works once and for 60 minutes, and completing a reset signs out every session on all of the Operator’s services
• a single sign-on code works once, within 60 seconds, and only for the service and the browser that asked for it
• the session cookie cannot be read by scripts in the page and is sent only over encrypted connections, and every sign-in starts a new session
• the databases are kept on an encrypted disk, and backups in encrypted storage closed to public access
• each broadcaster’s data is separated by account in the database queries
• the Operator’s administration tool, which reads the shared account records and contact messages, is not reachable from the internet, only through an encrypted tunnel
• chat messages, the state of the chat connection and what only the management screen shows are never sent to the broadcast screen, and viewers’ picture addresses never leave the server
• you can renew the key in your broadcast link at any time, and the old link stops working at once
• sign-in, registration, single sign-on, password-reset and contact-form requests are rate-limited, as are the app’s other API requests

No internet system is absolutely secure. Keep your password and your broadcast link secret, and tell us straight away about any suspicious access. If we learn of a personal data breach, we make the notifications the KVKK requires.

15. Automated decisions

RaceBroadcast makes no decision about anyone by automated means: today a race counts the chat lines it hears and names no winner, and a poll only adds up votes.

16. Children

RaceBroadcast accounts are only for people aged 18 or over. Younger viewers can, however, write in a TikTok LIVE chat; the broadcaster is responsible for setting age-appropriate rules for their audience and any prize. If you believe a child’s data is being processed unlawfully, tell us through the contact form.

17. Your rights

Under Article 11 of the KVKK you have the right to:

• learn whether your personal data is processed
• request information about it if it is
• learn the purpose of the processing and whether the data is used accordingly
• know the third parties in Türkiye or abroad to whom it is transferred
• ask for it to be corrected if it is incomplete or inaccurate
• ask for it to be deleted or destroyed where the conditions of Article 7 of the KVKK are met
• ask for corrections, deletions or destruction to be notified to the third parties the data was transferred to
• object to an outcome against you that results solely from analysis by automated systems
• claim compensation if you suffer damage because of unlawful processing

If you are in the European Economic Area or the United Kingdom, you may also have rights under the General Data Protection Regulation (GDPR) to access your data; to have it corrected, erased, restricted or ported; to object to processing based on legitimate interest; and to complain to the data protection authority of your country.

Where other laws require us to keep data, or a request would infringe the rights of others, we may not be able to meet a request in full or in part; in that case we explain why.

18. How to make a request, and closing your account

Send your request through the contact form, starting the message with “KVKK request”. State your name, your request, your RaceBroadcast account’s email address or the relevant TikTok username if there is one, and the approximate date and broadcast the request concerns. If you apply on someone else’s behalf, a document showing your authority is needed. Do not send identity documents we have not asked for; if needed, we will tell you a secure way to verify your identity.

The app has no button to close your account yet: ask through the contact form. Your account is the same on all of the Operator’s services, so closing it closes it on all of them, and we then delete what each of them keeps for it, RaceBroadcast’s records included. If you only want to stop using RaceBroadcast, say so: we delete RaceBroadcast’s own records and leave the account open for the others. Deleted data can remain in backups for the period given in section 13.

Requests are settled free of charge as soon as possible according to their nature, and within 30 days at the latest; if handling a request involves an additional cost, the fee in the tariff of Türkiye’s Personal Data Protection Board may be charged. If your request is refused, you find the answer insufficient, or it is not answered in time, you can complain to the Board within the periods set by the KVKK.

If you are a viewer and your request concerns a gift record from a broadcast, the fastest route is to contact the broadcaster who ran it first. If you cannot reach the broadcaster, you can contact us directly. Before disclosing broadcast data about someone, we verify that the identity, broadcast and record match.

19. Changes to this policy

We update this policy when the service, the data flows, our providers or the law change; while RaceBroadcast is in early access, expect it to change with the race. The date of the last update is shown at the top of the page. We announce a change that materially affects your rights or the purposes of processing on this page, and by email where appropriate, before it takes effect.