Grape
Locked notes for product managers

Lock a note. Nobody else can read it, not even us.

A locked note is encrypted on your device with a password only you know. It syncs like any other note, but what reaches our servers is a sealed block of text: no AI reads it, no search indexes it, and we could not open it if we were asked to. On every plan.
Encrypted on your laptop or phone before it syncs, with AES-256 and a key stretched from your password
One password for every locked note, typed once and locked again after a few minutes
A recovery key shown once when you set the password, the one other way in
Left out of search, the AI, the index, widgets and exports while it is locked
Its title stays in the list on every device, so you can tell your locked notes apart

Sealed before it leaves

The note is encrypted on your device. The password never leaves it, and the server holds only a block it cannot read.

A recovery key, once

Grape cannot reset a locked notes password, because it never has it. The recovery key you saved is the one other way in.

One password, every locked note

Type it once and every locked note opens until Grape locks them again: after a few minutes, in the background, or when you say so.

The AI never sees it

A locked note is left out of chat, semantic search, the index and any AI app connected to your account.

Syncs sealed

It travels between your devices encrypted, and opens on the phone with the same password you set on the laptop.

Text notes, for now

Headings, lists, tables, code and links lock. A note with an image or a recording asks you to take it out first.
Outcomes

Three things that stop living in your head

Not a feature list. What changes when six meetings a day land somewhere that can answer back.
The follow ups are in your head until the next call pushes them out.

Get the follow ups out of the meeting

Record, then ask for what you agreed and who owes what, before the next call starts.
Someone asks why it was built that way and the doc is called Untitled.

Answer why we built it that way

Search by the decision, not the doc title, and get the note that explains it.
Ten customer calls, ten transcripts, and no time to read them.

Turn ten customer calls into one theme

Ask what came up repeatedly across a folder of interviews and get it summarised.
A quarter

What that looks like for product managers

Three points in a planning cycle where the app changes the work.
01

Discovery

Record every call into one folder and let search do the pattern finding.
02

Spec writing

Draft in the note where the research lives and link to the decisions it depends on.
03

Planning

Ask for a summary of everything you captured about an area this quarter.
FAQ

Questions Before You Install It

The rest of them live in the help center.

Leave with the notes written.

Customer calls, specs, decisions and the reason behind them in one searchable library, so the context does not live in your head or in a chat thread.