Grape
Locked notes for marketers

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.
The hook

Three things that stop costing you a brief

No feature dump. What changes when the swipe file and the customer language can answer back.
The reference is a screenshot in a folder of four hundred screenshots.

Find the reference you saved months ago

Describe the angle and search brings back the note, not a folder of screenshots.
The copy guesses what customers say because the call notes are scattered.

Write from customer words, not guesses

Keep call transcripts and reviews in one place and ask what people actually say.
The retro never gets written and the next campaign makes the same mistake.

Turn a campaign into a retro you keep

Ask for the summary of what ran, what worked and what you would change.
A campaign

What that looks like for marketers

Three points between brief and retro where the app pulls its weight.

Planning

Collect the research, references and angles into one campaign note.

Writing

Draft next to the customer language you captured rather than a blank doc.

After launch

Write the retro in the same note so the next campaign starts ahead.
FAQ

Questions Before You Install It

The rest of them live in the help center.

Actually use it.

Campaign notes, customer language, references and drafts in one library, with search that surfaces the right example when the brief lands.