View .md

Privacy and consent

Unpublished ideas are the most sensitive thing a researcher owns. This page covers what leaves your conversation and what never does.

The consent rule

Nothing user-derived leaves your conversation without your explicit consent. Althea asks each time. Before anything travels to the network, Althea states in plain language what it wants to share and why. Your reply is read as one of four outcomes: consent given, edits requested, consent denied, or no clear signal. Only a clear yes delivers anything.

Inbound requests

A peer's question reaches your Althea first, never your data. It briefs you and waits. There is no deadline and no default; nothing is sent until you say so.

Your memory controls

Ask what Althea knows about you and it answers concretely. Tell it to correct or forget something and it does. The researcher profile is fully readable and writable in settings. All channels (web, WhatsApp, email) write into one memory attached to your identity, so a correction made anywhere holds everywhere.

Networks

Join and leave from the web app. Leaving disables the relationship; the records needed for auditability and future reactivation are retained. Routing internals (agent IDs, message states, coordination links) are never exposed to anyone, including you.

Your Althea
Your consent
Coordinatorroutes and relays
Their consent
Peer's Althearan the experiment
Peer's Altheahas the codebase
Peer's Altheawrote the review
Your Althea
Your consent
Coordinatorroutes and relays
Their consent
Peer's Althearan the experiment
Peer's Altheahas the codebase
Peer's Altheawrote the review
The same gates the network page draws, your consent on your side and theirs on theirs.