Privacy Policy – Foldmark

Foldmark is a Chrome extension for capturing highlighted text, adding notes, organizing a private library, and exporting saved highlights. Foldmark is designed to be local-first: your highlights, notes, folders, and preferences stay on your device by default.

1. What Foldmark stores locally

Foldmark uses chrome.storage.local to store data needed for the extension to work, including:

• saved bookmarks and highlighted text
• highlight titles, notes, review and archive state, pin metadata, resurfacing metadata, and folder assignments
• folders and folder preferences
• app settings and preferences
• recoverable deleted items, drafts, and retention settings
• a local anonymous analytics queue and analytics state

This local data is used to provide the extension’s features and is not uploaded by default.

2. What Foldmark does not collect for analytics

Foldmark does not send the following as part of analytics or product telemetry:

• your name, email address, or account identity
• passwords or authentication credentials
• payment or financial information
• raw highlighted text or bookmark body content
• full browsing history
• search queries, full source URLs, or user-created folder names

Foldmark only accesses the active page, the user’s selected text, and related page metadata needed for the save and capture features the user invokes.

3. Anonymous analytics

Foldmark includes optional anonymous usage analytics to help improve the product.

Default behavior

• Remote analytics upload is disabled by default.
• You must explicitly opt in before analytics are uploaded.
• You can disable remote analytics upload at any time in Settings.

What analytics are used for

Anonymous analytics are used to improve capture reliability, search and organization features, and overall product usability and quality.

What analytics may include

• anonymous user ID
• session ID
• event timestamps
• event names such as bookmark creation, editing, searching, exporting, processing, and settings changes
• non-sensitive product metadata such as counts, flags, current library view, internal folder IDs, and durations

If a source reference is included, it is limited to non-sensitive metadata such as a domain name where applicable.

What analytics do not include

• raw highlighted text
• bookmark content
• personal identity information
• search queries, full source URLs, notes, or user-created folder names

Local analytics queue

Foldmark may store anonymous analytics events locally on your device even when remote upload is disabled. This local queue supports batching, retry behavior, and analytics status/debugging inside the extension. Local queueing does not itself send data to a server.

Remote analytics upload

If you enable analytics upload:

• events are sent over HTTPS
• uploads are batched

Analytics retention

• remote analytics events are retained in the backend for up to 90 days
• local analytics queue data remains on your device until uploaded or until extension storage is cleared

4. No external content processing

Foldmark 0.4 does not expose live AI summary or metadata-suggestion actions and does not send bookmark content to an AI provider. Any future feature that transmits saved content will require updated product consent, this policy, and the corresponding Chrome Web Store disclosures before release.

5. Third-party services

Foldmark may optionally communicate with third-party services only for the following product features:

• Analytics ingest for user-enabled anonymous analytics upload

The current public extension build does not send bookmark content to an AI provider through the shipped UI flows. Third-party services are not used for advertising or data brokerage.

6. Data ownership and user control

You retain control of your data.

• bookmarks and notes are stored locally by default
• you can export your library
• you can delete bookmarks, notes, and folders
• you can clear extension storage to remove local data
• you can disable analytics upload at any time

7. Security

Foldmark uses the following privacy and security practices:

• local-first data storage
• minimal data collection
• no remote code loading by design
• HTTPS for network communication when optional network features are used
• opt-in remote analytics upload only

8. Changes to this policy

This policy may change as Foldmark evolves. Material changes will be reflected by updating the date at the top of this document.

9. Contact

For privacy questions or requests:

Product: Foldmark
Email: contact@foldmark.app

10. Compliance statement

Foldmark is intended to align with:

• Chrome Web Store Developer Program Policies
• Chrome Web Store disclosure and limited-use requirements
• privacy-by-design and data minimization principles

This document is intended for public display on the Foldmark website and Chrome Web Store privacy policy link.