Legal

Privacy notice

How Dialspire handles personal information: what we hold for our own customers, and what we process for them under the data processing agreement.

Last updated 13 October 2026

Draft, pending professional review. Where it describes how Dialspire works, that is how it works today. Some terms are still proposals, it has not been reviewed by a solicitor, and the details marked “coming soon” are still to be filled in. Please don’t rely on it as a final statement of our obligations.

Who is responsible

This notice explains how Dialspire Ltd (“Dialspire”) handles personal information in connection with dialspire.com and the Dialspire service. Proposed effective date: Coming soon. It should be read with the Cookie policy.

Our company number is 17546107, our place of incorporation is England and Wales and our registered office is 66 Paul Street, London EC2A 4NA, United Kingdom. VAT number: Coming soon. ICO registration or confirmed exemption: Coming soon. Contact jhw@dialspire.com for privacy matters and jhw@dialspire.com for service support. Data Protection Officer or responsible privacy lead: Coming soon. Any required UK or EEA representative: Coming soon.

Dialspire as controller. We determine the purposes of processing necessary to administer our customer relationships, accounts, payments, enquiries and service security. This notice covers that processing, including when your employer invites you to use Dialspire.

Dialspire as processor. The customer normally determines how its leads, calls, recordings, notes, emails and staff activity are used within a workspace. We process that information on its documented instructions under the DPA. The customer’s own privacy notice explains its purposes, lawful bases and retention. The same information may serve different purposes: for example, a call record used for customer reporting is processed for the customer, while the limited usage record needed to invoice it is processed for our own billing.

Information collected and its sources

  • Accounts and administration: names, work email addresses, workspace membership, roles, invitation details and hashed credentials. Sources include you, your employer or administrator and your use of the service.
  • Security and technical information: IP addresses, browser and device information, session timestamps, failed-login counters and operational logs generated through service use. Where error monitoring (Sentry) is switched on, it receives diagnostic information with personal details removed before anything is sent: email addresses, phone numbers, transcripts, notes, passwords, cookies, request bodies and query strings are stripped, and a user is identified only by an internal id. Retention in Sentry: Coming soon.
  • Billing: billing-contact and company details, subscription plan, seats, usage charges, invoices and payment-provider identifiers. Stripe collects card details on its hosted pages; we receive subscription and payment-status information rather than full card details.
  • Connected services: authorised caller-ID details, integration account identifiers, connection status and access credentials or tokens. Mailbox, calendar and CRM data are processed to perform the connection you or your employer authorise.
  • Enquiries and support: names, email addresses, company, team size, current tools, messages and support correspondence, provided by you or someone acting for your organisation.
  • Workspace content: imported contact details and custom fields; assignments and priorities; call times, durations and outcomes; notes, email content and delivery events; suppression records; recordings, transcripts and AI outputs; and information returned by enabled integrations or enrichment sources.

Sources of workspace data include customer uploads, customer users, call participants, connected services, Companies House and publicly available business websites where relevant features are enabled. These sources do not remove the customer’s obligation to explain indirectly collected information to the people concerned.

The platform is intended for adult business users, not children. Customers must not upload special-category or criminal-offence data or create lists targeting children. If such information is included inadvertently, contact the relevant customer or jhw@dialspire.com so it can be handled appropriately.

Our purposes and lawful bases

The following table concerns processing for which Dialspire is controller. Processing under customer instructions is governed by the DPA; Article 28 is not itself a lawful basis for the customer’s collection or marketing.

PurposeInformationLawful basis
Establish and administer a subscription, manage payment and respond to requested pre-contract stepsContact, account, billing and usage dataContract where the individual is the contracting customer; otherwise legitimate interests in providing and administering services to the organisation
Provide user access and communicate with customer staffAccount, role and service communicationsLegitimate interests in delivering the customer’s service and managing business relationships
Prevent abuse, protect accounts and investigate incidentsTechnical logs, sessions and proportionate incident informationLegitimate interests in security, fraud prevention and reliable service; legal obligation where specifically required
Answer enquiries and support requestsEnquiry and correspondence informationLegitimate interests in responding and resolving issues; contract where applicable to an individual customer
Maintain statutory accounts and respond to lawful demandsNecessary financial, identity and compliance recordsLegal obligation under applicable tax, accounting or other law
Understand use of the public website through optional analyticsThe visitor information described in CookiesConsent under the proposed configuration, including where the analytics technology uses no cookies
Send Dialspire’s own promotional communications, if introducedBusiness contact details and preferencesComing soon — no promotional use is assumed by this draft

We assess legitimate interests against your rights and expectations. You may ask about that assessment or object. Required account and billing information is needed to administer the service; without it we may be unable to provide access or complete a purchase. Optional enquiries, integrations and analytics are voluntary.

Calls, AI and workplace information

Recording is off by default and only a workspace administrator can switch it on. When it is on, the person called hears an announcement on their own line before recording starts, and the wording they heard is kept with the call. A recording is transcribed when a user asks (or automatically, where the workspace’s CRM sync is set to send transcripts), and summarised with a suggested outcome only when a user asks. The customer must explain recording and monitoring to callers and staff, select a lawful basis, obtain any required consent and set retention. The use of an announcement does not by itself satisfy every recording rule.

Call audio is transcribed by Groq. Anthropic writes call summaries from the transcript; briefs on a lead’s company from its public website, the company name and the contact’s job title (never the person’s name, phone number or email address); and draft follow-up emails from the recipient’s first name, their company, the latest call summary and the sender’s first name. Dialspire does not use customer calling content to train AI models or to build other customers’ lead lists. Provider retention, access and training restrictions are to be confirmed in DPA Schedule C. Summaries may be wrong and require human review. Dialspire makes no decisions about people by automated means: priority scores only order a calling queue, and a suggested outcome is for a person to accept or change. Customers separately explain their employee monitoring, lead ranking and decision-making.

Google user data

A user may connect their own Google account. Dialspire asks Google only for what that connection needs:

  • Your email address (openid, userinfo.email), to show which account is connected and to send from that address.
  • Send email on your behalf (gmail.send), to send an email you have written or reviewed in Dialspire, when you click Send. Dialspire never reads, searches, changes or deletes anything in your mailbox, and stores no content from it.
  • View calendar events (calendar.events.readonly), to show meetings booked with your leads on your own Dialspire calendar, visible only to you. We keep the time, title, joining link and matching attendee of meetings with your leads, and video meetings with outside attendees for you to link or hide (deleted 30 days after they end); every other event is discarded without being stored. Dialspire never creates, changes or deletes calendar events.

Dialspire’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements. We use Google user data only to provide the features above to the user who connected the account. We do not sell it, use it for advertising, transfer it to others except as needed to provide those features, comply with law or as part of a merger or acquisition, or allow humans to read it except with your consent, for security or to comply with law. We do not use Google user data, raw or derived, to develop, improve or train generalised or foundational artificial intelligence or machine learning models, and we do not send it to our AI providers.

You can disconnect at any time in Settings › Connections, or remove Dialspire’s access from your Google Account’s security settings. Disconnecting deletes the stored access tokens.

Cookies and optional website services

We set one cookie, cb_session, which keeps you signed in, and store your cookie choice in your browser (cb_cookie_consent). Vercel Web Analytics runs on the public website only after you choose Accept all. Vercel Speed Insights measures how quickly pages load. Cloudflare Turnstile checks the setup-call form for bots once you start filling it in. Plausible Analytics is Coming soon. We do not assert that analytics is absent merely because it is cookieless. See the Cookie policy for purposes, providers, lifetimes and choices.

Recipients and disclosures

We use providers for application hosting (Vercel), database storage (Neon), payments (Stripe), telephony and recordings (Telnyx), transcription (Groq), AI summaries, research and drafts (Anthropic), outbound email (Amazon SES) and system email (Coming soon), and, where switched on, error monitoring (Sentry) and website tools (Cloudflare, Vercel Analytics, Plausible). Company lookups go to Companies House and a web search provider (Brave Search) with a company’s name and town, never a person’s details. The full list, with what each receives, is on our sub-processors page.

Not every provider is a processor for every purpose. A payment or telecommunications provider may separately control information it needs to meet its own legal obligations. Details of those roles and applicable notices are Coming soon. Customer-connected email, calendar and CRM providers receive data at the customer’s direction and under its own relationship with them. Authorised workspace users can see information permitted by their roles.

We may disclose necessary information to professional advisers under confidentiality, public authorities where legally required, or a prospective or actual business purchaser with appropriate safeguards. We do not sell personal information or disclose customer content for third-party advertising.

International transfers

The database is in London (AWS eu-west-2) and the application runs in London. Telnyx, Groq and Anthropic process the data they receive in the United States, and other providers or their support staff may access data from the EEA or the United States. The transfer mechanism for each is Coming soon.

Restricted transfers require a valid route: applicable UK adequacy regulations, including the UK Extension to the EU–US Data Privacy Framework only for eligible certified recipients and covered data; or appropriate safeguards such as the UK IDTA or EU standard contractual clauses with the UK Addendum, with the required assessment and supplementary measures. A US address does not establish either adequacy or a valid safeguard. EU GDPR transfer requirements must also be met where applicable. Ask jhw@dialspire.com for relevant safeguards, subject to proportionate redaction.

Retention

InformationRetention or criterion to confirm before adoption
Customer accounts and workspace administrationWhile the workspace exists. Cancelling a subscription does not delete a workspace: it is deleted 30 days after an administrator closes it, or on request. A limit on storing an inactive workspace: Coming soon
Sign-in sessions30 days from sign-in, ending earlier on sign-out or revocation; a session idle for 12 hours asks for the PIN again. Expired sessions are deleted
Failed-login counters and security logFailed-login counters are deleted 24 hours after the last attempt unless an account is locked out; the workspace security log is kept for two years
Website enquiries24 months from submission, or sooner on request
Support correspondenceComing soon, measured from resolution or the last necessary interaction
Financial and statutory recordsComing soon, based on applicable tax/accounting obligations
Recordings, transcripts and summariesKept until deleted, unless an administrator sets a retention period (30, 90, 180, 365 or 730 days, or any period from 1 to 3,650 days). A recording is deleted at our carrier before we delete our link to it, and a summary is deleted with its transcript
Leads, notes, email and activity recordsCustomer instructions and DPA retention schedule, with deletion or return at the end of processing
Suppression and objection recordsOnly the address or number, its type, and the reason and source. Kept until an administrator removes the entry or the workspace is deleted, and kept when a person’s other records are erased, so that their objection is still honoured
BackupsOur database provider keeps a rolling point-in-time restore window of 6 hours, in London. There is no other copy. If a restore were ever needed, deletions made since would be applied again

Separate lawful financial retention does not justify keeping unrelated calling content.

Security

Our measures include TLS for every connection, encryption at rest in the database, integration tokens and credentials encrypted with AES-256-GCM, passwords and PINs stored only as salted scrypt hashes, workspace isolation checked on the server for every request, session revocation, and optional two-step verification that an administrator can require for every admin and manager. Dialspire does not hold SOC 2 or ISO 27001 certification. Operational controls, backups and recovery arrangements must match the completed DPA security schedule. No system can guarantee absolute security.

Your rights and how to use them

Depending on the circumstances, you may request access, correction, erasure, restriction or portability, object to processing based on legitimate interests, and withdraw consent. You have an absolute right to object to processing for direct marketing. Withdrawal does not affect the lawfulness of prior processing. Statutory conditions and exemptions may apply.

Contact jhw@dialspire.com or our registered office. We will verify identity only as reasonably necessary and ordinarily respond without undue delay and within one month under the applicable rules. Where a lawful extension or clarification-related adjustment applies, we will explain it. Requests are normally free; any permitted fee or refusal will be explained.

If your request concerns a customer’s lead record, recording or email, contact that business first if you know it. If you contact us, we will identify and forward the request to the relevant controller where possible and assist under the DPA. We remain responsible for requests about information we control ourselves. You can also report abusive use to jhw@dialspire.com.

Complaints and updates

You can complain about our handling of personal information at jhw@dialspire.com or 66 Paul Street, London EC2A 4NA, United Kingdom. We will acknowledge a data-protection complaint within 30 days, investigate without undue delay, keep you informed and explain the outcome. This complaints process does not replace the separate deadlines for rights requests.

You may also contact the UK Information Commissioner’s Office or another competent supervisory authority, and exercise any applicable court rights. A contractual jurisdiction clause does not remove those rights.

We will update the notice date when practices change and give additional notice where required. Any new purpose must have its own valid basis and transparency; a revised notice cannot manufacture consent.

Draft particulars — complete before adoption

These shared fields are repeated for review. Jurisdiction and SLA relate to the service contract; they do not restrict statutory privacy rights or regulator access.

DetailValue
Legal company nameDialspire Ltd
Company number17546107
Place of incorporationEngland and Wales
VAT number or confirmed statusComing soon
Registered office66 Paul Street, London EC2A 4NA, United Kingdom
ICO number or confirmed exemptionComing soon
Support emailjhw@dialspire.com
Privacy emailjhw@dialspire.com
Governing lawComing soon
Contractual court jurisdictionComing soon
Service-level agreement or explicit absenceComing soon
Effective dateComing soon