One issue, one owner
Support
Send the record, revision, request ID, and observed result.
Catalog correction
Open a public issue insourcey/startup-creditsor 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 emailclaims@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 subjectSourcey 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.
Security and privacy
Send security reports privately to claims@sourcey.comwith the subject Security report. Do not publish an exploitable report before Sourcey has acknowledged it. Privacy handling is described atprivacy.
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.