The causes are often mundane: an S3 bucket set to public access by mistake, a Notion page shared without restriction, a private GitHub repository accidentally made public, a Google Drive share open to "anyone with the link". A well-phrased search finds these files in seconds.

What these files contain

Exposed documents frequently include client contracts with prices and terms, payslips and salary grids, plans and roadmaps, financial presentations, technical architectures and source code, board minutes, and personal data of customers or employees. Each category carries a distinct risk.

Hard to detect

These documents get indexed silently. Search engines crawl them within days, and caches persist even after deletion. A removed file stays reachable through web archives for months. Without a watch, there is no way to know what is exposed.

What we do

We look for what is indexed under your name: targeted queries on your domain, storage buckets (S3, GCS, Azure Blob), public GitHub and GitLab repositories, collaboration tools (Notion, Confluence, Trello). Each document found is classified and gets a removal request.

How we step in

Step 01
The report
Mapping of the public exposure of your documents, storage buckets included.
Step 02
The removal
We contact the platforms concerned (AWS, Google, Notion, GitHub…) to get the files removed or closed.
Step 03
The configuration
A report of recommendations to fix the settings at the source and prevent reappearances.

Are your documents indexed publicly?

A report of your organisation's files reachable without authentication, free for the first audit.

Request the first audit See the tiers