Security
Your systems, your keys, your decision.
Kritch works with the systems your business runs on. This is how it keeps them safe, in plain words.
Keys never reach an AI
Keys to your systems are entered on a Kritch page, never in a chat. They are stored encrypted. Once saved, Kritch shows only the first and last three characters, so you can tell which key it is. No AI assistant, no log and no email ever contains a key.
Or no shared key at all
You can also connect by signing in as yourself in the other system. Your password is typed there, never in Kritch, and the connection can do there exactly what you can, nothing more.
No AI at work while Kritch runs
Kritch itself calls no AI service. Your assistant comes to Kritch to set things up; once a flow is approved, it runs without any AI, the same way every time.
A person approves every change
An assistant can propose and make a preview. Only a person in your company can put a flow into use, switch its schedule on or change who receives a file.
Everything is recorded
Every sign-in, change, approval, export and file sent is recorded per organization, including what Kritch support did when you asked for help. Admins can read it under Logs. The data itself is never in the logs, and the logs can’t be edited.
You see who used a connection
Every connection shows when it was last used, and by which flow or which person. One that nobody has used for 30 days stands out, so you can archive it.
Each organization on its own
The data of every organization is kept apart. People only see their own organization. Everyone signs in with a password and a code from an app on their phone.
Files don’t stay forever
A file Kritch makes is kept for 90 days and then removed.