Privacy information

Contact and your requests

For privacy questions or requests about your data, use the Help & contact form. There is a separate public form for account and related data deletion. We verify your authority before acting on an account-related request.

Website and request forms

The form saves your email and any other details you send, such as name, phone, property type, equipment model, area and message. We also record the request type, selected modules, interest in a QR + NFC sign, language and permitted campaign tags when present.

We use these details to respond, prepare a connection, provide support or handle a deletion request. The request is saved on the server; a failure to email the team does not erase it. Submitting a form does not subscribe you to marketing.

Accounts and property

Registration processes your email, name, password, property and entrance names, and account creation details. We store password and session token hashes, the shared trial and access dates, apartment or house names, and their module and camera selections. The primary user uses the same credentials for the website account and mobile app.

The primary user creates separate resident credentials by providing a name, email, password and apartment or house. Passwords are stored as hashes. Residents sign in to the mobile app and access the modules assigned to their address. The primary user can change the assigned address, reset a password or revoke access.

Visitor chats and photos

The visitor page processes the selected apartment or house, visit session, messages and photos, timestamps and chat status. Users assigned to that address can access the conversation. Messages and shared media are stored on the server.

The visitor browser uses session storage to resume a visit and a local database for its sending queue. Unsent text or photos may remain on the device until sent or cleared from that queue. Avoid sending unnecessary personal data in chat.

Notifications

When background notifications are configured and enabled by the user, the service processes the device notification identifier, platform, account association and delivery result. Apple or Google participates in delivering notifications, depending on the device. The public notification text is general; conversation content is loaded through authenticated access in the app.

Notification delivery depends on setup, the provider, internet connectivity and phone settings. Chat can also work without background notifications.

Camera, video and gate integrations

When add-ons are used, UKSEL processes device names and settings, connection addresses and credentials, camera images, gate commands and their results. Addresses and credentials saved in the website account are encrypted on the server. Passwords and keys are not shown when viewing settings. For RTSP video, the connection address and required credentials are sent only to an authorised user’s app, and the phone connects directly to the camera. The primary user assigns cameras to apartments or houses. Images are available to users with the relevant access, not to visitors on the public QR page.

The service server processes camera snapshots and short video segments for playback. The advertised service does not include a video recording archive. This does not mean the camera’s own system makes no recordings; camera users are responsible for their camera use and field of view.

Technical data and security

Technical request, session and error data are processed to run the service and prevent abuse. Technical outcomes for gate commands, access and notifications may be logged. Form submissions are protected by validation and rate limits.

Do not submit passwords, payment card details, API keys or secret access links through a public form.

Cookies and browser storage

Signing in to the website account uses the essential uksel_account cookie. Its default lifetime is 30 days; signing out removes it, and the server can revoke a session earlier. The cookie is HttpOnly, SameSite=Strict and Secure in production. Account session tokens are not stored in localStorage or sessionStorage. We do not use advertising or analytics cookies. Cloudflare may use essential security cookies.

When you dismiss this notice or manually choose a language, we remember that choice for 180 days in the same browser and website origin. We do not store a language selected automatically from your browser. You can reopen the notice using the Cookies link in the footer. Dismissing it is an acknowledgement, not permission for future tracking.

Browser localStorage stores only schema version 1 and an expiresAt timestamp under uksel:cookie-notice. The uksel:language entry also contains your chosen language: et, en or ru. These preference entries have no unique user identifier and are not sent to the server. LocalStorage does not expire automatically: the website removes an expired entry on your next visit. Clearing this website’s data in your browser also removes these choices.

Recipients and retention

Authorised people handling a request or running the service, and necessary infrastructure, email and notification providers, process the data needed for their tasks. You can ask about the data handling for a particular connection through the contact page.

Requests are retained as needed to handle them and meet applicable obligations. Conversation and media history is cleaned up according to the service’s configured retention period. Account deletion and automatic history cleanup are different operations. Use a privacy request to ask for details about retention or deletion.

Your rights and deletion

You can ask to access, correct or delete your personal data and make other requests available under applicable data protection law. Use the contact form or account deletion page. We may need additional information to verify your identity or connection to the account.

We explain in our response which data will be deleted and whether some data must be retained for a legal reason. This description does not limit your applicable rights.