Private access
Customer filing pages require a signed session or a time-limited magic link. Filing records are checked against the signed-in customer before they are returned.
Trust center
A filing workspace built around controlled access.
This page describes the safeguards currently used by Snapfile. We avoid publishing security claims that the product does not actually implement.
Last reviewed: October 22, 2026
Short-lived document links
Stored documents are not placed in a public directory. When a service needs a file, Snapfile creates a temporary signed link with a limited lifetime.
Separated responsibilities
Payments, email delivery, document storage and fax delivery are handled by specialist providers. Snapfile does not receive complete card details.
Verified inbound events
Payment, email and fax status callbacks are authenticated before they can change a filing record.
Data path
Who handles what
These providers receive only the information required for their role. Their own security and retention practices also apply.
Vercel
Website hosting, application delivery and anonymous performance analytics
Neon
Managed PostgreSQL database for accounts and filing records
Cloudflare R2
Private storage for filing documents and transmission receipts
Stripe
Checkout, payment processing, refunds and payment records
Telnyx
Outbound fax transmission and carrier delivery status
Resend
Transactional email and delivery events
Anthropic
AI-assisted completeness and consistency checks when that workflow is used
Sentry
Application error monitoring with sensitive filing content excluded where practical
Report a concern
Tell us directly and include the affected filing ID.
Security and privacy questions are handled by Horizons Furness LLC. Do not email tax IDs, passports or bank files.
For the information lifecycle, see the data-retention schedule.