Connectors
How Vigicap handles your credentials
These rules apply to every connector, without exception. Each connector page links here rather than repeating them: what changes from one tool to the next is what is read and with which rights — not how the credential is stored or what is done with it.
The access is created at the vendor, not here
Vigicap never asks for an administrator's password. Every connector expects either an OAuth consent the client grants inside their own tenant, or an API credential you create yourself in the tool's console. Either way the access stays yours: you can see it where you created it, and you can revoke it without going through us and without telling us.
What is stored, and what never comes back out
Values marked "secret" in the connect form are encrypted at rest and never returned to the browser — not for display, not for editing. The settings screen shows you that a secret is on file, never its value. When the connector is disconnected, those values are deleted.
Reads write nothing
A read connector changes nothing in the tool it queries: no creation, no correction, no automatic remediation. The only integrations that write are the ticketing connectors, and they say so on their own page, on the line naming what they file.
What is read, and how long it is kept
The question "which data exactly, and for how long" is not answered connector by connector but in a single register kept for all of them. It is also the document a data protection officer asks for by name. the data inventory.
What to enter in Vigicap
The form starts with the instance address, entered separately from the fields below. The public catalogue does not yet publish whether this connector needs one, or what it looks like — so this list is exact about everything else, and silent about that first field.
The trademarks named
The names and logos of the tools named belong to their respective owners. They identify the products Vigicap is compatible with and imply no partnership, affiliation or endorsement on their part.