Privacy for the Markd web app and Chrome extension

Information we collect

Markd may collect the following categories of information when you use the web app or extension:

• Account information such as your email address and basic profile details when you sign in with Google.
• Saved content you choose to store, including page URLs, video URLs, titles, descriptions, thumbnails, domains, timestamps, and other metadata relevant to the save.
• Workspace metadata such as queue state, favourites, collections, tags, and related organizational information.
• Limited technical storage needed to operate the extension, such as authentication tokens, API base URL configuration, and any temporary offline save queue stored in browser extension storage.

How the Chrome extension works

The Markd Chrome extension is designed to save the current page or YouTube video into your Markd workspace. Based on the current implementation, the extension:

• Uses Google sign-in through Chrome identity APIs so you can authenticate with your Markd account.
• Reads the current page or current YouTube video only when you actively use the extension or related save actions.
• Extracts metadata such as page information, YouTube video title, channel, timestamp, thumbnail, and duration when available.
• Stores limited data in extension storage to support authentication and temporary offline save retry behavior.

Chrome extension permissions

The current extension manifest includes permissions for storage, identity, active tab access, tabs, alarms, context menus, and scripting, as well as host permissions for YouTube and general page saving. These permissions are used to:

• Authenticate users and maintain extension session state.
• Save the active page or selected YouTube video.
• Support context-menu save actions and popup-based saving flows.
• Retry queued saves when connectivity returns.
• Display confirmation feedback on supported pages after a save succeeds.

How we use data

Markd uses saved content and related metadata to operate the product. This includes:

• Saving the content you explicitly choose to store.
• Displaying that content in your library, queue, sources, structure, favourites, and discovery surfaces.
• Supporting search, retrieval, organization, and recommendation features inside your workspace.
• Providing extension and web-app functionality such as sign-in, save confirmation, and offline retry handling.

Third-party services

The current implementation uses third-party services for core product operation, including:

• Google, for sign-in and Chrome identity flows.
• Supabase, for authentication and backend data handling.
• Other infrastructure and processing services that may be used to support search, organization, and AI-assisted features inside Markd.

Data sharing and selling

Markd is intended to use your data to provide the product to you. We do not design the product around selling your saved content. If processors or infrastructure providers are used to operate the service, they are used to provide Markd functionality rather than to advertise to you.

Your choices

You can choose what to save into Markd, whether to sign in, and whether to use the Chrome extension at all. You can also remove saved items from your workspace and stop using the extension by uninstalling it.