Security for voice-first writing.

Data protection

Typelora is designed to protect audio, transcripts, dictionary entries, and account information through standard web security practices.

• Encryption in transit with HTTPS
• Access controls for application data
• Separation of billing, auth, and product systems where practical

Account security

Authentication and session handling are built around established account infrastructure, with controls intended to reduce unauthorized access.

• Protected dashboard routes
• Session-aware account and billing flows
• Support for secure auth provider practices

Voice and AI processing

Voice and text submitted for transcription or enhancement are processed to return the requested output. We aim to keep these flows scoped to the task users ask Typelora to perform.

• Submitted audio is used for transcription workflows
• Submitted text is used for enhancement workflows
• Custom dictionary entries help improve recognition of user-specific terms

Operational practices

We monitor reliability and errors, keep dependencies under review, and prioritize security fixes that affect user data or service integrity.

• Build and type checks before release
• Monitoring for service health and abuse signals
• Focused access for operational troubleshooting

Responsible disclosure

If you believe you have found a security issue, please report it with enough detail to reproduce the behavior. Avoid accessing or modifying data that does not belong to you.

User responsibilities

Users should protect their devices, keep account access private, review generated output, and avoid submitting information they are not authorized to process.