popper.pro
TermsSupportRequest access

Early access alpha

Privacy notice

Popper Pro is built around durable reasoning. That means the things you enter can persist so your work survives reloads, sign-in cycles, and deployment updates. This page explains the current alpha handling of account, workspace, and operational data.

What We Collect

  • Email address, alpha access status, sign-in/session records, and owner/admin audit events.
  • Workspace content you enter, including missions, thread messages, problems, conjectures, criticisms, outcomes, and related product operations.
  • Usage records for alpha cost controls, such as chat turns and product-operation posts.
  • Operational metadata such as browser/user-agent, IP-derived request metadata, error logs, and hosting/provider logs needed to run and protect the service.

How We Use It

  • To provide sign-in, alpha access, workspaces, durable reasoning history, and owner support.
  • To keep the product reliable, debug failures, prevent abuse, and manage model/provider cost during the alpha.
  • To improve Popper Pro by learning where the product, protocol, or interface is failing users.
  • To contact you about access approval, sign-in, support, and important alpha service issues.

Model Processing

Popper Pro routes model work through the app's configured `ProtocolAdapter` and model providers. Workspace content you submit may be sent to model infrastructure so Popper can classify input, ask follow-up questions, generate conjectures, criticize ideas, and produce replies.

Do not enter secrets, credentials, regulated health information, financial account data, or anything you are not allowed to share with model providers.

Who Processes Data

Current infrastructure includes hosting, database, email delivery, and model/provider services. These processors help operate the product; they are not granted owner-console access to your account.

Retention And Requests

Popper Pro is durable by design. Alpha workspace data, sessions, access records, usage records, and admin audit events may persist until they are no longer needed to operate, secure, support, or improve the product.

Self-serve export and deletion are not complete alpha workflows yet. For access, correction, export, or deletion requests, contact hello@popperlabs.com.

Security

The app uses magic-link sign-in, request-gated alpha access, workspace authorization boundaries, owner TOTP for admin access, durable Postgres storage in production, and operational guardrails. No alpha system is risk-free; report suspected security or privacy issues privately to hello@popperlabs.com.