OneManOS Privacy Policy
Version 1.9 · Effective November 8, 2026 · Last reviewed November 8, 2026
OneManOS (“we”, “us”) is a bookkeeping and job-management service for small construction and trades businesses, operated by 18334013 CANADA INC., a corporation incorporated under the laws of Canada, from Ontario. This policy explains what personal information we collect, why, where it lives, who processes it, how long we keep it, and the rights you have over it. It is written to be read, not skimmed past. It is short because the truth is short.
Who is responsible
18334013 CANADA INC. has designated a Privacy Officer who is accountable for personal information at OneManOS. For any privacy question, request, or complaint, or to ask who the Privacy Officer is, contact the Privacy Officer at support@oneman-os.com.
What we collect, and why
- Your account: your full name, email address and password (password handled by our authentication provider; we never see it in plain text).
- Your business records: the bookkeeping data you enter: invoices, quotes, expenses, income, receipts (including photos you upload), jobs, schedules, the kind of work you do (your trade, which we also count across all accounts to see which trades use OneManOS), and the contact details of your clients, vendors, and subcontractors. This exists solely so the app can do its job for you.
- Payroll and tax identifiers: if you use payroll features, your employees’ details including Social Insurance Numbers (required for T4 slips) and identity documents they upload, and your subcontractors’ SIN or business numbers (required for T5018 reporting). SINs are stored encrypted (AES-256-GCM) and are never shown in bulk lists or logs.
- Bank account data via Plaid: if you connect a bank account, we receive your transactions (date, description, amount) and balances from Plaid Inc. See the Plaid section below.
- Billing: when you pay for OneManOS, the payment is handled by Stripe. Your card details go straight to Stripe’s own payment pages; they never pass through OneManOS and we never see or store them. We keep only what we need to run your plan: your Stripe customer and subscription numbers, your plan, when your bill is due, and whether it is paid. Stripe gets your login email and business name so your receipts carry them.
- Sign-up list: if you joined our sign-up list before self-serve accounts opened, or asked us to tell you when your province is supported, we keep what you gave us (name, company, trade, email, province) only to contact you about OneManOS.
We collect nothing beyond what the features you use require, and we never sell personal information (yours, your clients’, or your employees’) to anyone, for any purpose.
Bank connections (Plaid)
Bank connections are powered by Plaid Inc. You sign in on your bank’s own page; we never see or store your banking credentials. Through Plaid we receive your account transactions and balances, used only to keep your books reconciled against your bank. Plaid’s handling of your data is described in Plaid’s End User Privacy Policy, and you can view and manage what Plaid holds about you at my.plaid.com. You can disconnect a bank at any time in Settings → Bank Accounts; disconnecting revokes our access with Plaid and removes pulled transactions that you never booked into your records. If you revoke access at your bank or through Plaid directly, we detect that and do the same.
AI features: what leaves the app
Some features use an AI model (provided by Anthropic) to save you typing. In plain terms, here is exactly what gets sent, per feature, only when you use that feature:
- Receipt scanning: the receipt photo you scan is sent to the AI to read the vendor, amounts, and items.
- Bank statement import (text): the statement text is scrubbed first: SINs, card numbers, account numbers, and address blocks are removed before anything is sent.
- Bank statement import (photo/vision): because a page image cannot be scrubbed, this mode is off until you explicitly agree in the app the first time you use it.
- Budget advisor: summarized spending by category, vendor names, and your city/province, to produce advice and local price comparisons.
This data is processed to provide the feature and is not used by us for advertising or sold to anyone. If you don’t use these features, nothing is sent.
Google user data (Gmail)
If you connect your Gmail account (Settings > Integrations), OneManOS asks Google for two things only: permission to send email from your Gmail account, and your Google account’s email address, so we can show which account is connected and put it on the emails and documents you send.
- We use this only to send the quotes, invoices, receipts and other emails you create and choose to send from OneManOS. We do not read, search or keep your emails, contacts, calendar or any other Google data.
- The access Google gives us is stored encrypted. You can disconnect at any time in Settings > Integrations, or remove OneManOS from your Google Account’s security settings.
- Google user data is never sent to an AI model, and is never used to develop, improve or train AI or machine learning models of any kind.
- We do not sell Google user data or use it for advertising. People at OneManOS do not read it, unless you ask us to (for example for support), for security, or when the law requires it.
OneManOS’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. The use of raw or derived user data received from Workspace APIs will adhere to the Google User Data Policy, including the Limited Use requirements.
Help chat and Contact us
The app has a Help chat (the Help button) and a Contact us form. When you use them:
- They are recorded. We save the chat: what you type, the answers, the page you were on, any thumbs up or down, and what the assistant looked up about your account. If you are logged in, the chat is linked to your account, and the assistant can read a few facts about your own account to answer you (your plan and trial dates, how your emails are sent, and which setup steps are done). It cannot change anything. A Contact us message is emailed to our support inbox with your login email, business name, plan and the page you came from. When the chat asks for a person, we also email our support inbox your login email and a short summary of the chat.
- People at OneManOS read them to answer you and to fix problems, and an AI model reads each day’s chats to write us a short report on what people asked, what went wrong, and what to improve.
- Anthropic processes chat messages to answer them (the Help chat is an AI assistant). Anthropic’s model also reads each day’s chats to write our daily report. Please do not type passwords, card numbers or other secrets into the chat.
- How long: chats are kept for 12 months and then deleted automatically. This includes chats by team members with a login. Contact us messages, Help chat alerts and daily reports are kept in our support inbox for up to 12 months. Deleting your account deletes your chats right away. Our daily summary reports, which do not name anyone, are kept for 12 months.
- Visitors who are not logged in can use the chat too. We then keep a random id in a cookie (kept up to 1 year) and a scrambled (hashed) form of your IP address, only to stop abuse; we never store the IP address itself.
- If you cancel or ask for a refund, we may ask why. Answering is optional. We keep your answers until you delete your account, and email them to our support inbox (with your login email only if you say we may contact you).
Where your data lives, and who processes it
Each customer’s bookkeeping data lives in its own fully isolated database; there are no shared tables between customers. Our service providers (“processors”), each used only for the purpose stated:
- Turso: hosts your isolated bookkeeping database (encrypted at rest, AES-256).
- Supabase: login and authentication, Help chat records, and storage of uploaded files (receipt photos, employee documents) in private, per-customer folders.
- Vercel: hosts and serves the application.
- Cloudflare: checks that a visitor using the Help chat or the login forms is a person (Turnstile). It receives your IP address for that check.
- Stripe: subscription payments, invoices and receipts for your OneManOS plan. Card details are entered on Stripe’s pages and never reach OneManOS.
- Resend: sends OneManOS’s own emails to your login email: account emails (confirming your email, password resets) and billing emails (a payment that did not go through, a trial ending, an account about to lock). It also delivers your Contact us messages to our support inbox. And when your business uses “Send from OneManOS”, Resend sends your documents (quotes, invoices, receipts, contracts and links to your subcontractors) on your business’s behalf, to the people you send them to.
- Plaid: bank connections, as described above.
- Anthropic: AI features, the Help chat and the daily Help chat report, as described above.
- Google: sending email you compose in the app through your connected Gmail account, and address autocomplete on address fields.
- Google (advertising and analytics): runs the ad-measurement and analytics tags described above, on the pages and only with the consent described above. A separate use from the Gmail-sending and address-autocomplete use already listed.
- Meta (Facebook and Instagram): runs the Personalized ads tag described above, where in use, on the pages and only with the consent described above.
- Microsoft (Clarity): runs the Site analytics session recordings and heatmaps described above, on the pages and only with the consent described above.
Storage outside Canada: your bookkeeping database (Turso), the application host (Vercel), and the Stripe, Resend, Plaid, Anthropic, Google, Meta, Microsoft, and Cloudflare services process data on infrastructure in the United States; login, uploaded files and Help chat records (Supabase) are hosted in Canada. While information is in the United States it is subject to the laws of that jurisdiction, including access by its courts, law enforcement, and national security authorities under its lawful process. We protect it in transit and at rest with encryption regardless of where it sits.
How we protect it
- One isolated database per customer, with no cross-customer access paths.
- All traffic encrypted in transit (TLS 1.2+); databases encrypted at rest.
- SINs and bank-connection credentials additionally encrypted at the application level (AES-256-GCM).
- Access to production infrastructure is limited to the owner and protected by multi-factor authentication.
- Inside the OneManOS app there are no analytics, advertising, or tracking scripts. The only cookies there are the ones that keep you logged in, keep the login steps secure, and, if you use the Help chat without logging in, a random chat id that lasts up to 1 year. The public website is different: see “Website advertising and analytics” below.
Website advertising and analytics
On our public website, meaning the pages that introduce OneManOS, never the app you log into, we use a small number of tools to see how people find us and which ads bring them here. These tools never run inside the OneManOS app, the installed web app, the mobile apps, the Team Member Privacy Notice page, or any page a client, employee or subcontractor opens through an emailed link. They run only on the homepage, the pricing and comparison pages, the sign-up page, and our ad landing pages.
A cookie banner asks first, and nothing loads before you choose. Your choice has three separate switches:
- Ad measurement: a Google tag measures which of our ads lead to a visit, starting sign-up, or finishing it.
- Personalized ads: the same Google tag, plus the Meta Pixel (Facebook and Instagram) where it is in use, show our ads to people who visited these pages. Choosing this also turns on Ad measurement.
- Site analytics: Google Analytics and Microsoft Clarity show us how people use these pages: pages viewed, clicks, scrolls, a masked recording of the visit (Clarity never records what you type, and always hides the contents of every form field), and whether a form on the page, including the Help chat’s message box, was started or submitted (never what was typed in it). Google Analytics also uses data from people signed into a Google account for its reports.
This is separate from the Google user data (Gmail) section above: Gmail data is never used for advertising.
If you create an account from one of these pages, one more choice appears: a box, unticked by default, asking whether we may tell Google, using a scrambled (hashed) copy of your email, never the email itself, that your sign-up came from one of our ads, and later, that your account became active (you saved your first quote or invoice) or that you started paying, and, if you take our money-back refund, that the payment was refunded (we change its amount to zero). We never tell Google your invoice amounts, payroll details, or anything else about your business; for a first payment, the only number sent is our own subscription price for your plan, in Canadian dollars.
Google, Meta and Microsoft each act as an independent company here, not as our processor. See “Where your data lives” below for what each receives and where it is processed. What they receive depends on your choice, but always includes your IP address and the pages you view. A cookie may remember your choice or your visit: our own choice cookie lasts 180 days, after which we ask again; Google Analytics’ cookie lasts up to 2 years, renewed each visit (some browsers shorten it); Microsoft Clarity keeps an individual recording 30 days (a sample it keeps for its own benchmarking can last up to 9 months). If you came from an ad, that ad’s own id is kept in your browser tab for the visit, and, only for the categories you chose, added to your account for up to 90 days so a later sign-up can be matched to it, then removed.
You can change or withdraw your choice at any time with “Cookie choices” at the bottom of every page these tools can run on. You can also opt out directly with Google (myadcenter.google.com) or through the NAI/AdChoices opt-out (optout.aboutads.info), which also covers Meta.
How long we keep it
- While your account is active: your records are kept because that is the product: your books.
- If you delete your account (Settings → Security → Danger Zone): your entire database, uploaded files, bank connections, Help chats, and login are permanently destroyed, immediately. This is real deletion, not archiving. Only two small things stay, and they are described next. Note that Canada Revenue Agency rules require you to keep business records for six years from the end of the last tax year they relate to. That duty is yours and survives deleting the account, so export what you need first.
- Your billing records are not deleted with your account. Your OneManOS billing records (the invoices and payments for your OneManOS subscription, kept in Stripe) are our own sales records, and Canadian tax rules require us to keep them for six years. They hold your name, email, plan and payment history, never your bookkeeping data.
- One small record stays to stop misuse. We keep a scrambled (hashed) form of your login email, with two dates: your free trial and your money-back refund. It holds no name and no email. It exists so that deleting an account and signing up again does not give a second free trial or a second refund.
- If your plan is not paid: nothing is deleted. A free trial that ends without a plan, or an account that took the money-back refund, locks right away. For a paid plan that is not paid, AI features pause right away and the account locks after 30 days. A locked account can still sign in to pay, download all its data, or delete the account. We never delete a locked account on our own.
- Help chats and support: kept 12 months, then deleted automatically (see Help chat and Contact us above).
- Working data: expired statement-import review batches are purged automatically; internal change logs are kept for up to 24 months; records of any security incident are kept at least five years, as regulators require.
Your rights
You can access, correct, export, and delete your information. Most of this is self-serve in the app; for anything else, email the Privacy Officer above and you will get a written response within 30 days. You may withdraw consent at any time (which may mean some features, like bank connections, stop working). If you believe we have handled your information improperly and we have not resolved it, you may complain to the Office of the Privacy Commissioner of Canada (or, for Quebec residents, the Commission d’accès à l’information).
People whose data you enter
As a customer, you enter information about your own clients, employees, and subcontractors. You are responsible for having the right to do so. Where the app collects information directly from your employees (the emailed onboarding form), that form links to this policy so they know how their information is handled: it is stored only in your business’s isolated database, used only for payroll and government filings you prepare, and protected as described above.
Team member and accountant logins
A business can give its team members their own login. Each team member also gets the short Team Member Privacy Notice when they create their login.
What we collect, and from whom
- For a team member (a worker, lead hand or office login): the name and email the business entered on their team member card; the login itself (email and password, kept by Supabase, our login provider); the role the business gave them; the hours the business records for them and whether each entry was approved; their pay stubs; when they last used their login; messages they send to the Help chat.
- If the business uses clock in and clock out: clock times, breaks, the time on their phone when they tapped and whether the tap reached us late, notes they add, and who made the tap (the person, or their lead hand clocking them in or out; a tap made by a lead hand for someone else uses our server’s time and records no location). Only if the business turns on location stamps AND the person says yes: the location of their phone at the moment of their own clock tap, with its accuracy. Nothing is recorded between taps or when they are not clocked in.
- Photos they add to a job: the picture itself, an optional caption, who added it and when. The phone makes the picture smaller, and our server rewrites the file so that only the picture and its rotation are kept. The place it was taken, the time and camera details, and any comments inside the file are not stored, so a job photo carries no location. Only JPEG pictures are accepted. Photos are kept in a private storage folder for the business, and a picture is only shown through a link that stops working after a few minutes.
- When a lead hand clocks a crew member in or out for them, the entry is saved with the lead hand’s name next to it. No location is recorded for that tap.
- For an accountant: name, email, login, which businesses they are connected to, and when they last used the dashboard.
Why
- So the business can pay its employees and keep the hours and payroll records Ontario law asks it to keep (3 years for hours, 6 years for payroll), and so its accountant can read the books.
Who sees it
- The business. The employer is responsible for the data; OneManOS processes it for them.
- The team member sees their own hours, pay stubs and account.
- A lead hand sees who is clocked in on the jobs they are on and the hours today of the crew on those jobs (names and hours, never pay), and can clock a crew member in or out for them. An office login uses the business pages for quotes, invoices, clients, jobs, expenses and bookkeeping, and never payroll, the bank, billing or other logins.
- Job photos are seen by the business, its office login, the lead hand and the team members who are on that job. They are never shown to the accountant or to subcontractors.
- An accountant sees the books, never team member documents or SINs, except on the T4 and T5018 slips needed for filing.
- OneManOS staff do not look at it, except to fix a problem the business reports.
Where
- The same place as the business’s other data, with the same protections (see the processors list).
How long
- With the business’s records. When a login is removed, the hours and pay stubs stay with the business. The login itself (email and password) is deleted when the team member deletes their login, or when the business is deleted.
- Exact clock locations are deleted after 90 days, or sooner if the business chooses 30 or 60 days. The hours stay; only the exact place is removed.
- Job photos stay with the business’s records until someone removes them. Archiving or closing a job does not remove its photos, and removing a team member’s login does not remove the photos they added. The business owner can remove any photo, one at a time. A team member can remove a photo they added for 15 minutes after adding it. When the business is deleted, its job photos are deleted too.
Your rights as a team member
- See your own hours and pay stubs in My hours and My pay.
- Ask the business to correct a record.
- Download your own data from Account.
- Remove a job photo you added, for 15 minutes after you add it. After that, ask the business owner.
- Delete your login from Account (the business keeps its records).
- Withdraw your location consent any time in Account. Taps after that carry no location; stamps already recorded are deleted at the end of the keep period above.
Subcontractor logins
A business can invite a subcontractor it works for to a free login. The subcontractor uses it to record their own hours, send invoices to that business and see when they are approved and paid. One login can work for several businesses.
What we collect, and from whom
- From the business: the subcontractor’s name and email (the address the invite is sent to), and the details the business already keeps on its subcontractor record.
- From the subcontractor: the login itself (email and password, kept by Supabase, our login provider); which businesses the login is connected to; when they last used it; the invoices they send from it; messages they send to the Help chat.
- The details they type into the short form that opens after they create the login: their business name, contact person, phone and address, whether they are registered for HST and their HST number, and the email where the business sends their payments. Also their WSIB details: their account number and clearance certificate with its expiry date, or, if they carry no WSIB coverage of their own, their authorisation for the business to hold back the WSIB premium from their pay, with the full name they typed as their signature and the date. Once the form is finished the subcontractor cannot change these details themselves: a change goes through the business.
- Hours they record with the clock: the job, the clock in and clock out times, breaks, the note they may type when they clock in or out, the time on their phone when they tapped and whether the tap reached us late. We never record the location of a subcontractor’s phone.
Why
- So the subcontractor can send their invoices from their phone and keep their own record of their hours, and so the business can receive, approve and pay those invoices and keep the records CRA asks it to keep (T5018, six years).
Who sees it
- Each business sees the invoices sent to it, and nothing the subcontractor does for another business. The hours a subcontractor records with the clock are not shown to the business: it sees them only as the hours the subcontractor puts on an invoice they send. The business is responsible for the records in its books; OneManOS processes them for it.
- The subcontractor sees their own invoices, payments, hours and the details each business has on file, and never the business’s prices, clients, other subcontractors or books.
- OneManOS staff do not look at it, except to fix a problem someone reports.
Where
- The login in Supabase; the invoices and hours in each business’s own database, with the same protections as the business’s other data (see the processors list).
How long
- Invoices stay with each business’s records, also after the login is removed. Hours recorded with the clock stay in the same database, where the business does not see them. When a business removes a login, that login is signed out of the business at once. The login itself (email and password) is kept until the subcontractor deletes it in Account or asks our Privacy Officer to delete it, or until the last business it works for deletes its OneManOS account.
Your rights as a subcontractor
- See your own invoices, payments, hours and details in your pages.
- Ask the business to correct a record.
- Delete your login from Account (each business keeps its records).
If something goes wrong
If a security incident creates a real risk of significant harm, we will notify the affected people and the required regulators (the OPC, Quebec’s CAI where applicable) and our bank-data partner Plaid, promptly and honestly, and keep the records of the incident the law requires.
Changes to this policy
We review this policy at least annually (the “last reviewed” date above) and update it whenever how we handle data actually changes. Material changes are versioned, and continuing to use the service after a change requires accepting the new version.
See also our Terms of Service.