Contact
Four addresses, and a person at each one
There is no form on this page. A form would ask you to describe the problem twice and would give you nothing to keep; an email gives you a copy of what you sent and a thread to reply in.
- hello@pealboard.com
- General questions, anything about the product, and anything that does not fit below.
- support@pealboard.com
- Help with a workspace or a portal. Include the workspace name, the request number or issue number, and the request id from the error if there was one.
- security@pealboard.com
- Vulnerability reports. Describe what you found and how to reproduce it. Do not open a public GitHub issue.
- privacy@pealboard.com
- Data access, export and deletion requests, and questions about the data processing addendum.
Before you write
Most support questions are answered here
- Troubleshooting — sync delays, a repository that does not appear, a comment a customer cannot see, and what GitHub's refusals mean.
- Getting started — the five steps from an account to a first sync.
- Billing — what is counted, the trial, what a lapse does, and where the invoices are.
- Glossary — what each word means, and which words this product does not use.
What to include in a support message
- The workspace name.
- The request number (ACME-42) or the issue (acme/app#412).
- The request id from the error message, if there was an error.
- What you expected and what happened instead, in that order.
Mersoft Corporation
Pealboard is built and operated by Mersoft Corporation. Mersoft is the party you contract with and the entity named in the terms of service, the privacy policy and the data processing addendum.
The product itself is at app.pealboard.com, the API at api.pealboard.com, the MCP server at mcp.pealboard.com/mcp, and each portal at its own subdomain of pealboard.com.