Privacy Policy
-Last updated: January 3, 2026
+Last updated: September 12, 2026
Impro is a third-party web client for Bluesky. It is not affiliated with Bluesky PBC. This policy describes the web client. The services you @@ -32,18 +32,18 @@
Authentication and account access
Impro uses Atproto OAuth to authorize access to your account. Session - credentials are stored in your browser's local storage and used to - make authenticated requests to your account's services. Impro requests + credentials are stored in your browser's local storage and used to make + authenticated requests to your account's services. Impro requests permissions for a full social client, including reading and publishing - posts, managing follows and blocks, accessing preferences and - bookmarks, and reading and sending chat messages. Review the - permissions shown when authorizing Impro. + posts, managing follows and blocks, accessing preferences and bookmarks, + and reading and sending chat messages. Review the permissions shown when + authorizing Impro.
Where server-signed OAuth client assertions are enabled, your browser also sends the authorization server's address to Impro's signing - endpoint. That request is used to obtain a client assertion; it does - not contain your account's access or refresh tokens. + endpoint. That request is used to obtain a client assertion; it does not + contain your account's access or refresh tokens.
Browser storage and account services
@@ -55,10 +55,10 @@Account actions and data requests are sent to the relevant services, - including your account host, the selected feed and profile service, - and the chat service. Bluesky-operated services are governed by - Bluesky's Privacy Policy. If you use another account host or select an - alternative service, that provider's practices also apply. + including your account host, the selected feed and profile service, and + the chat service. Bluesky-operated services are governed by Bluesky's + Privacy Policy. If you use another account host or select an alternative + service, that provider's practices also apply.
Additional lookups and embedded content
@@ -77,9 +77,9 @@Loading media and other external resources involves requests to their - providers. For example, playing an embedded YouTube video loads a - player from YouTube's privacy-enhanced domain. The provider's own - privacy practices apply when its content is loaded. + providers. For example, playing an embedded YouTube video loads a player + from YouTube's privacy-enhanced domain. The provider's own privacy + practices apply when its content is loaded.
Community plugins
@@ -91,38 +91,37 @@Plugins run in a sandbox, with network requests mediated by Impro's permission system. Access to private account data, such as mutes, - bookmarks, notifications, and preferences, requires permission. - Plugins can also store data locally or in account preferences. + bookmarks, notifications, and preferences, requires permission. Plugins + can also store data locally or in account preferences.
A plugin with permission to access data and contact an external - destination may send that data to the destination. The sandbox does - not guarantee how a plugin uses permissions you grant. Review each - plugin's permissions and its developer's data practices before - enabling it. + destination may send that data to the destination. The sandbox does not + guarantee how a plugin uses permissions you grant. Review each plugin's + permissions and its developer's data practices before enabling it.
Optional push notifications
- Push notifications require selecting a notification service and - enabling notifications. Setup registers your browser's push - subscription with the selected service. If the service requires a - separate authorization step, Impro sends it your account identifier, - a return address, and whether you requested chat previews. + Push notifications require selecting a notification service and enabling + notifications. Setup registers your browser's push subscription with the + selected service. If the service requires a separate authorization step, + Impro sends it your account identifier, a return address, and whether + you requested chat previews.
- The notification service and your browser's push provider are - additional parties involved in delivery. Review the selected service's - permissions and privacy practices, particularly before enabling chat - previews. You can disable push notifications in Impro's settings. + The notification service and your browser's push provider are additional + parties involved in delivery. Review the selected service's permissions + and privacy practices, particularly before enabling chat previews. You + can disable push notifications in Impro's settings.
Contact
For questions about this policy, contact the project through - GitHub. - GitHub issues are public; do not include passwords, session tokens, - private messages, or other sensitive account information. + GitHub. GitHub + issues are public; do not include passwords, session tokens, private + messages, or other sensitive account information.
Go Back