CompanyBrain NLEN Sign in

Security and privacy

Where data is kept and what we do not keep

  • Chat content and log lines go from the AI platform straight to your storage. They are not kept at CompanyBrain.
  • We only keep a cursor per platform (how far we have read), metadata, your name and email address and your credentials for the connections.
  • For the account count we only keep monthly hashed email addresses (HMAC-SHA256, key per organization) and totals, for at most 13 months.
  • Payment details are processed by Stripe and never reach us.
  • If you delete a source, the storage or the organization, we delete the related credentials immediately.

Encryption and the Key Vault

Credentials are encrypted per organization with a key of its own (AES-GCM). That key is itself wrapped with a master key that lives in Azure Key Vault. Decryption only happens during a run and the data never appears in log files. All connections use https.

Signing in

  • Only with Microsoft or Google, there are no passwords. When you sign in we only ask for your name and email address.
  • A user is recognized by a fixed identifier of the provider and never by the email address alone. An organization follows the Microsoft tenant, or a domain verified through a DNS record.
  • Sessions can be revoked: signing out and removing a member invalidates them. Invitations are valid for 7 days and belong to an email address.
  • Administrators and members have separate permissions. Changes are recorded in an audit log.

Isolation between customers

Every organization has its own key, its own storage and its own data. Connections to addresses a customer enters are checked first: private, loopback and metadata addresses are refused and an API key is never sent to another host. Forms are protected against CSRF and the server sends strict security headers.

When something fails

  • If a run fails we try again every 15 minutes, at most 6 times a day. A day only counts as done when all sources succeeded.
  • Because we remember how far we have read, the next run catches up on what was missed. Records are merged on their id, so there are no duplicate lines.
  • Failed attachments are kept encrypted for a next run. Administrators get a notification on an error or a cursor older than 20 days.
  • With a payment problem runs pause after a grace period of 7 days. Nothing is ever deleted.

The GDPR and the works council

  • The logs contain what employees do with AI. Those logs sit in your storage and you decide the retention period and who has access. For your account details and the hashed account count Cafe Boon (KvK 92541003) is the controller.
  • You are responsible for processing the logs lawfully, including informing your employees (see the terms). If your organization has a works council, recording what employees do may require its consent. Put that to your own lawyer.

Privacy policy · Terms · Contact