Privacy policy

SensaAI operates SensaDial at dial.sensaai.ca on behalf of the businesses that use it to run calling campaigns (our clients; in the current pilot, Preeminent Marketing). For the people a client asks us to call, the client decides who is called and why, and SensaAI processes their information on the client’s behalf. For the people who sign in to SensaDial, SensaAI is responsible for their information.

Questions, requests and complaints about privacy go to team@sensaai.ca.

Accounts are created by SensaAI for our staff and for our clients’ staff; there is no public sign-up. When you sign in we handle:

• Your account: your name and email address, your role in each workspace, and whether you are a SensaAI administrator.
• Google sign-in: if you choose “Continue with Google”, Google tells us your name, email address and profile picture link, and, for a Google Workspace account, its domain. We use the domain only to check whether a SensaAI administrator signed in with a sensaai.ca account.
• Sessions (auth_sessions): when each session started and how you signed in, so a session can expire after 7 days and administrator powers only apply to the right kind of sign-in.
• Sign-in attempts (login_attempts and code requests): the email entered, the method, the time and whether it succeeded, so we can lock an account for 15 minutes after 5 failed attempts and limit how often codes are sent.
• Sign-in events (sign_in_events): refused Google sign-ins and each emergency password sign-in by an administrator, so we can review them for security.

Google sign-in asks only for the basic scopes openid, email and profile. We use that information only to sign you in and to check your access. SensaDial does not read your Gmail, Google Drive, contacts or any other Google data, and we do not sell Google user data, use it for advertising or share it except with the service providers listed below who run SensaDial for us.

Separately, a client can connect their own Google Calendar from Settings, with its own consent screen. SensaDial then checks that calendar’s free and busy times, lists its calendars so the client can pick one, and creates meeting invitations with a Google Meet link when a call books a meeting. The access token is stored encrypted and the client can disconnect it at any time from Settings or from their Google account.

SensaDial’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.

To run a client’s calling campaigns, SensaDial processes:

• Lead details the client uploads: name, company, phone number, email, industry, city and province or state, notes, and the number’s type (mobile or landline).
• Consent records: where and when the person agreed to be called and the evidence of it. SensaDial will not call a number that needs consent and has none.
• Call records: the recording, the transcript, the outcome, answers given on the call (for example a preferred callback time) and any meeting booked. Every call says at the start that it is made by an AI assistant and is recorded.
• The do-not-call list: numbers of people who asked not to be called again, so they are never called again.

We use this information only to place the client’s calls, book meetings, send confirmation emails and show the client the results.

• Call recordings and transcripts: 12 months, then deleted.
• Do-not-call entries: 3 years and 14 days from the request.
• Consent records: as long as the lead exists, plus 3 years.
• Session records: removed once they are more than 8 days old. Sign-in attempts and sign-in events are kept for security review until we delete them, and deleted on request.
• Accounts: until SensaAI removes the account.

These companies process information for us, only to run SensaDial:

• Supabase: database, sign-in, and storage for uploaded lead files and call recordings.
• Railway: hosting for the web app and the background worker.
• ElevenLabs: the AI voice that holds the conversation, its recording and transcript.
• Telnyx and Twilio: phone numbers and call connection; Twilio also checks whether a number is mobile or landline.
• Google: sign-in, and the client’s calendar when they connect it.
• Resend: sign-in codes and meeting confirmation emails.
• Anthropic: analysis of call transcripts to improve the call script.
• Sentry: error reports, with phone numbers, emails and transcripts removed before they are sent.
• Slack: internal alerts, which carry counts and ids, not personal details.

SensaDial’s database, files and servers are in the United States (US East). Our service providers may process information in other countries. Information stored outside Canada is subject to the laws of the country where it is held.

Under Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA) you can ask to see the personal information we hold about you, to correct it, or to have it deleted, and you can withdraw consent to be called. If you were called on a client’s behalf, we will delete your lead record and its calls and recordings, and keep only your number on the do-not-call list so you are not called again.

Email team@sensaai.ca with your name and the phone number or email address concerned. We answer within 30 days. If you are not satisfied with our answer you can contact the Office of the Privacy Commissioner of Canada.

We will update this page when SensaDial’s handling of personal information changes, and change the date at the top.