Information security

Our controls cover account information, form structures, versions, submitted responses and temporary data required to operate the service.

Public forms are accessed through non-enumerable links. Anyone holding a link may access the form while it is available, so creators should share it only with the intended audience.

The platform includes the following controls, among others:

• Passwords derived with scrypt and a random salt; passwords are never stored as readable text.
• Opaque, revocable sessions stored temporarily and delivered through HttpOnly, SameSite=Strict cookies.
• Random public identifiers that do not expose internal database identifiers.
• Server-side authorization protecting forms, templates, responses and account settings.
• Request limits, payload size limits and controls against automated or abusive submissions.
• Security headers, controlled origin policy and validation of submitted data.

Creators must limit questions to necessary data, avoid requesting sensitive information without proper justification and authorization, control who receives a public link and close a form when its purpose ends.

Each user should use a unique password, protect their devices, close unrecognized sessions and promptly report suspected unauthorized access.

Public communications must operate exclusively over HTTPS. Persistent information is stored in PostgreSQL, while temporary session, rate-limit and cache data is managed in Redis. Access to these components must remain restricted to authorized infrastructure.

When an incident is confirmed, the operator will assess its scope, contain the risk, preserve necessary evidence and provide notices required by applicable law. We do not publish details that could facilitate exploitation of an active vulnerability.