Privacy
Moral Trade separates public account information, broad matching previews, exact wishes, sensitive evidence, and contact details. Moving information between those layers requires an explicit purpose and permission.
Principles
Data summary
Purpose: Authenticate users, maintain accounts, and display only profile fields chosen for publication.
Processors: Supabase supports authentication and database storage.
Retention: Kept while the account or a required review record remains active, subject to export, correction, deletion, and restriction rights.
Purpose: Create broad previews, run controlled compatibility checks, support reviewed searches, and manage consented introductions.
Processors: Stored in Moral Trade records backed by Supabase; sensitive text may be encrypted before storage.
Retention: Limited by the relevant consent, expiry, review, safety, or deletion state. Exact wishes and source notes do not appear on public cards.
Purpose: Reconcile external payments, contribution evidence, agreement payment state, refunds, disputes, and provider events.
Processors: Stripe handles supported payment objects; Every.org handles off-site donation routes.
Retention: Identifiers, amounts, status, cadence, and evidence references may be retained for reconciliation, disputes, audit integrity, and compliance.
Purpose: Measure whether people understand the service, complete onboarding, perform a concrete first action, and encounter errors or safety blockers.
Processors: Privacy-safe internal funnel records and route-level service telemetry.
Retention: Uses paths, event types, coarse labels, counts, buckets, referral codes, and campaign attribution. Raw private content is excluded.
Purpose: Deliver account, evidence, review, matching, security, and service communications.
Processors: An external email provider may deliver queued notifications.
Retention: Preference, delivery, failure, opt-out, and support records are retained as needed to honor choices and diagnose delivery.
Consent-gated disclosure
registry, consent, introduced.
hidden, broad, specific, contact.
exact private wishes before consent, exact asks before consent, contact details before introduction, raw source notes, sensitive constraints in public preview, private feed payloads.
Optional analytics
Optional events use route paths, bounded event types, counts, buckets, and campaign attribution. They exclude exact wishes, private messages, evidence bodies, source notes, and contact details.
Your controls
Use the member workspace to export profile data and begin correction, deletion, or restriction requests.
Open data controlsEnter DELETE BACKGROUND NETWORKING in the workspace to remove the participant-facing private matching layer.
External services
Supabase supports authentication and database storage. Stripe handles supported card, payment, and payout objects. Every.org handles direct donation routes. An external email provider may deliver queued notifications. Those providers operate under their own security and privacy obligations in addition to Moral Trade's controls.