Sign-in events
Failed sign-ins in the apps and rejected sign-in renewals are written to a security log. Email address, IP address and user ID are stored there only as a hash.
Transparency
What gets logged
A trail for operations, security and troubleshooting.
Errors
Server errors and unexpected exceptions are reported to Sentry, with ingest in Germany, so they can be investigated and fixed.
Too many attempts
If too many sign-in attempts arrive within a short time, new attempts are rejected with a message to try again later.
Audit log
Important actions in the portal, such as changes to settings, are written to an audit log with the company, the user, the action and the time.
And what the logs are used for.
This page describes which events TapInn logs for operations, security, troubleshooting and audit, and what the logs are used for.
In short. TapInn logs what is needed to find errors, detect misuse and show who made important changes. Logging is not hidden surveillance of employees.