Hometether docs
v1.0.0
Get help
● Use

Privacy
what is stored, what is not.

Use this page to fill in your own privacy policy and the store data-safety forms. It describes what the code does; you remain responsible for your policy and for your hosting.

TLS, not end-to-endopt-in counts

01Stored on the phones

The first name, the paired family or helpers, the chosen TV and the settings are stored on the phone. Relay secrets and TV tokens are kept in the Keychain (iOS) or Keystore-backed storage (Android). The helper's session start times are kept on the helper's phone for the monthly count. The camera is used only to scan a pairing QR code; nothing is recorded or sent.

02Stored on your server

DataDetail
FamilyAn id, the parent's first name (1 to 40 characters), a device id, a hash of the secret, a creation time.
HelpersAn id, the helper's first name, a hash of the secret, a creation time.
Pairing codesOnly a hash, an expiry and a used flag.
Session logFamily id, start time, end time and end reason. Kept 90 days, for the per-family limits and the counts in the console.
Usage countsOnly for people who opted in: a random install id, platform, app version, Plus or not, last seen.
PurchasesOnly if you switch verification on: store transaction id, price, time. No install id.

First names are personal data. Tell your users that they are stored and why.

03Not stored

The content of a session: commands and results pass through memory and are never written to the database or the logs. There is no screen content, camera image, TV viewing history or contact list. The app contains no advertising or analytics package.

Not end-to-end encrypted

Traffic is protected by TLS (wss) with session tokens minted by the server. It is not end-to-end encrypted: the relay can in principle see commands while they pass through. Do not describe it as end-to-end encrypted in your policy or listing.

04What leaves the phone

CallConditionContent
Config requestOnly if you build with API_BASE_URLA normal request to your server.
Pairing and relayWhen someone uses remote helpNames, codes, secrets and commands over TLS to your server.
Usage pingOnly if the user switches it on (off by default), at most once a dayRandom install id, platform, version, Plus or not.
Purchase checkOnly if you switch verification onProduct id and store receipt or token.
TV controlAlways when controlling a TVStays on the home Wi-Fi, to the TV's private address.
Store purchaseWhen the user buysHandled by Apple and Google.

05Store forms

  • Permissions in the app: Android: internet, network and Wi-Fi state, multicast state, camera (QR scan only, optional hardware), billing. iOS: local network (with the Bonjour services listed in Info.plist) and camera, each with a plain-language reason.
  • iOS privacy manifest: ios/Runner/PrivacyInfo.xcprivacy declares no tracking and, for the opt-in counts, product interaction data not linked to the user and used for analytics. Review it against what you change.
  • Apple privacy label and Google Play data safety: your answers depend on your own server. Based on the code, think about names (the first names above), an app-generated install id (only with opt-in counts) and purchase history if you use verification. This is guidance, not legal advice.
  • Publish a privacy policy and put its address in brand.dart or the console (Legal). Both stores require one.