📋

Point-Click-Comment
Privacy Policy

Last updated: November 16, 2024

Point-Click-Comment ("PCC," "we," "us") is a Chrome extension that helps stakeholders capture annotated screenshots and deliver them to their own Slack workflows. We designed PCC to operate entirely on your device. This policy explains what we store, what we send, and how your data is handled.

1. Data We Store Locally

PCC saves only the configuration values you provide in the Options page:

  1. Slack webhook URL (Incoming Webhook or Workflow Builder trigger)
  2. ImgBB API key
  3. Display name shown in Slack messages

These values are stored in chrome.storage.local on your browser. They never leave your device unless you are syncing extensions through your Google account (in which case they sync only through Chrome's standard mechanism).

2. Data We Transmit

When a user submits feedback:

  1. PCC captures the visible portion of the active tab, draws the highlight and note entirely in-memory, and converts it to a PNG.
  2. PCC uploads that PNG to ImgBB using the API key you provided. The image is stored under your ImgBB account.
  3. PCC sends a JSON payload to the Slack webhook you configured (either classic /services or Workflow Builder /triggers). The payload includes:
    1. The public image URL returned by ImgBB
    2. The comment text and page URL the user provided
    3. Your configured display name

No other services receive this data. We do not log or relay it to any PCC-controlled server.

3. Data We Do Not Collect

  1. No personally identifiable information
  2. No browsing history or page content beyond the screenshot the user explicitly submits
  3. No analytics, tracking pixels, or telemetry
  4. No cookies or advertising identifiers

4. Third-Party Services

PCC relies on:

  1. Slack: You provide the webhook endpoint. Slack's handling of messages is governed by their own terms and privacy policy.
  2. ImgBB: Screenshots are uploaded via the API key you supply. ImgBB's storage and retention policies are governed by their service terms.

You control both endpoints. Removing or rotating your webhook/API key revokes PCC's access.

5. Security

  1. All network requests use HTTPS.
  2. We recommend using dedicated webhooks and API keys that you can revoke if necessary.
  3. If your device has multiple users, consider clearing the PCC options or removing the extension to prevent access to your stored keys.

6. Your Choices

  1. You can remove or update your Slack webhook, ImgBB key, or display name at any time through the PCC Options page.
  2. Uninstalling the extension removes all locally stored data.
  3. To delete images stored at ImgBB, sign in to your ImgBB account and remove the files there.
  4. To remove Slack messages, delete them directly in Slack (PCC does not have the ability to delete posts once sent).

7. Contact

If you have questions or need to report a privacy concern, contact:

Email: jesse@emptycan.com

By using Point-Click-Comment you acknowledge that the extension operates solely on your device, transmits data only to the Slack and ImgBB endpoints you configure, and does not otherwise collect or sell your information.