Encryption in transit
All communication between clients, application servers, and storage infrastructure is encrypted using TLS 1.2 or higher. Plaintext connections are rejected at the transport layer. This applies to all surfaces of the service, including the dashboard, upload portal, API, and webhook delivery.
Encryption at rest
Uploaded documents are stored with AES-256 server-side encryption. Encryption keys are managed by the storage infrastructure and are not accessible to application code. Database fields containing sensitive values use encryption where appropriate.
Automatic file deletion
Documents are permanently deleted from storage after the organization's configured retention period, which ranges from 7 to 30 days depending on the plan. Deletion is measured from the time a request is marked as completed. Once deleted, files cannot be recovered by any party, including SendMeDocs.
Passwordless authentication
All dashboard authentication is performed via passkeys (WebAuthn/FIDO2). No passwords are stored, transmitted, or accepted by the system. Each device registers an independent cryptographic credential, eliminating the risk of credential stuffing, phishing, and password reuse attacks.
Access controls
The service enforces strict multi-tenant isolation at the database and application layers. Every query is scoped to the authenticated organization. Role-based access control limits administrative operations to authorized members. Upload tokens are single-use and cryptographically generated, scoped to a specific request.
Audit logging
All email and SMS notifications are logged with delivery status and timestamps. Credit and billing transactions maintain a complete, append-only ledger. Session activity is tracked per device. Policy and BAA acceptances are recorded with the acceptor's identity, IP address, user agent, and timestamp.
Minimal data collection
SendMeDocs does not use tracking cookies, third-party analytics, or advertising pixels. A single session cookie is used for authentication. No document content is read, analyzed, indexed, or used for any purpose beyond delivering it to the authorized recipient.
Infrastructure
The service is hosted on infrastructure that supports regulated workloads and maintains appropriate compliance certifications. Application and storage components are provisioned in a single geographic region. Access to production systems is restricted and logged.