Privacy Policy
In brief
- TaeCondo is a Google Apps Script application. It works only with the permissions each user grants it through their own Google account.
- The condominium association’s records are kept in its own Google files (Google Drive, Google Sheets, Google Docs). There is no TaeCondo-hosted database and no application server operated by TaeCondo.
- Google data is used only to provide the TaeCondo features you use. It is never sold or used for advertising.
- Before setup, the association accepts an agreement with the operator. The operator keeps the evidence of this acceptance, and of the other documents accepted in the application, for 3 years after the agreement ends, then deletes it automatically.
- The email assistant is optional and off by default. It uses the association’s own Gemini API key. Nothing is sent to Gemini until the association has saved its key and approved, in the application, the assistant’s privacy impact assessment (EFVP), which states whether the key is on the free or the paid tier. On the free tier, Google may use the content sent to improve its products, and human reviewers may read it.
- This website uses no audience analytics, no tracking cookies and no advertising.
1. Scope of this policy
This policy describes how Stephane Galzin (“we”) handles information in connection with:
- the TaeCondo application, a bookkeeping assistant for self-managed condominium associations;
- the www.taecondo.com website;
- your communications with us, for example to request early access or to get support.
In particular, it explains how TaeCondo accesses Google user data, how it uses that data, where it is stored and with whom it is shared.
TaeCondo is intended for condominium associations and their board members. It is not directed at children.
2. Who we are
- Operator of TaeCondo: Stephane Galzin
- Person in charge of the protection of personal information: Stephane Galzin
- Privacy email: legal@taecondo.com
- Support: support@taecondo.com
3. How TaeCondo works
TaeCondo is a Google Apps Script application. Its code runs on Google’s infrastructure, not on servers that we operate. The operator owns the Apps Script project and provides the same application to every association: no association installs a copy of it. It consists of two web applications:
- TaeCondo Setup, used only by the Google account the association chooses for the installation (the “installation account”). It handles setup, settings and automatic tasks. That account’s Gmail mailbox is the one processed;
- TaeCondo, used by board members. It asks only for access to their Google Sheets spreadsheets and their email address. It does not ask for access to their Gmail, their Google Drive or their contacts.
Each user authorizes the application they use through their own Google account, on the consent screen presented by Google. The application then acts with the permissions that this user has granted. It can only access data that the user’s own account can access, and only within the limits of those permissions. It does not access any data without this authorization. What board members do in TaeCondo runs under their own account, and the application shows them nothing if they cannot open the association’s workbooks. When an action requested in TaeCondo needs a permission that this application does not have (for example creating the meeting document or a folder, or updating sharing or contact labels), it is carried out within five minutes by TaeCondo Setup’s next automatic task, under the installation account.
Automatic tasks run through Google Apps Script installable triggers, created in TaeCondo Setup by the installation account during initialization: reading new emails and handling the board’s requests every five minutes, daily retries and a daily list of payments to review, and nightly synchronization of sharing and contacts. As Google designed them, such a trigger runs under the Google account of the person who created it, with the permissions that person granted. Its execution therefore does not depend on which user is viewing or editing the shared files at that moment, and it continues even when the person who created it is not using the application. Because the association’s users may have different permissions and access rights, automatic tasks can only access what that person’s account can access.
The association determines which information it collects and enters in its files (for example, about its co-owners, tenants and suppliers), for what purposes, and with whom it shares it. It remains responsible for that information towards the individuals concerned. TaeCondo processes this information to provide its features. The operator remains responsible, in accordance with applicable law, for personal information it collects or holds through its own activities, for example when you communicate with it (section 11).
As owner of the project, the operator can change its code, which runs under users’ Google accounts: that is how updates reach every association. It can also view the application’s execution logs and error reports, and its shared storage, which holds no association data (section 6.2). It has no access to the associations’ workbooks, folders, emails or contacts, nor to their Gemini API key. To manage licences, the operator keeps in its own Google Drive one workbook per association, named after the address of its installation account and shared, read-only, with that account only. This workbook holds an internal ID for the association, its name, the installation account’s address, the default language and, where applicable, the addresses of accounts given access to certain features. TaeCondo Setup reads it to check that the licence is active; the application writes nothing to it.
Before any setup, the installation account accepts, on the association’s behalf, a personal-information agreement with the operator. Before turning on the email assistant, it also approves the assistant’s privacy impact assessment (EFVP, section 8). The “Remove TaeCondo” function records a notice ending the agreement in the same way (section 10). For each of these documents, the application gives the association a copy and sends the evidence to the operator’s archiving service (section 6.5).
4. Google data accessed and purposes
Depending on the functions used, TaeCondo may access the following Google services:
| Service | What TaeCondo may do | Why |
|---|---|---|
| Gmail | In the installation account’s mailbox: read incoming and outgoing Interac e-Transfer notifications and apply Gmail labels showing how they were processed; send alerts and a daily list of payments to review to the alert address chosen by the association; send the installation account itself a copy of each document accepted in the application, and send that account and the alert address reminders when a new version of the agreement must be accepted. If the optional email assistant is turned on: read new inbox emails (except Interac notifications and the account’s own emails), apply labels to them, send messages prepared from templates to the installation account itself, and create draft replies with no recipient. | Record and match payments; flag unrecognized notifications and payments to review. Give the association its copy of the accepted documents. Classify emails and prepare suggested replies (optional). The email assistant never sends emails to anyone else. |
| Google Sheets | Create the association’s workbooks during the welcome process; read and update the records they contain. | Keep the financial and administrative records: payments, matches, balances, budgets, expenses, units, co-owners, tenants, board members, suppliers and projects. |
| Google Drive | Create and organize folders and files. Automatically share, read-only, the co-owners’ folder with current co-owners and the tenants’ folder with current tenants and co-owners, removing access for other viewers; if the association turns this setting on (off by default for a new association), make the “Public” folder viewable by anyone with the link. Save the copy of the accepted documents in the board folder’s “Agreements” subfolder (“Ententes” in French). Find the association’s licence workbook. When TaeCondo is removed, move the configuration workbook to the trash. If the optional email assistant is turned on with a knowledge base: read the documents of the folder designated by the association to index them in Gemini. | Organize and share the association’s documents; check the licence; prepare suggested replies (optional). |
| Google Docs | Create the board meeting document. | Prepare meetings with the agenda and current projects. |
| Google Contacts | In the installation account’s contacts: keep two labels up to date (current co-owners and current tenants), create missing contacts, and delete contacts it created once they are in no label. People added to these labels by hand are removed from them. | Make it easier for the association to communicate with co-owners and tenants. |
| Basic Google account information | Know the email address of the signed-in user. For TaeCondo Setup, also obtain from Google an identity token (OpenID) that vouches for this account to the operator’s archiving service; this token gives no access to the account’s data. | Identify the user, check their access to the application, apply their preferences (such as language) and record who accepted a document or approved the EFVP. |
| Connection to an external service | Send content to Google’s Gemini API, with the association’s API key. Send the evidence of each accepted document to the operator’s archiving service. These are the only external services the application calls. | Gemini: only for the optional email assistant (see section 8). Archiving service: keep the evidence of acceptances (section 6.5). |
| Running in the background | Run when no one is using the application, through triggers. | Process emails and perform the daily and nightly tasks (see section 3). |
Which application uses these permissions: TaeCondo, the board members’ application, uses only Google Sheets and basic account information. All the other services in the table are used only by TaeCondo Setup, under the installation account, including for automatic tasks and for requests made by board members (section 3).
Google displays the list of requested permissions on its consent screen before you grant them. TaeCondo uses these permissions only for the functions described in the table above.
5. Use of Google data
TaeCondo uses data obtained through Google APIs only to provide users with the features described in this policy and visible in the application.
We do not:
- sell Google user data;
- use or transfer it for advertising, including targeted, personalized or interest-based advertising;
- use it to determine creditworthiness or for lending purposes;
- use it to develop, improve or train generalized artificial intelligence or machine learning models;
- transfer it to third parties, except as described in section 7.
These commitments describe the practices of TaeCondo and its operator. They do not describe Google’s own processing of content sent to the Gemini service when the optional email assistant is used: that processing is governed by Google’s terms, presented in section 8.
No one on our side reads Google user data, except: (a) with your explicit consent for specific data, for example when you share a file with us to get support; (b) when necessary for security purposes, such as investigating abuse; or (c) when required by law. The operator also consults the acceptance evidence that the association sends it when accepting a document (section 6.5), only to manage the agreements and to establish what was accepted.
TaeCondo is a small, non-commercial application, used initially by the condominium association to which the operator belongs. The operator may access that association’s files as a member of the association, according to the access the association grants, like any other authorized user. As owner of the application’s project (section 3), the operator can also view the execution logs of every association; it consults them only to provide updates and resolve problems.
TaeCondo’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.
6. Where data is stored
6.1 In the association’s Google environment
TaeCondo’s records and documents are kept in the association’s ordinary Google services, each according to its nature:
- Google Sheets: the financial and administrative registers (units, co-owners, tenants, board members, suppliers, projects, transactions, matches, balances, budgets, expense categories, and Interac sender names associated with a unit or supplier). A configuration workbook holds the association’s settings, including the installation account’s address, the alert address and the address of the person who chose the Gemini terms, the result of the latest licence check, and the versions of the accepted documents and the account that accepted them. Board members can view it; only the installation account can change it, and the application checks the settings’ integrity. If the email assistant is turned on, an “Emails” workbook also holds its rules, the list of knowledge-base documents and a queue (sender, subject, summary and outcome of each email processed), whose rows are deleted 30 days after processing, or 90 days after their last update for those still to review or that failed. The backup copies the application makes when it rebuilds the payment registers are deleted after 90 days;
- Google Drive: the association’s folders and shared files, including the workbooks and documents created by TaeCondo, and the “Agreements” subfolder (“Ententes” in French), which holds the association’s copy of each accepted document (as a PDF) and its evidence record (section 6.5);
- Google Docs: board meeting documents, owned by the installation account;
- Google Contacts: contacts and labels for co-owners and tenants, in the installation account’s contacts;
- Gmail: processing labels, the messages the assistant sends to the installation account itself, the copy of the accepted documents sent to that account, and draft replies, in that account’s mailbox.
The workbooks and folders are created by the installation account in the board folder chosen by the association. As Google works, they are generally owned by that account, unless that folder is in a shared drive or their ownership is transferred. The association can open, inspect, export and delete these items without going through TaeCondo.
6.2 While the application runs
When TaeCondo runs, the data needed for the current task is processed by Google Apps Script on Google’s infrastructure.
TaeCondo also keeps technical information in Google Apps Script storage, kept by Google with the application, not in the association’s files:
- user properties (specific to each account and each application): the chosen language and display preferences. For the installation account, in TaeCondo Setup: the status of the latest runs (dates, counts and, after an error, the message shown in the settings, which may name a person); a copy of the association’s settings; and the association’s Gemini API key. Only that account’s executions can read them; the key is never displayed again, and the operator has no access to it;
- user cache: each board member keeps a copy of the association’s settings for at most 60 seconds, readable only by their own executions;
- script properties (shared by all associations): only the keys used to sign the associations’ settings and temporary locks, which prevent two runs for the same association from running at the same time. They contain no association data and nothing that identifies an association. The operator can view them.
Google Apps Script also produces execution logs and error reports for every association’s runs. The operator, as owner of the project, can view them. According to Google’s documentation, these logs identify the user by a temporary key, not by their email address. The application is designed to write into them only fixed texts, technical IDs, counts and error codes: no email address, no name, no amount, and no content of an email, a document or what is sent to Gemini. When an error comes from a Google service, its message is included, with email addresses, quoted text and amounts masked.
We operate no separate application server or database for TaeCondo. Apart from the Google mechanisms described above, we do not keep copies of the association’s Google data, except for the licence information and the acceptance evidence described in section 6.5.
6.3 When the association shares information
When the association shares folders or files through Google Drive, or uses Google Contacts labels to communicate, the information becomes accessible to the people included in that sharing, according to the settings chosen by the association.
6.4 When the optional email assistant is used
Content is then sent to Google’s Gemini API. If the association uses a knowledge base, the documents of the folder it designates are also indexed in a Gemini search store, where they remain until deleted. See section 8.
6.5 With the operator: licence and acceptance evidence
The operator keeps in its own Google Drive:
- the licence workbook of each association (section 3), which only that association’s installation account can view, read-only;
- the acceptance evidence for the agreement, the EFVPs and the notices ending the agreement, which it shares with no one. At the moment of acceptance, TaeCondo Setup sends the operator’s archiving service, a Google Apps Script web application that runs under the operator’s account: the accepted document, as a PDF, and the answers given in it; the name and role of the person who accepted it, and their declarations; the address of their Google account; the date and time; their browser’s type, language and time zone; the association’s name and technical IDs; and hashes that make it possible to check its integrity. The service also writes a row in the association’s register (the person’s name, role and account, date and time, hashes) and returns a receipt, which appears in the association’s copy.
The archiving service checks with Google, through an identity token, that the evidence really comes from the association’s installation account. It does not keep this token, which gives no access to the account’s data. The IP address is not collected. This evidence is used only to establish what was accepted, by whom and when. None of it is emailed to the operator: the automatic notices it receives contain only technical IDs. Its retention and deletion are described in section 10.
7. Disclosure and sharing
We do not sell or rent any data. Data processed by TaeCondo may be accessible:
- to the association’s authorized users, according to Google account permissions and the Google Drive sharing set up by the association;
- to the people with whom the association shares folders or files, such as co-owners and tenants, according to the sharing settings chosen, and, if the association turns this setting on, to anyone with the link to the “Public” folder;
- to the alert address chosen by the association, which receives alerts (subject, sender and date of unprocessed Interac notifications) and the daily list of payments to review (amounts, names and suggested matches);
- to the operator, within the limits described in sections 3, 5 and 6.5;
- to Google, which hosts and processes the data as provider of the Google services used by the association, under the Google terms and privacy policy that apply to each user’s account;
- to Google’s Gemini API, only when the association turns on the optional email assistant, using its own API key. If the association uses the free tier, Google may also use this content for its own purposes, including improving its products (section 8).
Google, as provider of the services used, and Cloudflare, as host of this website, process information under their own terms and privacy policies.
If the law requires us to disclose information that we hold, we will do so to the extent required.
8. Optional email assistant (Google Gemini)
The email assistant is an optional feature, available in early access and off by default. TaeCondo works without it, and the association can choose not to use it.
The assistant uses Google’s Gemini API with the association’s own API key: TaeCondo has no key of its own, and the agreement covering the use of Gemini is directly between the association and Google. Nothing is sent to Gemini until the installation account has: (1) saved the association’s key; (2) approved, in the application, the assistant’s privacy impact assessment (EFVP), whose decision states whether that key is on the free or the paid tier of the Gemini API. The free tier requires a justification, including how the consent of the people concerned is obtained. The approval is recorded like the other accepted documents (section 6.5), and changing tier requires a new EFVP; and (3) chosen from which date emails are classified. The application cannot check the key’s tier itself: the choice stated must reflect reality.
8.1 Information sent to Gemini
- To classify an email: the email’s headers (sender, recipients, date and subject), its text (up to 20,000 characters), the names of its attachments and the attachments themselves when they are PDF or image files (PNG, JPEG, WebP), within certain size limits, together with the categories and classification rules defined by the association;
- To prepare a suggested reply: the same information about the email, the reply instructions defined by the association for that category and, if the category calls for it, the relevant passages of the knowledge base.
- Knowledge base (optional): if the association designates a Google Drive folder (declaration of co-ownership, by-laws, resolutions…), the documents in that folder are sent to Gemini in full every night and indexed in a Google “File Search” store. A document’s index remains with Google until it is deleted, which the application does when the document is removed from the folder.
Not sent: Interac notifications, emails sent by the installation account itself, and emails received before the chosen date. Requests are normally processed in the background: Google then keeps the interaction temporarily so that the application can retrieve the result.
These emails, attachments and documents may contain personal information, for example the names and email addresses of co-owners or tenants, or information about a unit or a payment.
8.2 Gemini API free tier
The free tier applies when the key’s Google Cloud project is not associated with an active billing account. An association that chooses this tier in its EFVP expressly accepts the following terms. Under the Gemini API terms, for Unpaid Services:
- Google uses the content submitted and the responses generated to provide, improve and develop Google products and services and machine-learning technologies;
- authorized human reviewers may read, annotate and process API input and output;
- Google states that it takes steps to disconnect this data from the Google Account, API key and Cloud project before reviewers see or annotate it;
- Google advises not to submit sensitive, confidential or personal information to the Unpaid Services.
Because the association’s emails often contain personal information, we recommend the paid tier. An association that nevertheless chooses the free tier should take this Google recommendation into account.
8.3 Gemini API paid tier
The Gemini API is a paid service only when the key belongs to a Google Cloud project associated with an active billing account. A consumer subscription, such as Google AI Pro or Google AI Ultra, does not make Gemini API usage paid. The association can move its key to the paid tier by linking its project to a billing account; API usage charges are then billed to the association’s billing account, and the association is responsible for them.
For Paid Services, Google states that it does not use prompts or responses to improve its products, and that it processes them under its Data Processing Addendum. Google nevertheless states that it logs prompts and responses for a limited period of time, solely to detect and prevent violations of its Prohibited Use Policy. This data may also be stored transiently or cached in any country in which Google or its agents maintain facilities. The paid tier therefore does not mean that Google retains nothing.
8.4 Human review and sending of emails
- Suggested replies are saved as drafts with no recipient; the application checks that no recipient is present and deletes the draft otherwise. The assistant never sends emails to anyone else: a person must review each draft, add the recipient and send it themselves.
- For some categories, the assistant sends a message prepared from one of the association’s templates, but only to the installation account itself, in the conversation of the email concerned.
- The Gmail permissions granted to TaeCondo technically allow emails to be sent to anyone. It is the way the application works, not the permission itself, that limits sending to the cases described in this policy.
- Generated suggestions may be inaccurate and must be checked before use.
The commitments in section 5 apply to TaeCondo and its operator: we do not use this content to train artificial intelligence models. Google’s processing is governed by its own documents: the Gemini API terms, the Gemini API billing page and the Gemini API usage policies.
9. Security
Access to TaeCondo data is governed by Google account permissions and Google Drive sharing. The security of this data therefore relies largely on Google’s security measures and on how the association manages access. We recommend that the association:
- turn on 2-Step Verification for board members’ Google accounts;
- regularly review who its folders and files are shared with;
- remove access for board members who leave the board.
No method of transmission or storage is completely secure, and we cannot guarantee absolute security. If we become aware of a confidentiality incident involving personal information for which we are responsible, we take steps to reduce the risks and record it in our incident register. If it presents a risk of serious injury, we notify the Commission d’accès à l’information and the people concerned. If an incident involves information for which an association is responsible, we inform that association without delay.
10. Retention, revoking access and deletion
- Association data: it remains in the association’s Google files for as long as the association decides. The association can delete it at any time through Google Drive, subject to its own legal record-keeping obligations.
- Revoking access: each user can revoke TaeCondo’s access to their Google account at any time from the Third-party apps & services page of their Google Account. Automatic tasks running with their permissions then stop. Revoking access does not delete files, contacts and drafts already created, or technical information kept by Apps Script (section 6.2): they remain until they are deleted.
- Content sent to Gemini: once sent, it is kept and processed by Google under the terms described in section 8 and the agreement between the association and Google; neither TaeCondo nor the operator can delete it. A document removed from the knowledge-base folder is deleted from the index by the application. To stop all sending, the association can clear the email classification date, remove its key in the settings, or approve a new EFVP that does not turn the assistant on.
- Pause: the installation account can suspend all automatic tasks at any time, for example during an incident. They resume when it lifts the pause.
- Stopping use: there is no copy of the application to delete. In TaeCondo Setup, the “Remove TaeCondo” function lets the installation account remove the application from the association, without going through the operator. It deletes the automatic tasks, the assistant’s knowledge base at Google and the installation account’s user properties for that association, including the Gemini API key. It also moves the configuration workbook to that account’s trash, where it can be recovered for 30 days. Optionally, it also deletes the contacts and contact labels the application created, its Gmail labels and the link sharing of the “Public” folder. The other workbooks, the folders, the “Agreements” subfolder, emails and drafts remain until the association deletes them. Removal counts as notice ending the agreement with the operator; if this notice cannot be sent to the archiving service, the association can send it in writing to legal@taecondo.com. When the licence ends, the application stops working for the association, except to allow this removal.
- Information we hold ourselves: to request deletion of the information you have sent us (see section 11), write to legal@taecondo.com. When the agreement ends, the installation account’s access to its licence workbook (section 3) is removed, and the workbook is deleted permanently and automatically no later than 90 days after the end. The acceptance evidence (section 6.5) is kept for 3 years after the agreement ends, so that what was accepted, by whom and when can be established. It is then deleted permanently and automatically, together with the association’s register. The end of the agreement is the date of the notice ending it, or the date the operator records when the agreement ends otherwise.
11. Your communications with us
When you write to us, for example to request early access or to get support, we receive the information you choose to send: your name, your email address, the name of your association, the content of your message and any other information you include.
We use this information to reply to you, manage early access and provide support. We keep it for no more than 24 months after our last exchange, then delete it, unless the law requires us to keep it longer. A notice ending the agreement received by email is kept for 3 years after the agreement ends, like the acceptance evidence (section 6.5). It is processed through our email service and is never sold or used for advertising.
To provide support, we only access your association’s files if you explicitly share them with us (see also section 5). You can remove that sharing at any time.
12. Website visitors
This website uses no audience analytics, tracking cookies, tracking pixels, advertising or third-party scripts. It does not load fonts, scripts or images from external services.
The site is hosted by Cloudflare Pages (Cloudflare, Inc.). Like most hosting providers, Cloudflare may record technical connection data (IP address, browser type, requested page, date and time) to operate and secure the service, under its own privacy policy. We do not use this data to identify visitors.
The “Request early access” buttons simply open your email software. No information is sent until you send the message.
13. Your rights
Subject to applicable laws, including Quebec’s Act respecting the protection of personal information in the private sector, you may request access to the personal information we hold about you, its correction or deletion, and withdraw your consent to its use. To exercise these rights, write to legal@taecondo.com. We will respond within the time limits set by law.
Information entered in an association’s files (for example about a co-owner or tenant) is under that association’s control. To access or correct it, first contact the association concerned.
For any complaint about the protection of your personal information, please write to us first at legal@taecondo.com. We acknowledge it within 5 business days and reply in writing within 30 days. If you are not satisfied with our response, you may file a complaint with the Commission d’accès à l’information du Québec.
14. Processing outside Quebec
Google’s services, including Google Apps Script and Gemini, as well as Cloudflare’s hosting of this website, may store or process information on servers located outside Quebec and Canada. That information may then be subject to the laws of the countries where it is located.
15. Changes
We may update this policy. The current version is always published on this page with its effective date. If we materially change how TaeCondo uses Google user data, we will inform users and, where required, ask for their consent again.
16. Contact us
For any question about this policy or your personal information:
- Stephane Galzin, person in charge of the protection of personal information
- Stephane Galzin
- legal@taecondo.com