kanukko

Trust Security and data

What we store, and how it's protected.

Kanukko sits between your assistant and other people's websites, so we keep it small: little data, short lists of who can reach what, and nothing sent on your behalf without a yes.

Your searches

Your chatsNever seen. Your assistant sends Kanukko only the tool call, such as the search words and a location. The conversation stays with your assistant.
What is loggedTool, assistant, duration, number of results, and search words with filler removed. Callers are identified by a one-way hash of the network address, used for rate limits and counts.
How long365 days, then deleted by a daily job. Signed-in sessions are removed 30 days after they end.
Personal detailsOnly with your yes. If an action would send your name, email, phone or resume to a board, the assistant must tell you which board and which fields first. Only those fields are sent, and the fact that they were sent is logged without their values.
Your rightsWith an account you can download or delete your data yourself at /account. Without one, write to hello@introex.in.

How the server is protected

Outbound

Only the public internet

Every call to a board goes through a guard that refuses private, loopback and cloud-metadata addresses, including after redirects, so a listing can't point the server at internal systems.

Board content

Treated as untrusted

Listings are cleaned of markup and handed to the assistant marked as third-party data, with an instruction never to follow commands found inside them.

Board keys

Encrypted at rest

If a board gives us an API key, it's stored encrypted with AES-256-GCM. The key to decrypt it lives only in the server's environment.

Limits

Rate limits both ways

Callers get a per-minute limit, and each board is called within the limit it asked for, with short caching in between.

Website

No third parties

No analytics scripts, ad tags or tracking cookies. Fonts are self-hosted and a strict content security policy blocks outside scripts.

Accounts

Sign-in through WorkOS

We never see passwords. Sessions live in HttpOnly cookies on our own domain, and requests that change anything are checked for origin.

Where it runs

ServerRender, Singapore region, over HTTPS with certificates renewed automatically.
DatabasePostgreSQL, reached only by the server.
Sign-inWorkOS AuthKit. Sign-in for developers is being switched on; searching never needs it.
Report a problemFound a security issue? Write to hello@introex.in with "Security" in the subject.