On this page
Privacy & Data Policy
Last updated: 18 July 2026
Leppa manages ephemeral channels in your Slack workspace. To do that it needs to remember a small amount of information about the channels it creates — and very little else. This page explains, in plain terms, what Leppa stores, what it deliberately never stores, and what happens to your data over time.
The short version:
- Leppa stores channel timers and settings, not conversations. It never reads your messages unless a workspace admin explicitly turns on the optional AI summaries feature.
- No personal names, no email addresses, and no message content are kept in our database.
- Uninstalling Leppa stops everything immediately, and your workspace's data is deleted after a 30-day grace period.
What Leppa stores
Everything below is stored per workspace, and every workspace's data is kept strictly separate from every other's.
| What | Why |
|---|---|
| Slack identifiers — your workspace's ID and the IDs of users, channels, and user groups | The minimum needed to manage channels and record who asked for what. These are opaque codes (like U0123ABC) that mean nothing outside your workspace. |
| The access credentials Slack issues when Leppa is installed | Slack requires them for Leppa to create, warn about, and archive channels in your workspace. They're stored encrypted, and revoked the moment you uninstall. |
| The names of channels Leppa created | So your dashboard can list and search your managed channels. These are names Leppa itself generated from your naming patterns. |
| Your templates and workspace settings | The product's own configuration: naming patterns, topics, welcome messages, durations, and default invitees (kept as Slack IDs, not names). |
| An audit trail — the action taken, the acting user's ID, the channel, and the time | So admins can see who extended, kept, or archived a channel, and when. |
| Your workspace's name, logo, and member count | Used to label and identify your workspace in the admin pages. This describes the workspace, not any person, and it's deleted with the rest of your data. |
| An optional contact email on a waitlist request | Only if you volunteer it when requesting access, and only so we can tell you when your workspace is approved. It's deleted the moment the request is decided. |
Usage analytics are counts only — how many channels were created, which templates get used, and broad app activity such as which pages get visited. Every metric is tied to an anonymised workspace label, never to a person; Leppa uses no third-party analytics service and no tracking cookies. These anonymous totals outlive workspace deletion.
What Leppa never stores
- Your messages. Leppa posts messages (reminders, welcome text) but never reads, processes, or keeps what your team writes. The one exception is the optional AI summaries feature described below — and even then, messages are read once to produce a summary and are never stored.
- Personal names and email addresses. The names and avatars of people you see in the admin pages are fetched from Slack while you're looking at the page and are never written to our database. (Your workspace's own name and logo are stored — they describe the workspace, not a person.) The only email Leppa ever holds is the optional waitlist email above.
- Direct messages. Leppa has no access to DMs or group DMs of any kind.
- Anything about channels Leppa doesn't manage. Channels it didn't create (and wasn't explicitly asked to manage) are invisible to it.
AI channel summaries — optional, off by default
Out of the box, Leppa cannot read messages at all. A workspace admin can
enable the optional AI summaries feature, which asks for one extra Slack
permission and uses it for exactly one thing: when a managed channel archives
(or when someone runs /leppa summarise), Leppa reads that channel's recent
messages and produces a short summary of decisions and outcomes.
- The messages are used once, to generate that summary, and are never stored.
- The summary is generated from a pseudonymised transcript ("Person A said…"), so no names or handles are ever sent to the AI.
- When the summary is posted back into the channel, Leppa re-attaches an @-mention to whoever owns each decision or open follow-up, so they're notified — the pseudonyms are matched back to the channel's own members afterwards, nothing extra is sent to the AI to do it.
- Summarisation runs inside our hosting provider (Cloudflare) — your messages are never sent to any other company.
- What Leppa keeps is the finished summary — a few sentences shown in the channel and on your dashboard. The copy kept for the dashboard stays pseudonymised, and it's deleted with the rest of your workspace's data on the schedule below.
Turning the feature off in Settings stops all message reading immediately.
The sign-in cookie
Signing in to the admin pages sets a single cookie in your browser. It holds your Slack workspace and user IDs, your display name and your workspace's name (used to label the pages), an expiry date, and a security token. It lives for up to 30 days, only on your device — your display name is never copied into our database. Signing out removes it.
Leppa sets no advertising or tracking cookies, on any of its pages.
How long data is kept
- While Leppa is installed, your workspace's data is kept so the product works.
- When you uninstall — from Slack's app management page or from Leppa's settings page — Leppa's access to your workspace is revoked and all channel management stops immediately. Your data is kept for a 30-day grace period, so reinstalling within it restores your templates and settings, and is then permanently deleted.
- The audit trail is kept for 1 year, then reduced to anonymous aggregate numbers.
Who else handles your data
Leppa is built on infrastructure from two companies:
- Cloudflare hosts all of Leppa's computing and storage, including the optional AI summaries.
- Slack is the platform Leppa works inside; Leppa exchanges data with Slack's API to do its job.
No other third party receives any of your data. Error reports and logs stay within Cloudflare, and never contain message content, names, or emails.
Deleting your data
Uninstall Leppa and your workspace's data is deleted on the schedule above: everything stops immediately, and the stored records are permanently removed after the 30-day grace period.
Because Leppa keeps no message content, personal names, or email addresses, there is usually nothing more to ask for: what exists during the grace period is the channel records, templates, settings, and audit entries described on this page, and all of it goes.