Privacy and reporting
plyk records aggregate download activity on this website. Reporting from an installed skill is optional and off by default.
Website download metrics
A download click records an event ID, event time, selected coding tool, package version, and package type. The website sends this event to its own analytics endpoint. It does not add an analytics identifier to your browser storage.
A ZIP request records a request for a package. Requests can repeat, include automated traffic, or end before the transfer completes. They do not establish unique people, successful installations, or active teams. A click and a ZIP request are separate events and their totals can differ.
Counts start at the stated tracking date. Earlier activity is not backfilled. Aggregate counters may take up to two minutes to refresh.
Optional skill reporting
Installation and team reporting require an explicit opt-in. When enabled, reports use a pseudonymous installation ID to associate events with the same installation. That ID identifies a reporting installation, not a person.
An installation report records a completed installation. A team report records creation of a team configuration. Creating a configuration does not establish that visible chats were created, agents started, or work finished.
Reported installations and team configurations cover only installations that opted in and successfully sent reports. Active installations counts consenting project installation IDs that created a team during the last 7 UTC calendar days. It does not count every invocation or unique people.
What event payloads exclude
The analytics API accepts a limited set of event fields. It does not collect prompts, source code, project names, project paths, credentials, account identifiers, or provider allowance and usage balances in event payloads.
Optional reports describe the event and its time, package version, coding tool, pseudonymous installation ID, and role count when applicable. The installer and team setup instructions explain how to enable or disable reporting.
Hosting logs and dashboard access
The hosting provider may separately process request logs, including IP addresses, user agents, and request times. Those operational logs are separate from the analytics event payloads described here. This page does not set the provider's log retention policy.
The public counter displays aggregate ZIP requests. Detailed metrics and CSV exports require signing into the analytics dashboard. Dashboard sign-in uses a server-managed session cookie. Passwords and setup tokens are not stored in browser local storage.
Your project content
The website's team builder keeps your input in the current page. Download metrics do not include that input. Your chosen coding tool may have its own data and logging policies.