Privacy Policy

1. Introduction

This Privacy Policy explains how Kaustubh Ghodke o/a DigiCatalyst Systems ("I," "me," or "DigiCatalyst Systems") collects, uses, discloses, and protects the information you provide when you visit digicatalyst.ca, book a call through Cal.com, email me, or buy the Website Design and SEO service.

It describes DigiCatalyst Systems as it operates today. Website design and SEO is the only service offered, and the Cal.com booking widget is the only place on this site where you can type personal information into a page. There is no contact form, no newsletter signup, no chatbot, and no live chat on any page.

The contact page also publishes a business phone number. Calling or texting it reaches a line DigiCatalyst Systems runs, and that line keeps a record of the call or the text. Section 2 says what it keeps, Section 3 names the companies that carry it, and Section 6 says how long it is kept.

Two different things are described here, and they do not mix. Sections 2 through 9 cover this website and the people who visit it. Section 10 covers something separate: the data I hold on behalf of care plan clients, which belongs to those client businesses and to their own customers, not to anyone who visits digicatalyst.ca.

Geographic scope: the website and services are directed at individuals and businesses located in Canada (excluding the province of Quebec) and the United States. They are not directed at residents of the European Economic Area, the United Kingdom, the province of Quebec, or any other jurisdiction outside the listed service area. If you're outside that area, please do not use the site or send personal information through it. If you are subject to GDPR, UK GDPR, or Quebec Law 25 and submit personal information to the site anyway, the rights afforded by your applicable local law apply to the extent DigiCatalyst Systems is subject to that law.

2. Information I Collect

I collect what you choose to give me, plus the technical request data that any website generates when a browser asks a server for a page.

• Booking information you provide: when you book a call, Cal.com collects your name, email address, an optional mobile number for a text reminder, the email address of anyone you add as a guest so they get the invite too, your answers to the questions on the booking form, and any notes you add to the booking. The booking reaches me by email, appears in the Cal.com dashboard, and is copied into a contact record, described in Section 3. Two attribution fields travel with it that you do not type: product, which records which offer the button you clicked was attached to, and lead_source, which records how you arrived at the booking, such as a page on this site or a campaign link you followed.
• Text reminders for a booked call: if you give a mobile number when you book, I text you a reminder on the day of the call, at 8 a.m. and, for a call after 3 p.m., again at 3 p.m., from the business number. Each reminder gives the time and where to join, and nothing else: no offers, no marketing. To send it, the booking's reference, your number and the call time are copied from Cal.com into DigiCatalyst Systems' phone records, together with a note of each reminder sent. Texting STOP stops the reminders the same way it stops every other automated text, and leaving the number out means no text at all.
• Notes from a booked call: on a booked video call I take notes of what we discuss: your business, what is not working, what you need, and what we agree. A call booked to talk about buying my services, the website call or the agency partner call, is a sales call and uses the note-taking tool described under sales calls below, not a recording. So is the readout call for a written audit bought on audits.digicatalyst.ca. On any other booked call, such as the kickoff of a project or a later client meeting, I ask at the start whether I may record it, and I record only if everyone on the call says yes. If anyone says no, nothing is recorded and I type my notes instead. The recording is made and transcribed on my own computer in Ontario; no transcription service receives it. The transcript sits with my notes on your contact record, described in Section 3, and the audio and every copy on my computer are deleted once the transcript is there. If you change your mind, during the call or after it, tell me and I delete the recording and the transcript.
• Email you send me: when you write to support@digicatalyst.ca, I receive your email address and whatever you put in the message, including any attachment.
• Calls, texts, and voicemail: the contact page publishes a business number, (905) 595-2596. If you call or text it, I keep your phone number, the text of any message you send, and the date and time. No call on this number is recorded: no audio of a call is kept. A call into this number is not transcribed either, unless it is a sales call described below. If you leave a voicemail, the recording and the number that left it are kept, and it may be transcribed automatically. A text that arrives outside business hours gets one automated reply asking what your business is and what you need; texting STOP stops every automated message to your number, takes effect immediately, and texting START turns them back on. A first text, a call I answer, or a voicemail also creates a contact record, described in Section 3. Nothing about the phone line is connected to your visit to this website: the two are not joined up, and the technical request data below is never matched to a phone number.
• Sales calls: I call businesses from this number to offer my services, businesses call me back about them, and people book the website call, the agency partner call, or the readout call for a written audit bought on audits.digicatalyst.ca. On these sales calls, and only when I switch it on, I use a note-taking tool. It never runs on any other call to this number. At the start of the call I say that I use a note-taking tool. While we talk, the sound of both sides goes to Deepgram, named in Section 3, which turns it into text as the call happens, and the last few things you said go as text, with no name or number attached, to Jev, which picks the prepared answer that fits so the tool can prompt me. No audio is recorded or kept, by me or by Deepgram. When the call ends the tool shows me the text of the call, and I keep that transcript, or a summary of it, on your business's contact record, described in Section 3. If you ask me not to use the tool, I stop it and keep nothing from it.
• Client and payment data: if you buy the Website Design and SEO service, I collect what the work requires: business contact details, billing details, and the content you supply for your site. Invoices are issued from Zoho Books, described in Section 3. You can pay by Interac e-Transfer or by card through Stripe. An e-Transfer arrives in my Canadian business bank account with your name, email address, and any message you add. Stripe processes payment-card information directly under Stripe's own privacy policy; DigiCatalyst Systems never sees or stores full card numbers. Section 10 covers the rest of what a client engagement puts in my hands, including the site itself, its backups, and the submissions from any form on it.
• Technical request data: the site is hosted on Cloudflare. Loading a page creates a standard server request record: your IP address, request headers such as browser and device type, TLS connection metadata, the URL requested, the time, and the response status. Cloudflare processes this as the hosting and delivery provider, and request-level operational logging is enabled on DigiCatalyst Systems' Cloudflare Workers account. This data keeps the site running and lets me investigate errors and abuse. It is not used to build a profile of you, and it is not linked to your booking.
• Page-view analytics: the site uses Cloudflare Web Analytics, a cookieless page-view count that Cloudflare adds to every page. When a page loads, a small script from Cloudflare reports which page it was, the page that linked to it, your country, your browser, operating system and device type, and how fast the page loaded, including the Core Web Vitals timings. It sets no cookie and stores nothing in your browser, and Cloudflare states that it collects no personal data through it and does not track anyone across websites. What I see is totals, such as how many visits a page had and how fast it loaded, for up to six months, never an individual visit, and it is never linked to a booking, a phone number or a contact record. There is no Google Analytics, no tag manager, and no advertising or social media pixel on any page, and nothing follows you to another website. Typefaces are compiled into the site and served from digicatalyst.ca, so loading a page does not call Google Fonts or any other font service.

3. Third-Party Processors

Eleven third-party services handle personal information connected to this site or to the published business number. Each is listed below with what it receives and why.

• Cal.com (booking): your name, email address, optional phone number, the email address of any guest you add, answers to the booking questions, booking notes, and the two attribution fields described in Section 2 are processed by Cal.com (https://cal.com) under Cal.com's privacy policy. The Cal.com script is not part of the page as delivered. It loads only when you open the booking dialog, or when the booking calendar on the contact page scrolls into view.
• Cloudflare (hosting, delivery, phone records, and backups): the site is served from Cloudflare's edge network, which processes the technical request data described in Section 2 under Cloudflare's privacy policy. It also runs Cloudflare Web Analytics, the cookieless page-view count described in Section 2. Cloudflare also holds DigiCatalyst Systems' own copy of the phone records: messages, call logs and the booking-reminder records in a Cloudflare D1 database, voicemail audio in private Cloudflare R2 storage, neither of them reachable from any public address. It carries the notice of each new booking from Cal.com to the automation that copies it into Notion, over an encrypted tunnel, and it stores the backups described in Section 6.
• VoIP.ms (phone and texting): the published business number runs on VoIP.ms (https://voip.ms), a Canadian telephone provider, on its Toronto point of presence. It carries the call or the text, including the reminder for a booked call, and it keeps its own record of your number, the message, and the call time under its privacy policy.
• Notion (contact records and call notes): the first text, answered call, or voicemail from a number creates a contact record in a private Notion workspace holding your number, the date of first contact, and a line for each message or call, such as the length of a voicemail. A call that rings out, lasts a few seconds, or arrives with no caller ID creates nothing there. A booking made through Cal.com creates or updates a contact record in the same workspace, with your name, email address, your mobile number if you gave one, the type and time of the call, the email address of any guest you added, your answers to the booking questions, your notes, and the two attribution fields. Keeping the number there means a later call or text from you reaches the same record. An automation I run on my own computer in Ontario makes the copy. My notes from the call, and its transcript if everyone agreed to a recording or a sales call's transcript or summary, sit on a page in that record. If I emailed you about your business's website, your record holds the business email address I found published and where I found it, and a line for each email between us with its date and subject, including a reply asking me to stop. An automation on the same computer writes those lines; the emails themselves stay in Zoho Mail. It is used to answer you and to keep track of the conversation, under Notion's privacy policy. It is never used for a mailing list and never shared.
• Anthropic (AI assistant): I use Claude, an AI assistant made by Anthropic, to help me work with contact records. It reads a record, including my call notes and the transcript of a call, to draft a summary of the call, a proposal, or a follow-up. Nothing it drafts reaches you until I have read it and sent it myself. Anthropic processes that text under its privacy policy, and my account is set so that it is not used to train Anthropic's models.
• Deepgram (call transcription): on a sales call, described in Section 2, the sound of the call streams to Deepgram (https://deepgram.com), which sends back the text as the call happens. Every request is opted out of Deepgram's model improvement program, and Deepgram states that it keeps data from an opted-out request only for as long as it takes to process it. The only copy kept afterwards is the transcript or summary on the contact record, described in Section 2.
• OpenRouter and TypeSafe (reading replies and calls): when you answer an outreach email, the subject and the first part of the words you wrote, without the email you are answering and without your email address, go through OpenRouter (https://openrouter.ai) to Jev, a model made by TypeSafe (https://typesafe.ai). Anything you put in the message goes too, such as a signature with your name or phone number. Jev picks one label for the reply, such as interested, a question, or a request to stop, and the label is kept on your contact record. It writes nothing, and nothing is sent to you because of it, except that a reply it reads as asking me to stop is treated as one. During a sales call, the same route carries the last few things the other person said, as text with no name or number attached, and Jev picks which prepared answer fits; it writes nothing. TypeSafe states that it does not train its models on what it receives and does not publish a fixed period for keeping it. Each handles that text under its own privacy policy.
• Zoho Mail (email): mail sent to support@digicatalyst.ca is received and stored in a Zoho Mail mailbox hosted in Canada. Outreach email is sent from kaustubh@digicatalystsystems.ca, a second address DigiCatalyst Systems uses only for outreach, and it and any answer to it are kept in a Zoho Mail mailbox hosted in Canada too, under the Zoho Mail privacy policy.
• Google (calendar): booked calls land in the Google calendar of the account that runs the booking page, and Cal.com sends the booking confirmation to that Gmail address, under Google's privacy policy.
• Zoho Books (invoicing): a client's name, business name, email address, billing address, invoices, and payment records are kept in Zoho Books, on its Canadian data center. Each invoice is emailed from it, under the Zoho Books privacy policy.
• Stripe (payment processing): client invoices paid by card are processed by Stripe under Stripe's own privacy policy. DigiCatalyst Systems does not store card numbers.

No other third party receives personal information collected through this site or through the published business number. The one exception is my Canadian bank, which receives an e-Transfer a client chooses to send, as Section 2 describes.

4. How I Use Your Information

I use the information I collect to:

• Confirm and conduct booked calls. Cal.com handles the calendar logistics; I receive the resulting calendar invite and email. If you gave a mobile number, I text it only to remind you of the call. It is also kept on your contact record, so a call or text you send later reaches the same record. I do not call or text it for anything else unless you contact me on it first, and never for marketing.
• Keep a record of each booked call, its notes, and its transcript if everyone agreed to a recording or a sales call's transcript or summary, with your contact record, so I can prepare for the call, write a proposal if you ask for one, and follow up on what we agreed.
• Reply to direct emails sent to support@digicatalyst.ca, and to answers to an outreach email.
• Quote, deliver, support, and invoice the Website Design and SEO service for clients who buy it.
• During a sales call, prompt me with the prepared answer that fits what you said, and keep the transcript or a summary of it with your business's contact record (Section 2).
• Answer calls and texts to the published business number, call or text you back when I could not pick up, and keep the thread of a conversation so a later message starts where the last one left off.
• Keep the site online and secure. Cloudflare request data is used to serve pages, diagnose errors, and investigate abuse. The request data is not used for marketing, profiling, or audience measurement.
• Count page views and measure how fast pages load, with Cloudflare Web Analytics (Section 2). It gives me totals only, which show which pages people read and whether they load quickly enough. It is never used to identify or contact anyone.
• Send marketing communications only if you have given express or implied consent under Canada's Anti-Spam Legislation (CASL). You can opt out of any marketing email by replying with the word "unsubscribe" or clicking the unsubscribe link in the message. A reply asking me to stop is recorded on your contact record automatically, and nothing further is sent.
• Reply to a text you send. Under CASL, texting a business is an inquiry, which gives implied consent to reply for six months from the date of your text. Texting STOP ends it before then, and that stop is recorded and honored automatically.
• Write to you about a call you booked. Under CASL, booking a call is an inquiry, which gives implied consent to write to you about it for six months from the date of the booking. Replying "unsubscribe" to any of those emails ends it before then.

5. How I Share Your Information

I do not sell, rent, or trade your personal information. The only third parties who receive your data are the processors named in Section 3, and only for the operational purpose described.

• Legal requirements: I may disclose information when required by Canadian law, by court order, or when necessary to protect against fraud or harm.
• Business transfers: if DigiCatalyst Systems is acquired or merged, your information may be one of the assets transferred. Any acquirer would be bound by the same privacy commitments.

6. Data Security and Retention

I use industry-standard security measures, including encryption in transit (HTTPS) and access controls on email and calendar systems, to protect your information. I retain personal information only as long as needed for the purpose it was collected, or as required by law.

• Cal.com bookings: retained by Cal.com under Cal.com's own retention policy. The confirmation email for each booking sits in the Gmail account behind the booking calendar and stays there until I delete it. A reminder text is kept with the phone records below, for the same three years.
• Email correspondence: retained in the Zoho Mail mailbox until deleted.
• Cloudflare request logs: edge request data and Workers operational logs are retained by Cloudflare under Cloudflare's own retention periods. I do not export them or keep a separate copy.
• Calls, texts, and voicemail: VoIP.ms keeps its own copy under its retention policy. Every morning DigiCatalyst Systems copies the message and call records, and any new voicemail audio, into the Cloudflare database and storage named in Section 3, and a nightly backup keeps a second copy for three years. Three years is the period a consent or complaint record has to survive, and the copy of a message you sent is the evidence of the consent you gave.
• Call recordings: the audio, and the copy of the transcript on my own computer, are deleted once the transcript is on your contact record, and never later than seven days after the call. That computer's disk is encrypted. The transcript on your record then follows the rule for contact records below.
• Transcripts of sales calls: the tool that transcribes the call keeps nothing once the call ends, and no audio is kept anywhere. The transcript or summary I put on the contact record follows the rule for contact records below.
• Contact records, call notes, and transcripts in Notion: deleted three years after we were last in touch, which is also how long a record of consent has to be kept. A client's records follow the client and billing rule below instead. Deleted sooner on request, subject to the note below. A nightly backup of these records is kept in Cloudflare for up to three years, so a deleted record leaves the backups as they age out.
• Booking and email copies on my own computer: the automations that copy a booking, or the date and subject of an outreach email, into Notion keep the booking or the email only when the copy fails, for 14 days, so it can be put right. That computer's backups are encrypted before they leave it and are kept for up to 90 days.
• A record that you opted out: if you text STOP, or ask by email to stop, the record that you did is kept even where the rest is deleted. It is the record that stops any further message reaching you, and CASL requires it to be provable.
• Client and billing records: invoices and payment records are kept in Zoho Books and cannot be deleted on request while the law requires them. Stripe retains card payment records under its own policy, and my bank keeps its record of each e-Transfer under its own. I keep invoices and client project files for as long as Canadian tax and record-keeping law requires.

Breach notification: if I become aware of a breach of security safeguards involving your personal information that creates a real risk of significant harm (PIPEDA standard) or otherwise meets a regulatory notification threshold under any applicable US state law, I will notify the Office of the Privacy Commissioner of Canada (where required), the relevant state authority, and you directly, without unreasonable delay and within timelines required by law.

7. International Data Transfers

Calls and texts to the business number are carried by VoIP.ms, a Canadian provider, on a Toronto point of presence, so the call itself stays in Canada. The stored copy does not: DigiCatalyst Systems' records of those calls and texts sit in Cloudflare and Notion, both in the United States, as described in Section 3.

The processors named in Section 3 (Anthropic, Cal.com, Cloudflare, Deepgram, Google, Notion, OpenRouter, Stripe, and TypeSafe) operate servers in the United States. Zoho Mail, Zoho Books, and VoIP.ms keep their copies in Canada. The automations that copy bookings and outreach email details into Notion run on my own computer in Ontario, and a recording of a booked call is transcribed there too: the audio never leaves that computer, and only the transcript goes to Notion and Anthropic. A sales call is different, on the phone or on video: its sound streams to Deepgram in the United States while we talk, as Section 2 describes, and nothing of it is kept there. By submitting information to the site, you consent to that data being transferred to and processed in the United States, where data protection laws may differ from your jurisdiction. I require contractual data-protection terms from each of these processors consistent with PIPEDA's accountability principle for cross-border transfers.

8. Your Privacy Rights (Canada and United States)

Depending on where you live, you may have specific rights regarding your personal information.

8.1 Canadian Residents (Under PIPEDA)

• Access: request a copy of the personal information I hold about you.
• Correction: request correction of any inaccurate or incomplete data.
• Withdraw consent: withdraw consent for the use of your information (subject to legal or contractual constraints).
• Deletion: request deletion of your personal data from my systems and from third-party processors where I have control to do so.

8.2 United States Residents

• Right to know: request disclosure of categories and specific personal information collected, sources, business purpose, and recipients.
• Right to delete: request deletion of your personal information, subject to legal exceptions.
• Right to correct: request correction of inaccurate personal information (CPRA, VCDPA, CPA, CTDPA, UCPA, OCPA, FDBR, MD, etc.).
• Right to opt out of sale or sharing: opt out of any sale or sharing for cross-context behavioral advertising. DigiCatalyst Systems does not sell personal information and does not share it for cross-context behavioral advertising.
• Right to limit use of sensitive personal information (CPRA-defined): DigiCatalyst Systems does not collect or use sensitive personal information for purposes beyond what is necessary to provide the service you booked or purchased.
• Right to non-discrimination: receive equal service regardless of whether you exercise your privacy rights.
• Global Privacy Control (GPC): DigiCatalyst Systems does not sell personal information and does not share it for cross-context behavioral advertising, so there is no sale or sharing for a GPC browser signal to stop. The site carries no script that reads a GPC signal, because there is no opt-out to apply. If that ever changes, this policy changes with it and the signal will be honored.

8.3 How to Exercise Your Rights

Email me at support@digicatalyst.ca with the subject line "Privacy request." A request about the phone line can also arrive as a text to that number, and it reaches the same person. I'll verify your identity (typically by confirming the email is the one tied to your booking or message) and respond within 30 days for Canadian requests, 45 days for US requests. If you are a customer of one of my clients and your request is about information you gave to their website, Section 10.4 explains who to ask.

9. Cookies and Tracking Technologies

This site sets no cookies of its own. Its one analytics script, Cloudflare Web Analytics (Section 2), works without cookies or any other storage in your browser, and there is no advertising or social pixel, so there are no analytics cookies and no tracking cookies on any page.

There is one exception: the Cal.com booking widget. When that widget loads, Cal.com may set its own cookies inside the embed to keep the booking session working. Those cookies belong to Cal.com and are governed by Cal.com's privacy policy. The widget loads only when you open the booking dialog, or when the booking calendar on the contact page scrolls into view, so nothing is set on a page you simply read. If you block cookies in your browser, the booking widget may not work.

No cookie consent banner is shown. With cookieless analytics and no advertising technology on the page, the only cookies in play are the strictly necessary ones the Cal.com booking widget sets when it loads. Global Privacy Control signals are covered in Section 8.2.

10. Data I Hold for Care Plan Clients

Read this section on its own. Everything above describes digicatalyst.ca and the information you give me when you visit it. This section describes a different flow: information that belongs to client businesses and to their own customers, sitting on systems I run or manage under a care plan. Nothing here is collected from visitors to this website, and nothing you submit here is ever added to a client's data. The statements above hold: the booking widget is still the only place on this site where you type personal information, and no third party beyond those named in Section 3 receives personal information collected through it.

If you are a customer of one of my clients and you filled in a form on their website, this section explains my role in that. Your relationship is with that business. They decide what to ask you and what to do with your answer. I keep their site running.

10.1 What I hold

• Site content and files: the pages, copy, images, and source code of the client's website.
• Backups: copies of the site and its files, kept so the site can be restored.
• Form submissions, on sites that have a form: many client sites carry a contact or booking form. When someone fills one in, the submission goes to the client, and I can see it too: in the mailbox or dashboard the form delivers to, and inside the backups. A submission typically holds the name, the email address or phone number, and whatever message that person chose to write. Some client sites have no form, and for those there are no submissions to hold.

10.2 Whose account the site lives in

This is not the same for every client, and the difference decides who controls the data.

• In an account DigiCatalyst Systems controls: some client sites run on Cloudflare under DigiCatalyst Systems' own account. For those, I have custody of the site and its backups.
• In an account the client owns: other client sites are deployed into a Cloudflare account the client owns. For those, the client has custody and I have access to do the work.

Each client is told which arrangement applies to their site, and it is recorded in their engagement paperwork. When an engagement ends, a site held under the first arrangement moves into an account the client owns.

10.3 My role, and what I will not do

For the personal information of a client's customers, the client is the business that decides why it is collected and what happens to it. I act as their service provider, on their instructions and for no other purpose. Concretely: I do not use a client's customer data for my own purposes, I do not sell or share it, I do not market to it, I do not add it to any list of mine, and I do not use it to train or improve any tool. I open it only when the work needs it, such as restoring a backup, fixing a form that has stopped sending, or moving a site to a new account.

10.4 Access, correction, and deletion requests

If you are a customer of one of my clients, the client is the party to ask. They hold the relationship with you and they decide the outcome, so write to them rather than to me. When a client receives a request like that, I help them locate the information in the systems I run and action it there. If you cannot work out who the client is, or you cannot reach them, email me at support@digicatalyst.ca and I will pass the request to them.

10.5 Retention

I hold a client's site data and backups for as long as their engagement runs. When it ends, the data is returned to the client and the copies I hold are deleted once the handover is complete. Backups rotate on a cycle, so a copy can sit in the backup system for a short period after deletion before it is overwritten. Records that Canadian tax and record-keeping law requires me to keep, such as invoices, are kept for the period the law requires.

10.6 Who else touches a client site

The same providers named in Section 3 do this work. Cloudflare hosts and delivers client sites and stores their backups. Mail forwarded from a client's site or its forms lands in the Zoho Mail mailbox named in Section 3. Cal.com runs booking where a client's site uses it. Zoho Books issues that client's invoices, and Stripe processes the ones paid by card. Where a client has wired their site to a service of their own choosing, that service is theirs, under their arrangement with it, and this policy does not cover it.

10.7 If something goes wrong

If I become aware of a breach of security safeguards affecting data I hold for a client, I notify that client without unreasonable delay and tell them what I know. The client decides whether and how to notify the people affected and any regulator, because the client is the business those people dealt with, and I help them do it. The breach commitment in Section 6, which covers information you gave me through this website, is separate and still applies.

11. Changes to This Privacy Policy

I may update this policy periodically. Any material change will be reflected by an updated date at the top of this page. If the change affects how I handle data you've already given me, I'll email you directly using the address on file.

The September 13, 2026 version narrowed this policy to the services DigiCatalyst Systems actually offers. Descriptions of SMS and AI phone services were removed: both were withdrawn on September 6, 2026, neither was ever sold to a customer, and no personal information was ever collected through either one. A reference to website analytics was also removed, because the site then ran no analytics tool.

The same version added Section 10, which sets out the data DigiCatalyst Systems holds on behalf of care plan clients, including the form submissions that arrive from those clients' own customers. That work predates the section. The disclosure is new, what it describes is not.

The September 17, 2026 version added the published business phone number as a collection path: what a call, a text, or a voicemail leaves behind, the automated after-hours reply and the STOP that ends it, and the three companies that carry or hold it, VoIP.ms, Cloudflare, and Notion. A call I answer and a voicemail create a contact record the same way a text does. Call recording was switched off on the same date. The account holds no recordings: one call reached the line while the setting was on, and nothing was kept, used, or disclosed.

The September 22, 2026 version added text reminders for booked calls: the optional mobile number on the booking form, the reminder sent from the business number on the day of the call, and the booking details copied into the phone records to send it. It also corrected where email is kept: support@digicatalyst.ca is a Zoho Mail mailbox in Canada, not Google Workspace, and booking confirmations reach the Gmail account behind the booking calendar.

The September 23, 2026 version added the contact record each booking now creates in Notion: what is copied, including the mobile number and any guest's email address, and the automation on DigiCatalyst Systems' own computer in Ontario that copies it. It also added the notes typed during a booked call, set a three-year limit on contact records and call notes, and corrected the number of providers named in Section 3 from six to seven.

The September 24, 2026 version added outreach email: the separate address it is sent from, the date and subject of each email kept on the contact record, and a reply asking me to stop recorded automatically. The automation that records them runs on the same computer in Ontario.

A second revision the same day changed booked video calls: a call is recorded only when everyone on it agrees at the start, it is transcribed on DigiCatalyst Systems' own computer in Ontario, and the audio is deleted once the transcript is on the contact record. No call was recorded before this revision, and calls to the business number are still not recorded. It also named Anthropic, whose AI assistant Claude reads contact records and call notes to draft summaries and proposals, as an eighth provider in Section 3. Claude read call notes before this revision too. The disclosure is new, what it describes is not.

The September 27, 2026 version corrected how clients are invoiced and pay. Invoices are issued from Zoho Books, on its Canadian data center, not from Stripe. Section 3 now names Zoho Books as a ninth provider. A client can pay by Interac e-Transfer into DigiCatalyst Systems' Canadian business bank account, or by card through Stripe. Zoho Books issued invoices before this version too. The disclosure is new, what it describes is not.

The September 29, 2026 version corrected what the site measures. Cloudflare Web Analytics, the cookieless page-view count described in Section 2, has run on every page since September 20, 2026, when the site's security settings stopped blocking the script Cloudflare adds. Every version in force from September 20, 2026 until this one, those of September 17, 22, 23, 24 and 27, said the site ran no analytics, which was wrong from that date. This version describes it in Sections 2, 3 and 9, and adds the Privacy Commissioner of Canada to Section 13.

The October 8, 2026 version named OpenRouter and TypeSafe in Sections 3 and 7 as a tenth and eleventh provider. When you answer an outreach email, Jev, a decision model made by TypeSafe, reads what you wrote through OpenRouter and picks a label for the reply. Both operate servers in the United States. Nothing is sent to anyone because of the label, and a reply read as asking me to stop is treated as one. Reading replies this way starts after this version is published, so no reply was read this way before it.

The October 9, 2026 version described sales calls: calls I make to businesses from the published number, calls back from those businesses, the website call and agency partner call booked on this site, and the readout call for a written audit bought on audits.digicatalyst.ca. These calls now use a note-taking tool instead of a recording. While we talk, the sound of both sides goes to Deepgram for transcription and what the other person says goes as text to Jev through OpenRouter, to prompt me with a prepared answer. No audio is recorded or kept, and the transcript or a summary of it is kept on the contact record. Section 3 names Deepgram as a twelfth provider. No call was transcribed this way before this version was published.

12. Children's Privacy

The services are intended for business owners and professionals, not children. I do not knowingly collect personal information from anyone under 18. If I learn that I've inadvertently collected information from a minor, I'll delete it.

13. Contact

For privacy questions, requests, or concerns, contact me at:

Kaustubh Ghodke o/a DigiCatalyst Systems

Email: support@digicatalyst.ca

BN: 779120153 RT0001

Privacy Officer: Kaustubh Ghodke (designated under PIPEDA Schedule 1, Principle 1: Accountability).

Toronto, Ontario, Canada

If you are not satisfied with how I handle your request or concern, you can complain to the Office of the Privacy Commissioner of Canada at priv.gc.ca or 1-800-282-1376.