home / skills / jeremylongshore / claude-code-plugins-plus-skills / granola-security-basics

This skill helps you implement Granola security basics across data handling, access control, and retention to protect meeting information.

npx playbooks add skill jeremylongshore/claude-code-plugins-plus-skills --skill granola-security-basics

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
5.0 KB
---
name: granola-security-basics
description: |
  Security best practices for Granola meeting data.
  Use when implementing security controls, reviewing data handling,
  or ensuring compliance with security policies.
  Trigger with phrases like "granola security", "granola privacy",
  "granola data protection", "secure granola", "granola compliance".
allowed-tools: Read, Write, Edit
version: 1.0.0
license: MIT
author: Jeremy Longshore <[email protected]>
---

# Granola Security Basics

## Overview
Implement security best practices for protecting meeting data in Granola.

## Data Flow & Security

### How Granola Handles Data
```
Audio Capture (Local Device)
        ↓
Encrypted Transmission (TLS 1.3)
        ↓
Processing Server (Transient)
        ↓
Encrypted Storage (AES-256)
        ↓
Access via App (Auth Required)
```

### Key Security Features
| Feature | Status | Details |
|---------|--------|---------|
| Encryption at rest | Yes | AES-256 |
| Encryption in transit | Yes | TLS 1.3 |
| SOC 2 Type II | Yes | Certified |
| GDPR compliant | Yes | EU data options |
| Audio retention | Configurable | Delete after processing |

## Access Control Best Practices

### Personal Account Security
```markdown
## Checklist
- [ ] Use strong unique password
- [ ] Enable 2FA (two-factor authentication)
- [ ] Review connected apps regularly
- [ ] Log out from shared devices
- [ ] Use SSO if available (Business/Enterprise)
```

### Sharing Permissions
| Share Level | Access | Use Case |
|-------------|--------|----------|
| Private | Owner only | Sensitive meetings |
| Team | Workspace members | Internal meetings |
| Link (View) | Anyone with link | Read-only sharing |
| Link (Edit) | Anyone with link | Collaborative notes |

### Configure Sharing Defaults
```
Settings > Privacy > Default Sharing
- New meetings: Private (recommended)
- Auto-share with attendees: Off (for sensitive meetings)
- External sharing: Disabled (for compliance)
```

## Sensitive Meeting Handling

### Pre-Meeting
```markdown
## Sensitive Meeting Checklist
- [ ] Disable auto-recording
- [ ] Confirm attendee list
- [ ] Review sharing settings
- [ ] Check for screen share visibility
- [ ] Consider using "Off the Record" mode
```

### During Meeting
- Announce recording to all participants
- Pause recording for sensitive discussions
- Avoid displaying sensitive documents on screen

### Post-Meeting
- Review notes before sharing
- Redact sensitive information
- Use private sharing link
- Set expiration on shared links

## Data Retention & Deletion

### Retention Settings
```
Settings > Privacy > Data Retention

Options:
- Keep forever (default)
- Delete audio after 30 days
- Delete audio after 7 days
- Delete audio immediately after processing

Recommendation: Delete audio after processing
(Notes are retained, raw audio is deleted)
```

### Manual Deletion
```markdown
## Delete Meeting Data

1. Open meeting in Granola
2. Click ... menu > Delete
3. Confirm deletion
4. Note: Deletion is permanent

## Bulk Deletion
1. Settings > Data
2. Export data (backup)
3. Select date range
4. Click "Delete meetings in range"
```

### Export & Portability
```markdown
## Data Export Options

Formats:
- Markdown (.md)
- PDF
- Word (.docx)
- JSON (full data)

Export includes:
- Meeting notes
- Transcripts
- Action items
- Metadata

Does NOT include:
- Raw audio files
- AI model data
```

## Compliance Considerations

### GDPR (EU Users)
| Requirement | Granola Support |
|-------------|-----------------|
| Right to access | Data export available |
| Right to delete | Full deletion option |
| Data portability | JSON export |
| Consent | Recording notifications |
| DPA available | Yes (Business plans) |

### HIPAA (Healthcare)
- Standard plans: Not HIPAA compliant
- Enterprise: BAA available on request
- Recommendation: Use only for non-PHI meetings

### SOC 2 Type II
- Granola is SOC 2 Type II certified
- Audit reports available for Enterprise customers
- Covers security, availability, confidentiality

## Team Security (Business Plans)

### Admin Controls
```markdown
## Available Controls
- [ ] Enforce SSO login
- [ ] Set password policies
- [ ] Manage user permissions
- [ ] View audit logs
- [ ] Control external sharing
- [ ] Enforce 2FA
- [ ] IP allowlisting
```

### Audit Logging
```
Available Events:
- User login/logout
- Meeting recorded
- Notes shared
- Data exported
- Settings changed
- User added/removed
```

## Security Incident Response

### If Account Compromised
1. Immediately change password
2. Revoke all sessions (Settings > Security > Sign out everywhere)
3. Review recent activity
4. Check shared notes
5. Enable 2FA if not already
6. Contact support if data exposed

### Reporting Security Issues
- Email: [email protected]
- Include: Detailed description, steps to reproduce
- Response: Within 24 hours

## Resources
- [Granola Security](https://granola.ai/security)
- [Privacy Policy](https://granola.ai/privacy)
- [Trust Center](https://granola.ai/trust)

## Next Steps
Proceed to `granola-prod-checklist` for production deployment preparation.

Overview

This skill documents security best practices for protecting meeting data in Granola. It summarizes encryption, access controls, retention options, and compliance considerations to guide secure deployment and daily use. Use it to design controls, review policies, or onboard teams on meeting-data security.

How this skill works

The skill explains how Granola handles meeting data from local audio capture through encrypted transmission (TLS 1.3), transient server processing, and AES-256 encrypted storage. It breaks down access controls, sharing levels, retention and deletion workflows, admin controls for teams, and incident response steps. Compliance mappings for GDPR, HIPAA, and SOC 2 Type II are included to align operational choices with regulatory needs.

When to use it

  • Implementing security controls for Granola in a project or workspace
  • Reviewing data handling and sharing settings before go-live
  • Configuring retention and deletion policies to meet compliance
  • Preparing incident response and user-recovery procedures
  • Onboarding admins and users to secure meeting practices

Best practices

  • Default new meetings to private and disable auto-share for sensitive sessions
  • Enable strong unique passwords and enforce 2FA or SSO where available
  • Delete raw audio after processing; retain notes only as needed
  • Restrict external sharing and set link expirations for shared content
  • Use admin controls: enforce SSO, password policies, audit logging, and IP allowlisting

Example use cases

  • Pre-launch security checklist for a product team using Granola for internal meetings
  • Compliance review to ensure GDPR export/deletion workflows are in place
  • IT admin configuration for a business workspace: SSO, 2FA, and sharing defaults
  • Incident response playbook when an account is suspected compromised
  • Data lifecycle setup: automatic audio deletion after processing and scheduled bulk deletions

FAQ

Is Granola encrypted in transit and at rest?

Yes. Granola uses TLS 1.3 for transmission and AES-256 for data at rest.

Can I delete raw audio automatically?

Yes. Retention settings allow deleting audio immediately after processing or after configurable windows (7 or 30 days). Notes and transcripts are handled separately.

Is Granola HIPAA compliant?

Standard plans are not HIPAA compliant. Enterprise customers can request a BAA and should limit PHI to properly configured Enterprise environments.

What should I do if an account is compromised?

Change the password immediately, revoke all sessions, enable 2FA, review recent activity and shared items, and contact support/security if sensitive data may be exposed.