TipCLI counts sponsor delivery, not developer behavior.
TipCLI exists to help maintainers fund open-source tools without turning developer workflows into surveillance surfaces. Sponsor cards can be measured for impressions and clicks, but the SDK does not read the work happening inside the terminal or project.
We do not collect source code.
We do not collect terminal logs.
We do not inspect environment variables.
We do not fingerprint developers.
We do not use cookies or tracking pixels for SDK delivery.
We only count sponsor impressions and clicks.
What a sponsor request needs
publisherKey
Identifies the reviewed project surface.
surface
Names the maintainer-approved placement.
category
Keeps matching inside allowed sponsor topics.
sdkVersion
Helps TipCLI debug SDK compatibility and launch behavior.
sessionId
Anonymous SDK session value used for delivery integrity, not developer identity.
ci / sdkDisabled / deliveryMode
Marks CI, disabled, fixture, internal, or test traffic as non-payable.
impressionToken
Records an impression or click for a reviewed card without cookies.
The sponsor request contains publisherKey, surface, category, sdkVersion, an anonymous sessionId, and non-payable delivery flags when they apply. Impression and click records use the issuedimpressionToken; they do not include project files, command output, user accounts, cookies, or device fingerprints.
TipCLI does not use privacy claims as a growth hack: no borrowed logos, no hidden retargeting, and no projected sponsor value presented as payable earnings.
Privacy, security, or data handling requests
Send the affected page, project, campaign, or request context through Contact TipCLI. Support handles privacy questions alongside campaign review, payout, and billing context so the answer can stay specific.