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

Legal

Privacy Notice

How personal data is handled when you visit or use KeyInOut.

Last updated: 20 October 2026

On this page
01Who is responsible for your data? 02Personal data we process 03Why we process data and our legal bases 04Emails and reminders 05QR labels and public return information 06Service providers and recipients 07International transfers 08Retention 09Your data-protection rights 10Cookies and analytics 11Security 12Changes and contact 13Digital receipts and signatures 14Mobile apps, camera and product analytics 15Deletion, exports and backups 16Marketing – Meta Pixel
Privacy and data use

KeyInOut is operated by AT Group AB (559604-9147), Sweden. Billing data includes organisation and contact details, tax identifiers, invoices and payment records. Card payments are processed by Stripe; invoices can be paid by bank transfer. KeyInOut does not store full payment-card numbers.

01Who is responsible for your data?

For account administration, service security, communications with KeyInOut and operation of the KeyInOut website, the controller is AT Group AB (559604-9147), Sweden, operating KeyInOut. Privacy enquiries can be sent to privacy@keyinout.com. General support enquiries can be sent to support@keyinout.com.

For personal data that a customer organisation enters into its workspace — for example employee or contractor details, key-holder records and key activity — the customer organisation normally determines why and how that data is used and is therefore the controller. KeyInOut processes that workspace data on the customer's behalf as a processor. The Data Processing Agreement describes that relationship.

02Personal data we process

  • KeyInOut is operated by AT Group AB (559604-9147), Sweden. Billing data includes organisation and contact details, tax identifiers, invoices and payment records. Card payments are processed by Stripe; invoices can be paid by bank transfer. KeyInOut does not store full payment-card numbers.

Passwords are not stored in readable form; password hashes are stored instead. Verification, reset and invitation secrets are stored as hashes where applicable.

03Why we process data and our legal bases

Where KeyInOut acts as controller, account and service data is processed to provide the requested service and administer accounts (performance of a contract or steps requested before entering one). Security logs, abuse prevention, service reliability and limited operational records are processed where necessary for our legitimate interests in protecting and operating KeyInOut. Data may also be processed where necessary to comply with a legal obligation.

Where KeyInOut acts as processor for a customer organisation, the customer determines the applicable purpose and legal basis. Customers are responsible for ensuring they have a lawful basis for personal data they enter into KeyInOut and for providing required information to their staff, contractors or other data subjects.

04Emails and reminders

KeyInOut sends transactional messages needed for account verification, password reset, invitations and service operation. A workspace may also configure overdue-key reminders. Reminder recipients and settings are controlled by the workspace. KeyInOut does not currently send third-party advertising through the service.

05QR 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.

06Service providers and recipients

Personal data is disclosed only where needed to operate the service, comply with law, protect the service or follow a customer's instructions. KeyInOut currently relies on infrastructure providers for web/database hosting and transactional email delivery. Our current infrastructure is hosted through Simply.com. We use Google Analytics 4 only after the visitor has consented to optional analytics. Stripe is used for subscription payment processing.

Our list of processors may change as KeyInOut develops. Material changes affecting customer workspace data will be reflected in this notice and, where applicable, the DPA/subprocessor information.

07International transfers

KeyInOut is operated from Sweden. We aim to use service infrastructure appropriate for an EU/EEA service. If a provider requires personal data to be transferred outside the EU/EEA, an applicable GDPR transfer mechanism and safeguards must be used where required. We will update this notice when new providers materially change the transfer position.

08Retention

Account and workspace data is generally retained while the workspace exists. Workspace owners can export data and can delete the workspace using the controls provided in KeyInOut. Deletion removes workspace data from the live application subject to technical backup cycles, security records that must be retained for a limited period, and any retention required by law. Authentication, delivery and security logs are kept only for as long as reasonably needed for their operational or security purpose.

Operational logs and backups are retained according to the production hosting, security and backup configuration. Backup copies may remain for a limited period after data is removed from the live application and are not intended for normal application use.

09Your data-protection rights

Where KeyInOut/AT Group AB (559604-9147) is the controller, you may have rights under the GDPR including access, rectification, erasure, restriction, data portability and objection, depending on the circumstances and legal basis. Contact privacy@keyinout.com to make a request.

If your request concerns data entered by your employer or another customer organisation, please contact that organisation first because it is normally the controller. KeyInOut will assist the customer as required by the DPA.

You also have the right to lodge a complaint with the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, IMY) or another competent supervisory authority.

10Cookies and analytics

KeyInOut uses technical browser/session mechanisms needed to keep users signed in securely and to operate the service. With consent, KeyInOut also uses Google Analytics 4 to understand website traffic and usage. Analytics is optional and the choice can be changed through Cookie settings.

11Security

We use technical and organisational measures intended to protect personal data. These include tenant-scoped access, role-based permissions, HTTPS, hardened sessions, CSRF protection, prepared database statements and minimised QR data. More information is available on the Security page. No online service can guarantee absolute security.

12Changes and contact

We may update this notice as KeyInOut develops, including when new infrastructure, analytics or payment providers are introduced. Material changes will be reflected by updating the date above. Questions about privacy can be sent to privacy@keyinout.com.

13Digital receipts and signatures

When customers use digital receipts, we process records of the handover: the recipient’s name and any organisation and contact details, relevant keys or bundles, timestamps, terms, notes and signature. Bundle receipts may include a snapshot of their contents. Records may be included in PDF receipts accessible to the customer. If the customer records an identity check, we also process the check indicator and the specified document type. The customer organisation determines the purposes and legal basis and provides the required information to recipients.

14Mobile 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.

The apps use PostHog for product analytics through the EU endpoint eu.i.posthog.com. App code records events such as app opening, successful sign-in, scans, scan errors, handovers and returns. We do not add names, emails, phone numbers, key names, QR contents, signatures or receipt contents as custom event properties. The analytics tool may also process an app instance identifier and technical app and device information. This is separate from website Google Analytics and browser cookie choices.

15Deletion, exports and backups

Receipt records and other workspace data are processed on the customer’s behalf under their instructions and the Data Processing Agreement. PDFs or exports downloaded by the customer may remain with the customer after deletion in KeyInOut. Customers are responsible for their own copies. Deletion from the active service does not mean all backups are overwritten immediately. Billing records subject to statutory retention are handled separately from operational workspace data.

16Marketing – Meta Pixel

With separate marketing consent, we use the Meta Pixel from Meta Platforms Ireland Limited on public marketing pages, registration and confirmation of a newly created trial. It measures page views and trial starts and may be used for advertising on Facebook and Instagram. Meta receives information including the visited URL, IP address, browser information and cookie identifiers. The pixel is not loaded in the signed-in key management workspace. We do not send keys, recipients, signatures or receipts as event data. _fbp and _fbc are marketing cookies normally stored for up to 90 days. keyinout_marketing_consent stores your choice for 180 days. You can change or withdraw consent through Cookie settings. Meta may process data outside the EU/EEA. See Meta’s Privacy Policy for processing and international transfers.

© 2026 KeyInOut
Security Terms DPA Cookies Create account