Security
Sygnal reads. It never writes.
Sygnal connects to the systems holding your customer data, so how that data is handled matters as much as what the reporting says. This page explains what Sygnal can reach, what it keeps and what it will never do. The privacy policy is the commitment; this is the explanation behind it.
We ask for read access and nothing more
Every system you connect is authorised with read permission. Where a platform offers scoped access we request the read scopes and leave the rest, and you can see exactly that on the consent screen before you approve it.
There is no code path in Sygnal that writes to a system you connect. The only requests it makes are the ones that fetch a report or a list of records.
We never hold your credentials
Passwords and access tokens sit with our authorisation provider, not in Sygnal and not in our database. Sygnal asks for a connection by name and never sees the key behind it.
You can revoke Sygnal's access from inside the connected system whenever you like, and we retain no other way in.
Your data is never sent to an AI model
Nothing you connect is passed to a third-party model, and none of it is used to train one. There is no such integration anywhere in the product.
Every figure Sygnal reports is computed by Sygnal, from your data, on infrastructure we run. The forecasting is statistics, and it stays inside your workspace.
One workspace cannot see another
Every record carries the workspace it belongs to, and every query the application makes is scoped to the workspace of the person signing in, through a single point in the code rather than a rule each page remembers separately.
The database enforces the same separation as a second layer, so any route that does not go through the application is scoped too.
What happens to it once it is here
It stays in the EU
Data is held in Frankfurt and is encrypted in transit and at rest by our hosting provider. The companies that process anything on our behalf are named in the privacy policy, and that list is exhaustive.
Raw copies do not linger
What a connected system returns is kept only long enough to rebuild your reporting without fetching it again, then deleted automatically. The privacy policy states the period and is the commitment.
Leaving revokes before it deletes
When an account closes we release our access to every connected system first, and only then delete the data. If a release fails we stop rather than continue, so we can never end up holding a working key to a system belonging to someone who has left.
The privacy policy is the operative document. It names every company that processes data on our behalf, states how long each kind of record is kept, and is what we are held to. Read the privacy policy.
What we do not claim
We have not been independently audited
Sygnal holds no SOC 2 report and no ISO 27001 certificate, and you will not find a compliance badge on this site. If that changes, this page will say so and name the auditor. Until then, treat everything here as something to check rather than something certified.
Not every tool offers scoped access
Some connect with an API key rather than granular permission. Sygnal still only reads, but there the guarantee is our code rather than the platform enforcing it, so issue the most limited key the tool will give you.
Our team can reach customer data
Running and supporting the product means engineers can see a customer workspace. It is limited to the people who need it to operate the service, and we would rather say so plainly than leave you to assume otherwise.
Bring your channel mix.
Twenty minutes, screen shared, and you can pick the channel you are least sure about.