Clear HandshakeAccount preparation for regional fiber teams Discuss pilot fit A 30-minute founder conversation to confirm account group, team, and fit. Do not include customer records, account data, credentials, pricing, or confidential provider information in the first email.

Privacy

A static public site now. Written handling rules before any real pilot.

The public website does not accept provider data or visitor submissions. A real pilot begins only under a separate written agreement that defines approved information, people, tools, access, retention, deletion, and human review.

Last updated August 9, 2026.

Public website and pilot boundaries

Public website today

Information-only and visitor initiated.

  • No public account or login.
  • No public data upload.
  • Clear Handshake does not intentionally add first-party analytics, advertising trackers, cookies, browser storage, or a receiving API.
  • Mailto contact opens the visitor’s email provider.

Real pilot

A separate written agreement controls.

  • Approved account group and fields.
  • Named people and access.
  • Approved tools and permitted uses.
  • Retention, deletion, and correction terms.
  • Human review and authority boundaries.
On this page

Current behavior

The public site does not receive visitor or provider data.

  • No public account, login, data upload, form receiver, or receiving API exists.
  • Clear Handshake does not intentionally add first-party analytics, advertising trackers, cookies, browser storage, or a receiving API.
  • The hosting provider may process ordinary technical logs or inject hosting-level analytics under its own configuration and terms.
  • The fictional workflow demo is session-only. It does not transmit or save visitor changes.
  • Contact links use mailto. The visitor chooses whether to send a message through their email provider.
  • External links are governed by the destination’s terms.
  • Release blocker: disable Cloudflare Insights before release if the desired claim is “No analytics.”

Before a real pilot

Handling terms come before account information.

The provider and Clear Handshake would sign a separate written agreement before receiving or preparing real account information.

Approved information
Specific account fields, sources, territory or account group, product focus, and permitted uses.
People and access
The manager, participating sellers, Clear Handshake reviewer, serviceability owner, and their access responsibilities.
Approved tools
Every system allowed to process pilot information and the bounded purpose for that processing.
Retention and deletion
How long information is kept, when it is removed, and how access ends.
Corrections
How provider, seller, customer, and technical corrections preserve the prior record.
Human review
Who reviews the preparation and which decisions remain with the provider, seller, customer, and Provider Engineering.

Authority

Preparation never changes the source of truth.

Provider systems
Provider systems remain authoritative for account and service records.
Provider Engineering
Owns address, serviceability, availability, construction feasibility, and economics.
Clear Handshake
Clear Handshake prepares and human-reviews the work.
Seller
The seller controls wording, customer contact, and whether and how to act.
Customer
The customer confirms or corrects customer reality.
Transmission
No autonomous outreach, automatic writeback, or automatic engineering request.

Email boundary

Do not send sensitive information.

A 30-minute founder conversation to confirm account group, team, and fit.

Do not include customer records, account data, credentials, pricing, or confidential provider information in the first email.

Discuss pilot fit

Privacy questions

. Do not include sensitive information.