Privacy & Data
A plain-language account of what is captured, what is never captured, and the controls that enforce it. Everything here reflects how the software actually behaves — not a statement of intent.
Last updated: August 2026. Material changes will be reflected here.
01 — What we capture
ReCapture captures only the fields it identifies as contact information: name, email address, and phone number — along with non-content metadata like time spent on the form, device type, and page URL.
A field's value is read after the visitor finishes entering it. Captured details are transmitted when a form is abandoned — on tab close, page navigation, exit-intent, or a periodic check while the form sits incomplete. If a visitor never enters a valid email or phone, no lead is created and nothing is sent.
02 — What we never capture
ReCapture does not log individual keystrokes and does not record or replay browsing sessions. It reads completed contact fields — it is not watching a live stream of typing.
Free-text fields are never captured. Anything typed into a message box, a "tell us about your situation" field, or a "describe your legal matter" or symptom field is never stored, never transmitted, and never forwarded to any alert, CRM, or webhook.
Sensitive fields — passwords, Social Security numbers, credit card numbers, CVV codes and similar — are hard-excluded at the code level and blocked before anything is read, even if a form happens to include them.
03 — Consent & geography
Visitors in the EU, UK, and Switzerland are not tracked at all. The tracker detects location and blocks capture for those regions, and fails closed — if location cannot be confirmed, it does not capture.
On sites running a recognized consent platform (OneTrust, Cookiebot, CookieYes), ReCapture captures only when the visitor has granted consent. And it runs only on domains a customer has explicitly authorized in their account.
04 — Opt-out & suppression
Once a phone number or email is on the do-not-contact list, all future recovery actions for that person — email, SMS, and AI voice callback — are suppressed automatically before they fire, across every channel.
05 — If you deploy ReCapture
We recommend adding a short disclosure near your forms so visitors know their contact details may be saved for follow-up — for example: "We may save the contact information you enter so we can follow up if you don't complete this form. See our Privacy Policy."
We also recommend reflecting form-abandonment recovery in your own privacy policy. Ready-to-paste language is available at /legal/client-privacy-template.
06 — One honest caveat
This page is not legal advice. Privacy rules vary by jurisdiction and industry. What we can tell you plainly is how the technology behaves and the controls it gives you — geo-blocking, consent-platform respect, sensitive-field exclusion, contact-fields-only capture, authorized domains, and opt-out. How you deploy and disclose it is a decision we help you make responsibly but do not make for you.
Questions? Get in touch, or see our full Trust & Compliance page.