Security & Compliance
Plain facts about how Password Pusher protects your data. No theatre, no filler β just what you need for your security review.
On this page
What Password Pusher Is (and Isn't)
Password Pusher is a tool for secure, temporary distribution of sensitive information. It generates one-time links that automatically self-destruct after a configurable number of views or elapsed time, with full lifecycle audit logging.
Password Pusher is not a credential manager, password vault, or secrets store. It does not retain or manage credentials long-term. Data is ephemeral by design.
Open Source Core, Paid Feature Superset
Password Pusher is available as OSS (fully open source) and as paid editions: Solo, Team, Organization, and Self-Hosted Pro. All editions share core encryption, payload handling, expiry logic, and lifecycle audit code with OSS Password Pusher. These core components are publicly auditable at github.com/pglombardo/PasswordPusher.
The paid editions add capabilities such as team collaboration, custom domains, branding, and policy enforcement. Some product-feature implementations are proprietary; the core components named above remain publicly auditable.
Through our Feature Pipeline, paid-edition features are periodically released to the open source edition. Subscribers get early access to new capabilities while supporting continued open source development.
Encryption & Data Handling
Text payloads are encrypted in the database with per-field derived keys. Hosted file contents use storage-layer encryption, not the application's AES-256-GCM text-encryption scheme. Self-hosted file encryption depends on the customer's storage configuration. On expiry, payload data is deleted from live service storage. Audit metadata follows account settings and is deleted on account deletion. Encrypted copies may remain in same-region database backups for up to 30 days until rotation. Backups serve disaster recovery, not recovery of individual deleted accounts.
For detailed technical documentation on encryption implementation, key derivation, risk mitigation strategies, and file upload security, see our Security & Encryption documentation.
Infrastructure & Data Residency
Password Pusher operates two distinct data regions. Sensitive data provided in pushes and requests is stored exclusively within the chosen data region and is never moved to another region.
EU Region (eu.pwpush.com)
The EU service database, file storage, and backups are hosted in the Netherlands. Copies of account, billing, newsletter, and other provider-processed information are not necessarily confined there; see the regional Privacy Policies.
US Region (us.pwpush.com)
The US instance is hosted in the United States on DigitalOcean infrastructure. Push and request data is stored exclusively in the US, is never moved to another data region, and is deleted upon expiration. Organizations requiring EU data residency should use eu.pwpush.com or self-host.
Certifications & Assurance
We believe in stating facts plainly. Here is exactly where Apnotic stands today:
What we have
- Open source core β all security-critical code (encryption, data handling, expiry, audit logging) is shared across editions and independently auditable (GitHub)
- Encryption at rest and in transit β AES-256-GCM + TLS 1.2+
- EU data residency β dedicated EU instance with data stored exclusively in the EU
- Ephemeral data model β payloads auto-expire and are deleted from live storage, subject to the documented backup window
- Full audit logging β lifecycle tracking for every push
- Self-hosting option β deploy on your own infrastructure under your own compliance controls
- Data Processing Agreement β automatically in effect via our Terms of Service
What we don't have yet
- SOC 2 Type II
- ISO 27001
- HIPAA BAA (for the hosted service)
- TISAX, CSA STAR, or similar third-party certifications
- Published penetration test summary
Apnotic, LLC is an independent, bootstrapped company founded in 2024. We have not yet pursued formal compliance certifications for the hosted service. We take security seriously β but we won't claim badges we haven't earned.
If your vendor onboarding process requires SOC 2 or ISO 27001 certification, the hosted service may not meet your requirements today. We recommend self-hosting Password Pusher β this gives your organization full control over the compliance posture and allows certification under your own ISMS.
Self-Hosting for Full Compliance Control
Recommended for regulated industries
When you self-host Password Pusher, Apnotic is a software vendor β not a data processor. Your data never touches our infrastructure. You control encryption, access, retention, and compliance certification entirely within your own environment.
Password Pusher is available as a container image for deployment on your own infrastructure. Self-hosting is the recommended approach for organizations in regulated industries or with strict vendor compliance requirements.
We maintain detailed guidance for self-hosted compliance scenarios:
With self-hosting, Password Pusher can operate within your existing SOC 2, ISO 27001, or HIPAA compliance scope. The guides above include control mapping, auditor Q&A, and data flow documentation.
Data Processing Agreement
A Data Processing Agreement (DPA) is automatically in effect for all organizations using the hosted service at pwpush.com or eu.pwpush.com. Our standard DPA is publicly available at pwpush.com/dpa and applies through acceptance of our Terms of Service β no separate signed document is required. It covers:
- GDPR Article 28 aligned processing terms
- Explicit data scope β Account Data (name, email, company) and Application Data (push/request payloads), with retention terms
- 72-hour breach notification, annual audit rights, and capped liability
- International transfer safeguards β EU Standard Contractual Clauses (Module 2), the UK International Data Transfer Addendum, and Swiss FADP provisions, incorporated by reference
Self-Hosted Customers β DPA Not Applicable
Apnotic does not sign DPAs for self-hosted Password Pusher Pro deployments. When you self-host, Apnotic is a software licensor β not a data processor. Your application data never touches Apnotic infrastructure. The only personal data Apnotic holds is the license purchaser's contact information (name, email, company) for account management.
For procurement and legal teams, our Self-Hosted Data Architecture guide provides technical documentation of data responsibilities, including why a DPA is neither applicable nor appropriate for self-hosted deployments.
Subprocessors
The following subprocessors are used by the hosted service:
| Subprocessor | Purpose | Location | EU Safeguards | Handles Push Data? |
|---|---|---|---|---|
| DigitalOcean | Application hosting, database & backups | Netherlands (EU) / United States | Provider DPA and applicable transfer safeguards | Yes β encrypted at rest |
| Stripe | Payments and fraud prevention | United States | EU SCCs | No payloads β billing, payment, device and fraud data |
| Buttondown | Email newsletter delivery | United States | EU SCCs | No β email address only |
| Brevo | Transactional email | France (EU) | EEA adequacy | No β email delivery only |
| Plausible Analytics | Privacy-focused website analytics | EU | EU-hosted cookieless analytics; raw IP addresses not stored | No β anonymous usage stats only |
| ChartMogul | Subscription analytics & revenue metrics | Germany (EU) | EEA adequacy | No β billing/subscription data only |
Key point for EU customers: DigitalOcean hosts the service database, files, and backups in the selected region. Other providers process billing, email, device, fraud-prevention, or usage information. Their roles and applicable transfer safeguards are described in the regional Privacy Policies.
Subprocessor list last updated: November 2026. For the authoritative and most current list, see the EU Privacy Policy or US Privacy Policy.
Security Practices
Access Control
- Production infrastructure access is limited to 2 individuals
- All production access requires multi-factor authentication
- Administrative access is logged
Development Practices
- Source code publicly auditable on GitHub
- Dependency vulnerability scanning via automated tooling
- Container images published from CI with reproducible builds
Incident Response
- Security issues can be reported to security@pwpush.com
- We aim to acknowledge security reports within 2 business days
Security Contact
Questions about security or compliance?
Email support@pwpush.com β we aim to respond to security inquiries within 2 business days.
For self-hosting guidance, see our deployment documentation.
Last updated: November 2026 Β· Apnotic, LLC