Privacy policy
Draft, not yet in force.
Two kinds of data
Visitors of sites that use Wayhint. The guide widget runs on our customers’ websites. When a visitor asks for help, the widget sends the visitor’s goal, the page path without the query string, the page title and headings, and a list of visible interactive elements with their labels. It never sends input values. Emails and long numbers in labels are masked in the browser before sending. For these visitors, our customer is the controller and Wayhint acts as a processor.
People who use this website and our dashboard. Account details you give us (name, email, company), billing information handled by our payment provider, and basic server logs.
Customer accounts (optional)
If one of our customers turns on account tracking for their site, the widget also sends the identifier of their own customer account (an opaque id they choose, such as a workspace or company id) and an optional display name, together with a one-way hash of their user id. We use these only to show that customer per-account usage of the guide: how many distinct users asked something, what they asked, and what went to support. We refuse identifiers that look like email addresses, bank or phone numbers, or secrets. The account identifier and name are never sent to the AI model. As for the rest of the guide data, our customer is the controller and Wayhint the processor. An account’s conversations are deleted with the rest of the analytics after 180 days, and the account record and its checklist progress once the account hasn’t been seen for 180 days. Everything is deleted at once when the site is deleted, and a single account’s data at once on our customer’s request. Where an account belongs to a single person, such as a sole trader, we treat this data as pseudonymous personal data.
Support handoff
When a visitor clicks Contact support, the widget builds a short summary of what the guide tried (the goal, how it ended, the steps, the page path, any comment) in the visitor’s browser, and passes it from the browser to the support tool on our customer’s page (such as Intercom, Zendesk or Crisp), WhatsApp, email or their support page. It does not go through our servers, and we don’t store it. Form values are never in it, and emails and long numbers in the summary are masked; in some chat tools the visitor’s goal is placed in the message as they typed it, where they can edit it before sending. From there, our customer’s own terms with that tool apply. Our customer can turn the summary off.
Alerts and webhooks
If our customer sets them up, Wayhint sends alerts and events about guide conversations to the chat channel or endpoint they choose: the visitor’s question and comment, masked, the account when account tracking is on, and a link to the dashboard. They never identify a visitor. Delivery logs are kept for 7 days, or 30 days for failed deliveries.
Observe mode
If a site owner turns on observe mode, the widget also reports masked page structure and which control led where, with a random identifier per browser tab and no user identifier. These records are kept for 90 days by default.
AI providers
To choose the next step, guide requests are sent to a model: by default DeepSeek V4 Flash, an open-weight model served by DeepInfra (US). A site owner can choose their own model provider instead in the dashboard; that site’s requests then go to that provider. Analytics about guide requests (questions, steps, outcomes) are deleted after 180 days. The full list of sub-processors is on the security page.
Design-partner applications
If you apply on the design-partner page, we store what you enter (work email, company website, help center, ticket range, languages, message) and the campaign parameters of the page you applied from, to reply to you and run the program. Your IP address is not stored with your application. Applications are deleted after 12 months, or sooner if you ask.
This website
This site runs the Wayhint widget itself, as a live demo, with observe mode turned off. The widget loads after your first interaction with the page and, apart from fetching its own configuration, sends nothing until you ask Nuri something. When you do, it sends your goal and the masked page structure described above (headings and labels of buttons and links, never input values). On this site the demo runs a keyword guide on Cloudflare instead of an AI model, and it doesn’t store what it receives. The site uses no advertising trackers. If we add analytics, we will list them here.
Your rights
You can ask for access to, correction of, or deletion of your personal data: write to [email protected].
See also security and privacy and the draft terms.