PLUMdata understands just enough about each file in your Drive to name it against your convention and organise it into a structure that makes sense — turning the unstructured files you already have into something both people and AI can actually retrieve. No new storage, no migration, nothing changed without your approval.
Private by design — processed in session, never stored, never used to train AI.
Most tools that tidy a Drive work from the filename and the folder it sits in. PLUMdata starts a layer deeper — from what each file actually is — which is what lets it name and organise files that have never had a meaningful name in their life.
PLUMdata doesn't read your files the way a person would — it takes in just the signals that identify one: the headings of a document, the column names of a spreadsheet, the key elements of a photo. That's all it needs. Across more than 30 common formats — PDF, Word, Excel, PowerPoint, Google Docs, Google Sheets, JPG, PNG, HEIC and CSV among them — those few signals are enough to create meaning from data that never had a useful name, and nothing it sees is kept.
Reading is only step one. PLUMdata pulls the critical information out of every file — what it is, who and what it concerns, the dates and amounts inside it — and classifies it by type, subject and sensitivity. That information surfaces the lakes of hidden files every Drive accumulates, and turns them into something that can be searched, sorted and trusted.
Separators, date format, capitalisation, the terms and spellings that matter to you — set once, and tunable on every scan. Apply one convention across the whole data estate, or give specific folders and groups their own standard where the work demands it. Every suggestion is shaped to that standard, the same way, every time.
Nothing changes without your say-so. Every rename and every move is reviewable and reversible, applied in place through the official Drive API — files keep their location, their permissions and their version history. And one guarantee is written into the code itself: PLUMdata cannot delete your files. Not on request, not by mistake — the capability does not exist. Ever.
Naming is the visible part. Underneath, every scan builds a described, deduplicated, sensitivity-aware picture of your Drive — a living index that stays in your own Drive, speaks the format AI systems understand, and keeps paying off long after the files are tidy.
The same problem — files that can't be found can't be used — shows up whether it's one person's photo library or a ten-thousand-seat estate. Here's what getting it fixed actually looks like, day to day.
The shoebox of downloads, fifteen years of camera dumps, the PDFs you can never find when a deadline is staring at you. PLUMdata turns all of it into something you can search in seconds.
When the whole business lives in one Drive, every lost file is billable time gone. PLUMdata puts one standard across client work, money and admin — and keeps it there as the files pile up.
Standards drift the moment more than a few people share a Drive. PLUMdata reconciles the whole estate to one convention regardless of who created what — and keeps it that way through growth and turnover.
At scale the expensive problem is invisible data — files no one knows the estate holds. PLUMdata applies one discovery-and-metadata layer across all of it: the precondition for any catalogue, fabric or retrieval system above.
PLUMdata runs a human–machine governance loop: the system proposes, you decide. Every change is reviewable, every change is reversible, and nothing is applied to your Drive without an explicit action from you.
Your first 100 files are free. Private by design — processed in session, never stored, never used to train AI.
See the full quote before you commit. No surprises.