🕵️♂️ Your privacy
How we protect you
To make the most out of our personal relationship management tool, you'll have to sync very private data with Nat.
Data like our email interactions, contacts or even our calendars is not something we share easily.
We hope that this page will give you a better understanding of how we use this data.
How and why we access your emails
Emails is where everything happens.
Gmail is aware of this and has made accessing such data extremely complicated for startups. As of January 2020, it will have been 6 months since we started to process to get approved by Gmail's Trust & Safety team. Our friend Ajay from Gmass has written a lot about it.
Because we're not yet approved, you'll receive a very scary warning when you try to sync your inbox. We're sorry about this. You can still continue by clicking Advanced >> Continue.
When you do, you'll see that we only request metadata access to your inbox. This means that we can only see who emails you and when, but not what they, or you, sent. We want to reassure you that we never import or read any email content, simply because we can't. The content of your emails is in Gmail and stays there.
How we use your data
Our algorithm looks at the people you send emails to, how often, who sends you emails and so on. This data get's analysed to find out who are your close contacts, who you're losing touch and to build timelines for your contacts.
Our algorithm accesses your contacts to prevent duplicates & find out who are your real contacts and who are simply newsletters or so.
Our algorithm scans your calendar to find out with whom you met and when. Besides adding this data to the timelines, it improves our algorithm and predicts your closeness with your contacts more accurately.
Further actions we take to protect you
This is your Project section introductory paragraph. Take this opportunity to give a brief overview of the work you do, and let users know what types of projects they’ll find in the showcase below. Try adding an image or video to spark their interest.
We use the industry standard 256-bit encryption with SSL.
Limited access to production environment
Access to production environments is limited to authorized team members only.
Passwords are updated regularly
We update all our critical passwords on a monthly basis. We also use 2FA whenever possible.
Ongoing Hacker Bounty
We have an ongoing hacker bounty program that rewards hackers who find critical issues