Privacy

This page is a working disclosure awaiting legal review. A contact request includes the name, business, contact details, topic, and context you submit. We record the request in the relationship Inbox, and a notification may be sent to our private Slack channel. Browser verification and short-lived retry records help us limit abuse and avoid duplicate requests. Sending a request does not book a meeting.

A visibility report request includes your website address if you have one, email, and explicit permission to deliver the report and contact you about that request. It does not subscribe you to marketing. We store this in our Railway Postgres relationship Inbox. Permitted campaign tags, source references, and the referring website's origin help us understand where the request came from; we discard referrer paths and query strings. Website addresses are normalized before storage and are not fetched by the intake form. Reports require review before delivery. You can optionally provide a phone number to request a human call about your report. We record that callback request separately from report-delivery permission. It does not authorize automated calls or text messages. Booking a meeting is a separate action.

If public-site analytics are configured, we ask before loading them. You can decline and still use the site. Analytics events record page paths and whether a contact form was started, an enquiry was stored, or a booking was confirmed. We do not put names, contact details, form text, or URL query parameters in those events.

You can calculate an estimate without sharing contact details. If you request an email copy, the address you provide is used for that report; a phone number is not required. Portal data belongs to your business and stays scoped to your account. Final retention and provider details remain pending review.

When you explicitly start the browser voice demo, your microphone audio is streamed to xAI so Grok Voice can transcribe it and respond in real time. Under xAI's default API policy, API inputs and outputs are encrypted at rest and retained for up to 30 days to audit suspected abuse or misuse, then automatically deleted. xAI says it does not use API inputs or outputs to train its models without explicit permission. Unlokd may review retained conversation history to operate and improve the service. You can read xAI's API security policy. A confirmed callback request sends only the contact details and concise qualification summary you approved to Unlokd's private Slack channel, not the full transcript.

Cloudflare Turnstile is used to verify that a real browser is starting a chat or a browser voice call, and Upstash Redis stores short-lived admission and deduplication records used to limit abuse. Turnstile runs in invisible mode, so nothing is shown to you and no puzzle is presented. Cloudflare describes what it processes in its Turnstile Privacy Addendum. The browser voice session ends after four minutes. Microphone access is requested only after you choose to start the live demo.

Questions, or a request to see, correct, or delete what we hold about you: use the contact form and one of the owners will pick it up.