Security, privacy and compliance at Zime

Security controls Zime runs

• Data security

  • TLS 1.2 and TLS 1.3 only, in transit
  • AES-256 encryption at rest on AWS
  • Database keys in AWS Key Management Service
  • Each customer's data separated by company
  Learn more: Data security ›

• Access control

  • Role based access with least privilege
  • Multi-factor authentication on all production systems
  • Production access reviewed every quarter
  • Access removed within three days of an employee leaving
  Learn more: Access control ›

• Infrastructure

  • AWS US East (N. Virginia), three availability zones
  • Continuous database backups, daily snapshots kept 14 days
  • Production access logged, with a cloud audit trail
  • Automated threat detection on production
  Learn more: Infrastructure ›

• Application security

  • Every change reviewed, tested and approved before release
  • Separate development and production environments
  • Independent penetration test at least once a year
  • Fix targets: critical 7 days, high 30 days
  Learn more: Application security ›

• Corporate security

  • Endpoint checks on every device that reaches Zime systems
  • No customer data on personal devices
  • A device that fails the checks may not access company data
  • Removable media and printing of customer data prohibited
  Learn more: Corporate security ›

Controls your team sets

• How calls are recorded

  • The Zime notetaker joins as a visible participant, and any host can remove it
  • Microsoft Teams native recording, with no bot, after your Microsoft 365 admin consents
  • Zoom native recording, with no bot, for hosts on a paid Zoom license
  • The Mac app records on the rep's Mac with no bot, then sends the transcript and audio to Zime
  Learn more: How calls are recorded ›

• Which meetings are recorded

  • Each user picks the meeting types Zime records: external with an outside host, external with their own team hosting, and internal
  • The notetaker can be switched off for any single meeting
  • A meeting already marked private in Google Calendar or Outlook when Zime first reads it is not recorded for that person
  Learn more: Which meetings are recorded ›

• Who sees what

  • Admins give each user a role: User, Manager or Admin
  • A visibility level per user: their own calls, their peers, their function, the accounts they work on, or the whole company
  Learn more: Who sees what ›

• Where recordings are kept

  • Your meeting recordings and transcripts in an Amazon S3 bucket in your own AWS account, set up by Zime per customer
  • With your own bucket, call insights, search data and account data stay in Zime's systems
  • Admins can delete a recording, and can allow users to do the same
  Learn more: Where recordings are kept ›