Support

Email support@devilabs.dev. Check the status page first: if something is broken for everyone, it is posted there, and you do not need to write.

The documentation covers setup, self-custody, and the API.

The more of this you send, the faster it is solved. Never send a private key, a seed phrase, a password, or an API key. We will never ask for one.

• What you expected, and what happened instead.
• The time it happened, with your timezone.
• The x-request-id header from the failing API response, if you have it.
• Any transaction hash and the network (Arc mainnet or Arc Testnet).
• The organization name, but not any secret.

If a payment looks wrong, or you think a key has been exposed, say so in the subject line. You can also act yourself right away: revoke the API key in the console, and use your guardian wallet to pause the vault. Both work without waiting for us. Refunds are never blocked.

Send security reports to support@devilabs.dev. Please give us a reasonable chance to fix a problem before you publish it, and do not access data that is not yours or move funds that are not yours to prove a point. Good-faith research that follows these rules is welcome. See Security for the model and what is in scope.

No bug-bounty programme is advertised on this page. If one is offered, its terms are published here.

When something affects other people, we post it on the status page as it happens and keep it updated until it is resolved. Serious incidents get a written summary afterwards.