Privacy policy
Tacktab has no account, no ads and no cookies. To find bugs, it sends anonymous crash reports and counts how often it is opened. Nothing it sends identifies you or your tablet, and none of it includes the pages you show. You can turn it off in Tacktab's settings.
Last updated: October 24, 2026
Crash reports and usage counts
From Tacktab 1.0.2, the apps send two things to servers Tacktab runs for itself (errors.applifyer.com and insights.applifyer.com, hosted by Microsoft Azure in Germany):
- Crash reports: when Tacktab crashes, the type of error and where in Tacktab's code it happened, with the Tacktab version and the tablet's model and system version. Crash reports are kept for 30 days.
- An app-open count: one anonymous "app opened" event when Tacktab starts, with the approximate location (country and city) worked out from the network address.
Neither includes your name, an account, a device identifier, the page address, anything on the page, or the remote control password. The network address itself is not stored. The data is not sold, not shared, and not used for advertising.
To stop sending both, turn off Send anonymous crash reports and usage in Tacktab's settings.
What stays on your tablet
- Your settings: the start page, display options, the settings PIN (stored as a one-way hash) and the remote control password.
- Cookies and website storage for the page you show, so you stay signed in to it. You can remove them by clearing Tacktab's data or uninstalling it.
The pages you show
Tacktab opens the web address you choose, such as a Home Assistant dashboard on your own network. That website's own privacy policy applies to what it collects. Tacktab does not read, copy or send page content anywhere.
Optional camera attention wake
From Tacktab 1.1.0, you can choose to let the front camera detect when a face is facing the screen, so the dashboard wakes when needed. You must turn this on and allow camera access on that tablet. Images are processed in memory on the device, never recorded, stored or uploaded. Tacktab does not identify people or keep a face database. It stops using the camera when you leave the app or open its settings. The system shows its camera-use indicator.
Android 1.3.1 extends this to local people and movement detection, with recovery after camera interruptions; the iPad update awaits publication. The same privacy rules apply. Its optional offline clock uses the tablet's time and date, independently of camera permission.
Optional voice and announcements
Tacktab 1.2 adds optional voice control and spoken announcements on Android and iPad. Both are off by default. Voice requires you to enable it on the tablet and grant microphone access. Tacktab sends microphone audio to the Home Assistant server you configure. In hands-free mode, that server listens for the wake word while Tacktab is visible. Capture stops in settings and outside Tacktab, and pauses during spoken playback. Your configured Home Assistant providers determine whether audio or text is processed locally, forwarded or retained by those providers. Tacktab does not send this audio to Applifyer's servers or include speech in diagnostics.
The Home Assistant access token is stored encrypted on the tablet using Android Keystore or iOS Keychain. Use HTTPS outside a trusted network: plain HTTP or WebSocket connections send the token and microphone audio without transport encryption. Speech text appears temporarily on the screen. Spoken announcements use the platform speech service and do not need microphone permission. An Android network voice may send text to its provider; the provider's privacy policy applies. Remote announcement requests require the existing remote control password and cannot enable either feature.
Connection checks authenticate with the Home Assistant server you entered and request its assistant names without opening the microphone. Microphone activity levels for the native listening display are computed in memory on the tablet and are not saved or included in diagnostics. Mute is stored locally and survives a restart. Home Assistant conversation identifiers remain in memory for follow-up commands and are cleared when voice is disabled or the connection or selected assistant changes.
Native voice and timers
Android 1.3 introduces optional tablet-local wake words and native Home Assistant timers; the iPad update awaits publication. In local wake mode, idle audio and a short pre-roll buffer stay in memory on the device. Command audio reaches your Home Assistant after a detected wake word is granted or you tap Talk. Background listening is a separate choice: Android shows a persistent listening notification with Mute and Stop actions, and iOS shows its system recording indicator. Opening settings, microphone mute and permission loss stop capture. Timer alerts have their own sound and mute settings.
Optional realtime conversations relay audio through your Home Assistant to the OpenAI, xAI or Gemini account you configure. Audio, conversation text, your instructions, device name and area, and authorized Home Assistant tool descriptions and results can reach that provider. Its charges and privacy terms apply. Provider API keys are stored in Home Assistant's ordinary configuration storage, not in Tacktab's mobile preferences or diagnostics. Conversation memory is optional and bounded in RAM on Home Assistant; it is not saved across a server restart. Timer names and state come from your Home Assistant and are not included in Tacktab diagnostics.
Purchases
Tacktab Pro is sold through Google Play and the Apple App Store. Google or Apple handles the payment and any promo or offer code. The app only learns whether you own Pro. We never see your payment details.
Remote control
If you turn on the remote control API, Tacktab answers requests from your local network that carry the password you set. It reports the current page address, the screen state, brightness, the battery level and the device model to the caller. Nothing is sent to us.
Permissions
- Internet and local network: to load the page you chose, to answer remote control requests, and to let Home Assistant find the tablet on your network.
- Notifications (Android): to show that remote control is on while it runs.
- Start at boot (Android): to reopen your page after the tablet restarts.
- Device administrator (Android, optional): to switch the display off when you ask it to, and, if you make Tacktab the device owner, to lock the tablet to your page. You can remove it in Tacktab's settings at any time.
- Camera (optional): local attention wake, only after you enable it and allow access.
- Microphone (Tacktab 1.2, optional): native Home Assistant voice control on Android and iPad, only after you enable it and allow access. Spoken announcements do not need this permission.
Tacktab does not use location. Pages shown in Tacktab cannot use the camera, microphone or location, even when native attention wake or voice is enabled.
This website
tacktab.com uses no cookies. It counts visits with its own cookie-free analytics at insights.applifyer.com: the page, the referring site, the browser and the approximate location. It keeps no network address, and it counts nothing if your browser sends Do Not Track. Cloudflare, which hosts the site, keeps standard request logs to run and protect it.
Children
Tacktab is not directed at children and does not knowingly collect data from anyone.
Changes and contact
We will update this page if anything changes and show the new date at the top. Questions: support@tacktab.com. Tacktab is made by Edi Hasaj.