Security

Wool reduces risk by avoiding server-side storage of dictated content. Saved transcription history, dictionary entries, snippets, and product preferences remain on your device. The application service stores numeric usage totals rather than the words you spoke.

Authenticated clients obtain short-lived access for live transcription. Transcript cleanup requests pass through Wool’s Cloudflare-hosted service to Groq and are handled transiently. Wool does not persist request bodies or transcript content in its application database.

Current account safeguards include:

• Secure cookies in production and time-limited sessions.
• Hashed password credentials managed through the Better Auth framework.
• Authentication rate limiting and protected desktop authorization flows.
• Application-level IP address tracking disabled in authentication.
• Database relationships that remove associated usage information when an account is deleted.

Wool runs on Cloudflare Workers and Cloudflare D1. Transport encryption protects traffic in transit. Sampled infrastructure logs and traces are used for reliability and security diagnostics; application code does not intentionally log transcript content.

No service can guarantee absolute security. You can help by using a unique password, protecting access to your computer, keeping Wool and your operating system updated, and reviewing dictated text before sharing it.

If you believe you found a security issue, contact the Wool team privately through the support channel in the application. Include steps to reproduce the issue and avoid accessing, changing, or sharing another person’s data. We will review good-faith reports and work to address verified issues.