CliqSpark Revenue Leakage Audit

Privacy

CliqSpark designed this diagnostic for aggregate business inputs and consent-based report delivery.

Data entered

The audit asks for business operating metrics and contact information for report delivery. It must not be used for claimant, medical, guest, payment, or confidential case data.

Browser drafts

Incomplete drafts may be saved in local browser storage with schema version, model version, run ID, and answers so the audit can be resumed.

Submission

When the report is unlocked, the app may transmit contact details, consent record, score summary, report payload, and UTM metadata to configured server systems.

Integrations

HighLevel, email, analytics, and Clarity are used only when configured. Contact information, raw financial inputs, private tokens, free text, and complete reports are excluded from analytics events.

Retention and deletion

Production retention is controlled by CliqSpark policy and Supabase report expiration settings. Deletion requests can be sent through CliqSpark contact channels.

Security

Private report tokens are generated with high entropy and stored only as hashes when Supabase is configured.