Support is not only for runtime failures. Use this page for operational problems, data-handling questions, privacy requests, and practical checks against the current product posture.
Confirm the app server is up, the workflow runtime is reachable, the request payload includes a topic, and the account is authenticated for private /api/briefs usage.
Beacon relies on durable workflow sleep and resume. Locally, keep `npx workflow dev` running. In deployment, confirm workflow endpoints and runtime hooks are healthy.
Checks:
1. use the exact same topic string
2. open /memory and confirm the topic exists
3. verify UPSTASH_REDIS_REST_URL
4. verify UPSTASH_REDIS_REST_TOKEN
5. rerun after memory is presentUse Settings to clear stored API keys, use Memory Bank controls to remove stored topic memory, and use your authenticated account context to review the briefs and logs that Beacon currently exposes back to you.
If you need a broader privacy review, export, correction, or deletion request across account data, memory, briefs, and logs, route it to the service operator through the project's support or repository issue channel and include the account identifier and affected run or topic where possible.
Escalate immediately if you believe Beacon stored sensitive personal data by mistake, exposed another user's data, retained data after a deletion request, or processed content through the wrong integration channel.
Beacon can currently surface account-scoped briefs, memory, log history, and stored-key status inside the product, which makes basic user review possible.
Beacon does not yet expose a full in-product privacy request workflow, enterprise retention controls, or formal regulator-facing response procedures. Those remain operator-governed processes rather than finished product features.
Use docs for setup, API, MCP, auth, rate limits, architecture, and security guidance.
Review current data categories, retention, vendor processing, and user-rights posture.
Inspect the durable state Beacon has stored for your account topics.
Review stored provider-key status and clear configured keys from your account.