Privacy Policy
Effective date: November 17, 2026. Version 3.3.
This policy says what personal data MiyaraHub Technologies LLC handles, why, who receives it, how long it is kept and what you can ask us to do. It covers every app listed in Appendix A, the Elan Audio Lab store, this website and email you send us. Appendix A gives the details for each app. If this page and an app's in-app text differ, write to us and we will correct the one that is wrong.
1. Summary
- Most of our apps control devices on your own network. The addresses, names and passwords of those devices stay on your phone or computer unless you send them to us yourself, for example in a diagnostic email, or unless your phone's own backup copies them.
- Most apps send crash reports to Google Firebase Crashlytics. In most apps this is on by default. Some apps have no switch to turn it off. The table below and Appendix A say which.
- Some apps send usage analytics to Google Firebase Analytics. Some ask first; some do not. The table below says which.
- Crash reports and analytics are linked to random identifiers created on your device, not to your name. They are still personal data under laws such as the GDPR, and we treat them that way.
- We do not sell personal data. We do not show ads in our apps.
- The Elan Audio Lab store handles customer accounts, orders and payments. It is described in its own block in Appendix A and in section 14.
| App | Crash reports | Usage analytics |
|---|---|---|
| Almanox | Off until you opt in | Firebase Analytics, off until you opt in |
| Elan Audio Lab | On by default in the apps | Firebase Analytics, on by default in the apps |
| UC Remote | Off until you opt in | Firebase Analytics, off until you opt in |
| UC-Remote Integration Hub | None | None |
| Syno Manager | Always on | None |
| UPSight | Always on | None |
| FuryPath | On by default | None |
| AVR Maestro | On by default, with a switch in About | Firebase Analytics, off until you opt in |
| AVR Maestro for Onkyo Pioneer | On by default | Firebase Analytics, on by default |
| AVR Maestro MC | Always on | None |
| Projector Pilot PJLink & VP21 | Always on | Firebase Analytics, off until you opt in |
| Projector Pilot D-ILA | On by default | Firebase Analytics, off until you opt in |
| NexusDeck | On by default | None |
| Network Deck | Always on | None |
"Always on" means the app has no switch that turns crash reporting off. "On by default" means it starts on and has a switch; Appendix A says where the switch is.
2. Who is responsible
The controller of your personal data is MiyaraHub Technologies LLC, a Texas limited liability company, 3704 Horseshoe Dr, Van Alstyne, Texas 75495, United States. Its managing member is Meir Miyara. Email: admin@miyarahub.com. Our legal notice has the full company details.
Meir Miyara is the person in charge of the protection of personal information, including for Quebec, and handles every privacy request. We have not appointed a data protection officer, because the law does not require one for a business of our size and type.
We have not appointed a representative in the European Union or the United Kingdom. You can contact us directly at the email address above, in any language.
3. What this policy covers
This policy covers our apps, the Elan Audio Lab store at elanaudiolab.com and its apps, the website miyarahub.com, and email you send us. It does not cover:
- Apple, Google and Microsoft when they sell you an app or handle your purchase. They act under their own privacy policies.
- Services you connect an app to yourself, such as Home Assistant, Hubitat, Synology QuickConnect, HEOS, your own web addresses for automation, or your device maker's cloud. They act under their own terms.
- Your phone's or computer's own backup, speech recognition and assistant features. They are run by the maker of your device.
4. The data we handle, by source
4.1 Email you send us
When you write to us, we receive your email address, your name if you give it, your message and any attachments. We use them to answer you.
4.2 Diagnostic reports you choose to send
Many apps have a button that prepares a diagnostic email or file. It opens your own email app or share sheet, and nothing is sent until you press send. Depending on the app, the report can contain your device model and system version, app settings, logs, and the network addresses, hardware (MAC) addresses, host names, model names and serial numbers of the devices you control. Some apps remove some of these first; many do not. Appendix A lists what each app includes. Read the report before you send it, and remove anything you do not want to share.
4.3 Crash reports (Firebase Crashlytics)
When an app crashes or hits a serious error, Crashlytics sends Google a report with the error and the code location, the app version, the device model, the system version, free memory and storage, a random Crashlytics installation identifier and a Firebase installation identifier. Google receives your IP address when the report is uploaded. In many apps, the error text can contain the network address or name of a device you control. Appendix A says, for each app, whether crash reports are on by default, where the switch is, and what is removed before sending.
4.4 Usage analytics (Firebase Analytics)
In the apps where it is active, Firebase Analytics sends Google events such as first open, session start, screen views, in-app purchases and the app events Appendix A lists. Each event carries a random app instance identifier, a Firebase installation identifier, the device model, system version, language, app version and an approximate location (country or region) that Google derives from your IP address. On iOS it can also use the vendor identifier. In apps where Appendix A says so, it also collects the Android Advertising ID. We use analytics to see which features are used and where apps fail. We do not use it to show ads.
4.5 Purchase and store reports
When you buy an app or an in-app upgrade, Apple, Google or Microsoft processes the payment. They send us sales reports with dates, countries, products, prices and order numbers. We do not receive your card details. Apps keep a record of your purchase on your device so they can unlock features; Appendix A says where.
4.6 The Elan Audio Lab store
The store handles accounts, orders, payments, shipping addresses, reviews, newsletter sign-ups, contact forms, quote requests, warranty registrations, giveaways and artist applications. See section 14 and the Elan Audio Lab block in Appendix A.
4.7 This website
GitHub Pages hosts miyarahub.com. GitHub receives your IP address and browser details when you load a page and keeps logs for security. Our fonts are served from miyarahub.com itself, so no font request goes to a third party. Our pages set no cookies and run no analytics. If you pick a language, your choice is saved in your browser's local storage under the key "lang" and never sent to us.
4.8 Data that stays on your device
Device addresses, settings, passwords and tokens you enter are stored on your device. We do not receive them unless you send them to us in a diagnostic report. Your device's own backup (iCloud, Google, or another backup tool) may copy them; Appendix A says which apps exclude what from backup.
5. Why we use data, and the legal basis
This section applies when the GDPR, the UK GDPR or the Swiss data protection law applies to you.
| Purpose | Data | Legal basis |
|---|---|---|
| Answering your email and support requests | Email, name, message, attachments, diagnostic reports | Our legitimate interest in helping you, or performing a contract when it concerns something you bought |
| Crash reports that are on by default | Crashlytics data in section 4.3 | Our legitimate interest in finding and fixing faults (see the balancing note below) |
| Crash reports and analytics you opted in to | Data in sections 4.3 and 4.4 | Your consent, which you can withdraw in the app at any time |
| Analytics that are on by default | Data in section 4.4 | Our legitimate interest in learning which features are used |
| Unlocking and restoring purchases | Purchase records | Performing our contract with you |
| Elan Audio Lab orders, payment, shipping and order email | Name, contact details, addresses, order details | Performing our contract with you |
| Tax and accounting records | Sales and order records | Our legal obligations |
| Newsletter and giveaway email | Email and name | Your consent |
| Reminders about items left in an Elan Audio Lab cart | Account email, cart contents | Our legitimate interest in completing sales |
| Publishing your product review | Name and review text | Your consent, given when you post |
| Keeping our systems and website secure, and defending legal claims | Logs, records of requests and correspondence | Our legitimate interest |
Balancing note. Where we rely on legitimate interests, we have weighed our interest against yours. Crash reports carry technical data and random identifiers, not names. We do not use them for ads or sell them, and Google keeps crash reports for 90 days. Error text can still contain a device address on your network, and some apps have no switch; Appendix A says which. You have the right to object at any time (section 9).
Where an app has a crash report switch, you can turn crash reports off there. We do not ask for consent before crash reports start in apps marked "On by default" or "Always on".
6. How long we keep data
| Data | How long |
|---|---|
| Email and diagnostic reports you send | We keep them while we work on your request and for later questions about it. There is no automatic deletion. Ask us and we will delete them, unless the law requires us to keep them. |
| Crash reports | 90 days in Firebase Crashlytics, then Google deletes them. |
| Analytics events | The retention setting of each of our Firebase projects has not yet been confirmed. Google offers 2 or 14 months for event-level data. Totals in reports can be kept longer. |
| Firebase installation identifiers | Until they are deleted. Google then removes them from its systems, which Google says takes up to 180 days. |
| Store sales reports | As long as tax and accounting law requires. |
| Elan Audio Lab order records | As long as tax and accounting law requires. |
| Other Elan Audio Lab records (contact forms, quotes, giveaway entries, newsletter, warranty, applications, reviews) | There is no automatic deletion. Ask us and we will delete them, unless the law requires us to keep them. Backup copies can keep deleted data for a period that has not yet been measured. |
| Data on your device | Until you delete it or uninstall the app. Appendix A lists what can survive an uninstall or be copied by backup. |
| Website logs at GitHub | As set by GitHub. |
7. Who receives data
We do not sell personal data. These companies receive it in the course of running our apps and store:
| Recipient | What for | Role |
|---|---|---|
| Google LLC (Firebase Crashlytics, Firebase Analytics, Firebase Cloud Messaging) | Crash reports, analytics, Elan Audio Lab app notifications | Our processor under the Firebase data processing terms |
| Apple, Google Play and Microsoft Store | Selling apps and upgrades, payment, refunds | Independent controllers |
| GitHub, Inc. | Hosting this website | Under GitHub's own terms and privacy statement |
| Our email provider | Receiving and storing email you send us | Processor |
| Supabase | Elan Audio Lab accounts, orders, forms and reviews | Processor |
| Square (including Afterpay) and PayPal | Elan Audio Lab payments | Independent controllers for payment data |
| United States Postal Service | Checking Elan Audio Lab shipping addresses | Independent |
| MochaHost | Elan Audio Lab email sending and file hosting | Processor |
| Google Analytics, Meta and Tawk.to | Elan Audio Lab website analytics, advertising measurement and live chat, only when switched on in the store's settings | See section 14 |
| Other services an app contacts | Weather, maps, update checks and similar; listed per app in Appendix A | Independent |
We may also disclose personal data when the law requires it, to protect our rights or someone's safety, or to a buyer of our business, who would be bound by this policy.
8. International transfers
We are based in the United States, and our providers process data in the United States and other countries. When you send data to us directly, the GDPR or UK GDPR still applies to how we handle it. Google LLC is certified under the EU-U.S. Data Privacy Framework, its UK Extension and the Swiss-U.S. Data Privacy Framework, and Google's data processing terms for Firebase also include the European Commission's Standard Contractual Clauses. For other providers, we rely on the safeguards in their own terms. You can ask us for details of the safeguard that covers a transfer.
9. Your rights
9.1 Everyone
Wherever you live, you can ask us to tell you what personal data we hold about you, to correct it, to delete it, or to stop using it. Email admin@miyarahub.com. We answer within 30 days. We may ask you to confirm your identity, for example by replying from the same email address or giving an order number. We will not treat you differently for asking.
Crash report and analytics data is linked to random identifiers, not to your name, so we may need your help to find it, such as the app, the device and the approximate dates. Turning off the switch in the app stops new data. Uninstalling the app stops all collection by that app.
9.2 European Economic Area, United Kingdom and Switzerland
You have the right to access, correct and delete your data, to restrict its use, to receive it in a portable format, to object to our use based on legitimate interests, to object at any time to direct marketing, and to withdraw consent at any time without affecting earlier use. We do not make decisions about you by automated means alone. We answer within one month; for complex requests we may extend this by up to two more months and will tell you why. You can complain to the data protection authority where you live or work, to the UK Information Commissioner's Office, or to the Swiss Federal Data Protection and Information Commissioner.
9.3 California
In the last 12 months we have handled these categories of personal information: identifiers (email address, name, random device identifiers, IP address and, for UC Remote and the Elan Audio Lab apps, the Android Advertising ID); commercial information (purchases and Elan Audio Lab orders); internet or other electronic network activity (app events and crash reports); geolocation (approximate location from IP address, and in Almanox the location you choose, which is sent to weather services); and customer records (Elan Audio Lab addresses and phone numbers). The sources, purposes and recipients are in sections 4 and 7.
We do not sell personal information. We do not share it for cross-context behavioral advertising, except that the Elan Audio Lab website loads the Meta Pixel when it is switched on in the store's settings (section 14). We do not use sensitive personal information to infer characteristics about you. Under the California Consumer Privacy Act you can ask to know, delete and correct personal information, and to opt out of sale or sharing. You can use an authorized agent; we may ask the agent for your signed permission. We do not offer financial incentives for personal information.
Under California's Shine the Light law, you can ask whether we disclosed personal information to third parties for their direct marketing. We have not.
9.4 Texas
We do not sell sensitive personal data. You can ask us to confirm, access, correct and delete your personal data and to get a copy. If we refuse your request, you can appeal by replying to our answer with the word "Appeal". We will answer the appeal within 60 days and explain our decision. If you disagree, you can contact the Texas Attorney General at texasattorneygeneral.gov.
9.5 Other US states
If you live in another US state with a privacy law, you can make the same requests as in section 9.1 and appeal a refusal as in section 9.4. We answer within the time your state's law sets, and never later than 45 days.
9.6 Canada, Brazil, Japan and other countries
You can ask for access to and correction of your personal data and withdraw consent, as your local law allows. In Canada you can complain to the Office of the Privacy Commissioner of Canada, or in Quebec to the Commission d'acces a l'information. In Brazil you can complain to the ANPD.
10. Children
Our apps and store are not directed to children under 13, and we do not knowingly collect personal data from them. If you are under 16 in the European Economic Area or the United Kingdom, or under the age your country sets, ask a parent before you turn on analytics or crash reports that ask for consent. Elan Audio Lab giveaways are for people aged 18 and over. If you believe a child has sent us personal data, email us and we will delete it.
11. Security and breaches
Data sent to Firebase, the Elan Audio Lab store and its payment providers travels over encrypted connections. Several apps store passwords in the system's secure storage. Some do not; Appendix A says which. Many devices you control, such as AV receivers, projectors and UPS units, use network protocols without encryption, so other devices on your network may be able to read that traffic. No method is completely secure.
If a breach of personal data affects you, we will tell you and the authorities as the law requires, including within 72 hours to the supervisory authority under the GDPR when it applies, and within 60 days to affected Texas residents, with notice to the Texas Attorney General within 30 days when 250 or more Texans are affected.
12. Cookies and similar technologies
miyarahub.com sets no cookies and runs no analytics or advertising code. It uses your browser's local storage only to remember the language you picked. The Elan Audio Lab website uses cookies and similar technologies; see section 14.
13. Do Not Track and Global Privacy Control
miyarahub.com does not track you, so it has nothing to change when your browser sends a Do Not Track or Global Privacy Control signal. Our apps do not read these browser signals. The Elan Audio Lab website does not respond to Do Not Track or Global Privacy Control signals.
14. Elan Audio Lab store
The Elan Audio Lab store at elanaudiolab.com and its Android and iOS apps are run by MiyaraHub Technologies LLC. When you create an account, place an order, or fill in a form, we store what you enter: name, email, phone, shipping and billing addresses, order details and notes. A guest checkout creates a guest sign-in on your device so the order can be tracked. Payments go through Square (including Afterpay) or PayPal; card details are entered in their own forms and do not reach our database. Shipping addresses can be checked with the United States Postal Service. Order and account email is sent through our mail server at MochaHost.
Product reviews are published right away under the name you give. Files you upload with an artist application are stored at public web addresses that anyone with the link can open.
The newsletter uses double opt-in, and every newsletter has an unsubscribe link. Signed-in customers who leave items in their cart can receive a reminder email. Entering a giveaway requires agreeing to receive promotional email.
The website can load Google Analytics, the Meta Pixel and Tawk.to live chat when they are switched on in the store's settings. When loaded, they set their own cookies and send your IP address, browser details and the pages you visit to Google, Meta and Tawk.to. Embedded YouTube videos set YouTube cookies. PayPal and Square set cookies during checkout. The cookie banner currently offers only an Accept button and describes essential cookies only; these services can load before you press it.
You can delete your account in the app. This removes your profile and clears names and addresses from your past orders. Some records keyed to your email address, and backup copies, are not removed by this; email us to delete them. There is no self-service download of your data; email us for a copy.
15. Changes to this policy
When we change this policy, we update the effective date and add an entry below. If a change affects how we use data you already gave us, we will tell you in the app or by email where we can.
- Version 3.3, November 17, 2026: the AVR Maestro block in Appendix A describes version 5.8.0: analytics are opt-in, crash reports have a visible switch and mask receiver addresses, tokens are in secure storage, Android no longer backs the app up, and a new action erases all app data.
- Version 3.2, November 15, 2026: section 2 gives our full postal address.
- Version 3.1, November 15, 2026: the website serves its fonts from miyarahub.com itself, so Google no longer receives your IP address when you load a page.
- Version 3.0, November 15, 2026: rewritten from a code audit of every app. Adds the legal bases, the retention table, the recipients, transfers, rights by region, the Elan Audio Lab store section and one block per app in Appendix A.
- Earlier versions: last updated September 23, 2026.
16. Contact
MiyaraHub Technologies LLC, Van Alstyne, Texas, United States. Email: admin@miyarahub.com. For privacy requests, put "Privacy" in the subject.
Appendix A: app by app
Each block below uses the same fields in the same order. The facts come from a review of each app's code on November 15, 2026.
Almanox
- Name and platforms
- Almanox, a sky and astronomy planner for Android and iOS. Not yet released.
- Data model
- Your locations, photos and settings are stored on your device. The app fetches weather, maps, terrain, satellite and aurora data from public services on the internet. There is no Almanox account and no MiyaraHub server.
- Network destinations
- MET Norway (api.met.no) receives the latitude and longitude of the active location rounded to about 11 meters, automatically and about every 3 hours. Open-Meteo receives the text of a place search. The Apple or Google geocoder receives exact coordinates or address text when a place is named. OpenStreetMap (map tiles), Amazon Web Services (terrain tiles about 39 km wide), CelesTrak (ISS data, nothing sent) and NOAA (aurora forecast, nothing sent) are also contacted, and Firebase only after you opt in.
- Crash reports
- Default: off. Switch: the consent prompt and Settings, one switch for both crash reports and analytics; turning it off deletes unsent reports. What is sent: the error message and stack, plus a Firebase installation ID, device model, OS version and app version, and Google sees your IP address. Redaction: not confirmed; the audit found no custom keys or user ID added to reports.
- Analytics
- Off until you opt in. The same switch in the consent prompt and in Settings controls it. Identifiers: app instance ID and Firebase installation ID; whether the Android Advertising ID is collected has not been confirmed. Events: app_open, screen_view and the automatic Firebase events.
- Permissions
- Android: internet, camera (sky finder), precise and approximate location (sky calculations), notifications (sky event alerts) and start at boot (to reschedule alerts and widgets). iOS: camera, photo library, location when in use and calendars. There is no background location.
- Purchases
- One optional one-time purchase, Almanox Pro, through the App Store or Google Play. The unlock is cached on your device.
- Local storage and uninstall
- Saved locations, the active location, settings, place photos, a map tile cache and a forecast cache are stored on your device. Android backup is turned off. On iOS this data is included in iCloud and device backups. Calendar events you add and files you save survive uninstall, and there is no single delete-all action.
- Egress to services you choose
- Opening a dark-sky site in Google Maps sends its coordinates to Google. A backup file you export contains all saved locations and goes wherever you share it.
- Support email contents
- The "Send all relevant files" action emails a ZIP to admin@miyarahub.com through your mail app. It always includes the active location name with latitude and longitude to about 1 meter, and a list of app preferences that contains all saved locations. There is no option to leave a part out.
- Known limits
- Location leaves the device to MET Norway, the platform geocoder and the map and terrain tile hosts. The support ZIP always carries your locations. iOS backups include saved locations and photos.
Elan Audio Lab
- Name and platforms
- Elan Audio Lab, the web store at elanaudiolab.com and the same store as an Android and iOS app. The app is released on the App Store and live on Google Play.
- Data model
- Accounts, orders, forms, reviews and sign-ups are stored in a Supabase database. You can create an account with email and password or check out as a guest. Guest checkout creates a guest sign-in with its own session ID that persists.
- Network destinations
- Supabase (database and sign-in), Square including Afterpay, PayPal, the USPS address check, MochaHost (outgoing email and file hosting), ExchangeRate-API (called from your browser), YouTube embeds and jsDelivr. Google Analytics 4, Meta Pixel and Tawk.to live chat are loaded when they are switched on in the store's settings, and whether they are on in production is not confirmed. When they are on, they load without waiting for the cookie banner.
- Crash reports
- Default: on in the Android and iOS apps; the web store has none. Switch: only in a hidden developer menu. What is sent: the crash stack, device model, OS version and a Crashlytics installation ID, and Google sees your IP address. Redaction: none described.
- Analytics
- On by default. In the Android and iOS apps there is no switch, and no code that turns Firebase Analytics off was found. Identifiers: app instance ID, Firebase installation ID and Advertising ID, because the Android app declares AD_ID. Events: the automatic Firebase events such as first_open and session_start; if Google Analytics 4 or Meta Pixel is switched on, the web store also sends page views.
- Permissions
- Android: internet, network state, notifications and Advertising ID. iOS: photo library, to upload product images and profile pictures. The app also fetches a push notification token.
- Purchases
- Card payments go to Square, including Afterpay, and PayPal payments go to PayPal. Square receives a card token, the amount, your email, and your billing name, email, phone and address; PayPal receives the amount, item names and prices, the order ID and your email. Card numbers do not reach Elan Audio Lab servers and are not stored; the payment ID and receipt link are kept with the order.
- Local storage and uninstall
- Your browser or device keeps the cookie choice, accessibility and theme settings, a guest cart, sign-in tokens and a payment idempotency token. If the payment window is blocked, the amount, email, billing address and order ID are kept briefly and removed when read. Uninstalling the app does not remove data in the store database. Account deletion removes your profile, cart, saved designs and reminders, and blanks names, addresses and notes on your orders; it does not remove email-keyed records (newsletter, contact messages, quotes, warranty, waitlist, quiz, giveaway entries, gift cards, names on reviews, Do Not Sell requests), backup files, or data held by Square, PayPal, Tawk.to, Google or Meta.
- Egress to services you choose
- The newsletter uses double opt-in, and each campaign has an unsubscribe link. Signed-in users with items left in the cart get an abandoned-cart reminder email after 24 hours. Giveaway entry requires agreeing to receive promotional email, and the rules say entrants must be 18 or older. Reviews are published straight away under the name you give, and files sent with an artist application are stored at public web addresses on MochaHost.
- Support email contents
- The contact form stores your name, email, phone and message in the store database. No diagnostic log email feature was found.
- Known limits
- The cookie banner offers only Accept and names essential cookies only. There is no self-service data export, so access requests are handled by email. There is no age check at sign-up or checkout. Database backups contain all customer records, and abandoned-cart reminders have no unsubscribe link.
UC Remote
- Name and platforms
- UC Remote, a controller for Unfolded Circle remotes, for Android. Live on Google Play.
- Data model
- The app talks to your Unfolded Circle remote on your local network. There is no account and no MiyaraHub server. Crash reports and analytics go to Google Firebase only if you allow them.
- Network destinations
- Your remote on the local network, including Wake-on-LAN. Album art and icons are loaded from whatever web address the remote reports, often a streaming service's image server, which then sees your IP address; Settings > Media Settings > Load artwork from the internet turns this off and keeps every image request on your local network. When you install an integration from a web address, the server at that address sees your IP address. Google Firebase only if you allow it, Google Play billing and review, and links you tap. The app refuses to send your remote's credentials over plain HTTP to an address outside your local network. Over HTTPS it trusts only the system's certificate authorities and, from version 4.1.0, a certificate you approved for that remote; version 4.0.0 accepted the remote's certificate without checking it.
- Crash reports
- Default: off until you opt in. The app asks once at first launch (Allow or Don't allow) and sends nothing before you answer. Switch: Settings > Privacy > Share crash reports and usage statistics; one answer covers crash reports and analytics. Saying no deletes reports not yet sent. What is sent: the error type, the redacted error message and the stack trace, the app version and version code, a Crashlytics installation ID, device model and OS version, and Google sees your IP address. Redaction: before upload, IP and MAC addresses, web addresses, .local names, tokens, passwords, PINs and entity or media names in structured data are masked. Names written in plain sentences can remain.
- Analytics
- Off until you opt in. The same answer as crash reports controls it, at first launch and in Settings > Privacy. Saying no resets the analytics data on the phone. Identifiers: app instance ID and Firebase installation ID; the Advertising ID is not collected, because the app removes the Advertising ID permissions and turns ad ID collection off. Events: only the automatic Firebase events, such as first_open, session_start, user_engagement, screen_view, app_update, os_update and in-app purchase events.
- Permissions
- Internet, network and Wi-Fi state, change Wi-Fi state, nearby Wi-Fi devices and approximate location (to discover remotes), wake lock, vibrate, a foreground media playback service, run scheduled work after a restart (home screen widgets), Google Play billing, and the Play install referrer, which Firebase Analytics reads only after you allow it. Biometric unlock is optional. No microphone, camera or contacts.
- Purchases
- Optional support tips in three sizes through Google Play. They are consumed after purchase and unlock nothing.
- Local storage and uninstall
- Remotes (name, host, port, API token, user name, password, MAC address) and the certificates you trusted are kept in encrypted storage. Settings, theme, weather choices, widget data, custom icons and caches are kept in normal app storage. Android backup leaves out remotes and their credentials, app lock, trusted certificates, your crash report and analytics answer, weather choices, widget data, safety backups and custom icons; general settings, theme, navigation tabs and button preferences are backed up. Settings > Privacy > Delete all my data erases everything the app keeps on the phone after two confirmations; tokens registered on your remote stay there until you remove them on the remote. Uninstall removes app data except what Android backup keeps.
- Egress to services you choose
- Export Configuration and Backup create a file and open the share sheet. The file holds remote names, addresses, ports and MAC addresses, settings and custom icons, but no API token, user name or password.
- Support email contents
- The app has no built-in email to MiyaraHub. Developer Options can share a log file through the share sheet. IP and MAC addresses, web addresses, .local names, tokens, passwords and entity names in structured data are masked; names written in plain sentences can remain, and the app warns before sharing.
- Known limits
- Crash reports and shared logs can still contain names written in plain sentences. On your local network the remote is reached over plain HTTP unless you set it to HTTPS. General settings are copied by Android backup.
UC-Remote Integration Hub
- Name and platforms
- UC-Remote Integration Hub, a set of drivers (CCTV, HDFury, HEOS, MusicCast, Yamaha AVR) that run on an Unfolded Circle remote or in Docker. Store availability is not confirmed in this policy.
- Data model
- Each driver runs on your remote and talks to your devices on your local network. Settings are kept in the driver configuration on the remote.
- Network destinations
- Your devices on the local network. The HEOS driver signs in to your Denon or Marantz HEOS account through your HEOS device, so that credential is used with Denon's cloud service. No other internet service is contacted by the drivers.
- Crash reports
- Default: none sent. Switch: none. What is sent: nothing; the drivers contain no Firebase or other crash reporting. Redaction: not applicable.
- Analytics
- Sends no analytics. No analytics or telemetry code was found in any of the five drivers.
- Permissions
- The drivers run on the remote and do not request phone permissions.
- Purchases
- No purchase flow is described for the drivers.
- Local storage and uninstall
- The CCTV driver stores camera user names and passwords, and the HEOS driver stores your HEOS account user name and password, in the driver configuration on the remote. Removing the driver from the remote is the way to remove them.
- Egress to services you choose
- HEOS account sign-in through your HEOS device to Denon's cloud service, if you set up the HEOS driver.
- Support email contents
- No support email feature was found in the drivers.
- Known limits
- This description is based on local copies of the drivers dated 2026-11-02, not the published versions. Driver configuration stores camera and HEOS passwords.
Syno Manager
- Name and platforms
- Syno Manager, a Synology NAS manager for Android, iOS, macOS and Windows. Released on the App Store, live on Google Play and live on the Microsoft Store. It is a paid download with no in-app purchases.
- Data model
- The app talks to your Synology NAS directly or through Synology QuickConnect. There is no account and no MiyaraHub server. Crash reports go to Google Firebase on Android and iOS only.
- Network destinations
- Your NAS on the local network, or your DDNS or WAN address if you set one. If you use QuickConnect, your QuickConnect ID goes to Synology (global.quickconnect.to), and the app may connect through a Synology relay, so your NAS sign-in and traffic, encrypted to the NAS, pass through Synology servers. Google Firebase, the app stores, and links you tap.
- Crash reports
- Default: on. Switch: only in a hidden developer menu, and crash reporting is turned back on at every launch, so turning it off does not last. What is sent: the error message and stack, an "App started" note, a Crashlytics installation ID, device model and OS version, and Google sees your IP address. Redaction: none on the crash path; error text can include your NAS IP address, host name or QuickConnect host.
- Analytics
- Sends no analytics. There is no analytics library and no switch. Whether the Android build declares the Advertising ID permission has not been confirmed, and no code uses it.
- Permissions
- Android: internet, microphone (assistant voice) and biometrics (app lock). iOS: local network, Face ID, microphone, speech recognition and photo library (to pick a file to upload). Speech recognition runs on the device only and the mic stops working rather than using a cloud service.
- Purchases
- Paid upfront through the store. The app has no in-app purchases, and MiyaraHub receives no payment data.
- Local storage and uninstall
- NAS addresses, user names, passwords, 2-step trust tokens and session tokens are kept in secure storage. Settings and home-screen widget data (NAS name, CPU, memory, temperature, health) are in normal app storage, which Android backup includes. On iOS, Keychain items survive uninstall and come back on reinstall. There is no single delete-all action; deleting a NAS removes its credentials.
- Egress to services you choose
- Synology QuickConnect and relay, and your DDNS or WAN host. The assistant uses on-device models (Google Gemini Nano on Android, Apple's model on iOS and macOS), and whether Google receives usage data from the Android model service is not confirmed.
- Support email contents
- The diagnostic ZIP, sent only when you choose, goes to admin@miyarahub.com or wherever you share it. It contains the debug log with your NAS user name and host, phone manufacturer, model, OS and locale, and raw NAS readings with the NAS serial number, model, host name, IP and MAC addresses and disk serial numbers. Only tokens and passwords are masked.
- Known limits
- Crash reporting cannot be kept off. Crash text and the diagnostic ZIP are not redacted for IP addresses, host names or serial numbers. iOS Keychain credentials survive uninstall.
UPSight
- Name and platforms
- UPSight, a UPS monitor for Android, iOS, macOS and Windows. Released on the App Store, live on Google Play and live on the Microsoft Store. It is a paid download with no in-app purchases.
- Data model
- The app reads your UPS devices over SNMP and NUT on your local network. There is no account and no MiyaraHub server. Crash reports go to Google Firebase on Android and iOS only.
- Network destinations
- Your UPS devices on the local network (SNMP and NUT). Google Firebase, the app stores, and links you tap.
- Crash reports
- Default: on. Switch: none. What is sent: the error message and stack, a Crashlytics installation ID, device model and OS version, and Google sees your IP address. Redaction: none on the crash path; error text can include a UPS IP address or host name.
- Analytics
- Sends no analytics. The Firebase Analytics library is in the app but switched off on Android and iOS, and no code sends events. The Advertising ID permission is removed.
- Permissions
- Android: internet, network state and notifications; the notification permission is requested at every startup. iOS: local network, and photo library read and add, for which no matching feature was found.
- Purchases
- Paid upfront through the store. The app has no in-app purchases, and MiyaraHub receives no payment data.
- Local storage and uninstall
- UPS devices, including IP address, serial number, SNMP communities, SNMPv3 and NUT user names and passwords, are stored without encryption. Power event history and settings are also stored on the device. Android Auto Backup and iCloud backup include all of it, credentials too.
- Egress to services you choose
- The settings export file contains SNMP communities and SNMP and NUT passwords in plain text, and goes wherever you share it.
- Support email contents
- The diagnostic ZIP, sent only when you choose, goes to admin@miyarahub.com or wherever you share it. Credentials, UPS serial numbers and configured hosts are masked, and IP and MAC addresses are masked unless you turn on "include network addresses". UPS model, firmware and status and phone device details are included.
- Known limits
- UPS credentials are stored in plain text, included in device backups and written into the export file. Crash reports cannot be turned off and are not redacted.
FuryPath
- Name and platforms
- FuryPath, a controller for HDFury devices, for Android, iOS, macOS and Windows. Released on the App Store, live on Google Play and live on the Microsoft Store. It is a paid download with no in-app purchases.
- Data model
- The app talks to your HDFury devices on your local network or over Bluetooth through an HDFury GO2 adapter. There is no account and no MiyaraHub server. Crash reports go to Google Firebase on Android and iOS only.
- Network destinations
- Your HDFury devices over the local network and Bluetooth. On iOS and macOS, an update check you start asks Apple (itunes.apple.com), which sees your IP address and the app ID. Google Firebase, the app stores, and links you tap.
- Crash reports
- Default: on. Switch: only in a hidden Developer Mode; once off it stays off. What is sent: the error message and stack, a Crashlytics installation ID, device model and OS version, and Google sees your IP address. Redaction: IP addresses keep only their first two parts and MAC addresses keep only their first three parts; serial numbers and host names are not masked.
- Analytics
- Sends no analytics. There is no analytics library and no switch.
- Permissions
- Android: internet, network and Wi-Fi state, Bluetooth scan and connect, and on Android 11 and older, location, because Bluetooth scanning needs it there. iOS: Bluetooth, local network and photo library (to restore a backup); camera and location strings are present and say the app does not use them.
- Purchases
- Paid upfront through the store. The app has no in-app purchases, and MiyaraHub receives no payment data.
- Local storage and uninstall
- Saved devices (name, IP address, port, model, host name, firmware, serial number) are kept in app storage, and the app stores no device passwords. Android Auto Backup and iCloud backup include the device list. The backup export file includes saved devices.
- Egress to services you choose
- The backup file you export, and links and email you open.
- Support email contents
- The diagnostic ZIP, sent only when you choose, goes to admin@miyarahub.com or wherever you share it. It is masked the same way as crash reports, and full network addresses are included only if you turn that on. Device model, firmware and capabilities are not masked.
- Known limits
- The crash switch is hidden from ordinary users. Serial numbers and host names are not masked in crash reports.
AVR Maestro
- Name and platforms
- AVR Maestro, a controller for Denon and Marantz receivers, for Android, iOS and desktop (Windows, macOS, Linux). Released on the App Store, live on Google Play and live on the Microsoft Store.
- Data model
- The app talks to your receiver on your local network. There is no account and no MiyaraHub server. Crash reports go to Google Firebase on Android and iOS only, and analytics go there only if you say yes.
- Network destinations
- Your receiver on the local network (HTTP, telnet, HEOS, discovery and Wake-on-LAN). An automatic update check, a plain request for avrmaestro.com/version.json with no parameters, which sees your IP address and your app and device type as any web request does. Google Firebase, store billing and review, and the on-device AI model download from Google or Apple. Voice input is recognized on your device.
- Crash reports
- Default: on. Switch: Settings, About, Crash reporting; off means nothing is sent. What is sent: the error message and stack, a Crashlytics installation ID, Firebase installation ID, device model, OS version, memory and disk state and app version, and Google sees your IP address. Redaction: receiver addresses, MAC addresses, serial numbers and host names are masked before a report is sent.
- Analytics
- Off until you opt in. The app asks once, before any event is sent, and Settings, About, Legal reverses the answer at any time. If you agree: app instance ID, Firebase installation ID and, on iOS, the vendor ID; the Advertising ID is not collected. Events: the automatic Firebase events first_open, session_start, user_engagement, app_update, os_update, app_remove and in_app_purchase, and Google derives approximate location from your IP address.
- Permissions
- Android: internet, network and Wi-Fi state, multicast (discovery), billing and microphone (voice, asked when you tap). iOS: local network, microphone and speech recognition; camera, location and photo strings are declared but never requested.
- Purchases
- One optional one-time integrations add-on through Google Play, the App Store or the Microsoft Store. It is checked on your device only, and the store record (order ID, purchase token, purchase time) is kept on your device.
- Local storage and uninstall
- Saved receivers (name, IP address, model, serial number, firmware, MAC address) are in app storage. Home Assistant and Hubitat access tokens are in the Android Keystore or the iOS Keychain. Android does not back the app up to Google Drive. The iOS Keychain purchase record survives uninstall, and so can other Keychain items from an earlier install; a fresh install clears them. Settings, About, Erase all app data deletes saved receivers, settings, tokens, Scenes, widget data and files after two confirmations, turns collection off and returns the app to its welcome screen. It keeps the store purchase record, which the store can restore anyway.
- Egress to services you choose
- Home Assistant, Hubitat and webhooks at addresses you enter receive receiver state and scene events. The app warns you when such an address is a public http:// address; it does not block it. On Android, only an app signed with our key, such as NexusDeck, can read your saved receivers. The backup export includes saved receivers with IP, MAC and serial number.
- Support email contents
- "All relevant logs", sent only when you choose, emails a ZIP to admin@miyarahub.com or opens the share sheet. It contains device information, probe files, and the debug log, with app version and device label in the email. Receiver addresses are hidden unless you ask for them, and tokens are masked.
- Known limits
- Crash reports are on until you switch them off. An address you type into a Home Assistant, Hubitat or webhook field is kept as you typed it. The update check cannot be switched off.
AVR Maestro for Onkyo Pioneer
- Name and platforms
- AVR Maestro for Onkyo Pioneer, a controller for Onkyo, Pioneer and Integra receivers, for Android, iOS and Windows. Store availability is not confirmed in this policy.
- Data model
- The app talks to your receiver on your local network. There is no account and no MiyaraHub server. Crash reports and analytics go to Google Firebase on Android and iOS only.
- Network destinations
- Your receiver on the local network. An automatic update check to www.miyarahub.com, which sees your IP address. Google Firebase, store billing and review, the on-device AI model download from Google or Apple, and the phone's speech recognizer, which may be a Google or Apple cloud service.
- Crash reports
- Default: on. Switch: only in a hidden Developer section. What is sent: the error message and stack, a Crashlytics installation ID, Firebase installation ID, device model, OS version and app version, and Google sees your IP address. Redaction: none; network error text can include the receiver's IP address.
- Analytics
- On by default. There is no switch in the app. Identifiers: app instance ID, Firebase installation ID and, on iOS, the vendor ID; the Advertising ID is not collected. Events: only the automatic Firebase events, such as first_open, session_start, user_engagement, app_update, os_update and in_app_purchase.
- Permissions
- Android: internet, network and Wi-Fi state, multicast, billing and microphone (voice). iOS: local network, microphone and speech recognition; camera, location and photo strings are declared but never requested.
- Purchases
- Three optional one-time purchases: Pro, Home Automation and a bundle of both, through Google Play, the App Store or the Microsoft Store. Signed store records are kept in secure storage on your device.
- Local storage and uninstall
- Saved receivers and settings are in app storage, and Home Assistant tokens are in app storage without encryption. The app keeps a usage trail on disk for the current and previous session: screens opened, controls used, scenes applied, connection state and errors, together with protocol captures and debug logs. Android Auto Backup includes app storage, Home Assistant tokens included.
- Egress to services you choose
- Home Assistant, Hubitat and webhooks at addresses you enter receive receiver state and events. On Android, the NexusDeck app can read your saved receivers.
- Support email contents
- The log bundle, sent only when you choose, goes to admin@miyarahub.com. It contains device information, capabilities, protocol captures with the receiver's identity data, the usage trail and debug logs for the current and previous session. Webhook paths, tokens, secrets and sign-in codes are masked; IP addresses, MAC addresses and serial numbers are not.
- Known limits
- Crash reports are not redacted and the switch is hidden. The usage trail is kept on the device. Home Assistant tokens are stored without encryption and included in Android Auto Backup.
AVR Maestro MC
- Name and platforms
- AVR Maestro MC, a controller for Yamaha MusicCast receivers, for Android, iOS and macOS. Store availability is not confirmed in this policy.
- Data model
- The app talks to your receiver on your local network. There is no account and no MiyaraHub server. Crash reports go to Google Firebase on Android, iOS and macOS.
- Network destinations
- Your receiver on the local network over HTTP without encryption. Google Firebase, store review, and links you tap.
- Crash reports
- Default: on, on Android, iOS and macOS. Switch: none. What is sent: the error message and stack, a Crashlytics installation ID, Firebase installation ID, device model and OS version, and Google sees your IP address. Redaction: none; error text can include the receiver's IP address.
- Analytics
- Sends no analytics. There is no analytics library and no Advertising ID permission.
- Permissions
- Android: internet, network state and Wi-Fi state. iOS: local network. No microphone, camera, location or photos.
- Purchases
- The app has no in-app purchases. Whether it is a paid download is not confirmed.
- Local storage and uninstall
- Saved receivers (name, model, IP address, Yamaha device ID, firmware), settings and review prompt counters are in app storage. Android Auto Backup includes them. The backup export includes saved receivers.
- Egress to services you choose
- Backup files, debug logs and diagnostics that you share through the share sheet.
- Support email contents
- "Email dev" in the review prompt opens your mail app addressed to admin@miyarahub.com with the app version, device manufacturer and model, and OS version filled in.
- Known limits
- Crash reporting has no switch and is not redacted.
Projector Pilot PJLink & VP21
- Name and platforms
- Projector Pilot PJLink & VP21, a projector controller for Android, iOS, macOS and Windows. Released on the App Store, live on Google Play and live on the Microsoft Store.
- Data model
- The app talks to your projectors on your local network. There is no account and no MiyaraHub server. Crash reports and, after you opt in, analytics go to Google Firebase.
- Network destinations
- Your projectors over ESC/VP21, PJLink and Epson Web Control. To find projectors, the app connects to every address in your Wi-Fi subnet on projector ports. Google Firebase, store billing and review, and links you tap; there is no update check.
- Crash reports
- Default: on from the first launch. Switch: none; the analytics switch does not affect crash reports. What is sent: the error message and stack, a Firebase installation ID, device model, OS version, memory and disk state, and Google sees your IP address. Redaction: none on the crash path; network error text can include a projector or Home Assistant IP address.
- Analytics
- Off until you opt in. The prompt appears during first setup, and the switch is in Settings > About. Identifiers: app instance ID and Firebase installation ID; the Advertising ID is removed on Android, and on iOS it reads as zeros because tracking permission is never requested. Events: app_open, scan_started, scan_finished, connection_tested, device_added, projector_connected, command_sent, paywall_view, paywall_unlock_tap, purchase_result and restore_tap, plus the automatic Firebase events; turning analytics off does not reset the app instance ID.
- Permissions
- Android: internet, network and Wi-Fi state (to find the subnet) and notifications (maintenance reminders). iOS: local network; photo, camera and location strings are present only because plugins reference them, and they say so.
- Purchases
- Three optional one-time purchases: Pro, Home Automation and a bundle of both, through the App Store, Google Play or the Microsoft Store. The unlock is cached in secure storage on your device.
- Local storage and uninstall
- Saved projectors (name, IP address, port, serial number, model, MAC address) are in app storage, and for Epson Web Control the password is also in app storage without encryption. Other projector passwords and Home Assistant and Hubitat tokens are in secure storage. Android Auto Backup and iCloud backup include app storage, the Epson Web Control password too. On iOS, Keychain items, including passwords and the free usage counters, survive uninstall, and there is no user-facing delete-all action.
- Egress to services you choose
- Home Assistant at an address you enter receives the projector name, model, serial number, lamp and filter hours, input and errors. Hubitat and webhooks at addresses you enter receive projector name, input and events. The backup export includes saved projectors, the Epson Web Control password included.
- Support email contents
- Feedback and bug reports, sent only when you choose, go to admin@miyarahub.com. They include your message, app version, OS, the selected projector name and brand, and the in-app log, which keeps IP addresses and projector names. The bug report also includes the projector's serial number and firmware.
- Known limits
- Crash reports have no switch and are not redacted. The Epson Web Control password is stored without encryption and included in backups and the export file. The support log keeps IP addresses.
Projector Pilot D-ILA
- Name and platforms
- Projector Pilot D-ILA, a controller for JVC D-ILA projectors, for Android, iOS, macOS and Windows. Not yet released.
- Data model
- The app talks to your projectors on your local network. There is no account and no MiyaraHub server. Crash reports and, after you opt in, analytics go to Google Firebase on Android and iOS only.
- Network destinations
- Your projectors on TCP port 20554. To find projectors, the app connects to every address in each private /24 network your device reports. Google Firebase, store billing and review, and links you tap; there is no update check.
- Crash reports
- Default: on. Switch: Settings > About, "Send crash reports"; turning it off deletes unsent reports. What is sent: the error text, context and stack, a Crashlytics installation ID, device model, OS version, app version and memory and disk state, and Google sees your IP address. Redaction: Before a crash report leaves your device, the app removes IP, MAC and web addresses, saved projector host names, saved projector names and access tokens from the error text it carries. Model names and serial numbers are not removed.
- Analytics
- Off until you opt in. The first-launch prompt offers "No thanks" or "Share analytics", and the switch is in Settings > About. Identifiers: app instance ID and Firebase installation ID; the Advertising ID is not collected. Events: app_open, scan_started, scan_finished, connection_tested, device_added, projector_connected, command_sent, paywall_view, paywall_unlock_tap, purchase_result and restore_tap, plus the automatic Firebase events including in_app_purchase.
- Permissions
- Android: internet and notifications (local maintenance reminders). iOS: local network; photo, camera and location strings are present only because plugins reference them, and they say so. No location permission is requested.
- Purchases
- Three optional one-time purchases: Pro, Home Automation and a bundle of both, through the App Store, Google Play or the Microsoft Store. Purchases are checked on your device only. On Android the Google Play purchase record, with order ID and purchase token, is kept in app storage.
- Local storage and uninstall
- Saved projectors (name, IP address, port, model, MAC address) and settings are in app storage, and projector passwords, Home Assistant and Hubitat links and automation triggers are in secure storage. Android Auto Backup and device transfer do not copy the saved projector list, the settings or the Google Play purchase record to your Google account; purchases come back through the Google Play restore. On iOS and macOS, Keychain items can survive uninstall, and the next install deletes them on first launch. Reset All App Data deletes passwords, hub links, triggers, widget data, logs and the other settings, and keeps the purchase records, the free d-pad counter and your crash reports choice. The free d-pad usage counter is three numbers (presses used in total, the last day used and that day's count), no personal data, kept in the system Keychain on iOS and macOS so that reinstalling does not refill the free allowance. It is never sent to us, stays in the Keychain after you uninstall the app, and is not removed by Reset All App Data. On Android the counter is kept in app storage, which is not backed up, so a reinstall refills the free allowance.
- Egress to services you choose
- Home Assistant at an address you enter receives each projector as a device with its name, model and OS details, then its state (power, input, MAC address, light source hours, settings), and its address, port and password when you add it there. Hubitat receives power and input commands. Webhooks at any address you enter receive the event, projector name, input, scene and time.
- Support email contents
- Feedback and bug reports, sent only when you choose through your mail app or share sheet, go to admin@miyarahub.com. They include app version, device maker and model, OS, locale, saved projector names and models, and a redacted diagnostic log.
- Known limits
- Crash reports are on before you are asked. Model names and serial numbers are not removed from crash reports. Whether the iOS settings reach an iCloud backup in practice has not been tested.
NexusDeck
- Name and platforms
- NexusDeck, a calibration file manager for Denon and Marantz receivers, for Android, iOS, macOS and Windows. Store availability is not confirmed in this policy.
- Data model
- The app keeps a calibration library on your device and talks to your receiver on your local network. There is no account and no MiyaraHub server. Crash reports go to Google Firebase on Android and iOS only.
- Network destinations
- Your receiver on the local network over HTTP, and local discovery. Google Firebase, store purchases and review, and links you tap. No other internet service is called.
- Crash reports
- Default: on. Switch: in About; once off it stays off. What is sent: the error message and stack, a Crashlytics installation ID, Firebase installation ID, device model and OS version, and Google sees your IP address. Redaction: IP addresses, web address hosts and private host names are removed from error text before upload; stack traces are sent as they are.
- Analytics
- Sends no analytics. The app has no analytics library, although an older version of this policy said otherwise.
- Permissions
- Android: internet, network and Wi-Fi state and multicast (discovery). iOS: local network. No location, camera or microphone.
- Purchases
- One optional one-time Pro unlock through the store.
- Local storage and uninstall
- The calibration library database, settings and the paired receiver's host and name are kept on your device. Android Auto Backup includes the database and settings. There is no single delete-all action.
- Egress to services you choose
- On Android, NexusDeck reads receivers saved by AVR Maestro on the same device (name, IP address, model, serial number, MAC address and calibrations). The backup export goes wherever you share it.
- Support email contents
- "Send debug report" opens your mail app addressed to admin@miyarahub.com with app version, package, build mode, device manufacturer and model, Android build ID and build fingerprint, and up to 1000 log lines that are not redacted and include receiver addresses. The receiver diagnostic screen emails a probe dump with the receiver's name. You can edit both emails before sending.
- Known limits
- The debug email log is not redacted. The calibration library is copied to Google Drive by Android Auto Backup.
Network Deck
- Name and platforms
- Network Deck, a UniFi network manager for Android. Store availability is not confirmed in this policy.
- Data model
- The app signs in to your UniFi controller with your UniFi account. There is no MiyaraHub account and no MiyaraHub server. Crash reports go to Google Firebase.
- Network destinations
- Your UniFi controller and UniFi Protect over HTTPS, with certificate validation turned off, so the app accepts any certificate when it sends your controller user name and password. The Site Survey speed test, when you start it, sends test data to Cloudflare (speed.cloudflare.com), which sees your IP address.
- Crash reports
- Default: on. Switch: a switch exists in Settings, but release builds turn crash reporting back on at each launch, and reports saved while it was off are then sent. What is sent: the error message and stack, a Crashlytics installation ID, Firebase installation ID, device model and OS version, and Google sees your IP address. Redaction: none; error text can include the controller address, API paths and client or device names.
- Analytics
- Sends no analytics. There is no analytics library.
- Permissions
- Internet, Wi-Fi state, change Wi-Fi state, precise and approximate location and nearby Wi-Fi devices, for the Wi-Fi scan in Site Survey. Biometric lock is optional.
- Purchases
- The app has no purchases.
- Local storage and uninstall
- Controller host, port, user name, password and site are kept in secure storage and deleted when you log out. Session cookies and settings are kept on the device. Android Auto Backup includes settings but not the secure storage.
- Egress to services you choose
- The Cloudflare speed test when you start it. The app displays client lists with names, MAC and IP addresses from your network, and sends them nowhere except in crash text or a log you share.
- Support email contents
- "Debug info" shares app version, package, OS, Dart version and the controller host and site through the share sheet. The log export shares the full app log without redaction.
- Known limits
- Crash reporting cannot be kept off and is not redacted. Certificate validation is off for the controller connection.