Sub-processors
Last updated: October 28, 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 this list for transparency and to support our obligations under GDPR Article 28. Contact us for the provider and contractual information applicable to your pilot.
Cloud processing and retention
Laisy uses cloud services to process and store information. The services that receive content depend on the feature being used and its configuration. Earlier release records described AssemblyAI and Recall.ai production audio paths, OpenAI staging transcription and Groq desktop transcription. Those records are historical, not a fresh audit of current deployments. The restricted firm profile disables these audio paths, external embeddings and reranking, and unapproved model endpoints. No Chinese-operated API endpoint or unapproved inference fallback is permitted. Inference remains blocked until the selected AWS route's retention and payload-logging controls are verified. The firm release uses bounded native document extraction; it does not send files to LlamaParse. Unsupported or scanned files require a separately verified extraction route and do not silently fall back to a cloud parser. Older deployed versions must be checked separately; removing a processor from code does not delete previously stored documents or provider copies. Provider retention, logging and training controls depend on the service and account configuration; we do not make a universal zero-retention promise. The provider and data scope for a pilot should be agreed before confidential information is uploaded.
Services and configured processing paths
This list describes services used by application paths; it is not evidence that every path is enabled in your environment. The restricted firm release keeps inference and other processing paths disabled unless their operator, endpoint, region, retention and logging controls have been verified. A configured model name or open model weights do not establish zero data retention. Intentional storage of workspace sources, chat answers, citation excerpts and reviewed copies is separate from inference retention. Ask for the environment-specific processing record before using confidential information.
- Purpose
- Earlier releases included Groq language-model inference and Whisper speech-to-text for desktop calls. These paths are disabled in the restricted firm profile. Their state on older deployments has not been re-audited for this release.
- Data categories
- Prompts and generated responses. For desktop recordings: the audio of the recorded call, sent as chunks of about 60 seconds, and the resulting transcript.
- Retention
- Laisy's temporary cloud copy of desktop audio is deleted after successful transcription or scheduled to expire after 24 hours; that deletion is asynchronous. Provider-side retention is subject to the provider's terms and the configured account controls and is not changed by Laisy deleting its copy. No zero-retention guarantee is made on this page.
- Contract
- Provider terms apply. Contact us for the contractual information applicable to your pilot.
- Purpose
- Amplify hosts the web application and EC2 hosts the API. SES delivers transactional email (verification, password reset, billing notices). The restricted firm profile uses only the approved Bedrock Runtime route when its current account, region, retention and logging checks pass. There is no unapproved inference fallback.
- Data categories
- Application traffic; recipient email address and message body for transactional email; prompts and generated responses for an enabled, verified inference route.
- Retention
- Subject to AWS service terms and the configured account controls.
- Contract
- AWS customer agreement and service terms. Contact us for the details applicable to your pilot.
- Purpose
- Earlier releases included OpenAI transcription in staging and an optional desktop fallback. Both are disabled in the restricted firm profile; this page does not assert their current state on older deployments.
- Data categories
- Audio and resulting transcripts if a legacy environment enables this provider.
- Retention
- Subject to OpenAI's terms and the configured account controls.
- Contract
- Provider terms apply. Contact us for the contractual information applicable to your pilot.
- Purpose
- Earlier production release records described AssemblyAI web-audio transcription and recording transcription when connected services supplied no transcript. This path is disabled in the restricted firm profile, and the earlier production runtime has not been freshly audited here.
- Data categories
- Meeting and voice-note audio, or a link to the recording, and the resulting transcripts.
- Retention
- Subject to the provider's terms and the configured account controls.
- Contract
- Provider terms apply. Contact us for the contractual information applicable to your pilot.
- Purpose
- Earlier release records described a meeting bot that joins a selected call and records/transcribes it. This path is disabled in the restricted firm profile. No current production enablement is asserted by this release record.
- Data categories
- The meeting link, the notetaker's display name, the call's audio, video and participant names as captured in the recording, and the resulting transcript.
- Retention
- Subject to the provider's terms and the configured account controls.
- Contract
- Provider terms apply. Contact us for the contractual information applicable to your pilot.
- Purpose
- A legacy path reorders search results by relevance. It is disabled in the restricted firm profile.
- Data categories
- Your search query and the text excerpts of the matching results being ranked, which can include candidate profile details.
- Retention
- Subject to the provider's terms and the configured account controls.
- Contract
- Provider terms apply. Contact us for the contractual information applicable to your pilot.
- Purpose
- Stores accounts, content and application state, plus the vector indexes used for search.
- Data categories
- Account data, user content (meetings, notes, candidates), encrypted integration tokens and embeddings.
- Retention
- Retained as described in the Privacy Policy. Account deletion starts with a request for review and does not immediately erase data. Published handover packs stay with the firm. The review covers subscription status, the deletion scope and any retained copies, including backups.
- Contract
- MongoDB Cloud terms apply. Contact us for the details applicable to your pilot.
- Purpose
- Legacy search paths can request managed embeddings from Voyage or MongoDB. These external embedding paths are disabled in the restricted firm profile.
- Data categories
- Selected text submitted for embedding.
- Retention
- Subject to the provider's terms and the configured account controls.
- Contract
- Provider terms apply. Contact us for the details applicable to your pilot.
- Purpose
- Payment processing and subscription billing.
- Data categories
- Billing email and payment method tokens handled by Stripe.
- Retention
- Per the Stripe Services Agreement.
- Contract
- Stripe Services Agreement.
- Purpose
- Error monitoring. Frontend diagnostics are disabled in the current web release. Backend diagnostics run only when the server is configured with a Sentry DSN.
- Data categories
- When enabled: stack traces and request metadata.
- Retention
- Per Sentry's retention policy when enabled.
- Contract
- Provider terms apply. Contact us for the details applicable to your pilot.
- Purpose
- Product analytics for feature usage. Your browser sends analytics events directly to Mixpanel from the production web application, including on public pages before you sign in. Session replay, heatmaps and autocapture are disabled. The API can also send usage events to Mixpanel, keyed by your Laisy user ID, but only when the server is configured with a Mixpanel token; it is not configured in production.
- Data categories
- When you sign in: a pseudonymous identifier (your Laisy user ID), your organisation ID and role, account status details when available (such as subscription status and sign-up date), and which integrations you have connected. Laisy does not send your email address or name to Mixpanel. Usage events: pages viewed (without query strings, and without share, invite or password-reset tokens), buttons clicked, features used, counts, durations and error codes, the length of a search but not its text, and onboarding answers (role, industry and goal). Browser details: browser, operating system and device type, time zone, language, screen size, the referring website (and the search engine, if you came from one), how you arrived (for example a share or invite link), a session identifier and a device identifier. Laisy tells Mixpanel not to use your IP address to work out your location; as with any web request, Mixpanel's servers still receive the IP address of the connection. Events are linked to your user ID, so they are pseudonymous, not anonymous. Earlier versions of the web application also sent your email address and first name; the web application removes them from your Mixpanel profile the next time you use it while signed in.
- Retention
- Per Mixpanel's retention policy.
- Contract
- Provider terms apply. Contact us for the details applicable to your pilot.
Encryption
- In transit: The public web application and the desktop application connect to the Laisy API over HTTPS. We do not assert a particular TLS version or transport configuration for every service listed above.
- Integration tokens: Connected-account tokens are encrypted before they are stored.
- Desktop recordings: The local recovery buffer of the desktop application is encrypted on the device with a key held in the operating system credential store. This protects the buffered files on disk; it is not end-to-end encryption, and cloud processing receives the audio in a form the services can process.
- Storage: Storage encryption and backups are managed by the hosting and database providers under their configurations. We do not claim a universal encryption standard for all stored data on this page.
Notification of changes
This page is where we record changes to the services that process your data. 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 download an account export or submit a deletion request from Settings → Account → Your data. A deletion request is pending review and does not immediately erase data, close your account or cancel a subscription. Published handover packs remain with your firm. Provider logs, analytics, email intake storage and backups may require separate handling or remain until their retention periods expire. Contact us using the address below with questions about the scope of a request. See our Privacy Policy for full details on how we handle your data.
Contact
Questions about our sub-processors, contracts, or data handling practices?
- Email: [email protected]