Security philosophy
Least privilege, server-enforced permissions, and desktop hardening. We do not claim Zero Trust or E2EE audio until those systems are real.
Trust Center
Trust is earned with honesty.
Trustworthy communication starts with clear boundaries: what ships, what is Coming soon, and what we refuse to invent.
Privacy approach
User-visible privacy controls, consent for policy changes, and channels for privacy requests — aligned with GDPR/KVKK practice, not a certificate badge.
Account protection
Authenticated sessions today. MFA / 2FA is on the roadmap as Planned — never shown as available early.
Safety standards
Community guidelines, reporting, and moderator roles. Automated AI safety is Planned and labeled as such.
Compliance posture
We publish policies, diagnostics notices, and request flows. Legal compliance is ongoing work — not a marketing slogan.
Honesty rules
What you will not see claimed here
These claims are forbidden on picom.gg until implemented and verified:
- End-to-end encrypted audio
- Recording or transcription as available features
- User MFA as a shipped control
- AI safety / trust scores as live product modules
- GDPR/KVKK “certified” language
Read the detail.
Security page covers audio privacy and permissions. Roadmap shows what is next.