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 Center
A practical trust center for a local-first AI voice product.
VoiceSlate is built around local-first records, provider flexibility, and product behavior that users can inspect instead of simply trusting by default.
What trust means here
Control, visibility, and clear support paths come before marketing language.
The trust model is simple: keep local artifacts visible, keep provider choice open, and stay specific about what is available today.
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.
Current boundaries
The public trust posture should be explicit about scope.
This is the current product posture for the website and public release.
- VoiceSlate keeps the public download trail visible through GitHub Releases.
- The product direction favors local-first archives before hosted lock-in.
- BYOK provider flows remain part of the trust model because optionality matters.
- Questions about product scope or evaluation can go to [email protected].
Reach the team directly at [email protected] for evaluation or trust questions.
Trust plus product context
Pair trust review with the product pages that lead to action.
The trust center should point people back to the product, the downloads path, and the release history instead of becoming a dead end.