Политика конфиденциальности
Что мы обрабатываем, что — нет, и почему приватность заложена в архитектуру.
Revision of 21 November 2026.
Entrixy is an app and a website for access control: gates, barriers, doors, locks and intercoms. This policy covers the Android app, the iOS app currently in development, and entrixy.com. Available features and system permissions depend on the platform and installed version.
Access packages are encrypted on your device. The server also processes the account, routing and delivery information needed to operate the service, as described below. Encryption does not hide every piece of service metadata.
1. Кто обрабатывает данные
Оператором выступает разработчик проекта Entrixy. Вопросы по обработке данных и запросы на удаление — hello@entrixy.com.
2. Данные в приложении
Геолокация
Если вы включаете автооткрытие по геозоне, приложение использует местоположение устройства (в том числе в фоне), чтобы определить приближение к объекту. Координаты обрабатываются на самом устройстве и на сервер в открытом виде не передаются. Без включённого гео-условия фоновое местоположение не запрашивается.
On iOS, optional motion observations help detect stale location readings. Route maps use Apple MapKit; map requests are handled by Apple under its privacy policy. iOS decides when background location and Bluetooth work can run; enabling a rule does not guarantee continuous background execution.
Wi-Fi и Bluetooth
Для условия "по сети Wi-Fi" приложение проверяет, к какой сети подключён телефон. Для прямого открытия по Bluetooth — ищет контроллер поблизости. Эти данные используются на устройстве и на сервер не передаются.
Данные объектов
The barrier's phone number and local webhook address and secret are not sent to the access server in readable form. The server keeps the webhook address and secret in readable form only when you choose server-side execution, so that it can send the request. The coordinates, the camera address and the set of Wi-Fi networks are encrypted on your device with the object key (AES-256-GCM), and only the encrypted package reaches the server. When you share access with a guest, the object key travels inside an encrypted parcel, and not even the developers can decrypt the contents.
Camera streams and local webhooks connect to the endpoint you configure. That endpoint and its operator receive the connection and relevant credentials. A phone call is handed to the phone system and carrier; iOS requires the system call confirmation. If you choose a number from contacts, the iOS system picker gives Entrixy only the name and phone number you selected; Entrixy does not upload your address book. These functions do not use your microphone.
Images, sounds and device protection
QR scanning uses the camera. A picture or sound you explicitly select can be stored with the corresponding object or event; object pictures shared with access travel in the encrypted package. Face ID and Touch ID are checked by iOS: Entrixy does not receive your biometric template. The Entrixy code and access credentials are held in device-only protected storage on iOS. A backup you explicitly export is an encrypted file; its destination and any later copies are under your control.
Гостю не нужны ни приложение, ни аккаунт: доступ приходит по ссылке или QR-коду, а сам ключ лежит в этой ссылке и на сервер не отправляется.
3. Разрешения приложения и зачем они
- Местоположение (в фоне) — только для условий по геозоне.
- Bluetooth — для прямого открытия контроллеров рядом с вами.
- Уведомления — показ статуса фоновой работы и сообщения о событиях.
- Телефон (звонок) — для устройств, открывающихся дозвоном на номер.
- Автозапуск и отключение экономии батареи — чтобы фоновая автоматизация не отключалась системой.
- On iOS: camera for QR scanning, selected Photos/files for your own images and sounds, Face ID for optional authentication, motion for configured location checks, and local-network access for your own endpoints. Android autostart and battery-exemption permissions do not apply to iOS.
Разрешения запрашиваются по мере необходимости. Без соответствующей функции разрешение не используется.
4. Данные на сервере
The access server stores encrypted object/key packages and encrypted messages, together with routing identifiers, key status, delegation limits, device bindings and action/audit records. It receives the source IP address of each connection. Phone numbers, coordinates, geofences and camera settings inside encrypted packages are not readable by the server. An explicitly configured server-side webhook is an exception: the server needs its destination and secret to execute it.
Android uses Google Firebase Cloud Messaging for delivery hints. The iOS notification integration uses Apple Push Notification service when enabled and configured. It registers an APNs device token, environment and a binding to an access-key hash. Apple receives a generic message notice or update hint, not the encrypted message, access key, object name or opening command. Opening a notification does not authorize an opening. Production iOS notification delivery is still being prepared.
Optional iOS diagnostics
Automatic crash reports require a separate opt-in in Entrixy settings, which can be turned off again. Reports contain app/build and iOS versions, an allowlisted crash stack and coarse technical state. A manual technical report is sent only when you request it. The iOS report format excludes access credentials, object names, phone numbers, coordinates, Wi-Fi names and raw arbitrary system logs. The receiving server still sees the connection IP. These reports go to entrixy.com even when you use another access server.
Entrixy information and promotion cards
The app can request cards from entrixy.com using a separate random installation identifier, app version, language, installation age and coarse feature tags such as whether a webhook or guest access is present. Tags are used to select the response and are not stored by that endpoint. Per-card view counts are stored by installation identifier and date to enforce display limits; clicks use the website redirect service. These requests do not contain owner credentials, key material, object names, coordinates or Wi-Fi identifiers. The iOS app contains no third-party advertising or analytics SDK; this does not mean that no usage information is processed.
5. Аккаунт на сайте
Аккаунт на сайте нужен для сохранения конфигураций, кабинета производителя и связанных функций. При регистрации мы храним адрес электронной почты (для входа, подтверждения и восстановления пароля) и пароль в виде необратимого хеша. Аккаунт не обязателен для использования приложения и гостевого доступа.
The iOS server settings sign in to an existing confirmed email account and can link or unlink the current owner device. They do not create an email account. Unlinking a device is different from deleting the website account. A custom access server may have its own operator and data policy.
6. Cookie на сайте
На страницах сайта (кроме разделов с приватными данными — сборка прошивок, приём ключей, авторизация, кабинет) мы используем cookie и инструменты веб-аналитики, чтобы понимать, как посетители пользуются сайтом: посещения, источники переходов, клики и взаимодействие со страницей. Cookie и аналитика не подключаются на страницах, где могут отображаться секреты или ключи.
При первом визите показывается уведомление об использовании cookie. Отключить их можно в настройках браузера — запретив cookie или включив режим, ограничивающий отслеживание.
7. Передача третьим лицам
We do not sell access data or share it with data brokers. Technical services include the website analytics service, Google for Android push, Apple for iOS push and maps, and the hosting and email services needed to run the website. Following an external link, making a phone call or using a configured camera/webhook also contacts that destination's operator. The encrypted access packages are not supplied to an advertising network.
8. Хранение и удаление
Object data is kept on your device and, where required, encrypted on the access server until it is removed or access is revoked. A website account and the data tied to it can be requested for deletion at hello@entrixy.com. Local deletion or device unlinking does not itself delete server objects or revoke keys already issued to guests.
The server cleanup routine targets action/audit records and ordinary crash reports older than 30 days, and queued offline delivery hints older than seven days. When the APNs worker is enabled and running, it also removes inactive device-token bindings after 30 days and queued APNs hints after seven days. These are maintenance rules, not a promise that a disabled worker has already removed data. Manual support logs and archived Android host logs can be kept for ongoing investigation; promotion view records currently have no automatic age-based deletion. Contact us to request their deletion where they can be identified. Hosting logs and backups may have separate retention schedules.
Deleting an iOS app can leave its Keychain item on the device. Do not rely on reinstalling to recover a forgotten Entrixy code or erase access. The iOS local-data reset flow explicitly replaces the protected access state and removes app settings and caches. It cannot recover an old code, revoke remote guests or erase backup files you previously copied elsewhere. Keep an encrypted backup and its password, or obtain replacement access from the owner before resetting.
9. Дети
Сервис не предназначен для детей младше 13 лет и сознательно не собирает их данные.
10. Изменения
Политика может обновляться. Актуальная версия всегда доступна по адресу entrixy.com/privacy; дата редакции указана вверху.
11. Контакты
По любым вопросам об обработке данных — hello@entrixy.com.