Local-first data handling
History, screenshots, archives, and learning signals are designed to stay visible and anchored locally instead of disappearing into a remote black box.
Trust & security
A local-first trust posture for AI voice workflows.
VoiceSlate is being shaped around local-first records, provider flexibility, and product behavior that users can inspect instead of simply trusting on faith.
Trust pillars
Security here starts with visibility, control, and honest boundaries.
The commercial stack is still maturing, but the trust model is already clear: keep local artifacts visible, keep provider choice flexible, and keep support paths explicit.
Bring your own providers
VoiceSlate is useful before a hosted stack is complete, so provider choice stays flexible rather than hidden behind a single locked workflow.
Inspectable memory behavior
Project memory, archive summaries, and learned vocabulary are intended to be inspectable and manageable instead of silently reshaping work.
Clear support and release trail
Trust is also operational. The public download path, release history, and support email help people evaluate what is real today.
What is true today
The clearest security page is the one that says exactly what exists now.
These facts help evaluators understand the current release without forcing them to infer trust posture from vague language.
- Current public product scope: Windows desktop workflow
- Support contact: [email protected]
- Primary trust model: local-first archives plus BYOK provider flexibility
- Public release trail: GitHub Releases and website changelog
Questions about rollout, provider setup, or trust review can go straight to [email protected].
Trust plus action
Review the trust posture, then go back to the product or install path.
Security pages should support conversion, not isolate from it. The next useful steps are the homepage and the downloads page.