← Back to home

Using Peek

Peek usage policy

Peek is a productivity assistant: it helps you understand what's on your screen, learn how to do things, and get work done on your Mac. These rules keep it that way. They apply however a request is worded, including as a story, a test, “for research”, or text placed on a web page or in a document for Peek to read.

What Peek won't do

Ordinary work that only sounds similar is fine: “kill the process on port 3000”, “how do I shoot portraits”, “the plot of my murder mystery”, “set up two-factor on my account”, “what's a safe dose of ibuprofen”.

How Peek keeps you safe

It only acts on what you ask

Text on web pages, in emails, documents or files is treated as information, never as instructions. If a page tries to tell Peek to do something (open a link, share your details, tell you your Mac is infected), Peek ignores it and warns you about it.

It asks before anything that matters

Sending a message or email, posting, buying, submitting a form, deleting, or changing account or security settings always waits for your OK.

Passwords and card numbers stay with you

Peek never types a password, a payment card number or a two-factor code; it asks you to type them yourself.

Apps you choose are never looked at

In Settings → Privacy you can list apps Peek must never capture.

How it's checked

These rules are tested before each release with sets of requests Peek must turn down, everyday requests that only sound risky (which it must still help with), and test web pages with hidden instructions planted in them (which it must ignore). The tests live in the app's source under app/scripts/router-eval/safety.txt and app/scripts/injection-eval/.