Pulse is a new AI data layer built to capture time & memory — the result of your work, never the raw artifacts behind it: no source code, no documents, no chat logs. This page explains exactly what lives where, who sees what, and which boundaries the system enforces.

⚠️ Pulse is in early beta. Features and schemas may change, and no uptime or support SLA is currently offered. The data model and access rules below are accurate as of the current release.

What Pulse stores

• Time entries — category, tool, project, description, duration, optional start/end times, optional note. Entries logged via MCP are tagged source: agent.
• Profile — name, email, role, team membership.
• Workspace catalog — categories, tools, and projects.
• API tokens — only the SHA-256 hash. The raw psk_… is shown once at creation and never recoverable from the database.
• OAuth artifacts — clients, authorization codes (5 min TTL), access tokens (1 h TTL), refresh tokens. All stored hashed.
• AI insight summaries — short cached summaries of your week / month, when the AI gateway is enabled.
• Work memories (optional, off by default) — decisions, learnings, outcomes, milestones, and blockers your team confirms: title, summary, optional detail, date, project, and — for agent-captured ones — which credential wrote it and any self-reported agent name/model/session id.
• GitHub memory-note pointers (optional) — only when a memory cites a note kept in a connected repo: the repo name, file path, commit id, and GitHub's file checksum. Never the note's contents.
• Jev review records (optional, off by default) — when a workspace turns this on, the proposal being reviewed, the evaluator's scores/answers, and the human's eventual decision.

What Pulse does NOT store

• The contents of your connected apps. Notion docs, GitHub diffs, Slack messages, Google Calendar events — none of it. Those apps are connected to your AI coding tool, not to Pulse.
• Raw work artifacts. No source code, no documents, no chat logs.
• Activity beyond what's explicitly logged. Pulse doesn't observe your screen, keystrokes, or app usage.
• The contents of a GitHub memory note. Pulse only ever asks GitHub whether a cited file exists at a given commit — it never reads, copies, or stores what's inside it.

The data flow

flowchart LR
  subgraph apps["Your apps (connected to your AI tool, not Pulse)"]
    A[Notion]
    B[GitHub]
    C[Google]
    D[Slack]
  end
  T["Your AI coding tool<br/>(Claude Code, Codex, Gemini…)"]
  P[("Pulse<br/>your timesheet only")]
  A --> T
  B --> T
  C --> T
  D --> T
  T -- "logs entry via MCP" --> P

Your AI coding tool reads what it needs from its own connected apps, decides what to log, and sends only the entry to Pulse. Pulse itself never makes outbound calls to those apps.