KeyInOut
🌐 English ▾
English ✓ Svenska Deutsch Norsk Dansk Français Español Nederlands Suomi Italiano Polski Português
← Home

Trust

Security at KeyInOut

Security principles and safeguards used to protect the KeyInOut service.

Last updated: 20 October 2026

On this page
01Workspace isolation 02QR labels and public return information 03Authentication and passwords 04Sessions and request protection 05Database and application safeguards 06Website resources and external services 07Data minimisation 08Roles and auditability 09Infrastructure and secrets 10Reporting a vulnerability 11Digital receipts and signatures 12Mobile apps, camera and product analytics
Security is an ongoing process

This page describes safeguards currently implemented in KeyInOut. It is not a certification, penetration-test report or guarantee that vulnerabilities cannot exist.

01Workspace isolation

KeyInOut is a multi-tenant service. Operational database queries are designed to scope workspace records to the authenticated company. Administrative permissions are enforced server-side rather than relying only on hidden interface controls.

02QR labels and public return information

The QR code contains a link with a random identifier. Codes such as ET-0001 are separate, persistent label numbers within the customer workspace. Self-printed labels do not print key names, references or locations. Identifiers can be linked to records in the service and are not fully anonymous. Purchased QR tags use a separate marking.

If the customer enables the public return page, anyone with the QR link can view the return details the customer chooses to publish: organisation name, return address, phone, email and an optional message. The customer can change the details or disable the page. The public page does not display key names, references, holders or activity history. The customer is responsible for having the right to publish any personal data in these details.

03Authentication and passwords

Passwords are stored using PHP's password-hashing facilities, using Argon2id when available. Password-reset, email-verification and invitation links use high-entropy tokens and store token hashes rather than reusable plaintext secrets where applicable. Login attempts are rate limited.

04Sessions and request protection

Authenticated sessions use hardened PHP session settings including HttpOnly cookies, SameSite protection, secure cookies on HTTPS and session-ID regeneration. State-changing application requests use CSRF protection. Sensitive authentication/token pages use restrictive caching/referrer behaviour.

05Database and application safeguards

Database access uses prepared statements with native PDO prepares. User-controlled output is escaped for HTML contexts. Critical key check-out/check-in operations use database transactions and row locking to reduce race conditions such as double check-out.

06Website resources and external services

The service is intended for HTTPS. The web application sends security headers including CSP, HSTS over HTTPS, frame restrictions and MIME-sniffing protection. Many resources are local, but external resources are used: the web scanner loads jsQR from jsDelivr and Google Analytics loads after consent. App analytics is described in the Privacy Notice.

07Data minimisation

QR codes do not embed key names, locations or holder details. Reminder emails intentionally minimise operational key information. User-facing workspace exports exclude password hashes and authentication-token hashes. Payment-card data is not currently collected by KeyInOut.

08Roles and auditability

Workspace roles separate owner/administrator capabilities from ordinary member access. Key handovers and returns are recorded in activity history, and administrative actions are logged where implemented. These records support accountability but do not replace a customer's own access-control procedures.

09Infrastructure and secrets

KeyInOut uses hosted infrastructure for the web application, database and transactional email. Sensitive email configuration is designed to stay outside the public web root. Safeguards and deployment configuration are reviewed on an ongoing basis.

10Reporting a vulnerability

If you believe you have found a security issue, email security@keyinout.com with enough information for us to reproduce and assess it. Please avoid accessing data that is not yours, disrupting the service, using destructive testing, or publicly disclosing details before we have had a reasonable opportunity to investigate and address the issue.

For privacy matters rather than security vulnerabilities, use privacy@keyinout.com.

11Digital receipts and signatures

PDF receipts are downloaded through authenticated, company-scoped access checks. The stored file’s SHA-256 checksum is verified before download. This checks file integrity; it does not guarantee the signatory’s identity.

12Mobile apps, camera and product analytics

The mobile apps use the same KeyInOut service for sign-in, key management and recording handovers and returns. Camera permission is used for QR scanning.

© 2026 KeyInOut
Privacy Terms DPA Cookies Create account