SIPHR
/
sign increate key
↳ /support · get a human

Get help.
Bring the contextwe can't see.

Because your repos are end-to-end encrypted, we genuinely can't open them and look. That's a feature. The cost: when something breaks, the most useful person in the room is you. Fill this out and it'll open your mail client with a draft to support@siphr.dev. Nothing is sent through a Siphr inbox.

1

What's wrong

· picks the routing tag on the subject line
2

What you'd tell a friend

· more useful than a stack trace
Subject
Describe it
↳ markdown ok · please don't paste private keys or passphrases · we'll ask you to rotate if you do
3

Context to share

· opt-in · stays in plaintext in the email body
Your public-key fingerprint
lets us cross-reference rate-limit / auth logs · still ciphertext from our side
sign in to attach
Browser & client version· always included
auto-detected from this session
(detecting)
4

Preview

· exactly what will be drafted in your mail client
MAIL → support@siphr.dev
tosupport@siphr.dev
from(your default mail account)
subject[repo] (no subject)
routedirect · no siphr.dev relay · no server inbox
bodyWhat I tried:
diagfp ✗ · ua ✓
repo body(not attached · still ciphertext on the server)
↳ opens your default mail client with this draft addressed to support@siphr.dev
↳ typical first reply · <1 business day · faster for billing & abuse