Privacy Policy

Effective September 29, 2026

TuneSpoke is provided by Alakor Inc. This policy explains how information is handled when you use TuneSpoke and contact us for support.

Audio playback and your saved setup

TuneSpoke receives audio over your local network and plays it through the audio output you select on your Mac. Your saved receiver configuration includes the receiver name, selected output and playback settings. These settings are stored on your Mac.

The sender and any music or streaming service you use have their own privacy practices. This policy describes TuneSpoke, not those services.

Analytics and crash diagnostics

TuneSpoke uses Google Firebase Analytics and Firebase Crashlytics to help us understand playback reliability, investigate failures and improve the app. Cloud reporting is enabled when the app's Firebase configuration is available. It is separate from the optional local debug-logging setting.

Information handled for these purposes includes:

• App version, operating-system and device information, and identifiers used by Firebase to distinguish app installations or devices.
• Pseudonymous receiver, playback-session, group and incident references. A receiver reference can connect diagnostic events across sessions, including after a receiver is renamed.
• Audio connection and format details, such as connection type, protocol, sample rate, channel count and supported sender/output characteristics.
• Playback measurements, startup and recovery timing, error categories and recovery results.
• Crash reports and diagnostic breadcrumbs. A receiver helper's unexpected exit can also be reported as a diagnostic event.

TuneSpoke's custom cloud-event schema excludes user-assigned speaker names, network addresses, music metadata and raw troubleshooting logs. These exclusions describe the app's custom events; Firebase also processes information needed to provide its services. Pseudonymous identifiers are not the same as anonymous data.

Google processes information through the Firebase services described above. For more information about Firebase's data handling, see Privacy and Security in Firebase.

Local troubleshooting logs and support

If you enable debug logging, TuneSpoke stores troubleshooting logs on your Mac. Those logs may include device names and connection details. When logging is enabled, the app can attach collected logs to a support email. You can also save logs and send them yourself.

When you contact support, we receive the information you choose to send, including your email address, message and any attachments. We use it to respond and investigate the issue. Review messages and attachments before sending them, and avoid including information that is unnecessary for support.

Turning off local debug logging does not turn off Firebase Analytics or Crashlytics reporting.

Website and support form

The TuneSpoke website is hosted by Cloudflare. Cloudflare processes network and technical information to deliver the site and provide security services. The support form uses Cloudflare Turnstile to help distinguish legitimate requests from automated abuse.

We use Cloudflare Web Analytics to understand website traffic and page performance. It collects page-view and referring-site information, browser and device characteristics, and performance measurements. Cloudflare Web Analytics does not use cookies or browser local storage to collect these usage metrics, and Cloudflare states that it does not fingerprint visitors for this purpose. See Cloudflare Web Analytics for details. This website analytics is separate from the app diagnostics described above.

When you submit the form, your name (if provided), email address, subject, and message are sent through our Cloudflare-hosted handler to the support mailbox hosted by Forward Email. The handler does not maintain a separate support-ticket database. You can also email support@tunespoke.com directly.

Service providers and disclosure

Google Firebase processes app analytics and crash-diagnostic information. Cloudflare processes website requests, website analytics and support-form submissions. Forward Email processes and stores support correspondence.

Retention

Detailed analytics: Our policy is a two-month retention period for detailed user-level and event-level data in Google Analytics, without resetting user-data retention when new activity occurs. Google deletes expired data during its regular deletion cycle. Standard aggregated reports are not subject to this setting and may remain available longer.

Crash diagnostics: Firebase Crashlytics retains crash reports and associated identifiers for 90 days before beginning their removal from live and backup systems. This does not mean that every copy is removed immediately on the ninetieth day.

Support correspondence: We retain support messages and attachments for 12 months after the last message in the conversation. If an issue remains unresolved or information must be retained to meet a legal obligation, we keep only the information needed for that purpose and delete it when the exception no longer applies.

Local receiver settings and logs remain on your Mac until removed through the app, operating system or other local file management. Logs may also be removed through the app’s log rotation.

Questions and privacy requests

Contact support@tunespoke.com with privacy questions or to request deletion of personal information associated with your support correspondence or app use. We may ask for information reasonably needed to verify your request and locate the relevant records.

Diagnostic records use installation and other pseudonymous identifiers rather than your email address. An email address alone may not allow us to identify a particular diagnostic record, and we will explain any resulting limitation.

We delete identifiable personal information in response to a valid request unless its retention is required or otherwise permitted by applicable law. Copies held in service-provider backups are removed according to those providers' retention and deletion processes.

Changes to this policy

We will publish updates on this page and change the effective date when this policy changes.