- How-to and design questions: use the central PipSync Discussions.
- Reproducible project bugs: open a bug report in the affected repository.
- Product or account support: use pipsync.io/support.
- Security vulnerabilities: follow
SECURITY.md; never disclose them publicly.
Community support is best effort. Public repository maintainers cannot access or troubleshoot private accounts, billing, broker connections, or production execution from a GitHub issue.
Please check the README, current release notes, existing issues, and the public API contract. Reduce the problem to a mock or synthetic example and include exact version information.
Sanitize all diagnostics. Never post API keys, authorization headers, webhook signatures, broker credentials, customer payloads, account identifiers, session cookies, or unredacted logs. Do not ask maintainers to place, modify, or close a live trade.
Open-source PipSync projects are developer tooling. They do not provide financial advice, guarantee compatibility with every broker, guarantee execution, or promise returns. Validate integrations in a controlled mock or paper environment before considering any production use.