Privacy policy
Last updated November 2, 2026 · applies to boardfinch.ca
BoardFinch is a dashboard for Alberta school councils and their parent fundraising societies. BoardFinch was called BoardFlow until October 2026. This page says plainly what information it holds, where that information lives, and what your rights are. If anything here is unclear, ask: privacy@boardfinch.ca.
What BoardFinch collects
- Sign-in accounts — the name and email address Google shares when you sign in. Sign-in is with Google only, and BoardFinch keeps no password. A board's Tech Admin names each address that may sign in, and every member of that board can see who can sign in. BoardFinch also keeps the day each member first saw the graduation screen, under their sign-in account, with the board's records; the data export includes it, and BoardFinch deletes it with the account. A few accounts made before October 1, 2026 were set up with a password; its scrambled form (a hash) can no longer be used to sign in, and it is deleted with the account.
- Sign-in session data — each sign-in also records the session's IP address and browser identification (user-agent) alongside the session itself. This is standard sign-in security data; BoardFinch stores it with the session and deletes it the night after the session expires, or with the account if that comes first.
- Board setup facts — what you enter when setting up a board: the school's name, the council's and society's legal names, fiscal year end, the society's registry identifiers, and, if your board adds them, its logo and colours.
- Guided-step answers — the facts you enter while working through a guided step so BoardFinch can tell you exactly what to type on an external form. Depending on the guide, that can include the names of the people signing an incorporation application, the society’s directors and signing officers, a registered office address, and contact details. BoardFinch stores these answers with the rest of the board’s records, shows them to that board’s members, and sends them to no government, bank or other outside service — a person types them in themselves. They are included in the data export, and deleted with the account.
- Google connection — if a Tech Admin connects an organization's Google account, BoardFinch stores that account's email address and the OAuth tokens Google issues. Tokens are encrypted (AES-256-GCM) with a key kept separate from the database, and the access is narrow: only calendars BoardFinch creates and files it creates in your Drive. You can disconnect at any time, which is also revocable from Google's side.
- The people directory — a record of everyone in the school’s operations that the board chooses to list: board members, school staff, division contacts, vendors and volunteers. For each, a name (for board members and school staff, a first and last name) and what they are, plus an email address, phone number, organization or short note where the board records one, for board members and school staff a home address, and any role they hold with the council or the society and the dates of that term. Most of these people never signed up for anything, so BoardFinch keeps the fields few and bounded, and a Tech Admin can remove anyone at any time — removing them also removes their roles. Visible to the board’s members, except a home address, which only the board’s executive and its Tech Admins see. Included in the data export, and deleted with the account. A Tech Admin can use the email addresses recorded here, and who was ticked present at a meeting, to write a message, which opens in that Tech Admin’s own Gmail for them to review and send — BoardFinch never sends that message and keeps no copy of it or its recipient list.
- Vault documents — files your board adds: a Tech Admin's uploads and scans (for example an incorporation certificate); a treasurer's receipts, bank statements and school reports, uploaded or photographed with a phone's camera; and the PDF BoardFinch makes of each annual statement the board approves. BoardFinch encrypts each of these files before it reaches storage. When the organization's Google Drive is connected, the file is also saved there, in the organization's own Drive (an ID never is).
- The board’s calendar — dates the board puts there itself: meetings, fundraisers and its own deadlines, with an optional start time and location. These are the board’s own entries, not the deadlines BoardFinch computes. If the board connects Google, BoardFinch also reads the events a person adds to the BoardFinch calendar in that Google account — title, date, time and place — and copies them into the board’s calendar. If the board adds another calendar’s address, BoardFinch stores that address encrypted and reads that calendar’s titles, times and places to show them, and to bring them into BoardFinch if the board chooses. BoardFinch only reads a calendar added by its address; the one calendar it writes to is the BoardFinch calendar in the board’s Google account.
- Board records — the council's and society's legal names and registry identifiers, the board roster (member names, optional email addresses, roles, and term dates), committees and who sits on each (a typed line of names, and people picked from the People list), computed obligations, recorded filings (dates and optional notes), meeting document content you generate, and onboarding answers you save (for example the Google for Nonprofits questionnaire).
- Operations records — to-dos the board tracks, including what needs doing, when it is due, and which person on the roster it is assigned to; activities and which committee runs them; agenda items queued for future meetings (titles and details a Tech Admin enters); and meeting minutes (who attended, who made each motion and how it ended, decisions, and action items — free text a Tech Admin writes). Minutes are kept for the life of the board’s account unless a Tech Admin deletes them. Visible to the board’s members, included in the data export, and deleted with the account.
- Financial records — if a board records its money in BoardFinch: the funds it keeps, who holds each one, and each recorded movement with its date, amount, description, category, and who was paid or paid the board; upcoming bills — a description, an amount, and a due date, and sometimes which fund it will come from; and a budget plan per fiscal year — a category name and a planned amount for each, so the board can compare its plan against what actually happened; the lines a bank’s file or a school’s report shows — the date, the bank’s own words (which can name a person), the amount and the balance after — each with what the board says it was for, the program, the GST on a receipt, and the paper that stands behind it (a receipt saved in the board’s own Google Drive), or the board’s written reason when there is no paper; the board’s own list of category names and the rules it made; and each month the board closes — the bank’s (or the school’s) closing balance typed in, the reason given when a month is reopened, and the month’s report stored when it closed (its funds and the board’s categories, with the entries that carry a written reason). A bill description is free text and can name a vendor or a person. Enter only what the record needs — a payee’s name is often enough, and a bank account number is never asked for and should never be typed in. From a bank’s own file BoardFinch keeps only the last four digits of the account and does not store the file itself. If BoardFinch cannot read one line of a bank’s file, it adds none of the file and names that line. Every member of the board sees each entry’s date, amount, words, category and who paid or was paid, and opens each receipt and bank statement the board saved to its Drive. Only a Tech Admin and the body’s treasurer open the bank’s lines themselves; when the treasurer explains a line, BoardFinch starts the entry’s words from the bank’s own words, and every member reads the words the treasurer keeps. The data export includes them, and deleting the account deletes them. Many of those names are other parents’: every member of the board sees them. BoardFinch keeps the council’s money and the society’s money apart: no page or paper shows one total for both. BoardFinch has no connection to any bank and no way to move money or make a payment.
- The school’s website — a page BoardFinch builds from what the board already keeps: the school’s and each body’s names and logos, upcoming meeting and AGM dates, each role’s mailbox and the board’s address for questions, the committees (each with its lead’s role, the typed line of who sits on it, and its activities with their figures), the other activities with their figures, and each body’s money for the year and its newest closed month by category. It shows whatever the board types in those boxes. A person picked from the People list, and the People list’s home addresses and phone numbers, never appear on it. Once a Tech Admin makes it public, anyone can open it at boardfinch.ca/the board’s address; until then only the board’s members can.
- Operational logs — our host (Cloudflare) keeps short-lived technical logs to run and debug the service. BoardFinch avoids writing personal details into them.
- Pretend schools — anyone can try BoardFinch at demo.boardfinch.ca with a pretend school. BoardFinch keeps what a visitor types there in a separate database only demos use, and wipes it with the pretend school: 10 minutes after its tab is closed, or 6 hours after its last page at the latest. BoardFinch keeps a problem report sent from a pretend school like any other problem report.
BoardFinch uses only the cookies it needs to work: the session cookie that keeps you signed in; a short-lived security cookie during the Google connection step; and two small cookies that only remember your own choices — which school you opened, if you belong to more than one, and whether you picked the light or the dark look, and, on the demo at demo.boardfinch.ca, one more that remembers which pretend school is yours until BoardFinch wipes it — no advertising or analytics cookies, no trackers. BoardFinch's pages load one small script from BoardFinch itself that makes the pages easier to use; no script from anyone else ever runs. BoardFinch sells none of this information, rents none of it and uses none of it for advertising. AI help is described below. The people who build BoardFinch read a bug report a person files on purpose with an AI assistant.
AI help (Finchley) — off unless your board turns it on
A board's Tech Admin can turn on AI help for their school; Finchley is BoardFinch's AI helper. When AI help is on and someone presses "Let Finchley rewrite" or "Let Finchley Phrase-Forage" on a minutes item, or leaves the Body box while typing one, the note they typed for that one item is sent to Anthropic, a company in the United States, together with the name of the agenda section it sits under and the kind of item (a note, a motion, a decision or an action), and a tidier wording or a short check comes back. When an item is saved, it is sent once more, with the first name (or full name, if two people share a first name) and role of each person who holds a role on your board (for example "Lark, Chair"), so it can spot action items and tell who is meant. The action items it finds go into the Action items box of those minutes, where the secretary checks and changes them. When the secretary presses "Ready to post", the action items in those minutes are sent once more, with those names and roles and the date of the next meeting, so each person's to-do can be worded for them. The secretary checks every to-do before it is added. BoardFinch sends nothing else — no email addresses, phone numbers or home addresses, no money records, no other minutes — and apart from those action items it keeps none of what is sent or what comes back. Anthropic's terms for this service say it does not use what is sent to train its models, and no one at Anthropic reads it as a matter of course: only a small team of approved safety reviewers can see it, and only if Anthropic's automated safety checks flag it for possible misuse; every such look is logged. A check answers only from a short fixed list; none of the AI's own words are shown. A check made when someone leaves the Body box is made before the item is saved. BoardFinch records that a suggestion or a check was asked for — who asked, when, and what it cost — and never what it said.
Where your information lives — cross-border notice
BoardFinch stores personal information outside Canada. Under Alberta's Personal Information Protection Act (PIPA), you're entitled to know that, and to a contact who can answer questions about it.
- The database (board records incl. the roster, sign-in accounts and their session records incl. IP addresses, encrypted tokens) is hosted by Neon Inc. in the United States (Oregon).
- The application and the encrypted vault files run on Cloudflare Inc. — vault files are stored with a North America location preference; the application runs on Cloudflare's global network. A board's logo, if it adds one, is stored there too as an ordinary picture — it is not encrypted, because it is a logo. A board's own agenda and minutes templates, if it uploads them, are stored there too as ordinary Word files, not encrypted, until the board replaces or removes them. A picture a person adds to a bug report is stored there too as an ordinary picture, not encrypted, until the report is fixed or deleted.
- If your board connects Google, the calendars, sheets, and documents BoardFinch creates live in your own Google account, under your agreement with Google LLC.
- A bug report a person files is read by the people who build BoardFinch with an AI assistant from Anthropic PBC in the United States.
- If your board turns on AI help, each time someone presses Let Finchley rewrite or Let Finchley Phrase-Forage, or leaves the Body box while typing a minutes item, the note typed for that one minutes item, with its section's name and the kind of item, is sent to Anthropic PBC in the United States, which sends back a tidier wording or a short check. Saving a minutes item sends it again, with the first name (or full name, if two people share a first name) and role of each person who holds a role on your board, so that action items can be found; when the secretary presses Ready to post, the action items are sent once more, with those names and roles and the date of the next meeting. The action items found are kept in the minutes' Action items box.
Information stored in the United States is subject to United States law. For written information about our use of service providers outside Canada, or any question about how they collect, use, or disclose personal information for us, contact privacy@boardfinch.ca.
How it's protected
- OAuth tokens and vault files are encrypted at the application layer before they reach storage, with dedicated keys held separately from the data.
- A file your board adds is saved in your board's own Google Drive when Drive is connected; BoardFinch also keeps an encrypted copy here until one of your board's Tech Admins removes it. Every member opens the bylaws, the council's files, and both bodies' bank statements, financial records and receipts; the society's other files open for its executive; ID documents open for Tech Admins only. BoardFinch opens a file from Drive for a member itself and never changes who Drive shares it with.
- Only your board's Tech Admins open the vault's own copies, and BoardFinch writes each upload, opening and removal of one into a log your board's Tech Admins can see.
- There is no password sign-in. Sign-in is by Google only: at an address a board's Tech Admin has named, at an address ending a board set up before October 1, 2026, or — for a council setting up its BoardFinch account for the first time — at any office mailbox that isn't a person's own. Nobody becomes a Tech Admin because of how their address looks. Sessions are HttpOnly cookies. Apart from the operator's decision on a new school (below), every change a person makes comes from a signed-in member of your own board, within what they may do: a Tech Admin changes anything; an officer changes the work their role holds (for example a treasurer their own body's money, a secretary the minutes); a person a yearly paper names approves it; and any member moves a to-do given to them.
What BoardFinch's operator can see
A person at BoardFinch checks each new school; until they approve it, the parts that reach outside it stay shut. BoardFinch's operator can see, for each school:
- The school's name, and its council's and society's names.
- Whether the society is active or struck, as your board recorded it.
- For a school still waiting for approval, or one that was not approved, whether its society is active or struck.
- For such a school with a struck society, the day it was struck, or that none was given.
- For such a school with a society, the society's number at Alberta's Corporate Registry, or that none was given.
- How far setup has got.
- How many Tech Admins and members there are — numbers, never names, except on a bug report, which the person sends on purpose with those details shown.
- Whether Google is connected for each body, and the day it last synced.
- The date the school signed up.
- The date the school was approved.
- The email addresses of the school's Tech Admins that name an office, such as admin@ or chair@ at the school's own address, so the operator can answer the person who may act for the school — never a member's name or a person's own address, except on a bug report, which the person sends on purpose with those details shown.
- Which month each body last closed — never an amount.
- The day someone from the school last used BoardFinch — never who.
- How many files the vault holds — never their names or what is in them.
- Whether the school has switched on help with wording, and what it cost this month out of the server's limit — never what was asked or written.
- The words and pictures a person puts in a bug report, the page it came from, the person's name and role email, and their phone number if they asked to be texted or called; the report says so before it is sent.
- The next setup step BoardFinch suggests to the school.
- For a school that has started leaving BoardFinch, the date it started — never who started it.
- For a school still waiting for approval, or one that was not approved, the email address of the person who signed it up. Once a school is approved, it no longer shows.
- What the server itself needs, which is about no school.
Never a board's records — no minutes, money, to-dos, people or files — except what a person puts in a bug report on purpose. Every time the operator opens a school's card or the help desk's reports, BoardFinch writes it to the server's log.
When you file a bug report, BoardFinch emails a copy to your sign-in address.
When the operator turns a new school away and then removes it, BoardFinch deletes that school’s names, its sign-up and the person’s place in it, and emails nobody.
How long it's kept
- Vault documents: BoardFinch keeps each file your board adds until one of your board's Tech Admins removes it, so your board has its papers on hand for grant applications, licence applications and filings. A copy saved in your board's Drive stays there until your board removes it. When a board that leaves asks for its records to be deleted, BoardFinch's operator deletes its vault files too.
- Bug reports: Pictures and files on a bug report are kept until the report is fixed; then BoardFinch deletes them.
- Everything else: kept while your account is active, deleted on your request when it closes.
Your rights and your data's portability
- Tech Admins can download the account's records anytime as a single JSON file from the dashboard — no request, no waiting. Vault files are the one exception: BoardFinch shows them to your board's Tech Admins and offers no way to save them. If your board leaves BoardFinch, the Leaving page lets a Tech Admin save each one.
- You may ask what personal information BoardFinch holds about you, ask for corrections, or ask for deletion: privacy@boardfinch.ca.
- If you believe a privacy concern hasn't been handled properly, you may contact the Office of the Information and Privacy Commissioner of Alberta (oipc.ab.ca).
Service providers
BoardFinch relies on: Cloudflare Inc. (application hosting, encrypted file storage and the email copy of a bug report), Neon Inc. (database, United States), and — only when your board connects it — Google LLC (your organization's own Workspace). BoardFinch also relies on Anthropic PBC (AI help, only for a board that has turned it on). The people who build BoardFinch read bug reports with an AI assistant from Anthropic PBC (United States). No other party receives your information.
Changes
Changes to this policy are posted here with a new date. Material changes affecting a connected board are flagged on the dashboard.
The terms for using BoardFinch during the trial are on the terms of use page (opens in a new tab).