Privacy policy.

Information you provide

When you submit a product, contact SkillChirp, configure a Chirp profile, use Career features, or use another account-enabled feature, we may receive information you intentionally provide such as a name, email address, product URL, description, social profile, startup information, target audience, topics, growth goals, job descriptions, project progress, and content you ask SkillChirp to draft or schedule.

Threads connection and Chirp data

If you connect Threads through Meta OAuth, SkillChirp may receive and store the Threads account identifier, profile information made available through the authorized API, granted permissions, token-expiration information, and a server-side access token. Chirp may import or sync your Threads posts, post metrics, account insights, replies and related performance snapshots when the permissions you grant allow it.

Chirp may also derive account-specific research fields from this stored data, such as posting frequency, whether a post contains a question or link, a rules-based content category, promotional-content indicators, creator-reply counts, engagement rates, and private content-mix summaries. These labels are product analytics derived from your synced account history; they are not Meta algorithm labels and do not establish that one behavior caused a performance result.

Threads access tokens are server-side credentials. SkillChirp does not include them in Chirp's external-agent API responses.

Chirp external API and agent access

Chirp lets a connected user create scoped API keys for an external agent or server-to-server client. A key is bound to one Chirp profile and can be limited to specific capabilities such as analytics, Scout, recommendations or scheduling. The full raw key is shown when it is created; SkillChirp stores a one-way digest rather than the raw key.

External API activity may create audit records containing the connected Chirp profile, API-key record, client/source label, requested action, required scope, success or failure, response status and timestamp. These audit records are designed not to store raw API keys or Threads access tokens. Scheduling through the external API uses a separate opt-in write scope and a short-lived, single-use confirmation step.

An external agent or client may separately process the information you send to it under that provider's own terms and privacy practices. Only connect Chirp to clients you trust. You can revoke a Chirp API key from Chirp Settings.

Disconnecting and deleting Chirp data

Disconnecting Threads removes the saved Threads access token from the connected Chirp profile and prevents its external Chirp API keys from being usable while the profile is disconnected. Previously imported analytics or other Chirp records may remain so the product can preserve history unless they are deleted through an applicable product control or privacy request.

Payments

If you purchase a paid SkillChirp plan, payment and subscription processing may be handled by a payment provider such as Stripe. SkillChirp may store provider identifiers and subscription status needed to recognize your plan, while payment-card details are handled by the payment provider rather than the Chirp external-agent API.

Usage and analytics data

SkillChirp may use analytics, first-party product events and server logs to understand page visits, referring pages, device/browser information, funnel steps, feature usage and aggregate product engagement. Battles may use privacy-preserving visitor identifiers to reduce duplicate votes, refresh inflation and obvious automated traffic.

One-time publishing credentials

If you explicitly use a Distribution Hub integration that asks for a Bluesky app password or DEV API key, SkillChirp uses that credential to perform the publishing action you request. The V1 integration does not intentionally persist those credentials in the SkillChirp database, and the interface asks for them again for a later publish.

How information is used

• Operate, secure and troubleshoot SkillChirp.
• Provide Chirp analytics, Scout, recommendations, scheduling, replies and account-sync features.
• Authorize scoped external-agent access requested by a Chirp user.
• Measure aggregate usage and improve product experiences.
• Process plan status and purchases when paid features are enabled.
• Detect abuse and suspicious engagement.
• Respond to support, privacy, security and legal requests.

Third-party services

SkillChirp relies on third-party services to provide parts of the product, including Meta/Threads for authorized Threads functionality and payment providers for billing when applicable. Availability and data handling by those services are also subject to their own terms and policies.

Requests

For access, correction or deletion questions, contact [email protected]. For security reports, contact [email protected].