ReDeck Privacy Policy

Summary

ReDeck does not collect, store, transmit, or sell personal information to the developer or to third-party analytics or advertising services.

ReDeck runs entirely on your device. Your layout, settings, and preferences are saved locally in your browser profile (extension) or app storage (desktop app). ReDeck does not operate any backend server that receives user data.

When you use ReDeck, you sign in to X through X’s own website in your browser or inside the desktop app. ReDeck does not receive, store, or transmit your X/Twitter password or credentials to the developer.

Personal Information

ReDeck does not access, collect, or transmit personal information (data that could be used to identify a person) to the developer.

ReDeck may display content from X — such as usernames, profile names, or posts — only because you choose to browse X while signed in. That content is loaded from X and shown in the extension or app. It is not sent to ReDeck servers, because ReDeck does not operate such servers.

Local Storage

ReDeck saves your preferences locally on your device, including:

Column layout and order

Per-column settings (width, auto-reload interval, display preferences)

Global settings (font size, sleep mode timeout, media viewer preference)

Account labels or tags you create in ReDeck

Workspace names and layout backups

This data stays on your device and is not accessible to the developer or any third party.

Network Activity

ReDeck does not make network requests to servers owned or operated by the developer.

All network activity is limited to X/Twitter and related domains (x.com, twitter.com, twimg.com, and other domains required for X to function):

Embedded X content: ReDeck loads X pages so you can use your existing X session. Communication with X is between your device and X, under X’s Privacy Policy.

Response header reading: ReDeck may read x-rate-limit-* response headers from X/Twitter API responses to display API rate limit usage. Request and response bodies are not collected or sent to the developer.

Header modification: ReDeck may adjust response headers on X/Twitter pages (such as Content-Security-Policy or X-Frame-Options) to enable the multi-column layout. This applies only to X/Twitter-related requests.

Analytics blocking: ReDeck may block selected X/Twitter analytics or tracking requests to reduce unnecessary network traffic.

Authentication

ReDeck does not provide its own login system. You sign in directly on X in your browser or inside the desktop app. ReDeck does not access, read, store, or transmit your X/Twitter username, password, or authentication tokens to the developer.

Third-Party Services

ReDeck does not integrate with third-party analytics, advertising networks, or data brokers. Your use of X/Twitter is subject to X’s own terms and privacy policy. ReDeck is not affiliated with X Corp.

Install pages (Chrome Web Store, Microsoft Edge Add-ons, Microsoft Store) have their own policies for downloads and updates.

Data Deletion

Because ReDeck does not collect personal information on developer servers, there is no developer-held account data to delete.

To remove locally stored ReDeck data from the browser extension, uninstall the extension or clear site data for x.com in your browser settings.

To remove locally stored data from the Windows desktop app, uninstall the app or clear the app’s local data through Windows settings.

Changes to This Policy

If this privacy policy is updated, the revised version will be published on this page.

Contact

Questions? Open an issue on the ReDeck GitHub repository: https://github.com/BurakVeziran/redeck