Privacy policy

FARWA Holding Ltd. (contact@diar.tv) is the data controller for DiarLaunch and is responsible for the personal data described below.

This policy covers the DiarLaunch website and the diar+ app for Android, iOS and the web. Where the app does something the website does not, it is said here.

From agents: name, contact details, agency/company name, spoken languages, bio, and brokerage licence documentation submitted during application and verification — and, in the diar+ app, the pictures and clips an agent posts as stories, which are public for twenty-four hours, and the broadcasts they go live with.

From viewers submitting an EOI or making an offer: name, email, phone, nationality, preferred unit type, any message you include, and a photo ID or passport uploaded with your submission.

From anyone using the contact form: name, email, and the content of your message.

From newsletter subscribers: your email address, the language you were browsing in, which page you signed up from, and the date and IP address of your consent. We keep the consent record so we can show when and how you asked for the newsletter. Every issue carries a one-click unsubscribe link; unsubscribing is recorded rather than deleted, so you are not added back by a later import.

You do not need an account to browse launches, on the website or in the diar+ app. Favourite (heart) selections stay on your own device — the browser's local storage, or the app's — and never reach our servers; we only count how many people have favourited a host.

If you sign in, on the website or in the diar+ app: the email address you signed in with, whether by an emailed link or code, or with Google; the launches you save; and, once you have made an enquiry, the name, phone number and nationality you entered, kept on your account so that your next form is filled in for you. If you allow notifications, we also hold the token your phone issues, or the subscription your browser issues, so that we can send them. You can withdraw that at any time under Alerts in the app, on your account page on the website, or in your phone's or browser's settings.

If you turn on notifications in your browser: the address that browser issues so that we can reach it, and when it was last used. Nothing else about the browser or the device is kept. The address is deleted when you turn notifications off, and when the push service tells us it no longer works.

• To verify an agent's brokerage licence before approval.
• To pass your EOI details to the listing agent so they (and, where relevant, the developer) can follow up with you directly.
• To respond to messages sent via the contact form.
• To keep the details you entered for your next enquiry, and to send the notifications you asked for, if you use the diar+ app and sign in.
• To operate core platform functionality — showing live launches, viewer counts, and in-stream chat.

An EOI you submit is visible to the agent hosting that launch, and is used to facilitate direct follow-up with the developer. Photo ID/passport uploads and brokerage licence documents are stored in access-controlled storage and are never publicly accessible — only the relevant agent (for their own leads) or a DiarLaunch administrator (for verification) can retrieve them, via short-lived signed links.

We do not sell personal data, and we do not share it with advertisers.

We use Supabase for database, authentication, and file storage, and Resend for transactional email (application, approval, and lead notifications). These providers process data on our behalf under their own security and privacy commitments, and only to the extent necessary to operate DiarLaunch.

We also use Google Analytics (GA4) for anonymous usage statistics, Cloudflare for live video delivery and for bot protection on public forms (Turnstile, which receives your IP address in order to check that a submission is genuine), and Vercel to host and serve this site. The booking calendar on our briefing page is provided by Calendly, and the map on our contact page by Google Maps. Neither loads until you ask it to. When you load one, that provider receives your IP address and the address of the page you are on, and may store cookies in your browser.

If you turn on notifications in your browser, the push service that browser uses (Google, Mozilla or Apple) receives the address it issued for that browser, so that we can reach it. It never receives your name or what a notification says: the push we send is empty, and your browser fetches the wording from us when the notification arrives. You can turn this off at any time from the same button, or in your browser settings.

The diar+ app relies on a few more. When you choose to sign in with Google, Google handles the sign-in and tells us the address on your Google Account; we never see your password. Expo delivers the notifications you allow through its push service (which receives the notification token, not your name), delivers updates to the app's code, and serves the web version of the app at diar-plus.expo.app. Cloudflare Stream transcodes the clips an agent posts as stories and delivers every broadcast you watch.

When we review a broadcast for advertising compliance, Cloudflare produces a written transcript and we send that text — never the audio — to Anthropic’s Claude API, which checks it against our advertising rules. We do not keep the transcript; the caption track stays with Cloudflare alongside the recording.

Cookies. We store your language choice and your answer about analytics cookies. In the EEA and the UK, Google Analytics stays off until you accept it. Elsewhere it is on by default — you can switch it off at any time under Cookie settings, at the bottom of every page. Either choice costs you no functionality.

If you apply for a job with us, we collect your name, email, phone number, the role you applied for and the CV you upload, and keep them only for as long as we are considering applications. We also record the IP address a lead or enquiry was submitted from, in order to detect abuse.

Messages sent in a launch's live chat are public. They are shown to everyone viewing that launch, including people who arrive later, and are stored in our database alongside the display name you enter. Please do not share private information in chat.

Each message carries an identifier generated for it, so a retried send is not stored twice. The diar+ app also keeps a random identifier for your device, used only to tell your own actions apart from other people's — a reaction you sent, a host you favourited — and never for advertising.

You can report a chat message or a story from the app. We keep the report — what was reported, the reason you chose, that device identifier and, if you were signed in, your account — for as long as it takes a person to look at it, and it is never shown to the person you reported.

We retain agent verification records for as long as an agent account remains active, and EOI records for as long as needed to support the launch and any related follow-up. You can request deletion of your data — see below.

You can request access to, correction of, or deletion of your personal data by contacting us via our contact page. We'll respond as soon as we reasonably can.

If you signed in, on the website or in the diar+ app, the same applies to the account this created: write to us from the address you signed in with and we will delete it and everything it holds — or delete it yourself from your account page.

We may update this policy from time to time. Material changes will be reflected by updating the date at the top of this page.