Privacy notice

Last updated September 7, 2026

Who this notice covers

This notice covers visitors to warpix.io, early-access applicants, customer administrators and workspace members, and people whose information a customer submits through a Warpix workspace or widget.

For website, business-contact, account-administration, support, and service-security information, the Warpix provider identified in the applicable written order form acts as controller. For personal data that a customer submits to its workspace or collects through its widget, that customer generally acts as controller and Warpix acts as its processor or service provider. The customer decides why that data is collected and is responsible for its notices, permissions, lawful basis, and accuracy.

If you interact with a Warpix widget supplied by another company, contact that company first about its privacy practices or a rights request. Warpix will assist that customer as described in the Data Processing Addendum.

Information we handle

Website and early-access information

• Work email, company name, role, team size, workflow answers, and other information you choose to submit.
• Scheduling details you provide when booking a call and correspondence you send to us.
• With your permission, limited first-touch and latest-touch attribution, including the landing path, referring-page path, and selected campaign parameters.
• With your permission, pseudonymous page views and explicit interaction events with a random, session-scoped browser identifier. We do not send form values, names, email addresses, or company details to PostHog.

Optional analytics and attribution remain off until you select “Allow analytics.” Your choice is stored in the browser. You can change it through “Analytics choices” in the footer; choosing necessary-only removes Warpix's analytics and attribution identifiers from that browser and stops future events. Previously sent events remain subject to the provider's retention. An unfinished early-access form may be kept only in the current browser tab as functional draft recovery and is removed when the tab session ends or the form is submitted.

Customer service data

• Tenant, workspace, member, and role information, including stable identity-provider organization and subject identifiers.
• Customer-account and contact identifiers, names, email addresses, plans, segments, lifecycle and payment states, revenue and currency metadata, source, freshness, and tags.
• Feedback requests, votes, comments, labels, internal notes, merge history, roadmap items, releases, imports, audit history, and the relationships among them.
• Widget configuration, allowed origins, public board identifiers, assertion metadata, hashed short-lived session and replay identifiers, and user actions needed to operate and secure the service.

Revenue in Warpix is customer-supplied account or voter context. Warpix does not use it to charge a payment method and does not process payment-card data.

Technical and security information

We may process IP addresses, browser and device details, request paths, timestamps, request IDs, authentication and authorization results, rate-limit events, and service diagnostics. Application logs are designed not to contain request bodies, authorization headers, identity assertions, widget sessions, signing keys, or customer commercial context.

Why we use information

• Provide, authenticate, authorize, maintain, and secure the website and service.
• Collect, organize, search, deduplicate, and display customer feedback and its permitted account context.
• Support onboarding, answer requests, diagnose failures, recover service, and preserve necessary audit evidence.
• Evaluate early-access fit, conduct requested research, and improve Warpix using feedback and aggregated or de-identified operational information.
• Comply with law, enforce agreements, prevent abuse, and establish or defend legal claims.

Where Warpix acts as controller, processing is based as applicable on performing or preparing a contract, legitimate interests in operating and securing an early-stage service, your consent for optional website analytics and attribution, and legal obligations. You may withdraw analytics consent for future processing at any time. Where Warpix acts as processor, the customer's documented instructions provide the scope of processing.

Public and private information

A customer's widget can display feedback titles, descriptions, status, labels, public vote and comment counts, and public comments. After trusted identity succeeds, the session response may return the current end user's display name derived from that signed assertion for the widget's “Submitting as” notice. Public board, request, vote, and comment responses do not include private account evidence, revenue, payment status, plans, segments, tags, provenance, internal notes, import audits, or private roadmap or release evidence.

Sharing and subprocessors

We disclose information only to people who need it to operate Warpix, to providers that perform a documented service for us, when a customer directs us, or when law requires it. We do not sell personal data or share it for cross-context behavioral advertising. Our current provider list, purposes, and locations are published on the Subprocessors page.

Early-access forms are processed by Formspark and protected by Cloudflare Turnstile. Calendly processes details you provide when booking a call. PostHog EU Cloud receives the limited website analytics described above. These marketing services do not receive Warpix workspace content through the product.

International processing

Warpix's current primary application and database server is in the United States. Static website and application assets may be delivered through global edge infrastructure, and other providers may process information in the locations disclosed in their terms. Before processing data subject to a restricted-transfer regime, Warpix and the customer must document an applicable transfer mechanism, such as the European Commission Standard Contractual Clauses or the UK Addendum, where required. The Warpix DPA does not by itself complete those transfer instruments.

Retention, export, and deletion

• Active service: customer content is retained while the applicable service agreement remains active, unless the customer requests earlier deletion and the agreement or law permits it.
• Requests and termination: Warpix does not yet have self-service or a general full-workspace export or purge tool. Before activation, the customer's order form must state the operator-assisted export scope and format, post-termination request window, deletion or de-identification method, completion target, and any audit fields that must remain. Access ends on termination and ordinary use of retained content stops.
• Backups: current database backups are local, created weekly, and retained on a 14-day rotation. Deleted information may remain until the applicable backup expires. When an open, documented deletion request exists and a backup is restored, the operator checks the protected request record and re-applies the agreed procedure before re-opening the affected service.
• Security and legal records: limited records may be retained longer where reasonably necessary to investigate abuse, maintain transaction or audit integrity, meet legal obligations, or establish and defend claims. Identifying fields are minimized when full retention is unnecessary.
• Website and support: early-access and support information is kept only while it remains reasonably useful for the requested relationship, support, security, or legal purpose. We review early-access records at least annually and delete information that is no longer needed.

An owner or other verified authorized contact can request access, correction, a scope-limited machine-readable export, or deletion at hello@warpix.io. We verify authority and agree the available records, format, secure delivery, deletion method, lawful exceptions, and timing for that request or in the order form. We will not activate processing that requires an export or deletion outcome we cannot safely perform within the applicable legal deadline.

Security

Warpix uses encrypted transport, tenant and workspace isolation, role-based authorization, short-lived credentials, one-time signed widget assertions, hashed widget sessions, origin allowlists, bounded inputs, rate limits, privacy-aware logs, dependency and source scanning, tested migrations, and controlled deployments. No service can guarantee absolute security. Report suspected exposure with the subject “URGENT SECURITY” to hello@warpix.io, without including tokens, assertions, private keys, or sensitive customer content.

Prohibited sensitive data and children

The early-access service is intended for ordinary B2B product-feedback data, not children or consumers acting in a personal capacity. Customers must not submit payment-card numbers, account passwords, signing keys, government identifiers, health information, biometric data, criminal-history data, special-category personal data, or other regulated or unnecessary sensitive information unless Warpix has agreed in writing to appropriate safeguards first.

Your choices and rights

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a portable copy of personal data, or to complain to a regulator. Contact the customer that supplied the widget for customer-controlled data. You may also contact hello@warpix.io; we will either handle the request as controller or route it securely to the applicable customer.

Changes and contact

We will update the date above when this notice changes. If a material change affects an active customer's service data, we will provide notice through the agreed customer contact where reasonably practicable. Privacy, support, and security questions can be sent to hello@warpix.io. The legal identity and business address of the applicable Warpix provider are stated in the customer's written order form before activation.