We don't collectwhat we don't need.
Effective: 23 October 2026 (Cloudflare R2 named as the store for Stream Cloud recordings; before that, 22 October 2026: connected platforms, Plan-to-Cloud and every provider named; crash reports carry your account email, not your name, plus the module's recent log lines; 21 October 2026: genuine-copy check added, and the build marker in crash reports; 11 October 2026: demo requests added, and what we keep about the PCs signed into the Studio spelled out) · Broadcasteer by Abelitie Designs · Governed by PDPA 2010 (Malaysia)
The Short Version
For your account, we collect your name and email address from your Google account. Authentication is handled entirely by Google OAuth; Broadcasteer never asks for, sees or stores a password. If you connect YouTube, Facebook, Twitch or Google Drive, we keep the access token that service gives us (never your password for it) until you disconnect. We don't sell your data, share it, or use it for anything beyond running your account. If you subscribe, your payment is processed by Stripe — we never see your card number.
If you use Broadcasteer Relay, your live service passes through our infrastructure on its way out. We don't record it, and the only thing we measure is how many bytes went through this month — no IP addresses, no session logs.
If you ask for a demo, we keep the details you type into that form — only to arrange the demo and follow up. You send them to us on WhatsApp yourself, and we keep a copy so a request isn't lost. See Demo requests below.
What We Collect
- ✓Name & email address — Provided by Google at sign-in via OAuth. Used to identify your account and send transactional emails. Nothing else.
- ✓Subscription status — Which plan you are on (FREE / PRO / MAX) and billing cycle dates, provided by Stripe.
- ✓Connected platforms — Only if you connect them in Settings. YouTube, Facebook, Twitch and Google Drive each give us an access token (never your password for them). We keep it in your account so the Studio can create, run and end your broadcasts, or save plans to your own Drive. Disconnect removes it.
- ✓PCs signed into the Studio (seats) — For each PC signed into the Studio: a random ID the desktop app creates on that PC, the PC's Windows computer name, your first name, and when its Studio was last open. Used to enforce your plan's seat limit and to list your PCs under Seats on your dashboard. A PC's entry is removed when you sign out of the Studio on it, release it from your dashboard, or another PC takes its seat.
- ✓Crash & reliability reports (Sentinel) — If a Broadcasteer module fails and Sentinel reporting is enabled (Settings › Fortress — on by default, off anytime), we receive a technical report: app version, build marker, Windows version, processor type, the error's technical trace, and that module's last 60 log lines with file paths and keys masked. It carries your account email and the PC's machine ID so we can reach you about it, never your name. It never carries the contents of your lyrics, media, plans or messages, though a log line can name a file or a song. Deleted with your account.
- ✓Genuine-copy check — To protect Broadcasteer from unlicensed copies, the desktop app includes its name and build marker when it verifies your licence, and the Studio checks which web address it is running from. We record something only when it does not look genuine (the Studio running from a web address that is not ours, or an app reporting a name or build marker that is not ours): the product, version, build marker, that web address or app name, the country (from our hosting provider, never your IP address) and, if signed in, the account. Genuine copies are never recorded. It only reports; it never switches anything off on your PC.
- ✓Relay data volume — If you use Broadcasteer Relay, we count how many bytes were relayed and keep one running total per calendar month — literally a month label and a number. No IP addresses, no session logs, no per-connection records, nothing about who connected or what was carried. It exists only to enforce your monthly allowance.
- ✓Your Broadcasteer address — If you claim one, we store the name you chose and the tunnel record that points it at your setup.
- ✓Demo requests — If you fill in "Request a demo" (no account needed): your name, position, phone number, email address, church or organisation, its congregation size and language, your town (or where you are, if outside Perak), and on our Contact page anything you add as a note — plus which page you sent it from, when, and which version of the notice you agreed to. Used only to arrange your demo and follow up about Broadcasteer. Details below.
What We Do Not Collect
- ✗Recordings of your broadcasts — unless you turn on Stream Cloud (MAX+) and choose to keep a service; see “Stream Cloud recordings” below. Relay passes through and is never written down
- ✗Usage analytics or behavioural tracking
- ✗Location or GPS data from your devices (the town you give in a demo request is the only place we know about)
- ✗Third-party advertising pixels or tracking scripts
- ✗Card numbers or banking details (Stripe handles all payment data)
- ✗Any data from your cameras or microphones beyond the live session
- ✗IP addresses or connection logs for relayed sessions
Why We Require an Account
Registration confirms you are a real person — not a bot or automated script. It allows us to enforce fair usage (seat limits per plan) and send you transactional emails. Sign-in is handled by Google OAuth — Broadcasteer never creates or stores a password on your behalf.
A subscription is entirely optional. You can use Broadcasteer FREE indefinitely with no payment required. Subscribing to PRO or MAX simply unlocks additional features when you are ready.
Payments (Stripe)
Subscriptions are processed by Stripe Inc., a PCI-DSS Level 1 certified payment processor. Stripe stores your card details on their secure servers — Broadcasteer does not receive, store, or have access to your card number or bank details. We only receive your subscription status (active / cancelled) and renewal dates. Stripe's own privacy policy governs your payment data.
Your Rights (PDPA 2010)
Under Malaysia's Personal Data Protection Act 2010, you have the right to:
- →Access — Request a copy of the personal data we hold about you.
- →Correct — Update or correct inaccurate data via your account settings at any time.
- →Delete — Write to support@broadcasteer.com from your account email stating that you want your account and data deleted. We complete deletions within 30 days, including any Stream Cloud recordings. Stripe billing records are retained as required by Malaysian tax law (7 years). If you only sent a demo request, write to info@broadcasteer.com or message us on WhatsApp and we delete it within 30 days.
- →Withdraw consent — You may close your account at any time to withdraw consent for data processing. For a demo request, tell us to stop and we stop contacting you and delete it.
To exercise any of these rights, email info@broadcasteer.com. We respond within 14 working days.
Data Storage & Security
Sign-in is handled by Google OAuth. Your identity data (name, email address, Google account ID) is stored in Broadcasteer's own account database. Broadcasteer does not store passwords — none exist. Subscription data is managed by Stripe. Data in transit is encrypted via TLS 1.3.
Demo requests are kept in the same Firebase database, which Google encrypts at rest.
Our website and platform are hosted on Vercel, Inc. infrastructure. When you use Connect-Anywhere (remote) features, Broadcasteer Relay, or a Broadcasteer address, your live session traffic — including video — transits Cloudflare, Inc.'s network via an encrypted tunnel or relay; it passes through in real time and is not stored by us or by Cloudflare on our behalf.
We do not store your broadcast sessions, stream recordings, or camera footage on our servers. Broadcasteer is a local-first tool — your production data stays on your device. Two exceptions are yours to switch on: Plan-to-Cloud saves a plan, its song words and its media to your own Google Drive (Broadcasteer can see only the files it created there), and Stream Cloud keeps the recordings described below.
Stream Cloud recordings
Stream Cloud is an optional MAX+ add-on. When you turn it on, each service you stream through your Broadcasteer address is saved so your people can replay it. Those recordings are stored on Cloudflare R2 on your behalf: the standard-definition copy for as long as your address is active, and the high-definition copy for up to two years. You can delete any recording at any time from Studio › Stream Cloud, and that is the only place it can be deleted from. If the add-on lapses, your library stays readable for 90 days, then our daily sweep removes it. Nothing is recorded unless you switch Stream Cloud on.
Broadcasteer Relay
Relay is a pipe, not a recorder. Your service passes through our infrastructure and is gone. We keep no copy, no cache, no archive — and the only thing we measure is how many bytes went through, as a single running total per month.
When Relay is active, your live session — congregation video and audio included — transits Cloudflare's relay network on its way to its destination. That traffic is encrypted in transit. It is not written to disk by us, and we have no ability to play back a service after it has ended.
Your congregation's data. Live services capture people who never signed up for Broadcasteer — congregation members, children, and people sharing prayer requests or personal testimony. For that footage your church is the data controller: you decide what to broadcast and you are responsible for the notices and consents your local law requires. We act as a processor, carrying the stream on your instruction and for no purpose of our own. We never use it to train anything, never review it, and never share it.
Metering. Enforcing the monthly allowance needs one number, so that is all we keep: a month label and a byte count, plus any air-time you have purchased. No IP addresses, no timestamps beyond the month, no record of which devices connected or how long they stayed.
Demo Requests
What we ask for. The "Request a demo" form on our homepage and Contact page asks for a contact person, their position, a phone number, an email address, the church or organisation, its congregation size and main language, and your town in Perak (or where you are, if you're outside Perak). All of these are needed to arrange a demo; on the Contact page you can also add a note if you like. You don't need an account, and you tick a box to agree before anything happens.
How it reaches us. Pressing the button opens WhatsApp with your details written into a message to us. Nothing goes through WhatsApp until you press Send there, and that message is covered by WhatsApp's own privacy policy. At the same moment the website saves a copy in our Firebase database, so a request isn't lost if the WhatsApp message never gets sent. We also record which page you sent it from, when, and which version of this notice you agreed to.
Why. Only to contact you to arrange the demo — in Perak we come to your church; elsewhere we talk first — and to follow up about Broadcasteer. Not for advertising. We never sell it or share it with anyone else.
How long. We keep a request only as long as we need it to arrange and follow up the demo. Ask us to delete it at any time — by email to info@broadcasteer.com or on WhatsApp — and we do so within 30 days. You can also ask for a copy of what we hold, or for a correction.
Spam protection. To stop automated sign-ups, the website limits how many requests one connection can send. It does this with a one-way code made from your IP address, held in the server's memory for up to an hour and never saved. Your IP address is not stored with your request.
Who Else Touches Your Data
We use a small number of service providers. Each one is bound to process data only on our instructions:
- →Google LLC — Sign-in via OAuth (your name and email address; never a password). Gmail, which sends our account and service emails. And only if you connect them: YouTube, to create and run your broadcasts, and Google Drive, for Plan-to-Cloud and support uploads.
- →Vercel, Inc. — Hosting for our website, platform, and dashboard. Located in the United States.
- →Cloudflare, Inc. — Encrypted tunnels for Connect-Anywhere, the Relay network that carries live sessions, and DNS for Broadcasteer addresses. Traffic passes through; it is not stored. And only if you switch on Stream Cloud: R2 storage for your recordings.
- →Stripe, Inc. — Subscription and one-time payments. Holds your card data under its own privacy policy; we never see it.
- →Google Firebase — Account records, subscription status, device registrations, connected-platform tokens, crash reports, Relay usage totals, and demo requests.
- →Meta Platforms (Facebook) — Only if you connect Facebook: we keep its access token to go live on the Page you pick.
- →Twitch Interactive — Only if you connect Twitch: we keep its access token to stream to your channel.
- →WhatsApp (Meta Platforms) — Only if you message us on WhatsApp, or send a demo request through it. That message travels under WhatsApp’s own privacy policy and reaches us on our phone.
We do not sell your data, and we do not share it with anyone beyond the providers above except where the law requires it.
Gladia and ElevenLabs are not our providers. LiveCaptions and Language Rooms use your own accounts with them: the keys stay encrypted on your PC, and the sermon audio goes from your PC to them under their own privacy policies, never through Broadcasteer.
If You Are Outside Malaysia
Broadcasteer is operated from Malaysia and governed by the PDPA 2010. Our providers are largely United States companies, so your account data is processed outside Malaysia. Relay traffic is routed through whichever Cloudflare location is nearest to your session, which may be in another country.
If your church is in the United Kingdom or the European Economic Area, the UK GDPR or EU GDPR also applies to you. In that case: your church is the controller for anything you broadcast and we are your processor; our lawful basis for the account data we hold is performance of our contract with you; and you have the rights of access, rectification, erasure, restriction, portability, and objection. Write to info@broadcasteer.com to exercise any of them, or if you need a data processing agreement in place.
Cookies
We use session cookies to keep you logged in. We do not use analytics cookies, advertising cookies, or any third-party tracking. You cannot disable session cookies and remain logged in, but you may log out at any time to clear your session.
Changes to This Policy
If we update this policy, we will revise the effective date at the top of this page. Material changes will be communicated by email. Continued use of Broadcasteer after any update constitutes acceptance of the revised policy.
Contact
Broadcasteer — a product by Abelitie Designs
Email: info@broadcasteer.com
Ipoh, Perak, Malaysia
For complaints, you may also contact the Department of Personal Data Protection Malaysia (JPDP) at www.pdp.gov.my.