Security from the ground up
Erik is built to work close to your company's most important data and systems. That is why security, privacy and control are a fundamental part of how the service works.
Your passwords stay private
Erik doesn't need to see your passwords, API keys or login tokens to do his work.
You approve sensitive actions
Important actions, like sending emails, changing code or handling payments, can require active approval first.
Your data isn't used for AI training
Your company's conversations, files and information are not used to train AI models.
Your information is kept separate
One company's data, memory and integrations are never mixed with other customers' environments.
Data is encrypted
Information is protected both in transit and at rest.
Erik only gets the access he needs
Integrations can be limited to exactly the systems and functions a task requires.
You control who can do what
Administrators decide which integrations are available and what access users get.
Protection against harmful instructions
Content in emails, documents and web pages is treated as information – not automatically as commands.
Support for your company login
Larger organisations can use SSO and their existing identity management.
Full control over data and access
Access is logged, integrations can be switched off instantly and data can be deleted when it's no longer needed.
Data protection is a core part of Erik. All customer data is stored and processed within Europe and never leaves the EU/EEA. We follow GDPR requirements on data protection, access and the handling of personal data. A data processing agreement (DPA) is available to all customers.
Frequently asked questions
All customer data is stored and processed within the EU/EEA and doesn’t leave it. We follow GDPR, and a data processing agreement (DPA) is available to every customer.
No. Your company’s conversations, files and information are never used to train AI models.
Sensitive actions, such as sending emails or handling payments, can require active approval before Erik carries them out.
Admins decide which integrations are available and what access users get. All access is logged, and integrations can be switched off instantly.
Content in emails, documents and web pages, for example, is treated as information, not automatically as commands.
Yes. Larger organisations can use SSO and their existing identity management.