Why does Hugo ask for permission to access/edit my calendar data?

Why does Hugo need calendar access?

Hugo improves meeting productivity by connecting your documents and tasks to the people and organizations you're meeting with.

This makes it easy to:

  • Surface previous or related meeting notes.
  • Prepare for upcoming and recurring meetings.
  • Share notes with internal or external teams.
  • Assign tasks to the right people after each meeting.

To achieve these features, Hugo needs to query certain data points from your calendar provider. This is what Google or Microsoft will ask you to approve when signing up. 

In order for Hugo to work, we require read-only access to your calendar.

Is Hugo safe?

Yes - absolutely. Hugo is proud of our industry-leading security infrastructure. 

Here's a high-level summary of how we keep your data safe:

All Hugo services and data are hosted with Amazon Web Services (AWS) in the United States in the US West region. Amazon employs a robust physical security program with multiple certifications, including an SSAE 16 certification.

All of our servers are located within an isolated Virtual Network separated from other internal & external networks that prevent unauthorized access.

All data sent to or from Hugo is encrypted in transit and all data stored by Hugo is encrypted at rest, using 256-bit encryption. Our API and application endpoints are TLS/SSL only.

We are currently preparing for a SOC 2 compliance audit, which requires us to have implemented numerous technical, physical, and people-based security processes, including a significant disaster response and recovery plan. 

Hugo is a member of and adheres to the EU-US Privacy Shield Framework

Hugo's read-only access to your calendar means that your data is secure. You can connect with confidence as data is only used to provide the calendar-first experience that powers tens of thousands of companies including Netflix, Shopify and Twitter.

Learn more about Hugo's security here, or contact us.
Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.

Still need help? Contact Us Contact Us