PatrolPost 隱私權政策 ／ Privacy Policy

English

PatrolPost is a Chrome extension that saves the social media posts and media you are browsing to your own computer and organizes the posts you have viewed, locally. PatrolPost has no server of its own, does no analytics or tracking, and does not send your data to the developer or any third party. This policy explains what PatrolPost handles, where it is stored, and how to delete it.

1. What data PatrolPost handles

PatrolPost handles the following data only inside your browser and never sends it to the developer or any third party:

• Post content: posts you download, and posts you have viewed on platforms that support Post Patrol. This includes post text, the author's display name and handle, post time, engagement counts (likes, comments, shares, views, etc.), the post URL, image and video URLs, and the images, videos and audio files you choose to download.
• Download records: for each download, the file name, time, platform, download mode, and which posts were downloaded (platform and post ID).
• Post Patrol records: summaries of posts you have viewed on Threads, Instagram, X, Bluesky and Dcard pages (used for ranking), and the history of your Post Patrol exports (up to 20 entries).
• Settings: output format, file name template, image quality, Post Patrol keywords and preferences, interface language, and the AI agent switch.
• Platform cooldowns: when a platform answers "too many requests" or asks for verification, PatrolPost records until when that platform is paused.
• Redeem status: whether a valid redeem code has been entered (a single yes/no value). PatrolPost does not store the code you typed.
• The current tab's URL: on enabled platform pages, to decide which buttons to show. On other tabs, PatrolPost reads the URL only when you click the PatrolPost toolbar icon, to check whether the tab is a supported platform.

PatrolPost does not collect passwords, payment data (credit cards, etc.), location, health data or private messages. PatrolPost does not read or store your cookies, with one exception: requests to www.instagram.com need the value of the csrftoken cookie in a header of the same request. That value is used only in memory, is never written to storage, and is never sent to any other site.

2. Where data is stored

All data stays on your computer:

• Extension storage (chrome.storage.local): settings, Post Patrol preferences, the AI agent switch, platform cooldowns, interface language, redeem status.
• Extension session storage (chrome.storage.session): a temporary map from download IDs to temporary file URLs while downloads are in progress. Each entry is released when its download ends, and the whole storage is cleared when the browser closes.
• The extension's IndexedDB: the library (data of posts you downloaded), download records and Post Patrol export history. Only the extension's own pages can read the database itself; websites cannot.
• Download buttons on web pages: for posts already in your library, the download button PatrolPost adds to the platform page is marked "Already downloaded". The button is part of the website's page, so the website's own scripts can see this mark, and therefore which posts on screen you have downloaded (and that PatrolPost is installed).
• The website tab's sessionStorage: the Post Patrol list is stored in that website's tab and is cleared when you close the tab. The website's own scripts can read this list too.
• Your Downloads folder: downloaded files are saved under PatrolPost/ (one folder per platform; Post Patrol exports in PatrolPost/patrol/, library re-exports in PatrolPost/library/ by default, backups in PatrolPost/backup/).
• Temporary in-memory caches: post data that was read is kept in the tab's memory for a while and disappears when you close the tab.

When disk space runs low, the browser may clear the extension's IndexedDB (the library). Downloaded files are not affected; export a backup regularly if the library matters to you.

3. How the data is used

The data is used only to provide the features you ask for:

• Creating the files and file names you download, and packing ZIP files.
• Showing, searching and filtering the library on the dashboard, and marking posts as already downloaded.
• Ranking, exporting and keeping the export history of Post Patrol.
• Answering the AI agent when you turn it on (see section 7).
• Remembering your settings and interface language.
• Pausing a platform that rate-limits or asks for verification, so PatrolPost does not overload it.
• Checking whether sponsor features are unlocked.

PatrolPost does not use data for advertising, analytics, creditworthiness or any purpose unrelated to these features, and does not sell data. PatrolPost's use of user data complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.

4. Network requests

PatrolPost has no developer server, does no analytics or tracking, and does not connect to any AI service. It only sends requests to platforms you have enabled and their media servers (CDNs), to read the post data you ask for and download the images and videos you choose:

• When it connects: Threads is enabled by default. Other platforms connect only after you click "Enable" in the extension and accept Chrome's permission prompt; you can revoke them anytime on the dashboard's "Platforms" page. Most requests are sent only when you act (download, open the download menu or batch panel, view the batch range in the popup, start a batch download, re-export "All" or "Media only" from the library on the dashboard) or when the AI agent calls PatrolPost. When you re-export from the library, media is fetched only from the media servers of platforms that are currently enabled; for revoked platforms and platforms this version does not support (for example YouTube posts imported from a backup of the self-loaded version), only text is exported and nothing is requested. One exception: while you browse bsky.app, PatrolPost sends the author handles and post identifiers of posts on screen to Bluesky's public API to get post times and engagement counts (for Post Patrol and the download menu), without you clicking anything.
• Login state: these requests are sent from your browser. Requests to the platform websites themselves (for example www.instagram.com, www.facebook.com, www.tiktok.com, www.dcard.tw, pinterest.com) may carry your existing login state (cookies) for that platform, just like opening that page yourself. PatrolPost does not read or store cookies (see section 1 for the Instagram exception). Downloads from media servers are sent without cookies, except TikTok videos: they are downloaded by the TikTok page from video servers on the tiktok.com domain, so the browser sends that site's cookies.
• Pace: PatrolPost uses a conservative pace (batch downloads have a post limit and a delay between requests). When a platform answers "too many requests" or asks for verification, PatrolPost pauses that platform for a while (5 minutes on most platforms, 2 minutes on Bluesky; longer if the platform asks for it, at most 24 hours). It does not retry automatically and never tries to get around these limits.
• Redeem codes stay offline: the redeem code you type is checked only on your computer (the code is turned into a hash and compared with a list built into the extension). It is never sent to any server, and no account is needed.
• The redeem code box on web pages: when you choose a sponsor feature on a supported platform page, PatrolPost opens a dialog on that page. The redeem code box inside the dialog is one of the extension's own pages, shown in an iframe, so the website cannot read the code you type. Only websites of platforms PatrolPost supports may embed this page. It only checks the code locally and sends no network requests.
• External links: the Telegram, email and Buy Me a Coffee links on the dashboard and in the sponsor information open in a new tab only when you click them. PatrolPost sends no data to these services. Anything you provide on those sites is covered by their own privacy policies.

5. No sharing with third parties

PatrolPost does not sell, share or transfer your data to anyone. The only things PatrolPost itself sends are the requests listed in section 4, which fetch content from the platforms. Those requests let the platform know which posts are being read, the same as when you browse those pages yourself.

In addition, a website's own scripts can read what is on its own pages: the download buttons and "Already downloaded" marks PatrolPost adds, the Post Patrol list stored in the tab's sessionStorage (section 2), and the window.PatrolPost interface once you turn on the AI agent (section 7). PatrolPost does not separately send this information to the website or anyone else, but it cannot stop a website from reading what is on its own pages.

6. Retention and deletion

• Library: kept until you delete it. You can delete posts one by one or select several and delete them together in the dashboard's library. Deleting a post does not delete the download records, which keep its platform and post ID; to delete those too, use "Clear all data" below.
• Clear all data: "Clear all data" under the dashboard's "Settings" empties the library, download records and Post Patrol export history, and can optionally reset your settings to the defaults. It does not delete files already downloaded to your computer, and it does not revoke platform permissions, end platform cooldowns or reset the redeem code (to reset the redeem code, use "Reset redeem code" in "Sponsor & redeem code" on the dashboard).
• Post Patrol list: cleared when you close that website tab.
• Platform cooldowns: expire automatically.
• Backups: you can export a JSON backup file (saved in your Downloads folder) and import it again from your own file. A backup contains the library, download records, Post Patrol export history (including keywords and the list at that time), settings, Post Patrol preferences, the interface language, and which platforms were enabled when it was made (on import this is only used to remind you to enable them again). It does not include the AI agent switch or the redeem status, and importing it never restores platform permissions. Importing only reads the local file you choose. A backup file records which posts you downloaded; keep that in mind before sharing it.
• Uninstalling: removing PatrolPost deletes the data the extension stored (extension storage and IndexedDB). Files already downloaded to your computer, including backup files, are not affected; delete them yourself if needed.

7. AI agent

• AI agent access is off by default. When you turn it on in the toolbar popup or on the dashboard, PatrolPost first shows an explanation and asks you to confirm; it takes effect only after you click "Turn on". Turn it off when you do not need it.
• Once it is on, PatrolPost adds a window.PatrolPost interface to every tab of an enabled platform. When the browser supports WebMCP, it also registers read-only tools with the page (list posts, read a post, Post Patrol list, reply context). Until you turn it off, any script on those tabs (including your AI tool and the website itself) can use it to:
  • list the posts on the page and read post content, the Post Patrol list and reply context;
  • start downloads;
  • scroll the page down at a human-like pace so the website loads more posts (just like scrolling yourself, the website loads them with your login state).
• The AI agent never posts, comments or likes.
• PatrolPost sends no data to any AI service. Your own AI tool reads the data on the page; what happens to it afterwards depends on the AI tool you use and its privacy policy.
• Backup files do not include the AI agent switch, so importing a backup never turns it on.

8. Changes to this policy

When this policy changes, this page and its "Last updated" date are updated, and the change is noted in the extension's release notes. If PatrolPost ever needs to send data to a new recipient, this policy will be updated and the change will be explained in the extension before it takes effect.

9. Contact

If you have any questions about this policy or how PatrolPost handles data, contact the developer:

• Telegram: @ElongmaTech
• Email: service@elongma.net