Acceptable use
Firm responsible-use boundaries for every UmmahSignal workspace and developer client.
No sensitive profiling
Do not use UmmahSignal, custom categories, exports, API access or connected tools to infer, label, score or profile an individual’s religion, ethnicity, health, politics, sexuality or another sensitive trait.
Brands, creators and organisations of every background can use the product. Public discussion of an organisation, topic or service is not evidence of an author’s faith or identity.
Official public sources only
Do not attempt to access private messages, protected content, private groups, deleted material or data obtained without appropriate authority. Do not scrape, evade provider controls, circumvent quotas or reconnect Reddit or LinkedIn through hidden or unofficial paths.
No harassment or person-level surveillance
Do not target individuals for harassment, intimidation, discriminatory treatment, eligibility decisions or disproportionate surveillance. Do not join authors across platforms or build shadow profiles from public-source records.
Human review required
Do not treat automated classifications, summaries, sentiment, priority, moderation flags or recommendations as fact. Review the canonical public source, surrounding context and confidence before acting.
Low-confidence, policy-restricted, conflicting or unprocessed records must remain visibly Unclassified or Needs review rather than being assigned an invented result.
No autonomous engagement
Do not use UmmahSignal, its REST API, MCP tools or webhooks to post autonomous replies, send private messages, impersonate people or issue religious, legal, medical or safeguarding rulings.
Security and integrations
Protect invitation links, API keys, OAuth grants and webhook secrets. Use the minimum scopes required, verify signed webhook timestamps and revoke credentials that may be exposed.
Removal, correction and accountability
Respect public-content removal, provider compliance and workspace deletion requests. Preserve the internal history of classification corrections and workflow changes, without retaining raw public content beyond the approved lifecycle.
Enforcement and legal review
We may pause monitors, revoke developer access or suspend a workspace while investigating suspected abuse. This policy requires qualified legal and provider-policy review before paid production launch.