Ir al contenido
Entrixy Entrixy

Política de privacidad

Qué tratamos, qué no, y por qué la privacidad está incorporada en la arquitectura.

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. Quién trata los datos

El responsable del tratamiento es el desarrollador del proyecto Entrixy. Para preguntas sobre el tratamiento de datos y solicitudes de borrado, escribe a hello@entrixy.com.

2. Datos en la aplicación

Geolocalización

Si activas la apertura automática por geozona, la aplicación usa la ubicación del dispositivo, también en segundo plano, para saber cuándo te acercas a un objeto. Las coordenadas se procesan en el propio dispositivo y nunca se envían al servidor en claro. Si no hay ninguna condición geográfica activa, la ubicación en segundo plano ni siquiera se solicita.

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 y Bluetooth

Para la condición de red Wi-Fi, la aplicación comprueba a qué red está conectado el teléfono. Para la apertura directa por Bluetooth, busca un controlador cercano. Estos datos se usan en el dispositivo y nunca se envían al servidor.

Datos del objeto

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.

El invitado no necesita ni la aplicación ni una cuenta: el acceso llega como enlace o código QR, y la clave está dentro de ese enlace y nunca se envía al servidor.

3. Permisos de la aplicación y para qué sirven

Los permisos se piden cuando hacen falta. Si no usas la función correspondiente, el permiso no se utiliza.

4. Datos en el servidor

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. Cuenta en el sitio

La cuenta en el sitio hace falta para guardar configuraciones, para el área de fabricante y funciones relacionadas. Al registrarte guardamos tu dirección de correo (para iniciar sesión, confirmar y recuperar la contraseña) y tu contraseña como un hash irreversible. No hace falta cuenta para usar la aplicación ni para el acceso de invitado.

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. Cookies en el sitio

En las páginas del sitio —salvo en las secciones con datos privados: compilación de firmware, recepción de llaves, autenticación y área de cuenta— usamos cookies y analítica web para entender cómo usan el sitio los visitantes: visitas, fuentes de referencia, clics e interacción con la página. En las páginas donde pueden mostrarse secretos o claves no se cargan ni cookies ni analítica.

En tu primera visita se muestra un aviso de cookies. Puedes desactivarlas en los ajustes del navegador, bloqueándolas o activando un modo que limite el seguimiento.

7. Cesión a terceros

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. Conservación y borrado

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. Menores

El servicio no está dirigido a menores de 13 años y no recoge sus datos a sabiendas.

10. Cambios

Esta política puede actualizarse. La versión vigente está siempre disponible en entrixy.com/privacy; la fecha de la versión figura arriba.

11. Contacto

Para cualquier pregunta sobre el tratamiento de datos, escribe a hello@entrixy.com.