Política de privacidade
O que tratamos, o que não tratamos, e porque é que a privacidade está inscrita na arquitetura.
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. Quem trata os dados
O responsável pelo tratamento é o programador do projeto Entrixy. Para perguntas sobre o tratamento de dados e pedidos de eliminação, escreva para hello@entrixy.com.
2. Dados na aplicação
Geolocalização
Se ativar a abertura automática por geozona, a aplicação usa a localização do aparelho, também em segundo plano, para saber quando se aproxima de um objeto. As coordenadas são processadas no próprio aparelho e nunca são enviadas ao servidor em claro. Sem nenhuma condição geográfica ativa, a localização em segundo plano nem sequer é pedida.
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 e Bluetooth
Para a condição de rede Wi-Fi, a aplicação verifica a que rede o telemóvel está ligado. Para a abertura direta por Bluetooth, procura um controlador por perto. Estes dados são usados no aparelho e nunca enviados ao servidor.
Dados do 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.
Um convidado não precisa nem da aplicação nem de conta: o acesso chega como ligação ou código QR, e a própria chave está dentro dessa ligação e nunca é enviada ao servidor.
3. Permissões da aplicação e para que servem
- Localização (em segundo plano) — só para as condições de geozona.
- Bluetooth — para abrir diretamente controladores perto de si.
- Notificações — mostrar o estado do trabalho em segundo plano e as mensagens de eventos.
- Telefone (chamadas) — para equipamentos que abrem quando se liga para um número.
- Arranque automático e isenção da otimização de bateria — para que o sistema não desligue a automação em segundo plano.
- 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.
As permissões são pedidas à medida que se tornam necessárias. Se não usar a funcionalidade correspondente, a permissão não é utilizada.
4. Dados no 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. Conta no site
A conta no site é precisa para guardar configurações, para a área de fabricante e funções afins. No registo guardamos o seu endereço de e-mail (para iniciar sessão, confirmar e recuperar a palavra-passe) e a sua palavra-passe como um hash irreversível. Não é precisa conta para usar a aplicação nem para o acesso de convidado.
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 no site
Nas páginas do site — exceto nas secções com dados privados: compilação de firmware, receção de chaves, autenticação e área de conta — usamos cookies e analítica web para perceber como os visitantes usam o site: visitas, fontes de proveniência, cliques e interação com a página. Nas páginas onde podem aparecer segredos ou chaves não se carregam cookies nem analítica.
Na sua primeira visita é mostrado um aviso de cookies. Pode desativá-los nas definições do navegador, bloqueando-os ou ativando um modo que limite o rastreio.
7. Partilha com terceiros
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. Conservação e eliminação
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. Crianças
O serviço não se destina a crianças com menos de 13 anos e não recolhe conscientemente os seus dados.
10. Alterações
Esta política pode ser atualizada. A versão em vigor está sempre disponível em entrixy.com/privacy; a data da versão está indicada em cima.
11. Contactos
Para qualquer pergunta sobre o tratamento de dados, escreva para hello@entrixy.com.