Privacy Policy
Effective date: April 16, 2026 Applies to: Skeeditor browser extension and related documentation site
This Privacy Policy describes how Skeeditor handles information when you use the extension.
1. Who we are
Skeeditor is an open-source browser extension for editing your own Bluesky posts. Unless otherwise stated, references to “we”, “us”, or “our” in this policy refer to the Skeeditor project maintainers.
2. Scope
This policy applies to:
- the Skeeditor extension running in your browser; and
- extension-related service endpoints explicitly used by extension features.
This policy does not govern third-party services that Skeeditor interacts with (for example, Bluesky infrastructure). Those services are governed by their own terms and policies.
3. Information processed by the extension
Skeeditor does not operate an analytics or advertising data pipeline. The extension does, however, process limited data required for core functionality.
3.1 Information stored locally in your browser
Skeeditor stores the following in extension storage (browser.storage.local):
- OAuth access and refresh tokens, account identifiers, and account selection state
- per-account service configuration (for example, PDS URL)
- extension settings (for example, edit time limit and save strategy)
- pending labeler prompt state
- DPoP key material used for OAuth proof-of-possession
This data is stored locally in your browser profile and is not directly readable by websites.
3.2 Information transmitted over the network
To provide extension features, Skeeditor transmits data to:
- Bluesky OAuth and AT Protocol endpoints (authorization, token exchange/refresh, record read/write)
- Skeeditor labeler endpoints (label emit and label subscription websocket)
- Slingshot read-acceleration endpoint for public record lookup in specific flows
- DID/profile resolution endpoints (
plc.directory,api.bsky.app,public.api.bsky.app) - Skeeditor documentation-hosted OAuth metadata/callback pages
When labeler emit is active, Skeeditor may send your OAuth access token in an authorization header to permit labeler-side identity verification. Skeeditor does not send refresh tokens to the labeler.
4. What we do not do
Skeeditor does not:
- run telemetry, analytics, ad-tech trackers, or crash-reporting pipelines
- sell personal information
- broker or rent user data
- use extension data for personalized advertising
5. Purpose of processing
Data is processed only to provide extension functionality, including authentication, account/session management, post editing, conflict handling, and optional labeler-related behavior.
6. Data sharing and disclosure
Skeeditor does not share data with data brokers or advertising networks. Data is transmitted only as required to provide extension features, comply with legal obligations, or protect service security and integrity.
7. Retention and deletion
Skeeditor data is retained in your browser extension storage until you remove accounts, clear extension data, or uninstall the extension. You can sign out and remove account sessions from extension UI controls.
8. Security
Skeeditor uses HTTPS/WSS for network transport and follows OAuth 2.0 + PKCE and DPoP patterns for authentication flows. No method of transmission or storage is guaranteed 100% secure, but reasonable technical safeguards are applied.
9. Children’s privacy
Skeeditor is not directed to children and is intended for users of Bluesky-compatible services.
10. International use
Depending on your selected services/endpoints, data may be processed in jurisdictions outside your country of residence.
11. Changes to this policy
We may update this policy from time to time. Material changes will be reflected by updating the effective date and publishing the updated version at this URL.
12. Contact
For privacy questions or requests, open an issue at: