Sign In Start Free
Contact

How to reach LinkSilo, by category.

LinkSilo separates contact channels by purpose: a general-purpose email and an OpenPGP-encrypted equivalent on this page; a dedicated security-disclosure address on the security page; a dedicated legal-process address on the transparency page. Pre-launch, the general channel below is the placeholder shape it will hold when public traffic begins.

Last reviewed 2026-05-17

General contact

Email contact, pending launch-prep publish.

The general-purpose contact address publishes on the linksilo.io domain, matching the same domain the product's transactional mail sends from. We deliberately leave the local-part visibly blank until launch-prep rather than burning a placeholder address into the pre-launch marketing surface; the address that lands here at launch is the address it will keep, monitored by the team rather than auto-forwarded to a personal inbox.

Use this channel for general questions, product feedback, press, and partnerships. The two dedicated channels — security disclosure and legal process — are routed differently and have their own published intake addresses on the pages linked from Section 4 below.

General
__________linksilo.io
Local-part publishes at launch-prep. Domain matches the noreply@linksilo.io transactional canon.
GPG-encrypted contact

OpenPGP, for privacy-sensitive messages.

Some categories of correspondence warrant end-to-end encryption between the sender and the receiver: whistleblower-adjacent reports about the platform, sensitive press inquiries, journalist correspondence about a story in progress, or simply a personal preference for encrypted email. The OpenPGP key below is the receive-side key for that traffic. The fingerprint and the armored public-key block both publish at launch-prep; the placeholder shape below is what the channel looks like in the meantime.

Fingerprint
____ ____ ____ ____ ____ ____ ____ ____ ____ ____
Public key (armored)
-----BEGIN PGP PUBLIC KEY BLOCK-----

[Public key block pending launch-prep]

-----END PGP PUBLIC KEY BLOCK-----
New to GPG? It is a long-standing end-to-end encryption tool for email: you encrypt to the receiver's public key in your client; only the holder of the matching private key can decrypt. Email Self-Defense from the Free Software Foundation is a clear walkthrough. If GPG is more friction than the message warrants, the unencrypted address in Section 2 is the right channel.
Other paths

Pointers, by category.

Security disclosure
Vulnerabilities, privacy-relevant findings, or anything that belongs under coordinated disclosure: the security page publishes the dedicated intake address, the PGP key for that address, the bounty schedule, and the response timeline. Use that channel rather than the general address above.
Legal process
Lawful requests for user data, subpoenas, court orders, and other formal legal correspondence: the transparency page publishes the receiving channel, the verification expectations, and the postal address. The general address above is not the right intake for legal process.
Architectural posture
Questions about what LinkSilo is, why we built it, who builds it, and what state it is in: the about page covers the structural framing. The transparency page covers the operational posture in more detail. Read both before sending a question that those pages already answer.
Codebase
Our open-source monorepo on GitHub. Issues and pull requests are received through the standard GitHub flow; security-sensitive findings should follow the security-disclosure path above rather than the public issue tracker.