Privacy Policy
How EDR APPS / EDR Broadcast handles information.
Last updated: 24 June 2026
This Privacy Policy explains how EDR APPS / EDR Broadcast handles information for the website, desktop app, accounts, licensing, subscriptions, remote sessions, public live timing and support.
1. Who we are
EDR APPS / EDR Broadcast is operated by M.C HALDEN & C.D WILSON, a partnership registered in Australia under ABN 52 315 882 514.
In this policy, EDR APPS, EDR Broadcast, we, us and our refer to that partnership and the EDR Broadcast products and services.
Contact: apps@endurotechracing.com.
2. What this policy covers
This policy applies to the EDR Broadcast website, desktop application, account system, subscriptions, licensing, remote browser control, public live timing, support services and related online features.
3. Information we collect
Account information
We may collect account information such as your name, email address, username, authentication details, account settings, plan, trial status and subscription status.
Subscription and billing information
Payments and subscriptions are processed through Stripe. We may receive and store payment-related records such as subscription status, plan, renewal date, invoice records and billing status. We do not intend to store full payment card numbers on our own systems.
Device, app and licence information
EDR Broadcast uses a hashed device identifier to manage licensing, PC limits and activations. Raw hardware details are not stored by EDR servers. We may also process app version, operating system, licence status, activation records and related support/security information.
Hashed IP-derived identifiers
We may use hashed IP-derived identifiers for rate limiting, abuse prevention, guest/session security and related service protection. Raw IP addresses are not stored by EDR servers for these purposes based on the current product design.
Race, session, incident and timing data
EDR Broadcast reads iRacing data to provide overlays, camera control, live timing, replay cues and incident features. This may include driver names or handles, team names, car numbers, classes, positions, gaps, lap times, sector times, timing data, incident markers and related session information.
When remote-session features or public live timing are used, EDR Broadcast sends the race/session information needed to operate those live features to EDR servers. Race/session data and public live-timing data sent to EDR servers are wiped after the remote session is closed or expires.
Remote control rooms
Remote browser control lets authorised operators control parts of a broadcast from a browser. Remote rooms use access controls such as invite or secret-link access, optional invite-only approval, role permissions, host revoke/kick controls, entitlement checks, rate limiting and session expiry/closure controls.
Operator control actions, such as camera changes or replay triggers, are not persisted server-side based on the current product design.
Incident logs
Incident logs are stored locally only, except that current incident/timing information may be displayed to connected remote viewers/controllers while a live remote or public timing session is active. EDR APPS does not retain server-side incident logs after the session closes or expires.
Support and diagnostics
If you contact us for help, we may collect your name, email address, account details, plan, app version, device information, screenshots, logs, diagnostic files and messages you send to us.
EDR Broadcast does not currently use third-party crash reporting and does not automatically upload crash/error reports from the desktop app. Error logs and diagnostic bundles are stored locally on your device unless you choose to send them to us for support.
Website, cookies, embeds and analytics
We use Google Analytics to understand website usage and Google Search Console to understand search performance. We do not currently use advertising or marketing pixels. Our website may include a Twitch video embed and a Discord invite link.
Google Analytics and embedded third-party content may use cookies or similar technologies. See our Cookie Policy for more detail.
Emails
We use Brevo to send trial-related emails. We may add other service emails such as account, billing, security, support, trial, subscription or product update emails as the service develops.
4. How we use information
- to create and manage accounts;
- to provide trials, subscriptions, licensing and plan access;
- to operate EDR Broadcast features, including remote control and public live timing;
- to process payments, invoices, cancellations and refunds;
- to enforce device, PC and operator limits;
- to provide support and respond to enquiries;
- to send trial-related and service emails;
- to diagnose bugs, security issues and misuse;
- to improve the app and website;
- to comply with legal, tax, accounting and regulatory obligations.
5. How we share information
We may share information with service providers that help us operate EDR Broadcast, including Stripe, Supabase, SiteHost, Google Analytics, Google Search Console, Brevo, website hosting, email/support providers, professional advisers, regulators, courts or law enforcement where required.
We do not sell personal information.
6. Third-party services
EDR Broadcast may interact with or depend on third-party services including iRacing, OBS, Stripe, Supabase, SiteHost, Google Analytics, Google Search Console, Brevo, Twitch, Discord, social platforms and streaming platforms. Third-party services have their own terms and privacy policies.
7. International processing
Our providers may store or process information in Australia, New Zealand, the United States, the European Union, the United Kingdom or other locations where our service providers operate.
8. Retention
| Information type | Retention position |
|---|---|
| Race/session data sent for remote sessions | Wiped after the remote session is closed or expires. |
| EDR-hosted public live-timing data | Wiped after the remote session is closed or expires. |
| Non-timing room/session metadata | Retained for up to 90 days after closure or expiry for operations, abuse prevention and support. |
| Incident logs | Local only, except for live display during an active remote/public timing session. |
| Operator control actions | Not persisted server-side based on the current product design. |
| Account data | Deleted within 7 days of a verified deletion request, except for records we are legally required or reasonably entitled to retain. |
| Billing/invoice records | Retained where required for tax, accounting, dispute resolution and legal compliance. |
9. Account deletion and access requests
You may request access to, correction of, export of or deletion of personal information by emailing apps@endurotechracing.com from the email address linked to your EDR Broadcast account.
We aim to complete verified deletion requests within 7 days. Account and service data will be deleted from active systems, except for records we are legally required or reasonably entitled to retain, such as billing, tax, accounting, fraud prevention, security, legal compliance or dispute records.
Account deletion does not automatically cancel billing. If you have an active paid subscription, you must also cancel it through the Stripe billing portal or contact us for help.
10. iRacing non-affiliation
EDR Broadcast is an independent tool and is not endorsed by, sponsored by, approved by or affiliated with iRacing.com Motorsport Simulations, LLC. iRacing and related names, logos and data remain the property of their respective owners.
11. Contact
Email: apps@endurotechracing.com
Location: QLD 4226, Australia.