Skip to content

The technical depth — for your assessors

Promises that live in the mechanism

Visitor management meant to provide evidence has to do more than store data: it has to prevent it from being changed later, and it has to delete what must be deleted. This page describes how that's done here — not which standards it ‘complies with’.

Check it on your own workspace, not on this page.

Free, no credit-card details — with log, retention periods and roles to click through.

Set up your free trial

The log can't be doctored

Chained entries, no write rights

  • Every entry contains the checksum of the previous one. Whoever changes or removes an entry invalidates all the following ones — and that shows up at the audit, not only in the assessment.

  • The database itself sets the checksum, not the application. Even someone who took over the application couldn't produce a matching chain.

  • The application's operating identity has only the right to read and append on this table. No changing, no deleting — not for your administrators and not for us.

  • A nightly run records, outside your database, how far your log reaches. That also reveals when someone restores an older state — your own chain would then be internally consistent but incomplete.

Your data doesn't sit next to anyone else's

A dedicated database per customer

  • Each customer gets their own database — not a shared table where a column tells customers apart.

  • If a tenant's database is missing, the application refuses service instead of falling back to a shared one. A configuration error thus leads to an outage, not to a silent mixing.

  • Within the database, a row-level access rule applies on top. The operating identity has no right to bypass it — so the separation doesn't depend on every single query being written correctly in the code.

  • The area we operate from as the provider also sits in its own database. A customer can't see it, and a check run proves exactly that regularly.

Personal data has an expiry date

Retention, holds, deletion

  • You set the periods: when a visit is pseudonymised, when anonymised, when deleted. An hourly run carries it out — for the files in document storage too, not just database rows.

  • Reasoned defaults are preset, which you adjust with your data-protection officer. The application enforces upper and lower bounds, so no one accidentally sets it to never delete.

  • If a case is ongoing, a hold keeps the affected data and takes it out of the run. It requires a reason — otherwise the log later says that something was kept, but not why.

  • A transaction's IP address deliberately sits next to the log entry, not inside it. That way it stays deletable without breaking the chain.

Operation and recovery

Data centre in the EU, backup, maintenance window

  • Servers in a data centre in the EU: with our provider Contabo in Lauterbourg, France. The data in visitvia is processed only in the EU, with no transfer to a third country.

  • Daily backup of database and documents, kept for 30 days. Every day the most recent backup of each customer is automatically checked for completeness and integrity.

  • Updates run in an announced maintenance window: back up first, then migrate, and reopen only on success. Because nothing is written during the window, the backup at its start is a restore point with no data loss.

  • A restore checks that the area is ready for use afterwards and has a guided way back if something goes wrong.

Accounts

Second factor, roles, four-eyes principle

  • For every admin account the second factor is mandatory, not a setting.

  • If a device is lost, there are recovery codes — and afterwards a way to register a new device. A recovery that works only ten times and then locks the account for good is none.

  • Roles separate who sees visitors, who changes documents and who touches settings. Particularly consequential steps can be placed under the four-eyes principle.

  • Repeated failed attempts lead to staggered lockouts and trigger an alert. The sign-in always responds the same way — an attacker learns nothing from it about whether an account exists.

Encrypted where it counts

Transport, secrets, passwords

  • The connection between browser and application is encrypted throughout (TLS). That also applies to the check-in terminals at reception.

  • Secrets in the database aren't in plain text: the keys for two-factor sign-in are encrypted with AES-256-GCM — with a key derived per customer and bound to the specific row. An entry copied out of the database is worthless elsewhere.

  • Passwords are never stored, only kept as an Argon2id hash — the same method that also applies to the recovery codes.

  • The background queue also runs only over an encrypted connection. The application won't even start if it's missing: that's where check-in codes and invitation links sit.

When you leave

Cancellation, export, deletion

  • Your data is yours. The visitor list and log can be exported at any time, including at the end.

  • After the agreed period expires, your area disappears completely: the database is discarded, the files in storage are removed, and so is the log.

  • That nothing is left behind is verified by a dedicated test run — one that checks the promise rather than repeating the code's assumptions.

The honest comparison

How to recognise an audit-proof system

Visitor management on paper and a general visitor app both solve something — just not the same thing. Here's what matters, before it matters.

Comparison of paper and Excel, general visitor apps, and visitvia across seven requirements
RequirementPaper & ExcelGeneral visitor appsvisitvia
Prove a single visit in an assessment
not met: search the binder
limited: a list, usually without proof
met: log with a checksum
Signed briefing as a document
limited: paper, loosely filed
limited: depends on the vendor
met: a signed PDF per visit
Later changes ruled out
not met: the sheet can be swapped
not met: the record can be edited
met: chained, with no write access
Retention periods run on their own
not met: no one clears it out
limited: depends on the vendor
met: hourly retention run
Separation from other customers
met: your own binder
limited: usually a shared database
met: a dedicated database per customer
Data stays in the EU
met: the front desk
limited: often outside the EU
met: a data centre in the EU (France)
Effort at reception per visitor
not met: sign in, call, follow up
met: largely self-service
met: self-service, under 2 minutes

The middle column describes the common state of things, not one particular product: there are good visitor apps, and some can do more than this says. Ask every vendor three things: Can anyone change entries after the fact? Is our data kept separate from other customers'? And where exactly do the servers stand?

Standards and assessment catalogues

Where visitvia connects to your assessment scope

The measures around reception appear in the catalogues our customers are assessed against — and there they're the part that runs on paper the longest.

Emergencies & safety

ASR A2.3 · DGUV

Evacuation and assembly point · Briefing of outside firms · Accident records

At the assembly point, completeness counts — explicitly including visitors and outside firms. And after an accident, what counts is who was there and whether they were briefed.

Information security

TISAX® · ISO/IEC 27001 · BSI IT-Grundschutz

Controlled access · External parties under confidentiality · Logging

Automotive and IT check the same thing at reception: who came in, were they under obligation, is it on record? What's asked for is proof of a single visit.

Food

IFS Food · BRCGS

Food defense · Visitor log · Hygiene for visitors

The site visit must be documented, access controlled, and visitors follow the same hygiene rules as staff. The auditor looks at the log.

Construction

BaustellV · Minimum Wage Act

Who was on the grounds · Coordinating the trades · Evidence for authority and insurer

Who was on the site must be documented — for coordinating the trades, for the authority, and as a decisive factor when something happens.

This overview is guidance, not an audit result: what applies to you is decided by your auditors, authorities and safety officers. visitvia supplies the evidence — judging it is someone else's job.

You can provide this evidence starting tomorrow.

The free trial shows you exactly the evidence that's asked for.

Set up your free trial

What we don't claim

No seal that doesn't exist. visitvia is not ‘TISAX-certified’ — no software can be. You are the one assessed; we make sure you have something to present at this point.

No absolute security. Every piece of software has flaws, and whoever promises otherwise either hasn't looked or isn't telling the truth. What we can promise: that the important assurances don't hang on good will but on mechanism that can be checked.

No legal advice on your retention periods. How long you may and must keep visitor data is decided by your data-protection officer and your TISAX consultancy. We provide reasoned defaults and the mechanism to keep to them.

Vertrauenszeichen „IT Security made in Germany“ des TeleTrusT — Bundesverband IT-Sicherheit e. V.
Vergeben vom TeleTrusT — Bundesverband IT-Sicherheit e. V. Das Zeichen steht unter anderem für Entwicklung und Sitz in Deutschland und für die Zusage, keine verdeckten Zugänge einzubauen.

Documents for your assessment

Description of the tamper-proofing, tenant-separation concept, retention-and-deletion concept, data-processing agreement with the technical and organisational measures.

info@gefim.de

FAQ

What assessors want to know first

Is visitvia TISAX-certified?

No. TISAX assesses sites and organisations against the VDA ISA catalogue — there is no TISAX seal for a piece of software, neither for us nor for anyone else.

What we provide is the evidence for the controls that concern your reception, and the documents for it: how tamper-proofing is established, how tenant separation works, which data sits where. For your own assessment, request these documents from us — they're written for it.

Do you need a data-processing agreement?

Yes. We process visitor data on your behalf, so Article 28 GDPR applies. You get the agreement together with the technical and organisational measures before signing — not as an attachment some time later. For the free trial there is no data-processing agreement: real visitor data does not belong there. We process the sign-in data of the users of a trial workspace ourselves, as controller.

Who on your side can see our data?

For operations there is a separate area with its own accounts, its own sign-in and its own log. It serves customer administration — creating, blocking, cancelling — not looking into your visitor lists. Every step in it is logged, and the operations log is separate from yours.

What happens in an outage or a security incident?

Outages go into their own log and trigger an alert. Alerts about one delivery channel always go via another — sending a warning ‘your Microsoft connection is expiring’ via Microsoft would fail to arrive exactly when it's needed. In the event of a reportable incident under Article 33 GDPR we inform you without delay; the deadlines run with you as the controller.

Can we check this ourselves?

Yes. You get the technical description of the tamper-proofing, the description of tenant separation and the retention concept as documents. If you want to run your own security tests, talk to us first — we have nothing against a test environment, but we do against unannounced tests on the production system.

Nothing convinces faster than your own workspace.

See the log, retention periods and roles in your own demo area.

How we handle your data on this website is in the privacy policy. Short version: there's nothing to collect here.