twinmind-data-handling

TwinMind Data Handling

Contents

• Overview
• Prerequisites
• Instructions
• Output
• Error Handling
• Examples
• Resources

Overview

Data privacy, retention, and compliance procedures for TwinMind meeting transcriptions including PII redaction, GDPR data subject requests, consent management, and data anonymization.

Prerequisites

• Understanding of GDPR/CCPA requirements
• TwinMind account with admin access
• Database access for data management
• Legal/compliance team consultation

Instructions

Step 1: Configure Data Retention Policies

Define RetentionPolicy with configurable retention days for transcripts (default 90), summaries (linked to transcript), action items (180 days), and user profiles (30 days post-deletion). Implement auto-cleanup job for expired data.

Step 2: Implement PII Redaction

Build PII detection with regex patterns for SSN, credit card, email, phone, and IP address. Create redactPII() function returning redacted text and a count of redactions by type. Enable automatic redaction via TwinMind settings API.

Step 3: Handle GDPR Data Subject Requests

Implement GDPRHandler with right to access (Article 15), right to erasure (Article 17), and right to data portability (Article 20). Track DSR requests with 30-day deadline and compliance team notifications.

Step 4: Manage Consent

Build ConsentManager tracking consent per purpose (transcription, aiProcessing, storage, sharing, marketing). Add Express middleware requireConsent() that blocks processing without valid consent.

Step 5: Data Anonymization

Implement transcript anonymization using HMAC-based ID hashing, PII redaction, and speaker name replacement for analytics exports.

See detailed implementation for complete retention policy, PII patterns, GDPR handlers, consent manager, and anonymization code.

Output

• Data retention policy configuration
• PII redaction implementation
• GDPR request handlers
• Consent management system
• Data anonymization utilities

Error Handling

Issue	Cause	Solution
DSR deadline missed	Processing delay	Automate DSR handling
PII not redacted	Pattern not matched	Update regex patterns
Consent invalid	Version mismatch	Re-request consent
Data not deleted	Cascade failure	Verify deletion recursively

Examples

Basic usage: Apply twinmind data handling to a standard project setup with default configuration options.

Advanced scenario: Customize twinmind data handling for production environments with multiple constraints and team-specific requirements.

TwinMind Privacy Features

• No audio storage: Audio processed in real-time and immediately deleted
• On-device processing: Option for local transcription
• Encrypted storage: Transcripts encrypted with user-controlled keys
• Data residency: Choose storage region (EU, US, APAC)

Resources

• GDPR Official Text
• TwinMind Privacy Policy
• TwinMind DPA Template

Next Steps

For enterprise access control, see twinmind-enterprise-rbac.