Who is responsible
LatchCall is a business-to-business service operated by Cytron Limited (company number 06655326), registered in England and Wales. Registered office: 20–22 Wenlock Road, London, England, N1 7GU. Contact: info@cytron.co.uk.
For caller and appointment information submitted through a customer business's receptionist, that business decides why and how the information is used and is normally the controller. Cytron processes that information on the business's instructions to provide the service. Cytron is a controller for its own account, billing, security and service-administration records.
Information and purposes
- Business account and configuration information, including work email, business details, call instructions and notification recipients, to provide and administer the account.
- Call routing and service records, including phone numbers, call status, timestamps and duration, to answer calls, deliver messages, support the service and calculate usage.
- Call content supplied or generated for the business, such as transcripts, summaries, caller details and callback requests, to provide the call-handling service.
- Appointment requests and booking details if the business enables the optional calendar.
- Subscription and payment status through Stripe, and technical/security records needed to protect and operate the service.
Call transcripts are available in the customer's dashboard by default. The account owner may opt in to transcript emails to their login address and configured recipients. The owner is responsible for adding only authorised recipients; delivered email copies are outside the application's deletion controls.
Do not use LatchCall for healthcare, special-category data, or other high-risk processing unless Cytron has separately reviewed and agreed that use in writing. The service is designed for ordinary business enquiries, not emergencies.
Lawful basis and transparency
The customer business, as controller for caller information, must identify and document an appropriate UK GDPR lawful basis for its own purposes, give callers the required privacy information, and set suitable instructions and retention periods. Depending on the actual purpose and relationship, it may consider contract, legitimate interests, legal obligation, or consent where consent is genuinely appropriate. There is no blanket caller-consent basis implied by using an AI receptionist.
Cytron may rely on contract to provide and administer a business account, legitimate interests for proportionate service security and support, and legal obligation where it must retain or disclose records. The appropriate basis depends on the processing and must be assessed in context.
The receptionist should tell callers that they are speaking with AI and that the call may be transcribed or processed to handle the enquiry. A caller who declines can ask not to continue; the configured refusal flow is intended to erase the application's call content. The business should provide a suitable alternative way to contact it.
Service providers and international transfers
Depending on deployment configuration and enabled features, the service may involve LiveKit (real-time voice), Telnyx (telephony and numbers), Deepgram (speech recognition), OpenAI (AI processing), Cartesia (speech generation), Supabase (application data and authentication), Resend (email), Hostinger (website or email services), and Stripe (subscription checkout, billing and payment services). Their roles differ: Cytron uses some providers to process call or account data on its behalf; Stripe separately provides payment services and may determine purposes for its own records.
This list identifies systems used or configured by the application, not a verified list of every supplier, subprocessor, legal entity, hosting region or data flow. Current supplier contracts, Article 28 terms, processing locations, transfer mechanisms and any required transfer assessments remain to be verified. No promise is made here that a particular region is used, that a transfer is approved, or that a supplier does not use data for model training. The business must not send data it is not authorised to disclose.
Retention and deletion boundaries
Application call content is scheduled to be anonymised 90 days after the call starts. The call row remains for billing and service usage; its tenant relationship, status, timestamps and duration may remain and are pseudonymous rather than fully anonymous. Content fields scheduled for removal include phone numbers, transcript, summary, caller details and message tokens.
Appointment records are scheduled for deletion after 12 calendar months from the later of the appointment end or its status change, and only after the appointment has ended. Existing appointment rows receive a conservative status-change date when this retention feature is installed; that can delay deletion of older rows until 12 months after installation. Active future bookings are not removed by that routine. The customer business should manage appointments it no longer needs.
An owner can erase content on a completed or failed call from its dashboard. To avoid interfering with the live call system, an owner request cannot erase an in-progress call; the caller can use the live refusal option instead. If the call has a future unverified, pending or confirmed booking, its booking details are retained until that appointment is no longer active. Call IDs, call status, timing, duration and usage linkage remain for billing and service records.
The application does not store a call recording as a call-content record. Voice and transcription suppliers may process audio or related data to deliver the live call; their storage, retention and use have not been verified and may differ. Recipient-owned emails, backups and supplier-held copies are outside the application's scheduled deletion and cannot be purged by its retention job. Separate deletion requests or provider-side retention controls may be needed.
Your rights and requests
Callers should normally exercise rights with the business that handled their call, as controller. Cytron will assist that business with requests within the service capabilities and contractual terms. Account owners can download their workspace data and erase call content from the dashboard. For account deletion or a request that cannot be handled there, contact info@cytron.co.uk. Account closure may require manual handling; do not assume that deleting an account will cancel a paid subscription or delete provider-held copies.
We aim to respond to a valid rights request within one month. Where the law permits an extension for complex or multiple requests, we will explain the extension and reasons. We may need to verify identity and may withhold or limit a response where the law allows.
You may complain to the UK Information Commissioner's Office (ICO complaint guidance). You can also contact the ICO through its current contact channels.
Changes and review status
We will update this notice when the service or processing changes. This draft must be reviewed against the live deployment, supplier contracts and actual data flows before being treated as final legal advice.