Privacy policy for Pocketify
Pocketify by AES Tech Studio
PRIVACY
Browser Extensions Privacy Policy
Effective and updated: October 27, 2026 · Applies to Pocketify browser extensions 1.3.0
This policy describes data handling by the Pocketify (AES Tech Studio) browser extensions for Chrome, Firefox, and browser versions using the same functionality. The Pocketify Mac and iPhone apps and their cloud features are covered by their respective app privacy policies.
The extension accesses browser data to search, display, and save content. It contains no advertising or behavioral analytics SDK and does not send browsing history, bookmarks, or page content to an analytics server operated by us. Browser account sync, external search, and resource loading can still involve the network transfers described below.
1. Data processed and purposes
Bookmarks, history, and frequently visited sites: titles, URLs, and related browser metadata are read to match and display results in the new tab page and command palette. History searches generally cover the last 90 days. We do not upload your entire bookmark or history library for advertising or analytics.
Open tabs: titles, URLs, icons, window IDs, and tab IDs are used to search and switch tabs and identify the page you want to save.
Pages you choose to save or preview: the URL, title, selected text, and page HTML may be read. Previews may also extract a description, site name, cover, and icon. Saving an image uses its URL, the source page URL, and title. HTML may contain personal information displayed on the page; save only content you want Pocketify to handle.
Pocketify content and configuration: available saved links and their titles and URLs are read from the local Mac app for display and search. Followed sites, search sources, and appearance settings are synchronized. Actions to add or remove content or sites change the corresponding app data.
Settings and operational state: the extension stores language, search-source names and URL templates, triggers, site ordering and hidden entries, connection and recent-operation status, and temporary information needed to restore a workbench session. Exported settings files contain the corresponding configuration; review custom content and URLs before sharing them.
2. Website access
HTTP/HTTPS website access supports the command palette when invoked, the return-to-workbench control on sites opened from the workbench, and reading pages or retrieving icons when you request a save, preview, or search-source edit. Broad website permission does not mean the extension automatically uploads the content of every page you visit.
The extension does not use a cookies permission to bulk-read or export credentials. When you request saving a linked page, it may request that page from its original website using your existing browser session to retrieve content you are signed in and permitted to view, subject to browser rules. Website login cookies are not sent to the Mac app as saved-content fields.
3. Local communication with Pocketify Mac
The extension uses browser Native Messaging to communicate with a local companion component, which connects to Pocketify Mac over the local loopback interface. Save and preview data, search-source settings, and related requests may pass through this local path. This channel itself does not send them to an internet server operated by us.
Clicking the toolbar to open the Mac save-confirmation window may already transfer page data to the Mac app for preview, even if you later cancel. Keyboard and context-menu actions may initiate a save directly. Once saved in the Mac library, content is stored, synchronized, and deleted according to the Mac app settings and policy. App cloud sync or sharing with other services can transfer content off the device.
4. Browser sync and external websites
Configuration sync: saving settings uses the browser's storage.sync; a “Sync now” action is also available. If browser account sync is enabled, Google, Mozilla, or the relevant browser provider may process and synchronize configuration across devices. It may include custom URLs, search templates, site ordering, and hidden URLs. This differs from local-only storage.
External searches and links: confirming a search sends its terms as query parameters to your selected search-source website. Opening results or sites makes ordinary browsing requests to their destinations. Those websites' own privacy policies apply.
Icons, covers, and previews: requests may go to websites, image servers specified by pages, or icon URLs you configure. Those servers may receive your IP address, browser request information, the requested resource URL, and browser-permitted referrer information. These requests are not fully offline processing.
5. Use and sharing limits
We use the data above to provide and maintain the extension's visible features. We do not sell user data or use it for personalized advertising, credit assessment, or tracking unrelated to the extension. The extension contains no implementation that uploads browsing activity to advertising or analytics platforms. Beyond user-directed saving, search, sync, resource requests, or sharing, it does not provide this content to third parties for independent data trading.
Pocketify's use and transfer of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements.
6. Retention, controls, and deletion
Search results and previews may be held in memory or local extension caches. Configuration and some operational state remain in the browser profile until replaced, cleared, or removed with the extension. We do not maintain a separate server retention period for this local data.
You can disable or uninstall the extension, restrict site access, or clear extension data using your browser's available controls. Restricting permissions affects the corresponding features.
Manage synchronized configuration through your browser provider's sync and deletion controls. Clearing one device does not necessarily delete copies in the browser account.
Manage original bookmarks and history in the browser. Uninstalling the extension does not delete them.
Delete saved Mac content, cloud copies, and exported files in the relevant app or storage location. Uninstalling the extension does not delete the Mac library. The local companion component can also be uninstalled separately.
7. Security and this policy page
Executable extension code is included in the installed package. The browser manages extension permissions and its account-sync channel; Mac communication uses local Native Messaging and loopback transport. Websites and custom search sources may use HTTP, so transport protection depends on the destination. Prefer HTTPS and avoid including sensitive information in untrusted search sources or URL templates.
This policy page uses no advertising, analytics scripts, or tracking cookies. Its hosting provider may still process IP addresses and ordinary request logs to serve the page and maintain security.
8. Contact and updates
For privacy questions, concerns, or requests, contact hi.aestech.studio@gmail.com. Do not include your full browsing history, passwords, or sensitive page content in an initial message. We will update this page and its date when the extension's data handling changes.