Privacy by design

Your work data
stays under your control.

LinkContext needs system permissions to understand the work in front of you. That access is a capture boundary—not permission to build a permanent archive of everything you see.

Captured work data is processed and saved on your Mac by default, and LinkContext does not operate a cloud work archive. Enabled integrations send selected data only when you explicitly invoke an action—for example, creating a Notion page sends the resource title and LinkContext resource link directly to Notion.

Processed locally by defaultNo cloud work archiveIntegration sharing is user-triggered
Local-first
Privacy boundaryYour data, under your control
Protected
Work data stays on your Mac by defaultRelationships and usage records stay local
Local
No cloud work archiveNotion receives the title and link only when you create a page
On demand
Choose when to capture or revoke accessLocal-first by design
✓No cloud sync
01

Why LinkContext asks for Accessibility

Accessibility

Identify the active app, focused window, and linkable work surface.

Requested only during an explicit capture; no background event archive is created.
02

From your action to a useful resource

  1. 1Your actionOpen Current Resources or choose Refresh
  2. 2Local captureApp, window, selected text, and app adapter
  3. 3Local recordResource identity, link, and usage metadata
  4. 4Your relationshipsStable local links between resources

Never captured in the background

  • Application-switch history
  • Browser-tab history
  • Image processing or model requests

Always under your control

  • Choose when to capture the current resource
  • Revoke permissions in macOS System Settings
  • Manage and remove local LinkContext data
  • Keep confirmed links and recent use separate