Privacy Policy
Last updated: November 14, 2026
On this page
This Privacy Policy explains how Common Good Labs Inc. (“Common Good Labs,” “we,” “us,” or “our”), the operator of the Clerra platform (“Clerra,” the “Service”), collects, uses, discloses, and safeguards personal information. It covers our website, the Clerra web application and client portal, our mobile apps, the Clerra apps for Microsoft Teams and Zoom, the email, calendar and document-storage connections and the FreshBooks connection described in section 6, and the Clerra browser extension. We handle personal information in accordance with Canada’s Personal Information Protection and Electronic Documents Act (PIPEDA) and, where they apply, provincial private-sector privacy laws, including Québec’s Act respecting the protection of personal information in the private sector and the Personal Information Protection Acts of Alberta and British Columbia.
1. Who this policy applies to, and our role
Clerra serves two groups of people, and our role differs for each:
- Firm users — accounting and bookkeeping firms (each, a “Firm”) and their staff who subscribe to and use Clerra. For account, billing, and usage information about Firm users, Common Good Labs is the organization responsible for that information.
- Firm clients — the clients of those Firms, including individuals who use a Firm’s client portal. Information that a Firm enters or uploads, or that a Firm’s clients submit through the portal (“Customer Data”), is collected by and under the control of that Firm. The Firm decides what it collects, why, how long it keeps it, and with whom it is shared. Common Good Labs acts only as the Firm’s service provider, processing Customer Data on the Firm’s behalf and on its instructions. The Firm is accountable for that information under privacy law, and the Firm’s own privacy practices govern how it is handled.
This policy also covers people who visit our website or contact us, and the limited business information described in section 2 about prospective clients that a Firm researches.
2. Information we collect
- Account information: name, email address, phone number (if you choose to sign in by text), firm name, role, and authentication data. Passwords are stored only as salted hashes. Two-factor secrets are stored where you enable two-factor authentication.
- Customer Data: information Firms enter or upload about their own clients, such as names, contact details, business numbers, tax and compliance attributes, documents (including receipts, bills, statements and returns), notes, messages, invoices, and time records.
- Electronic signature and consent records: when someone signs a document or gives consent through the Service, we record the signer’s name, email address and signature (including any initials applied), the date and time of their consent and signature, IP address, device and browser details, the wording and version of the disclosure they agreed to, and a fingerprint of the signed document. This creates an evidentiary record of the signature or consent.
- Billing information: subscription plan and status, and a billing contact. Payment card details are collected and processed directly by our third-party payment processor. We do not store full card numbers.
- Usage and technical data: log data, device and browser information, IP address, and actions recorded in the audit trail (such as sign-ins, document access, deletions, permission changes, and exports), kept for security and accountability. See section 6 for diagnostic data.
- Communications: messages exchanged between a Firm and its clients within the Service, conversations with our in-app support assistant, and any correspondence you send us.
- Mobile app data: if you install a Clerra mobile app and allow notifications, a device push token and basic device type, used to deliver notifications.
- Vehicle log: if you keep a vehicle log in your Firm’s client portal, Clerra stores the drives you record or type in (the date, start and end times, the distance in kilometres, the vehicle, the purpose, and whether the drive was business or personal), the names of places you save, and your odometer readings and their photos. When you press Start drive, Clerra uses your phone’s location only while that drive is running and Clerra is open on your screen. It never collects location in the background or when Clerra is closed, and it measures nothing until you press Start drive. The individual GPS readings stay on your phone and are cleared when the drive ends. Only the total distance and the drive’s start and end points, rounded to about 100 metres so a saved place such as home or work can be named, are saved. No route is stored, and no mapping or location service receives your location. Your vehicle log is stored in Canada and can be seen only by you, anyone else with portal access to the same client account, and your Firm’s staff. You can change or delete any drive, saved place or odometer reading at any time; a deleted reading’s photo stays with the documents you’ve shared with your Firm, and your Firm can delete it.
- Clerra Shift (an employee’s time clock): if a business that is a client of your Firm adds you to its team in Clerra Shift, Clerra stores your name, the email address (and, if given, the mobile number) the business entered for you to sign in, and the time records you make in the Clerra Shift app or website: when you clock in and out and take breaks, the job you worked on, your time-off requests and balances, and the fixes you ask for. The business, the managers it names and its accounting Firm can see these records; other employees can’t. Pay stubs and tax slips the business or Firm uploads for you are shown only to you and to them. If the business lets you log drives, Clerra uses your phone’s location only while a drive you started is running, exactly as described for the vehicle log above: never on the clock, never in the background, and only the distance and the rounded start and end points are saved. Clerra Shift doesn’t record where you are when you clock in or out. To leave, ask the business to remove you from its team; to have your sign-in deleted, see Delete your account.
- Microsoft Teams data: if you add the Clerra app in Microsoft Teams, the Teams and Microsoft identifiers needed to deliver your notifications there and, where your Firm uses Teams meeting notes, the transcripts and notes of client meetings, as described in section 6.
- Zoom data: if you connect your Zoom account, your Zoom user ID, account ID and email address and Clerra’s encrypted access to your Zoom and, for meetings you host with a client, the transcript, who attended and, where your Firm uses AI meeting notes, the notes, as described in section 6.
- FreshBooks data: if your Firm connects FreshBooks, the FreshBooks businesses that login can reach and Clerra’s encrypted access to them, the figures shown on a linked client’s record, and, where your Firm switches them on, the invoices, payments and receipts exchanged with FreshBooks, as described in section 6.
- Prospect information: where a Firm uses the Service’s prospect-research tools, publicly available business information about the prospective clients the Firm researches, such as business name, website, industry, and size estimates.
The Clerra browser extension accesses only your Clerra account data, such as timers, clients, and reminders. It does not read the web pages you visit or collect your browsing history.
3. How we use information
- To provide, operate, maintain, secure, and improve the Service;
- To compute filing deadlines, generate work, and deliver the features a Firm uses;
- To authenticate users, enforce access controls, and maintain the audit trail;
- To process subscriptions and payments and send transactional messages (e.g. invitations, document requests, reminders, notifications);
- To provide support and respond to enquiries;
- To detect, investigate, and prevent fraud, abuse, and security incidents;
- To comply with legal obligations and enforce our Terms of Service.
We may create aggregated or de-identified information from the use of the Service, for example usage statistics, to operate and improve it. We do not attempt to re-identify de-identified information, and we do not disclose it in a form that identifies any Firm or individual.
We do not sell personal information. We do not use Customer Data for advertising. We do not use Customer Data or Google user data to train artificial-intelligence or machine-learning models, whether ours or anyone else’s.
We do not make decisions about individuals based exclusively on automated processing. Automated features, such as computed deadlines and email triage, produce suggestions and outputs for Firm staff to review. The Firm remains responsible for the decisions it makes.
If we send you promotional messages, we do so in accordance with Canada’s Anti-Spam Legislation, and every such message includes a way to unsubscribe. Service and account messages, such as security notices and changes to our terms, are sent regardless of marketing preferences.
4. Consent, and the Firm's responsibilities
We collect, use, and disclose personal information with consent (express or implied) or as otherwise permitted or required by law.
Because each Firm controls its Customer Data, each Firm is responsible for:
- having a lawful basis and any consents required to collect its clients’ information and enter it into the Service;
- informing its clients that it uses service providers such as Clerra, including that some processing occurs outside Canada (section 5);
- deciding which information to collect and upload, and limiting it to what its engagement requires;
- obtaining any additional consent the law requires for sensitive information it uploads, such as health information contained in medical receipts or disability tax credit forms;
- responding to its clients’ privacy requests and complaints;
- controlling which staff and clients have access, and removing access promptly when a person leaves or a relationship ends; and
- complying with Canada’s Anti-Spam Legislation and other laws for messages the Firm sends to its clients through the Service.
5. Where information is stored and processed
Customer Data and Firm account data are stored in Canada, in data centres in a Canadian cloud region (Montréal, Québec). This includes our database, sign-in system, file storage, and backups. The Clerra application also runs on servers in Canada (Montréal). Static website content, such as images and scripts, may be delivered from a global content-delivery network.
Some of our service providers process information outside Canada, mainly in the United States. Section 6 lists them. Information processed outside Canada is subject to the laws of that country, and may be accessible to its courts, law-enforcement, and national-security authorities. Our service providers’ personnel may also access information from outside Canada to support and maintain their services, subject to their contractual obligations to us. In limited circumstances, such as a regional outage, a provider may temporarily process information in another region. We protect cross-border processing with contractual and technical safeguards.
6. Service providers (sub-processors)
We rely on a small number of service providers to operate the Service. We describe them here by category and function. A current, named list is available to Firm administrators on request.
- Cloud infrastructure — database, authentication, file storage, and backups, hosted in Canada (Montréal, Québec).
- Application hosting — hosted in Canada (Montréal, Québec), with static content delivered from a global content-delivery network.
- AI processing — our third-party AI provider, in the United States, processes content for the following features:
- email triage of messages clients send to a Firm, which a Firm administrator can switch off;
- the in-app support assistant;
- prospect research, when a staff member requests it for a prospective client;
- notes from a client meeting in Microsoft Teams, Google Meet or Zoom (a summary, action items and what the client promised to send), where a Firm has switched on AI meeting notes; and
- other on-demand features a Firm user chooses to run, which may include client names and the client details the feature needs.
- Payment processing — subscription billing and, where a Firm accepts online payment, its clients’ payments of invoices and proposals. Card details are handled directly by the processor and never stored on our servers. The processor may process information outside Canada.
- Transactional email delivery — United States.
- SMS delivery — one-time sign-in codes, for users who choose to sign in by text (United States).
- Mobile push notifications — delivers short notification text to the mobile app (United States).
- Document processing — scanning uploaded files for viruses, and converting tax-authority PDF forms so they can be filled and signed. Both run on servers in Canada (Toronto and Montréal) and keep no copy of the file.
- Bot and abuse protection — on sign-in and public forms (United States).
- Website analytics — counts visits to our public website, without cookies and without identifying you personally (United States). It is not used inside the Service.
- Background-job orchestration — schedules work such as generating a complete client-file export, scanning an upload or keeping a connected mailbox in step. It runs on our own servers in Canada (Toronto) and receives only record identifiers and counts, never the contents of client records, documents or email.
- Mailbox and calendar sync — the background work that keeps a connected Microsoft 365 or Google mailbox and calendar in step with Clerra runs on our own servers in Canada (Toronto), which read from the provider and write to Clerra’s database in Canada and keep no copy of their own.
- Error monitoring & diagnostics — captures errors and performance data, with technical context such as user and request identifiers, IP address, browser details, and details of the request that caused the error. For a sample of sessions, and for sessions where an error occurs, it also records a reconstruction of on-screen interactions, with on-screen text and form inputs masked. We use this to keep the Service reliable and secure (United States).
- Optional integrations a Firm connects — such as accounting software, tax software, or a third-party sign-in. When a Firm connects an integration, information flows to that provider at the Firm’s direction and is handled under that provider’s own terms and privacy policy. We are not responsible for that provider’s practices.
- Microsoft 365 mailbox and calendar — where a staff member connects their own Microsoft 365 / Outlook account, Clerra keeps a copy of that mailbox (message text and formatting, senders and recipients, subjects, dates, folders and read state — the last 90 days, plus any older mail they choose to load) and of their Outlook calendar, stored in Canada, so it can be shown and searched in the Service and kept in step with Microsoft both ways. Attachments stay with Microsoft until the staff member saves one to a client’s file. A conversation with one of a client’s known email addresses (or an address the Firm confirmed before) is linked to that client automatically, and staff who can see that client can then see it; the rest of the mailbox is visible only to that staff member (and to anyone they hand a conversation to). A staff member can turn automatic linking off for their own mailbox, or mark a conversation personal so it is never linked. Disconnecting the account deletes Clerra’s copy of the mailbox and calendar, except conversations linked to a client, which stay on that client’s record. The mailbox itself, at Microsoft, is never changed by disconnecting. Where a Firm switches on Next steps, a conversation a staff member opens (never Junk or Deleted mail) is sent to our AI provider to suggest calendar items, a reply and to-dos, on the terms described above. Where a Firm switches on automatic job filing, a new email from a client is sent to the Firm’s configured AI model to pick the job it belongs to, on the same terms. Connecting can also add a separate “Clerra” calendar to the staff member’s Outlook with their deadlines, jobs and time off, if they choose.
- Gmail / Google Workspace mailbox — where a staff member connects their own Gmail or Google Workspace account, Clerra keeps a copy of that mailbox (message text and formatting, senders and recipients, subjects, dates, labels and read state — the last 90 days, and new mail from then on; messages in Spam are kept without their content), stored in Canada, so it can be shown and searched in the Service and kept in step with Gmail both ways. What the staff member does in Clerra — sending, replying, archiving, labelling, moving to Trash or Spam, marking read — is done in their Gmail account. Attachments stay with Google until the staff member saves one to a client’s file. Linking to clients, who can see a conversation, Next steps, automatic job filing and disconnecting work exactly as described for Microsoft 365 above: disconnecting deletes Clerra’s copy (except conversations linked to a client) and revokes Clerra’s access at Google, and never changes the mailbox at Google.
- Google Calendar — where a staff member connects their Google account and the Firm has Google Calendar on, Clerra asks Google for three calendar permissions and uses each only for this:
calendar.events.owned, to read the events on calendars the staff member owns (title, times, location, attendees, the meeting link and their answers) so they show on the staff member’s calendar in Clerra, and to create, change or cancel an event, with its invitations and a Google Meet link, when the staff member does so in Clerra;calendar.app.created, to make one separate “Clerra” calendar in their Google Calendar and keep their deadlines, jobs, approved time off and team events there, if they choose; andcalendar.freebusy, to see when colleagues are busy (times only, never titles) for “Find a time”. Clerra keeps a copy of those events, stored in Canada, kept in step with Google both ways. Clerra never reads, changes or deletes events on calendars the staff member doesn’t own, other than the “Clerra” calendar. Disconnecting the account deletes Clerra’s copy of the calendar; the calendar itself, at Google, is not changed by disconnecting. - Google Meet meeting notes — where a Firm turns on Google Meet meeting notes and a staff member turns them on for their own Google account, Clerra uses the
meetings.space.readonlypermission to learn when a transcript of a Google Meet meeting that staff member organized is ready, and to read that transcript, who joined and the meeting’s details. Clerra matches the meeting to a client through the invitation on the staff member’s own calendar. When one of a client’s contacts was invited, Clerra saves the transcript, with the meeting’s title and times and attendees’ names and email addresses, to that client’s record in Canada. Meetings with no client in them are never stored, unless a Company Admin has switched on saving team meetings (then only attendees and the Firm’s Company Admins can open them), and recordings stay with Google. Where the Firm has switched on AI meeting notes, the transcript is sent to our AI provider (United States) to write a summary, action items and what the client promised to send, on the terms described above. Saved transcripts and notes are Customer Data, kept and deleted like the rest of the client’s record (section 10). Turning meeting notes off, or disconnecting the Google account, stops new meetings from being read; meetings already saved stay on the client’s record. - A Firm’s own document storage (OneDrive, SharePoint, Google Drive or Dropbox) — where a Firm connects its own storage, client documents are kept there instead of in Clerra’s vault; files already in the vault stay there until the Firm moves them. A file that reaches the Firm through Clerra (for example a portal upload or a saved email attachment) is held briefly on our servers in Canada so it can be scanned for viruses, written to the Firm’s storage and checked, and is then deleted from our servers, within 24 hours. Clerra keeps only what it needs to show and manage each file there (its name, folder, size and identifiers). Clerra does keep, on its servers in Canada and with no set end date, a PDF copy of each file a staff member sends for signature from the Firm’s storage (including drafts never sent and requests that ended unsigned, until a staff member discards the draft), the signed PDF and certificate of completion of every document signed through Clerra, and any complete client-file PDF the Firm generates, even when a copy is also saved to the Firm’s storage. Files in the Firm’s storage are held wherever that provider stores them, which may be outside Canada (with Google Drive or Dropbox, for example, the provider decides where files are kept, and Clerra can’t promise Canada). With Google Drive, Clerra can see only the folders and files it created, or that a staff member chooses to add with Google’s file picker. Clerra does not back up files kept in the Firm’s own storage: their backups and retention follow the Firm’s Microsoft, Google or Dropbox settings. Clerra’s own records, including the list of those files, are backed up as usual. Disconnecting the storage leaves every file in it where it is.
- Microsoft Teams — where a staff member adds the Clerra app in Microsoft Teams, Clerra keeps what it needs to send them notifications in a personal chat: the Teams chat (conversation) ID and the address Microsoft gives for it, their Microsoft user ID and organization (tenant) ID, and their Microsoft sign-in name, which is used to match them to their Clerra account. These are stored in Canada. The text of each notification, which can include a client’s name, is delivered through Microsoft and kept in the staff member’s Teams chat under their organization’s Microsoft 365 settings. Removing the app, or typing “sign out” in the chat, stops all messages to that chat. Where a Firm turns on Microsoft Teams meetings and a staff member connects their own Microsoft account, Clerra keeps that account’s Microsoft user ID, email address and an encrypted access token, stored in Canada, and reads the transcripts of Teams meetings that staff member organizes. When one of a client’s contacts attended, Clerra saves the transcript, with the meeting’s subject, times and attendees’ names and email addresses, to that client’s record in Canada. Meetings with no client in them are never stored, and recordings stay with Microsoft. Where the Firm has switched on AI meeting notes, the transcript is sent to our AI provider (United States) to write a summary, action items and what the client promised to send, on the terms described above. Saved transcripts and notes are Customer Data, kept and deleted like the rest of the client’s record (section 10). Disconnecting the Microsoft account deletes Clerra’s access token and stops new meetings from being read; meetings already saved stay on the client’s record.
- Zoom — where a Firm turns on Zoom and a staff member connects their own Zoom account (with Connect Zoom on their Clerra profile, or by adding Clerra from the Zoom App Marketplace and then confirming in Clerra which Zoom account to connect), Clerra asks Zoom for three read-only permissions and uses each only for this:
user:read:user, to learn who connected (their Zoom user ID, account ID and email address);cloud_recording:read:list_recording_files, to find and download the transcript of a cloud recording of a meeting that staff member hosts; andmeeting:read:list_past_participants, to see who joined that meeting (names, and email addresses where Zoom provides them), which, with the invitation in the staff member’s connected calendar, is how the meeting is matched to a client. Clerra keeps that Zoom user ID, account ID and email address, the permissions granted, when the account was connected and last saved a meeting, and Zoom’s access and refresh tokens (encrypted), stored in Canada. Clerra reads only meetings hosted by the staff member who connected, with their own connection. It never joins, records, posts to, changes or deletes a meeting, a recording or anything else in Zoom, and recordings stay in Zoom’s cloud. When one of a client’s contacts was in the meeting, Clerra saves the transcript, with the meeting’s topic and times, attendees’ names and email addresses, the meeting link and a link to Zoom’s recording page, to that client’s record in Canada. Meetings with no client in them are never stored, unless a Company Admin has switched on saving team meetings: then a meeting in which every invitee is on the Firm’s staff is saved on no client’s record, and only its attendees and the Firm’s Company Admins can open it. Where the Firm has switched on AI meeting notes, the transcript is sent to our AI provider (United States) to write a summary, what was decided, action items, what the client said they would send and any dates mentioned, on the terms described above. Our background-job orchestration system (our own servers in Canada, Toronto) receives only record identifiers, including Zoom’s meeting and recording-file identifiers, never a transcript, a name or a meeting topic. Saved transcripts and notes are Customer Data, kept and deleted like the rest of the client’s record (section 10). Disconnecting Zoom in Clerra (or a Firm turning Zoom off) ends Clerra’s access at Zoom and deletes the stored tokens and Zoom identifiers immediately; removing Clerra from the Zoom account (Zoom then notifies Clerra) deletes them immediately too. Either way new meetings stop being read, and meetings already saved stay on the client’s record and are deleted with it. To ask us to delete information Clerra holds from Zoom, write to support@clerra.ca or our Privacy Officer (section 16); see also Your rights (section 11). - FreshBooks — where a Firm is offered FreshBooks and someone with the Integrations permission connects a FreshBooks login, Clerra asks FreshBooks for read-only permissions to the profile, clients, invoices, payments, bills, bill payments, vendors, taxes and reports of the businesses that login can reach, and lists those businesses so each can be linked to one client record. For a linked business Clerra reads, and keeps on that client’s record in Canada, the figures the Firm sees there: receivables and how old they are, payables, recent payments, bank balances, profit and loss, the balance sheet, tax rates, customer and vendor counts and the business’s address and phone number. Clerra keeps the FreshBooks business identifiers, which business is linked to which client, the permissions granted, and FreshBooks’ access and refresh tokens (encrypted), stored in Canada. Two further uses happen only when the Firm switches them on, each asking FreshBooks for the matching write permission at that time: invoicing, for a Firm that keeps its own practice books in FreshBooks, sends the Firm’s invoices created in Clerra to the Firm’s own FreshBooks (the client’s name, email address and billing details, the invoice’s lines, taxes and number, and payments recorded in Clerra) and reads payments recorded in FreshBooks back, marking a voided invoice deleted in FreshBooks, where FreshBooks keeps it and it can be restored; and receipts, which, once a staff member approves a receipt, posts it to that client’s linked FreshBooks business as an expense (merchant, date, category, amounts and taxes) with the receipt image attached. Clerra never sends an email from FreshBooks, never notifies a client of a payment there, and never permanently deletes anything in FreshBooks. Our background-job orchestration system (our own servers in Canada, Toronto) receives only record identifiers, never a figure, a name or a receipt. Figures, invoices and receipts are Customer Data, kept and deleted like the rest of the client’s or the Firm’s records (section 10). Disconnecting FreshBooks in Clerra ends Clerra’s access at FreshBooks and deletes the stored tokens, the business links and the cached figures immediately; FreshBooks does not tell Clerra when an app is removed on its side, so remove it in Clerra too. To ask us to delete information Clerra holds from FreshBooks, write to support@clerra.ca or our Privacy Officer (section 16); see also Your rights (section 11).
- Online identity verification (Didit) — where a Firm must verify a person’s identity under Canada’s anti-money-laundering rules (FINTRAC) and chooses to do it online, the check is run by Didit (Didit Identity, Inc. and Didit Identity Spain, S.L.), acting on the Firm’s behalf. Before the check starts, Clerra tells the person who Didit is, what is collected and where it is processed, and asks for their agreement; the person may ask the Firm to verify them another way instead. Didit collects photos of a government-issued photo ID and the details printed on it, a selfie used to check that a live person is present and to compare their face with the ID photo, and device and network (IP) information, and screens the person’s name against sanctions and politically-exposed-person lists. Didit processes and stores this information in the European Union, not in Canada; see Didit’s Verification Privacy Notice. Clerra has opted out of Didit using verification data to train its models, and has set Didit to keep verification data for five years, the period FINTRAC requires a Firm to keep its identification records. Clerra receives and keeps, in Canada, only the result of each check and the details FINTRAC requires the Firm to record: the name as it appears on the ID, the document type, its number (encrypted), where it was issued and its expiry date. Clerra does not store the ID images, the selfie or any video. Our background-job orchestration system (our own servers in Canada, Toronto) receives only record identifiers. Identification records are Customer Data, kept and deleted like the rest of the client’s FINTRAC records (section 10). To ask about information Didit holds from a check, write to the Firm, to support@clerra.ca or to our Privacy Officer (section 16).
- Dropbox — a Firm connects one Dropbox account, with someone who has the Integrations permission signing in to Dropbox and pressing Allow. For importing client files, Clerra asks Dropbox for read-only permissions:
account_info.read, to learn which account connected (its Dropbox account ID, name, email address and, for a Dropbox team, the team’s name), andfiles.metadata.readandfiles.content.read, to list the folders the Firm chooses and copy the files in them into the matching clients’ files in Clerra’s vault in Canada, after a virus check. Clerra keeps a record of each file it imported (its name, folder, size, Dropbox’s identifier and content fingerprint, and which client it went to), so a file is never brought in twice. Where the Firm chooses Dropbox as its own document storage, Clerra also asks forfiles.content.writeandfiles.metadata.write, to make a folder for each client and save, rename, move and delete files there as described above under the Firm’s own document storage; a file deleted in Clerra goes to Dropbox’s deleted files, where it can be restored. Clerra never asks Dropbox to permanently delete anything, to make shared links or to change a team’s settings. Clerra keeps the Dropbox account details above, the folder identifiers it needs, the permissions granted, and Dropbox’s access and refresh tokens (encrypted), stored in Canada. Our background-job orchestration system (our own servers in Canada, Toronto) receives only record identifiers, never a file, a file name or a client’s name. Disconnecting Dropbox in Clerra ends Clerra’s access at Dropbox and deletes the stored tokens and account details immediately; files in Dropbox and in Clerra’s vault are left as they are, and the record of imported files is kept with the Firm’s records so that connecting again never imports a file twice. To ask us to delete information Clerra holds from Dropbox, write to support@clerra.ca or our Privacy Officer (section 16); see also Your rights (section 11). - AI assistants (Claude and ChatGPT) — where a Firm’s Company Admin turns on AI assistants (confirming the Firm has assessed sending its data to them) and a staff member whose role allows it connects their own Claude (Anthropic) or ChatGPT (OpenAI) account to Clerra, signing in to Clerra and choosing what the assistant may do, that assistant can read, with that staff member’s own access and nothing more, the Firm’s records the staff member can already see in Clerra: filing deadlines, clients, jobs, document requests, setup issues, firm settings, the team and reports. Where the staff member’s role allows changes and they allowed it when connecting, the assistant can also add notes, to-dos, the staff member’s own time, jobs and new clients (with their essential details), move jobs and their steps (never to done or filed), and update a client’s contact details, owner, status and filing set-up and a few settings, as listed at clerra.ca/developers/ai-assistants; it can never delete anything. Clerra never sends an assistant SINs, dates of birth, bank details, pay rates, phone numbers or file contents, and shows only the last three digits of long account numbers. What the assistant reads is sent to Anthropic or OpenAI and processed in the United States, under the Firm’s or the staff member’s own account and agreement with that company, not Clerra’s, and is not covered by Clerra’s Canadian storage. Clerra keeps, in Canada: the connection (which assistant, the permissions allowed, who connected and when), its sign-in credentials (stored only as one-way hashes, or encrypted), and a record of each request (the tool used, when, by whom and whether it succeeded, never what was asked or returned) and of each change with its old and new value, in the Firm’s activity log. Connections renew every 180 days. Disconnecting (the staff member in Profile → Connected accounts, a Company Admin in Settings → AI assistants, or the Firm turning AI assistants off) ends access immediately and deletes the connection’s credentials; it does not remove what the assistant already read from Anthropic’s or OpenAI’s service, which is governed by their terms. A client who signs in to their Client Center can also connect their own Claude or ChatGPT, as their own choice (the Firm’s AI-assistant setting doesn’t apply to it); it reads only what that client sees in their Client Center (requests, deadlines, work in progress, documents to sign, invoices owing), changes nothing, and is processed by Anthropic or OpenAI under the client’s own account. To ask us about information Clerra holds from an AI-assistant connection, write to support@clerra.ca or our Privacy Officer (section 16).
We require our service providers, by contract, to protect personal information with appropriate safeguards and to use the content we send them to provide their services to us. Some providers, such as our communications providers, also act independently for limited purposes, such as security, fraud and abuse prevention, legal compliance, and improving their own services, for which they may use account, usage, and message-routing information (for example, a phone number and delivery status) under their own privacy policies. We will make reasonable efforts to give Firm administrators advance notice before adding a new category of service provider that processes Customer Data.
Google user data — Limited Use. Clerra’s use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We use data accessed through Google APIs (Gmail™, Google Calendar™, Google Meet™ and Google Drive™) only to provide and improve the user-facing features described above. We never sell it or use it for advertising. We do not use it to develop, improve, or train generalized or standalone AI or machine-learning models, and neither do our providers.
Google, Gmail, Google Calendar, Google Meet, Google Drive and Google Workspace are trademarks of Google LLC. Microsoft, Microsoft 365, Outlook and Microsoft Teams are trademarks of the Microsoft group of companies. Zoom is a trademark of Zoom Communications, Inc. Clerra is not affiliated with or endorsed by these companies.
Our personnel do not read Google user data except (a) with the user’s consent for specific messages, for example to provide support; (b) where necessary for security, such as investigating abuse; (c) to comply with applicable law; or (d) where the data has been aggregated and de-identified for internal operations.
Who we share Google user data with. We share data obtained through Google APIs only with the service providers strictly necessary to deliver the features above, and only for that purpose:
- Our cloud infrastructure provider (hosted in Canada, Montréal/Québec) — stores the copy of a connected Gmail mailbox and Google Calendar described above, saved Google Meet transcripts and notes, what a staff member saves from a message (such as a logged communication or an attachment saved to the client’s vault), and the names and identifiers of the Google Drive files Clerra manages; and holds a file on its way to Google Drive for at most 24 hours.
- Our third-party AI provider (United States) — receives the content of an email only (a) where the Firm has switched on Next steps, when a staff member opens a conversation, or (b) where the Firm has switched on automatic job filing, when a new email arrives from a client — to return that result, on the non-training terms described above. A Google Drive file is sent to it only when a staff member runs a feature on that file, such as reading a receipt. A Google Meet transcript is sent to it only where the Firm has switched on AI meeting notes and the meeting was saved to a client’s record (or as a team meeting).
- Our servers that keep mailboxes in step (Canada, Toronto) — read a connected Gmail mailbox and Google Calendar from Google and write them to Clerra’s database in Canada; they keep no copy of their own.
- Our document-processing providers (Canada, Toronto and Montréal) — scan a file for viruses before it is written to Google Drive, and convert a file a staff member sends for signature. They keep no copy.
- Our background-job orchestration system (our own servers in Canada, Toronto) — receives only record identifiers and counts, never the content of an email, a transcript or a file.
We do not otherwise share, transfer, sell, or disclose Google user data to any third party.
7. When we disclose information
We disclose personal information only:
- to our service providers, as described in section 6;
- at a Firm’s direction, for example when a Firm shares documents with its client through the portal or connects an integration;
- where required or permitted by law, such as to comply with a court order, warrant, subpoena, or a demand or requirement from a government authority (including tax authorities). Where Customer Data is involved, we will refer the request to the Firm where reasonable. Where the law allows and it is reasonable, we will notify the affected Firm before disclosing;
- where reasonably necessary to protect the rights, property, or safety of our users, the public, or Common Good Labs, or to investigate fraud or a breach of our Terms of Service;
- in connection with a prospective or completed business transaction, such as a financing, merger, acquisition, or sale of all or part of our business. Disclosure is limited to what the transaction requires, the recipient must agree to use and protect the information only for that purpose, and any successor remains bound by the commitments in this policy for information it receives; and
- otherwise with your consent.
8. Security
We apply layered safeguards, including:
- encryption in transit and at rest;
- row-level data isolation between Firms, and between a Firm and its clients;
- least-privilege access controls;
- short-lived signed links for document downloads;
- optional two-factor authentication;
- bot protection on public endpoints; and
- an audit trail of sensitive actions.
Our personnel access Customer Data only where necessary to provide support a Firm requests, to maintain the security and integrity of the Service, or to comply with law.
You are responsible for keeping your sign-in credentials confidential, enabling two-factor authentication, securing the devices you use to access the Service, and managing the access you grant to others. No method of transmission or storage is perfectly secure. We cannot guarantee absolute security, but we protect personal information with safeguards appropriate to its sensitivity.
9. Privacy incidents
If we confirm a security breach affecting Customer Data, we will notify the affected Firm without undue delay. We will give it the information reasonably available to us to help it meet its own obligations. Because the Firm controls Customer Data, the Firm decides whether and how to notify its clients and regulators, and we will reasonably assist it. For personal information that Common Good Labs controls, we will report incidents to the appropriate privacy regulator and notify affected individuals where the law requires. We keep records of breaches as the law requires.
10. Retention
Because Clerra supports regulated financial and tax workflows, records (including documents and the audit trail) are retained for a configurable minimum period — seven (7) years by default — before they become eligible for deletion, consistent with common professional record-keeping practice in Canada. While a Firm’s account is open, Clerra never deletes the Firm’s documents automatically, including once that period has passed. A document can be deleted before the period ends only with the approval of one of the Firm’s Company Admins, confirmed with that admin’s own security code, and each such deletion is recorded in the audit trail. A document under a legal hold can’t be deleted. Firms may archive a client at any time. Each Firm is responsible for setting retention that meets its own professional and legal obligations.
We retain account information and Customer Data for as long as a Firm maintains its account. A Firm can export its data before closing its account. After an account is closed, we delete or de-identify Customer Data within a reasonable period, except where we must keep information to meet legal, tax, or accounting obligations, or to resolve disputes. Copies held in backups are removed as those backups expire in the ordinary course, and remain protected until then.
If you ask us for a demo, we keep your request (your name, email, firm, team size and message) for up to 24 months, then delete it.
11. Your rights
Subject to applicable law, you may request access to, or correction of, your personal information, and may withdraw consent (which may limit your ability to use the Service). Residents of Québec also have rights under Québec law, including the right to receive certain computerized personal information in a structured, commonly used technological format.
- If you are a member of a Firm, contact your Firm administrator or us.
- If you are a client of a Firm, please direct requests about your information to that Firm, which controls it. If you contact us, we will refer your request to the Firm and assist the Firm as its service provider.
We will respond within the time required by law, generally within 30 days. We may need to verify your identity first. We may decline a request where the law permits, for example where responding would reveal another person’s information or information subject to legal privilege.
If you have a concern, please contact our Privacy Officer first (section 16) so we can try to resolve it. You also have the right to complain to the Office of the Privacy Commissioner of Canada or the privacy regulator of your province, such as the Commission d’accès à l’information du Québec.
13. Children
The Service is intended for businesses and is not directed to individuals under the age of majority. We do not knowingly collect personal information directly from children. A Firm may hold information about its clients’ dependants as part of its professional services. That information is Customer Data, and the Firm is responsible for it.
14. Changes to this policy
We may update this Privacy Policy from time to time. We will post changes here with a revised “Last updated” date. For material changes that reduce your privacy protections, we will give Firm administrators reasonable advance notice by email or within the Service, normally at least 30 days, unless a change is required sooner by law.
15. How this policy relates to our agreements
This policy describes our privacy practices. It is not a contract and does not create contractual rights or obligations. Our relationship with Firms is governed by our Terms of Service, our Data Processing Addendum, and any other written agreement with the Firm. If a written agreement with a Firm conflicts with this policy about Customer Data, the agreement prevails.
16. Contact us
Common Good Labs Inc. is the organization responsible for personal information under its control. Our Privacy Officer is the person in charge of the protection of personal information. To exercise your rights, ask a question, or make a complaint, contact the Privacy Officer, Common Good Labs Inc., at privacy@commongoodlabs.ca.
