Security and data

Communication and forms

The website uses HTTPS. The forms validate fields on the server, limit sizes and frequency, and verify each submission. Confirmation depends on an actual write to the database.

Administrative access

Reading and managing requests requires authentication and administrative permissions on the server. Changes require security checks from the superadmin and maintain history with author and date. Private responses are not cached publicly.

Minimization

The contact requests communication and context data. You do not use these forms to receive identification documentation or credentials. Abuse protection uses limited technical data and references to avoid duplicates.

Integrations and responsibilities

Each integration must define credential protection, permissions, data separation, validation of notifications and incidents. An internal approval, return screen, or repeat request is not a substitute for confirmation from the provider.

Report an incident

Check the domain and use contact to report a problem. Don't share private keys, recovery phrases, or authentication codes.