Privacy
What we collect, and what we do with it.
This site has one form on it. This page explains what that form collects, where it goes, who else can see it, and how to have it deleted.
Not yet confirmed
Everything else on this page describes what this website actually does, and was checked against the code that runs it. These 5 items have not been confirmed, and are listed here rather than written as though they had been.
The legal entity and its registered address
A privacy notice has to say who the accountable organisation is and where to reach it. Nothing in this repository knows the incorporated name or the business address, so neither is stated anywhere on the page rather than being guessed at.
How long a lead is kept
The page describes the retention that is configured today, which is none: the table has no expiry and nothing deletes a lead. A period has to be chosen and then implemented, because a policy that promises a deletion nothing performs is worse than no policy.
Who answers a privacy request
Requests currently go to the general mailbox, which is also a placeholder. Larger organisations name a privacy officer; whether that is warranted here is the business's call.
Whether the AI assistant endpoint is in use
The deployed stack routes an AI service that would send text to Groq for processing. No page on this site calls it, so the page says visitor input does not reach it — true of the website as it stands, and worth re-checking before publishing in case something else does.
A review against PIPEDA by someone qualified to give it
This page was written by reading the code, not the statute. It aims to describe the system accurately and completely; whether that description discharges the obligations that apply to this business is a legal question.
Statements about how the system behaves were last checked against the code on 6 September 2026.
What we collect
Only what the form asks for.
There is no tracking on this site, so with one exception below, we hold nothing about you that you did not type into a form and send.
Required, when you send us a message
Your name, an email address for the reply, what the enquiry is about — bots and voice, consulting, cybersecurity or something else — and your message.
Optional, if you choose to answer
Your company name, your timeline — when you would want the work done — how many people are at your company, and a short description of what is running today: the models, clouds and data stores involved.
These four exist to make a first call useful rather than introductory. Every one of them can be left blank and the form still sends, and you can book a call without answering any of them.
Your IP address, briefly
The one thing you do not type. When a message is submitted, the address it came from is counted for a few minutes so that the same connection cannot flood the form. It is not written to the database and it is not stored alongside your message.
A hidden field, to catch bots
The form carries a field that is invisible to people and attractive to automated submitters. If it is filled in, the submission is discarded without being stored. A real visitor never sees it and never fills it.
Why
To reply, and to prepare for the call.
We use what you send to answer you, and to prepare for a conversation if we have one. The optional questions are there so that whoever takes the call can read up on your systems beforehand instead of spending the first fifteen minutes establishing what they are.
We do not sell it, rent it, or use it for advertising. We do not add you to a mailing list. There is no mailing list.
Where it goes
Two places, both in the United States.
A database record
Each submission is written to an Amazon DynamoDB table in Amazon's us-east-1 region, in Northern Virginia. If you are in Canada or the EU, that means your information is stored in the United States and is subject to the laws that apply there, including lawful access by US authorities.
An email to us
The same information is emailed to our own mailbox through Amazon SES so that someone sees it promptly. The email is addressed so that replying to it replies to you.
Operational logs
The function that receives the form writes technical logs — errors and timings — to Amazon CloudWatch, where they are deleted automatically after one month. This site keeps no web access logs at all.
How long we keep it
Honestly: at present, indefinitely. A lead is treated as a business record and nothing currently deletes one automatically. We would rather say that plainly than publish a retention period that no part of the system enforces. Choosing one, and implementing it, is listed in the notice at the top of this page as outstanding.
In the meantime, you can ask us to delete yours at any time and we will, which is the part that is actually under your control.
Who else is involved
Three companies, in different tenses.
We keep this list short on purpose. Each entry says plainly whether it applies to you today.
Amazon Web Services — now
Amazon Web Services hosts this site, stores the database record and sends the notification email. They process it on our instructions in order to provide those services.
Calendly — only if you book
Booking a call is handled by Calendly, embedded on our contact page and linked from our consulting page. If you book, the name, email and any answers you give in their form go to Calendly directly, under their privacy policy rather than this one. If you never book, nothing about you reaches them.
ElevenLabs — not yet, and here is the notice in advance
We are building a voice assistant that would let you talk to this site, using ElevenLabs. It is not switched on. No audio from this website reaches them today, and this paragraph exists so that the disclosure is already written when it does.
When it goes live: speaking to the assistant would send your audio, and a transcript of it, to ElevenLabs for processing. They are a third-party processor with no Canadian data region — processing happens in the United States and the European Union — so using the voice assistant would mean your voice leaving Canada. It will be an optional feature you have to start deliberately, the text form will always remain, and we intend to configure it not to retain recordings. We will update this page before it is available, not after.
What is not here
There is no analytics on this site. No Google Analytics, no tag manager, no advertising pixel, no session recorder, no heatmap. We do not know how many people read this page.
We set no cookies. Choosing light or dark mode stores that one preference in your own browser, where it stays; it is never sent to us. The conversation demos on the site are scripted and run entirely in your browser — nothing you click in them is transmitted anywhere.
Your choices
Ask us, and we will do it.
You can ask for a copy of what we hold about you, ask us to correct it, or ask us to delete it. You can withdraw a request to be contacted at any time. Email hello@29eleventech.com and say which.
There is no account to log into and no automated portal — a person reads the mailbox and acts on it. If you are not satisfied with how we handle a request, you can complain to the Office of the Privacy Commissioner of Canada.
Changes
We will date them.
If what we collect changes, this page changes with it, and the date above moves. The change that is coming is the voice assistant, and it is described above already.