Privacy Policy
Hinto reads real evidence, including your product's sessions, so it can investigate support tickets accurately. This policy explains what that means for privacy: what we capture and what we deliberately never do, who counts as a customer of ours versus a customer of yours, and what happens to data once it reaches us.
What this covers
This Privacy Policy explains what personal data Hinto collects, why, and what we do with it. It covers the Hinto dashboard, the browser SDK you can install in your own product, the API and MCP endpoints, and this marketing website.
It does not cover the practices of the third-party services you choose to connect, such as Slack, GitHub, Sentry, or Linear. Their own privacy policies apply to how they handle your data.
The two roles Hinto plays
For the staff accounts your organization creates to sign in to Hinto, and for visitors to this marketing website, Hinto decides how that data is used and is the controller.
For data about your own end users that flows through your connected integrations or the browser SDK, your organization decides what is captured and why. Hinto acts as a processor there, handling that data only on your organization's instructions.
What the browser SDK captures
If your organization installs Hinto's browser SDK in your own product, it records what a user did, not what they typed. It captures:
- Page views and navigation
- Clicks and other interactions, recorded as an element's tag, role, and label, never its value
- Console messages
- JavaScript errors and unhandled promise rejections, including the error message, filename, line, column, and stack trace
- Network request outcomes: method, URL, status, and duration, never request or response bodies, headers, or cookies
- The browser's user agent string, sent with every batch of events
- Custom events your own code sends with track(), including whatever properties you pass to it
- The signed-in user you attach with identify, so a session can be matched to a customer
What it never captures
The SDK's defaults are deny-first: it keeps as little as possible, and scrubs what it does keep before anything leaves the browser. It never captures:
- Form values and keystrokes
- Request and response bodies
- Headers and cookies
- A visual recording or a snapshot of your app's page layout
- Full query strings, which are stripped by default from every captured URL
What identifies a person
By default, a captured session is anonymous: it is tied to a random session id, not a name or email address. If your organization calls identify() from the SDK with a signed-in user's email or your own user id, that value is stored so a session can be matched to a customer for support purposes. Without that call, a session is not linked to a named person by default. What it does capture, including URL paths, console output, error text, and the browser's user agent, comes straight from your own application, so if your app puts a name, an email address, or another identifying detail into one of those, that detail is captured along with it.
Your organization's own staff accounts identify the same way any B2B product's do: through Clerk, our authentication provider, using the name and email you sign up with.
What your connected integrations expose to Hinto
When your organization connects Slack, Hinto can read the messages in the channels you choose to track and post replies there; it does not read your entire workspace.
When your organization connects GitHub, Hinto reads the one repository you point it at, through a scoped installation or a token you provide, to look for the code responsible for a bug. It does not write to your repository.
Sentry and Linear are integrations you connect and control the credentials for. Hinto reads error data from Sentry to investigate a ticket, and can create issues in Linear when your organization sets up that escalation. Hinto does not operate its own copy of either service; they remain your own accounts.
How AI is used
Hinto uses a third-party large language model, reached through Vercel's AI Gateway, to investigate tickets, triage incoming messages, and match sessions to customers. That means evidence relevant to a ticket, such as session summaries, error details, and code excerpts, is sent to that model provider so it can produce a finding.
We have not negotiated any special data-handling terms with our model provider beyond its own standard API terms. We do not use your data to train models for other customers.
This website and the waitlist
If you join our waitlist, we store the email address you give us and a salted, one-way hash of your IP address, never the address itself, so we can rate-limit signups and prevent abuse.
We use your waitlist email only to tell you when it's your turn and about Hinto itself. We do not sell it or share it with anyone outside Hinto.
Cookies and analytics
This marketing website does not set any analytics or advertising cookies today. If that changes, we will update this policy first.
The Hinto dashboard uses cookies from Clerk, our authentication provider, to keep you signed in. Those are necessary for the product to work and are not used for advertising.
Subprocessors
We use a small number of other companies to help run Hinto. Each one only sees the data it needs to do its job.
Clerk
Stripe
Supabase
Vercel
OpenAI
Security
Every organization's data is isolated in our database using row-level security tied to your Clerk organization, so one customer's data is never visible to another.
API keys and the OAuth tokens issued for MCP connections are stored as a hash, not in a form we could read back, the same way passwords normally are.
Some other stored values, including Slack bot tokens and the credentials for connected integrations such as Sentry and GitHub, are not additionally encrypted in our database today, beyond our infrastructure's own access controls. We are telling you this now rather than waiting until it changes, and tightening it further is on our roadmap.
Retention
We do not currently run an automatic retention or deletion schedule. Data you send to Hinto, including captured sessions and investigation records, stays in our database until your organization asks us to remove it or closes its account.
You can ask us to delete your organization's data, or a specific person's data, at any time by emailing hello@gethinto.com.
International transfers
Our subprocessors operate globally, so data may be processed in countries other than your own. We rely on each subprocessor's own compliance program for how they handle data across borders.
Your rights and how to exercise them
You can ask to see, correct, or delete the personal data we hold about you, or ask what we have and why, by emailing hello@gethinto.com. We will respond as quickly as we reasonably can.
If you are an end user of a company that uses Hinto and you have a question about your own data, we encourage you to also reach out to that company directly, since they control what is captured about you.
Children
Hinto is a business product, not directed at children, and we do not knowingly collect personal data from anyone under 16.
Changes to this policy
We may update this Privacy Policy as Hinto changes. If we make a material change, we will make a reasonable effort to let you know, such as by email or a notice on this site.