> ## Documentation Index
> Fetch the complete documentation index at: https://getpullrequest.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Data and connectivity

> What connects where, and what data moves between phone, cloud, and machine.

## Connections

```text theme={null}
Phone  --HTTPS REST-->  api.getpullrequest.com
Phone  --WSS--------->  hub / relay
Daemon --WSS--------->  hub / relay
Backend --HTTPS------>  GitHub / Jira / Slack (when connected)
Daemon --local------->  agent process, git, filesystem
```

## Data categories

| Data                             | Typical path                                                       |
| -------------------------------- | ------------------------------------------------------------------ |
| Account identity                 | Firebase → GPR backend                                             |
| Task / board metadata            | Phone ↔ backend                                                    |
| ACP session frames               | Phone ↔ relay ↔ daemon ↔ agent                                     |
| OAuth tokens (GitHub/Jira/Slack) | Stored server-side when you connect                                |
| Repo contents                    | Local disk / worktrees; pushed only via git / PR flows you trigger |
| Daemon logs                      | Local `~/.gpr/daemon.log`                                          |

## Pairing

Pairing uses a short-lived token in the QR payload. After pairing, the daemon authenticates with its device credentials on the websocket.

## Encryption in transit

Production daemon traffic uses `wss://`. App REST uses HTTPS.

## Local retention

Uninstall without purge keeps `~/.gpr/`. Use:

```bash theme={null}
gpr uninstall --purge
```

when you want local state removed.