Privacy
What form tracking stores and does not store, how it handles Do Not Track and Global Privacy Control, and which code runs under your own consent rules.
This page explains what form tracking collects. For site owners, it also explains which code you must place under your own consent rules. For all other data, see Data privacy.
What the Forms tag does on the page
Form tracking uses its own script, the Forms tag (forms.js). It does not need Web Analytics, and it makes no page view, session or visitor. On every page that has the tag, VitalSentinel stores form events for the forms on the page, also for forms that you do not track. It uses them to suggest forms. There is no setting to turn form tracking off. To stop it on a site, remove the tag.
- No storage. Form tracking writes nothing to cookies,
localStorage,sessionStorageor IndexedDB. - No device details. The tag sends no browser or device details. The only browser setting that it reads is the Do Not Track or Global Privacy Control signal.
- No field values. The script never reads the value of a field.
- No message text. After a submit or a click on a button, the script tests a success or error message and the text around the form. It does this in the browser only, and it holds the text in memory during this check. It never stores or sends the text.
VitalSentinel never submits a form.
What VitalSentinel stores
A stored form event can hold these items:
- The domain
- The form key
- The event: shown, success or fail
- The source: the script or your code snippet
- The page path, with no query string
- The form type and the form platform
- The field count and the kinds of field, for example email or message
- The time
VitalSentinel redacts text in the path that looks like an email address, and segments that look like an ID. For example, a path with an ID shows as /jobs/:uuid/apply. All such pages count as one page.
The form key is a hash. The raw id, name and action values of the form do not leave the browser.
What VitalSentinel does not store
A stored form event has none of these items:
- An IP address or a User-Agent
- A location
- A field value
- Message text
- A visitor, session or device identifier
The browser still sends the IP address and the User-Agent with each request, as with any request. VitalSentinel does not store them with a form event. To limit how many form events one sender can send, VitalSentinel makes a keyed hash of the IP address and keeps it for 70 seconds.
Do Not Track and Global Privacy Control
The Forms tag honors Do Not Track and Global Privacy Control. While a signal is in force, the tag runs no form tracking. The tag uses the signal that the browser shows it. If an extension or a proxy adds only the header, form tracking still runs.
VitalSentinelForms.grantConsent()lifts the signal, so form tracking runs. The tag stores nothing, so the grant applies only to the current page. Your consent tool must call it on each page load.VitalSentinelForms.revokeConsent()restores the signal, so form tracking stops.VitalSentinelForms.optOut()stops form tracking for the current page load.VitalSentinelForms.optIn()starts it again.
Form tracking does not depend on a consent level. If the browser sends no signal, revokeConsent() does not stop form tracking. To stop it for a visitor, call optOut() on each page load.
These rules also cover a Page attribute, because the tag makes that call.
See Do Not Track and Global Privacy Control and Consent banner and opt-out.
Code that runs outside the script
The Tracking pixel, JavaScript and Webhook calls run outside the Forms tag. They do not check Do Not Track, Global Privacy Control, optOut() or the consent level. You place these calls, so place them under your own consent rules.
- The Tracking pixel and the JavaScript line run in the browser of the visitor. The call has the tracking ID, the token of the form and, for a fail,
outcome=fail. The browser also sends the IP address and the User-Agent of the visitor, as with any request. - The pixel sends no referrer. The JavaScript line sends no referrer and no cookies.
- The Webhook runs on your server or in your form tool, not in the browser of the visitor.
How long VitalSentinel keeps the counts
Your plan sets how long VitalSentinel keeps the counts. VitalSentinel stores the counts by the hour, with the page path and the minute of the last event in that hour. Single form events are kept for up to 30 days, or for your plan's period if that is shorter. See Plans and limits.
Delete history in Page Monitoring also removes the form data of that page. Rows with a shared redacted path, such as /jobs/:uuid/apply, stay until your plan's history ends. Delete history cannot remove the form data of a page that the crawler never reached, for example a page behind a login. That data stays until your plan's history ends or you delete the domain. Past alerts keep the page paths that they named.
If you delete a domain or your account, VitalSentinel deletes its form data. See When you delete a domain or your account.
Related
- Data privacy - what VitalSentinel collects
- Tracking scripts - install and check the scripts
- How to add the code - where the code goes
- Theo and privacy - what Theo sends to its AI provider
Troubleshooting
Fix common Form Monitoring problems - a form on Waiting, zero Submitted, Not available, pages with IDs in the URL, consent tools and plan limits.
Overview
The Google Search Console module shows your clicks, impressions, CTR and position in Google Search, with top queries, pages, countries and devices.