Skip to content
SPARKX / SECURITY

Data and security

Understand how data flows and what to confirm before a trial. This guide distinguishes the public website from the signed-in analytics product.

Public demo

The demo uses predefined synthetic data and does not connect advertising accounts. The preparation assistant reads CSV files in your browser; it does not upload their contents.

Access requests

Submitting a form sends your name, email, company and request to our website endpoint for follow-up and trial coordination. A receipt is shown only after storage succeeds.

Optional analytics

Language and theme settings stay in your browser. Microsoft Clarity loads only after analytics consent; form areas and local file-check results are masked.

Product access and organization isolation

The product uses authentication and organization-level access controls, with backend permission checks and database row-level security. Effective protection depends on deployment configuration, migrations and verification.

Data used for AI-assisted analysis

Signed-in AI features may send relevant model context to the configured AI provider. Confirm transmitted fields, processing region, provider terms and retention settings with the team before a trial. The public sample demo does not call an AI service.

Confirm enterprise requirements

SSO, dedicated hosting, retention, backup and recovery, audit exports and SLAs must be confirmed for your environment. This page does not claim SOC 2 or ISO 27001 certification.

Data requests and questions

To access, correct or delete an access request, contact the team with the email used for submission. Do not include passwords, ad-account keys or raw customer records in the contact form.

Interpret model outputs alongside data quality, assumptions and validation. Predictive accuracy alone does not establish causal incrementality.
Discuss your data requirements →