GalaciaRegion and retention are yours
You agree the bucket, the region and the retention settings before onboarding. Your organisation owns the provider account and its charges.
Solutions / Regulated record keeping
Record files in a region and bucket you choose.
If your policies say where files must live and how long they’re kept, Galacia Vault leaves those decisions with you. The contents go to Amazon S3 storage your organisation owns. Galacia configures the bucket with you during onboarding.
The situation
Your policy already says where the files should be.
Teams with retention schedules, residency rules or audit obligations often want record files in storage they control, under settings their own people manage.
Vault keeps the working experience on the Salesforce record while the file contents use your bucket. It doesn’t make a process compliant by itself, and Galacia doesn’t claim that it does.
With Galacia Vault
What changes for your team.
You can see where the data goes
In the standard S3 path, transfers go through Salesforce. File contents go to your bucket, and the metadata and record link stay in Salesforce.
Access is checked twice
Record visibility doesn’t grant file access. File sharing and storage-connection access are configured and tested with permitted and restricted users.
Encryption at rest
On Amazon S3, files are encrypted at rest by Amazon’s server-side encryption on your bucket. Vault adds no encryption layer of its own on S3.
In the demo
Ask to see these.
Bring a typical record, your user roles and a few non-sensitive files.
- The data flow for your configuration, including every service that handles a file.
- Retention and deletion: who can delete a file, and what your recovery procedure is.
- How storage credentials are owned, rotated and revoked.
- The exit route: how you keep your files and the file-to-record mappings if you stop using Vault.
Plain facts
Limits worth knowing first
- Galacia publishes no certification or audit report. Galacia is operated by James Collard personally.
- This website isn’t a data processing agreement. Agree data processing terms, provider locations and retention in writing.
- A separately configured transfer gateway is a different data path and needs its own assessment.
- Support is provided by one person, with no backup cover at present. Agree escalation and planned absence before rollout.
See Vault on a Salesforce record page.
Book a demo, bring a typical record and a few non-sensitive files, and decide from there.