Legal
Privacy Policy
How we collect, use, and protect your information.
Last updated: October 14, 2026 · Version 2 (interim)
This is an interim policy. It is written to describe what Noble Labor actually does today, in plain words, and it will be reviewed by a lawyer and updated. Where something is unfinished, we say so rather than describing an intention as if it were already built.
The short version
You are a worker, a hirer, or both. Here is what matters most.
- We do not sell your personal information. There are no advertising trackers, no ad networks and no behavioural analytics on this site.
- Your phone number is hidden on your profile. It is released to the person you are booked with once a booking is confirmed, so the two of you can coordinate the day. Accepting a quote releases both sides’ phone and email — that one is spelled out below.
- We record where your device is when you clock in and when you clock out of a booked shift. We do not record your location between those two moments, and we do not record it when you are not on a booked shift. The section called Where your location goes is the one worth reading.
- Our database is in Canada. Our files — photos, résumés, ID documents — are in the United States. Every company that touches your information is named below.
- You can ask us what we hold about you, ask us to correct it, and ask us to delete your account. Today all three go through a person, not a button, and we answer within 30 days.
- If we get it wrong, complain to us, and then to the Office of the Information and Privacy Commissioner for British Columbia. You do not need our permission to do that.
What we collect, and why
This is the heart of the policy. One line per thing, what it is for, who can see it, and how long we keep it. If something we collect is not on this list, that is a mistake and we want to hear about it.
- What we collect
- Your email address
- Why we collect it
- To create your account and sign you in, and to send you booking, invoice and account emails. Before you can hire we also check that your email address is confirmed — a confirmed email and a verified mobile number are both required. Company verification is not required to hire: a company that is not verified can still post jobs and send callouts, and workers are shown that it is not verified before they accept
- Who can see it
- You, and our staff. It is released to another member when a quote is accepted, and it is visible to signed-in members if you set your email address to public yourself
- How long we keep it
- While your account exists
- What we collect
- Your phone number
- Why we collect it
- To text you a callout when a hirer offers you work, to send you a one-time code when you verify your number, to alert a hirer when you clock in, and for day-of coordination once a booking is confirmed. If you hire on Noble Labor you have to verify a mobile number before you can post a job, send a callout or book anyone — so the person you book can reach a real human on the day, and so one person cannot stand up endless hiring accounts. We keep the fact that you verified it and the date. If you change your number it stops counting as verified until you verify the new one. Your number is also checked with our messaging provider to see whether it is a real mobile line
- Who can see it
- You; the person you are booked with, after a booking confirms; the other party to a quote, once the quote is accepted; and signed-in members if you set your number to public yourself. Otherwise hidden on your profile
- How long we keep it
- While your account exists
- What we collect
- An alert address for each phone or computer you switch alerts on for
- Why we collect it
- So your phone can buzz you the moment a hirer offers you work. On an on-demand job the first worker to accept gets it, so being told quickly is worth real money to you. When you say yes to alerts, your browser creates an address that points at that one device, plus two keys we use to lock the message so only your device can open it. We store those three things, linked to your account, along with when you switched alerts on and when you last opened Noble Labor on that device. That is all — no phone model, no device name, no IP address
- Who can see it
- Nobody but our own servers. No member account of any kind can read it, and it never appears on your profile
- How long we keep it
- Until you switch alerts off, or until your device stops accepting them. It is also deleted with your account. We are building a sweep that will retire an address you have not used for six months
- What we collect
- Your name
- Why we collect it
- To identify you to the other party — on your profile, on the callout text, on the invoice and on the job report
- Who can see it
- Anyone who can see your profile; the people you work with
- How long we keep it
- While your account exists
- What we collect
- Your postal code, and your street address if you enter one
- Why we collect it
- Your postal code is turned into the centre point of that postal area so jobs and workers can be matched by distance — that is an area, not your doorstep. Your postal code and city are also printed on the invoice, because an invoice names the parties to it
- Who can see it
- Your postal code is not shown on your profile. Your street address follows your address privacy setting, which starts at private. Your city and postal code do go to the hirer on the invoice
- How long we keep it
- While your account exists; the invoice copy is kept as a business record
- What we collect
- A job’s site address (entered by the hirer)
- Why we collect it
- To run the job — it goes to the worker who is booked, it is on the hirer’s job report, and it is the centre point we measure the clock-in distance from
- Who can see it
- By default, signed-in visitors can see the street address, map pin and postal code of a posted job. A hirer can switch that off when posting. People who are not signed in see the city only
- How long we keep it
- While the job posting exists
- What we collect
- Saved venues (hirers)
- Why we collect it
- When you save a job site as a venue, we keep its site address, postal code, city, province, map coordinates and time zone, so future jobs at that site fill in automatically
- Who can see it
- Only you. The map coordinates stay on our servers
- How long we keep it
- Until you remove the venue, or your account is permanently deleted
- What we collect
- Job-site searches and temporary selection records, where location search is available
- Why we collect it
- To find the job site and automatically determine its city and time zone. Mapbox receives the address or place-name search you enter through our server, with a random search-session code, renewed after about two minutes without a search or after 50 searches, that Mapbox cannot link to your account; if your profile has a Canadian postal code, we also send a fixed city-centre point for your province or territory (for example, Vancouver for BC), chosen from its first letter, so nearby results rank first — never your postal code or your own location. When you pick a result, Mapbox also receives that address (number, street, postal code, city and province) so it can confirm the exact point, and we work out the time zone from that point ourselves. When you reuse an older saved venue or job, we send its saved address and postal code to Mapbox once to re-confirm it. The address we save is the one Mapbox confirms; a venue name you picked is not kept. We do not deliberately send your account identifier. We keep the returned location suggestions and a temporary record linking your selection to your account, with the site coordinates, city, time zone and rule version. Coded lookup counters record attempts to prevent abuse
- Who can see it
- Mapbox receives the search text, the search-session code, the address you pick and, where applicable, that fixed provincial ranking point. Our hosting and temporary-storage providers process the lookup records. These temporary records are not shown to other members; a saved job follows the job-address visibility rules above
- How long we keep it
- Location suggestions expire after five minutes, the search-session code after about two minutes without a search, and selected-site verification records expire after one hour, in our temporary store. Coded lookup-attempt timestamps can remain for almost 48 hours. These periods do not describe provider logs or backups. Saved jobs and bookings follow their existing retention rules.
- What we collect
- Address-box searches in the address boxes outside job posting (your profile, company verification, programs, quote requests, posts and Projects), for signed-in members
- Why we collect it
- To suggest and fill in the address or city you are typing. Mapbox receives what you type through our server, with a random search-session code, renewed after about two minutes without a search or after 50 searches, that Mapbox cannot link to your account, and the countries searched (Canada, and the United States where the box allows it). When you pick a result, Mapbox also receives that address (number, street, postal code, city and province or state), or that city with its province or state, so it can confirm it. We do not deliberately send your account identifier, and we send no ranking point. Each suggestion is held in a temporary record tied to your account, so only you can pick it. The form then receives the address Mapbox confirms (with any unit number you typed in front of a street address kept there, where the box has room), with its city, province or state, postal code (for a street address) and map point. The address box itself keeps no address longer than three minutes; whether the form keeps the address depends on that form.
- Who can see it
- Mapbox receives the search text, the search-session code, the countries searched and the address or city you pick. Our hosting and temporary-storage providers process the temporary records. These records are not shown to other members
- How long we keep it
- Each suggestion, and the confirmed address once you pick it, expires after three minutes in our temporary store; the search-session code after about two minutes without a search. Coded lookup-attempt timestamps can remain for almost 48 hours. These periods do not describe provider logs or backups. What a form saves follows that form’s own retention.
- What we collect
- Where your device is when you clock IN
- Why we collect it
- Two things. First, to check how far you are from the job site when you say you are there — see Where your location goes. Second, to keep a record of it as evidence of attendance if there is ever a dispute about the shift
- Who can see it
- No member account of any kind can read the coordinates — not the hirer, not us through the website. Our staff can read them on our administrative tools to look into a dispute
- How long we keep it
- See How long we keep things
- What we collect
- Where your device is when you clock OUT
- Why we collect it
- To keep a record of where you were when you finished. We do not run a distance check at clock-out — the coordinate is recorded, not compared to anything
- Who can see it
- Same as clock-in
- How long we keep it
- See How long we keep things
- What we collect
- Your clock-in and clock-out times
- Why we collect it
- To record attendance, and to fill in the starting hours and total on your invoice
- Who can see it
- You and the other party; they appear on the job report
- How long we keep it
- For the life of the booking record
- What we collect
- Your work history, skills, trades and bio
- Why we collect it
- To show a hirer your experience
- Who can see it
- On your profile. If you list a reference, their phone and email are not shown with it
- How long we keep it
- While your account exists
- What we collect
- Your certifications and tickets
- Why we collect it
- To show what you are qualified for
- Who can see it
- The type, name, issuer and status are shown on your profile. The certificate number itself is not shown to other members
- How long we keep it
- While your account exists
- What we collect
- WCB number, business number, licence number, liability insurance (a statement)
- Why we collect it
- To verify a business at our verification desk. Your business number is also printed on the quotes you send
- Who can see it
- Your business number appears on the quotes you send. If our desk has verified your WCB account number, that number appears on your quotes too, and your profile shows 'WCB · Verified by Noble Labor'. Your licence number is shown to no other member. For liability insurance we record only your own statement that you carry it — your profile shows 'stated by the company' or 'not indicated', never a policy number
- How long we keep it
- Your business and licence numbers: while your account exists. A desk-verified WCB number and your liability statement: while your company stays verified — we clear them if a verification is withdrawn
- What we collect
- Your company-verification application — company name, legal name, business number, business address, phone, contact name and role, website and social links, WCB account number and province, your liability statement, and your confirmations
- Why we collect it
- To verify that your business is real and, if you give one, to look up your WCB account with WorkSafeBC
- Who can see it
- Noble Labor's verification desk reads it. The only details that ever leave the desk are your business number and legal business name, which print on the quotes you send, and — once our desk has verified it — your WCB account number, which prints there too. Other members see the outcome — verified, stated, or not indicated — never the rest. If you work on your own, the address and phone here are probably your home address and personal mobile: they are used only by our verification desk, they are never shown on your profile, and your profile's address-privacy setting does not apply to them
- How long we keep it
- As the record of your application, while your account exists
- What we collect
- Your résumé file
- Why we collect it
- So you can apply for jobs
- Who can see it
- The owner of a job you apply to. Links to it expire after 15 minutes
- How long we keep it
- See How long we keep things
- What we collect
- Vetting documents — government photo ID, a criminal record check, proof of address
- Why we collect it
- To check identity and eligibility before a "vetted" mark goes on a profile. This review is done in-house, by Noble Labor. We do not send these documents to a screening company today. If we engage a trusted third-party verification provider in the future, your documents may be shared with them for verification purposes only, and we will update this policy before that happens
- Who can see it
- Senior Noble Labor administrators only. They are not served to the public internet
- How long we keep it
- See How long we keep things
- What we collect
- Profile photo, cover image, logo, gallery photos
- Why we collect it
- To show on your profile
- Who can see it
- Anyone who can see your profile. These are served from a public file host, so a person who has the direct link to an image can open it without signing in
- How long we keep it
- See How long we keep things
- What we collect
- Photos and video you post to the feed
- Why we collect it
- To publish on the feed — and each one is screened automatically for explicit or violent content before it is shown. See Automatic photo screening
- Who can see it
- Whoever the post is shown to; the screening service
- How long we keep it
- While the post exists
- What we collect
- Your milestone campaign and its updates — the title, description and goal, the deadline, category and tags, the city, region and country you add, the amount raised and number of supporters shown on it, the photos and video you upload, and any updates you post (a title, a short summary, the text, the dates you post or edit them, and up to 6 photos and 1 video each). We also store a postal code with the campaign, taken from your profile unless you enter one; it is not shown
- Why we collect it
- To show your campaign, and the progress you share on it, to the people you want to reach
- Who can see it
- Public, including people who are not signed in, as long as your profile is visible — hiding your profile or closing your account takes the campaign down too (a photo or video link someone already opened can keep working for up to an hour). Your campaign and its own photos and video can remain public after the campaign ends; your updates, and the photos and video attached to them, are shown only while the campaign is active. Anyone who can see your campaign can copy it, and we cannot recall copies other people have already made
- How long we keep it
- While the campaign exists, and deleted with your account. When you remove an update, we delete its text and stop showing it straight away. The photos and video that belong only to that update stop appearing on your campaign at once (a link someone already opened can keep working for up to an hour) and are queued for deletion from our file storage. A photo or video that is also your campaign's cover, is used by another update, or is another video's preview image is not deleted — it stays on your campaign. We keep a short record that the update existed (when it was posted and removed, with no text) until the campaign or your account is deleted
- What we collect
- Messages and the images attached to them
- Why we collect it
- So you and the other party can talk on the platform
- Who can see it
- The people in that conversation. The alert we send about a new message includes the opening of it
- How long we keep it
- Kept — there is no automatic deletion today
- What we collect
- Notifications we send you
- Why we collect it
- To tell you something happened on a booking, a job or your profile
- Who can see it
- You. They carry the other person’s name and the job title
- How long we keep it
- Kept — there is no automatic deletion today
- What we collect
- Endorsements, follows and connections
- Why we collect it
- To build your professional network
- Who can see it
- Counts are visible publicly; the endorsements themselves are shown to signed-in members
- How long we keep it
- While your account exists
- What we collect
- Reviews
- Why we collect it
- Reputation — reviews only mean something if people can read them
- Who can see it
- Public, including the review text, the stars, and the reviewer’s name and photo
- How long we keep it
- Kept
- What we collect
- Who looked at your profile
- Why we collect it
- When a signed-in member opens your profile, we record who it was, when, and which part of the site they came from. See Being looked at below
- Who can see it
- You are not shown who viewed you today. We can look it up
- How long we keep it
- Kept — no deletion schedule is set
- What we collect
- Late cancellations and no-shows
- Why we collect it
- To warn a future counterparty about repeated short-notice cancellations. See Do we keep score of whether you show up?
- Who can see it
- The people you are booked with, on the screens where they manage that booking. It is not on your public profile
- How long we keep it
- The counts are kept
- What we collect
- A hirer’s live "not on site" flag
- Why we collect it
- So a hirer can say, during a shift, that a worker has not turned up. It alerts you by notification, email and text, and clocking in clears it
- Who can see it
- You and that hirer
- How long we keep it
- For the life of the booking record
- What we collect
- A cancel-by-agreement record
- Why we collect it
- When both sides agree to cancel a booking, we record who proposed it and that you both agreed — that is what lets it close with no reliability mark on either of you
- Who can see it
- You and the other party
- How long we keep it
- For the life of the booking record
- What we collect
- Invoices and booking records
- Why we collect it
- The billing document for the work. It names both parties: your name, city and postal code go to the hirer, and their name, city and postal code — plus their street address when the hirer is a business — come to you
- Who can see it
- Both parties
- How long we keep it
- Kept as business records, including after your account is closed
- What we collect
- A hirer’s supervision confirmation when creating an on-demand job
- Why we collect it
- We save the exact supervision statement you confirm and the time you create the job, so there is a record of what you confirmed for that job. This records your confirmation, not proof that supervision occurred
- Who can see it
- You, as the hirer, and administrators with super-user access
- How long we keep it
- Kept with the job record. Deleting a disposable job deletes its confirmation. Jobs protected by committed work, attendance or other work records cannot be deleted through job deletion. Account deletion keeps jobs with any booking record, including unanswered or cancelled bookings, and their confirmations. There is no automatic deletion timer for retained job records
- What we collect
- Your acknowledgment when a job is paid off the platform
- Why we collect it
- Some jobs are paid by the hirer directly. When you accept one of those, we record that you were told the payment does not go through Noble Labor and that our payment protection does not apply
- Who can see it
- Both parties, and our staff
- How long we keep it
- For the life of the booking record
- What we collect
- Your acknowledgment when the hirer is not verified
- Why we collect it
- Some hirers have not been through our verification desk. Their job says so — the business reads “not verified”, WCB reads “not verified” and liability reads “not indicated” — and when you accept one of those we record the moment you confirmed you had read that and were taking the job anyway. It is a record of what you were told, not a judgement about you
- Who can see it
- Our staff
- How long we keep it
- For the life of the booking record
- What we collect
- The record that you accepted our Terms and this policy
- Why we collect it
- Proof of what you agreed to and when
- Who can see it
- Our staff
- How long we keep it
- While your account exists
- What we collect
- "How did you hear about us?"
- Why we collect it
- We ask, and we store your answer. We are not doing anything else with it today
- Who can see it
- Our staff
- How long we keep it
- While your account exists
- What we collect
- Your IP address and browser
- Why we collect it
- Three places: our sign-in provider records them when you sign in; our anti-abuse service uses your IP for a few minutes to stop spam; and when a page shows a map, your browser contacts Mapbox directly, so Mapbox receives them (see the list of companies below). When a signed-in member opens a job posting we record who opened it and when — not the IP address or browser
- Who can see it
- Our staff and those providers
- How long we keep it
- Sign-in records: for the life of that session record. Anti-abuse: 1 to 10 minutes. Mapbox: under its own policy
- What we collect
- A "Build With Us" message (a bug report or an idea)
- Why we collect it
- So we can fix what broke and hear your ideas. It carries your message, whether it is a bug or an idea, the page you were on (only the page address, without anything after a "?"), your account and your account’s email so we can reply. It never includes a screenshot. A copy is emailed to our support inbox
- Who can see it
- Our staff, our email provider (to deliver the copy), and the provider that hosts our support inbox
- How long we keep it
- Kept with your account, and deleted when the account is permanently deleted. The emailed copy stays in our support inbox until we delete it by hand (ask and we will). "Report a problem" reports sent before October 14, 2026 went to our error-monitoring provider and are deleted on its schedule (we are confirming the exact period), or sooner if you ask
- What we collect
- Details of a resident, entered by a property manager
- Why we collect it
- So a job can be coordinated at that address. See What if someone else entered your details?
- Who can see it
- That property manager and our staff
- How long we keep it
- Kept
- What we collect
- A training provider’s program contact email and phone
- Why we collect it
- So people can ask about a course. The school chooses whether to add one; it is empty unless they do
- Who can see it
- Anyone who opens that program page
- How long we keep it
- While the program exists
- What we collect
- Sign-in links and session records
- Why we collect it
- So a worker can open a callout from a text message without needing a password
- Who can see it
- Our servers only
- How long we keep it
- Kept
- What we collect
- Two-step login, if you set it up
- Why we collect it
- To ask for a code from your authenticator app when you sign in. Our sign-in provider (Supabase, in Canada) holds the app’s secret key and notes your IP address each time a code is checked; for your ten backup codes we keep only scrambled copies, never the codes themselves
- Who can see it
- Our servers only
- How long we keep it
- Normally removed as soon as you turn two-step login off or use a backup code. If that clean-up fails, or you leave a set-up unfinished, it is removed the next time you set it up. Always deleted with your account
- What we collect
- Internal logs
- Why we collect it
- Diagnostics — records of sign-up events and expiry jobs, so we can tell what went wrong
- Who can see it
- Our staff
- How long we keep it
- Kept. Some of these keep an account identifier after the account itself is gone
| What we collect | Why we collect it | Who can see it | How long we keep it |
|---|---|---|---|
| Your email address | To create your account and sign you in, and to send you booking, invoice and account emails. Before you can hire we also check that your email address is confirmed — a confirmed email and a verified mobile number are both required. Company verification is not required to hire: a company that is not verified can still post jobs and send callouts, and workers are shown that it is not verified before they accept | You, and our staff. It is released to another member when a quote is accepted, and it is visible to signed-in members if you set your email address to public yourself | While your account exists |
| Your phone number | To text you a callout when a hirer offers you work, to send you a one-time code when you verify your number, to alert a hirer when you clock in, and for day-of coordination once a booking is confirmed. If you hire on Noble Labor you have to verify a mobile number before you can post a job, send a callout or book anyone — so the person you book can reach a real human on the day, and so one person cannot stand up endless hiring accounts. We keep the fact that you verified it and the date. If you change your number it stops counting as verified until you verify the new one. Your number is also checked with our messaging provider to see whether it is a real mobile line | You; the person you are booked with, after a booking confirms; the other party to a quote, once the quote is accepted; and signed-in members if you set your number to public yourself. Otherwise hidden on your profile | While your account exists |
| An alert address for each phone or computer you switch alerts on for | So your phone can buzz you the moment a hirer offers you work. On an on-demand job the first worker to accept gets it, so being told quickly is worth real money to you. When you say yes to alerts, your browser creates an address that points at that one device, plus two keys we use to lock the message so only your device can open it. We store those three things, linked to your account, along with when you switched alerts on and when you last opened Noble Labor on that device. That is all — no phone model, no device name, no IP address | Nobody but our own servers. No member account of any kind can read it, and it never appears on your profile | Until you switch alerts off, or until your device stops accepting them. It is also deleted with your account. We are building a sweep that will retire an address you have not used for six months |
| Your name | To identify you to the other party — on your profile, on the callout text, on the invoice and on the job report | Anyone who can see your profile; the people you work with | While your account exists |
| Your postal code, and your street address if you enter one | Your postal code is turned into the centre point of that postal area so jobs and workers can be matched by distance — that is an area, not your doorstep. Your postal code and city are also printed on the invoice, because an invoice names the parties to it | Your postal code is not shown on your profile. Your street address follows your address privacy setting, which starts at private. Your city and postal code do go to the hirer on the invoice | While your account exists; the invoice copy is kept as a business record |
| A job’s site address (entered by the hirer) | To run the job — it goes to the worker who is booked, it is on the hirer’s job report, and it is the centre point we measure the clock-in distance from | By default, signed-in visitors can see the street address, map pin and postal code of a posted job. A hirer can switch that off when posting. People who are not signed in see the city only | While the job posting exists |
| Saved venues (hirers) | When you save a job site as a venue, we keep its site address, postal code, city, province, map coordinates and time zone, so future jobs at that site fill in automatically | Only you. The map coordinates stay on our servers | Until you remove the venue, or your account is permanently deleted |
| Job-site searches and temporary selection records, where location search is available | To find the job site and automatically determine its city and time zone. Mapbox receives the address or place-name search you enter through our server, with a random search-session code, renewed after about two minutes without a search or after 50 searches, that Mapbox cannot link to your account; if your profile has a Canadian postal code, we also send a fixed city-centre point for your province or territory (for example, Vancouver for BC), chosen from its first letter, so nearby results rank first — never your postal code or your own location. When you pick a result, Mapbox also receives that address (number, street, postal code, city and province) so it can confirm the exact point, and we work out the time zone from that point ourselves. When you reuse an older saved venue or job, we send its saved address and postal code to Mapbox once to re-confirm it. The address we save is the one Mapbox confirms; a venue name you picked is not kept. We do not deliberately send your account identifier. We keep the returned location suggestions and a temporary record linking your selection to your account, with the site coordinates, city, time zone and rule version. Coded lookup counters record attempts to prevent abuse | Mapbox receives the search text, the search-session code, the address you pick and, where applicable, that fixed provincial ranking point. Our hosting and temporary-storage providers process the lookup records. These temporary records are not shown to other members; a saved job follows the job-address visibility rules above | Location suggestions expire after five minutes, the search-session code after about two minutes without a search, and selected-site verification records expire after one hour, in our temporary store. Coded lookup-attempt timestamps can remain for almost 48 hours. These periods do not describe provider logs or backups. Saved jobs and bookings follow their existing retention rules. |
| Address-box searches in the address boxes outside job posting (your profile, company verification, programs, quote requests, posts and Projects), for signed-in members | To suggest and fill in the address or city you are typing. Mapbox receives what you type through our server, with a random search-session code, renewed after about two minutes without a search or after 50 searches, that Mapbox cannot link to your account, and the countries searched (Canada, and the United States where the box allows it). When you pick a result, Mapbox also receives that address (number, street, postal code, city and province or state), or that city with its province or state, so it can confirm it. We do not deliberately send your account identifier, and we send no ranking point. Each suggestion is held in a temporary record tied to your account, so only you can pick it. The form then receives the address Mapbox confirms (with any unit number you typed in front of a street address kept there, where the box has room), with its city, province or state, postal code (for a street address) and map point. The address box itself keeps no address longer than three minutes; whether the form keeps the address depends on that form. | Mapbox receives the search text, the search-session code, the countries searched and the address or city you pick. Our hosting and temporary-storage providers process the temporary records. These records are not shown to other members | Each suggestion, and the confirmed address once you pick it, expires after three minutes in our temporary store; the search-session code after about two minutes without a search. Coded lookup-attempt timestamps can remain for almost 48 hours. These periods do not describe provider logs or backups. What a form saves follows that form’s own retention. |
| Where your device is when you clock IN | Two things. First, to check how far you are from the job site when you say you are there — see Where your location goes. Second, to keep a record of it as evidence of attendance if there is ever a dispute about the shift | No member account of any kind can read the coordinates — not the hirer, not us through the website. Our staff can read them on our administrative tools to look into a dispute | See How long we keep things |
| Where your device is when you clock OUT | To keep a record of where you were when you finished. We do not run a distance check at clock-out — the coordinate is recorded, not compared to anything | Same as clock-in | See How long we keep things |
| Your clock-in and clock-out times | To record attendance, and to fill in the starting hours and total on your invoice | You and the other party; they appear on the job report | For the life of the booking record |
| Your work history, skills, trades and bio | To show a hirer your experience | On your profile. If you list a reference, their phone and email are not shown with it | While your account exists |
| Your certifications and tickets | To show what you are qualified for | The type, name, issuer and status are shown on your profile. The certificate number itself is not shown to other members | While your account exists |
| WCB number, business number, licence number, liability insurance (a statement) | To verify a business at our verification desk. Your business number is also printed on the quotes you send | Your business number appears on the quotes you send. If our desk has verified your WCB account number, that number appears on your quotes too, and your profile shows 'WCB · Verified by Noble Labor'. Your licence number is shown to no other member. For liability insurance we record only your own statement that you carry it — your profile shows 'stated by the company' or 'not indicated', never a policy number | Your business and licence numbers: while your account exists. A desk-verified WCB number and your liability statement: while your company stays verified — we clear them if a verification is withdrawn |
| Your company-verification application — company name, legal name, business number, business address, phone, contact name and role, website and social links, WCB account number and province, your liability statement, and your confirmations | To verify that your business is real and, if you give one, to look up your WCB account with WorkSafeBC | Noble Labor's verification desk reads it. The only details that ever leave the desk are your business number and legal business name, which print on the quotes you send, and — once our desk has verified it — your WCB account number, which prints there too. Other members see the outcome — verified, stated, or not indicated — never the rest. If you work on your own, the address and phone here are probably your home address and personal mobile: they are used only by our verification desk, they are never shown on your profile, and your profile's address-privacy setting does not apply to them | As the record of your application, while your account exists |
| Your résumé file | So you can apply for jobs | The owner of a job you apply to. Links to it expire after 15 minutes | See How long we keep things |
| Vetting documents — government photo ID, a criminal record check, proof of address | To check identity and eligibility before a "vetted" mark goes on a profile. This review is done in-house, by Noble Labor. We do not send these documents to a screening company today. If we engage a trusted third-party verification provider in the future, your documents may be shared with them for verification purposes only, and we will update this policy before that happens | Senior Noble Labor administrators only. They are not served to the public internet | See How long we keep things |
| Profile photo, cover image, logo, gallery photos | To show on your profile | Anyone who can see your profile. These are served from a public file host, so a person who has the direct link to an image can open it without signing in | See How long we keep things |
| Photos and video you post to the feed | To publish on the feed — and each one is screened automatically for explicit or violent content before it is shown. See Automatic photo screening | Whoever the post is shown to; the screening service | While the post exists |
| Your milestone campaign and its updates — the title, description and goal, the deadline, category and tags, the city, region and country you add, the amount raised and number of supporters shown on it, the photos and video you upload, and any updates you post (a title, a short summary, the text, the dates you post or edit them, and up to 6 photos and 1 video each). We also store a postal code with the campaign, taken from your profile unless you enter one; it is not shown | To show your campaign, and the progress you share on it, to the people you want to reach | Public, including people who are not signed in, as long as your profile is visible — hiding your profile or closing your account takes the campaign down too (a photo or video link someone already opened can keep working for up to an hour). Your campaign and its own photos and video can remain public after the campaign ends; your updates, and the photos and video attached to them, are shown only while the campaign is active. Anyone who can see your campaign can copy it, and we cannot recall copies other people have already made | While the campaign exists, and deleted with your account. When you remove an update, we delete its text and stop showing it straight away. The photos and video that belong only to that update stop appearing on your campaign at once (a link someone already opened can keep working for up to an hour) and are queued for deletion from our file storage. A photo or video that is also your campaign's cover, is used by another update, or is another video's preview image is not deleted — it stays on your campaign. We keep a short record that the update existed (when it was posted and removed, with no text) until the campaign or your account is deleted |
| Messages and the images attached to them | So you and the other party can talk on the platform | The people in that conversation. The alert we send about a new message includes the opening of it | Kept — there is no automatic deletion today |
| Notifications we send you | To tell you something happened on a booking, a job or your profile | You. They carry the other person’s name and the job title | Kept — there is no automatic deletion today |
| Endorsements, follows and connections | To build your professional network | Counts are visible publicly; the endorsements themselves are shown to signed-in members | While your account exists |
| Reviews | Reputation — reviews only mean something if people can read them | Public, including the review text, the stars, and the reviewer’s name and photo | Kept |
| Who looked at your profile | When a signed-in member opens your profile, we record who it was, when, and which part of the site they came from. See Being looked at below | You are not shown who viewed you today. We can look it up | Kept — no deletion schedule is set |
| Late cancellations and no-shows | To warn a future counterparty about repeated short-notice cancellations. See Do we keep score of whether you show up? | The people you are booked with, on the screens where they manage that booking. It is not on your public profile | The counts are kept |
| A hirer’s live "not on site" flag | So a hirer can say, during a shift, that a worker has not turned up. It alerts you by notification, email and text, and clocking in clears it | You and that hirer | For the life of the booking record |
| A cancel-by-agreement record | When both sides agree to cancel a booking, we record who proposed it and that you both agreed — that is what lets it close with no reliability mark on either of you | You and the other party | For the life of the booking record |
| Invoices and booking records | The billing document for the work. It names both parties: your name, city and postal code go to the hirer, and their name, city and postal code — plus their street address when the hirer is a business — come to you | Both parties | Kept as business records, including after your account is closed |
| A hirer’s supervision confirmation when creating an on-demand job | We save the exact supervision statement you confirm and the time you create the job, so there is a record of what you confirmed for that job. This records your confirmation, not proof that supervision occurred | You, as the hirer, and administrators with super-user access | Kept with the job record. Deleting a disposable job deletes its confirmation. Jobs protected by committed work, attendance or other work records cannot be deleted through job deletion. Account deletion keeps jobs with any booking record, including unanswered or cancelled bookings, and their confirmations. There is no automatic deletion timer for retained job records |
| Your acknowledgment when a job is paid off the platform | Some jobs are paid by the hirer directly. When you accept one of those, we record that you were told the payment does not go through Noble Labor and that our payment protection does not apply | Both parties, and our staff | For the life of the booking record |
| Your acknowledgment when the hirer is not verified | Some hirers have not been through our verification desk. Their job says so — the business reads “not verified”, WCB reads “not verified” and liability reads “not indicated” — and when you accept one of those we record the moment you confirmed you had read that and were taking the job anyway. It is a record of what you were told, not a judgement about you | Our staff | For the life of the booking record |
| The record that you accepted our Terms and this policy | Proof of what you agreed to and when | Our staff | While your account exists |
| "How did you hear about us?" | We ask, and we store your answer. We are not doing anything else with it today | Our staff | While your account exists |
| Your IP address and browser | Three places: our sign-in provider records them when you sign in; our anti-abuse service uses your IP for a few minutes to stop spam; and when a page shows a map, your browser contacts Mapbox directly, so Mapbox receives them (see the list of companies below). When a signed-in member opens a job posting we record who opened it and when — not the IP address or browser | Our staff and those providers | Sign-in records: for the life of that session record. Anti-abuse: 1 to 10 minutes. Mapbox: under its own policy |
| A "Build With Us" message (a bug report or an idea) | So we can fix what broke and hear your ideas. It carries your message, whether it is a bug or an idea, the page you were on (only the page address, without anything after a "?"), your account and your account’s email so we can reply. It never includes a screenshot. A copy is emailed to our support inbox | Our staff, our email provider (to deliver the copy), and the provider that hosts our support inbox | Kept with your account, and deleted when the account is permanently deleted. The emailed copy stays in our support inbox until we delete it by hand (ask and we will). "Report a problem" reports sent before October 14, 2026 went to our error-monitoring provider and are deleted on its schedule (we are confirming the exact period), or sooner if you ask |
| Details of a resident, entered by a property manager | So a job can be coordinated at that address. See What if someone else entered your details? | That property manager and our staff | Kept |
| A training provider’s program contact email and phone | So people can ask about a course. The school chooses whether to add one; it is empty unless they do | Anyone who opens that program page | While the program exists |
| Sign-in links and session records | So a worker can open a callout from a text message without needing a password | Our servers only | Kept |
| Two-step login, if you set it up | To ask for a code from your authenticator app when you sign in. Our sign-in provider (Supabase, in Canada) holds the app’s secret key and notes your IP address each time a code is checked; for your ten backup codes we keep only scrambled copies, never the codes themselves | Our servers only | Normally removed as soon as you turn two-step login off or use a backup code. If that clean-up fails, or you leave a set-up unfinished, it is removed the next time you set it up. Always deleted with your account |
| Internal logs | Diagnostics — records of sign-up events and expiry jobs, so we can tell what went wrong | Our staff | Kept. Some of these keep an account identifier after the account itself is gone |
Things we do not collect at all. We have no date-of-birth field, no gender field, no social insurance number, and no bank account or card number anywhere in our database.
Being looked at
When you open another member’s profile while signed in, we record that it was you, when, and which part of the site you came from.
Right now, other members are not shown who viewed them — as far as anyone else on Noble Labor is concerned, you are browsing anonymously. It is not anonymous to us, and we would rather say that plainly than let the word "anonymous" do work it cannot do. We keep your identity against that view and we can look it up. We do that for two reasons: to look into abuse, harassment or impersonation when someone reports it, and because we intend to build a feature that shows a member who has been looking at their profile. If and when that feature launches, we will describe it here first, including whether you can switch it off. We do not sell this information.
People who are not signed in are not recorded at all.
Where your location goes
This is the most sensitive thing we hold, so this section is deliberately specific.
There are three different kinds of location on this platform, and they are not the same thing.
1. Your postal area. When you enter your postal code we convert it to the centre point of that postal area so jobs and workers can be matched by distance. That is an area, not your doorstep — we do not geocode you to a street address. Your city is shown on your profile; your postal code is not. It does appear on your invoice, because an invoice names the parties to it. We also use its first letter to rank job-site search suggestions toward your province.
2. A job site’s address. A hirer gives the site address when posting. Some of these are private homes. People who are not signed in see the city only. Signed-in visitors can see the full address and map pin by default, and the hirer can turn that off when they post. The booked worker gets the address, and it appears on the job report we email the hirer.
Finding a job site and its time zone. Where location search is available, the address or place-name search you enter goes through our server to Mapbox, together with a random search-session code, renewed after about two minutes without a search or after 50 searches, that Mapbox cannot link to your account, and Mapbox returns possible locations. To rank nearby results first, we may also send a fixed city-centre point for your province or territory, chosen from the first letter of your profile postal code; we never send the postal code itself. When you pick a location, Mapbox also receives that address so it can confirm the exact point, and we work out the time zone from that point ourselves. We do not deliberately send your account identifier to Mapbox. Before October 2026 these searches went to Geoapify, which remains a backup until we remove it. We use your selected location to set the job’s city, coordinates and time zone automatically. The other address boxes on the site (your profile, company verification, programs, quote requests, posts and Projects) also search Mapbox through our server for signed-in members, in the same way but without a ranking point. Postal codes are turned into map coordinates by Mapbox, with Google’s postal-code tool kept as a backup, as described below.
3. Your device’s location when you clock in and out of a shift. This is the one that matters.
We record your device’s location at two moments: when you clock in, and when you clock out. We do not record it between those two moments, and we do not record it when you are not on a booked shift.
At each of those two moments we store your coordinates, the time, and the kind of device when you clock in; if you clock in from a long way away and confirm it, we also store how far.
At clock-in you are asked for your location. At clock-out it is recorded as part of clocking out, without a separate prompt. We are telling you that because you would otherwise not know.
What we do with it, honestly, because the two ends are different:
- At clock-in we check the distance between you and the job site. On a phone, being too far away blocks the clock-in. On a desktop browser, it warns you and asks you to confirm.
- At clock-out we do not check anything. The coordinate is recorded as part of the attendance record. It is not compared to the job site.
Who sees it:
- The hirer does not see your coordinates. No member account of any kind can read those fields — they are held back from the website itself, not just hidden on a screen.
- The hirer’s job report shows a location marker. Be clear about what that marker means: it means a location was captured at one of your punches. It is not a statement that you were at the site.
- One fact about your location does reach the hirer. When you clock in we text and email them. If you are a long way from the site, that message says roughly how far. So while nobody sees your coordinates, a hirer can learn that you were not at the site.
- Noble Labor staff can open the stored records to look into a dispute or suspected fraud.
How long we keep it: We keep these records for 12 months after you clock in or out, and then delete the coordinates. The record that you clocked in and out stays.
What we do not do with it. We do not use your location for advertising, we do not sell it, and we do not share it outside the service providers named below unless the law requires us to. The only device location we store is your clock-in and clock-out on a shift you accepted. One other thing worth knowing: if you press "Use my location" while searching, your device sends its coordinates with that search so results can be ranked by distance — we use them for that search and do not save them to your profile.
What the person who hires you can see
Almost no platform answers this. Here is our answer.
Before you have any relationship with them: your name, your photo, your city, your bio, your skills and trades, your certifications (type, name, issuer and status — not the certificate number), your work history, your hourly rate, your reviews and endorsements, and whether you are marked as vetted. If you have a company profile or have switched on subcontract work, it also shows whether your business is verified, whether your WCB account was verified, and whether you have stated you carry liability insurance — shown as verified, stated, or not indicated.
Once a booking is confirmed, they also get your phone number, for coordinating the day. Not before. It is released by the booking itself — it is not sitting on your profile waiting to be found.
Once you have worked a shift, they get the work record: your clock-in and clock-out times, minutes late if any, a no-show marker if one was recorded, the hours and pay total from your invoice, and the location marker described above. These arrive in a job report email.
Your invoice names both parties. Your name, city and postal code go to the hirer. Their name, city and postal code come to you, plus their street address when the hirer is a business. That is what an invoice is for, and it is deliberate.
If you accept a quote, both sides exchange phone number and email address. Apart from setting your email address to public yourself, this is the only place on the platform where an email address is released to another member, and it happens because a quoted job cannot be run without direct contact. Before a quote is accepted, neither side sees the other’s contact details.
A hirer does not get, through a booking: your email address, your street address, your clock-in or clock-out coordinates, your password (we cannot see it either), or your private notes, saved lists and dismissed alerts.
What you can see about the person hiring you
It goes both ways, so here is the other direction. On a job posting, on a callout and on a confirmed booking, we show you three things about the company hiring you: whether we have verified the business, whether we have verified its WCB account, and whether it has stated that it carries liability insurance — the same three states we show about you, verified, stated by the company, or not indicated. We show you the state, never the numbers behind it.
We show the absence too. Company verification is not required to hire here. If a company has never applied — or applied and was not approved — those lines read “not verified”, and that is a statement about our records, not an accusation about them. When you accept a job from a company in that state we ask you to confirm you have read it, and we keep a record of that confirmation.
Homeowners hiring for work at their own home are not companies and carry none of these lines. Contact details follow the same rules in this direction as they do in yours: you get the hirer’s phone number once a booking is confirmed, and their email address only if a quote is accepted.
What someone who is not signed in can see
Your name, your photo, your city, your bio and your skills. Your reviews are public — the text, the stars, and the reviewer’s name and photo.
Your directory card, and the quick view that opens from it, also show the working details that make a profile useful to a hirer: your job title, how many jobs you have completed on Noble Labor, your years of experience and which industries they are in, the tools and equipment you list, whether you are currently available, and whether you are open to on-demand work. Full profile pages are for signed-in members only.
Campaign pages, with their photos, video and updates, are open to people who are not signed in.
Endorsements are not shown to people who are not signed in; they see a count. Contact details, street address and postal code are not shown to people who are not signed in.
For a company, or a worker who has switched on subcontract work, the same page also shows whether the business is verified, whether its WCB account was verified, and whether it has stated that it carries liability insurance — shown as verified, stated, or not indicated, never the numbers behind them.
Your privacy settings, and what they do today
Contact details. Every account starts with email and phone set to "contacts only". We want to be straight with you about what that means right now: nothing on the platform currently makes another member a "contact" for this purpose, so on that setting your email and phone are not shown to other members at all. It behaves like private. You can set a field to public if you want to — if you set your phone to public, any signed-in member can see it, with or without a booking. That is your choice, and it is off unless you make it.
Your city. The same settings hold a control called City/Region, which decides who sees the city on your profile. It starts at public, and you can set it to contacts only or private. The other two location controls sit beside it: Street Address, which starts at private, and Postal/ZIP Code — and your postal code is not shown on your profile to anyone regardless of that setting.
Two things happen regardless of these settings, and both are described above: your phone goes to the person you are booked with once a booking confirms, and accepting a quote releases phone and email both ways.
Hiding your profile. You can hide your profile. A hidden profile does not appear in search and is not available publicly. Hiding is not the same as deleting — see Getting a copy, correcting something, or closing your account.
Do we keep score of whether you show up?
Yes, and almost nobody in this industry tells you that, so here it is.
What we record. If you cancel a booking close to its start time, that is recorded on your profile as a late cancellation, with the date. A confirmed no-show is recorded too. If a hirer reports you as a no-show, their written reason is stored, and so is your response.
What it does. We count late cancellations in a rolling 90-day window. At three or more, a "Low Reliability" note is shown alongside your name.
A hirer can also flag you as not on site during a shift, starting fifteen minutes after the scheduled start. That sends you a notification, an email and a text. Clocking in clears it.
A booking cancelled by mutual agreement leaves no mark on either of you. One side proposes it, the other confirms, and the booking closes with no late-cancellation record for anybody. We record which side proposed it, because that handshake is what keeps the door honest.
Whether you were on time is attested by the hirer, not calculated from your clock. A late clock-in is not automatically a mark against you.
Your rights over all of it. This is information used to make a decision that affects you, so:
- we keep the records behind it for at least a year after we use them, so you have a real chance to ask for them;
- you can ask us what your record says, how it has been used, and who it has been shown to;
- you can ask us to correct it, and if we do correct it we will pass the correction to anyone we showed it to in the past year;
- if we decline to correct it, we will note on the record that you asked and we refused, so that anyone who sees it later also sees your objection.
Write to the Privacy Officer below for any of these.
Automatic photo screening
Images and video posted to the Noble Labor feed are screened automatically by Amazon Rekognition to detect content that breaks our rules — explicit or violent imagery. The screening looks at the picture only. It is not face recognition: we do not build face templates and we do not match your photo against your ID. If your content is hidden by the screening you can ask our support team for a person to look at it.
The early access list — for people who are not members yet
Before you can join, our front page asks whether you want an invite. If you fill in that form we collect your first and last name, your email address, your phone number, and which kind of user you are.
We use it to contact you about early access to Noble Labor and to invite you in — by email or by text. When you submit the form, two emails go out through our email provider: one to the Noble Labor team so we know you are waiting, and a welcome email to you.
Being on this list does not create an account. If you would like to be taken off it, email support@noblelabor.com and we will remove you. Please say which email address or phone number to look for. If you don’t ask, your entry is deleted automatically 12 months after you join the list. One exception: if you have asked us to stop contacting you, then at 12 months, or sooner if you ask us to remove you, we clear your name, phone number and everything else, but keep your email address and the record of what you agreed to, when, and your request to stop, so we don’t email you again and can show we respected your request. These deletions cover our list. They do not cover the email our team received when you joined, which stays in our support inbox until we delete it by hand (ask and we will), or our email provider’s record of the emails it sent.
We do not sell this list, and we do not hand it to anyone for their own use. Like everything else on this page, it does pass through the service providers named below, who process it for us and are not free to use it for anything of their own.
Who else touches your information
We share your information with the companies that help us run the platform, and only what each one needs. We do not sell personal information and we do not share it with advertisers or data brokers.
- Company
- Supabase
- What they do
- Our database, sign-in, and account emails such as confirmations and password resets
- Where they process it
- Canada — Montreal ✅ confirmed
- Company
- Amazon Web Services (S3, CloudFront)
- What they do
- Every file you upload: photos, résumés, vetting documents
- Where they process it
- United States — Ohio ✅ confirmed
- Company
- Amazon Rekognition
- What they do
- Automatic screening of feed images and video
- Where they process it
- United States — Ohio ✅ confirmed
- Company
- Vercel
- What they do
- Website hosting, server logs, and page-speed measurement
- Where they process it
- ⚠️ region not confirmed
- Company
- Twilio
- What they do
- Sending text messages, and checking whether a phone number is a real mobile line
- Where they process it
- ⚠️ region not confirmed
- Company
- Resend
- What they do
- Sending email — your address and the content of the message
- Where they process it
- ⚠️ region not confirmed
- Company
- Sentry
- What they do
- Error reports when something breaks. Until October 14, 2026, also "Report a problem" reports, including any screenshot attached
- Where they process it
- ⚠️ region not confirmed
- Company
- Upstash
- What they do
- Rate limiting to stop spam and abuse. Receives your account id, or your IP address if you are not signed in. Where job-site lookup is available, also holds short-lived location suggestions and selection records, including exact site details, coordinates, time zone, rule version and coded account/site bindings, plus coded lookup-attempt counters and the current search-session code. For the address boxes, also holds each suggestion’s address parts and a coded account binding and, once picked, the confirmed address and map point, for three minutes, plus the same kind of coded lookup-attempt counters and the same search-session code. Also holds the centre point, city and province of postal areas already looked up, for 30 days, and a note of postal codes that could not be placed, for a day, with no link to any account
- Where they process it
- ⚠️ region not confirmed
- Company
- Apple (Apple Push Notification service)
- What they do
- Delivering alerts to an iPhone, iPad or Mac. Receives the alert address for your device and a locked message it cannot read
- Where they process it
- ⚠️ region not confirmed
- Company
- Mozilla (Firefox push service)
- What they do
- Delivering alerts to the Firefox browser. Receives the alert address for your device and a locked message it cannot read
- Where they process it
- ⚠️ region not confirmed
- Company
- Microsoft (Windows Notification Service)
- What they do
- Delivering alerts to the Edge browser on Windows. Receives the alert address for your device and a locked message it cannot read
- Where they process it
- ⚠️ region not confirmed
- Company
- Google (Firebase Cloud Messaging)
- What they do
- Delivering alerts to an Android phone or the Chrome browser. Receives the alert address for your device and a locked message it cannot read
- Where they process it
- ⚠️ region not confirmed
- Company
- What they do
- Turning postal codes into map coordinates, as a backup kept until we remove it: only when Mapbox cannot place a postal code or cannot be reached, Google receives that postal code and its country through our server
- Where they process it
- ⚠️ region not confirmed
- Company
- Geoapify
- What they do
- Our previous job-site search provider, kept as a backup until we remove it. When used, it receives address or place-name searches through our server; we do not deliberately send your account identifier. If we switch back to it, we will update this policy first
- Where they process it
- ⚠️ region not confirmed
- Company
- Mapbox
- What they do
- Four things. Job-site search, through our server: the address or place-name search you type, a random search-session code, renewed after about two minutes without a search or after 50 searches, that Mapbox cannot link to your account, and the address you pick, so it can suggest and confirm the job site; these requests come from our server, so Mapbox does not get your IP address from them. Address boxes elsewhere on the site, also through our server: what you type, the same search-session code used for job-site search, the countries searched, and the address or city you pick, so it can suggest and confirm it. Postal codes, through our server: your postal code or a job’s, and its country, nothing else, to turn it into the centre point of that postal area. Map pictures on job, callout, booking, quote and program pages, and placing an older address on such a map. ⚠️ For the map pictures your browser contacts Mapbox directly, so Mapbox receives your IP address and browser, and the map point or the address text of the place being shown, without it passing through us. The map data includes © OpenStreetMap contributors. Mapbox handles this information under its Product Terms, its Data Processing Addendum and its own Privacy Policy, which also let Mapbox use it in de-identified, aggregated form
- Where they process it
- United States (US company) — ⚠️ region not confirmed
- Company
- YouTube (privacy-enhanced mode)
- What they do
- Only if a page you open has a video embedded in it
- Where they process it
- —
- Company
- Stripe
- What they do
- Payments — not in use today. See the paragraph below
- Where they process it
- ⚠️ region not confirmed
| Company | What they do | Where they process it |
|---|---|---|
| Supabase | Our database, sign-in, and account emails such as confirmations and password resets | Canada — Montreal ✅ confirmed |
| Amazon Web Services (S3, CloudFront) | Every file you upload: photos, résumés, vetting documents | United States — Ohio ✅ confirmed |
| Amazon Rekognition | Automatic screening of feed images and video | United States — Ohio ✅ confirmed |
| Vercel | Website hosting, server logs, and page-speed measurement | ⚠️ region not confirmed |
| Twilio | Sending text messages, and checking whether a phone number is a real mobile line | ⚠️ region not confirmed |
| Resend | Sending email — your address and the content of the message | ⚠️ region not confirmed |
| Sentry | Error reports when something breaks. Until October 14, 2026, also "Report a problem" reports, including any screenshot attached | ⚠️ region not confirmed |
| Upstash | Rate limiting to stop spam and abuse. Receives your account id, or your IP address if you are not signed in. Where job-site lookup is available, also holds short-lived location suggestions and selection records, including exact site details, coordinates, time zone, rule version and coded account/site bindings, plus coded lookup-attempt counters and the current search-session code. For the address boxes, also holds each suggestion’s address parts and a coded account binding and, once picked, the confirmed address and map point, for three minutes, plus the same kind of coded lookup-attempt counters and the same search-session code. Also holds the centre point, city and province of postal areas already looked up, for 30 days, and a note of postal codes that could not be placed, for a day, with no link to any account | ⚠️ region not confirmed |
| Apple (Apple Push Notification service) | Delivering alerts to an iPhone, iPad or Mac. Receives the alert address for your device and a locked message it cannot read | ⚠️ region not confirmed |
| Mozilla (Firefox push service) | Delivering alerts to the Firefox browser. Receives the alert address for your device and a locked message it cannot read | ⚠️ region not confirmed |
| Microsoft (Windows Notification Service) | Delivering alerts to the Edge browser on Windows. Receives the alert address for your device and a locked message it cannot read | ⚠️ region not confirmed |
| Google (Firebase Cloud Messaging) | Delivering alerts to an Android phone or the Chrome browser. Receives the alert address for your device and a locked message it cannot read | ⚠️ region not confirmed |
| Turning postal codes into map coordinates, as a backup kept until we remove it: only when Mapbox cannot place a postal code or cannot be reached, Google receives that postal code and its country through our server | ⚠️ region not confirmed | |
| Geoapify | Our previous job-site search provider, kept as a backup until we remove it. When used, it receives address or place-name searches through our server; we do not deliberately send your account identifier. If we switch back to it, we will update this policy first | ⚠️ region not confirmed |
| Mapbox | Four things. Job-site search, through our server: the address or place-name search you type, a random search-session code, renewed after about two minutes without a search or after 50 searches, that Mapbox cannot link to your account, and the address you pick, so it can suggest and confirm the job site; these requests come from our server, so Mapbox does not get your IP address from them. Address boxes elsewhere on the site, also through our server: what you type, the same search-session code used for job-site search, the countries searched, and the address or city you pick, so it can suggest and confirm it. Postal codes, through our server: your postal code or a job’s, and its country, nothing else, to turn it into the centre point of that postal area. Map pictures on job, callout, booking, quote and program pages, and placing an older address on such a map. ⚠️ For the map pictures your browser contacts Mapbox directly, so Mapbox receives your IP address and browser, and the map point or the address text of the place being shown, without it passing through us. The map data includes © OpenStreetMap contributors. Mapbox handles this information under its Product Terms, its Data Processing Addendum and its own Privacy Policy, which also let Mapbox use it in de-identified, aggregated form | United States (US company) — ⚠️ region not confirmed |
| YouTube (privacy-enhanced mode) | Only if a page you open has a video embedded in it | — |
| Stripe | Payments — not in use today. See the paragraph below | ⚠️ region not confirmed |
⚠️ "Region not confirmed" means exactly that. We have not yet obtained written confirmation of where these companies process our data, and we would rather tell you that than guess.
Payments and Stripe. Noble Labor does not process payments today. No money has moved through the platform and no Noble Labor account is connected to Stripe. When we do begin processing payments, we intend to use Stripe. At that point Stripe would receive what it needs to take a payment — your email address and your Noble Labor account identifier — and card details would be entered on Stripe’s own pages rather than ours, so we would not hold your card number. We will update this policy to describe how it works before the first payment is taken.
What is not on this list. No Google Analytics, no Meta Pixel, no advertising network, no session-replay recorder, no keystroke or cursor logging, no third-party background-check company, no artificial-intelligence or large-language-model service, and no social sign-in.
We may also disclose information when the law requires it — a court order, a subpoena, a warrant or a valid regulatory request — and if Noble Labor is ever sold or merged, your information would transfer with the business.
We stay responsible for your information when we hand it to these companies. Where we retain another organization to do work involving personal information, we require an agreement obliging them to protect it to the standard we owe you.
Does your information leave Canada?
Yes, some of it, and you should know what that means.
Our database is in Canada (Montreal). Your uploaded files are in the United States (Ohio) — that includes profile photos, résumés, and any government ID or criminal record check you submit for vetting. Several of the service providers above are US companies.
Information stored in the United States is subject to United States law, which is not the same as Canadian privacy law, and it may be accessible to United States courts, law enforcement and national security authorities under that country’s laws. That is a real consequence of using a US-hosted service, and it applies to us as it does to most Canadian technology companies.
No law requires a Canadian company to keep personal information inside Canada. What the law requires is that we tell you, and that we protect it by contract. We are doing both.
Noble Labor is offered in Canada. It is not directed to people in the European Economic Area or the United Kingdom.
Texts and emails
We send text messages in three situations: a callout, when a hirer is offering you a shift; a one-time code when you verify your phone number; and a clock-in alert to a hirer when a worker starts a shift. A callout text carries your first name, the hirer’s name, the job title, the rate and the date, plus a link to open it. It does not carry the job site’s street address.
We do not send marketing texts. If that ever changes it will be a separate opt-in you tick yourself — not bundled into the Terms, not pre-ticked — and you will be able to refuse it and still use the platform.
To stop texts, reply STOP to any message. Every text identifies Noble Labor and carries that instruction. STOP is handled by our messaging carrier, which stops the texts. On the early access list, if you ask us to stop contacting you, we record that so our own team can see you have opted out.
Emails. Booking confirmations, invoices and account notices are part of the service and are sent because you have a booking with someone — you cannot switch off a notice you need in order to get paid. Anything optional you can switch off, and if you tell us to stop sending you a kind of message, we will.
Alerts on your phone
If you add Noble Labor to your phone’s home screen, we can send an alert straight to your lock screen. That is the fastest way to hear about a callout — and on an on-demand job the first worker to accept gets it, so seconds genuinely matter.
We only turn this on if you ask for it. We show you our own explanation first, with a Yes, alert me and a Not now. Only Yes, alert me goes anywhere near your phone’s own permission prompt. Tapping Not now touches nothing on your phone and creates no alert address — we record only that you closed the message, so that we do not keep showing it to you.
What we keep. When you say yes, your browser creates an alert address that points at that one device, plus two keys we use to lock the message. We store those three things, linked to your account, along with when you switched alerts on and when you last opened Noble Labor on that device. Nothing else about the device — not your phone model, not a device name, not your IP address.
Who carries it, and what they can read. The alert travels through the company that makes your browser or phone: Apple for an iPhone or iPad, Google for an Android phone or Chrome, Mozilla for Firefox, or Microsoft for Edge on Windows. We cannot hand it to your phone ourselves — that is how alerts work for every app on your phone. We lock the message before it leaves us, and neither Apple nor Google can read it. What they do see is that a Noble Labor alert went to your device, and when. Both are United States companies, so what we say above about the United States applies to them too.
What the alert says. Today the only alert we send this way is a callout, and it deliberately says as little as it can: that work has been offered to you, and nothing about who offered it, what it pays, or where it is. You open Noble Labor to see that. It appears on your lock screen, which means anyone holding your phone can read it. If you would rather it did not, your phone’s own settings let you hide the contents of alerts until the phone is unlocked.
Turning it off. The switch is in your Noble Labor account, under Alerts on your phone, and you use it on the phone you want to silence — open Noble Labor from its home-screen icon on that phone and switch it off there. That stops the alerts and deletes the address we are holding. Your phone’s own Settings will also stop them, but only the switch in your account deletes the address; if you use Settings instead, we delete our copy the next time we find it no longer works. If you no longer have the phone, write to us at the address at the end of this policy and we will delete it for you.
When we delete the address. When you switch alerts off in your account. When you sign out on that device. When your phone, Apple or Google tells us the address no longer works. And with the rest of your account when you close it. We are also building a sweep that will delete an address you have not used for six months.
How long we keep things
The honest answer is that most of it is kept while your account exists, and some of it outlives the account. Here is the real picture.
- What
- Your profile and account
- How long
- While your account is open
- What
- Bookings, invoices and payment records
- How long
- Kept as business records, including after a job ends and after an account is closed
- What
- Messages and notifications
- How long
- Kept — there is no automatic deletion today
- What
- The alert address for a phone or computer you switched alerts on for
- How long
- Until you switch alerts off or it stops working. Deleted with your account. We are building the six-month sweep
- What
- Clock-in and clock-out location records
- How long
- We keep these records for 12 months after you clock in or out, and then delete the coordinates. The record that you clocked in and out stays.
- What
- Reliability records, vetting results, and anything else used to make a decision about you
- How long
- At least a year after we use it, so you have a real chance to ask for it
- What
- Records of who viewed a profile
- How long
- Kept — no deletion schedule is set today
- What
- Records of who viewed a job posting
- How long
- Kept — no deletion schedule is set today
- What
- Sign-in records (IP address, browser)
- How long
- For the life of that session record, at our sign-in provider
- What
- The one-time codes we text you to verify your phone number, and the number we sent each one to
- How long
- Our copy is deleted as soon as your number is verified (the number on your profile is not affected). Any other code, used or not, expires after 10 minutes and is deleted within about an hour after that, along with the number it was sent to. This does not cover the text message itself as kept by our text-message provider, or backups.
- What
- Anti-spam and rate-limit records outside job-site lookup
- How long
- 1 to 10 minutes
- What
- Temporary job-site suggestions, selection records and coded lookup-attempt records, where lookup is available
- How long
- Location suggestions expire after five minutes, the search-session code after about two minutes without a search, and selected-site verification records expire after one hour, in our temporary store. Coded lookup-attempt timestamps can remain for almost 48 hours. These periods do not describe provider logs or backups. Saved jobs and bookings follow their existing retention rules.
- What
- Temporary address-box suggestions, confirmed picks and coded lookup-attempt records
- How long
- Each suggestion, and the confirmed address once you pick it, expires after three minutes in our temporary store; the search-session code after about two minutes without a search. Coded lookup-attempt timestamps can remain for almost 48 hours. These periods do not describe provider logs or backups. What a form saves follows that form’s own retention.
- What
- Postal-area centre points we have already looked up (point, city and province, with no link to any account)
- How long
- 30 days in our temporary store; a note that a postal code could not be placed, one day
- What
- "Build With Us" messages (bug reports and ideas)
- How long
- Kept with your account, and deleted when the account is permanently deleted. The emailed copy stays in our support inbox until we delete it by hand. Older "Report a problem" reports and any screenshot: on our error-monitoring provider’s standard schedule (we are confirming the exact period), or sooner if you ask
- What
- Files you uploaded — photos, résumés, vetting documents
- How long
- Deleted when the account is permanently deleted — at the end of the 30 days, not the moment you close it. The files go after the records they belong to, and we check each one afterwards to prove it is gone
- What
- Early access list entries
- How long
- Deleted automatically 12 months after you join the list, or sooner if you ask us to remove you. If you have asked us to stop contacting you, we do not delete it completely: at 12 months, or when you ask us to remove you, we clear your name, phone number and everything else, and keep your email address, the record of what you agreed to and when, and your request to stop, so we don’t email you again and can show we respected your request. No end date is set for that record yet
- What
- Support requests you send while signed out (your email address, your message, and the help topic, page and search you sent it from)
- How long
- Deleted automatically 12 months after you send them
- What
- Internal diagnostic logs
- How long
- Kept. Some keep an account identifier after the account itself is gone
- What
- The record we keep when an account was suspended, removed for cause, or the subject of a report escalated to a lawyer
- How long
- Kept after the account is gone. We review these records after two years — that review is a decision a person makes, not something that happens on a timer
- What
- The anonymous monthly count of account closures
- How long
- Kept. There is nothing in it that could point back to a person
- What
- The record that a file was proven deleted
- How long
- Kept as the proof the erasure happened. Once we have the proof, the filename is replaced by a one-way code
| What | How long |
|---|---|
| Your profile and account | While your account is open |
| Bookings, invoices and payment records | Kept as business records, including after a job ends and after an account is closed |
| Messages and notifications | Kept — there is no automatic deletion today |
| The alert address for a phone or computer you switched alerts on for | Until you switch alerts off or it stops working. Deleted with your account. We are building the six-month sweep |
| Clock-in and clock-out location records | We keep these records for 12 months after you clock in or out, and then delete the coordinates. The record that you clocked in and out stays. |
| Reliability records, vetting results, and anything else used to make a decision about you | At least a year after we use it, so you have a real chance to ask for it |
| Records of who viewed a profile | Kept — no deletion schedule is set today |
| Records of who viewed a job posting | Kept — no deletion schedule is set today |
| Sign-in records (IP address, browser) | For the life of that session record, at our sign-in provider |
| The one-time codes we text you to verify your phone number, and the number we sent each one to | Our copy is deleted as soon as your number is verified (the number on your profile is not affected). Any other code, used or not, expires after 10 minutes and is deleted within about an hour after that, along with the number it was sent to. This does not cover the text message itself as kept by our text-message provider, or backups. |
| Anti-spam and rate-limit records outside job-site lookup | 1 to 10 minutes |
| Temporary job-site suggestions, selection records and coded lookup-attempt records, where lookup is available | Location suggestions expire after five minutes, the search-session code after about two minutes without a search, and selected-site verification records expire after one hour, in our temporary store. Coded lookup-attempt timestamps can remain for almost 48 hours. These periods do not describe provider logs or backups. Saved jobs and bookings follow their existing retention rules. |
| Temporary address-box suggestions, confirmed picks and coded lookup-attempt records | Each suggestion, and the confirmed address once you pick it, expires after three minutes in our temporary store; the search-session code after about two minutes without a search. Coded lookup-attempt timestamps can remain for almost 48 hours. These periods do not describe provider logs or backups. What a form saves follows that form’s own retention. |
| Postal-area centre points we have already looked up (point, city and province, with no link to any account) | 30 days in our temporary store; a note that a postal code could not be placed, one day |
| "Build With Us" messages (bug reports and ideas) | Kept with your account, and deleted when the account is permanently deleted. The emailed copy stays in our support inbox until we delete it by hand. Older "Report a problem" reports and any screenshot: on our error-monitoring provider’s standard schedule (we are confirming the exact period), or sooner if you ask |
| Files you uploaded — photos, résumés, vetting documents | Deleted when the account is permanently deleted — at the end of the 30 days, not the moment you close it. The files go after the records they belong to, and we check each one afterwards to prove it is gone |
| Early access list entries | Deleted automatically 12 months after you join the list, or sooner if you ask us to remove you. If you have asked us to stop contacting you, we do not delete it completely: at 12 months, or when you ask us to remove you, we clear your name, phone number and everything else, and keep your email address, the record of what you agreed to and when, and your request to stop, so we don’t email you again and can show we respected your request. No end date is set for that record yet |
| Support requests you send while signed out (your email address, your message, and the help topic, page and search you sent it from) | Deleted automatically 12 months after you send them |
| Internal diagnostic logs | Kept. Some keep an account identifier after the account itself is gone |
| The record we keep when an account was suspended, removed for cause, or the subject of a report escalated to a lawyer | Kept after the account is gone. We review these records after two years — that review is a decision a person makes, not something that happens on a timer |
| The anonymous monthly count of account closures | Kept. There is nothing in it that could point back to a person |
| The record that a file was proven deleted | Kept as the proof the erasure happened. Once we have the proof, the filename is replaced by a one-way code |
Job-site lookup records. The expiry periods above apply to records in our temporary store. Provider logs and backups have separate schedules; these expiry periods do not promise erasure from them. Temporary lookup records expire on their own timers rather than being erased immediately when an account is closed; they may already have expired when you request a copy or correction. Saved jobs and bookings continue to follow their existing retention and account-deletion rules.
The law requires us to destroy or anonymise personal information once the purpose it was collected for is finished and there is no legal or business reason to keep it. Where this table says something is simply "kept," that is a description of the platform as it stands today, not a claim that it is where we should end up.
Getting a copy, correcting something, or closing your account
Write to the Privacy Officer (below). We may ask you to confirm your identity first, so that we do not hand your information to someone pretending to be you.
What you are entitled to ask for:
- the personal information we hold about you;
- how it has been used and is being used;
- who we have disclosed it to.
Our deadline is 30 days. If we need longer — because the request is large, or we have to consult someone — we may take up to 30 more days, and we will tell you why, when you will get an answer, and that you can complain to the Commissioner about the delay. If we refuse any part of a request we will tell you the reason, the part of the law we are relying on, who to speak to about it, and that you can ask the Commissioner to review our decision.
There is no download button today. A request for a copy goes to a person, who assembles it. That is slower than a button; it is not a smaller right, and the 30-day deadline is the same.
If producing your information takes real work we may charge a minimal fee — and if we do, you get a written estimate first and can withdraw the request.
Corrections. If something we hold about you is wrong or incomplete, tell us and we will correct it as soon as we reasonably can, and pass the correction to anyone we disclosed it to in the past year. If we decline, we will note on the record that a correction was asked for and refused.
Closing your account. You can close your account yourself, from your Account page. We make sure it's really you before we close it — a full sign-in, not just a tap on an emailed link — so nobody who got hold of a link to your account can close it for you. The account closes right away and is permanently deleted 30 days later (later if the deletion is on hold, for example while a report about the account is with a lawyer); if you change your mind inside those 30 days, write to the Privacy Officer. Some things do not disappear when your account does, and you should know which:
- messages you sent stay in the other person’s inbox;
- invoices and booking records are kept, because they are the record of a transaction between you and another person, who has their own claim on that record;
- reviews and activity other people rely on may remain;
- files you uploaded — photos, résumés, vetting documents — are deleted when your account is permanently deleted — normally at the end of the 30 days, later if the deletion is on hold or a file has to be retried — not the moment you close it. They go after the records they belong to, and we check each one afterwards to prove it is gone;
- the emailed copy of a "Build With Us" message you sent stays in our support inbox. Closing your account does not delete it by itself; ask and we will delete it too;
- some internal diagnostic logs keep an account identifier.
- If we have suspended you, removed your account for cause, or escalated a report about you to a lawyer, we keep a small record of that after your account is gone — your account ID, your email, when the account was made and deleted, whether we removed it for cause, and counts of moderator actions against you (warnings included), no-show reports made against you, and your late cancellations. This record does not hold your name, messages or report details (your email address may itself include your name). It is there so that we have a record if someone we suspended, removed or escalated to a lawyer comes back. We review these records after two years. If none of that ever happened to you, no such record is kept.
- Our moderators' log about your account is kept with your account ID removed. It records each time a moderator opened a report about you and what they decided — no action, a warning, a suspension, or passing it to a lawyer — and each time our staff made a password reset link for you. A moderator's notes in it may still mention you, and there is no set date for deleting it yet.
- Reports you made about another member, including a no-show report, are kept with your account removed from them, so our team can finish dealing with them. What you wrote, and any notes our moderators added, stay with the report and may still identify you. There is no set date for deleting them yet. A report is deleted if the member it is about deletes their account.
- We also keep an anonymous count of how many people closed their account each month — whether they were here to work or to hire, the reason they picked from a list, and whether they said they would come back — with nothing in it that could point back to you.
- We keep a record that each of your files was proven deleted, with the filename replaced by a one-way code once we have the proof.
Withdrawing consent. You can withdraw consent to anything that is not required to run the service, at any time, by telling us, and we will tell you what stops working if you do. Some things you cannot switch off and still use the platform — we cannot run a booking without your name, or send you a callout without your phone number. Withdrawing consent does not require us to delete records we have a legal or business reason to keep.
Security, and what happens if there is a breach
We protect your information with administrative controls (who on our team can see what, and why), physical controls (our providers’ facilities), and technical controls (encryption in transit, access controls on the tables that hold personal information, and gating that limits what other members and our own systems can read).
No system is perfectly secure, and we are not going to claim otherwise.
If a breach happens, we keep a written record of it, we assess whether it creates a real risk of significant harm to anyone, and where it does we notify the people affected and the Office of the Privacy Commissioner of Canada as soon as we can — with enough detail for you to understand what it means for you and what you can do about it.
What if someone else entered your details?
A property manager using Noble Labor can enter a resident’s name, phone number and email so a job can be coordinated at that address. If you are that resident, you are not a Noble Labor member and you did not sign up for anything.
The person who entered your details is responsible for having your permission to do so. We hold that information to run the job it relates to. If your details are on our platform and you want them removed, write to the Privacy Officer below and we will remove them.
Is Noble Labor for people under 18?
No. Noble Labor is for people 18 and over. We do not ask for your date of birth when you register, so we are not in a position to verify your age — but if we learn that someone under 18 has an account, we will remove their information.
Who to contact — our Privacy Officer
Noble Labor has designated a Privacy Officer responsible for our compliance with British Columbia’s Personal Information Protection Act.
- Position
- Privacy Officer, Noble Labor
- Name
- Cody Fleming
Which laws apply
Noble Labor is operated from British Columbia, Canada. We handle personal information in accordance with:
- British Columbia’s Personal Information Protection Act (PIPA) — our primary law;
- the federal Personal Information Protection and Electronic Documents Act (PIPEDA), which applies to personal information that crosses provincial or national borders — which ours does, because our files and several of our providers are in the United States;
- Canada’s anti-spam law (CASL) for the emails and texts we send.
How to complain
Start with us. Write to the Privacy Officer above. We will acknowledge your complaint, look into it, and tell you what we found and what we are doing about it.
If you are not satisfied, complain to the regulator. You do not need our permission and you do not need to come to us first:
- Office of the Information and Privacy Commissioner for British Columbia — oipc.bc.ca · info@oipc.bc.ca
- Office of the Privacy Commissioner of Canada, for cross-border matters — priv.gc.ca
Changes to this policy
We will update this policy as the platform changes. When we do, we will change the date at the top. Changes that affect how we use your information will be brought to your attention in the app rather than left for you to find.
This version is an interim policy written by the Noble Labor team. It is being reviewed by a lawyer and will be replaced by the reviewed version.
Still need help?
Reach out through the Help page support form and our team can assist further.
Contact support