When your team evaluates a new developer tool, the conversation rarely starts with the privacy policy. It starts with the demo, the pricing page, the GitHub integration, and whether the CLI actually works the first time. Privacy comes later — usually surfaced by a security-conscious engineer, a cautious engineering manager, or the procurement process that kicks in once the tool starts touching production infrastructure. Today, that conversation gets easier. PreviewDrop's /privacy page is live as of April 7, 2026, and it's built to answer the questions your team will eventually ask before they ever need to ask them.

The Trust Gap in Developer Tooling

There's a peculiar problem in the developer tooling market. Most tools in this space — ephemeral preview environments, CI/CD integrations, deployment orchestration platforms — are built by engineers for engineers. The technical quality is often excellent. The legal and compliance infrastructure lags years behind.

That gap creates friction at exactly the wrong moment: when a team is ready to scale adoption. An individual developer can spin up PreviewDrop and start using it in an afternoon. Getting it approved for a 20-person engineering team at a company with any kind of procurement process is a different matter. Legal needs to sign off. Security wants to know where data lives. The CTO wants to understand what access the GitHub OAuth integration actually grants.

The trust gap is real, and it costs adoption. Tools that close that gap early — by shipping clear privacy policies, terms of service, and security documentation before they're forced to by compliance requirements — earn the trust of teams that would otherwise wait months before expanding usage.

What the Policy Covers

PreviewDrop's privacy policy is organized into nine sections, each addressing a specific aspect of how the platform handles your data:

• Data collected: account info, GitHub integration details, usage data, technical identifiers
• How it's used: operating the service, product communications, usage analysis, billing — and explicitly NOT sold to advertisers or shared with unrelated third parties
• Data retention: data is not kept longer than necessary to operate the service
• Your rights: clear contact pathway to exercise data subject rights

Why Ephemeral Environments Have a Unique Data Question

Ephemeral preview environments have a particular data characteristic that distinguishes them from most SaaS tools: they're designed to be temporary. A preview environment spins up for a pull request, hosts a running version of your application, and then gets torn down when the PR is merged or closed.

What happens to your environment configuration when the environment is destroyed? If your preview environment touched environment variables — API keys, database credentials, service tokens — where do those values live in the platform's infrastructure, and for how long?

PreviewDrop's policy addresses this directly: the ephemerality of the environments extends to the data practices surrounding them.

A Practical Checklist for Teams Evaluating PreviewDrop

• Terms of Service at /terms — Effective April 7, 2026
• Privacy Policy at /privacy — Nine sections, structured for readability. Effective April 7, 2026
• GitHub OAuth Scope — Documented in the data collection section
• Contact pathway — Direct route to the PreviewDrop team for compliance questions

Head to previewdrop.com to create your account. The product is ready. The policy is live.