Overview
Numinor handles sensitive financial data on behalf of Canadian businesses. Our security program is built around five principles: encrypt everything, grant the least access necessary, monitor continuously, prepare for the worst, and improve after every incident. This page describes how those principles show up in our day-to-day practice.
We would rather this page be specific than reassuring. It describes what is in place and nothing that is not, and a sentence changes the day what it describes does. The date at the top is the last time somebody read every sentence here against the systems it describes.
Data encryption
In transit. All data moving between your devices, our systems, and integrated platforms is encrypted using TLS 1.3 (or TLS 1.2 where a partner does not yet support 1.3). The Site and the Portal are served over HTTPS only; a plain HTTP request is redirected before anything is sent. The Site also tells your browser to reach it over HTTPS only for the next year, so a later visit never tries a plain connection. The Portal's address, app.numinor.ca, does the same for about a year: its hosting platform sends that instruction with its responses, and we read it there on October 25, 2026.
At rest. Client data stored in our systems and at our cloud partners is encrypted using AES-256, with encryption keys managed and rotated by Google Cloud. The credential that lets the Portal read a connected QuickBooks file is held in Google Cloud Secret Manager, one secret per client, and is readable only by the server-side code that needs it — never through the Portal and never from a browser. Only the project's owner account can reach Secret Manager directly.
Backups. Backups are encrypted with the same standards as live data and kept in the same country as the system they protect. What they consist of is under Business continuity.
Access controls
- Sign-in. Nobody has a password to the Portal. Staff and clients sign in through a single-use link emailed to them, so access to the Portal is access to that mailbox — and the Portal account itself is ours to revoke at any time.
- Multi-factor authentication. Staff sign in to the Portal with an emailed link and a code from an authenticator app on their phone, and the Portal does not open for a staff account until that second factor is set up. Clients sign in with an emailed link.
- Role-based access. A client account can read only its own records, and can never set a status the server owns — an approval, an export, a filing — however the request is made. These limits are enforced in the database's security rules and in the server-side code, not in the screen. Staff accounts see the firm's clients. When a staff member leaves, or a client tells us someone no longer works with them, we remove that person in the Portal: their account is disabled, their sessions and any connected AI assistants are ended, their devices stop receiving notifications, and every removal is recorded with who made it and when. A Portal page they already have open keeps its access until its sign-in expires, which is within an hour.
- An audit trail. Every approval, correction, rejection, reopening, export, connection and disconnection is written to an audit log with who did it and when. The log has exactly one writer in our code, and a test keeps it that way.
Infrastructure
Numinor's systems run on Google Cloud, through Firebase, as managed services: a document database, file storage, serverless functions, hosting, and identity. There are no servers we operate or patch — Google patches the platform — and nothing of ours listens on the open internet except the Site, the Portal, and the functions behind them. Google Cloud holds SOC 2 Type II attestation and publishes its audit reports under non-disclosure to customers.
- Where your data is held. We would rather be specific than reassuring. Your accounting records, review history, messages, audit logs, the credential for a connected accounting platform, uploaded receipt and document images, the packages assembled from them, and the PDF copy of each monthly report are held in Canada (Montreal), as are their backups and prior versions. Every uploaded file is sent to a virus scanner in Montreal too, which keeps nothing. A file it finds infected is deleted, and the upload is marked refused with the virus's name kept on the record. A file it cannot read is not processed and is marked failed, with the original left in storage and the sender asked to upload it again. If the scanner itself fails, the file is accepted and marked as not scanned, so that an outage of the scanner does not stop uploads, and we are alerted. Files uploaded before October 4, 2026 were copied to Montreal that day, and their original copies in the United States have been deleted. Sign-in data such as email addresses is held in the United States, and the processing by Anthropic and Mailgun described under Vendor management takes place there.
- A region is fixed when a system is created rather than chosen per client, so if an engagement requires Canadian-only storage, raise it before signing and we will confirm in writing whether we can meet it.
- Access to the production project is through Google Cloud's identity and access management, with named accounts and the least role each needs. The database and file storage are reachable only through their security rules and our own server-side code.
- Development and testing run against a local emulator and a sandbox accounting file, never against a client's data. Changes reach production through a reviewed pull request and an automated deploy that refuses to report success unless every function it deployed is live.
People and training
Every Numinor team member completes security training during onboarding and again annually. Training covers phishing, secure handling of Client data, password hygiene, and incident reporting. Senior team members and anyone handling Client financial data also receive specialized training on Canadian privacy laws (PIPEDA) and applicable provincial regulations.
Background checks are performed on all employees before they receive access to Client systems. Every team member signs a confidentiality agreement and a data-handling acceptable-use policy as a condition of employment.
Vendor management
We carefully select and review every vendor that touches Client data. Vendors are evaluated against security, privacy, and compliance criteria before onboarding, and reviewed annually thereafter. The vendors that touch Client data are QuickBooks Online and the cloud and processing providers named on our privacy policy: Google Cloud, Anthropic, and Mailgun.
Client portal. Documents and messages you share with us go through the Numinor portal, which we built and operate ourselves rather than hosting on a third-party practice-management platform. It runs on the same cloud infrastructure described above, is invite-only with no public sign-up, and clients sign in through an emailed link rather than a password. Sign in at app.numinor.ca.
Email. Mailgun sends the Portal’s email from the United States. Those messages carry a link into the Portal and never a record: no amount, vendor, tax figure or attachment.
Sending documents by email. Each client has its own Numinor address, which accepts mail only from the client’s own Portal users and the senders we add at the client’s request, and only when the sender’s own mail provider has signed the message. What a client emails to that address passes through Mailgun in the United States, attachments included, on its way to Montreal; Mailgun keeps none of its content once it has passed it to us, only a record of the delivery. In Montreal every attachment goes to the virus scanner like any other upload, and the ones we accept become the client’s documents, kept with its other records. We keep the documents and not the message: no subject and no body. For each message we also keep, for thirteen months, a record of its arrival: the sender’s address as the message gave it, even when we refused the message, and each attachment’s name, type and size.
Invoices sent to your customers. A client can email an invoice raised in the Portal to its customer. The email goes to the one address the client chose, and carries the client’s name, the invoice number, the due date and a link to the invoice at app.numinor.ca. Anyone holding that link can open the invoice for 180 days after the email that carried it. The link is a random 160-bit code that we store only in a scrambled (hashed) form, so nothing we hold can be turned back into a working link. It shows the invoice as issued and nothing else about the client: no other invoice and no private notes. A link stops working when its invoice is voided or written off, when the client asks, when the invoice is sent again (unless the sender keeps the earlier link), and when the client leaves Numinor. Each link opens at most fifty times a day, and a link that matches nothing records nothing. We record when a link was opened, never from where. Mailgun carries every such email from the United States, and, for a client who switches it on, a PDF copy of the invoice attached to it. That attachment is the one deliberate exception to the rule in the paragraph above: once sent, the PDF is a copy in the customer’s mailbox and in every mail system it passed through, which we cannot recall.
AI assistants connected by our staff. A member of our staff may connect Claude, from Anthropic, to our clients’ books. Numinor admits Claude and no other assistant, and our staff connect it from the firm’s own Claude Team workspace and no other account. It sees the books of the firm’s clients as a staff account does (Access controls, above): the figures Numinor has computed, each entry of a client’s books with its memo and document number as the company file holds them, and, in the Portal, the invoices, bills, proposals for changes to a company file, bank lines, contacts, tasks, documents (their classification and what was read from them, never the file itself), recurring journal entries, imported statements, reconciliations, requests, the record of a month’s close and client settings, and the client’s chart of accounts, customers, products and services and tax codes as last read from its QuickBooks file. A month whose figures do not agree with the client’s own accounting file is withheld from it, apart from the two totals that show where it disagrees. Connecting one needs the staff member’s second factor, and it stops working the moment that person’s own access does. A staff member can disconnect their own assistant, and an administrator any assistant in the firm, at any time from Connected assistants in the firm’s Settings. Every read is recorded in the audit trail, with who asked and what was read, and never the figures themselves. Clients cannot connect an assistant, and nothing an assistant writes reaches a client without a member of our team.
AI assistants making changes. A connected assistant reads only, until the staff member allows changes: after a fresh second-factor sign-in, for thirty days at most, their Claude assistant can make changes in the Portal and in a client’s QuickBooks file on their behalf. Among the changes that ask the staff member to confirm them in the conversation first are sending, reminding, voiding, writing off or deleting an invoice; approving or voiding a bill; approving a correction or a proposal to a company file; a proposal for a tax code, an exchange rate or a closing date; making an account, customer, supplier, product or list entry inactive; clearing a bank line; signing off, closing or reopening a month; changing a client’s settings; archiving a contact or a task; withdrawing a proposal; stating the end of an agreement; and pushing to a company file other than as a trial. Most other changes do not ask: a draft invoice or bill, a bill’s query, schedule or marking paid, a journal entry or a proposal that only prepares something, matching or dismissing a bank line, a statement import, a reconciliation, and a new or edited contact or task. The staff member answers for every change as for one they made on a screen. The assistant can create and edit draft invoices and send them, with their reminders, to a client’s customer, and void or write one off; create bills, and approve, query, schedule, mark paid or void them; prepare and approve corrections to transactions already in a client’s QuickBooks file, a line’s tax code among them at the total QuickBooks will compute for it, and journal entries; approve, but not prepare, a correction of a transaction’s date, a line’s amount or its lines that a person prepared on the Proposals screen; prepare and approve new and changed accounts, customers, suppliers, products and services and the file’s other lists, tax codes built only from the published rates, company details, exchange rates and the file’s closing date; delete a record nothing else depends on, but only after a second confirmation of what it names; retry pushing the invoices and bills a company file refused, and push a client’s approved receipts to it; pull a client’s bank feed; ask for a statement or a bill in the vault to be read again; and import statements, match bank lines, run reconciliations, file the client’s documents, keep our own contacts and tasks for a client, change a client’s settings, and sign off, close and reopen a month. Each of these is something a staff member can do on a screen, and the assistant can do nothing a screen cannot: every refusal a screen makes, it meets too, and a correction, a journal entry, a change to a list or a setting, or a deletion in a client’s QuickBooks file is written only where that kind of change has been switched on for that client. The one exception is a bill: voiding a bill that was posted to a client’s QuickBooks file deletes it there, on the staff member’s one confirmation and whatever the deletion setting for that client is, the same as voiding it on a screen. It cannot change who can see or do anything (a user, an invitation, a connection or a grant), edit an invoice once it has been sent, approve a receipt, or send anything to a client: a message, a request or a report. Nothing in the connection can tell the staff member’s own confirmation from the assistant reporting one, so the audit trail records it as exactly that: each change names the assistant and the staff member, and says whether the assistant reported the staff member’s confirmation, and a deletion records both of its confirmations. What an assistant reads and writes is sent to Anthropic in the United States, under the same commercial terms as the document processing below.
Automated document processing. Receipts and documents you upload are read by Anthropic’s Claude models, which extract the vendor, date, amounts, and sales-tax breakdown of a receipt, and decide what kind of document each upload is. A document is read whole to decide that, so a tax slip, a statement or an agreement you upload is read by these models too. The same models draft our monthly commentary, answers to your questions about your books, and notes for our staff on why an account changed, over figures we compute. Those figures can name the businesses and people you pay or who pay you, and on a payroll account that includes your employees and what they were paid. Anthropic processes this content in the United States, under commercial terms that exclude it from being used to train models. Every extraction is checked by a member of our team before it reaches your books — nothing is filed on a machine’s say-so.
Incident response
Numinor maintains a documented incident response plan that defines roles, escalation, containment steps for each credential and system we run, and who is notified. Every incident, and every defect found in production, gets a written post-incident review that ends in the rule it produced; those reviews are kept and are how this program improves.
Notification. If a confirmed security incident materially affects your Client data, we will notify affected Clients in writing as soon as practicable, and in any event within the timeframes required by applicable Canadian privacy law (PIPEDA Mandatory Breach Notification within the period prescribed by regulation). Where an incident involves personal information about people in Quebec and presents a risk of serious injury, we also notify the Commission d’accès à l’information du Québec and the people concerned, as Quebec’s private-sector privacy law requires, and every confidentiality incident is entered in our incident register whether or not it is notified. Where an incident involves data read from a connected QuickBooks file, we also notify Intuit as its developer terms require.
Data retention and disposal
We retain Client data only as long as necessary to deliver Services, meet legal and regulatory obligations, and complete reasonable backup cycles. Tax-related records are held for seven years from the end of the tax year they relate to, consistent with CRA recordkeeping requirements.
On termination of an engagement, Client data can be returned in standard formats on request. After legal retention periods expire, data is securely deleted from production systems and overwritten from backups according to industry-standard wiping procedures.
Business continuity and disaster recovery
Our systems are managed services, so the failures we plan for are our own — a bad script, a mistaken bulk delete, a purge with the wrong year end — rather than a machine that fails. The database keeps seven days of continuous point-in-time recovery, recoverable to any moment in that window, and cannot be deleted outright without a protection flag being removed first. A full export is taken weekly and kept for ninety days, in the same region as the database. Uploaded files keep thirty days of prior versions, so an overwrite or a deletion is reversible in that window.
Our recovery time objective for core Client-facing services is 24 hours. Our recovery point objective is minutes for the books and review history, and one version for files. Restores are tested rather than assumed: the weekly export was last restored into a separate database and checked against the original on September 2, 2026, and the test is repeated at least annually and after any change to what the export covers.
Compliance
Numinor's practices are aligned with Canadian regulatory expectations for handling personal and financial information, including:
- PIPEDA (Personal Information Protection and Electronic Documents Act).
- Applicable provincial privacy legislation, including Quebec Law 25 and Ontario's PHIPA where the engagement involves health-sector clients.
- CPA Canada professional conduct rules and confidentiality obligations.
- CRA recordkeeping and electronic-records requirements.
Our infrastructure partners hold SOC 2 Type II attestation, and we leverage their audit reports as part of our own vendor risk management. Numinor itself does not hold a SOC 2 or ISO 27001 certification.
Report a vulnerability
We welcome reports from security researchers and members of the public. If you believe you have found a security issue in our Site or in our systems, please email us at hello@numinor.ca. Include enough detail for us to reproduce and assess the issue. We will respond within five business days and keep you informed as we work on remediation.
We ask that you do not access or modify data beyond what is necessary to confirm the issue, and that you give us reasonable time to remediate before public disclosure.
Contact
Questions about our security program? Reach out to:
Numinor Accounting · Security
hello@numinor.ca
22 King St S Suite #300, Waterloo, ON N2J 1N8
