Skip to content
Entrixy Entrixy

Privacy Policy

What we process, what we do not, and why privacy is built into the architecture.

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. Who processes the data

The controller is the developer of the Entrixy project. For questions about data processing and deletion requests write to hello@entrixy.com.

2. Data in the app

Geolocation

If you enable automatic opening by geofence, the app uses the device location, including in the background, to tell when you are approaching an object. The coordinates are processed on the device itself and are never sent to the server in the clear. With no geo condition enabled, background location is not requested at all.

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

For the Wi-Fi network condition the app checks which network the phone is connected to. For direct opening over Bluetooth it looks for a controller nearby. This data is used on the device and never sent to the server.

Object data

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.

A guest needs neither the app nor an account: access arrives as a link or a QR code, and the key itself sits inside that link and is never sent to the server.

3. App permissions and what they are for

Permissions are requested as they become necessary. If you do not use the corresponding feature, the permission is not used.

4. Data on the server

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. Website account

A website account is needed for saving configurations, for the manufacturer area and related features. On registration we store your email address (for signing in, confirmation and password recovery) and your password as an irreversible hash. An account is not required to use the app or guest access.

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 on the website

On the site's pages — except the sections that carry private data: firmware building, key acceptance, authentication and the account area — we use cookies and web analytics to understand how visitors use the site: visits, referral sources, clicks and interaction with the page. Cookies and analytics are not loaded on pages where secrets or keys may be displayed.

On your first visit a cookie notice is shown. You can turn them off in your browser settings, by blocking cookies or enabling a mode that limits tracking.

7. Sharing with third parties

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. Storage and deletion

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

The service is not intended for children under 13 and does not knowingly collect their data.

10. Changes

This policy may be updated. The current version is always available at entrixy.com/privacy; the revision date is shown at the top.

11. Contacts

For any questions about data processing write to hello@entrixy.com.