| name | twinmind-security-basics |
| description | Security best practices for TwinMind: on-device audio processing, encrypted cloud backups, microphone permissions, and data privacy controls.
Use when implementing security basics,
or managing TwinMind meeting AI operations.
Trigger with phrases like "twinmind security basics", "twinmind security basics".
|
| allowed-tools | Read, Write, Edit, Bash(npm:*), Bash(curl:*), Grep |
| version | 1.13.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","twinmind","security"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
TwinMind Security Basics
Overview
Security best practices for TwinMind: on-device audio processing, encrypted cloud backups, microphone permissions, and data privacy controls. TwinMind uses the Ear-3 speech model (5.26% WER, 3.8% DER) for transcription, with GPT-4, Claude, and Gemini for AI summarization.
Prerequisites
- TwinMind account (Free, Pro $10/mo, or Enterprise)
- Chrome extension installed and authenticated
- Understanding of TwinMind workflow
Instructions
Step 1: Setup
TwinMind operates as a Chrome extension and mobile app with optional API access for Pro/Enterprise users.
const config = {
apiKey: process.env.TWINMIND_API_KEY,
model: "ear-3",
aiModels: ["gpt-4", "claude", "gemini"],
};
Step 2: Implementation
const twinmind = {
transcriptionModel: "ear-3",
languages: ["en", "es", "ko", "ja", "fr"],
features: ["transcription", "summary", "action-items"],
privacyMode: "on-device",
};
async function verify() {
const health = ();
.(, health.());
}