FilePreserve

Your data stays in two places you already own.

Not a claim layered on a hosted product. The principle FilePreserve was built around.

Box 1

Your Salesforce org

Records and live files stay here. FilePreserve runs inside it.

Archive out, retrieve back
Box 2

Your AWS S3 bucket

Archived files land here, in an account you control and audit.

No FilePreserve server in between.

Where your data lives: two places, both already yours

Salesforce record data stays in your org

FilePreserve runs entirely inside your Salesforce organization as a managed package. It reads records using the permissions and sharing rules of whichever user is running it, so it never sees more than that user can already see. No external service is involved in reading your records.

Archived files go to your own AWS S3 bucket

When an archive job runs, files move to a bucket you create and control in your own AWS account, never to FilePreserve's infrastructure. The connection uses Salesforce's built-in AWS Signature Version 4 authentication, with no custom signing code and no storage layer in between.

Runs with your users' permissions

Every piece of code that touches data runs under the signed-in user's own access rules. There is no FilePreserve-operated server or proxy. The files and records the app handles go only to the S3 bucket you configure yourself. Billing is separate and goes through Stripe.

Your files. Your account. Your controls.

Archived files carry the same regulatory weight as your Salesforce records: FDA CAPA and complaint documentation, or records that may be sensitive for a health plan. Keeping them in an AWS account you already control and audit means their compliance posture does not depend on a vendor's certifications or practices.

Where each choice leaves your files

QuestionIf a vendor hosts the archiveWith FilePreserve and your own S3
Where files sitUsually in the vendor's own storageAn AWS account you already control and audit
Whose controls applyThe vendor's, which you rely on rather than auditYour own AWS controls
CopiesDepends on the vendorWe never host, proxy or keep a copy of your archived files

What FilePreserve does not claim

What it is

  • A tool for faster, complete packets

    FilePreserve helps produce complete, audit-ready documentation packets faster.

  • A setting inside your org

    Retention and legal hold are settings inside FilePreserve, and your team decides when they apply.

What it is not

  • SOC 2, HIPAA or otherwise certified

    It does not claim to be. That follows from the own-storage decision: your compliance posture stays governed by your own AWS account and controls.

  • Legal or compliance advice

    It does not tell you when a hold should apply or how long to keep a record. Your counsel and records policy decide that.

Outside services are limited. Billing is handled by Stripe, a PCI-compliant payment processor, and it only touches billing information, never your Salesforce records or archived files. The website waitlist stores the email you submit. The Privacy Policy has the exact breakdown.

Read exactly how your data is handled.

The Privacy Policy and the setup guide go into the detail behind everything on this page.