GateVia
◆ Security & privacy

How GateVia protects access, data, and your residents.

Member links and tokens

When you grant a member access, GateVia mints a 16-character hex token (cryptographically random, ~64 bits of entropy). The token is scoped to one gate, can carry a schedule, an expiry date, and a max-usage cap. Revoking a token takes one click — the link stops working immediately, and any subsequent attempt is logged as a failed try.

Audit log

Every open, every admin action, every change of permission is recorded. Each entry stores the actor, the target, the IP, the user-agent, and the exact timestamp. Admins can export the full log anytime (CSV) and pipe Slack notifications to a channel for live monitoring.

Authentication

Account-based access is delegated to a trusted, audited third-party identity provider — we never see or store passwords. Members without an account use the magic-link path, where the link itself is the credential and is bound to the original recipient's email at the time of redemption.

Hosting & data residency

GateVia is hosted in the EU. The database, the API, and the marketing site all run on EU-located infrastructure. We don't move data outside the EU, we don't process data outside the EU.

Rate limits & abuse protection

Both the network edge and the application layer enforce rate limits. Failed open attempts are exponentially throttled. Repeated invalid tokens trigger automatic alerts to the admin.

GDPR & your data

You can export your data and your residents' data at any time. Members can delete their account from the Settings page — that endpoint cascades through all memberships and revokes every token they hold. We minimise PII: name and email are all we keep about a member.

What we don't do

  • We don't read SMS messages.
  • We don't talk to the gate hardware directly — only via standard CallerID-based authorisation.
  • We don't sell or share data. There's no ad network, no third-party analytics on the app side.