Does the search only cover Claude?

No. The service supports datasets from several AI services, including ChatGPT, Claude, Gemini, Grok, Kimi and AI Studio. Source labels on results show which services are actually present in the current dataset.

No. The query itself is not stored. A short one-way hash of the network address is used only to limit automated bulk extraction.

Why can I search with one character?

Domains, country codes and Norwegian characters can be useful signals. The search keeps å distinct from a and supports æ, ø and å without folding them into other letters.

Teknologikk's Exposure Check

See whether you or your organisation is exposed

Publicly shared conversations from AI services became searchable and made headlines after CVs, job applications, company documents and access keys were found. Search for your organisation, email domain, customers, projects or products to see whether exposed conversations contain traces of you or your organisation.

This check is a warning light, not proof that everything is safe. No match only means we found nothing in the dataset currently loaded.

Find a signal without republishing the leak

The results list shows short excerpts, and you can open the full conversation in redacted form. API keys, tokens, private keys, other authentication secrets, email local parts, phone numbers after the country code, share IDs, IP addresses and names in known fields are redacted before storage and once again before display. Raw, unredacted conversations and original share links are not stored by this service.

Why could shared AI conversations appear in search?

This was generally not a breach of private conversations. The problem arose when a share button created a public web page, the user understood the link as “only for the person I send it to”, and a search engine later discovered it through an open page, post or archive.

1. “Share” meant publish
ChatGPT, Claude and Gemini describe share links as pages anyone with the link can read. Such links normally have no password, recipient list or expiry date.
2. A link made the page discoverable
Search engines discover URLs through links on other sites. If a public conversation page can be read and lacks an effective noindex control, it may become searchable.
3. Deleting the original did not retrieve copies
Once others have shared, imported or archived the content, deleting the original does not necessarily remove copies. Treat a share link as publication from the first click.

How to prevent it

1Never use a public share link for customer or employee data, contracts, source secrets, API keys or internal decisions.
2Review the full snapshot before sharing. Several services share everything up to the moment the link is created, not just the last answer.
3Use a business account and workspace-restricted sharing when collaboration is required. Administrators should disable public sharing if it is not needed.
4Regularly review “Shared links”, “Public links” or the equivalent in every service, and revoke anything no longer needed.
5If you find exposure: revoke the provider link, remove posts and archives you control, rotate exposed keys immediately, and ask the search engine to refresh or remove the result.

Relevant next steps

Turn a finding into safer AI use

A match calls for follow-up. No match is an opportunity to prevent one. These next steps directly address the risks surfaced by the Exposure Check.

Free course

Choose the right AI tool for work

Learn the difference between personal and business accounts, and what that choice means for data, sharing and control.

Take the free course Organisation check

The Safety Assessment

Map how your organisation actually uses AI, where governance is missing and which actions should come first.

View the Safety Assessment Free guide

Get started safely with AI at work

Get a practical starting plan and checklist for safer AI use in a Norwegian workplace.

Get the guide

Sources and further help

See whether you or your organisation is exposed

This check is a warning light, not proof that everything is safe. No match only means we found nothing in the dataset currently loaded.

Find a signal without republishing the leak

Why could shared AI conversations appear in search?

1. “Share” meant publish

ChatGPT, Claude and Gemini describe share links as pages anyone with the link can read. Such links normally have no password, recipient list or expiry date.

2. A link made the page discoverable

Search engines discover URLs through links on other sites. If a public conversation page can be read and lacks an effective noindex control, it may become searchable.

3. Deleting the original did not retrieve copies

Once others have shared, imported or archived the content, deleting the original does not necessarily remove copies. Treat a share link as publication from the first click.

How to prevent it

1Never use a public share link for customer or employee data, contracts, source secrets, API keys or internal decisions.

2Review the full snapshot before sharing. Several services share everything up to the moment the link is created, not just the last answer.

3Use a business account and workspace-restricted sharing when collaboration is required. Administrators should disable public sharing if it is not needed.

4Regularly review “Shared links”, “Public links” or the equivalent in every service, and revoke anything no longer needed.

5If you find exposure: revoke the provider link, remove posts and archives you control, rotate exposed keys immediately, and ask the search engine to refresh or remove the result.