Security & support
How to get beta help, report a vulnerability, or respond to a suspected account or payment incident.
Get help
Email support@omnious.xyz with the release version, network, request or receipt identifier, approximate time, and a description. Never send a private key, seed phrase, raw payment signature, OAuth token, or full sensitive prompt.
Report a vulnerability
Email security@omnious.xyz with reproducible steps and impact. Give us a reasonable opportunity to investigate before public disclosure. Do not access other users’ data, move funds, degrade service, use social engineering, or test production destructively. We will acknowledge beta reports as capacity allows; no bounty is promised unless agreed in writing beforehand.
If you suspect compromise
- Stop paid requests and disconnect affected integrations in Settings.
- Revoke provider grants at GitHub, Google, Slack, Microsoft, Notion, Linear, Dropbox, or Figma as applicable.
- Move remaining assets to a fresh wallet if wallet material may be exposed; do not reuse the suspected key.
- Preserve receipt/request identifiers and contact support from a safe device.
Current controls
Omnious uses bounded inputs, signed and replay-protected payment/action messages, encrypted connector tokens, separate OAuth storage, least-duration sessions, SSRF controls, rate limits, reconciliation, restore drills, and protected release gates. No control makes beta software risk-free.