TRUST CENTER

Trust should be visible, not implied.

This page distinguishes controls already reflected in the public experience from policies and operating procedures that still require owner or qualified review.

READINESS AT A GLANCE

Clear status before claims.

PharmaARMs will not present unfinished policies as approved or describe future controls as operational. Each area below shows its current development status.

Public summary available

Educational boundaries

Clear prohibitions on PHI, employer and affiliated-company information, drug or product brand names, confidential information, urgent matters, and reliance on PharmaARMs as professional advice.

Read the public summary →
Active and regression-checked locally

Current public data boundary

Free membership enrollment and secure email sign-in are active. Enrollment collects only an email address and Terms acceptance. No public file uploads, saved ARIA messages, analytics SDKs, member document access, or Case Desk submission occurs without the applicable protected membership flow.

Active in this local preview

Search-engine release gate

Preview builds tell search engines not to index or follow the site and publish no sitemap entries. Indexing remains fail-closed until a future approved cutover explicitly enables it.

Operating design in progress

Source and editorial governance

Substantive content requires provenance, dates, named ownership, qualified review, version history, and withdrawal controls.

Qualified review required

Privacy notice

A final notice must reflect actual collection, purpose, retention, deletion, sharing, security, and contact practices before launch.

Qualified review required

Terms of use

Current user obligations prohibit PHI, employer or affiliated-company information, and drug or product brand names. Complete permitted-use, relationship, limitation, and dispute provisions still require counsel-approved language.

Required before member community

Community guidelines

Conduct, moderation, reporting, enforcement, appeals, incident response, and staffing must be approved before community launch.

Owner approval required

ARIA assistant governance

The assistant remains unimplemented until users, sources, prohibited inputs, escalation, citations, retention, editorial workflow, and testing are approved.

Do not submit sensitive or identifying information

Do not send PHI, patient identifiers, claim or authorization numbers, employer or affiliated-company information, drug or product brand names, credentials, private case documents, screenshots, or other confidential organizational information. Use only fictional, non-brand scenarios.