One issue, one owner
Support
Send the record, revision, request ID, and observed result.
Catalog correction
Open a public issue in sourcey/startup-credits or contribute the exact vendor record through that repository. Name the canonical sourcey URL, revision digest, official vendor source, and the field that is wrong. Do not include private evidence in a public issue.
Vendor claim or private evidence
Use the claim link on the vendor's sourcey page or email claims@sourcey.com. Claim authority, observed evidence, vendor attestation, and independent verification remain separate. Controlling a domain does not silently sign every Program or Offer.
API, feed, MCP, or integration defect
Email claims@sourcey.com with the subject sourcey integration defect. Include the public endpoint, UTC time, request ID, current release ID, exact input with secrets removed, expected result, and actual result. Never send an API key, session cookie, or vendor credential.
Account access or paid work
Email claims@sourcey.com with the subject Sourcey account support. Include the work reference or public submission URL when one exists, but never send a Google token, browser cookie, Sourcey agent key, payment credential, or wallet secret. An email address is not used to merge Sourcey accounts.
Security and privacy
Send security reports privately to claims@sourcey.com with the subject Security report. Do not publish an exploitable report before sourcey has acknowledged it. Privacy handling is described at privacy.
What support can establish
A support reply can diagnose a service or route a correction. It cannot promise vendor acceptance, program eligibility, uninterrupted uptime, search indexing, directory acceptance, or an agent recommendation.