Docs menu
Reference

Data sent and retention

What InlineShield receives with each sign-up, what it keeps and for how long. InlineShield does no device fingerprinting.

Last updated

What /verify receives

The fields your server sends:

FieldTypeRequiredDescription
emailstringyesThe address the player signed up with.at least 1 character
ipstringnoThe player's IP address (IPv4 or IPv6). Without it, the IP of the calling connection is used, which is your server's. Anything that is not an IP address gets 400 INVALID_IP.
userAgentstringnoThe player's browser User-Agent. Only this field is read; the request's own User-Agent header (your HTTP client) is ignored. Without it the User-Agent counts as empty.
usernamestringnoThe username the player chose, if any.
clientDwellMsnumbernoMilliseconds the sign-up form was open before it was submitted, if you measure it. Not measured means unknown, never a fast submission.
honeypotstringnoThe value of a hidden form field that people leave empty. A non-empty value is a bot signal.

What /check receives

The fields the browser script sends; the IP address and User-Agent come from the browser's request:

FieldTypeRequiredDescription
siteKeystringyesYour site key (bs_site_…, or bs_site_test_… for test mode).
emailstringyesat least 1 character
usernamestringno
clientDwellMsnumbernoMilliseconds the form was open before it was submitted.
honeypotstringnoThe value of a hidden field people leave empty.
signalsobjectnoBrowser signals collected by inlineshield.js. Invalid values are ignored.
signals.webdriverbooleanno
signals.tzstringnoIANA time zone, e.g. Europe/Berlin.at most 64 characters
signals.langsarray of stringnoUp to 5 browser languages are kept.
signals.automationHintsarray of stringnoValues: webdriver, cdc_props, no_languages, headless_ua_ch, phantom, nightmare, selenium_props

What is kept, and for how long

  • Each screening is recorded for your account: the email, IP address, User-Agent and username it was given, and the result. You see them in the console's History.
  • After 180 days (the default retention period), the raw email, username, IP address and User-Agent of a screening are blanked; the result stays. The same applies to the stored webhook payloads.
  • Outcome labels, and the per-screening data used for learning, are removed after 13 months.
  • Test screenings are kept and blanked the same way.

What leaves InlineShield

  • registration.allowed and registration.blocked webhooks contain the player's email and IP address. signup.approved and signup.rejected contain neither.

Policies

The Privacy Policy and the Data Processing Addendum are the binding terms.