Trust & policy
PosMeet is a sensitive-health community. Privacy, moderation and consent cannot live only in fine print, so this hub connects each promise to the control that makes it real.
Current beta principle
A health detail starts private. Sharing is a deliberate action with an audience and identity choice—not the default cost of joining.
The policy set
Plain-language summaries help you navigate; the detailed sections explain the actual boundaries.
Privacy Policy
A product-by-product map of health choices, Community, Circles, Journal, rooms, feedback, safety evidence and account deletion.
Terms of Use
Eligibility, account responsibility, content rights, prohibited use, moderation and the current limits of the beta service.
Community Standards
Memorable rules and concrete examples for privacy, stigma, health claims, sexual boundaries, images and voice rooms.
Supporting notices
Kept separate so Privacy stays readable, but connected here so storage, vendors and policy changes are never buried.
Read-only copies of the exact Privacy, Terms and Standards versions in the registration bundle.
Open noticeAn exact inventory of session cookies, optional Story drafts and other tab-level state.
Open noticeWhat AWS, Agora and Resend receive, when each service is called and what remains unfinished.
Open noticeCurrent versions, material-change rules, registration receipts and unfinished re-consent delivery.
Open noticeHow trust follows the journey
Mature communities repeat the right rule near the action. PosMeet should do the same instead of expecting members to remember a long policy page.
Before the first contribution
Show the six Community commitments, then link the full examples without forcing a wall of legal text into the composer.
Age, policy versions and separate health-personalization choices are explicit.
Audience, Profile or Anonymous identity, image risk and the relevant rule are close to Publish.
Host, room identity, recording mode and one-tap safety controls are visible before entry.
Block acts immediately; Report creates a private trail with a status and reasoned outcome.
Export, retention effects, the seven-day deletion cooling-off period and exceptions are explained before confirmation.
Direct controls
Limited beta readiness
The revised pages describe the product in detail, but content alone does not create compliance. General availability still needs:
What changed
Privacy 1.2 separates Support Needs from optional health personalization, explains encrypted verified email and neutral off-site updates, and makes clear that Community profile visibility governs existing and future profile-mode attribution without changing anonymous, Journal or health boundaries.