Privacy

DraftPlaceholder text. Not legal advice and not yet in force.

Last updated: Not yet published

Two kinds of person

Entry Keep processes data about two groups, and the rules differ. Customers are the organizations that run a gate and the staff who sign in. We are the controller for their account data. Visitors are the people checked in at a gate. The customer is the controller for those records, and Entry Keep is a processor acting on their instructions.

What is recorded at a check-in

A visit holds the visitor's name, the host or host unit they came to see, the times of check-in and check-out, and the staff account that recorded each. A site can additionally enable a document-number field; it is off by default.

What this website collects

No analytics, no advertising pixels, and no session replay. Server logs hold ordinary request metadata for a short retention window. Fonts are served from this origin, so no third party learns that you visited.

Retention

Visit records are kept for the window in the customer's plan or agreement, then deleted. Deletion requests from a visitor are routed to the customer, since they decide what their site is required to keep.

Your rights

Access, correction, deletion, and objection, exercised against the controller. If you were checked in somewhere and want your record removed, contact that site; if you cannot reach them, write to us atinfo@entrykeep.com and we will route it.

Subprocessors

A current list belongs here, naming each subprocessor and what it does, including the authentication provider and the hosting and database providers.