# How your LinkedIn Cookie is used

## ​​How your LinkedIn Cookie is used

Navigating the balance between sales productivity and platform compliance can feel like a tightrope walk. Delpha is built specifically to bridge the "Data Sovereignty Gap" by ensuring the information you are already authorized to access actually reaches your Salesforce CRM—without putting your LinkedIn account at risk.

Here is how Delpha maintains a safe, compliant, and "Human-Intent" focused workflow.

### The "Human-Intent" Standard

At the core of Delpha’s architecture is the Human-Intent framework. Unlike traditional "bots" that run autonomously, Delpha operates strictly as a technical extension of an authorized human user’s manual workflow.

* **Authorized Interoperability**: We do not bypass LinkedIn’s security or commercial boundaries; we facilitate the transfer of data a user is already contractually authorized to access.
* **User-Initiated Triggers**: The Delpha server remains dormant by default. It only processes a profile when a human user actively intends to view a page and triggers the agent. It does nothing else.
* **Cloud-Based Surrogate**: Our server acts as a proxy for the logged-in user, utilizing their specific Session Token and Browser Fingerprint. This ensures all traffic is authenticated and attributed to a real person.

### Strict Prohibitions (Our "Never" List)

To protect your account and meet enterprise risk standards, Delpha adheres to these strict prohibitions:

* **No Synthetic Identities**: We never create fake accounts or use shared/pooled accounts.
* **No Autonomous Activity**: We do not run unattended crawls or scheduled scraping jobs.
* **No Circumvention**: We do not bypass access controls, CAPTCHAs, or native platform "use limits".
* **No Shadow Databases**: Delpha does not build cross-customer databases or resell profile data.

### Built-in Guardrails & Rate Limiting

To prevent "industrial speed" activity that could flag an account, Delpha enforces strict multi-dimensional governors on volume and velocity.

* **Natural Pacing**: Activity is limited to 150 profiles per working day, mimicking natural human-scale interaction.
* **Hard Product Ceilings**: Delpha honors Sales Navigator’s native limits, such as the 10,000 total saved leads cap and standard pagination limits.
* **The "Kill Switch"**: If a security limit or "Commercial Use" warning is detected, Delpha performs a hard stop. The tool remains frozen until you manually reactivate it.

### Data Privacy: Stateless Processing

We prioritize Stateless Processing, meaning Delpha acts as a real-time processor rather than a data warehouse.

1. **Fetch**: Data is retrieved via the user's authorized session.
2. **Process**: Information is structured via AI.
3. **Purge**: Once the data is pushed to Salesforce, it is deleted from our processing layer—leaving no trace and no "shadow" storage.

### Secure Cookie Handling

Your LinkedIn session cookie is the key to this authorized access, and we treat it with Tier-1 security protocols:

* **Encrypted & Secure**: Your cookie is encrypted and stored only within your Salesforce instance. It can’t be used by any human, including Delpha employees or your own Salesforce admins.
* **Purpose-Bound**: The cookie is transferred securely and temporarily only for enrichment tasks you initiate.
* **Zero Private Access**: The Delpha agent can only visit the profile you intended to visit and nothing else. It is strictly prohibited from reading or sending messages or internal LinkedIn content.

## Key Takeaways

| **Pillar**          | **Policy**                  | **Impact on Your Safety**                                                                          |
| ------------------- | --------------------------- | -------------------------------------------------------------------------------------------------- |
| Operational Control | Human-Intent Framework      | No autonomous bots. The system is dormant until you manually trigger a sync.                       |
| Data Retention      | Stateless Processing        | Data is purged immediately after the Salesforce sync; no "shadow" databases are ever built.        |
| Account Protection  | Native Limit Alignment      | Automatically honors Sales Navigator’s lead caps and pagination to maintain account health.        |
| Encryption          | Vaulted Cookie Security     | Tokens are AES-256 encrypted and stored *only* in your Salesforce instance—inaccessible to Delpha. |
| Risk Mitigation     | Intelligent "Kill Switch"   | Instant hard-stop upon detecting platform warnings, preventing "industrial speed" flags.           |
| Compliance          | Authorized Interoperability | Transfers only the data you are already contractually authorized to access.                        |


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.delpha.io/delpha-for-salesforce/how-to-faq/delpha-linkedin-connector/how-your-linkedin-cookie-is-used.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.