1) Form owners choose what to ask
- • Each team decides which fields appear on a form.
- • You can keep forms minimal or collect more detail when needed.
- • Optional fields can reduce over-collection.
Privacy page
Privacy controls in plain language
PasaForm helps teams collect registrations and submissions with clear controls. This page explains what the product can capture, what form owners can configure, and how teams can keep ownership of their data.
2) Consent notices can be shown
- • Form owners may display consent or disclosure text on forms.
- • Notices can explain why data is requested and how it will be used.
- • Teams can adapt wording to their own policies.
3) Secure cookies where needed
- • Secure cookies may be used for core product functions.
- • Examples include session continuity and sign-in related behavior.
- • Cookie usage depends on enabled features and workflow design.
4) Browser and device metadata for review
- • Basic browser and device metadata can support review workflows.
- • Teams may use this context when checking submissions.
- • Collection depends on configuration and operational needs.
5) IP and location metadata when enabled
- • IP and location-related metadata may be available when enabled.
- • Teams can use this for anti-abuse checks or operational review.
- • Availability depends on deployment setup and chosen settings.
6) Exports keep your records usable
- • Data exports help teams work with submissions in external tools.
- • Exported records can support reporting, audits, and internal handoffs.
- • Teams maintain practical access to their collected data.
7) Self-hosting for infrastructure control
Organizations that self-host PasaForm can manage their own infrastructure choices, deployment environment, and operational controls. This supports teams that need stronger ownership of where systems run and how data handling is managed internally.
Need help mapping these controls to your workflow?