What happens today
The patchwork
- Pasting confidential text into a cloud chatbot
- A model that logs and trains on what you send
- A vendor DPA nobody on the matter has read
- A copy on someone’s server waiting to be subpoenaed
Edge playbook
Private client work on device
Use AI on sensitive material without sending it to a server.
- 5 min read
- Intermediate
- 4 moves
- Run any time
The number
The read-and-draft that used to eat an afternoon lands in minutes, and never leaves the phone.
3hr → 8min
The situation
From material that can’t leave the room to AI work that never leaves the phone.
Open a privileged brief, an NDA-bound deck, or a client file inside Edge. The assistant reads it, reasons over it, and drafts what you need: entirely on-device, with no internet, no cloud copy, and nothing behind an account. Unlock it with your fingerprint or face.
With Edge
The workflow
- One assistant, running fully on the device
- No network calls: nothing to intercept or leak
- A per-client Space, sealed from every other
- A finished draft that lived and died on the phone.
How the work moves
Four moves.
Edge runs each move locally, with a preview you can read before you act. Nothing leaves the device between steps: you can turn on airplane mode and the run is identical.
Edge at work
One brief travels through the whole job. Context stays attached until the finished work lands.
Open
Open the privileged file inside Edge. Tell it what you need.
Edge starts from the material in front of it and asks only for what’s missing. No account, no upload, no round-trip to a server: the model is already on the phone.
Read
Point it at the clauses, exhibits, or notes that matter.
Edge works through the document on-device, cleaned and cross-checked against what you keep in this Space. Every reference traces back to a line you can see: nothing is fetched from outside.
Reason
Ask it to weigh the options, risks, or positions.
The assistant thinks out loud where it counts: trade-offs named, assumptions surfaced, judgments explained. All of it stays inside this Space, walled off from every other client.
Draft
Get the memo, summary, or reply back. Edit the last 10%.
A first draft lands on the device in the shape you asked for. You keep it, copy it out by hand, or delete it: either way there was never a server copy to worry about.
Prompts worth keeping
Paste these into Edge.
Three prompts: a kickoff, a full run, and a packaging pass. Copy the one that matches where you are. Rewrite any detail to fit the matter in front of you.
Kick it off
You are Edge, running entirely on my phone with no internet and nothing sent to a server. I’m working on privileged material that cannot leave this device. Here is the file. My goal: a clean first draft I can review and finish myself, with nothing ever copied to a cloud. Walk me through the first move and tell me what you need from me.
Run it in one shot
Run the full playbook end-to-end, all on-device: open the file and tell me what you see, point me at the clauses and notes that matter, weigh the options and name the trade-offs, then hand back a draft in the shape I asked for. Keep everything in this Space. Ask before skipping any step. Show your work as you go.
Package the output
Give me the output as a single memo I can read on the device: lead with the bottom line, then the reasoning and the lines you relied on. Call out anything that changed your read mid-run. Keep it local; don’t suggest sending it anywhere.
What goes in. What comes back.
Inputs in, outputs out.
Edge runs on what’s already on the phone and hands the result straight back to it. Nothing is uploaded: skip any input and the assistant asks for it the first time it needs it.
Give it
- The privileged file, note, or draft on your device
- A one-line brief on what you need from it
- The Space this client’s context lives in
Get back
- A drafted memo or summary, on the device only
- The reasoning and the lines it relied on
- A result that never touched a server or account
The finished artifact
A finished draft, on the device: nowhere else.
Every run ends the same way: a packaged result that stays on the phone, behind your fingerprint. Here’s a preview of what shows up: locally, never in a shared channel.
Edge → your team
Your draft is ready: on this phone only
playbooks
On device · just now
Here’s the result. I ran the playbook end-to-end on the device, kept everything inside this Space, and packaged the draft for you to review. Nothing was uploaded, synced, or logged: it exists only here, behind your unlock.
- Open the privileged file inside Edge. Tell it what you need.
- Point it at the clauses, exhibits, or notes that matter.
- Ask it to weigh the options, risks, or positions.
- Get the memo, summary, or reply back. Edit the last 10%.
What moved
3hr → 8min
The read-and-draft that used to eat an afternoon lands in minutes, and never leaves the phone.
draft.md · notes.md: stored on device, encrypted at rest
Before you run it
Where people stall.
Three ways we see this go sideways and how to avoid each one.
Keep judgment with the team. The playbook should make the work clearer, not hide the assumptions behind it.
- Reaching for a cloud chatbot out of habit. If the material is privileged, keep it in Edge: the whole point is that nothing is sent.
- Mixing clients in one Space. Give each matter its own Space so context stays walled off by construction, not by memory.
- Skipping the review because it read well. The draft is on-device and yours to own: check the first one by hand, then trust compounds.
Questions
Before you start.
No. Edge runs a capable model entirely on-device, so the file, your prompts, and the draft never touch a server or an account. You can switch on airplane mode and the run is identical, because nothing depends on a network call.
Everything is encrypted at rest and unlocked only with your fingerprint or face. Lose the phone and the data stays opaque: there’s no cloud copy to breach and no account to compromise.
Yes, give each client its own Space. Every Space carries its own context and memory and is sealed from the others by construction, so Client A’s material never surfaces in Client B’s work.
Nothing. There’s no account, no sync, and no telemetry after first-run setup, so there’s simply nothing on a server to subpoena, leak, or breach. The only traffic Edge ever makes is opt-in model updates you trigger yourself.
