Service-provider register
Provider register 1.0Who helps PosMeet run—and exactly where.
A provider name without context is not transparency. This register explains the feature that calls each service, the information it receives and the boundary PosMeet is responsible for enforcing.
AWS for media
S3 stores uploaded media; CloudFront delivers standard Community and profile images.
Agora for live audio
Agora receives a short-lived room token and carries audio only while a member is connected.
Resend for transactional email
Resend delivers one-time codes and enabled neutral account updates.
No ad network
The current beta has no behavioral-advertising or cross-site tracking provider in its application code.
A live register, with one release gap
How this register works
PosMeet uses each provider for a named technical job and does not intentionally send health stories for ad targeting. Final production agreements must preserve that boundary.
- A provider should receive only the data needed for the feature it runs.
- PosMeet remains responsible for choosing the provider, configuring access and responding to member rights and incidents.
- Some technical request data—such as IP address, device details and timestamps—is visible whenever a browser connects to an external service.
- Clicking an external resource, such as WHO or Find A Helpline, takes you outside PosMeet. That site’s notice applies after you choose to open it.
Amazon Web Services and CloudFront
AWS provides object storage and media delivery; it is not the audience selector for a post.
Provider role
Media storage and delivery
- Data received
- Uploaded profile, Story and feedback images; Journal voice notes; object identifiers; upload and delivery request metadata.
- When it is called
- When you upload media, play a private voice note through an authorized link, or load a standard image delivered through CloudFront.
- Important boundary
- Standard media is delivered through the CDN and its exact URL can be shared or cached. Private media stays in the private path and uses short-lived authorized access.
- Retention note
- The PosMeet record and purpose-specific schedule control deletion requests. CDN caches or backups can take additional limited time to expire.
Current technical configuration
us-east-1. The deployed production region and any backup region must be confirmed here before public launch rather than assumed from source-code defaults.Agora
Agora is the audio transport for a room, while PosMeet remains the control plane for room access, roles and moderation.
Provider role
Real-time voice rooms
- Data received
- A pseudonymous room/channel identifier, participant identifier, audience or speaker role, a short-lived RTC token, technical connection data and live audio while connected.
- When it is called
- Only after an active room participant requests audio access and the Agora provider is configured. A token normally lasts no more than one hour and never beyond the remaining room time; the server caps configuration at two hours.
- Important boundary
- The browser receives an app identifier and short-lived token, never the Agora application certificate. Only rooms labelled Not recorded can receive an RTC token in the current Web Beta.
- Retention note
- PosMeet retains room attendance, role and moderation events under its own schedules. Agora’s operational diagnostics and network records are governed by the provider arrangement that still needs launch-region review.
No recording promise has a product dependency
Resend
Resend is a transactional delivery service for passwordless sign-in and configured neutral account updates, not a health-content newsletter.
Provider role
Authentication and neutral transactional email
- Data received
- The destination email address, sender identity, transactional message content—including a one-time code or a generic PosMeet update—and ordinary delivery status or diagnostic data.
- When it is called
- When a member requests a Join or Sign in code, or when an enabled notification category has an eligible update. Local development can use a console-only authentication path.
- Important boundary
- Authentication codes expire quickly and work once. Notification subjects and previews do not include an STI, diagnosis, Support Need, Journal entry, Circle or Room topic; the member signs in to view the update.
- Retention note
- Expired PosMeet authentication challenges and delivery-attempt records follow bounded operational schedules. Provider-side delivery retention requires confirmation in the final production agreement.
Protect the mailbox, too
What is not installed in the current beta
Absence is worth recording for a sensitive-health product, because a future SDK can materially change the data flow.
No behavioral ad network
The current product does not intentionally send STI status, Journal activity or room participation to any provider for targeted advertising.
No third-party web analytics tag
The current application code does not install Google Analytics, Meta Pixel, PostHog or a comparable member-surface analytics tag.
No social sign-in provider
The beta uses one-time email codes rather than passing account access through Google, Apple or Facebook sign-in.
No external AI content processor
The current Community, Journal and moderation paths do not send member text to a named generative-AI service.
This is a statement about the current code, not permission to add a tool silently. A new provider must be assessed, added to the data map and disclosed before it receives live member information.
Processing regions and international transfers
A global service can process technical or member information outside the country where a person lives.
AWS, Agora and Resend operate international infrastructure. A member’s information may therefore be processed outside their home country when the relevant feature is used. PosMeet has not yet published the final launch-country transfer mechanism, regional representative or complete production subprocessor locations.
Public-launch requirement
Provider changes and questions
A provider register is useful only if members can tell when it changed.
PosMeet should publish a dated entry before a new provider receives live member data. A material change involving health information, advertising, AI training, recording or a new processing purpose may also require an in-product notice and a fresh choice.