Pilot-stage website information
Privacy and data processing
This page describes the website enquiry flow and the controls that must be completed before a Dialext pilot can accept customer audio. It is not a completed formal privacy policy or data processing agreement.
Website enquiries
The pilot form asks for your name, organisation, work email and a short description of the kind of meeting you want documented. Do not include a recording or sensitive meeting content.
The server validates those fields and relays the request to the configured Dialext pilot mailbox using SMTP. It does not write the enquiry to the application database. Your network address is used only in a short-lived, in-memory abuse limit and is not written to a website enquiry log by this handler.
The receiving mailbox provider and mailbox retention period have not yet been confirmed in the public processor record. Those details must be completed before public launch.
Before customer audio is processed
Dialext’s operating checklist requires the client identity, lawful basis, participant recording notice, data processing agreement, meeting scope, processor inventory, regions, retention settings, training-use settings, intake path and delivery recipient to be recorded before transcription.
The current processor configuration is not marked pilot-ready. The pipeline blocks billable transcription until the required provider evidence is verified.
Customer audio is not sent to the minutes-generation provider. Only transcript text is sent when that provider is configured. Managed source audio is deleted only after a known delivery outcome via an explicit deletion step, and the result is recorded as deletion evidence.
These controls do not establish what a third-party processor retains. Processor retention, regions, contractual terms and training exclusions must be separately verified and agreed before audio is accepted. Internal copy retention follows the P0-P7 inventory schedule by data class.
Details still required before public launch
- Dialext’s registered business identity, address and formal privacy contact
- The executed data processing agreement and formal privacy notice
- The selected SMTP provider, processing region and mailbox retention
- Verified processor and subprocessor terms, regions and retention settings
- The secure intake method and contractual deliverable-retention period
Contact route
A public privacy email address has not been confirmed. Until it is, use the pilot request form for website enquiries. Do not use that form to send recordings, legal notices or sensitive meeting content.