No manufactured threats
A proposal must not reward newly escalated harm, coercive leverage, extortion, harassment, or a worse baseline created to extract concessions.
Core rules
What every workflow must preserve
No surprise disclosure
Exact wishes, identities, sensitive constraints, evidence bodies, and contact details remain private until the relevant person approves a scoped disclosure.
No autonomous outreach
Private matching does not scrape private feeds, mass-message candidates, or contact a possible counterparty without an accountable human request and review.
Third-party harms count
A deal can be mutually preferred by its direct parties and still require externality review, affected-party standing, correction, or rejection.
Evidence stays scoped
A receipt or log may show that an action occurred. It does not automatically prove the no-trade baseline, causation, impact, or absence of externalities.
Recourse remains available
Participants and affected parties can challenge evidence, request correction, appeal decisions, report incidents, revoke grants, or freeze private matching state.
Blocked or escalated
Proposal classes outside the service boundary
- Violence, threats, extortion, coercion, harassment, doxxing, or stalking.
- Fraud, impersonation, illegal acts, deceptive evidence, or attempts to evade provider rules.
- Pressure on vulnerable people or demands that create unsafe personal, medical, legal, or financial exposure.
- Political campaign contribution offsets or other regulated activity outside the service boundary.
- Proposals that require unrestricted private-data access or unconsented contact disclosure.
Public contracts
Inspect the controls behind the claims
Machine-readable endpoints expose security, operations, disclosure, appeal, incident, and externality rules. Public copy should remain tied to those checks.
Security health
Open the current public contract and validator result.
Open JSONOperations health
Open the current public contract and validator result.
Open JSONDisclosure contract
Open the current public contract and validator result.
Open JSONChallenge and appeal
Open the current public contract and validator result.
Open JSONIncident response
Open the current public contract and validator result.
Open JSONExternality review
Open the current public contract and validator result.
Open JSONScale gates
Sensitive capabilities do not expand without named controls
Sensitive admin scale
blockedDo not expand sensitive admin access until MFA, device/session review, key rotation, and incident-response evidence are ready.
Requires two factor admin gate, device session review gate, key rotation gate, incident response reporting.
Paid-action volume scale
blockedDo not expand paid-action volume until provider/security boundaries, key rotation, incident response, and abuse throttles are documented.
Requires platform abuse throttling, provider encryption at rest, server only secret management, key rotation gate, incident response reporting.
Trust badge scale
passDo not expand public trust badges unless private cache, authenticated session, abuse throttling, and incident reporting remain verifiable.
Requires private no store cache, supabase auth cookies, contact disclosure mfa step up, platform abuse throttling, incident response reporting.
Non-claims
What the service does not promise
- Moral Trade does not claim custom field-level encryption for every private Moral Trade table; background-networking sensitive text has a separate versioned keyring control.
- Moral Trade does not claim the app-level MFA/2FA admin gate replaces provider-console MFA, device inventory, session revocation, or key-rotation evidence.
- Moral Trade does not claim a completed key-rotation program until provider rotation records are published.
- Moral Trade does not claim 24/7 staffed security operations or zero incidents; incident summaries stay aggregate and privacy-redacted.
- Moral Trade does not claim zero security risk; public health endpoints expose blockers instead.