Contact
Get in touch
By Paperclip Team · Published · UpdatedThe fastest way to reach the team is email. Pick the address that fits the question, and anything that needs a paper trail or a signed contract has one by default.
Channels
Pick the channel that fits the question. Bug reports and feature requests go to GitHub. Anything that touches your data, your bill, or your contract goes to email so we have a written record.
- hello@paperclip.inc
- GitHub
- github.com/paperclipinc
- Security
- security@paperclip.inc
Support and response times
Community support runs by email, with the team responding during European working hours. Most questions get an answer within a few hours during the week. Open-source bug reports filed on GitHub are triaged within two business days.
Paid plans get email support with a one-business-day response target. Enterprise plans get a private Slack channel, named on-call contacts, and a contractual response SLA.
Enterprise and self-hosting
Self-hosting on your own Kubernetes cluster, single sign-on, audit-log export, and a dedicated success engineer are part of the enterprise tier. Email enterprise@paperclip.inc for a conversation. Include rough headcount, the kind of work you want agents to do, and any compliance constraints you have.
Security disclosures
Report vulnerabilities to security@paperclip.inc. We acknowledge within one business day and triage promptly. We do not yet run a paid bug bounty, but we credit reporters on the public security page once a fix ships.
Mailing address
The postal address is available on request to keep the inbox clean. Email hello@paperclip.inc and we will send it back the same day. Most of the team works remotely across European timezones, so a registered office is not where decisions get made anyway.
Press and analysts
Coverage requests and analyst briefings go to press@paperclip.inc. We typically respond within two business days with a short note and offer a call if the topic warrants one.
How to get a fast answer
If the question is concrete (a config option, an error message, a sample request), include the smallest version that reproduces what you saw. A short trace, a screenshot, or the exact command you ran almost always shortens the round trip to one reply. Vague questions are still welcome and will get an answer; concrete ones get faster ones because the team can act on them without a back-and-forth.
For anything that involves billing, account access, or data export, send the request from the email address tied to the account. We will not move billing-sensitive operations through chat because the audit trail is too easy to lose, and we do not want to ask for verification each time when an email thread already proves it.