Help with FYInbox
Support
Best-effort support for the notification system for people and agents: account access, central project notifications, MCP connections, export, deletion and suspected credential exposure.
Last updated:
Contact and service level
Support is best-effort. There is no SLA, guaranteed response or resolution time, published support schedule or on-call coverage. Send a concise description to the verified support contact below.
What support covers
Support covers account access, authenticated notification ingestion, the central inbox for people and agents, MCP authorization and revocation, optional Web Push, export and deletion controls, and suspected exposure of a source credential.
Support does not provide custom integration consulting, monitoring of third-party projects, legal advice, emergency response or guarantees for external tools and browser push infrastructure.
What to include
Share only the minimum information needed to reproduce the issue. Redact notification content and personal data before sending it.
- An approximate timestamp and time zone.
- The action or endpoint and HTTP status, without authorization headers.
- A non-secret project or source identifier and only the non-secret API-key prefix.
- Browser and version, device type, and short reproduction steps.
Never send secrets or sensitive content
Do not email passwords, session tokens, API keys, cookies, authorization headers, root keys, payment data, backups, private notification payloads or special-category data. If a source API key was exposed, revoke it in FYInbox and create a replacement before contacting support.
Privacy and service rules
The privacy notice explains how a support request and account data are handled. The terms describe permitted use, security responsibilities, availability and account termination.