What the extension accesses

XPorter accesses the following to perform the exports you start and build the local seen-post dataset:

• X.com session cookies — to authenticate API requests on your behalf, making the same calls X.com already makes in your browser. No credentials are stored or copied.
• X.com API responses — profile info, posts, your current account's personal bookmarks, and follower/following lists, processed locally to build your export file (CSV, JSON, XLSX or TXT). Bookmark content is accessed only when you explicitly start a Bookmarks export.
• X public client assets — a public JavaScript asset may be downloaded from X's abs.twimg.com CDN and parsed as text to derive a request header required by some X feeds. XPorter does not execute that remote code and sends the CDN no cookies, auth headers, usernames, or export data.
• X media files — when you explicitly select embedded photo previews and save an XLSX file, XPorter downloads optimized previews from pbs.twimg.com without credentials and adds them locally to a Media sheet. This is off by default. Images are not sent to XPorter or any third-party server; the original media URL remains in the export even when a preview cannot be downloaded.
• Posts already loaded while you browse X.com — non-reply posts and their public metrics are deduplicated by post ID and stored locally in IndexedDB. No additional request is made and page URLs are not stored.
• Extension settings — your preferences (language, theme, export options) stored locally via Chrome's storage.local.

What XPorter does NOT do

• Does not collect or store your X.com password
• Does not send your exported data, X content, usernames, or browsing history anywhere
• Does not use analytics, advertising, or tracking SDKs during normal use
• Does not store browsing history or page URLs; the local dataset contains post data and the X timeline operation that supplied it
• Does not modify your X.com account (no posting, following, liking, bookmarking or removing bookmarks)
• Does not inject ads or promotional content
• Does not load any remote code — everything runs from the extension package

Diagnostics and uninstall feedback

Chrome opens a feedback page when you remove XPorter. Its URL carries a compressed diagnostic summary, which the page records through Google Apps Script in a private Google spreadsheet. Compression is not encryption; the summary can be read from that URL and may remain in browser history. The summary contains:

• Extension and coarse browser version, operating system, installation timing, interface language, light/dark mode and selected theme preset
• Popup opens, number of ladybugs squashed, approximate active time, active days, export counts, collected row counts and selected export settings
• Since the interface-counter baseline: Start clicks, submitted and accepted starts, validation or worker failures, views without an X session, initial status-read failures, Settings/About visits and committed theme or speed changes. These are counts; typed account names and form contents are not included.
• Current colorful appearance and ladybug preferences, window width and height, element and text size percentages, automatic deletion and its saved hours, selected export mode and format, content filters and photo options
• Up to five recent export attempts: mode, format, timing, result, fixed error code, phase, request/retry/rate-limit counts and pause time
• Up to five recent save attempts: generation time, file size, part count, browser completion or interruption, and photo-preview counts
• A random installation identifier, which links reports from the same installation; it is not an X account identifier
• Feedback language, time on the page, selected reasons and any text or contact details you submit, linked by a random per-visit session identifier created by the page

Optional feedback can specify the step that failed and the file formats you wanted. These are your answers, not records of formats you exported. An unfinished answer is temporarily kept in this browser tab so it survives a reload.

Recent details may be omitted to fit Chrome's uninstall URL limit. Reports mark omitted records explicitly. No exported content, X identifiers, file names, cookies, request URLs or full browser user-agent string are included automatically.

During use

Product diagnostics stay local while using the extension. The optional usage-sharing experiment and local report button have been removed.

Reports help diagnose failures and improve XPorter. Uninstall feedback covers only people whose feedback page loads; it is not a complete count of users.

Permissions explained

cookies

Reads authentication tokens (CSRF token) from your X.com session to make authenticated API requests.

downloads

Saves the exported CSV, JSON, XLSX or TXT file to your Downloads folder when you click download.

storage & unlimitedStorage

Stores preferences, resumable export batches, recent export history, local diagnostic counters, and the deduplicated seen-post dataset locally in Chrome. unlimitedStorage prevents larger local datasets and exports from being truncated by Chrome's normal storage quota.

Host access to x.com

Required to make API calls to X.com to retrieve the data you asked to export, and to read the address of an open X.com tab so the popup can suggest the profile you are viewing.

Data storage

• Export rows are saved in batches to Chrome's storage.local so interrupted exports can be resumed without losing already saved rows
• Downloaded CSV, JSON, XLSX or TXT files are saved to your local Downloads folder
• The current export and data snapshots for up to five recent history entries may remain locally until they expire, you start or clear an export, clear history, or uninstall the extension
• The seen-post dataset keeps one row per post ID, retains the 50,000 most recently seen unique posts, and remains until you clear it in Settings or uninstall the extension
• If you enable detailed “About this Account” data for user lists, public per-account results are cached in storage.local for up to seven days to avoid repeating the same X requests. Failed lookups expire after one hour, and the cache is capped at 25,000 accounts
• Settings are stored in Chrome's storage.local and cleared when you uninstall
• A bounded local diagnostic record (including opens, active time, export counts, install date, and last error code) is kept in storage.local to build the uninstall summary, and removed when you uninstall

Third-party services

XPorter integrates with no analytics platforms, ad networks or trackers. Normal exports contact X-owned x.com APIs and may read a public abs.twimg.com client asset as text; that asset is never executed, and no authentication or export data is sent to the CDN. The diagnostic and feedback flows described above use Google Apps Script and Google Sheets.

Data security

All communication with X-owned services uses HTTPS. Your own X session cookies and CSRF token are read only when a request is made, are never stored or copied by XPorter, and are sent only to x.com API requests — never to abs.twimg.com or to the feedback service. X's public web-client bearer token, which is the same for every user and identifies no one, may be cached locally in storage.local together with discovered API operation IDs.

Children's privacy

XPorter is not directed at children under 13 and does not knowingly collect information from minors.

Changes to this policy

Updates will be reflected on this page with a new effective date. Significant changes will be noted in the extension's changelog.

Contact

Questions about this policy or the extension? Message me on Telegram (fastest reply), or email art.lemelson@gmail.com (I check it rarely, so I may be slow). You can also find me on GitHub.

Effective date: September 22, 2026