Please wait
Preparing your Gatepass workspace
Loading workflows, responses, channels and verified records with a clean secure view.
Last reviewed
June 15, 2026
Plain-language policy
This page explains how Gatepass operates for account owners, workspace members and people submitting records through forms, ID capture projects and event registrations. Organizations with special legal or regulatory requirements should review these terms with their own adviser.
Security approach
Gatepass is designed to protect accounts, workspaces, submissions, files, generated records and billing activity through layered product and operational controls.
- Authentication and session controls for account access.
- Workspace roles and permissions for team access.
- Audit and usage records for important actions where available.
- Operational monitoring to detect errors, abuse and security issues.
Account and workspace security
Customers are responsible for protecting their own accounts, devices, team invitations and downloaded exports. Workspace owners should review who has access and remove members who no longer need it.
- Use strong passwords and secure email accounts.
- Do not share login credentials.
- Invite only trusted team members.
- Review workspace roles and remove inactive users.
Uploads and exports
Gatepass may store uploaded photos, files, signatures, ID records, event badges, tickets and reports. Downloaded exports leave the Gatepass platform and become the customer's responsibility to secure.
- Request uploads only when needed.
- Limit access to sensitive files and generated documents.
- Store exported reports in secure locations.
- Avoid sending private exports through unsecured channels.
Verification and public links
Gatepass may provide verification pages, QR codes, public links and generated reference records. Customers should test public links and avoid exposing private projects accidentally.
- Check project visibility before sharing links.
- Archive or close projects when collection ends.
- Use verification responsibly and do not misrepresent generated records.
- Report suspicious or unauthorized public links quickly.
WhatsApp security
Where WhatsApp is enabled, link codes, session state, message content and uploaded media may be processed to support account linking, form sessions and support conversations. Users should protect their phones and report unauthorized access.
- Do not share link codes with unauthorized people.
- Use CANCEL or support if a session was started by mistake.
- Unlink a number if it should no longer access the account.
- Be careful when sending sensitive files through WhatsApp flows.
Reporting security concerns
If you suspect unauthorized access, account takeover, harmful public forms, leaked exports or suspicious billing activity, contact support with clear details as soon as possible.
- Include account email, workspace, form or event name where relevant.
- Describe what happened and when it started.
- Attach screenshots or references if helpful.
- Do not publicly share private keys, passwords, exports or sensitive records.
Security reference
Common security areas in Gatepass.
| Area | How it applies | Note |
|---|---|---|
| Account access | Login, sessions, role checks and account status controls. | Customer and platform responsibility |
| Workspace roles | Owners/admins control who can view, review, export or manage projects. | Customer controlled |
| Uploads | Files and photos are stored for project use and review. | Handle carefully |
| Exports | Downloaded data is outside Gatepass after export. | Customer responsibility |
| Monitoring | Logs and security signals support abuse prevention and reliability. | Operational |
Need help?