Contact
One form, four addresses. Pick whichever gets your question in front of the right person fastest.
Every message reaches a person, not a queue that forwards to nobody. If your question is about a specific delivery, include the endpoint id and an event id. If it is about a finding, include the finding id and the domain or repo, never the key itself. Either way, the first reply will have an answer in it rather than a request for details.
Support
support@shellorbit.com
Leak Alarm findings, delivery failures, endpoint configuration, replay questions. Include the finding or event id, never the key itself.
Security
security@shellorbit.com
Vulnerability reports and suspected compromise. Read the disclosure conditions in section 10 of the terms first.
Privacy
privacy@shellorbit.com
Data access, deletion, and portability requests, and questions about the data processing addendum.
Message received
It reached our inbox and was logged against your email address. A reply goes to the address you gave, usually within one business day.
- What happens next
- A person reads it, not an autoresponder. Support questions are answered with the findings and delivery records in front of us.
- If it is urgent
- Security reports go straight to security@shellorbit.com and are read the same day.
- While you wait
- The documentation covers retries, replay, and signature verification, including what each failure means and which side it came from.