Privacy policy
This policy explains how Nata (“we”, “us”) handles personal data. It covers what we collect and why, how we handle it, and your rights. We never sell personal data, and we never use it for advertising.
Who this policy covers
This policy covers:
- visitors to this website, natasecurity.com;
- people who use the Nata app at app.natasecurity.com (our customers’ admins and members);
- people who email us.
Our customers also put data about other people into Nata: their employees and contractors (the people roster), the accounts in their identity provider, and whatever is in the evidence they upload. For that data the customer decides what goes in and why; we process it only to provide Nata to them, on their instructions. If you’re one of those people, for example you received a policy acceptance email from Nata on behalf of your employer, please contact your employer about your data. We’ll help them answer you.
What we collect and why
We collect only what Nata needs to work.
This website
This website sets no cookies and runs no analytics, trackers or third-party scripts. Our hosting provider (Google Firebase Hosting) processes your IP address and browser details to deliver the pages.
Your Nata account
- Email address, to sign you in and send you the messages you need (sign-in links, invitations, notifications you’ve chosen).
- Passkeys: the public key, a name for each passkey (by default your browser and operating system, like “Chrome on macOS”), and when it was created and last used. Your private key never leaves your device.
- Sign-in links and sessions are stored only as one-way hashes, along with the email a link was sent to and when a session was last active.
- Your role in your organization, and your notification preferences.
Nata has no passwords, so we never collect or store one.
Data our customers put into Nata
- People roster: full name, email, job title, department, employee or contractor, and start and end dates.
- Policy acceptances: which policy version a person accepted, and when. These records can’t be changed or deleted, because they’re compliance evidence.
- Training: completed courses, completion dates, and uploaded certificates.
- Evidence: files and titles uploaded by the customer. These can contain anything the customer chooses to upload.
- Directory data from the customer’s identity provider (Google Workspace, Okta or Microsoft Entra ID), when the customer connects it: each account’s email, display name, whether it’s active or an administrator, whether it has multi-factor authentication (and, for Okta, whether it relies only on SMS or voice), its last sign-in time and when it was created. Nata compares these with the roster to show the customer which accounts need attention.
- Code hosting data (GitHub or GitLab), when the customer connects it: repository settings, and the usernames and roles of people with access to the monitored repositories.
- Integration credentials (access tokens, API keys, Slack webhook addresses), encrypted before they’re stored.
- Activity log: who (by email) created, changed or deleted what, and when. It records chosen fields only, never file contents or secrets, and it can’t be changed.
Google user data
When a customer connects Google Workspace, Nata reads its user directory with read-only access. It stores only the fields listed above (email, display name, active and administrator status, 2-Step Verification enrollment, last sign-in and account creation time), and uses them only to show the customer their own compliance status in Nata.
We don’t sell this data, use it for advertising, use it to train AI models, or let people read it except as described in “When we access or share your information”. Nata’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Cookies in the app
The app sets one cookie, nata_session, which keeps you signed in and protects your forms against cross-site request forgery. It’s essential, so there’s nothing to opt out of. Nata sets no other cookies and uses no analytics or advertising.
Security and operations
To protect Nata, we limit how often sign-in and other sensitive requests can be made. That uses your IP address in memory only; we don’t store it. Our server logs record which page type was requested, the result and how long it took. They don’t record IP addresses, email addresses, cookies or the content of requests.
Email to us
When you email us (for example privacy@, security@ or sales@natasecurity.com), we keep the conversation so we can refer back to it.
When we access or share your information
Service providers. We use a few companies to run Nata. They process personal data only to provide their service to us:
| Provider | What for | Data | Location |
|---|---|---|---|
| Google Cloud Platform (Google LLC) | hosting the app, database, uploaded files and backups | all app data | USA (Iowa, us-central1) |
| Amazon Web Services, Inc. (Amazon SES) | sending the app’s email | recipient email address and name, message content | USA (us-east-1) |
| Google Workspace (Google LLC) | our own email | whatever you send to our addresses | USA |
| Google Firebase Hosting (Google LLC) | hosting this website | visitors’ IP address and browser details | Global network |
We’ll update this list before we add a provider that handles customer data.
Services you connect. When a customer connects an integration (for example Slack, GitHub, GitLab, Okta, Microsoft Entra ID or Google Workspace), Nata exchanges data with it on the customer’s instruction. Notifications sent to a connected Slack channel include task titles, which can include a person’s name or email address.
People at Nata. No one at Nata looks at a customer’s data except to help with a support request you’ve asked for help with, to fix an error that stops Nata from working, to investigate abuse, or when the law requires it.
When the law requires it. We disclose data to authorities only when legally compelled, such as by a valid subpoena, court order or warrant, and we tell the affected customer first unless we’re legally prohibited from doing so.
If Nata changes hands. If Nata is acquired or merges with another company, we’ll tell you before your personal data is transferred or becomes subject to a different privacy policy.
How long we keep data
- Customer data stays in Nata while the organization is a customer. When an organization stops using Nata, or asks us to, we delete its data within 30 days. Today we do this on request; the app doesn’t have a delete button for a whole organization yet.
- A removed member loses access right away, and their sessions are ended. Their email stays in the organization’s activity log, which is kept for as long as the organization’s data.
- Directory data is replaced on every sync and deleted when the customer disconnects the identity provider.
- Sign-in links expire after 15 minutes. Sessions end after 60 minutes of inactivity or 12 hours, whichever comes first.
- Backups: deleted data can remain in backups until they’re replaced. Daily backups are kept for up to 14 days, and the database’s most recent backups taken before each software update are kept until newer ones replace them. Uploaded files (evidence and certificates) are kept as earlier versions for 30 days after they’re deleted, then can be recovered for 7 more days before they’re gone for good.
How we protect data
All traffic to Nata and this website is encrypted in transit (HTTPS). Google Cloud encrypts stored data, including the database, backups and uploaded files. The database is reachable only on a private network and requires encrypted connections, and integration credentials are encrypted before they’re stored. Uploaded files are kept in private storage where the app can add and read files but can’t change or delete them. Every organization’s data is kept apart both by the application and by database-level rules. There’s more on our Security page.
Your rights
Wherever you live, you can ask us to:
- tell you what personal data we hold about you and how we use it;
- give you a copy of it;
- correct it;
- delete it (if you’re an account user, that ends your access to Nata);
- restrict or stop processing it, or object to how we use it.
Email privacy@natasecurity.com. We may need to confirm your identity first, usually by replying from the email address we have for you. If someone asks on your behalf, we’ll need your signed permission. If we say no to a request, we’ll explain why and how you can appeal. We won’t treat you differently for using these rights.
If your data is in Nata because a customer put it there (for example you’re on your employer’s people roster), we’ll pass your request to that customer and help them answer it.
You can also complain to your data protection authority.
Where your data is
Nata runs in the United States. If you’re outside the US, your data will be transferred to and stored in the US. Customers who need a data processing agreement can ask for one at privacy@natasecurity.com.
Children
Nata is a business service and isn’t meant for anyone under 16. We don’t knowingly collect data from children.
Changes to this policy
We’ll update this policy when our practices change, and change the date at the top. If we make a significant change, we’ll tell customers by email before it takes effect.
Questions
Email privacy@natasecurity.com.
This policy is adapted from the Basecamp privacy policy by 37signals, used under CC BY 4.0. We rewrote it for Nata.