Our Commitment to Transparency
This page reflects what is actually implemented in our platform today, what is actively being improved, and what is on our roadmap. We will not claim controls we have not built.
Compliance & Certifications
GDPR
EU data protection — DPA, SCCs, and user rights framework in place
CCPA
California Consumer Privacy Act — no data sale, rights requests supported per our Privacy Policy
NJ DLRA
New Jersey Data breach notification obligations met
Our Security Commitment
PDFFillr is designed specifically for the security requirements of private equity and financial services firms. Our customers process KYC packets, fund subscription agreements, LP data, and regulatory filings through our platform. The controls described on this page reflect that responsibility.
Security is not an afterthought at PDFFillr — it is a foundational design principle that informs our infrastructure choices, authentication architecture, and data handling practices at every layer of the stack.
Authentication & Session Management
How users and systems authenticate to PDFFillr — verified from production code.
Auth0 OIDC · JWT RS256 · verified via JWKS endpoint
Google OAuth via Auth0 — token never stored in browser
httpOnly cookies — inaccessible to JavaScript, not extractable by XSS
15 minutes — short-lived by design
30 days with automatic rotation on each use
Family-based replay detection — stolen refresh tokens are revoked chain-wide
Auth0 client-credentials flow for M2M integrations
Secret keys SHA-256 hashed before storage — never stored in plaintext
httpOnly: true · secure: true · sameSite: none · domain-scoped
httpOnly cookie delivery means your session cannot be stolen via JavaScript injection. Refresh token rotation with replay detection means a stolen token is detected and invalidated on its next use.
Encryption
How data is protected at rest and in transit.
Encryption in Transit
LiveAll traffic between clients and our servers is protected with TLS 1.3. Auth0 communication enforces HTTPS at the SDK level. TLS 1.0 and 1.1 are not supported.
Encryption at Rest — S3
LiveAll documents are stored in AWS S3 with server-side encryption (AES-256) enforced via bucket policy. No unencrypted writes are permitted at the bucket level.
Credential Hashing
LiveAPI secret keys and refresh tokens are hashed with SHA-256 before storage. Plaintext credentials are never written to the database.
Document Security
Controls specific to KYC, LP, and financial document processing.
Secure Document Storage
LiveDocuments stored in AWS S3 with owner-scoped key structure: {orgId}/{uuid}/{filename}. No cross-tenant access — each organization's documents are logically isolated. Filenames sanitized — non-alphanumeric characters stripped before storage. No public S3 bucket access.
Presigned URL Access
LiveDocuments are never exposed via permanent public URLs. All document access is via time-limited presigned S3 URLs generated per request. URLs can be obscured from browser history via backend proxy. Frontend does not upload directly to S3 — all uploads go through the authenticated backend.
No AI Training on Your Data
GuaranteedPDFFillr does not use your documents, extracted data, or AI outputs to train, fine-tune, or improve any AI model. Documents are processed transiently within the AWS Bedrock boundary and are not retained for model development purposes.
Human Review Policy
Exception-onlyHuman access to your documents occurs only on an exceptional basis — for example, when you raise a support ticket or during a security investigation. All personnel with access are under NDA and confidentiality agreements. Human review is never routine or automated.
Audit Logging
Full traceability of document and API activity.
All requests logged with method, URL, IP address, status code, and timestamp
Token issuance, refresh, rotation, and replay attempts — all logged with user identity
Immutable DocumentAuditLog per document — upload, access, processing, deletion events
Every API request updates last_used_at — usage is traceable per key
ApiRequestLog + UsageSummary models capture all programmatic API activity
authorization and cookie headers are automatically redacted from all logs
Log viewer protected by Basic Auth — not publicly accessible
Audit logs exportable via API for SIEM integration (enterprise plans)
Infrastructure
Amazon Web Services (AWS) — US regions
AWS Bedrock — processed within AWS VPC boundary, no data leaves to external AI providers
Private S3 buckets — no public ACLs, versioning enabled, AES-256 SSE enforced
PostgreSQL — connection encrypted in transit via SSL
Global: 15 requests / 60 seconds per IP — applied to all endpoints
Global ValidationPipe with whitelist: true — unknown fields stripped and rejected on every request
10 MB per document — enforced at the server layer
Docker — consistent, reproducible deployment environments
Environment-variable based — migration to AWS Secrets Manager in progress
Data Retention & Deletion
| Data Type | Retention | Deletion |
|---|---|---|
| User documents (saved) | Duration of active account | Removed from active systems within 30 days of deletion request |
| Encrypted backups | Up to 90 days | Overwritten automatically in backup rotation — never actively accessed |
| Application logs | 90 days | Rotated automatically — daily log files |
| API request logs | 90 days | Purged per retention schedule |
| Refresh tokens | 30 days from issuance | Revoked on logout, rotation, or replay detection |
Incident Response & Breach Notification
Notification Commitments
- Affected enterprise customers notified within 48 hours of confirmed breach
- EU supervisory authority notified within 72 hours (GDPR requirement)
- NJ DLRA notification obligations met
- Notifications include: scope, data categories affected, timeline, and remediation steps
Response Process
Automated alerting triggers incident response
Affected systems isolated, access revoked, scope assessed
Customer notification with initial impact assessment
Root cause analysis and remediation report issued
Vulnerability Disclosure
If you discover a security vulnerability in PDFFillr, please report it responsibly to Support@pdffillr.ai. We commit to acknowledging all reports within 48 hours and will work with you to resolve confirmed issues. We do not take legal action against good-faith security researchers.
All vulnerability reports are treated confidentially. We will notify you when a reported issue has been resolved and credit researchers who wish to be acknowledged.
Security Contacts
Security Issues
Support@pdffillr.ai
Privacy & DPA
Support@pdffillr.ai
Enterprise & Compliance
Support@pdffillr.ai
General Support
Support@pdffillr.ai
Legal & Compliance Documents
Terms of Use
Acceptable use, liability, and platform rules
Privacy Policy
How we collect, use, and protect your data
Data Processing Addendum
GDPR processor obligations and SCCs
Service Level Agreement
Uptime commitments and incident response SLAs
SaaS Agreement
Enterprise subscription terms and obligations
Order Form (Exhibit A)
Subscription scope, pricing, and support terms