Privacy Policy

1. Scope

Pompeii Labs, Inc. ("Pompeii Labs," "we," "our," or "us") operates workbenches.dev, the Workbenches registry, dashboard, cloud runs, API, MCP server, and related services (the "Service"). This Privacy Policy describes how we collect, use, disclose, and retain personal information when you use the Service, including through the wb CLI, or communicate with us. It does not govern third-party services that have their own privacy policies.

2. Information We Collect

Account and profile information

We collect details such as your name, email address, profile image, organization membership, API keys, account settings, and authentication identifiers. If you sign in with Google, we receive the profile and account information authorized through the OAuth flow, such as your Google account identifier, name, email address, and profile image. We do not receive your Google password.

Content and integration data

We collect Workbench packages and images, instructions, messages, repository content, source code, files, run events, outcomes, artifacts, feedback, and other content you submit or generate. Connected repositories and integrations may provide metadata, content, OAuth tokens, installation identifiers, permissions, or other data within the access you authorize. Secrets you store are encrypted with a cloud key management service, made available only to the runs that need them, and redacted from stored run events and outcomes.

Billing and usage information

We collect plan, subscription, invoice, payment status, spend limits, metering, sandbox usage, run history, and transaction history. Our payment provider processes payment-card and bank information; we do not need to store complete payment-card numbers. Model usage is billed by your model provider, not by us.

CLI usage counts

The wb CLI reports anonymous save and run counts for public registry Workbenches published by organizations you are not signed in to. It does not report Workbenches from your own organizations, local paths, GitHub sources, or private versions. A one-time notice appears before the first report. Set DO_NOT_TRACK=1 to disable reporting entirely.

Device, log, and communication data

We collect IP address, browser and device information, timestamps, feature activity, request and error logs, performance data, authentication events, and security signals. We also collect contact requests, support requests, feedback, and other communications you send us.

3. How We Use Information

We use information to:

• authenticate users and operate accounts, organizations, the registry, and cloud runs;
• execute runs, deliver outcomes, and provide requested tools and integrations;
• review, list, and show usage for published Workbenches;
• process payments and enforce paid, free, rate, spend, and usage limits;
• maintain, debug, analyze, support, and improve the Service;
• send transactional, security, support, and permitted product communications;
• detect, investigate, prevent, and respond to fraud, abuse, credential theft, security incidents, unlawful conduct, and violations of our terms; and
• comply with law, enforce agreements, and protect rights, safety, and property.

4. Cloud Runs and Sandboxes

To perform requested work, cloud runs may process your instructions, repository content, files, outputs, configured tools, and permitted secrets in isolated third-party sandbox environments. Sandbox providers process this data to run the code and tools a Workbench declares and return results. Run events and outcomes are stored so you can follow, resume, and review a run. Isolation is a security measure, not a guarantee that code or data cannot cause harm.

A run may push branches and open pull requests in repositories you connect, where they are visible to anyone with access to that repository. Do not include credentials or sensitive data in code, output, or Workbench packages unless needed and appropriately protected.

5. AI Routing and Model Providers

We do not provide model inference. Runs send model requests using the keys and accounts you connect, such as your OpenRouter account, which may route them to the underlying model provider selected by you, the Workbench, or your organization. The request and response, including content placed in model context, can be processed by OpenRouter and the routed provider under their own terms and privacy practices.

Provider logging, retention, and use of data for training or service improvement differ by model, provider, and route. We do not represent that every available route provides zero retention or a universal no-training commitment. Before submitting highly sensitive data, assess the settings and terms relevant to the provider and model you use. See OpenRouter's Privacy Policy and its privacy and provider-logging documentation.

6. When We Disclose Information

We may disclose information in the following circumstances:

• Within the Service: Organization content is available to authorized organization members. Public Workbenches, their publisher, versions, and usage counts are available to anyone.
• Processors: Vendors process data for authentication, cloud hosting and databases, object storage, key management, payments, sandbox infrastructure, analytics, and communications.
• Integrations you authorize: We exchange information with repository hosts, model providers, OAuth providers, and other connected services according to your configuration and their terms.
• Legal, safety, and abuse matters: We may disclose information when we reasonably believe it is required by law or needed to enforce our terms, investigate abuse, respond to security incidents, prevent harm, or protect Pompeii Labs, users, providers, third parties, or the public.
• Business transactions: Information may be disclosed in connection with financing, due diligence, a merger, acquisition, reorganization, bankruptcy, or sale of assets.
• At your direction: We disclose information when you request or consent to it.

This list describes processor categories and is not a complete named subprocessor list or a promise that every category is used for every account. We do not sell personal information for money.

7. Retention, Deletion, and Export Requests

We retain information while an account is active and as reasonably needed to provide the Service, maintain security and continuity, resolve disputes, enforce agreements, and meet legal obligations. Retention periods vary by data type, organization settings, backup cycle, provider behavior, and legal or security need. Deletion may not be immediate, and residual copies may remain in backups, logs, provider systems, or records we must preserve. Content shared with other organization members may remain available to that organization. Published Workbench versions are immutable and may remain available to people who already installed them.

You may request account deletion by emailing hello@pompeiilabs.com. A terminated account holder may also request export of Workbench versions and run records they own or are authorized to receive. Eligibility, identity and authority verification, available format, timing, retention limits, and technical feasibility apply. We may deny, restrict, or delay a request for legal, security, abuse-prevention, investigation, provider, or third-party rights reasons.

8. Security and Abuse Monitoring

We use technical and organizational safeguards designed to protect information. We may monitor account, network, tool, repository, registry, and sandbox activity; inspect relevant logs and content; restrict access; and preserve evidence to detect or investigate abuse, credential exfiltration, security bypasses, fraud, and threats. No security measure is perfect, and we cannot guarantee absolute security.

9. International Processing and Availability

We and our providers may process information in the United States and other countries whose data-protection laws differ from those where you live. Data may move between regions as needed to provide the Service, execute code, or use an integration. Specific features, processors, or the Service itself may be unavailable or restricted in certain countries or regions for legal, sanctions, provider, security, or operational reasons.

10. Cookies and Analytics

We use cookies and similar technologies to authenticate you, maintain sessions, remember preferences, and secure the Service. We measure site usage with Plausible, which does not use cookies and reports aggregate statistics. Browser controls may let you restrict cookies, but essential features may then stop working.

11. Your Choices and Rights

You can manage certain account, organization, repository, integration, secret, and communication settings in the Service or through the relevant third party. You can revoke an OAuth integration or delete a secret, but this does not delete information already processed or retained for the purposes described in this policy.

Depending on your location, you may have rights to access, correct, delete, or receive a copy of personal information; object to or restrict processing; withdraw consent where applicable; or appeal a denied request. To submit a request, email hello@pompeiilabs.com. We may verify your identity and authority, and legal exceptions may apply.

12. Children's Privacy

The Service is not directed to children under 16, and we do not knowingly collect their personal information. If you believe a child has provided personal information, contact us so we can investigate and take appropriate action.

13. Changes to This Policy

We may update this Privacy Policy by posting a revised version and changing the effective date. We will provide additional notice when required by law. Your continued use of the Service after an update is subject to the revised policy.

14. Contact