Who can see what
Your own thinking is yours alone. Here’s exactly who can read everything else.
The short version: your own thinking, your entries, and your threads are yours alone. Shared thinking is read by the people it’s shared with, and no one else. Nothing moves from your own thinking into shared thinking unless you share it.
At a glance
| Who can read it | |
|---|---|
| Your own thinking, its entries, and your threads | Only you |
| Ideas kept from your conversations with connected AIs | Only you |
| The team’s thinking and its entries | Everyone on the team |
| A group’s thinking, entries, and threads | Everyone in the group |
| A group’s name | Its members. In a team, also the team’s owners and admins. |
| Your highlights and pins | Only you, even on shared thinking |
| What you share with the team or a group | Everyone there, credited to you |
| Slack replies from @Cranes | Everyone in that channel |
What team owners and admins can’t see
Being an owner or admin doesn’t open anyone’s own thinking. Owners and admins can see who’s on the team and their roles, read the team’s thinking like everyone else, and see that each group exists so they can delete it.
They can’t read your own thinking, entries, threads, or kept ideas; open or read a group they aren’t in, or see who’s in it; or change the settings of an entry someone else added.
Answers never mix audiences
When a reply will be read by several people, Cranes only draws on thinking all of them can see. A group thread never draws on anyone’s own thinking. A Slack reply never does. Your AI, when you say the work is for the team, leaves your own thinking out.
Connected AIs
A connected AI can use only the thinking you chose for it, and never the exact words of entries marked Keep off connected AIs. See Choose what an AI can use.
Improving Cranes
In a workspace you own, Settings › Privacy has Help improve how Cranes learns. When it’s on, Cranes records learning activity, such as when something was learned or held back and how much evidence supported it. Messages, entry titles, and other content are never sent, and the workspace is identified only by a scrambled code.
For how we handle personal information more broadly, read our privacy policy.