How pilot information is handled

Information collected

The application collects the work email, company, service category, sales territory, checkout time, and policy version submitted on the pilot form. It records Stripe Checkout Session, Payment Intent, Payment Link, amount, currency, test/live mode, refund or dispute events, and pilot access dates. Stripe—not ConstructCue—collects and processes card details.

For email operations, ConstructCue records entitlement status, unsubscribe status, scheduled-delivery keys, provider message identifiers, send status, and limited error codes. Operational logs record source-refresh, payment, and delivery outcomes. Public project records and private source snapshots are stored separately from card data.

The site uses first-party engagement measurement to record a random tab-session identifier, a random page-visit identifier, page path, coarse browser and device category, country code supplied by the hosting provider, external referrer hostname, campaign labels when present, page views, scroll milestones, pricing-section views, key call-to-action clicks, sample downloads, source-link clicks, and checkout starts. The engagement table does not store names, email addresses, form contents, full referrer URLs, advertising identifiers, exact location, or full IP addresses.

How information is used

Information is used to measure whether visitors reach important product information, validate checkout, document consent, prevent duplicate or unauthorized access, provide the 14-day pilot, send source-linked digests, process refunds and disputes, honor suppression requests, secure the service, diagnose failures, and evaluate whether the founding pilot is useful.

Category and territory help evaluate pilot fit and future product design. They do not currently create a uniquely personalized feed for each buyer.

Service providers

Cloudflare hosts the application and data stores, Stripe hosts checkout and processes payment, and Resend transmits operational email. Like other hosting providers, Cloudflare receives normal request information, including IP address and user agent, to deliver and protect the site and may retain operational logs under its policies. ConstructCue does not place third-party advertising trackers or cross-site tracking cookies on the site and does not sell personal information for money or cross-context behavioral advertising.

Retention and suppression

First-party engagement records are automatically deleted after 90 days. The random session identifier is stored only for the browser-tab session, and measurement is disabled when the browser sends a recognized Do Not Track or Global Privacy Control signal. ConstructCue keeps payment, consent, entitlement, delivery, and security records as reasonably needed for the pilot, accounting, dispute handling, fraud prevention, and legal obligations. An email suppression record may be retained to make sure an opt-out remains effective. When information is no longer reasonably needed, ConstructCue may delete or de-identify it.

Choices and requests

Every pilot email includes an unsubscribe method. You may also ask to access, correct, or delete information, subject to records ConstructCue must retain, by contacting signals@constructcue.com. Send a privacy request from the address involved so ConstructCue can verify it without collecting unnecessary identity documents.

Security, location, and children

ConstructCue uses access controls, signed provider events, mode separation, bounded requests, suppression controls, and encrypted provider connections. No internet service can promise absolute security. The service is operated in the United States and is intended for business users, not children.

Changes and contact

Material changes will be posted here with a new effective date or version. Privacy questions can be sent to signals@constructcue.com.