Security
Robots that touch your ERP need to be trusted
What the platform does today to protect your systems and data. If your security team has a questionnaire, send it to us and we will answer it.
Where it runs
- The RINKT cloud platform runs on Google Cloud in Frankfurt, Germany.
- For regulated operations the whole platform can run on-premise, inside your own infrastructure, with its own database and sign-in.
Credentials and secrets
- Passwords and other secrets the robots use are encrypted at rest with AES-256-GCM, each value separately.
- Values marked as secret are removed from run logs, and password fields are masked when the robot records a screen's structure.
- Each robot gets its own key, stored only as a hash and bound to the machine it was paired with.
- Traffic to the platform is encrypted in transit with TLS.
Who can do what
- Organisations have owner, admin and member roles; projects can be private to named members and editors.
- API keys carry a scope, from read-only to admin, so an integration gets only the access it needs.
Audit trail
- Every approval and rejection is recorded with who decided and when.
- The audit log is append-only and each entry is sealed with a keyed hash, so an edited entry is detectable.
- Every saved workflow version records who saved it and can be rolled back.
- The audit log can be exported as CSV or JSON for your own records.
AI
- Document reading and the workflow builder use OpenAI, Azure OpenAI or Anthropic models.
- Your organisation can choose the extraction model and the OCR engine, including a self-hosted OCR engine, and can use its own AI provider keys by arrangement.
How we build it
- Every change to the platform is checked for known-vulnerable dependencies, and container images are scanned before they reach production.
Security questionnaire or a question?
contact@rinkt.com · +44 203 627 1130