Privacy Policy
Effective July 1, 2026
Draft pending review by counsel. Not in force.
This Privacy Policy explains how Tsenawt Technologies Inc. ("Tsen'awt", "we", "us") handles personal information in connection with the Tsen'awt Operating System platform at tsenawt.app (the "Platform") and our website. We are based in British Columbia, Canada, and we handle personal information in accordance with Canada's Personal Information Protection and Electronic Documents Act (PIPEDA) and British Columbia's Personal Information Protection Act (PIPA), together with the anti-spam rules in Canada's Anti-Spam Legislation (CASL) for the messages we send.
The Platform keeps each organization's records on that organization's own instance, apart from the shared service people sign in through. That design shapes this whole policy. Read section 2 first: it explains the two different layers of information involved, because your rights and our commitments differ between them.
1. Who this policy covers
This policy applies to the people who administer and use the Platform on behalf of an organization, and to visitors to our website. The organization that licenses the Platform, most often a First Nation, a Tribal Council, or an Indigenous organization, is referred to here as the "Customer".
This policy does not govern how a Customer collects or uses personal information about its own members, clients, or community inside its Space. In that relationship the Customer is the party responsible for the information, governed by the Customer's own privacy laws and policies and, where it applies, by the First Nations principles of OCAP®. We act only as the operator of the software that holds those records on the Customer's behalf.
2. Two layers of information
It matters where information lives. The Platform involves two separate layers, and we treat them differently.
Layer one: your Space records and content
Each Customer's Space runs as its own instance: a separate virtual server on its own network segment, with its own databases and its own Office, which is built on Nextcloud. The documents, spreadsheets, forms, collected responses, files, mail, registers, AI conversations and other records a Customer creates or imports in its Space are stored there, together with the Space's audit log, its members, roles and invitations, the saved views of its registers (each person's own views and default, and the views shared with the organization or a department), and the index its assistant searches. They are owned and controlled by the Customer.
Each department has a place in the Space, and its files are kept in a team folder in the Office, which people browse, upload to, change and delete from inside the Platform. The Platform makes the team folder and an Office group for each department, and keeps the group's members in step with the department: its members, the leads of departments above it and organization-wide administrators, while they are active and have linked their Office account. They may read and change the folder's files but not share them from the Office; files leave only under the Customer's own sharing rules, classification and protocols. The Platform records who last changed each file there. When a department is deleted its team folder and files are kept, and no one reaches them through that department any more. Deleting a file moves it to the Office's trash.
News posts and announcements are written in the Space for the whole organization or for named departments, in English, French or both, with an optional image. They are kept with their author, audience, publishing times and the history of who published, changed and unpublished them, and the Space records who closed an announcement and who follows or recently opened each department's place. Members are told of a post in the Platform and, if they choose, by email; the email names the kind of notice and gives a link, not the post's title or text.
We do not sell this content, mine it for advertising, or use it to train artificial-intelligence models. No analytics vendor sits in the path of this content. We process it only as needed to run the software the Customer asked us to run.
Space content leaves the instance only in encrypted backups (section 8) and in the ways below, each of which the Customer controls:
- Hosted AI. The assistant runs on the Customer's own instance by default, using a local model, and nothing it reads leaves the instance; search indexing, proposed document names and descriptions, funding report drafts, and the summaries of event feedback and questions written for an event's organizers, and the daily summaries an event's attendee app writes for each attendee, also stay on the instance. An administrator may turn on hosted AI providers (OpenAI, Anthropic, Google and Cohere), each with the Customer's own key. When a person chooses a hosted model, or the Customer makes one its default model for the assistant and its automated AI tasks, the provider receives what the person types and the earlier messages in that conversation, the organization's name, type and own words for its offices and instruments, and the answers in its governance profile, and receives records and files only where the Customer's rules let them leave: at a classification level the Customer allows (Public and Internal to start with; an administrator may add Confidential), with that level set by a person rather than by default, with no personal information recorded on them, and not withheld by the Customer's folder or tag rules. Restricted records, records under a cultural or community protocol, and files attached to a chat message are never sent. If anything in a request may not leave, no record context is sent, and the person is told. Hosted providers may process information outside Canada.
- Connected services. An administrator may connect the Customer's own accounts with event services (Eventbrite, Cvent and Zoom) and event payment providers (section 6). The details each exchange needs, such as attendees' names and email addresses, are sent to that service.
- Event notifications. When an attendee turns on notifications in an event's attendee app, the notices the organizers send, changes to sessions on their agenda and a seat that opens for them are sent to them through the push service of their browser's maker (Google, Mozilla, Apple or Microsoft). Each message is encrypted to the attendee's browser before it leaves the instance, so the push service cannot read it; the push service receives the address of the subscription, the time and the size. The subscription (that address and two public keys of the browser) and the language the attendee used are kept on the instance.
- Public events. An event the Customer sets as public may be indexed by search engines and appears on the Customer's public list of events, where it keeps one. Events set to invitation only or hidden ask search engines not to index their pages and are reached by their link.
- Public registers. A resolution the Customer publishes to its public register, which must have no personal information recorded on it and is marked Public when published, is copied as published to a public index on the shared sign-in service so that the public register can show it. Fields the Customer chooses to leave out, such as the mover and seconder, are not copied. Each publication is kept on the Customer's instance with who asked for it, who approved it and when, and is withdrawn from the index when the Customer withdraws it.
- Member Portal. A law, resolution or minutes the Customer releases to its members, which must have no personal information recorded on it and be Public or Internal, is shown as released to the members, and the guests, the Customer chooses, on the members site its instance serves. The members site and its accounts run on the Customer's instance, not on the shared sign-in service. The in-camera part of minutes is never released; only a public summary, or the resolutions it passed, where the Customer records one. A release is withdrawn from the members site when the Customer withdraws it or raises the record to Confidential or Restricted. Where the Customer's members include other organizations, its members site also serves the people each member Nation on its roll names to read for it, named through the Nation's registration link or recorded by the Customer, with the designating resolution or letter.
- Published assistant. Where the Customer opens it, its instance serves a public link where anyone may ask questions with no account, and answers them only from what the Customer published to it: documents, spreadsheets and web pages it added, and laws, resolutions, minutes and Office files it chose. Each must have no personal information recorded on it and may not be Confidential or Restricted, and a staff member confirms when publishing an uploaded document, a spreadsheet or a web page that it holds no personal information. Material is marked public or members-only: a person signed in on the members site, who is not a guest and is in reach of a members' audience, also gets answers from members-only material. A law, resolution or minutes released to the public through it becomes Public, and an Office file must already be Public to go to the public. Material leaves answers at once when it is withdrawn, deleted or replaced, or when its record's level or personal information changes so that it may not be used. Answers come only from that material, are given with its name and the date it was published, and decide nothing; with nothing relevant no model is called and the Customer's contact is given. The Customer chooses a local model or a hosted one it configured. With a hosted model, the provider receives the question, a few earlier turns of that conversation, and the passages of published material the answer draws on, only where the Customer's disclosure rules let that material out, and each call is logged without its text. Embeddings stay on the instance. The Customer lists the domains its web pages are read from; the instance reads those pages over https once a day, never from a private network address. When a published page's words change, answers stay on the published text until staff review the change and publish it again. Test questions staff ask before publishing are not kept or counted. A member's own file. Where the Customer turns it on and chooses which verification methods qualify, a member signed in through the Member Portal and verified one of those ways can see their own records on the link: their register status, membership applications, membership decisions once communicated (not the reasons), ISET and land records once staff connected them to the register, and their own row on lists the Customer uploaded, in the columns it chose. A row connects to a person by an exact match on name and birth date, member number, email or the list's own ID; anything less waits for staff, and unconnected rows are shown to nobody. This is a plain lookup: no AI model, local or hosted, receives any of it, and it is not kept with questions, whatever the Customer chose to keep. Each view is logged with the account and without what it showed. A helper sees a member's file only where the Customer allows it. Child and family services records are not included. External collaborators. The Customer can mark a person internal or external to it, which applies to that membership only and shows beside the person in its people and access review screens, in its logs and in its Office. An external person holds a normal paid seat and follows the same rules as anyone else, and the Customer may limit them further: records they are not named on, closed applications, AI search, the staff directory and bulk export. Where the Customer sets an end date, access stops on that day and the seat is freed. A person with no department, level or role yet reads Public records only. Ownership declarations. A business, non-profit, charity or other organization says at sign-up whether it is Indigenous-owned, and may attach a document such as a certification or a Nation's letter. An organization that answers no may still use the platform. A person at Tsen'awt reads each document attached and records a decision; nothing is decided automatically, and each reading is logged. The uploaded document is held by Tsen'awt with the registration record.
- Email. Email the Platform sends, such as notifications and invitations, leaves through a mail relay, which may be an outside provider.
Layer two: account, sign-in and billing information
People sign in once, through a shared service we operate, and reach every organization they belong to. To provide that and to run the Platform as a business, we hold a small amount of information about the people who use an account and about the commercial relationship: names, email addresses, language preference, sign-in credentials and second sign-in steps, sessions and security events, which organizations a person belongs to and whether they administer it, registrations, subscriptions and billing details, proponent portal accounts and submissions, and support correspondence. The shared service holds no Space records other than the resolutions a Customer publishes and, for events, the Customer's connections to event services and payment providers and the payment checkouts made through them. This layer is the subject of most of the rest of this policy.
3. Information we collect
Depending on how you use the Platform, we may collect:
- Account information: your name, email address, preferred language, the organizations you belong to, your role in each, and your account preferences.
- Authentication information: your password, stored only as a scrypt hash, or, if you choose to sign in with Google or Microsoft, the account identifier those services return. We do not receive your Google or Microsoft password.
- Second sign-in steps: the passkeys and security keys you register, your authenticator app setting, your recovery codes and the codes we email you (both stored only as hashes), and the browsers you choose to trust, with each browser's user agent and IP address.
- Sessions and security events: when you sign in, from which IP address and browser, sign-in failures, and changes to your password or second sign-in steps.
- Billing information: the plan, number of seats, billing contact, and the identifiers of the Customer's Stripe customer record and subscription. Card details are entered on our payment processor's page (see section 6); we do not store card numbers on our systems.
- Space content: the records described in section 2, layer one, held on the Customer's instance. This includes files and email an administrator imports from Google Drive, Gmail, Microsoft 365, Box or Dropbox, with the details the source held about each item, such as its authors, dates, column values and retention label, documents imported from Laserfiche, with each document's entry ID, path, template and field values, tags, version, creator and dates, the Laserfiche record series it was filed under and its records management properties (such as its cutoff date and disposition state), a summary of its annotations (type, page, author, date and comment), and the Laserfiche holds named for it, and documents imported from M-Files, with each object's ID, class, properties, version, creator and dates.
- Event sessions: if you attend an event an organization runs on the Platform and take part through your registration link, that organization's instance holds your answers to session polls, the questions you ask and the questions you vote for, your session ratings and comments, your answers to the event's evaluation, and a record of each of these actions with its time. A question you ask without your name is shown to other attendees without it, but the event's moderators, who are its organizers and the session's speakers, see who asked. A youth participant's question is shown to other attendees, and on the presenter's screen, without their name, unless the organization has turned that protection off (see Youth participants below). Poll results, ratings and comments are shown to the organizers and to the session's speakers without your name. The event's reports and their CSV files give counts and averages by session, category and day, without names or comments. Summaries of comments, questions and evaluation answers are written for the organizers by the organization's local model, without names, are marked as written by AI, and are never sent to a hosted provider. This information is kept with the event's records, under the organization's control.
- Usage and technical information: actions recorded in the Space's append-only audit log, and server logs such as IP address, the page or address requested, browser type and timestamps needed to operate and secure the service.
- Proponent portal: if you use the portal to send referrals, land requests or instruments to organizations, your email address, name, organization and preferred language, your profession, regulator and member number where you submit land instruments, and your submissions, files and messages.
- Member Portal: if you are a member of an organization that uses the members app, or a guest it invites, your email address and preferred language, your sessions, and for each organization whether you are a member or a guest, how and when you were verified and by whom, and whether your access is active, suspended or ended. A member's account is linked to their entry on the organization's own membership register, which the organization keeps; a guest's records who the organization says the guest is and until when. If you ask to join, the names and date of birth you give, and any note, are kept with the organization's decision. The organization may keep your email address, mobile number, mailing address and how you want notices in its members directory, separately from its register. A helper who reads for a member is recorded with their email address and the period the member's permission runs. If a Nation names you to read for it in an organization it belongs to, such as a Tribal Council, your name, email address and role, the designating resolution or letter (its reference, date and any file), how you were named, who confirmed it, and when the designation ends or ended are kept by that organization. The organization's staff see these records, and the Nation sees the names and roles of its own representatives through its registration link; other members and guests do not.
- Published assistant: if you ask a question on an organization's published link, that organization's instance counts it, and your network address is used to limit how often questions can be asked and is not kept with your question. Whether your words are kept is the organization's choice, and the page says which it made: only a count, with no words kept, which is the default; your questions without your name, with email addresses and telephone numbers masked, though anything else you type stays in them; or your questions and their answers, with your members-site account if you are signed in. Staff see what is kept. If you ask that your question be passed to staff, the question and any way of reaching you that you give are kept for the organization's staff. The conversation on the page is not stored in your browser and goes when the page closes. Where the organization chose a hosted model, your question and the published text the answer draws on go to that provider.
- Communications: the content of messages you send us for support, feedback, or sales.
Event attendees
A Customer that holds an event in its Space can run attendee features on the pages a registrant reaches from the private link in their confirmation. The Customer chooses which run, and can turn each off for an event. These records are Space content (section 2, layer one), held with the event. When the features run:
- Activity: the Platform records, once per action, what an attendee does at the event and on these pages: each day they are checked in, each session they attend (confirmed in the attendee app, or joined on Zoom), a session rated or the evaluation answered, a poll answered, a question asked, a question voted for, a meeting agreed, a partner's page visited, a session material or partner file opened, a sponsor placement opened, and a challenge completed, with what it was on and when.
- Directory and meetings: an attendee is listed in the event's attendee directory only if they choose to be, with their name and only the details they choose to show (organization, job title, email address, Nation or community, and a short note). Meeting requests, their notes and answers are kept with the event. Unless the organization has turned these protections off (see Youth participants below), youth participants are not listed and neither receive nor make meeting requests with other attendees.
- Points and leaderboard: when the Customer turns them on, an attendee earns points for each kind of action, at values the Customer sets, and for challenges the Customer sets. An attendee is hidden on the leaderboard until they choose to show their initials and Nation or community, or their name, and earns points either way. Youth participants are not shown by name unless the organization has turned that protection off.
- Engagement score: the Customer's event staff see a score for each attendee, the number of each kind of action multiplied by a weight the Customer sets, with the counts that produced it, and can export it. Attendees see their own points, not this score, and the attendee pages say that participation is recorded and scored. The Platform makes no decision about an attendee from the score.
- Sharing with event partners: an attendee may share their name, organization, job title and email address with one of the event's partners, such as a sponsor or exhibitor, by consenting on that partner's page. This is a disclosure to a third party chosen by the Customer: the partner's staff see the details through a private link and can download them, and the partner then holds its copy under its own practices. The attendee can stop sharing on the same page; the partner then no longer sees them, but a copy already downloaded stays with the partner. When an attendee asks to meet a partner, the partner's staff see the attendee's name, organization and note. Youth participants cannot share their details with a partner unless the organization has turned that protection off.
- Youth participants: an event's youth participants (those registered through a youth program) have five protections: not listed in the attendee directory, no meeting requests with other attendees, no sharing of their details with partners, not named on the leaderboard, and questions shown without their name. The organization sets each one for all its events and may set it differently for one event. Each is on unless the organization turns it off. Details a youth participant shared with a partner while that protection was off are no longer shown to the partner once it is on again; a copy the partner already downloaded stays with the partner. Every change to these settings is recorded in the organization's audit trail.
- Sponsor placements: sponsor images on the attendee pages and the event's public page are counted only in aggregate, as how many times each was shown and opened on each page and day, with nothing about who saw or opened it. An attendee's first opening of a placement is also recorded as their activity. Opening a placement goes to the sponsor's website, whose own practices apply.
These features set one cookie, tsenawt_events_form, only when a form on these pages is not accepted, so that what was typed is not lost (see Cookies and browser storage). Their pages are not saved in the browser for reading offline.
Cookies and browser storage
The Platform sets only the cookies it needs to work, and uses no analytics or advertising cookies. Sign-in cookies are marked HttpOnly and, on secure addresses, Secure. The session and trusted-browser cookies use the __Host- prefix, which ties them to the exact address that set them. The Platform sets these cookies:
- __Host-tsenawt_session keeps you signed in. Without Remember me it ends when the browser closes, after 12 hours at most, or after 8 hours without activity. With Remember me it lasts 30 days, or less where an organization you belong to sets a shorter session (8 hours, 24 hours, 7 days or 14 days).
- __Host-tsenawt_device is set when you pass the second sign-in step with Remember me, so that later sign-ins in that browser skip the second step, for up to 30 days, or less where an organization you belong to sets a shorter period or turns it off. It stops working sooner if you remove the browser from your account, end your other sessions, reset your password or remove a second sign-in step, if you are removed from the last organization you belong to, or if an organization you belong to turns on two-step verification, turns trusted browsers off or sets a period shorter than the browser has been trusted.
- tsenawt_2fa, tsenawt_2fa_next, tsenawt_mfa, tsenawt_mfa_enrol, tsenawt_mfa_reauth, tsenawt_verify, tsenawt_invite and tsenawt_reauth hold the step you are on while signing in, verifying your email address, accepting an invitation, adding a passkey or confirming your identity again, for 10 minutes.
- g_state and g_pkce protect a sign-in with Google, m_state and m_pkce a sign-in with Microsoft, and mig_state and mig_pkce the connection of a Google, Microsoft, Box or Dropbox account for importing files, each for 10 minutes. tsenawt_oauth_next holds the page to return to after a Google or Microsoft sign-in, for 10 minutes.
- tsenawt_control_signin carries a sign-in from the shared sign-in service to your organization's instance, and tsenawt_ws_signin and tsenawt_ws_link carry a sign-in from, or a link to, the organization's Office, each for 5 minutes.
- tsenawt_locale remembers your language, and rail-collapsed and record-rail-collapsed whether you folded the side panels, each for one year.
- tsenawt_portal keeps you signed in to the proponent portal for 12 hours, and tsenawt_portal_email holds your email address between the two portal sign-in steps, so that it does not appear in the address bar, for 15 minutes.
- tsenawt_members keeps you signed in to an organization's members site for 30 days, until you sign out, and tsenawt_members_email holds your email address between the two members site sign-in steps, for 15 minutes.
- tsenawt_members_draft keeps what staff entered on a Member Portal form that was not accepted, such as a member's contact details, so it does not have to be typed again and never appears in the address bar, for 2 minutes. It is sent only with the Members app's own pages.
- tsenawt_register_draft keeps what was entered on a Nation's registration link that was not accepted, such as a representative's name and email address, so it does not have to be typed again, for 2 minutes. It is sent only with the registration link's own pages.
- tsenawt_form_result shows the result of a public form after you submit it, and tsenawt_procurement_form keeps what you entered on a form that was not accepted, so you do not have to type it again, each for 2 minutes.
- tsenawt_events_form keeps what you entered on an Events form that was not accepted, so you do not have to type it again, for 2 minutes: an event's registration form (when the page runs without script), the attendee pages reached from a registrant's own link, and an event's organizer pages. It is sent only with the pages of that event or link, and boxes that record agreement, such as consent to share your details with a partner or the code of conduct, are never kept.
- int_keys keeps what an administrator entered on the events integrations page after an error, for 5 minutes, and roles_team_left shows a notice after you leave a team, for 30 seconds.
- The Office, built on Nextcloud, sends you to the Platform to sign in, then sets its own session cookies on the Office address.
The Platform also keeps these settings in your browser's storage. They are not sent to us:
- In local storage, until you clear it: tsenawt_theme, the light or dark appearance you chose on the sign-in pages; tsenawt.ai.model and tsenawt.ai.effort, the AI model and effort you last chose; rail-collapsed and record-rail-collapsed, whether you folded the side panels; and rail-notice entries, the notices you dismissed.
- In session storage, until the browser tab closes: ai-draft, an AI chat message you have not yet sent; lands-boundary-draft entries, a land boundary you are drawing and have not saved; tsenawt:folder-holds, the holds list of a folder import you have not yet started; and doc-restored, app-areas, events-areas, onboarding-dismissed, tsenawt:migration-sites and tsenawt:laserfiche-folders entries (one for each Laserfiche connection and repository), which hold screen state such as a restored document notice, application and event menus, a dismissed introduction and the sites or Laserfiche folders chosen for an import.
An event's attendee app, reached through a registrant's own link, installs a service worker for that link. It keeps in the browser's Cache Storage the app's pages for that registrant (Today, their agenda, the program, their badge with its code, the venue, the More menu and its offline page) and the app's scripts, styles and fonts, so they can be read offline. Pages that need the network, such as polls and questions, the evaluation, people, partners, points and the registration page, are never saved; offline they show the offline page. These are not sent to us. They stay until the registration is cancelled or the organizer switches the app off, which removes them the next time the app opens online, or until the site's data is cleared in the browser. If the attendee turns on notifications, the browser also keeps a push subscription for the event, which is sent to the instance as described in section 2, until the attendee turns notifications off.
4. How we use personal information
We use personal information to:
- provide, maintain, and improve the Platform;
- create and secure accounts and authenticate sign-in;
- process payments, manage seats, and administer the licensing or hosting relationship;
- respond to support requests and communicate about the service, including service notices and, with your consent where CASL requires it, other messages;
- keep the service secure, investigate misuse, and maintain the audit trail; and
- meet our legal obligations.
We do not use your information for third-party advertising, we do not sell it, and we do not use Space content to train AI models. If we ever propose a new use, we will update this policy and, where the law requires, ask for your consent first.
5. Consent
Under PIPEDA and BC PIPA we rely on your consent to collect, use, and disclose personal information, except where the law permits or requires us to act without it. By creating an account or using the Platform you consent to the handling described in this policy. You may withdraw your consent at any time, subject to legal and contractual limits, by contacting us as set out in section 12; withdrawing consent may mean we can no longer provide part or all of the service.
6. Service providers and disclosure
We keep outside processors to the minimum the business needs. To run the Platform we use:
- a payment processor (Stripe) to take registration payments and manage subscriptions and seats;
- an email relay to send account, security, invitation and notification messages; and
- sign-in providers (Google and Microsoft), only if you choose to sign in with them; each returns your account identifier, email address and name.
These providers handle only the account and billing information needed for their function. They do not receive your Space content. We do not use data brokers, advertising networks, or analytics vendors on the Platform.
Services a Customer connects
A Customer's administrator may connect the services below under the Customer's own account with each provider. Each is off until it is connected, and each receives only what its function needs:
- hosted AI providers (OpenAI, Anthropic, Google and Cohere), under the rules in section 2;
- event services: Eventbrite, Cvent and Zoom, which exchange event, ticket, registration, session and attendance details, including attendees' names and email addresses, for the events the Customer links to them;
- event payment providers: Stripe Connect, Square, PayPal, Moneris and Helcim, which take card payments for the Customer's events into the Customer's own account, with the payer's name, email address, the amount and what was bought; card details are entered with the provider;
- Google (Google Drive and Gmail) and Microsoft 365 (OneDrive, SharePoint and Outlook mail), from which an administrator imports the Customer's files and email, with read-only access. Access to Gmail is asked for only when an administrator connects a Google account for email, and reads that account's mailbox; each message is copied once, under the labels it was filed under, leaving out spam, trash and, unless asked for, drafts. An administrator may connect Microsoft 365 for the whole organization, with permissions a Microsoft 365 administrator approves, so that the import can read every site and library and, for email, every mailbox in that organization. Nothing from the Space is sent to these services; and
- Box, from which an administrator imports the files a connected account can reach, with read-only access (the root_readonly scope). Nothing from the Space is sent to Box;
- Dropbox, from which an administrator imports the files a connected account can reach, including a team's folders where the account belongs to one, with read-only access (the account_info.read, files.metadata.read and files.content.read scopes). Nothing from the Space is sent to Dropbox;
- M-Files, from which an administrator imports the Customer's documents and their metadata through an M-Files Web Service the Customer names, with a user name, password and vault GUID the Customer provides. The import only reads: it lists objects and their classes, reads each object's properties and copies its files. Nothing from the Space is sent to M-Files, other than that sign-in;
- Laserfiche, from which an administrator imports the Customer's documents and their metadata, either from Laserfiche Cloud, with a service principal's access key and key limited to reading (the repository.Read scope), or from the Customer's own Laserfiche Repository API Server, with a user name and password the Customer provides. The import only reads: it lists folders, reads each document's metadata and records management properties, and exports each document's content for copying. Nothing from the Space is sent to Laserfiche. A Laserfiche export the Customer places in its Space can be imported instead, without connecting Laserfiche.
Keys, passwords and access tokens for these connections are stored encrypted. A Laserfiche key or password, or an M-Files password, is not shown again once saved, and is deleted when an administrator disconnects that source.
Browser push services
Notifications from an event's attendee app go through the push service of each attendee's browser maker (Google, Mozilla, Apple or Microsoft), only for an attendee who turns them on, and only while the Customer has not switched them off for the event. Each notification is encrypted so the push service cannot read it (section 2).
A Customer's event partners receive an attendee's contact details only when that attendee consents on the partner's page, as set out in section 3 under Event attendees.
We may also disclose personal information where the law requires it, to enforce our agreements, to protect the rights and safety of people and the service, or as part of a business transfer, in which case we will give notice as required by law.
7. Where information is stored
Space content is held on the Customer's own instance (section 2, layer one). Account, sign-in, billing and portal information, and the public index of published resolutions, are held on the shared sign-in service we operate. Members app accounts, sessions and directories are held on the Customer's instance with its Space content. Each instance keeps its own copy of a person's name and email address, without any password or second sign-in step, together with its own sessions and security events. When a person signs in to the Office, the instance gives the Office their name, email address and an account identifier, and records which session the Office was opened through, so that signing out of one signs out of the other.
Where a Customer runs its own EdgePod, the sign-in service for its people, with the information that service holds, runs on the Customer's own hardware beside its instance, and we operate it there. Where the Customer also has a second EdgePod at another site, encrypted backups of its instance and of that service are copied to the second site. If the first site is lost, both are restored from those backups and served from the second site until they are moved back. Both sites are the Customer's. With one site, the encrypted backups are copied to storage at another location the Customer nominates.
Information sent to the providers in section 6, and to the services a Customer connects, leaves these servers. Some of these providers operate outside Canada, and information processed outside Canada is subject to the laws of that jurisdiction. Where a request is made to us for a Customer's records, we direct the requester to the Customer and tell the Customer, unless the law prevents it.
8. How long we keep information
We keep account and billing information for as long as the account is active and afterward only as long as needed for the purposes in this policy, to meet legal, tax, and audit requirements, and to resolve disputes. Space content is retained on the Customer's instance under the Customer's control and its own retention rules, and nothing is destroyed under those rules without a custodian's authorization; on termination, the Customer can export its records as set out in the Terms of Use.
Files and email imported from Google Drive, Gmail, Microsoft 365, Box or Dropbox become records of the Space and are kept under the same rules. Each copy is checked against the checksum the source gives, where it gives one, and a copy that does not match is not registered as a record. An import from Microsoft 365 can repeat daily or weekly to bring in what changed at the source; an item later deleted at the source is marked as deleted there, and the Space's copy is not deleted.
Documents imported from Laserfiche become records of the Space in the same way. Laserfiche provides no checksum, so each copy is recorded with the SHA-256 of what was copied and as not verifiable against the source, and an electronic file whose size does not match the size Laserfiche reports is not registered as a record. An administrator maps each Laserfiche record series to one of the Customer's series. The Laserfiche holds an administrator lists for an import, or a Laserfiche export names, are placed as legal holds on the imported documents and folders, so that nothing they cover is destroyed under the retention rules; an import never releases a hold. Running an import again copies only the documents changed in Laserfiche since they were copied.
Documents imported from M-Files become records of the Space in the same way, each kept with its object's class, properties, version, creator and dates. M-Files provides no checksum, so each copy is recorded with the SHA-256 of what was copied and as not verifiable against the source. Running an import again copies only the objects changed in M-Files since they were copied.
An administrator may also import a folder already in the Customer's Office, such as a Windows file share mounted there or a drive copied to its server. The folder is only read. Each file becomes a record of the Space in the same way, except system files and shortcuts, which are noted and left. A folder gives no checksum, so each copy is recorded with the SHA-256 of what was copied and as not verifiable against the source, and a copy whose size does not match the size the folder lists is not registered as a record. Holds an administrator names by path are placed as legal holds, and an import never releases a hold.
A file deleted from a department's documents stays in the Office's trash, where it can be restored, until the Office's trash retention ends, and is never removed while a legal hold covers it. A deleted department's team folder and its files are kept, under the Customer's retention rules and holds, until a custodian disposes of them or the Space is deleted. News posts and announcements are kept as Space content until the Space is deleted; an unpublished post is kept, not deleted.
In the members app, sign-in codes are deleted when used or once expired, sessions once they end, and invitations not used are deleted 90 days after they expire or are cancelled. Member and guest accounts, their links to each organization, requests to join, directory entries, and member Nations' representatives with their designating documents are kept as the organization's records under its own rules; an account that is suspended or ended is kept, not deleted, so that what it could read and when stays on record. On the published assistant, questions an organization chose to keep are deleted after a year, and questions passed to staff a year after staff close them; monthly counts hold no words and stay with the organization's records. A data set's text is kept until it is replaced or deleted.
A browser you trust to skip the second sign-in step is kept, with its user agent and IP address, for up to 30 days, or less where an organization you belong to sets a shorter period or turns it off, and is deleted when that time ends, when you remove it, or on the other events described under Cookies and browser storage.
In an event's attendee app, a browser's notification subscription is removed when the attendee turns notifications off, when the push service reports it no longer exists, when the registration is cancelled or declined, or 30 days after the event ends, whichever comes first. The daily summary written for an attendee is deleted after the next day.
Event attendee records (activity, directory choices, meetings, consents to share with partners and sponsor placement counts) are kept with the event as Space content under the Customer's rules. A consent an attendee withdraws is kept, with when it was given and withdrawn, as the record of it.
Backups are encrypted, and offsite copies are kept as the latest 30 daily, 12 monthly and 7 yearly backups, so information deleted from a server can remain in an encrypted backup for up to seven years.
A Space is deleted at the request of one of its administrators, approved by a second where it has two or more, after a waiting period of 30 days in which the deletion can be cancelled. A deletion cannot be requested, approved or carried out while a legal hold applies to the Space or any of its records. Where the Space runs on the Customer's EdgePod, its server and disks are destroyed when the deletion completes, and before that the key that encrypts the whole-server backups of that Space is destroyed, so that those backups, at every site, can no longer be read. The key to the Space's other encrypted backups is held offline by two key custodians, who destroy it once the deletion completes, unless the Customer has asked in writing for the backups to be kept for return; those backups then can no longer be read either. The administrators named on the deletion request are sent a confirmation when it completes. A record of the deletion, with its date and the identifier of the destroyed whole-server backup key, is kept after the Space is gone.
Server, application and security logs, including records of sign-in and account activity and of the emails the Platform sends, are kept for twelve months, and sign-in, account and email records for up to 400 days, then deleted. Network monitoring records, which hold the address of every connection to a server, are kept for 14 days. A Space's audit log of administrative actions is kept for as long as the Space exists, because it can only show that it is complete if no part of it is removed.
9. Security and breach notification
We protect information with encryption in transit (TLS) between members and the pod, encryption at rest on the pod's storage, access controls, and an append-only audit log of administrative actions. Each server is monitored for intrusion, unexpected open ports, failed backups and service outages, and these alert our operations team by email. No system is perfectly secure, but we take reasonable measures appropriate to the sensitivity of the information.
You can sign in with a password or, where they are offered, with Google or Microsoft. Passwords are stored only as scrypt hashes, and session and trusted-browser tokens only as hashes, so a copy of the database cannot sign anyone in. You can add a second sign-in step: a passkey or security key, an authenticator app, recovery codes, or a code we email you. A Customer can require a second step of all its members. If you lose every second step, two other administrators of your organization approve a reset; where your organization has too few administrators, two Tsen'awt support staff decide the request after verifying your identity. You can see and end your own sessions from your account, and see and remove the browsers you trust to skip the second step. A Customer can limit how long its members' browsers are trusted, or turn trusted browsers off. The Office signs people in through the Platform, so the same password, second step and trusted browsers apply to it, and it admits only active members of the Customer, with a seat where the Customer assigns seats. Signing out of the Office signs you out of the Platform in that browser, and ending a session in the Platform signs you out of the Office opened through it.
Access to a Space is granted, changed, and removed by the Customer's own administrators, who must sign in with an authenticator app, a passkey, or a security key. Removing a member ends their access to the Space and their sessions in it. The Platform opens a review of who holds access on a schedule the Customer sets, quarterly unless it chooses monthly or every six months; an administrator other than the person concerned decides each person's access (where a Customer has a single administrator, that person's decision on their own access is recorded as an exception), and the review is signed off and kept. Each grant, change, removal, and review is recorded in the audit log.
If a breach of security safeguards creates a real risk of significant harm to affected individuals, we will report and notify as required by PIPEDA and BC PIPA, including to the Office of the Privacy Commissioner of Canada or the Office of the Information and Privacy Commissioner for British Columbia and to affected individuals, and we will keep records of breaches as the law requires.
10. Your rights
Subject to the law, you may:
Right of access
Ask what personal information we hold about you and request access to it.
Right to correction
Ask us to correct information that is inaccurate or incomplete.
Right to withdraw consent
Withdraw your consent, subject to legal and contractual limits.
Right to complain
Make a complaint to us, and to the Office of the Privacy Commissioner of Canada or the Office of the Information and Privacy Commissioner for British Columbia.
To exercise these rights, contact us as set out in section 12. We will respond within the timelines the law requires. If you are a member or client of a Customer and your request concerns records in the Customer's Space, we will direct you to that Customer, who is responsible for those records.
11. Indigenous data sovereignty and OCAP®
The Platform is designed around the First Nations principles of OCAP®, a registered trademark of the First Nations Information Governance Centre. The four principles work together:
Ownership
A Customer owns its records; the documents, data, and content created in its Space belong to the Customer, not to Tsen'awt.
Control
A Customer controls who can reach its records and on what terms, manages access through the Space's own permissions and governance, and reviews it on a schedule it sets.
Access
A Customer decides how its records are accessed, and can reach and export them.
Possession
A Customer's records are held on its own instance, apart from every other Customer's records and from the shared sign-in service.
For Métis, Inuit, and other communities, we support these commitments within the broader movement for Indigenous data sovereignty. Tsen'awt operates the software; the Customer holds the data.
12. Children, changes, and contact
Children
The Platform is intended for organizations and their staff, not for direct use by children. We do not knowingly collect personal information from children through the account layer.
Changes to this policy
We may update this policy from time to time. We will post the updated version with a new effective date and, for material changes, give reasonable notice.
How to contact us
Privacy Officer
Tsenawt Technologies Inc.
6-2020 Vine Street, Vancouver, British Columbia, Canada V6K 3K1
Email: privacy@tsenawt.io
For privacy questions, access or correction requests, or complaints, contact our privacy officer at the address above. You may also contact the Office of the Privacy Commissioner of Canada (priv.gc.ca) or the Office of the Information and Privacy Commissioner for British Columbia (oipc.bc.ca).