Privacy Policy

Last updated: September 11, 2026. This describes what pendnt collects, why, who else handles it on our behalf, and how to get it deleted. See Security for the technical detail on how data is protected.

1. Who we are

pendnt (https://pendnt.dev) is operated by Kade Angell, located at 550 S 300 W, N337, Salt Lake City, UT 84101, USA ("pendnt", "we", "us"). This policy applies to pendnt.dev, api.pendnt.dev, and the MCP server, and to anyone who creates a workspace or is sent an approval/notification through one.

2. Controller and processor roles

Two different roles apply depending on the data:

• Data you send us about yourself — your account email, workspace name, and billing details — we are the data controller: we decide why and how that data is processed, in order to run your account and bill you.
• Data your agent submits through the service — approval/notification text, inbound webhook payloads, KV values, and wakeup payloads ("customer content") — you are the data controller and we are the data processor: we store and relay it only as instructed by you (via your API key and configuration), and don't decide what's in it or why it's sent. If your customer content includes personal data about other people (e.g. an operator's name in an approval message), you're responsible for having a lawful basis to send it to us.

A Data Processing Addendum (DPA) is available on request at arkade523@gmail.com for customers who need one under GDPR Article 28 or similar.

3. What we collect

• Account data: the email you sign up with, workspace name, and plan.
• Billing data: handled by Stripe — we receive your plan, subscription status, and billing history, but never see or store full card numbers ourselves.
• API keys: we store a SHA-256 hash and short prefix, never the full key after creation — see Security.
• Customer content: approval/notification titles and details, inbound webhook events (method, path, query params, headers with hop-by-hop and Cloudflare-internal headers stripped, and body up to 256KB), KV key/value pairs, and scheduled-wakeup payloads.
• Delivery channel identifiers: whatever you connect — an email address, a Telegram chat ID, a webhook URL, or a push subscription — so we know where to deliver approvals and notifications.
• Operational and log data: IP addresses and request metadata used for rate limiting, abuse prevention, and debugging.
• Page-view counts on pendnt.dev: date, page path, and the hostname of the referring site if any — see Cookies and page counts below.
• One session cookie: see Cookies and page counts below.

We don't collect data we don't need to run the service — see Security for what we deliberately never ask for (cloud/deploy credentials, production secrets).

4. How we use it

Solely to operate pendnt: authenticating requests, storing and delivering approvals and notifications, receiving and relaying inbound webhook events, firing scheduled wake-ups, running the KV store, enforcing rate limits and plan limits, billing, and responding to support requests. We don't sell customer content or account data, we don't use customer content to train AI models, and we don't run behavioral advertising.

5. Subprocessors

We use a small number of subprocessors to run pendnt. Each is limited to processing data as needed for its function:

• Cloudflare — Workers (API/MCP compute), D1 (primary database), KV (rate-limit counters), Durable Objects (per-workspace coordination and wakeup timers), and Queues (channel delivery). All data storage and compute for pendnt runs on Cloudflare's network.
• Resend — sends transactional email for approval requests, notifications, and dashboard magic-link logins.
• Stripe — processes payments and manages billing/subscription state; handles your card details directly, we never see or store full card numbers.
• Telegram — delivers approvals and notifications to workspaces that connect a Telegram bot as a channel; only used if you set that channel up.

We'll note material changes to this list in the changelog.

6. Retention and deletion

Requests (approvals, questions, and notifications — resolved or still pending), inbound webhook events, and Telegram messages are retained for 7 days on the Free plan and 90 days on Pro, then automatically deleted — see Pricing. The per-workspace KV scratchpad isn't subject to this window. (Team, including its own retention window, is coming soon.) Account and billing records are kept for as long as your account is active, plus whatever period we're required to retain billing records for tax and accounting purposes after that.

You can delete your account at any time by contacting arkade523@gmail.com or from the dashboard. On request, we delete your workspace and its associated customer content promptly, and no later than 30 days out — with the exception of billing records we're legally required to keep, and backups, which age out on their normal cycle rather than being purged immediately.

7. Security

All traffic to pendnt.dev and api.pendnt.dev is encrypted in transit (TLS). API keys are never stored in full — only a salted hash, checked in constant time. Operator answer links are cryptographically signed (HMAC-SHA256) and single-purpose rather than session-based logins. Each workspace's data is isolated from every other workspace's. Full detail is on the Security page.

8. Cookies and page counts

The dashboard sets one session cookie to keep you signed in — that's it.

pendnt.dev (this marketing site) keeps first-party, cookieless page counts: for each page view, we record the date, the page path, and the hostname of the referring site if there was one (e.g. news.ycombinator.com) — nothing else. No cookies, no IP addresses, no user-agent strings, and no fingerprinting are used to produce these counts, and they're never shared with or run through a third party — the numbers live in our own database and nowhere else. We don't run third-party analytics, advertising pixels, or cross-site tracking of any kind on pendnt.dev or the dashboard.

9. Your rights (GDPR / CCPA and similar)

Depending on where you live, you may have the right to: access the personal data we hold about you; correct inaccurate data; delete it; export it in a portable format; restrict or object to certain processing; and not be discriminated against for exercising these rights. To exercise any of these, contact arkade523@gmail.com. For account and billing data we act as controller (see Controller and processor roles); for customer content you control, we'll support your own workspace's export/deletion, and we'll assist you in responding to a request from someone whose data is in your customer content, since we can't identify or act on it without you.

Our subprocessors (above) may process data outside your country, including in the United States; each is bound by its own data-protection commitments and contractual terms with us.

10. Children

pendnt isn't directed at children, and you must be 18 or older to create a workspace. We don't knowingly collect personal data from anyone under 18.

11. Changes to this policy

We may update this policy as the product evolves. Material changes will be noted in the changelog; continued use of pendnt after a change takes effect means you accept the update.

12. Contact

Questions, deletion requests, or a DPA request: arkade523@gmail.com. Data controller/operator of record: Kade Angell, 550 S 300 W, N337, Salt Lake City, UT 84101, USA.