Replyo Privacy Policy

Last updated: October 11, 2026 (PDT)

Replyo is an independent browser extension that shows the directly replied-to post beside supported replies in X notifications. This policy explains how Replyo handles information. Contact: alanhu1024@gmail.com.

What Replyo processes

After you review the data-use notice and enable Replyo, it reads information from supported X pages in your browser: post and reply text, author display names and usernames, public follower counts of post authors and repliers when available in X's loaded page data, post identifiers and links, and the relationship between a reply and its direct parent. Follower counts come from data X has already loaded for the page; Replyo makes no additional profile requests to obtain them. It also reads the current X account handle from the navigation profile link to keep context caches separate when accounts change.

This includes website content and personal information such as names and usernames. For the extension's context feature, the Web history disclosure covers only the specific X post links needed for context, and the Personal communications disclosure covers only posts and replies the signed-in X account can access. Processing happens locally even though this information is not sent to the developer. Replyo does not read X direct messages, your password, or authentication cookies. It does not read Chrome's history database, process content from other websites, or track activity across them.

Why it uses this information

Replyo uses this information only to identify a reply's direct parent, display its text and author together with available public follower counts for the original author and replier, reuse recent context, and avoid mixing information between signed-in accounts. It does not use it for advertising, profiling, AI training, or unrelated purposes.

Loading missing context

Previously cached context can be displayed automatically. If context is missing, manual loading is the default. When you choose to load it, Replyo may open a temporary inactive X tab to read the relevant parent page. You can separately enable automatic loading in the popup. It loads one page at a time. It closes its own loading tab after completion, failure, or timeout if you have not taken it over and it is still on the requested post page or has been redirected to an X sign-in page. Tabs you take over or navigate elsewhere are kept open.

These page requests go directly from your browser to X over HTTPS using your existing X session. X may receive normal website request information, such as the requested page and network information, under its own practices. Normal browser history behavior may also apply to these visits. Replyo does not copy or send your login credentials to the developer.

Storage and retention

• Preferences: The enabled and automatic-loading settings are stored in chrome.storage.local. They remain until you change them or uninstall Replyo; they are not synchronized through Chrome Sync by the extension.
• Context cache: Recent post context is stored in chrome.storage.session and separated by the identified X account. Parent-author follower counts are stored with the post context under the same cache limits, but each count has a separate 15-minute validity period. Reading and saving a valid count starts or restarts that count's period. An unknown count does not extend the previous count's deadline; a cached count can be reused only for the same author while it remains valid. Expired counts are not reused and are cleared during subsequent cache operations. Replier follower counts remain only in the current page's memory and are not written to extension storage. Replyo does not create a separate profile database. Each time Replyo reads a post from X's loaded page data and saves it, that record's 15-minute validity period starts or restarts. Reusing an existing Replyo cache entry does not extend the period. Expired records are not reused and are removed at the next cache operation. There is no background timer guaranteeing physical deletion at exactly 15 minutes. The cache is limited to 300 records and 4 MiB overall, and can be evicted earlier. It is cleared when the browser session ends.
• Temporary loading state: While loading context, session storage also records the extension-created tab identifier, the requested parent-post identifier, and whether the tab has been taken over. These records support safe cleanup, are removed when loading ends, and do not form a list of your other tabs.
• Session coordination: A numeric cache-revision counter synchronizes cache clearing and pausing across extension components. It contains no post content or account identifier and is cleared when the browser session ends.
• Clear cache: You can delete the current context cache from the Replyo popup at any time. Content on an open X page remains governed by X and is not deleted by this action.

Replyo does not keep an archive of your conversations or a copy on a developer server.

Sharing and developer access

Replyo has no developer-operated backend, analytics service, advertising tracker, or AI service. The extension does not transmit cached posts, account handles, follower counts, or preferences to the developer or sell them to anyone. Apart from the direct X requests needed to load context, Replyo does not transfer this information to another service.

If you voluntarily email support, the developer receives your email address, message, and any attachments you choose to send. The email provider processes that correspondence. It is used to answer your request and troubleshoot the issue, retained only as needed for that purpose and any applicable obligations, and deleted on request when it no longer needs to be kept. Please avoid sending passwords, authentication cookies, or private post content. Support does not require access to your X account.

Your controls

You can enable or disable Replyo, choose manual or automatic loading, clear its context cache, or uninstall it. Turning it off stops new content processing and clears the context cache. Uninstalling removes the extension's local settings and storage. For support correspondence or privacy questions, email alanhu1024@gmail.com.

Security and limitations

Replyo requests access only to https://x.com/* and uses packaged extension code. Its context cache is temporary browser-session storage; this policy does not claim that cached data is separately encrypted by Replyo. Other people or software with access to your browser or device may be able to access information displayed there. X controls the source content and its availability.

Chrome Web Store Limited Use

Replyo's use of information complies with the Chrome Web Store User Data Policy, including its Limited Use requirements. Information handled for context previews is used only for that disclosed feature. It is not sold, used for personalized advertising, or used to determine creditworthiness or lending eligibility.

This policy page and changes

The packaged policy page contains no scripts, external fonts, or tracking resources. If you view a hosted copy, your browser contacts that website's hosting provider; this is separate from the extension's operation.

The policy may be updated when Replyo changes. The date above identifies the latest revision. Material changes to data handling will be disclosed in the extension before the changed handling begins, with consent obtained where required.

Replyo is not affiliated with or endorsed by X Corp.