Privacy Policy

1. Introduction

TagHue is developed and operated by Devside SRL (Belgium). This Privacy Policy explains how we handle information when you use the TagHue iOS application. By using TagHue, you agree to the practices described here.

2. Data We Do Not Collect

TagHue does not collect any personal data. There is no account system, no login, and no data transmitted to our servers. Specifically:

• No name, email address, or account credentials
• No notification content is stored or transmitted off-device
• No analytics or crash reports are sent by default
• No advertising identifiers are used

3. Data Stored Locally

TagHue stores the following data exclusively on your device:

• Your selected notification sources and their enabled/disabled status
• Flash color and repeat count per source
• Selected Hue bulb IDs per source
• Your Hue Bridge IP address and API key
• The recent flash event log (last 100 events)

This data never leaves your device unless you enable iCloud Sync (see section 4).

4. iCloud Sync (Optional)

If you enable iCloud Sync in TagHue Settings, your configuration (sources, colors, Bridge credentials) is synced to your personal iCloud account via Apple's NSUbiquitousKeyValueStore. Devside SRL has no access to your iCloud data. This feature is disabled by default.

5. Hue Bridge Communication

TagHue communicates with your Philips Hue Bridge exclusively over your local Wi-Fi network. No data is sent to Philips, Signify, or any third party. The Bridge API key is generated locally and stored only on your device.

6. Slack Integration (Optional)

If you add Slack as a notification source, TagHue uses the Slack API with a user token you provide. This token is stored locally on your device and used exclusively to poll for new messages. No Slack data is transmitted to Devside SRL.

7. Location Data (Optional)

If you enable Home-Only mode, TagHue requests access to your device's location. Your location is processed entirely on-device to determine whether you are near your home. Location data is never transmitted to any server.

8. Calendar Access (Optional)

If you add Calendar as a notification source, TagHue requests access to your calendar events via Apple's EventKit. Event data is read locally to trigger flash alerts and is never transmitted off your device.

9. Notification Access

TagHue requests permission to receive iOS notifications so it can intercept them and trigger Hue light flashes. Notification content is processed in memory and logged locally in the flash history. It is never stored permanently or transmitted off-device.

10. Third-Party Services

TagHue does not integrate any analytics, advertising, or crash-reporting SDKs. The only external communication is:

• Slack API — only if you configure the Slack source
• Apple iCloud — only if you enable iCloud Sync
• iTunes Search API — used to load app icons in the source list (no personal data sent)

11. Children

TagHue is not directed at children under 13. We do not knowingly collect any data from children.

12. Changes to This Policy

We may update this policy from time to time. Any significant changes will be communicated through an app update.

13. Contact

Devside SRL — contact@devside.com