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.
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: We support secure email authentication (Hash/PKCE flows) and standard OAuth providers.
4. Artificial Intelligence (AI) Data Policy
ToWebForm utilizes AI exclusively to accelerate form creation by detecting fields on uploaded PDF documents.
Zero Data Retention for Training
We utilize Enterprise API agreements for our AI models. No customer data, uploaded PDFs, or form submissions are ever used to train the underlying AI models. All AI processing is strictly ephemeral; the document is processed in memory to generate the schema and the raw data is discarded by the model provider.
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.