Introduction
NoteWave uses reasonable technical and organisational measures to protect your meeting recordings, transcripts, and personal data. This article explains our security practices and the protections we provide.
Data Encryption
NoteWave uses encrypted connections and managed storage protections as part of its security controls.
HTTPS/TLS protects supported data moving between your device and NoteWave services.
Managed database and private storage services apply encryption at rest and access controls to stored data.
Layered Protection
Infrastructure Security
NoteWave uses managed application, data, processing, and billing services with technical and contractual safeguards appropriate to their role.
Security layers:
- Private application infrastructure - Hosts the customer-facing product and protected processing services
- Managed data services - Provide authenticated database and private file-storage controls
- Specialist processing services - Process limited data needed to provide transcription and AI features
- Secure billing services - Handle card entry, store purchases, and payment verification
- Contractual controls - Service providers process data under the arrangements described in our Privacy Policy
Authentication & Access Control
Multiple layers of authentication protect your account from unauthorized access.
Security features:
- Connected sign-in - Supported OAuth providers let you sign in without sharing their password with NoteWave
- Protected sessions - Signed session tokens and server-side checks help protect account access
- Password protection - Password-based accounts use managed authentication and secure password storage
- Email verification - Email ownership is verified during applicable account flows
Best Practice
Row Level Security (RLS)
Database-level security policies help isolate records and enforce owner, sharing, and team access rules.
What RLS protects:
- Meetings and transcripts are isolated to their owners
- Shared transcripts enforce explicit permission checks
- Team data requires membership verification
- Payment and subscription data is strictly user-specific
Database policies add an important layer of defence, but they work alongside application checks, authenticated requests, and regular security review.
Security Monitoring
NoteWave and its infrastructure services record and monitor relevant operational and security events.
Relevant operational and security events can be recorded and reviewed to investigate failures, abuse, or suspicious activity.
Managed infrastructure includes recovery and continuity controls appropriate to the service. NoteWave should not be treated as your only archive for critical records.
Webhook Security
Supported integration and billing webhooks are checked using the verification mechanism required by the sending service, such as cryptographic signatures or validated tokens.
Request Verification
Data Breach Notification
If we become aware of a security compromise involving personal information, we will investigate, take reasonable containment and remediation steps, and provide notifications where applicable law requires them.
Our response includes:
- Notice as soon as reasonably possible where required by law
- Available information about the nature and likely consequences
- Reasonable containment and remediation steps
- Practical actions affected users can take where appropriate
Security Limitations
While we implement comprehensive security measures, no system is 100% secure. You play a critical role in protecting your account.
Your Responsibility
Was this article helpful?
Your feedback helps us improve our documentation.