Self-Hosting VoiceChatMate: A Privacy Checklist for Operators

If you deploy VoiceChatMate yourself: what to put in Seo:PublicBaseUrl, logs, retention, abuse contacts, and why visitors deserve consistent policy pages.

VoiceChatMate is designed to be self-hosted. If you run an instance for the public internet, visitors judge trust by consistency: the domain in the address bar should match Seo:PublicBaseUrl, your support inbox, and the legal names on policy pages.

Set PublicBaseUrl honestly

Canonical tags, Open Graph URLs, and /sitemap.xml all derive from Seo:PublicBaseUrl. A mismatch between https://example.com and https://www.example.com looks like a neglected site to humans and crawlers alike.

Publish Seo:SupportEmail and LegalEntityName

AdSense-style reviews look for reachable humans. Put SupportEmail and LegalEntityName in configuration—they surface on /contact and the footer when set.

Align retention with your privacy story

The codebase includes retention knobs (for example conversation cleanup intervals). If you log aggressively for abuse investigations, say so plainly on /privacy. Surprises erode trust faster than imperfect but honest policies.

Moderation integrations are your responsibility

Placeholder classifiers are not production-ready. Wire real providers before marketing to vulnerable populations.


User-facing context: Privacy overview · Terms template

Try VoiceChatMate

Open the lobby to pick a display name, then text, voice, or video.