Data location and providers
Identify each service in your configuration, where data is stored and which organisations can process it. Discuss residency and transfer requirements before onboarding.
Review website data handling separately from the Salesforce and cloud storage configuration agreed for your organisation.
In the standard S3 path, transfers go through Salesforce. A separately configured transfer gateway is a different path and needs its own assessment.
On the Salesforce record page
They use the Vault component on the record they’re already working on.
In Salesforce
Salesforce code checks the file operation and the storage connection. The file’s metadata and its link to the record stay in Salesforce.
In your S3 bucket
File contents use the bucket and region you agreed. Your organisation owns the storage, its retention settings and its provider account.
Files use customer-owned Amazon S3 storage for the current assisted setup. Region, access, retention, recovery and provider charges depend on your agreed configuration.
Galacia handles installation, API connections, bucket configuration and testing. Confirm access with both permitted and restricted users before rollout.
Read Vault storage responsibilitiesThe website handles enquiries and optional company accounts. It does not accept Salesforce files or storage credentials.
Account features use essential sign-in cookies. Public pages contain no analytics or advertising scripts. Demo requests are stored privately and sent to the owner through Discord.
Read privacy and cookie information| Area | Galacia | Your organisation |
|---|---|---|
| Installation | Installs the agreed version, sets up API connections and adds Vault to the agreed record pages. | Provides access and names a Salesforce administrator and a storage owner. |
| Storage | Configures the bucket for the agreed setup. | Owns the bucket and decides region, retention and who pays provider charges. |
| File access | Assigns the agreed administrator and user permissions. | Decides who can reach files, and owns the storage credentials and their rotation. |
| Testing | Tests the agreed setup before handover. | Confirms the result with permitted and restricted users. |
| Recovery and exit | Records the installed version and configuration in your handover. | Agrees who backs up file contents and Salesforce metadata, who tests restoration and how credentials are revoked. |
Access to a Salesforce record doesn’t automatically grant access to its Vault files. File sharing and storage-connection access are checked separately.
Identify each service in your configuration, where data is stored and which organisations can process it. Discuss residency and transfer requirements before onboarding.
Agree Salesforce access, storage permissions, who owns credentials and how access is revoked. Use an agreed secure channel for setup secrets.
Agree backup ownership, recovery checks, retention settings and deletion. Customer-owned storage still needs a documented operating plan.
Share required questionnaires, contract clauses or assurance evidence. Certifications and audit reports are not published here. See the support window and first-response target; any contractual service-level agreement needs separate agreement.
Galacia publishes no certification, audit report or penetration-test summary, and this page isn’t a statement of regulatory compliance. Galacia is operated by James Collard personally.
If your review needs specific evidence or contract terms, say so before the demo. The procurement checklist covers the topics to settle in writing.
Email hello@galacia.app with the affected URL or product, when you noticed the issue and safe steps to reproduce it.
Do not include passwords, tokens, customer files or unnecessary personal information. If sensitive evidence is needed, ask for a suitable transfer route first.