Security and data handling

How Pumpkin handles your code, model requests, and account data today, and which outside services pumpkin.club uses. This page describes how the service is built; it is not a contract. The privacy policy and terms are the policies that govern your account. The privacy policy also describes organization identity, audit logs, budgets, and published canvases.

Where your code and model requests go

• The editor and its agent run on your workspace machine: your computer, or a host you open over SSH or WSL. Own-key model requests do not send your files to pumpkin.club; optional hosted services below receive the content you choose to send or publish.
• With your own provider keys, model requests go directly from that machine to the provider you chose, with no Pumpkin inference relay. The provider's terms and data policy apply to what you send it. Model API keys are kept in the operating system's protected secret storage.
• With a supported Codex or Claude Code subscription, requests go to that provider under your plan's terms.
• The local model runs on your computer. Once it is installed, its inference does not use a cloud model endpoint.
• pumpkin.club itself holds your account (email, name, hashed password), team membership and invitations, billing state from Stripe, and hashed sign-in tokens that let the editor confirm your license.

Optional services that send data elsewhere

Each of these is off until you use it.

• Pumpkin credits. Fireworks models on Pumpkin's key send your requests through pumpkin.club to Fireworks. pumpkin.club records the tokens and cost of each call to bill your credit balance.
• Remote access. The pumpkin.club broker stores machine and device identifiers, public identity keys, approval state, and approximate online status. Prompts, replies, and commands travel only over encrypted WebRTC connections. The one exception is optional push notices about agent questions: your computer encrypts each notice, and pumpkin.club forwards it to the browser's push service without keys to read it. When a direct connection is not possible, Cloudflare's TURN service relays the encrypted traffic and cannot read it.
• Slack. If you connect the Pumpkin Slack app, pumpkin.club relays your Slack mentions and messages to your connected machines and posts the agent's progress back to the thread. The relay keeps no message tables.
• Usage reports and logging. Shared usage logs go to storage you or your organization configure (Amazon S3, Cloudflare R2, Google Cloud Storage, or Azure). Storage credentials saved on pumpkin.club for reports are encrypted with AES-256-GCM.
• Canvas sharing. When you publish a canvas, pumpkin.club stores its title and its HTML, compressed, and serves it at a /c/ link. A link share can be opened by anyone who has the link; an organization share only by signed-in members of your business organization. Shared pages are marked not to be indexed by search engines. Updating a share replaces the stored HTML. Revoking a share deletes its HTML and the link stops working; a record of the share id, title, and owner stays so the id is never reused.
• Feedback. What you submit from the editor, with any attachments, is stored by pumpkin.club so we can read it.
• Sync and connected tools. Multiple-computer sync and the tools you connect follow the storage and sharing settings you choose.

Subprocessors

These are the outside services the pumpkin.club code uses today and what each one handles. The privacy policy names Stripe, Amazon Web Services, Cloudflare, Google, GitHub, Fireworks, Slack, and organization-configured identity and storage services. Fireworks and Slack receive data only when you use Pumpkin credits or the Slack app. Model providers you reach with your own keys or subscriptions are your own vendors, not Pumpkin's.

• Amazon Web Services (United States, us-east-1): hosts the site and its database, sends and receives our email, and stores feedback attachments.
• Stripe: payments, sales tax, invoices, and refunds. Card numbers go to Stripe and never reach pumpkin.club.
• Google: Sign in with Google when you choose it, and Google Ads and Analytics measurement on public pages as described in the privacy policy.
• Fireworks: model inference for Pumpkin credits.
• Cloudflare: the TURN relay for Remote access.
• Slack: the Pumpkin Slack app, when you connect it.
• GitHub: hosts the editor downloads.

How data is protected

• pumpkin.club serves only HTTPS. Plain HTTP requests are redirected, and every response carries HTTP Strict Transport Security.
• Passwords are stored as bcrypt hashes. Editor sign-in tokens are stored as hashes, and revoking a license deletes that person's tokens at once.
• Feedback attachments sit in a private Amazon S3 bucket with public access blocked and server-side encryption.
• The Remote broker has no pairing root keys and cannot recover them, and session content does not pass through it, apart from encrypted optional question notices it cannot read.
• The privacy policy states that server logs are kept for up to 90 days. Email us to delete your account.

Certifications

Pumpkin does not hold SOC 2, ISO 27001, HIPAA, or other security certifications today.

Report a security issue

Email support@pumpkin.club with "Security" in the subject. Include what you found and how to reproduce it. Please do not test against other people's accounts or data.

Data processing agreements

To request a data processing agreement, email support@pumpkin.club with your company name and what you need. We do not publish a standard agreement on this site.