Privacy Policy
Last updated: October 15, 2026
- Record data
- Stays in your Salesforce org
- Archived files
- Your own S3 bucket
- We collect
- Waitlist email, page and time
- Billing
- Handled by Stripe
Who we are
FilePreserve is made and operated by Georgina Hawley ("we," "us," "FilePreserve"), an independent software maker. You can reach us at hello@filepreserve.com.
What FilePreserve is, and why this matters for data handling
FilePreserve is a Salesforce managed package for regulated teams (FDA CAPA/complaint documentation, CMS RADV audit response) that archives files off active Salesforce storage, enforces retention and legal-hold rules, and merges/exports files across a record's related lists on demand. Because it's built for compliance-sensitive data, the core design decision behind everything below is simple: your Salesforce record data and your archived files never leave infrastructure you already own and control.
Salesforce record data
FilePreserve runs entirely inside your own Salesforce organization as a managed package. It reads the object/record data you configure an archive job to act on, using the permissions and sharing rules of whichever user is running it, so FilePreserve never sees or accesses more than that user already has access to inside your org. There is no external API call, and no third-party service, involved in reading or evaluating your Salesforce records. Your record data is never sent to FilePreserve's own infrastructure. It stays inside your Salesforce org. (Archived files are handled separately; see the next section.)
Archived files: your own AWS S3 bucket, not ours
When an archive job runs, files are moved to an AWS S3 bucket that you create and control in your own AWS account. FilePreserve connects to it using Salesforce's native AWS Signature Version 4 authentication (a built-in Named Credential/External Credential pattern). There is no FilePreserve-operated storage layer in between. We never host, proxy, or retain a copy of your archived files ourselves. This is a deliberate design choice, not just a technical detail: hosting regulated compliance data ourselves would make us a data processor/custodian for FDA- and CMS-adjacent records, which is a compliance-certification burden we've chosen not to take on. Your files stay in an AWS account you already audit and control.
This is documented in more operational detail in the setup guide's storage section (see Setup Guide) and in the product's own buyer-facing data-handling material if you've requested a copy as part of an evaluation.
Retention, legal hold, and disposal data
Retention periods, legal-hold flags, and disposal-mode settings (Preserve forever, Ask me first, or Delete automatically after a notice period) are configuration you set and that lives in your own Salesforce org as custom object records, not data we see or store. When a disposal job actually deletes a file, it deletes it from your S3 bucket and your Salesforce org directly; we don't retain a separate copy or log of deleted file content anywhere.
Usage data we do collect
We do not collect telemetry about your archive jobs, record content, or file contents. If you contact us for support, we keep that email correspondence to respond to you and for our own support records and nothing more.
Billing information
Billing is handled directly by Stripe, a PCI-compliant third-party payment processor. We do not see or store your full payment card details. Stripe handles that directly and processes it under its own privacy policy. We receive confirmation that a subscription is active, tied to your org's identity, so we can manage your account, plus standard billing information (email, subscription status) needed to administer that subscription.
Waitlist and website data
If you join the waitlist on this site, we store the email address you enter, the page and button you used, and the time. We use it only to tell you when FilePreserve is available, and you can ask us to delete it at any time by emailing hello@filepreserve.com. Your IP address is used briefly to limit repeated submissions and is not kept with your signup.
The site does not use advertising or cross-site tracking cookies. It is served through Cloudflare, which processes standard request data to deliver pages, and we may use Cloudflare Web Analytics for aggregate traffic counts (pages visited, referral source, country or region). That tool sets no cookies and collects no personal data about individual visitors, which is why the site shows no cookie banner.
The roadmap page (/roadmap) makes your browser request docs.google.com to read the public roadmap from a Google Sheet, so Google can see that request, including your IP address. No other page loads anything from a third party.
Data retention and deletion
Because FilePreserve never stores your Salesforce record data or archived files outside your own infrastructure, there is nothing on our end to delete when you uninstall the package. Uninstalling removes FilePreserve's own objects and configuration from your org per Salesforce's standard managed-package uninstall process. What happens to files already archived in your S3 bucket at that point is entirely under your own control, since that bucket is yours. Billing records are retained by Stripe per their own retention policy.
Changes to this policy
If this policy changes in a way that affects what data FilePreserve touches or how it's used, we'll update the date at the top of this page and, for material changes, notify active subscribers by email.
Contact
Questions about this policy: hello@filepreserve.com.
Your record data and archived files never leave infrastructure you already own and control.
That is the design decision behind everything on this page.
Questions about your data?
Ask before you join. Email goes to the person who runs FilePreserve.