Privacy Policy

Last updated: May 19, 2026

Summary

CoopleDog helps Slack users preview HTML locally in their browser. CoopleDog does not store HTML, clipboard content, Slack message text, or Slack files.

Data We Process

Slack sends event payloads to CoopleDog when subscribed events occur. CoopleDog may inspect message text in memory to detect likely HTML and decide whether to post a renderer link.

CoopleDog stores workspace installation information needed to operate the Slack app, including workspace ID and bot token. Short-lived OAuth state and event dedupe records may also be stored.

CoopleDog also stores aggregate renderer usage counts when someone successfully renders HTML. These counts may include a broad source such as file, paste, or manual entry, but do not include HTML, filenames, clipboard content, Slack identifiers, or user identifiers.

Data We Do Not Store

• HTML content
• Clipboard content
• Slack message text
• Slack file contents
• File names
• Rendered previews

Rendering

The renderer reads clipboard content only after the user clicks or pastes. Pasted or dropped HTML is written into a local browser iframe and is not sent to CoopleDog for rendering. A successful render sends one small usage ping so CoopleDog can count that the renderer was used. Scripts and external URLs are enabled by default for a realistic preview and can be turned off from the renderer settings.

Third Parties

CoopleDog uses Slack for app events and Cloudflare for hosting. CoopleDog does not sell user data. If rendered HTML references external URLs, the user's browser may request those URLs unless external resources are disabled in settings.

Retention

Workspace installation tokens are retained until the app is uninstalled or access is revoked. OAuth state and event dedupe records expire quickly.

Contact

Email support@rhylan.uk.