GlobalCanadaEuropeAsia-Pacific
Sign in

Privacy Policy

Distronode Corporation • Last Updated: October 10, 2026 • Version 2026-10-10

01. Overview & Accountability

Distronode Corporation ("we," "us," or "our"), a Canadian corporation federally incorporated under the Canada Business Corporations Act, operates District AI, an AI-powered voice receptionist platform. We are committed to protecting your privacy in accordance with the Personal Information Protection and Electronic Documents Act (PIPEDA) in Canada and Quebec's Law 25, the General Data Protection Regulation (GDPR) and the UK GDPR in Europe, and the consumer privacy laws of United States states.

Which role we play depends on whose information it is, and the distinction matters. We are the Data Controller for information about our own visitors, account holders and prospects: what you tell us when you sign up, contact us, or browse this website. For the content inside a customer's workspace, including the information their callers give the AI receptionist, we are that customer's processor and we handle it only on their instructions, as set out in our Data Processing Agreement. If you are a caller wanting your information corrected or deleted, the business you called decides that, and we will help them do it.

Our operations are headquartered at RBC WaterPark Place, 20 Bay Street, 11th Floor, Toronto, Ontario, Canada.

02. What We Collect and Why

This table covers the information we hold as controller, about visitors, account holders and prospects. The last row is the content inside a customer's workspace, which we hold as that customer's processor and touch only on its instructions.

02. What We Collect and Why
CategoryExamplesWhy we collect itBasisSource
Identity and contactName, business name, email address, phone number, business addressCreate and administer your account, respond to you, invoice youContract; legitimate interestsYou
Account credentials and sign-in historyPassword hash, two-step verification enrolment, and the time, IP address, country and device of each successful sign-inAuthenticate you, detect misuse of your account, notify you of a sign-in from a new locationContract; legitimate interests (security)You; your browser
BillingCard details held by Stripe (we see only the last four digits and the card brand), billing address, tax identifiers, invoicesCharge subscriptions and usage, collect tax, keep the records tax law requiresContract; legal obligationYou; Stripe
Usage and device dataPages visited, features used, browser and operating system, referring campaign, consent choice, edge-detected countryOperate and secure the service, measure our marketing where you consent, remember your preferencesLegitimate interests; consent for analytics and advertising cookiesYour browser; our servers; our edge network
Support correspondenceYour name, email address, subject and message text, and the replies in that threadAnswer your request and keep a record of it for the retention period belowContract; legitimate interestsYou
Workspace content (as processor)Caller phone numbers, call audio, transcripts and summaries, contacts, messages, appointments, knowledge-base documentsProvide the receptionist and inbox on the business's instructionsThe business's own lawful basis; we act on its instructions under the DPACallers; the business; carrier caller-ID lookup; enrichment providers where the business enables them

03. Lawful Basis for Processing

Contract

To create and run your account, deliver the receptionist and inbox you subscribed to, bill you, and answer your support requests.

Legal obligation

To keep the billing and tax records the law requires, to keep records of unsubscribe requests under anti-spam law, and to answer lawful requests from regulators and courts.

Consent

When you accept analytics and advertising cookies, or connect a third-party account such as Google. You can withdraw it at any time.

Legitimate interests

To keep the service secure and prevent fraud, to understand how the product is used so we can improve it, to promote our own services through our website, social media and advertising (subject to your cookie choices, and never by email), and to enforce our terms. Where we rely on this basis under the GDPR or UK GDPR you can object, and we will stop unless our grounds override yours.

05. Cookies & Similar Technologies

We set a few first-party cookies, none sold or shared for cross-site tracking.

distronode_session: essential (14 days). Keeps you signed in.

dn_consent: essential (12 months). Remembers your cookie choice.

dn_attrib: analytics (180 days). Records the campaign or referral that first brought you here; in consent-required regions, set only after you accept.

Google Analytics cookies (_ga and related): analytics and advertising, set through Google Tag Manager only where Consent Mode permits.

li_fat_id: advertising (30 days), set by the LinkedIn Insight Tag only after you accept. It identifies your browser to LinkedIn to measure which of our ads led to sign-ups.

oauth_workspace_id: essential (10 minutes). Carries your workspace through an account-connection flow.

dn_country: essential (24 hours). Holds only the two-letter country code our edge network detected, for consent rules and regional prices.

dn_home: essential (12 months). Holds only your region's name, to send you to its sign-in page.

Workspace selection: essential. Remembers your current workspace. A preference, never a permission: access is always re-checked.

Connection-flow state: essential, single-use. Verifies that a Google, Microsoft or social account link returned from the flow you started; discarded on completion.

localStorage holds interface preferences, a copy of your cookie choice and, with analytics consent, Mixpanel's identifiers, so Mixpanel sets no cookies (section 06).

Change your cookie choice via Cookie preferences in the footer.

06. Advertising & Analytics

We measure site usage with Google Analytics 4 through a first-party, server-side Google Tag Manager container hosted in Canada (Stape, sst.distronode.com). Consent Mode governs what these tags may store. Where your advertising choice allows it, the same container also tells Google Ads when you start a checkout.

LinkedIn ads are measured by its Insight Tag (li_fat_id, section 05) and, from our servers, the LinkedIn Conversions API. We send only website and conversion events, a SHA-256 email hash and that cookie's identifier, so a sign-up can be matched to the ad that led to it, never plaintext emails, IP addresses or mobile advertising identifiers. Where prior consent is required, the tag loads only after you accept.

Conversion reporting

Our servers report completed purchases to Google Analytics and Google Ads, possibly with a SHA-256 account email hash. They also tell Google Ads when a visit from one of our ads starts a live demo, sending only that ad's click identifier. Where consent is required, only with your analytics and advertising consent. We do not sell personal information or share it for cross-context behavioral advertising beyond this.

Product analytics

Mixpanel measures the signed-in dashboard and our public pages, never for advertising, with European data residency, identifiers in localStorage rather than cookies and IP geolocation off; where prior consent is required, it loads only after you accept. The dashboard uses a SHA-256 hashed account identifier. Public pages use an anonymous identifier, and Mixpanel receives no email address and nothing you type into a form; if you later sign in on the same browser, those earlier visits are linked to your account.

Some lifecycle events (account or workspace created, subscription purchased, workflow run completed, call handled) are sent from our servers without cookies, as first-party service telemetry listed on our sub-processors page.

Withdraw consent any time via Cookie preferences in the footer.

07. AI Processing Infrastructure

We use Google Cloud Vertex AI and Gemini models. Your content is isolated per workspace by row-level security in our own databases, and it is never used by us to train public or foundational models.

Call audio is transcribed and voiced by specialized speech providers acting on our behalf: Deepgram for the engine a new workspace starts on outside Canada, Amazon Transcribe and Amazon Polly, in Montreal, for the engine a new Canadian workspace starts on. ElevenLabs, AssemblyAI, Inworld, and Cartesia are available as optional voice engines, depending on the voice a workspace selects. Where a workspace enables the optional video avatar, video sessions are rendered by Tavus.

Tenant isolation: row-level security

08. Call Records & Caller Data

District AI answers calls on behalf of the businesses that use it. When you call a District AI number, the call is answered by an AI assistant, which transcribes and summarizes it. The audio of the call is not recorded. The phone number you call from may be checked against a carrier lookup that returns the caller name on record and the type of line, so the business can recognize returning customers. We do not buy spam or risk scoring on callers. This information is stored in the business's private workspace and is controlled by that business; we process it on their behalf.

Where a workspace enables lead enrichment (District Global Intelligence), we supplement business-contact records with professional information, such as company, role, and business email, sourced from licensed B2B data providers (currently People Data Labs and Apollo) and carrier caller-ID lookups (Twilio). Enrichment data is used only inside that workspace's CRM and is never sold.

09. Automated Decision-Making

The receptionist answers, qualifies and books on the instructions of the business you called, and that business can read, correct and override anything it records. We do not use personal information to make decisions that produce legal effects on you, or similarly significant effects, by automated means alone. Where a business chose to use District AI in a way that would, it is responsible under its own law for the notice and the human review that requires, and our Data Processing Agreement asks it to provide them.

10. Data Residency & International Transfers

Your workspace's home region is the United States (default, Google Cloud), or Canada (Montreal), Europe (Frankfurt, serving the EU and UK) or Asia-Pacific (Singapore) on Amazon Web Services. Workspace content is stored in an isolated regional database.

Canada: browser call audio is processed in Montreal (ca-central-1). The language model runs in Montreal on every engine except the realtime one (us-east4). New Canadian workspaces start on an all-Canadian engine; other engines run speech recognition and synthesis in the United States. Asia-Pacific: the same, in Singapore.

Telephone calls: the calls a Canadian, European or Asia-Pacific workspace places, or receives on our numbers, are handled in its region; European numbers we issue in Frankfurt and Canadian ones we issue through Telnyx in Montreal. A number on your own carrier account is answered in the United States.

Outside your region: payments (Stripe, United States); support requests (Atlassian, Canada, under the EU adequacy decision for Canadian commercial organisations); optional linked knowledge base questions (Atlassian); number registration documents (Twilio, United States). United States sign-in and routing copies are kept for rollback and Asia-Pacific access checks, and in our encrypted backups.

Live call events carry the caller's name, phone numbers, transcript and AI summary, never audio; each is created where the call is answered.

Transfers rely on Standard Contractual Clauses and adequacy decisions.

The data residency map details each data type.

11. Data Retention

Workspace records (contacts, call records, transcripts, messages): deleted with your account.

Call audio: not recorded; calls leave a record, transcript and AI summary. Callers in Canadian and European workspaces, or wherever enabled, are told calls are transcribed. This policy will say so before any recording feature captures a call.

Number registration documents: kept while in use; deleted 30 days after release or withdrawal, or immediately on account deletion.

Backups: encrypted; all copies deleted within about eight weeks.

Erasure requests: honored without undue delay, within 30 days (Mixpanel included).

Support requests: website and dashboard requests are deleted 365 days after opening, once resolved; help-centre and emailed ones on request. Unmatched or desk-refused erasures are finished by hand within 30 days.

Sign-in history: time, IP address, country, browser or app, and method of each successful sign-in, kept 90 days to confirm sign-ins were yours and trigger our new-country email alert. Failed attempts are not kept.

Billing and tax records: six years after year-end, per Canadian tax law. Stripe holds payment methods under its own rules.

Contact inquiries and unsubscribes: kept until you withdraw consent, ask for deletion, or we no longer need them; unsubscribes stay on file to block marketing email.

Traffic and diagnostic logs: short, fixed provider windows; never used for profiling.

12. Security

We protect personal information with the controls described on our Sovereign page. They are TLS 1.2 or higher on every public endpoint, database storage encrypted at rest by the provider hosting each region, and tenant isolation enforced by PostgreSQL row-level security. Stored credentials are encrypted again with Google Cloud KMS, secrets are managed, access to production is least-privilege, and rate limiting sits in front of authentication. No method of transmission or storage is completely secure, and we do not promise that ours is.

If a breach of our security safeguards creates a real risk of significant harm to you, we notify you and the regulators that PIPEDA, Law 25 and the GDPR require, and we keep a register of such incidents. A customer whose workspace is affected is notified under the timelines in our Data Processing Agreement, so that it can meet its own duties to its callers.

13. Your Rights

Under PIPEDA, Quebec's Law 25, the GDPR and the UK GDPR, you can access, rectify or erase your personal information, object to processing based on legitimate interests, and request portability. Workspace owners can export workspace data as structured JSON, and delete their account and its data, from the dashboard.

Connected a Facebook, Instagram or Threads account? See data deletion requests to erase that data or check a request's status.

Where consent is our basis, you can withdraw it any time without affecting earlier processing: for cookies via Cookie preferences, otherwise by writing to us. We verify requesters' identity and may ask for information to do so. We answer within 30 days; if the law allows an extension, we will say why and for how long. We may decline manifestly unfounded or excessive requests, with reasons.

You can complain to the Office of the Privacy Commissioner of Canada, or the Commission d'acces a l'information du Quebec for Quebec personal information; under the GDPR or UK GDPR, to your country's supervisory authority or the UK Information Commissioner's Office.

For anything you cannot do from settings, contact our Privacy Officer at legal@distronode.com, or start with our Sovereign portal.

Sovereign

14. Marketing Communications

We do not send marketing email. We have no newsletter and no promotional mailing list, and nothing on our website, at checkout or in your account asks you to join one.

The email we do send is about your account and the service you use: receipts and invoices, sign-in and security notices, call reports and usage alerts, replies to your support requests, and notices of changes to our policies and terms. These are not marketing, and they continue for as long as you have an account.

If we ever wanted to send marketing email, we would ask for your consent first and update this policy before sending any.

15. Children

Our services are for businesses and are not directed to anyone under 18. We do not knowingly collect personal information from a child, and if you believe a child has given us some, write to legal@distronode.com and we will delete it.

16. United States Residents

For residents of California and other US states with consumer privacy laws: we do not sell personal information. The consent-gated conversion measurement in section 06 sends a one-way hashed email to Google Ads and LinkedIn, matching a sign-up to its ad. Under California law that may count as sharing for cross-context behavioral advertising, so you can opt out at any time: choose Decline, or the Cookie preferences / Do Not Sell or Share link in the footer. A Global Privacy Control signal from your browser is treated as that opt-out automatically, without asking you to confirm, unless you have chosen Accept here. We honor requests to know, correct, and delete in any state, without discrimination, through section 13's channels.

17. Changes to This Policy

We may update this policy as the service and the law change. Each version is identified by the date at the top of this page, and our sitemap carries the same date. For a material change we give account holders at least 30 days' notice by email or in the dashboard before it takes effect; for anything else the new version applies from the date shown. Earlier versions are available from legal@distronode.com on request.

18. Contact

For any inquiries, please contact our Privacy Officer, Sean Dean, founder and CEO:

legal@distronode.com

19. SMS & Messaging

Distronode Corporation uses SMS for critical service notifications to account holders, such as account or service alerts. We verify accounts by email and send no SMS one-time passcodes; a text claiming to be a Distronode login code is not from us.

Businesses can exchange SMS, MMS and WhatsApp messages with customers through our telephony partners (Twilio, Sinch and Telnyx); those conversations sit in the workspace inbox, controlled by that business. For a business using District AI, we may text a caller who asked for one during the call, at the number in that call's record, never one the caller supplies or the AI model chooses.

No Sharing of Messaging Consent Data

We do not share, sell, or provide your mobile phone number or messaging consent data to third parties or affiliates for marketing or promotional purposes. All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.

Opt-Out

Reply STOP to any message to opt out, or HELP for assistance. Frequency varies, typically one or two messages per call. Message and data rates may apply. See section 20 of our Terms of Service.

20. Google User Data & Limited Use

When you connect a Google account to Distronode, we request only the scopes needed to power the features you enable:

Google Calendar

Used solely to check your availability and create or update appointments that you or your AI agent schedule on your behalf. We do not read or store calendar data beyond what is required to complete these actions.

Google Contacts (read-only)

Used solely to let you import your existing contacts into your workspace CRM. We access this data only at your explicit request and never modify your Google Contacts.

YouTube (Distronode's own channel only)

Distronode uses YouTube API Services to upload videos to, and read view and engagement statistics for, Distronode's own YouTube channel from our internal publishing tool. We do not ask customers or visitors to connect a YouTube account, and we do not collect information about the people who watch our videos beyond the aggregated statistics YouTube reports to channel owners.

Distronode's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Limited Use Commitments

21. Microsoft Account Data

When you sign in with or connect a Microsoft account, Distronode requests only the access each feature needs, when you turn that feature on:

Sign in with Microsoft

Your name, email address and an account identifier, used only to sign you in. Signing in grants no access to your mailbox, calendar, contacts or photo.

Outlook Calendar (when you connect it)

Used to check when you are busy, to create, move or cancel appointments that you or your AI receptionist schedule, and, when you ask your AI receptionist about your day, to read you the title, time and number of attendees of your upcoming events. We never read event descriptions. When the AI receptionist books a caller, Microsoft sends that caller a calendar invitation.

Outlook Contacts (read-only, when you start an import)

We ask for this permission only when you import contacts. We read each contact's name, email addresses and phone numbers, and save the name, one email address and one phone number to your workspace contacts. Your AI receptionist then uses them to recognise callers and greet them by name. We never modify your Outlook contacts.

We store the access Microsoft grants us encrypted. Event titles and times read to you, and the names of recognised callers, are processed by the AI and speech providers listed on our sub-processor page, to answer you during the call.

We do not use Microsoft account data for advertising, we do not sell it, and we do not use it to train generalized AI models.

You can disconnect Outlook at any time from your workspace settings, and the workspace stops using that calendar immediately. If you own the workspace, we also delete the stored Microsoft credentials, except while they are still your only way to sign in or still power an Outlook contacts import in one of your workspaces. Disconnecting does not remove Distronode from your Microsoft account; to do that, remove it from your Microsoft account's app permissions, or ask your organization's administrator.