Geekpulp Life, Design, Code

Pulp extension

Pulp Privacy Policy

Pulp helps you turn the current webpage into a markdown link post and commit it to a GitHub repository you choose. This page explains what information the extension handles, how it is used, and where it is stored.

Effective date: 22 April 2026

Pulp - Markdown Blog Link-Post Creator (“Pulp” or the “extension”) helps users create markdown link posts from the current webpage and commit those posts to a GitHub repository they choose.

What this extension does

  • Reads the active tab URL and title when the user opens the extension popup or invokes the extension from its context-menu shortcut.
  • Optionally reads user-selected page text from the current page to include as a quote.
  • Builds markdown content locally in the browser.
  • Sends authenticated requests to GitHub to list repositories and create markdown files in the user-selected repository.

Information the extension handles

1) User-provided authentication data

  • GitHub sign-in access token, if the user connects using the extension’s built-in GitHub sign-in flow.
  • GitHub Personal Access Token (PAT), if the user chooses the token fallback instead.

2) Repository and account metadata

  • GitHub account username/login.
  • Repository list available to the authenticated account.
  • Selected repository details (owner/name/default branch/permissions summary).
  • User-configured posting defaults (branch, posts path, drafts folder, filename template, title prefix, categories, tags, attribution template).

3) Webpage context (only for post creation)

  • Active tab URL.
  • Active tab title.
  • Optional selected text from the active page (if present).

How information is used

Information is used only to:

  • Complete GitHub sign-in or PAT-based authentication.
  • Allow the user to choose a target repository.
  • Load repository metadata for that authenticated account.
  • Create markdown files in that repository when the user explicitly submits a post.
  • Pre-fill the post form with the current page title, URL, and optional selected text only during user-initiated post creation.

The extension does not use collected information for advertising, profiling, or data brokerage.

Where data is sent

Data is sent only to GitHub endpoints required for authentication and repository/file operations:

  • https://github.com/*
  • https://api.github.com/*

The extension does not download, evaluate, or execute remote code. All executable code is packaged with the extension.

Local storage

The extension stores configuration and auth state in Chrome extension storage, including:

  • chrome.storage.local for persistent configuration and auth tokens.
  • chrome.storage.session for temporary values (for example, context-menu selection and sign-in flow UI state).

Data sharing

The extension does not sell or share user data with third parties for advertising or unrelated purposes.

Data retention and user control

Users can control stored information by:

  • Replacing or removing credentials in extension options.
  • Signing out of GitHub auth from extension options.
  • Uninstalling the extension (which removes extension-local storage).

Security note

Users do not need a personal access token for the default setup; the extension supports GitHub sign-in directly.

If a user chooses PAT-based access, they should prefer a fine-grained token with the minimum required repository access and Contents: Read and write permission.

Children’s privacy

This extension is not directed to children under 13.

Changes to this policy

This policy may be updated as the extension evolves. Material changes should be reflected by updating this document’s effective date.

Contact

For questions or requests, send an email to: Pulp Feedback