Security & Compliance

This document outlines the security architecture, data protection mechanisms, and compliance postures implemented by ToWebForm. It is designed to assist enterprise customers and vendors during standard security reviews and risk assessments.

1. Data Protection & Encryption

ToWebForm employs a defense-in-depth approach to data protection, utilizing strict encryption both at rest and in transit.

• Data in Transit: All data transmitted between the client, our application servers, and our databases is encrypted using TLS 1.2 or higher.
• Application-Layer Encryption (Data at Rest): ToWebForm implements strict AES-256-GCM application-level encryption for all sensitive end-customer data before it is written to the database or storage bucket. This ensures that even in the event of a raw database compromise, the sensitive data remains cryptographically secure. Encrypted fields include form payloads, PII, verified contact info, signature audit trails, and submission IP addresses. Note attachments and submission images are encrypted prior to upload, decrypted server-side only during generation, and immediately purged.
• Zero-PII Stateless Fill & Download Mode (Team Plan): For regulated workflows, court filings, notary documents, or strict data-minimization policies, administrators can configure any form in Fill & Download Official PDF Only (Zero-PII Storage Mode). In this mode, respondent answers (and optional bidirectional translations) are processed and stamped onto the original PDF strictly in volatile server memory and streamed directly back to the respondent's browser without writing any respondent answers or PII to the database or storage buckets.

2. Infrastructure & Hosting

• Hosting & Edge Compute: The application is hosted on an enterprise-grade cloud platform utilizing serverless and edge functions, providing built-in DDoS protection, a Web Application Firewall (WAF), and global CDN distribution.
• Database: Our data layer uses a managed PostgreSQL service with underlying Transparent Data Encryption (TDE), automated backups, and strict network isolation.
• Rate Limiting: All public endpoints and form submissions are protected by global edge-based rate limiting to prevent abuse, brute-force attacks, and application-layer DDoS.

3. Access Control & Data Isolation

ToWebForm is a multi-tenant platform architected with strict logical data isolation to ensure tenant data never bleeds across organizational boundaries.

• Row-Level Security (RLS): We leverage native PostgreSQL Row-Level Security. Every query strictly enforces access via an organizational ID using a secured database function. A user authenticated in Organization A physically cannot query data belonging to Organization B at the database kernel level.
• Role-Based Access Control (RBAC): Access within an organization is strictly governed by RBAC, allowing strict permissions for Members, Admins, and Owners.
• Authentication: Users sign in with email and password, emailed sign-in links (Hash/PKCE flows), or Google or Microsoft sign-in. Email and password accounts confirm their address before they can publish forms or send anything to other people.
• Two-Factor Authentication: Users can add a 6-digit code from an authenticator app to their sign-in, with one-time backup codes for a lost phone. Owners and admins can require two-factor for everyone in their organization who signs in with email and password, and see who has it turned on. They also choose whether a device can be remembered for 7, 14 or 30 days after a code is entered, or ask at every sign-in. Remembering is off on any device unless the person ticks "Remember this device", can be forgotten from Settings, and ends when the authenticator changes. It is enforced in the database as well as the application: until the code is entered on a device that is not remembered, a session cannot read or change organization data. Users receive a security email whenever two-factor is turned on or off or a backup code is used, and ToWebForm's own administrative accounts always use it.

4. Artificial Intelligence (AI) Data Policy

ToWebForm utilizes AI exclusively to accelerate form creation by detecting fields on uploaded PDF documents.

5. Development & CI/CD Security

• Strict Quality Gates: All code must pass strict static analysis, type checking, and business logic test suites before deployment.
• No Direct Migrations: Database schema modifications are strictly managed via version-controlled files and executed exclusively through secure administrative channels by authorized personnel, preventing rogue schema mutations.