Policy updates
Change ledger 1.1What changed should never be a guessing game.
This page connects the policy text members can read today with the exact registration versions PosMeet stores, their read-only public snapshots and any re-consent work a future material change may require.
Dated changes
Each ledger entry explains the member-facing effect, not only a version number.
Notice near the feature
A material change should be explained where the affected choice is made.
Fresh choice when needed
Expanded sensitive-data use should not rely on silent continued use.
Versioned receipts
A receipt should identify the exact document version and acceptance time without copying member content.
Registration receipts now match
registration-beta-1.2 and separately records terms-beta-1.1, privacy-beta-1.2 and standards-beta-1.1. The exact component versions are frozen when the email verification challenge is requested so a later policy change cannot silently alter what the member confirms. Earlier 1.1 receipts still point to their original snapshots.Current member-facing documents
These are the versions in the current registration bundle. Each version link opens a stable read-only snapshot.
“Updated” describes the text on the page. It does not by itself prove that a member accepted that exact version. Acceptance is a separate database receipt described below.
Limited Web Beta change ledger
This ledger is reconstructed from the current product pages and versioned consent records in the application.
October 2, 2026
Clearer recommendation, profile and email boundaries
Published Privacy 1.2 and registration bundle 1.2. Support Needs can now guide Circle suggestions independently of optional health personalization; verified email can deliver neutral off-site updates according to notification settings; and the member profile visibility control applies to existing and future profile-mode content without crossing Journal, anonymous or health boundaries.
September 30, 2026
Trust & Policy redesign
Expanded the data and visibility map; corrected Journal audio encryption language; named AWS/CloudFront, Agora and Resend; documented safety evidence, feedback attachments, Private Journey, product listening, on-device drafts and account deletion; and added STI-specific Community examples. The matching versioned registration bundle is active for new account creation.
September 20, 2026
Health Personalization version 1
Added a versioned choice for using participation role, selected conditions, support needs and journey stage to suggest relevant topics or Circles. The choice can be revoked without deleting the private account facts a member keeps.
September 17, 2026
Private Journey recording version 1
Added a consent version for recording eligible contribution facts after Journey is enabled. Paused periods and earlier activity are not silently backfilled.
September 13, 2026
Original Web Beta agreement
Earlier beta registrations used a combined Terms-and-Privacy version with code web-beta-2026-09-13. New registrations no longer use it, but an immutable public snapshot of the historical text is not yet published.
What counts as a material change
Not every spelling correction needs a new consent screen. A change to a sensitive-data bargain does.
Usually material
- A new purpose for health, Journal, voice or safety information.
- A new audience, advertising use or external AI processor.
- Recording, transcription or a longer safety buffer in rooms.
- A meaningfully longer retention period or weaker member control.
- A new legal entity, launch region or cross-border transfer arrangement that changes rights.
Usually a clarification
- Correcting grammar or a broken link.
- Adding an example without changing a rule.
- Explaining an existing control more clearly.
- Naming a provider already performing the disclosed function, while still recording the transparency update.
- Strengthening privacy or shortening retention without removing a member right.
Substance wins over labels
How notice and choice should work
A policy banner alone is weak when the decision happens deep inside a health or voice feature.
- 1
Publish before use
Create the new document version and dated summary before the new processing starts, except for an urgent security measure that cannot safely wait.
- 2
Explain the member effect
Say what changed, why, what data or feature is affected and which control is available. Do not send members to compare two long pages unaided.
- 3
Place notice near the decision
Show recording changes before room entry, personalization changes at the recommendation control and draft-storage changes in the composer.
- 4
Request a fresh choice when required
Pause the affected optional processing until the member accepts the new version. Continued browsing is not a substitute for specific consent to expanded sensitive use.
- 5
Keep the outcome reviewable
Store the version and timestamp, let the member review active choices and preserve an immutable copy of the accepted text.
Policy-change delivery is a separate workflow
Consent receipts and active choices
A receipt should prove the choice without becoming another copy of sensitive member content.
- Record the consent type, exact policy version, account, acceptance time and revocation or replacement time where relevant.
- Do not place a Story, Journal entry, diagnosis narrative or voice content in the consent receipt.
- Keep optional health-personalization and Private Journey choices separate from the required account agreement.
- The current retention rule allows minimal consent and deletion proof for up to seven years when needed for legal accountability.
Archive status and questions
A version code is not a usable archive if nobody can retrieve the text it names.
Registration bundles registration-beta-1.1 and registration-beta-1.2 have stable read-only snapshots for every versioned component. Privacy 1.1 remains unchanged after its retirement, and Privacy 1.2 uses a new URL. The exact September 13 legacy text was not preserved, so it remains unavailable rather than being reconstructed and mislabeled as the original.
The archive rule is now in use