fog — Privacy Policy
Last updated: February 24, 2026
Overview
fog is a collaborative ideation canvas. The fog Chrome extension lets you save images, links, and text from any webpage to your fog account. The extension only accesses page content when you explicitly initiate a capture action — it does not run in the background, monitor your browsing, or collect any data without your direct interaction.
What fog collects
-
User-selected website content — When you choose to capture content (via right-click menu or the extension popup), the extension reads image URLs, page titles, and source URLs from the active tab. Only the content you explicitly select is sent to the fog server and stored in your account.
- Authentication token — A token linking the extension to your fog account is stored locally in Chrome's extension storage. This token is used to authenticate requests to the fog server. It is never shared with third parties.
What fog does not collect
-
fog does not collect personally identifiable information such as your name, email address, or physical address through the extension.
-
fog does not collect or monitor your browsing history.
-
fog does not track your activity — no clicks, mouse movements, scroll behavior, or keystroke logging.
-
fog does not passively scrape, scan, or read page content in the background. The content extraction script is only injected into a page after you explicitly trigger a capture action.
-
fog does not collect location, financial, or health data.
-
fog does not sell, share, or transfer any data to third parties.
- fog does not use any collected data for purposes unrelated to saving content to your fog account.
Permissions explained
-
activeTab — Grants temporary access to the current tab when you initiate a capture. Used to read the page URL, title, and selected content. Access is revoked when you navigate away.
-
scripting — Injects the content extraction script into the active page on demand, only after you click the extension icon or use the right-click menu. No scripts run automatically or persist after the capture is complete.
-
storage — Stores your authentication token and API endpoint locally in Chrome's extension storage.
-
contextMenus — Adds the "Add to fog" right-click menu option for quick captures.
- Host permission (.supabase.co) — Required to authenticate your account and sync captured content to the fog server. This is the only external host the extension communicates with.
Data storage and security
Captured content is stored on fog's servers (hosted via Supabase) and is accessible only to your account. All communication between the extension and the fog server uses HTTPS encryption. You can delete any saved content at any time from the fog library or canvas.
Changes to this policy
We may update this privacy policy from time to time. Any changes will be reflected on this page with an updated date. Continued use of the extension after changes constitutes acceptance of the updated policy.
Contact
For questions about this policy or your data, contact hello@fog.do