Security and data
Security and data protection
For your IT department and your data protection officer: the list of measures in place. We only write here what the code enforces.
In short
- At the scan, the shop sees the first name, last name, photo, company and the result; when the card is valid, also its end date (if there is one) and the shop's current offers. Never the email or the employee ID.
- Nothing to install: no app, no device. The shop's phone is only used to check cards.
- Application and data hosted in Switzerland. No advertising, no trackers.
The only sign-in link we send is the one in your invitation, valid once. After that: a code, never a link. Never give your code to anyone, not by phone and not by message.
Hosting
- Application and database hosted in Switzerland, by a Swiss hosting provider.
- HTTPS mandatory: HSTS (six months, subdomains included) and redirection from HTTP to HTTPS.
- Internal folders (configuration, code, uploaded files, logs) are closed to any web access.
- Backups: those of the hosting provider, in Switzerland, kept for 30 days, with access restricted to the operator.
Accounts and secrets
- Password-free back office. First sign-in: a personal single-use link, valid for 7 days. After that, a 6-digit code every time, sent by email, valid for 15 minutes, single use, 5 attempts at most. No password can therefore leak or be guessed.
- Code requests limited per address and per device, identical response whether an account exists or not (no account enumeration).
- Optional passkey sign-in (Face ID, fingerprint). Every sign-in from a new device is reported by email, with a “This wasn't me” button that closes all sessions.
- Links and sessions: 256-bit random tokens, stored only as a SHA-256 hash. 6-digit codes: HMAC hash with a server key, limited attempts.
- A card's QR code holds a 256-bit random identifier, without any personal data.
- Back-office sessions: closed after 30 minutes of inactivity, 12 hours at most (8 hours for the super administrator). Alert email when signing in from a new browser.
- Chained audit log: each line is linked to the previous one by an HMAC with a server key. A change or a deletion is detectable. The head of the chain is copied outside the database every hour, so a truncation is also detected.
Bots and abuse
- Server-side rate limits, stored in the database, on sign-in, codes, shop phone activation, forms, emails and imports.
- Invisible anti-bot proof of work on public forms, with honeypot and signed timestamp. Never a puzzle to solve.
- Temporary blocking of IP addresses probing trap paths (IPv6 grouped by /64).
- Neutral messages: a form never reveals whether an email address exists.
Separation between companies
- The current company always comes from the session, never from a URL parameter. Every business query filters by company.
- An identifier from another company returns "not found": nothing is revealed.
- An administrator never sees the name of another company. Automated tests check this separation.
Data and retention periods
- An employee's data: number, first name, last name, email, language, expiry date and, if the company wishes, a photo.
- Photo re-encoded on upload (EXIF and GPS metadata removed) and served by a script with access control. It is not sent to Google Wallet unless the operator turns this option on (off by default).
- At the scan, the shop sees the first name, last name, photo, company and the result; when the card is valid, also its end date (if there is one) and the shop's current offers. Never the email or the employee ID. A card not accepted at that shop shows no personal data.
Periods
- Link between a scan and a person
- 90 days, then erased (statistics remain, without the person)
- IP address in the audit log
- 30 days
- Codes received by email
- valid 15 minutes, deleted one day after expiry
- Unused shop phone
- automatically deactivated after 180 days
- Deactivated card
- permanently deleted after 90 days (record, photo, link to scans)
- Right of access and erasure
- copy of an employee's data by their HR (without the details of checks); full copy and immediate deletion by the operator, on request
Compliance (Swiss FADP)
- Each client company is the controller; IDemployee acts as processor.
- Data minimisation: only the data needed for the card is requested; email and photo are optional.
- The privacy policy details the data, the cookies and your rights.
Processors and external services
- Swiss hosting provider: application, database, sending of emails.
- Google Wallet (optional, if the employee adds the card): first name, last name, company and its logo, validity date and verification address stored by Google, outside Switzerland. No photo, unless the operator turns the option on.
- Apple Wallet (optional): the card is on the phone; updates go through Apple's notification service.
Report a vulnerability
Found a vulnerability? Write to the address given in our security.txt file (RFC 9116). Please do not run destructive tests or access other people's data.
A question from your IT department?
Write to us: we answer security questionnaires and requests from your data protection officer.