How the workflow
handles information.
A plain-language account of the information used, the services involved and the choices available.
Effective 16 October 2026
Scope
This policy describes the private LDL n8n automation operated by London Data Labs. It covers the handling of recordings, source transcripts and working outputs in that workflow.
It does not describe every London Data Labs service or establish a retention policy for separate client pilots.
Information processed
Depending on the source material and task, processing may include audio recordings; speaker-labelled transcripts; names and other personal information spoken or written in those sources; document titles and source references; project classifications; working notes; review responses; and operational execution records.
Google Meet transcripts may be imported from Google Docs with their source provenance. Gemini summaries are not treated as verbatim transcript evidence.
How information is used
Information is used to transcribe recordings, organise material by project, prepare working notes and review packets, and support human review. Separate approval precedes changes to canonical project context.
Google Drive and Docs access supports reading selected source material and storing transcripts and results. Slack or email may carry review notifications and operational alerts, depending on the workflow.
Services involved
The workflow runs through n8n on an operator-managed Mac and uses Google Drive and Google Docs for source material and outputs. Audio is sent to AssemblyAI for transcription.
Transcript content used for language processing is sent through OpenRouter to Fireworks-hosted DeepSeek. A zero-data-retention request is configured where applicable. This is not an independently verified guarantee covering every provider or processing route, and it does not remove copies held locally, in Drive or in n8n execution history.
Cloudflare-protected review forms connect reviewers to the operator’s local services. Slack and email services may process notification or alert content. These services receive information for the relevant workflow step.
Storage and retention
Source material and results remain in Google Drive, and n8n execution history may contain workflow inputs and outputs. Local services also process workflow data.
London Data Labs retains audio recordings as project evidence alongside transcripts, review packets and approved notes while they are needed for the project. Our retention policy is to review that material at least every six months and remove or anonymise information that is no longer needed, taking account of project requirements and applicable obligations.
The six-month interval is a review interval, not an automatic deletion deadline. No uniform automatic deletion period is currently established for production workflow execution history or backups. Deletion requests are assessed across relevant stored copies, and any limits affecting provider-held copies or backups will be explained when handling a request.
Separate client staging pilots have their own retention arrangements. Those arrangements do not establish a general deletion period for this workflow.
Your choices and requests
You can contact beanabadger@gmail.com with questions or to request access, correction or deletion relating to information processed through the app. The operator will need enough context to locate the relevant material and assess the request.
A connected user can revoke the app’s Google account access through their Google account settings. Revocation stops future access using that authorisation; it does not itself delete information already stored or processed.
About this website
This website is hosted by Cloudflare. It contains no analytics scripts, advertising code, embedded media or forms and does not set application cookies. Cloudflare processes connection information and may record access and diagnostic information to deliver, protect and operate the website. This can include IP addresses, requested URLs, timestamps and browser information. Please do not include sensitive information in website URLs.
Contact and updates
App support and privacy contact: beanabadger@gmail.com.
This policy is effective from 16 October 2026. Changes to the workflow or its data practices may result in an updated policy on this page.