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

# Security & Data

> What data Edges processes, how LinkedIn credentials are stored, what a connected account can do, and how to revoke access.

This page covers what Edges processes, how LinkedIn credentials are protected, what a connected account can do, and how to revoke access.

## Data Edges processes

Edges processes:

* Public professional data about people and companies you extract or search for
* Name, email, and usage of users in your workspace, plus the LinkedIn profile data they connect
* No data from your end customers beyond what you send in API requests

Results are returned in the API response or delivered to [callback URLs](https://docs.edges.run/v1/runs/callbacks.md) you configure. Edges does not write into your systems.

## Credential storage

In [managed mode](https://docs.edges.run/v1/identities/modes.md#managed-accounts), Edges uses accounts it provisions. Your LinkedIn credentials are never used.

In direct mode (and when you sync your own accounts), the LinkedIn session cookies `li_at` and `li_a` are stored encrypted at rest and in transit. Only the Edges services that execute runs can decrypt them.

See [Connecting a LinkedIn Identity](https://docs.edges.run/v1/identities/linkedin.md) for how accounts are connected.

## What a connected account can do

Edges only runs the actions your workspace calls with its API key. Every run is logged.

| Mode | Scope |
| - | - |
| `direct` | The identity (or identities) you pass in `identity_ids`. Edges executes only the actions you call. |
| `auto` | Load is spread across **all** valid accounts in the workspace. A connected account can therefore run actions beyond the single use you had in mind. |
| `managed` | Edges-provisioned accounts. Your credentials are not used. |

See [Identity modes](https://docs.edges.run/v1/identities/modes.md) for when to use each mode.

## Revoking access

To stop Edges from using a connected LinkedIn account:

1. [Disconnect the integration](https://docs.edges.run/v1/api/integrations/delete.md) — Edges deletes the stored cookie and no new run can use it.
2. Sign out of every LinkedIn session, or change the LinkedIn password — that also invalidates the cookie on LinkedIn's side.

When the integration is deleted, Edges posts an `event: "DELETED"` webhook so you can tear down local state. See [Monitor & Recover](https://docs.edges.run/v1/identities/linkedin-recovery.md#setup-process).

## Relationship with LinkedIn

Edges has no partnership, license, or affiliation with LinkedIn. Direct and managed modes are how workspaces choose whose LinkedIn account executes each action — see [Identity modes](https://docs.edges.run/v1/identities/modes.md).

## Data retention

Run data is available via the API for 90 days, then archived for 2 years and deleted permanently. Account and platform data are deleted when the workspace is closed. Full detail: [Run data retention](https://docs.edges.run/v1/runs/manage.md#run-data-retention).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.