We don't collectwhat we don't need.

Effective: 19 September 2026 · Broadcasteer by Abelitie Designs · Governed by PDPA 2010 (Malaysia)

The Short Version

We collect your name and email address from your Google account — that's it. Authentication is handled entirely by Google OAuth; Broadcasteer never sees or stores a password. 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.

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.
✓Device identifiers — A count of devices registered to your account, used to enforce your plan's seat limit.
✓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, Windows version, hardware model, and the error's technical trace, linked to your account so we can help. Never your lyrics, media, plans, or messages. Deleted with your account.
✓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.

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
✗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).
→Withdraw consent — You may close your account at any time to withdraw consent for data processing.

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.

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. The one exception is a recording you choose to keep, 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 is removed by our daily sweep. 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.

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. Provides your name and email address; never a password.
→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.
→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, and Relay usage totals.

We do not sell your data, and we do not share it with anyone beyond the providers above except where the law requires it.

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.