Privacy policy

What we keep about you

Your phone number and your name. Your mobile number is your account — it is how we identify you and how access to a gate is granted to you, and we send a one-time code to it by SMS to sign you in. The app also asks you to choose a name before you can use it.
Your sessions. Which devices are signed in, when each was last used, and a value that ties a session to the device that started it. At most three sessions are live at a time.
Your access. Which gates you may open, your role at each, any validity window or schedule attached to it, and the label a gate's manager may write next to your name.
The gate's location — its own section below.
The gate-open log — its own section below.
Your view of the app. A nickname, icon, colour, and tile order you give a gate. These are yours alone; other people at the same gate do not see them.
Installation records, for installers — which gate was provisioned, when, and how it went.
Technical data. App version, device or browser type, IP address, and language. The IP address is used to limit abuse of the service. We never use it to work out where you are.

The gate's location

Every gate has an address, entered when it is installed. Where the installer's device allows it, we also store the gate's precise coordinates, captured once from that device while the installer is standing at the gate.

The position is stored for the gate, not tracked for the person. We do not follow your device, infer where you are or whether you are home, and we run no geofencing. Opening a gate through the app is not treated as evidence of where anyone was.
The device's position is read once, at that moment during the installation, and never again.
The installer can always type the address instead. Declining the location permission does not stop an installation.
Coordinates are shown to that gate's managers only — never to residents.
Where a gate is a private home, we treat its address and its coordinates as personal information.

The gate-open log

Every open is recorded: who opened which gate, when, over which connection, whether it was allowed or refused and on what ground, and how long the command took. Changes to a gate's operating state are recorded the same way.

Who can read it. You can see your own activity. A gate's managers can see that gate's log, because an access-control product has to be able to say who opened a gate. Nobody at SeloGate holds a standing right to read residents' data in the live service; access to it is scoped and audited.

How long we keep it. We have not set a retention period for this log. Rather than publish a period we do not keep to, we say so plainly: it is an open question, and this page will carry the period once it is settled. Deleting your account removes your record from it — see below.

Amazon Web Services hosts the service, in Frankfurt, Germany (eu-central-1). Everything above is stored there.
Inforu delivers the one-time sign-in code by SMS on our instruction, and your mobile operator carries it to your phone. Your number and the code itself are what reach them.
Google. While a gate is being installed, the address the installer types into the search box is sent from their browser directly to Google, which suggests matching addresses. If the gate's position has already been captured on that device, it is sent along with the text to bias the suggestions. Google receives this in the United States, and it acts as its own controller under its own terms rather than on our instruction — so this is a sharing of data, and we name it here. Typing the address without using the search box sends Google nothing at all.
The gate vendor's message service. Opening a gate over the internet sends the gate's code and the command through a message broker operated by the gate hardware's vendor, which is how it reaches your gate.

We do not sell personal data, and we share none of it for advertising or for anyone else's own purposes beyond what is named here.

What we do not do

No tracking. There is no advertising identifier, no cross-app or cross-site tracking, and nothing in SeloGate is linked to data from anyone else for advertising or measurement.
No analytics and no crash reporting. The app carries no analytics service, no session recording, and no crash-reporting service.
No address book. When you invite someone, you may pick a single contact through your phone's own picker. Only that one number reaches us; your contacts are never read or uploaded.
No camera images. Scanning a gate's QR sticker decodes it inside your browser. No frame, image, or video ever reaches us.
No presence detection over Bluetooth. Your phone can open a gate directly over Bluetooth when it is in range, without going through the internet. That connection carries the gate's own credential and the open command — nothing about you — and it is never used to work out where you are or whether you are nearby.
No continuous or background location, and no marketing messages.

Deleting your account

You can delete your account from inside SeloGate, and it is permanent — see how to delete your account. Your profile, your memberships and your personal views go; your history is anonymised.

One record survives, on purpose: a note that a deletion happened, holding no phone number and no name, so that restoring a backup can never bring your data back. It exists to keep the deletion true, and it identifies nobody.

Asking us about your data

You can ask to see what we hold about you, to correct it, or to have it erased. Write to contact@selogate.com. We may need to check that you control the phone number the account is on before we act on a request.

Two things we say plainly

Opening a gate through the app is not proof that anyone was physically at the gate. The log records that a command was sent and what the gate answered, and nothing more.

Setting a gate to stay closed stops the app. It does not stop someone holding a physical remote.

Changes, and how to reach us

If this page changes, the date at the top changes with it. Questions go to contact@selogate.com.