Privacy policy

Public Bluesky data

Bluesky posts and public account information are public data, available to anyone through the AT Protocol, not just people logged into Bluesky. This project processes that public data; it does not access private messages or other non-public account information.

The monitor reads public AT Protocol data through Jetstream archive and live streams. For matching replies, it stores post identifiers, posting times, author DIDs (stable account identifiers), and parent-post and parent-author identifiers. It also caches public handles and, when a handle cannot be resolved, account status reported by a relay.

This data is used to calculate reply counts, author rankings, and monthly statistics. Author identifiers, available handles, and account status labels appear in public reports. The statistics database stores identifiers and metadata, not the full text of matching replies.

No AI is used to process this data. Matching replies and calculating statistics use ordinary code and database queries, not AI models. This project does not send Bluesky data to AI services or use it to train AI models.

Historical records currently have no automatic expiry. Deleting a post or closing an account on Bluesky does not automatically remove its previously recorded contribution from these statistics. Handles and account statuses are refreshed periodically, but may be out of date.

Visiting this website

You do not need an account or a Bluesky login to use this site. The application does not set analytics or advertising cookies, use browser local storage for tracking, or include third-party analytics. Search text in the author list is processed in your browser.

Like other websites, requests expose information such as your IP address, browser information, requested URL, and request time to the server and any hosting infrastructure. Operational logs and telemetry may record request details and errors for reliability and diagnosis; this policy does not promise that hosting logs are absent or have a particular retention period.

Requests to Bluesky

Your browser contacts Bluesky's public API to retrieve displayed post text and, when you open a profile preview, profile information. It may also resolve handles mentioned in displayed profile text. Public profile images are loaded from Bluesky's CDN. These requests disclose your IP address and the requested post, profile, or handle to those services. API lookups do not send Bluesky login credentials and use short-lived, in-memory caches.

Following a Bluesky profile or post link takes you to another service, whose own privacy policy applies. See Bluesky's privacy policy.

Questions and requests

Contact Barry Dorrans on Bluesky at @blowdart.me with privacy questions or requests concerning your recorded data. Include your account DID or a relevant post link so the records can be identified. Do not send passwords or other secrets. If you contact me publicly, your message will also be public.

The operator can exclude your DID from this project, deleting stored replies authored by or addressed to it and removing its cached identity data. The DID itself is retained in an exclusion list to prevent future ingestion. Exclusion affects the active database; it cannot remove copies already downloaded by others, earlier diagnostic logs, or separately managed backups.

This policy may change as the project changes. The update date above identifies the current version.