| name | lindy-data-handling |
| description | Data handling best practices for Lindy AI agents.
Use when managing sensitive data in agent workflows,
implementing data privacy controls, or ensuring compliance.
Trigger with phrases like "lindy data", "lindy privacy",
"lindy PII", "lindy data handling", "lindy GDPR", "lindy HIPAA".
|
| allowed-tools | Read, Write, Edit |
| version | 1.15.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","lindy","compliance"] |
| compatibility | Designed for Claude Code, also compatible with Codex and OpenClaw |
Lindy Data Handling
Overview
Lindy agents process data through triggers, LLM calls, actions, knowledge bases,
and memory. Data flows through Lindy's managed infrastructure with AES-256
encryption at rest and in transit. This skill covers data classification, PII
handling, prompt-level data controls, and regulatory compliance.
Prerequisites
- Understanding of data types processed by your agents
- Knowledge of applicable regulations (GDPR, CCPA, HIPAA)
- For HIPAA: Business Associate Agreement (BAA) with Lindy (Enterprise plan)
Lindy Data Architecture
| Component | Data Storage | Retention |
|---|
| Tasks | Task inputs, outputs, step data | Visible in dashboard |
| Memory | Persistent snippets across tasks | Until manually deleted |
| Context | Per-task accumulated context | Task lifetime only |
| Knowledge Base | Uploaded files, crawled sites | Until manually removed |
| Integrations | OAuth tokens, connection data | Until disconnected |
| Computer Use | Browser session, screenshots | 30 days after last use |
Instructions
Step 1: Classify Data in Agent Workflows
Map what data each agent processes:
| Data Category | Examples | Handling |
|---|
| Public | Product info, FAQs, pricing | No restrictions |
| Internal | Sales reports, meeting notes | Limit to authorized agents |
| Confidential | Customer emails, CRM data | Access controls + audit |
| Restricted | PII, PHI, payment data | Minimize exposure + compliance |
Step 2: PII Controls in Agent Prompts
Add data handling instructions directly to agent prompts:
## Data Handling Rules
- Never include full email addresses in summaries — use "[name]@[domain]"
- Redact phone numbers in logs — show only last 4 digits
- Do not forward customer personal information to Slack channels
- When storing to spreadsheet, omit columns: email, phone, address
- If asked to share customer data externally, decline and escalate
