Data Transparency

BackNova PII-0 Architecture — What we collect, what we don't, and how to verify.

✓ PII-0 Compliant

Zero Personally Identifiable Information

BackNova is designed from the ground up to make decisions without ever seeing, storing, or processing personal data. All identifying information is hashed client-side before transmission.

What We Collect

BackNova collects 35 behavioral and technical signals to evaluate lead quality. None of these are personally identifiable.

Behavioral Signals (15)

SignalDescriptionPII?
time_on_site_secSeconds spent on page✓ No
scroll_depth_pctHow far user scrolled (%)✓ No
page_viewsNumber of pages viewed✓ No
mouse_distanceTotal mouse movement (px)✓ No
clicksNumber of clicks✓ No
rage_clicksFrustration click patterns✓ No
form_completion_secTime to fill form✓ No
form_changes_countForm field edits✓ No
engagedUser engagement flag✓ No
returning_visitorHas visited before✓ No
fast_scrollBot-like scroll pattern✓ No
keystrokesKeyboard activity count✓ No
paste_eventsCopy-paste usage✓ No
tab_switchesTab focus changes✓ No
touch_eventsMobile touch count✓ No

Technical Signals (10)

SignalDescriptionPII?
user_agentBrowser identification string✓ No
browserBrowser name (Chrome, Firefox)✓ No
device_typedesktop / mobile / tablet✓ No
screen_resolutionScreen size (1920x1080)✓ No
viewport_sizeBrowser window size✓ No
languageBrowser language (en-US)✓ No
timezoneTimezone (Europe/London)✓ No
platformOS (Windows, macOS)✓ No
cookies_enabledCookie support flag✓ No
do_not_trackDNT header status✓ No

Traffic Source Signals (7)

SignalDescriptionPII?
utm_sourceTraffic source (google, facebook)✓ No
utm_mediumTraffic medium (cpc, email)✓ No
utm_campaignCampaign name✓ No
utm_termSearch keyword✓ No
utm_contentAd content variant✓ No
referrerPrevious page URL✓ No
urlCurrent page URL✓ No

Hashed Identifiers (3)

SignalDescriptionPII?
session_idRandom session identifier✓ No
browser_fingerprintSHA-256 hash of browser config✓ No
fingerprint_emailSHA-256 hash of email✓ No*

* Email is hashed client-side using SHA-256 before transmission. The plain text email never leaves the browser.

What We NEVER Collect

Plain text email addresses
Plain text phone numbers
Names (first, last, full)
Physical addresses
Credit card or payment information
Social security numbers
Government IDs
Passwords or credentials
Any other personally identifiable information

How We Protect Data

1. Client-Side Hashing

When an email or phone is provided, it's hashed using SHA-256 in the browser before being sent to our servers. We never see the original value.

// What happens in your browser: const email = "user@example.com"; const hash = SHA256(email); // → "b4c9a289323b21a01c3e940f150eb9b8c542587f1abfd8f0e1cc1ffc5e475514" // Only the hash is sent to BackNova // The original email NEVER leaves your browser

2. Built-in PII Validator

Our SDK includes a PII-0 validator that scans all data before transmission. If any potential PII is detected, it's automatically blocked.

// SDK automatically blocks: // - Email patterns (xxx@xxx.xxx) // - Phone patterns (10+ digits) // - Name patterns // - Credit card patterns // - SSN patterns

3. Open Source SDK

Our SDK source code is publicly available. You can inspect exactly what data is collected and how it's processed.

View SDK Source Code →

Verify Yourself

Open your browser's Developer Tools (F12) → Network tab → Filter by "backnova" or "decision" to see exactly what data is being sent.

Real-time Data Inspector

If you have BackNova SDK installed, run this in your browser console:

BackNova.getPII0Report()

This will show you exactly what data is collected and confirm PII-0 compliance.

Compliance

Third-Party Audits

We welcome independent security audits of our SDK and infrastructure. Contact us on Telegram @backnova for audit requests.