Sub-processors
Last updated: April 9, 2026
What is a sub-processor?
A sub-processor is a third party that processes personal data on our behalf when you use Laisy. We publish the full list below for transparency and to meet our obligations under GDPR Article 28. Every vendor listed has a Data Processing Agreement or equivalent contract in place.
Zero retention AI inference
Laisy routes all AI inference to providers we have configured for zero data retention. Prompts and completions are discarded the moment each response returns. Your inputs are never stored, never logged, and never used to train any model.
Current sub-processors
- Purpose
- Primary LLM inference and Whisper voice transcription.
- Data categories
- Prompts, model outputs, uploaded audio for transcription.
- Retention
- Zero retention. Data Controls enabled at the account level so prompts and completions are discarded the moment each response returns.
- Contract
- Groq Data Processing Addendum
- Purpose
- Fallback LLM inference when Groq is unavailable or the request requires a model Groq does not host.
- Data categories
- Prompts, model outputs.
- Retention
- Zero retention. Account is configured to route only to ZDR endpoints, and every request also sets the per request zdr flag. Training opt out is enabled.
- Contract
- OpenRouter Data Processing Addendum
- Purpose
- Primary database. Stores user accounts, content, and application state.
- Data categories
- Account data, user content (meetings, notes, contacts), encrypted OAuth tokens.
- Retention
- Retained for the life of your account. Deleted on request or when you delete your account.
- Contract
- MongoDB Atlas DPA
- Purpose
- Transactional email delivery (email verification, password reset, billing notifications).
- Data categories
- Recipient email address, message body.
- Retention
- Delivery metadata retained per AWS SES policy. Message content is not stored after successful delivery.
- Contract
- AWS GDPR Data Processing Addendum
- Purpose
- Payment processing and subscription billing.
- Data categories
- Billing email, payment method tokens. Full card details never touch Laisy servers.
- Retention
- Per the Stripe Services Agreement.
- Contract
- Stripe Services Agreement (includes DPA)
- Purpose
- Error monitoring and crash reporting.
- Data categories
- Stack traces, request metadata. PII is scrubbed before events are transmitted.
- Retention
- Retained per the Sentry retention policy.
- Contract
- Sentry Data Processing Addendum
- Purpose
- Product analytics to understand feature usage.
- Data categories
- Anonymized event data and aggregate usage metrics.
- Retention
- Retained per the Mixpanel retention policy.
- Contract
- Mixpanel Data Processing Addendum
Encryption
- At rest: All stored data is encrypted with AES-256.
- In transit: TLS 1.3 between your browser, our API, and every sub-processor above.
- OAuth tokens: Encrypted with Fernet before persistence.
Notification of changes
This page is the authoritative list of Laisy sub-processors. Before we add a new sub-processor or replace an existing one, we will update this page and, for customers on plans that require it, provide advance notice by email. You can subscribe to updates by emailing the address below.
Your data rights
You can export or delete all of your data at any time from Settings → Account → Danger Zone, or by emailing the address below. See our Privacy Policy for full details on how we handle your data.
Contact
Questions about our sub-processors, DPAs, or data handling practices?
- Email: contact@laisy.io