Galacia.

Storage and trust

Data ownership.
Security and operations.

Understand where files are stored, agree your organisation’s configuration and review how this website handles your information.

How the standard S3 file flow works

  1. Salesforce record pageThe user opens Vault and requests an upload or download.
  2. Vault in SalesforceSalesforce code checks the file operation and connection access. File metadata and the record association stay in Salesforce.
  3. Your S3 storageFile contents use the agreed bucket and region. The standard connection uses a Salesforce Named Credential for storage access.

In the standard S3 path, transfers go through Salesforce. A separately configured transfer gateway is a different path and must be assessed if included in your setup. The Galacia website’s demo form is separate from this file workflow.

Galacia handles the setup

Installation, API connections, bucket configuration and testing are part of the agreed onboarding. Record the installed version and configuration in your handover.

Your team owns the decisions

Nominate Salesforce and storage owners. Agree region, file access, credential rotation, provider charges, retention and recovery responsibilities before rollout.

File permissions need their own check

Access to the parent Salesforce record does not automatically grant access to its Vault files. File sharing and connection access must both be configured and tested with permitted and restricted users.

Storage ownership is not a recovery plan

Agree who backs up file contents and Salesforce metadata, who tests restoration and how credentials are revoked. Before removing the integration, preserve the file-to-record mappings and verify that your team can retrieve the required files. Bucket access alone does not reconstruct those Salesforce relationships.

Use the procurement checklist to record configuration, support and exit responsibilities in your agreement.

Your organisation’s storage

Vault stores files in customer-owned Amazon S3 storage for the current assisted setup. Storage location, access, retention and provider charges depend on the configuration agreed for the organisation. Galacia configures the bucket and API connections and tests your agreed setup.

This website

For a company-wide overview, read privacy and cookies or visit the security centre.

Public pages explain Galacia products. Company accounts store owner details and company information, and use essential sign-in cookies. Resend delivers verification and recovery emails. Purchases and trials are disabled during the accounts-only beta. The website does not accept Salesforce files or storage credentials and includes no analytics or advertising scripts. The hosting provider may process connection information such as IP addresses to serve requests.

Demo request privacy notice

Galacia, operated by James Collard, stores your work email, company, role and any optional name, storage estimates, download needs and migration interest in the existing private website database to respond to your demo enquiry and discuss a written offer. Supported campaign tags (utm_source, utm_medium, utm_campaign, utm_term, utm_content and utm_id) from the demo page URL are stored with the request when JavaScript is enabled. They are not used to add you to a marketing list.

Galacia also sends demo request details and campaign tags to its owner through a Discord webhook, including a text attachment with the complete request. Discord processes and stores those messages under its own policies; access is limited by the channel settings chosen by the owner. Contact Galacia to request correction or deletion from both the database and Discord.

Requests are accessible to the owner through authenticated server access and are included in existing database backups. No Salesforce files, payment details or storage credentials should be submitted. Contact hello@galacia.app to ask about your request or request correction or deletion. Requests should be removed when the enquiry no longer needs follow-up; backup copies expire under the existing backup retention schedule. The form uses no additional cookies or browser storage.

Configuration and testing

Agree storage location, access requirements, retention and operational responsibilities with Galacia. Installation and testing cover the configuration agreed for your organisation.

Before a production rollout

Review the agreed configuration, access requirements, data flows and recovery arrangements against your organisation’s policies before rollout.

Find support guidance