Acceptable use
Keep RequestBeacon out of sensitive and harmful workflows.
The founding product is for ordinary service-business inquiry notifications, not regulated intake, emergency response, or customer-facing automation.
Prohibited sensitive workflows
Do not use RequestBeacon for medical or health intake; legal intake; financial services; detailed insurance claims; identity verification; children’s data; payment-card data; government IDs; emergency response; dispatch; or any workflow in which sensitive data is central.
Prohibited acquisition
Do not submit purchased, scraped, stolen, or unlawfully obtained leads. RequestBeacon is not for cold outreach, old-lead reactivation, advertising, political campaigning, marketplace prospecting, or list enrichment.
Prohibited customer automation
RequestBeacon must not be used to send customer-facing email, text, voice, or social responses; qualify customers; book appointments; answer, record, forward, or transcribe calls; or impersonate a person.
Prohibited technical behavior
Do not attempt unauthorized access, tenant mixing, secret disclosure, malicious payloads, forwarding loops, source spoofing, denial of service, evasion of limits, or use of an unapproved source route.
Response to prohibited data
A live service must stop, quarantine, restrict, or delete prohibited data according to approved incident and legal procedures. This public preview does not accept source connections or customer records.