Privacy Policy
privacy-beta-1.2You decide what belongs in the room—and what stays yours.
This notice follows the real PosMeet experience: joining, choosing support, sharing with a profile or anonymously, entering a voice room, keeping a private Journal and receiving a discreet update away from the site.
Health stays private
Conditions, health journey and Journal entries are never profile fields.
One visibility control
Making your profile private also neutralizes existing profile-mode author cards.
Discreet email
Off-site updates use neutral wording and follow your delivery settings.
No silent recording
Current live rooms are not recorded by PosMeet.
What changed in 1.2
The short version
A sexual-health community needs boundaries that are understandable before—not after—you share.
- Your verified email is never displayed to other members.
- Conditions, health journey, support preferences and Private Journal entries do not become profile fields.
- Support Needs are optional organization preferences. We may use them to suggest Circles even when Health Personalization is off, without inferring that you have a particular condition.
- A Community Profile post and an Anonymous post are different identity choices. Changing profile visibility affects profile-mode attribution; it does not reveal anonymous history or move Journal entries into Community.
- We do not sell personal or health information, broker it, or use it for cross-site behavioral advertising.
Peer support, not a medical record
What we collect
We separate community identity, private health context and operational safety records instead of treating them as one profile.
| Area | Examples | Normal visibility |
|---|---|---|
| Account & security | Verified email, adult confirmation, locale, time zone, session times, coarse device class, browser family and operating-system family, consent receipts and abuse-prevention signals. | You and authorized PosMeet systems or operators. |
| Community profile | Display name, avatar, bio and optional non-health social details you choose to add. | Signed-in members only while your profile visibility is Community-visible. |
| Health context | Participation role, selected conditions and health journey stage. | Private account data unless you independently choose to write about it in Community. |
| Support preferences | The support needs you select, such as everyday support or communication help. | Private account preferences used to organize suggestions; they do not appear on your profile. |
| Community & Circles | Posts, replies, reactions, saves, images and Circle membership or activity. | The signed-in audience or Circle access shown before you contribute. |
| Private Journal | Mood, symptoms, optional note, voice note and retention choice. | Never shown in Community or on your profile. Operational access is tightly limited. |
| Voice rooms | Reservation, room identity, attendance, speaking role, hand requests and moderation events. | People in the room see your room identity; restricted safety records are not public. |
| Feedback & safety | Private feedback, screenshots, reports, report-time evidence, blocks, appeals and review history. | You and specifically authorized Care or safety reviewers, as applicable. |
| Journey & notifications | Optional contribution facts, levels, keepsakes, notification settings and delivery status. | Private by default; only profile elements you deliberately enable are displayed. |
Account & security
Verified email, adult confirmation, locale, time zone, session times, coarse device class, browser family and operating-system family, consent receipts and abuse-prevention signals.
Who normally sees it: You and authorized PosMeet systems or operators.
Community profile
Display name, avatar, bio and optional non-health social details you choose to add.
Who normally sees it: Signed-in members only while your profile visibility is Community-visible.
Health context
Participation role, selected conditions and health journey stage.
Who normally sees it: Private account data unless you independently choose to write about it in Community.
Support preferences
The support needs you select, such as everyday support or communication help.
Who normally sees it: Private account preferences used to organize suggestions; they do not appear on your profile.
Community & Circles
Posts, replies, reactions, saves, images and Circle membership or activity.
Who normally sees it: The signed-in audience or Circle access shown before you contribute.
Private Journal
Mood, symptoms, optional note, voice note and retention choice.
Who normally sees it: Never shown in Community or on your profile. Operational access is tightly limited.
Voice rooms
Reservation, room identity, attendance, speaking role, hand requests and moderation events.
Who normally sees it: People in the room see your room identity; restricted safety records are not public.
Feedback & safety
Private feedback, screenshots, reports, report-time evidence, blocks, appeals and review history.
Who normally sees it: You and specifically authorized Care or safety reviewers, as applicable.
Journey & notifications
Optional contribution facts, levels, keepsakes, notification settings and delivery status.
Who normally sees it: Private by default; only profile elements you deliberately enable are displayed.
We also receive technical information needed to deliver and protect the service, including request time, browser or device details, IP-derived security signals, delivery diagnostics and actions taken in the interface. We do not require precise location for the current product. In the member-facing active-session record, we retain only a coarse device class, browser family and operating-system family—not a full User-Agent string or raw IP address.
The visibility boundaries
Profile visibility, post identity and content audience answer different questions.
Community-visible profile
Signed-in members can see your display name, avatar, bio and optional non-health social details.
Private profile
Existing and future profile-mode Story and response author cards use a neutral PosMeet Member identity while the setting remains private. The content is not deleted.
Anonymous contribution
Members see a neutral identity and cannot open a profile from it. Changing profile visibility never converts it into profile-mode content.
Circle activity
People with access to the Circle see the contribution. There is no public Circle member directory.
Private Journal
Never shown in Community, on your profile or in a member search. Retention and deletion are controlled separately.
Health & support choices
Conditions, journey stage and Support Needs stay private even when your Community profile is visible.
Anonymous to members—not to safety systems
A member can still copy, quote, screenshot or infer identity from details you choose to share. A visibility control reduces exposure; it cannot make already shared words impossible to copy.
Why we use information
Each use is tied to a product purpose; joining does not grant a blanket right to repurpose sensitive information.
- Provide the service: authenticate you, save preferences, display authorized contributions, deliver media, reserve rooms and keep your Journal available to you.
- Organize your experience: use selected Support Needs for topic and Circle suggestions, and use health context only under the separate choice described below.
- Protect people: enforce blocks, review reports, preserve bounded evidence, detect coordinated abuse and maintain service integrity.
- Communicate: deliver authentication, required account or safety notices and optional neutral updates through the channels you enable.
- Improve reliability: diagnose failures and measure whether core flows work without placing health or Journal content in ordinary product analytics.
- Listen to members: show optional questions, retain a skip so we do not repeatedly interrupt you, and ask whether a shipped improvement helped.
Support suggestions and optional health personalization
These are two independent recommendation inputs with different privacy consequences.
Support Needs
You can select up to the number shown in the interface, skip the question, change your choices or clear them later. PosMeet may use those selections to suggest official Circles or topics without a Health Personalization grant. A Support Need is not displayed to members and is not treated as proof of a diagnosis.
Separate control does not mean non-sensitive
Health Personalization
Selected conditions, participation role and health journey stage are used for health-based recommendations only after you grant the separate, current Health Personalization choice. It is off without a current grant. Revoking it stops future health-based recommendations; it does not delete private facts you choose to keep in your account.
Private Journey
If you start Private Journey, eligible contribution facts made after you enable it can calculate levels and keepsakes. Anonymous contributions can count through the protected internal account link, but do not become a public anonymous-history page. You can pause, hide profile display, delete keepsakes, export or clear Journey.
Review recommendation and Journey choices Sign-in requiredChange Support Needs, health personalization, visibility and Journey controls from your private account space.Verified email and discreet off-site updates
Email is an account channel, not a public identity or a place for sensitive community content.
- The verified address is stored encrypted in protected identity records, with a one-way keyed representation used for account lookup and abuse prevention.
- PosMeet decrypts the address only inside an authorized delivery path when it must call the email provider. The provider necessarily receives the address and delivery metadata to send the message.
- Optional off-site categories follow your notification settings. Required account, security or safety messages can remain enabled when they are necessary to operate or protect your account.
- Notification email uses neutral PosMeet wording. The subject and preview do not name an STI, diagnosis, support need, Journal entry, Circle or voice-room topic; you sign in to view the update.
- Quiet hours delay ordinary optional updates. Time-sensitive account or safety delivery may bypass them when waiting would create risk.
A shared inbox is still a shared surface
Voice rooms, images and audio
A voice or image can identify someone even when their display name does not.
Current rooms are labelled Not recorded. Agora carries live audio, but PosMeet does not keep the conversation audio. PosMeet does store reservations, room identity, attendance, stage role, moderation events and a limited post-room reporting window. Other participants hear your voice and may violate the rules by recording it themselves.
Profile and Community images are resized and re-encoded to remove embedded camera and location metadata before publication. Standard media is stored in private Amazon S3 and delivered through CloudFront, but anyone who receives an exact standard-media URL may be able to open or share it while it remains available or cached.
Journal voice notes and feedback screenshots use private-media access. Journal text is application-encrypted before database storage. Private audio and images use restricted object storage and short-lived access; PosMeet does not claim they are end-to-end encrypted.
Future recording requires a new decision
Service providers and international processing
A provider receives only what is needed for its role, but using one is still a disclosure.
Amazon Web Services / CloudFront
Store private and standard media and deliver standard media through a CDN.
Data involved: Uploaded images or audio, object identifiers and delivery requests.
Agora
Carry live room audio and connection diagnostics.
Data involved: Room identifiers, technical connection data and live audio while connected.
Resend
Deliver authentication messages and enabled neutral account updates.
Data involved: Email address, neutral transactional message and delivery diagnostics.
Providers may process information outside your country. Production agreements must restrict their use to the contracted service and applicable legal duties. PosMeet does not authorize them to use member information for targeted advertising.
Open the service-provider registerSee each provider, the feature it supports and the data path involved.How long information stays
Different records need different clocks; private health content is not kept merely because an account once existed.
Authentication & sessions
Minutes to 30 days
Verification challenges expire within the period shown in the sign-in flow. Active web sessions last no more than 30 days; bounded security cleanup follows expiry or revocation.
Private Journal
30 / 90 / 365 days, or until deleted
The period runs from each entry’s creation. Shortening it can make older entries immediately eligible for irreversible deletion.
Room incident reporting
7-day reporting window
A limited attendance reference remains reportable after departure so a member is not forced to report while distressed. Safety evidence normally follows its separate 180-day rule.
Private feedback
Two years after closure
Feedback threads, private replies and attachments are scheduled for deletion after closure unless a justified hold applies.
Account deletion
7-day cooling-off period
You may cancel before execution. Deletion removes private data, retires identity and preserves only scoped non-identifying records where required.
Consent & deletion proof
Up to 7 years
Minimal, non-content receipts can remain to prove a policy choice or completed deletion and to meet legal obligations.
Caches, backups and justified holds
Your controls and privacy rights
Product controls are available to every member; additional statutory rights depend on where you live.
Hiding a profile, deleting a post, clearing Journey and deleting an account are separate actions. PosMeet will not treat a request to use a privacy control as a popularity or trust signal.
Security, contact and policy changes
No system is risk-free; sexual-health information deserves layered controls and an honest record of change.
- Use encrypted transport, protected identity records, private object storage and separation between community and sensitive records.
- Restrict staff by role, audit access to sensitive operations and preserve reviewable moderation decisions.
- Remove image metadata, use short-lived private-media access and keep credentials or internal identifiers out of member URLs.
- Investigate unauthorized access or disclosure and notify affected people and authorities when applicable law requires it.
Signed-in members can use Help & feedback for a private privacy question. Before broad public launch, PosMeet must publish its legal operating entity, monitored privacy contact, mailing address, launch regions and any required regional representative or transfer details.
A material change receives a new version, effective date, stable archive URL and plain-language summary. Expanded sensitive-data use requires a fresh, specific choice where law or product integrity requires it; continued browsing is not a substitute.
Version integrity
registration-beta-1.2 contains Terms terms-beta-1.1, this Privacy Policy privacy-beta-1.2 and Community Standards standards-beta-1.1. A registration challenge freezes those exact components, and earlier 1.1 receipts continue to reopen their original archived text.