How we connect to your systems
We use each platform’s approved sign-in method for integrations where one exists. Where it does not, we ask you to create a separate integration user with only the permissions the work needs. We never use a staff member’s personal login.
Exactly what we can access
Before anything is built you receive a written list of each system, each type of record, and whether we read it, write it, or both.
Read-only until you approve
While we plan, we ask for read-only access to confirm your systems and data support the plan. Write access is enabled for the test build, and for production only after your approval. In test mode the platform blocks any change to a live system.
Where your data goes
You receive a one-page diagram showing what data enters the integration, where it is held, which services touch it, and where it ends up. Your own systems remain the source of truth.
Hosting and location
The platform runs on Google Cloud in the United States. Your data and its backups stay in US locations. If a contract requires data to stay in another region, tell us during the consultation.
Your credentials
The keys and tokens you give us for your systems are encrypted at rest and in transit. They are never written to logs. Values are hidden in the dashboard. An administrator can reveal one value at a time, and each reveal is limited and recorded with the name of the person who did it.
Encryption
Data is encrypted in transit. Stored data sits on Google Cloud, which encrypts data at rest by default.
Kept separate from other customers
Each customer’s data is separated by design, not by a filter someone has to remember to apply. Automated tests check on every change that one customer can never see another’s data.
How your team signs in
Your team signs in to the dashboard with their own Microsoft work account, so we never hold your passwords and your own sign-in policies apply. Access is by invitation only, tied to the invited email address and to your organization.
A record of every change
The dashboard keeps a log of each record the integration handled, when it last synced and the data it carried. Administrative actions, such as stopping a run or revealing a credential, are recorded with the person who took them.
What we store
The platform keeps a copy of the records it moves, along with their change history. That is how it knows what changed and avoids sending repeats. Your own systems remain the source of truth.
How long we keep data
Run logs are kept for 30 days and delivery logs for 90 days, then deleted automatically. The integration runs until the shut-off date you set with us.
Backups and recovery
Daily and weekly backups, the ability to restore to any point in the previous seven days, and a second copy held in a separate US region. We rehearse a full restore every quarter.
Third parties
Google Cloud for hosting, Microsoft for sign-in, and Postmark for notification emails.
Testing before production
Everything is built and tested in a sandbox first. For platforms without a sandbox, we can use a test event or set up a simulated sandbox. Your team reviews it against a checklist, and nothing goes live without your sign-off. Show day fixes and changes have an expedited process that ensures safety and speed.
If something goes wrong
Our team is alerted automatically when a run fails, stalls or cannot recover.
Independent assurance
We complete your security questionnaire and provide our documentation on request.
When the project ends
We switch the integration off on the agreed date, remove our access, and hand over the documentation, so you are never locked in.