Private static draft. noindex, nofollow. No public launch, no live form, no tracking, and no data is sent.
CallLeak Radar private draft

CallLeak Radar data boundaries

This page draft makes the data path explicit before any report-request flow goes live. It is a trust page, not legal advice.

Boundary principle

The first CallLeak Audit preview should use public business information and minimum owner-provided business details only. Do not collect private customer data just to test demand.

No tracking, no ads, no live form, no third-party processor, and no data storage are active in the private draft.

Allowed first-pass inputs after approval

  • Business name.
  • Website or Google Business Profile URL.
  • City or service area.
  • Trade and requester role.
  • Contact email.
  • Optional missed-call estimate and business-level concern.

Forbidden first-pass inputs

  • Customer names or homeowner phone numbers.
  • Call recordings, transcripts, raw call logs, or voicemail exports.
  • Payment data, CRM exports, passwords, API keys, or credentials.
  • Any information the requester is not authorized to share.

Retention default

Use the shortest practical retention window for the preview request and delete test submissions after the learning value is extracted. A live retention rule requires Yuri approval before activation.

Before live use

  1. Approve public identity and contact inbox or processor.
  2. Approve privacy copy, minimum fields, consent copy, and retention rule.
  3. Test that submissions work without collecting forbidden data.
  4. Keep paid traffic blocked until tracking and privacy are approved.