Publication draft — not yet effective. Last reviewed: 11 November 2026.
Privacy at a glance
espurr is a free companion for programmable Bluetooth cat ears, published by Andromeda Powers-Holmes in Melbourne, Australia. This policy covers the espurr apps, their widgets and this website. “We” and “us” mean the publisher and people handling espurr support.
- Accessory control, settings and sensor processing work locally. You do not need an espurr account.
- App analytics and crash reporting are optional and off until you allow them.
- You choose whether to send support messages, share files or publish an issue.
- We do not sell your personal information or use it for advertising.
Questions or privacy requests: espurr-support@neggles.dev.
1. Information on your devices
The apps use Bluetooth identifiers, connection information, accessory settings and diagnostics to find and control your ears. Your phone, paired Watch and accessory exchange the information needed for those features. Settings, sensor readings, recordings and local troubleshooting history stay on your devices unless you choose to export or share them.
Audio-reactive effects use microphones on the ears, which can remain active while an effect runs even when the phone app is closed. On supported hardware, you can request and save a short recording. Recordings can contain voices or other personal information; they are not automatically uploaded or attached to support reports.
You can clear local diagnostics and remove saved accessory settings. Files you export and operating-system backups are managed separately.
2. Optional analytics and crash reports
With your permission, the Android, iPhone/iPad and Mac Catalyst apps use Google Analytics for Firebase and Firebase Crashlytics to understand app use and diagnose failures. Watch apps and widgets do not use these services.
Reports can include:
- App activity, such as app opens, sessions, connection results and firmware-update results.
- Crash details, error information and relevant app or system state.
- App version, device model, operating system, language and event times.
- Generated installation identifiers that relate reports from the same installation. Google also receives network information, including your IP address, and can derive an approximate region.
We do not add your name, email address, accessory identifiers, credentials, recordings, raw sensor data or support messages to these reports. Reports are not guaranteed anonymous: installation identifiers link activity, and crash details can contain personal information.
You can decline without losing local accessory features, and change Share analytics and crash reports in Settings or Support. Turning it off stops future collection; it does not recall reports already sent or automatically delete data held by Google. Android closes the app when you turn sharing off; you can reopen it to continue.
See Firebase’s privacy information and Google’s privacy policy for how Google handles this information.
3. Support and information you share
If you email support, we receive your email address, any display name, message and attachments. We use them to respond, investigate problems and handle privacy requests. Support mail is stored in Google Workspace and may be copied to the people handling support. Private support correspondence is not automatically published.
The apps let you review and share technical support summaries. You can choose to include logs or other diagnostics. These can contain personal information, so check them before sending.
Opening a GitHub issue draft sends GitHub a short technical summary in the browser URL before you post; the app warns you first. Posting makes the issue and your GitHub account public. Closing an issue does not delete it. See GitHub’s privacy statement.
Saving or sharing a file sends it to the destination you choose. We do not receive a copy unless you send it to us.
4. Website visits and downloads
Cloudflare hosts this website, and GitHub serves firmware downloads. These providers receive information such as your IP address, requested URLs and browser or request details. They also process connection and error information to deliver content, protect their services and diagnose network problems. This processing is separate from the app’s optional analytics setting.
The website does not receive accessory data or app diagnostics. It has no advertising or site analytics. Following external links or using an email, file or app-store service is subject to that service’s privacy practices.
See Cloudflare’s privacy policy and GitHub’s privacy statement.
5. How we use and share information
We use the information described here to provide espurr’s features, respond to support and privacy requests, understand opted-in app usage and improve reliability. We use the service providers named in this policy for those purposes. They also process service and security records under their own terms.
We do not build advertising profiles or combine your support correspondence with analytics records to identify you. We may disclose information if required by law.
6. Storage and overseas processing
Local app data uses your devices’ storage and operating-system protections. The apps use encrypted connections for firmware downloads and Google telemetry. Support and service accounts are restricted to authorised access.
Google, Cloudflare and GitHub operate internationally. Information they receive can be processed outside Australia, including in the United States and other countries where they or their service providers operate. Their linked privacy information explains their practices.
7. Access, deletion and complaints
You can decline or turn off app analytics, clear local diagnostics and remove saved accessory settings. Deleting app data does not remove files you exported, messages you sent or public issues.
To request access to, correction of or deletion of personal information we hold, email espurr-support@neggles.dev. Include enough detail to find the relevant message or information. We may need to verify that it concerns you. Because analytics records are not linked to your contact details, we may be unable to identify a particular installation or report.
We handle requests manually and explain the outcome, including any legal retention requirements or limits affecting provider backups and copies outside our control.
You can use the same address to make a privacy complaint. We will review it and respond. You can also contact the relevant privacy regulator, including the Office of the Australian Information Commissioner where it has jurisdiction. This policy does not limit your rights under applicable law.
8. How long information is kept
Local settings and files remain until you or your operating system removes them; troubleshooting history can expire sooner. Delete exported copies separately.
Support messages and attachments are kept until manually deleted. You can request deletion at the support address.
Analytics, crash reports and hosting records follow the relevant provider’s retention and deletion practices. Different periods can apply to reports, aggregate statistics, operational records and backups. Turning off app analytics or deleting a local copy does not erase every provider-held copy.
9. Changes to this policy
We publish the current policy at espurr.neggles.dev/privacy. Released apps include a copy for that release. We review the policy when our information handling changes and update the date. Where a change needs your consent, updating this policy does not replace asking you.
Policy sources and reuse
The structure follows the OAIC’s Guide to developing an APP privacy policy, with approaches adapted from Automattic’s Privacy Policy. Neither organisation endorses espurr or this policy.
This policy text is licensed under Creative Commons Attribution-ShareAlike 4.0 International. That licence does not change the licences of espurr’s software, firmware, hardware or artwork.