LockstepsConnector Analytics

Privacy

Privacy and data

Each accepted event can store:

  • The scrubbed phrase, or nothing if scrubbing left too little text.
  • Tool name, platform, and timestamp.
  • Optional outcome, latency_ms, result_count, country, and connector_version, when those fields were valid.
  • A hash of session_id (conversation-scoped). Raw value discarded. Returned on ingest when minted server-side. Used to stitch FREE in-plugin conversions.

The API does not store IP addresses or user agents. It does not store the API key. Setup stores a hash of the key, plus the organization name, email, role, and connector slug for the account.

The shared view is opt-in. It does not name an organization, a connector, or a user. Identifiers are scrubbed before a phrase can appear. With the current defaults, a phrase can appear even if it has been seen once. Those minimums can be raised in configuration.

The legal pages are privacy and terms. They are draft text for review.

More

Questions: hi@locksteps.ai