Outline of Data Gathered by Your Tedee Devices and Tedee Services
Under the Resolution No. 2023/2854 EU Data Act we would like to present you with a simplified list of data we gather throughout the life-cycle of your Tedee Devices. We firmly believe that each of our customers should have the right to know what data is generated and to have full visibility into it. If you have any questions, feel free to contact us at [email protected].
Tedee Devices
| Data Type & Format | Tedee Lock Activities |
| Description | All device-generated events: lock/unlock actions, door events, keypad triggers, dry-contact impulses, auto-lock triggers; with timestamps, method, and user identity/PIN alias |
| Purpose | Provide a security audit trail and access transparency. |
| Data storage location (device, remote server) | Device |
| Data retention period | Until factory reset or memory limit |
| How to access the Data | Tedee App or API |
| Data Type & Format: | Tedee Device Configuration |
| Description: | Auto-lock settings, pull-spring/latch settings, button behavior, paired accessories, alert settings, Matter pairing data. |
| Purpose: | Enable customizable device behaviour and integrations. |
| Data storage location (device, remote server): | Device |
| Data retention period: | Until factory reset |
| How to access the Data: | Tedee App or API |
| Data Type & Format: | Tedee Device States |
| Description: | Realtime functional state: lock position, door status, battery level, charging status, connectivity, Matter status. |
| Purpose: | Display current state, run automation, and support integrations. |
| Data storage location (device, remote server): | Device |
| Data retention period: | Until power off |
| How to access the Data: | Tedee App or API |
| Data Type & Format: | Tedee Device Security Data |
| Description: | Cryptographic key pairs (device-only), public certificates, revocation list metadata, secure channel parameters |
| Purpose: | Ensure secure communication and device authentication |
| Data storage location (device, remote server): | Device |
| Data retention period: | Persistant or until factory reset |
| How to access the Data: | No |
| Data Type & Format: | PIN Code Authorization Data |
| Description: | PINs stored on the; metadata: PIN alias, schedule, validity. |
| Purpose: | Allow keypad-based access control with scheduling and auditing |
| Data storage location (device, remote server): | Device |
| Data retention period: | Persistent until removed by user. |
| How to access the Data: | App or API |
| Data Type & Format: | Fingerprint Authorization Data |
| Description: | Fingerprint biometric templates stored only inside the fingerprint module. Device store metadata: slot index, custom label, schedule. Templates cannot be exported or read. |
| Purpose: | Provide biometric access to the device while protecting biometric privacy. |
| Data storage location (device, remote server): | Device |
| Data retention period: | Persistent until removed on device. |
| How to access the Data: | User can see list of enrolled fingerprints (labels) in app and remove them. Raw fingerprint data is never accessible |
| Data Type & Format: | Tedee Bridge Authorization & Network Data |
| Description: | WiFi SSID/password, MQTT credentials. |
| Purpose: | Allow Bridge to connect to cloud securely. |
| Data storage location (device, remote server): | Device |
| Data retention period: | Persistent until reset. |
| How to access the Data: | Not visible; user can only reconfigure via setup flow |
| Data Type & Format: | Tedee BriDevice Internal Logs |
| Description: | Crash reports, error flags, watchdog resets, firmware debug logs |
| Purpose: | Firmware diagnostics and troubleshooting |
| Data storage location (device, remote server): | Device |
| Data retention period: | Persistent until reset. |
| How to access the Data: | App |
| Data Type & Format | Description | Purpose | Data storage location (device, remote server) | Data retention period | How to access the Data |
| Tedee Lock Activities | All device-generated events: lock/unlock actions, door events, keypad triggers, dry-contact impulses, auto-lock triggers; with timestamps, method, and user identity/PIN alias. | Provide a security audit trail and access transparency. | Device | Until factory reset or memory limit | Tedee App or API |
| Tedee Device Configuration | Auto-lock settings, pull-spring/latch settings, button behavior, paired accessories, alert settings, Matter pairing data. | Enable customizable device behaviour and integrations. | Device | Until factory reset | Tedee App or API |
| Tedee Device States | Realtime functional state: lock position, door status, battery level, charging status, connectivity, Matter status. | Display current state, run automation, and support integrations. | Device | Until power off | Tedee App or API |
| Tedee Device Security Data | Cryptographic key pairs (device-only), public certificates, revocation list metadata, secure channel parameters | Ensure secure communication and device authentication | Device | Persistant or until factory reset | No |
| PIN Code Authorization Data | PINs stored on the; metadata: PIN alias, schedule, validity. | Allow keypad-based access control with scheduling and auditing | Device | Persistent until removed by user. | App or API |
| Fingerprint Authorization Data | Fingerprint biometric templates stored only inside the fingerprint module. Device store metadata: slot index, custom label, schedule. Templates cannot be exported or read. | Provide biometric access to the device while protecting biometric privacy. | Device | Persistent until removed on device. | User can see list of enrolled fingerprints (labels) in app and remove them. Raw fingerprint data is never accessible |
| Tedee Bridge Authorization & Network Data | WiFi SSID/password, MQTT credentials. | Allow Bridge to connect to cloud securely. | Device | Persistent until reset. | Not visible; user can only reconfigure via setup flow |
| Device Internal Logs | Crash reports, error flags, watchdog resets, firmware debug logs | Firmware diagnostics and troubleshooting | Device | App |
Tedee Software
| Data Type & Format | Tedee App Authorization Data |
| Description | OAuth tokens, refresh tokens, app certificates |
| Purpose | Enable secure login and allow app to communicate with backend and devices |
| Data storage location (device, remote server) | Device |
| Data retention period | Until logout/token expiry/uninstall. |
| How to access the Data | Not directly visible; managed via logout/account settings |
| Data Type & Format: | Tedee App Cached Device Data |
| Description: | Locally cached list of user devices, settings, accessories, and partial access rights. |
| Purpose: | Improve performance, enable offline mode, reduce API calls. |
| Data storage location (device, remote server): | Local storage on mobile device. |
| Data retention period: | Until logout |
| How to access the Data: | Visible indirectly via device list and settings UI. |
| Data Type & Format: | Tedee App Firmware Storage (OTA) |
| Description: | Temporary firmware files downloaded for device updates. |
| Purpose: | Deliver firmware updates to the device via BLE. |
| Data storage location (device, remote server): | Local temporary storage on mobile. |
| Data retention period: | Deleted immediately after update. |
| How to access the Data: | Not visible to user. |
| Data Type & Format: | Tedee App User Data |
| Description: | Logged-in user identity: email, profile data, selected language, app preferences. |
| Purpose: | Personalize the user experience and authenticate requests. |
| Data storage location (device, remote server): | Device |
| Data retention period: | Persistent until account deletion/logout |
| How to access the Data: | App |
| Data Type & Format: | Tedee App Logs |
| Description: | Debug logs: BLE scans, connection events, errors, crashes, performance traces. |
| Purpose: | Diagnostics and support troubleshooting. |
| Data storage location (device, remote server): | Local mobile storage |
| Data retention period: | Short-lived up to 3 days or until memory capacity reached |
| How to access the Data: | Export via App |
| Data Type & Format: | Tedee App Last Auto-Unlock Status |
| Description: | Result and reasoning of the last auto-unlock attempt: geofence checks, WiFi verification, motion state, BLE discovery, timing steps |
| Purpose: | Allow user to understand why auto-unlock succeeded or failed |
| Data storage location (device, remote server): | Local mobile storage |
| Data retention period: | Temporary (most recent event only). |
| How to access the Data: | Visible in app under Auto-Unlock → Last Status |
| Data Type & Format: | Device configuration data |
| Description: | Configuration data of Tedee devices |
| Purpose: | Managing devices |
| Data storage location (device, remote server): | Until account deletion |
| Data retention period: | Yes |
| How to access the Data: | API |
| Data Type & Format: | Access Control Data |
| Description: | Who can access the Tedee device, access level, schedules |
| Purpose: | Access control |
| Data storage location (device, remote server): | Until account deletion |
| Data retention period: | Yes |
| How to access the Data: | App |
| Data Type & Format: | Certificate & Crypto metadata |
| Description: | E2E certificates, revocation metadata |
| Purpose: | Access Control and security |
| Data storage location (device, remote server): | Until account deletion |
| Data retention period: | No |
| How to access the Data: | No |
| Data Type & Format: | Device Activities |
| Description: | All lock activities like lock/unlock/trigger events, timestamps, source |
| Purpose: | Historical log of access for auditing |
| Data storage location (device, remote server): | Until account deletion |
| Data retention period: | Yes |
| How to access the Data: | API |
| Data Type & Format: | User configuration |
| Description: | User configuration like notification preferences, app configuration, |
| Purpose: | User system personalization |
| Data storage location (device, remote server): | Until account deletion |
| Data retention period: | Yes |
| How to access the Data: | API |
| Data Type & Format: | Registered mobile devices |
| Description: | List of mobile devices used by user together with device name and operation system |
| Purpose: | Security and push notifications control |
| Data storage location (device, remote server): | Until account deletion |
| Data retention period: | Yes |
| How to access the Data: | API |
| Data Type & Format: | Access Links |
| Description: | Generated access links with access details |
| Purpose: | Managin access for guests |
| Data storage location (device, remote server): | Until account deletion |
| Data retention period: | Yes |
| How to access the Data: | API |
| Data Type & Format: | Organization configuration |
| Description: | Configured organizations by user with organization name, users, groups, assigned devices |
| Purpose: | Managing organization |
| Data storage location (device, remote server): | Until account deletion |
| Data retention period: | Yes |
| How to access the Data: | API |
| Data Type & Format: | User account Data |
| Description: | Authentication Identity, email, display name |
| Purpose: | Authentication and security |
| Data storage location (device, remote server): | Until account deletion |
| Data retention period: | Yes |
| How to access the Data: | API |
| Data Type & Format: | Rental Services |
| Description: | Configured smart rental services and linked account |
| Purpose: | Authentication |
| Data storage location (device, remote server): | Until account deletion |
| Data retention period: | No |
| How to access the Data: | API |
| Data Type & Format: | Rental Bookings |
| Description: | Bookings synced from configured smart rental services |
| Purpose: | Showing bookings and enabling automations |
| Data storage location (device, remote server): | Until account deletion |
| Data retention period: | No |
| How to access the Data: | API |
| Data Type & Format: | Rental Listings |
| Description: | Listings synced from configured smart rental services |
| Purpose: | Showing bookings and enabling automations |
| Data storage location (device, remote server): | Until account deletion |
| Data retention period: | No |
| How to access the Data: | API |
| Data Type & Format: | API Requests |
| Description: | Log of API requests sent to our system |
| Purpose: | Security, auditing and rate limits |
| Data storage location (device, remote server): | year |
| Data retention period: | No |
| How to access the Data: | No |
| Data Type & Format: | Device state |
| Description: | Current Tedee device connection/battery/position state |
| Purpose: | Automations and remote device control |
| Data storage location (device, remote server): | Until account deletion |
| Data retention period: | Yes |
| How to access the Data: | API |
| Data Type & Format | Description | Purpose | Data storage location (device, remote server) | Data retention period | How to access the Data |
| Tedee App Authorization Data | OAuth tokens, refresh tokens, app certificates | Enable secure login and allow app to communicate with backend and devices | Device | Until logout/token expiry/uninstall. | Not directly visible; managed via logout/account settings |
| Tedee App Cached Device Data | Locally cached list of user devices, settings, accessories, and partial access rights. | Improve performance, enable offline mode, reduce API calls. | Local storage on mobile device. | Until logout | Visible indirectly via device list and settings UI. |
| Tedee App Firmware Storage (OTA) | Temporary firmware files downloaded for device updates. | Deliver firmware updates to the device via BLE. | Local temporary storage on mobile. | Deleted immediately after update. | Not visible to user. |
| Tedee App User Data | Logged-in user identity: email, profile data, selected language, app preferences. | Personalize the user experience and authenticate requests. | Device | Persistent until account deletion/logout | App |
| Tedee App Logs | Debug logs: BLE scans, connection events, errors, crashes, performance traces. | Diagnostics and support troubleshooting. | Local mobile storage | Short-lived up to 3 days or until memory capacity reached | Export via App |
| Tedee App Last Auto-Unlock Status | Result and reasoning of the last auto-unlock attempt: geofence checks, WiFi verification, motion state, BLE discovery, timing steps | Allow user to understand why auto-unlock succeeded or failed | Local mobile storage | Temporary (most recent event only). | Visible in app under Auto-Unlock → Last Status |
| Device configuration data | Configuration data of Tedee devices | Managing devices | Until account deletion | Yes | API |
| Access Control Data | Who can access the Tedee device, access level, schedules | Access control | Until account deletion | Yes | API |
| Certificate & Crypto metadata | E2E certificates, revocation metadata | Access Control and security | Until account deletion | No | No |
| Device Activities | All lock activities like lock/unlock/trigger events, timestamps, source | Historical log of access for auditing | Until account deletion | Yes | API |
| User configuration | User configuration like notification preferences, app configuration, | User system personalization | Until account deletion | Yes | API |
| Registered mobile devices | List of mobile devices used by user together with device name and operation system | Security and push notifications control | Until account deletion | Yes | API |
| Access Links | Generated access links with access details | Managin access for guests | Until account deletion | Yes | API |
| Organization configuration | Configured organizations by user with organization name, users, groups, assigned devices | Managing organization | Until account deletion | Yes | API |
| User account Data | Authentication Identity, email, display name | Authentication and security | Until account deletion | Yes | API |
| Rental Services | Configured smart rental services and linked account | Authentication | Until account deletion | No | API |
| Rental Bookings | Bookings synced from configured smart rental services | Showing bookings and enabling automations | Until account deletion | No | API |
| Rental Listings | Listings synced from configured smart rental services | Showing bookings and enabling automations | Until account deletion | No | API |
| API Requests | Log of API requests sent to our system | Security, auditing and rate limits | year | No | No |
| Device state | Current Tedee device connection/battery/position state | Automations and remote device control | Until account deletion | Yes | API |
How to access your data
Your Tedee devices generate different types of data as you use them. Some of this data lives only on your own equipment – for example, on your smartphone through the Tedee App. You can view and manage this locally stored information directly on your device. Because this data never leaves your phone, Tedee cannot access it, and therefore cannot export or retrieve it on your behalf.
Other data – such as device activity logs, configuration details, or cloud-based events – is processed through our systems. You can request access to these datasets at any moment, and we will provide them to you in a structured, machine-readable format.
Requesting your data
If you would like Tedee to prepare an export of the data we process for you:
- Submit a request
Send a short email to [email protected] and specify which Tedee device(s) your request refers to, or use the form template available here [URL]
- Identity and device verification
To protect your security, we may need to confirm that the request is coming from the rightful user or device owner.
- Receiving your data
Once verified, we will compile your data and deliver it in a commonly used, machine-readable format together with the metadata required to interpret it.
The full Data Access & Sharing Terms are available at Tedee Data Access & Sharing Terms
If anything is unclear or you need additional help, our support team is always available at [email protected].
