Trust and safety

Protected speech needs real safety infrastructure.

PARA depends on a difficult balance: anonymity where thought needs protection, validation where civic participation needs legitimacy, and enough moderation and account control that public politics does not collapse into chaos.

This page sits outside the docs shell on purpose. Trust and safety is not just another subsection of reference material. It is a first-order product surface that shapes how identity, participation, and governance can work at all.

01

Identity

Profiles, political self-placement, and public-versus-private participation controls.

02

Moderation

Baseline rules, labelers, appeals, and proportional enforcement.

03

Verification

Identity proofs, geographic signals, and reputation without forced doxxing.

04

Privacy

Data handling, federation visibility, and user-facing controls.

Design principle

If the product does not make exit legible, the consent is not real.

Account deletion, data export, and appeals are not afterthoughts. They are part of the trust surface. Every feature we build is evaluated against whether a user can understand, control, and leave it.

01 / Identity

Who you are, who you appear to be, and who can tell the difference.

PARA is designed around personas and proof bundles, not a single public name. You can operate with different masks for different communities, and you can choose how much of your verification stack is visible in each context.

Pseudonymity and personas

View persona features
  • Multiple personas per account, switchable without logout.
  • Each persona can have its own display name, bio, and political placement.
  • Personas are not burner accounts; they are first-class identity surfaces.

Proof bundles

View verification layers
  • INE scan for Mexican voter verification.
  • Biometric gate and app-state auto-lock.
  • QR export to share verified bundles offline.
  • Custom surface builder to control what each context sees.
02 / Moderation

Rules, tools, and proportionality.

We enforce baseline rules through human review and automated signals. We also design for composable safety—labelers, user controls, and community-specific norms—so moderation is not a single gatekeeper.

Baseline

Community Guidelines

Safety first, respect others, be authentic, follow the rules. These four principles govern what we remove or limit on PARA services we operate.

Composable

Labelers and user controls

Where the protocol supports it, users can subscribe to additional labelers and adjust safety settings. Communities can add context on top of baseline rules.

Appeals. If we restrict or suspend your account, you may appeal within fourteen (14) days. Late or bare appeals may be declined. We retain discretion to make final calls.

03 / Verification

Trust without forced exposure.

Validation matters for civic participation, but not every user should have to expose their real name to participate. PARA holds both at once.

What verification enables

View benefits
  • Access to verified-only communities and representative channels.
  • Higher weight in certain aggregation or ranking surfaces.
  • Reputation that persists across personas where you choose to link it.

What anonymity protects

View protections
  • Freedom of thought for people in unsafe political environments.
  • Whistleblowing and dissent without personal exposure.
  • Exploration of political identity before committing to a public position.
04 / Privacy

Data visibility in a federated system.

PARA is built on open protocol infrastructure. That means public posts may be replicated by third-party services outside our direct control. We design the product to make visibility legible, not hidden.

Public by default

Posts, votes, and profile fields are public unless the product offers a restricted mode. Federation means copies may exist elsewhere.

Messages

Direct and group messaging uses end-to-end encryption where the protocol supports it. Metadata may still be visible to infrastructure operators.

Retention

We keep data as long as needed to operate the service and meet legal obligations. Deletion requests go to support and are handled when verifiable.

05 / Account control

You should be able to leave, export, or appeal.

Account deletion, data export, and appeals are not afterthoughts. They are part of the trust surface.

Deletion

You can delete your account where the product provides the feature. We remove content from services we control, subject to backups, legal holds, and safety needs.

Export

Repository exports are possible through protocol-native tools. Contact support if you need help locating the right export path.