Crew Cab Studios

Privacy Policy

In effect from 6 October 2026 · Version 2026-10-06

Each app:ChangedMatchedDoseCrews OutWeather X

This policy explains what our apps collect, why, who else handles it, how long we keep it, and how to see, fix or delete it. One part applies to every app we run, and each app has its own section saying what that app collects and how it uses our providers. An app we have not released yet collects nothing until this policy has a section for it.

We do not sell personal information, we do not use it for advertising, and we never have.

Who we are

Crew Cab Ventures, of Edmonton, Alberta, Canada, runs our apps. Our website is crewcabstudios.com. In this policy “we” and “us” mean Crew Cab Ventures.

Our privacy officer is Darren Wood. Write to him at hello@crewcabstudios.com about anything in this policy.

Two kinds of information

Our apps hold two kinds of information, and we handle them differently.

Yours. If you run or work for a business that uses our apps, we hold your account and your business's records. You deal with us directly, and this policy governs that.

Your customers' and other people's. When you use our apps, you give us information about other people, such as the customers you send a change order to. We hold that for you, as your service provider, and use it only to run the app for you. You decide what to collect and how long to keep it. If one of your customers asks us about their information, we send them to you and help you answer.

What every app collects

  • Your account: your name, email address, your role on your team, when you last signed in, and your settings.
  • Signing in: an emailed code or link, or an account you already have, such as Google or Jobber. From that account we get your name, email address and picture, or less where an app's section says so. We keep a session record so you stay signed in.
  • Your business's records: what you and your team put into the app, and what it brings in from services you connect. Each app's section says what that is.
  • Agreeing to our terms: when you agree to our Terms of Service and this policy, for example by continuing past the line under a sign-in button, we record who agreed, for which company, to which version, when, and from which IP address and browser.
  • Billing: your plan, and the IDs our payment provider gives your subscription. The payment provider holds your card details; we never see your full card number.
  • Help: what you send when you ask for help or give feedback.
  • Technical data: server logs, IP addresses, browser and device type, and error reports, so the apps work and we can stop abuse. Usage counters for our limits hold a one-way hash, not your email or address.

Why we use it

We use information to run the apps you signed up for, to sign you in and keep your account secure, to send the messages you ask the app to send, to bill you, to answer you, to find and fix problems, to improve the apps using statistics that do not identify anyone, and to meet our legal duties. We rely on your consent, given when you sign up and use the apps, and on what is needed to provide the service.

We do not use your information, or your customers', for marketing, and we do not let our providers use it for theirs.

Who else handles it

We use service providers to run our apps. Each does a set job for us. They may use the information only to provide their service to us, and must protect it.

These are the kinds of providers we use, what each is for, and what it handles. Not every app uses every kind.

  • Hosting and infrastructure: runs our websites, apps, servers and background jobs, and delivers pages to your browser. Handles everything an app stores or shows, and the technical data in each request, such as your IP address and browser.
  • Databases: store your account and your business's records. Handle everything an app stores.
  • File storage: keeps photos, videos, logos, documents and exports. Handles the files you and your team add, and files an app makes, such as a signed PDF or an export.
  • Email: sends sign-in codes, invites, notices and the messages you ask an app to send, and receives email sent to an app's addresses. Handles names, email addresses, and each message with its attachments.
  • Text messages: sends the texts you ask an app to send, and brings back replies and delivery reports. Handles phone numbers, names and each message.
  • Payments: takes subscription payments and works out sales tax, if you are on a paid plan. Handles your plan, your billing contact and address, and your card details, which we never see.
  • Error reports and product analytics: tell us when something breaks and how the apps are used, so we can fix and improve them. Handle what is described under Error reports and usage analytics below, and never what you type into a form.
  • Site analytics and page speed: count page views and measure how fast pages load, without cookies. Handle the page's address with private parts removed, the page you came from, your browser, device type and country. They keep nothing that identifies you.
  • AI processing: drafts, reads, transcribes, matches and answers, for the AI features each app's section describes. Handles only what a feature needs, only when someone uses it, such as a note, a photo, an email, the sound of a video or a question.
  • Bank connections: let an owner connect a bank or card account to an app that reads card charges. Handle the accounts the owner chooses and their posted charges. Your bank password stays with your bank and the provider; we never see it.
  • Sign-in: lets you sign in with an account you already have, such as Google. Handles your name, email address and picture from that account, or less where an app's section says so.
  • Data lookups: answer a question for an app, such as the weather at a place on a date. They receive only the question, such as map coordinates and dates, and nothing that names you or your customers.

Services you connect. Some apps work with services you choose and connect, such as Jobber, your card platform, a texting service such as Quo, or your own AI assistant. Those are yours, not our providers. Each works on your authorization and under its own terms and privacy policy. An app reads from and writes to them only what its section describes, and you can disconnect them at any time.

We may also disclose information if the law requires it, and we will tell you unless we are not allowed to.

The list of providers

Our Service providers page names each company we use today, for each app, with what it does, what it handles and where it is. It shows the date it last changed. It is part of how we keep this policy current, and each app links to it beside this policy.

We update the list when we add or replace a provider within the kinds above. That does not change this policy, and we do not send a notice for it. Before we add a new kind of provider, collect a new kind of information, or use information for a new purpose, we change this policy and tell you first, as described under Changes to this policy.

Where it is stored

Most of our providers store and process information in the United States, so your information leaves Canada and may be reachable by courts and authorities there. The Service providers page says where each one is. We choose providers that protect it to a standard comparable to Canadian law.

AI features

Some apps send information to an AI provider to draft, read, transcribe or answer. Each app's section says which feature sends what, and the Service providers page names the provider each one uses. We send only what the feature needs, only when someone uses it, and we choose providers whose business terms say they do not train their models on it. What an AI feature produces is a suggestion that a person reviews.

If you connect your own AI assistant (such as Claude, ChatGPT or Muse) to one of our apps, the assistant reads what you ask it to from the app. That assistant is yours: its provider's policy, not ours, covers what it does with what it reads.

Error reports and usage analytics

When they are switched on, our websites and apps send error reports to our error reporting provider, record how pages are used with our product analytics provider, and count page views with our site analytics provider, so we can find bugs and make things easier to use.

  • An error report says what went wrong, on which page, in which browser and device. Before it is sent we remove anything you typed into a form, your cookies, and the query part of the web address.
  • Product analytics records the pages you visit and what you tap, and can record a replay of a visit. Anything typed into a form is hidden and never recorded. In the signed-in parts of our apps the replay also hides the text on screen, except labels and buttons we checked hold no customer information.
  • Site analytics counts page views and measures page speed. It sets no cookie, gets no ID for you, and keeps nothing that identifies you. Private parts of a page's address, such as a sign-off link, are removed before it is sent.
  • When you are signed in, error reports and product analytics know you only by an internal number, never your name or email. On our websites a visit is known only by a random ID stored in your browser.
  • If your browser sends a Do Not Track or Global Privacy Control signal, we do not load product analytics.

Cookies and storage in your browser

  • Needed to work: a cookie that keeps you signed in, and short-lived cookies that protect sign-in with services such as Jobber and Google. The apps do not work without them.
  • Analytics: when product analytics is switched on, a random ID in your browser, as described above. Site analytics sets no cookie.
  • Your preferences: some apps remember things on your device, such as a dismissed tip or where to save photos. That stays in your browser and is never sent to us.

We do not use advertising cookies or trackers.

How long we keep it

We keep your records while your account is open, because that is what they are for: a record from two years ago can matter today. After you close your account you have 60 days to ask for an export. After that we delete your account and its records within 30 days, and from backups within a further 90 days. Logs are kept for up to 12 months. We keep what the law requires longer, such as billing records for tax, and what we need for a legal claim. An app's section says where it differs.

Your rights

You can ask us to show you the personal information we hold about you, to correct it, or to delete it, and you can withdraw your consent (which may mean we can no longer provide an app). Write to hello@crewcabstudios.com. We will answer within 30 days, and we may need to check who you are first.

In Canada, the Personal Information Protection and Electronic Documents Act and Alberta's Personal Information Protection Act give you these rights. If you are not satisfied with our answer, you can complain to the Office of the Information and Privacy Commissioner of Alberta or the Office of the Privacy Commissioner of Canada.

In the United States, some state laws give residents similar rights, such as the right to know, correct and delete. We honour them where they apply. We do not sell or share personal information for advertising, and we will not treat you differently for asking.

If you are one of our customers' customers, ask the business that sent you the link first, since it is their record. If you write to us, we will pass your request to them and help them answer.

Security

Connections use TLS. Keys and tokens for services you connect are encrypted before they are stored. Access to production systems is limited to the people who need it. No service can promise perfect security. If a breach creates a real risk of significant harm to you, we will tell you and the regulator as the law requires.

Children

Our apps are for businesses. They are not meant for children, and we do not knowingly collect information about children.

Changes to this policy

Each version of this policy has a version number and an effective date at the top of the page. When a change matters, we tell account holders at least 14 days before it takes effect, by email and in the app, and our apps show a notice the next time you open them. A change matters when it adds a new kind of provider, collects a new kind of information, uses information for a new purpose, or reduces your rights.

Other changes take effect when we post them: wording made clearer, a new feature that works within this policy, or a provider added or replaced within the kinds above. The Service providers page shows the providers in use and the date that list last changed.

Contact and complaints

Darren Wood, privacy officer, Crew Cab Ventures, Edmonton, Alberta, Canada.

Email: hello@crewcabstudios.com

Changed

Changed (itschanged.app) is our app for change orders. A contractor writes a change order, sends it to their customer, and the customer signs off from a link on their phone. The part of this policy for every app applies to Changed too; this section adds what is particular to it.

What Changed collects

From the contractor and their team:

  • Company details: the company name, logo, phone and email for customers, the terms they add to every change order, and an optional payment link.
  • Jobs and customers: jobs, addresses, and customers' names, email addresses and phone numbers, typed in or brought in from Jobber.
  • Change orders: the reason, the lines and prices, photos, videos the team records, the schedule, and the timeline of what happened and who did it.
  • Forwarded email: emails and attachments a contractor or supplier sends to the company's Changed address.
  • Connections: encrypted keys and tokens for Jobber and Quo, and records of the AI assistants the team has connected (we keep only a one-way hash of each assistant's tokens).

From Jobber, when the contractor connects it: the account's name and phone, jobs with their properties and line items, clients' names, emails and phone numbers, products and services, and team members' names, emails and roles.

From Quo, when the contractor connects it: delivery reports for the texts Changed sent, and replies to them.

People who sign off in Changed

If a contractor sent you a change order through Changed, this part is for you. You do not have an account with us, and you never agree to our terms; the change order is between you and the contractor.

What we record when you open and sign off. When you first open the link; whether you ticked the consent box, when, and which version of the disclosure you saw; your name as typed; your signature, drawn or typed; when you signed off; your IP address and browser; and a fingerprint (a hash) of exactly what the page showed you. If you ask for changes, we keep your note. These are recorded so the sign-off can be proven later, which is the point of the product.

Where it goes. Into the signed PDF and its certificate page, emailed to you and to anyone else who signed off with an email address, and available from your link. The contractor's team sees it in Changed, and when the contractor uses Jobber, a link to the PDF goes on the job. Anyone with the PDF's check page address can see the change order's details with emails and phone numbers partly hidden.

Who controls it. The contractor. We hold it for them as their service provider and use it only to run Changed for them. We never use it to market to you, and we never sell it.

What we do not record. Your page and its PDF are never recorded by product analytics or session replay, and your signature is never sent to an error report. Site analytics may count that a sign-off page was viewed, without its private link, a cookie or anything that identifies you.

How long. As long as the contractor's account is open, then as the part for every app describes. Keep the PDF you were emailed: your link stops working once the records are deleted.

Your requests. To see, correct or delete your information, ask the contractor; their contact details are at the bottom of your page. If you write to us at hello@crewcabstudios.com, we will pass your request to them and help them answer.

Service providers for Changed

Changed uses the kinds of providers in the part for every app, including file storage for photos, videos, logos and signed PDFs, email to send sign-in codes, invites, change orders and signed copies and to receive email sent to company addresses, and AI processing for the features below. The Service providers page names each one Changed uses and where it is.

Changed also works with services the contractor connects: Jobber, as described above, and Quo, to send texts from the contractor's own number. Texts that go from a tech's own phone are sent by that phone, not by us.

AI in Changed

  • Autofill sends the tech's note, the photos, the job's title, address and lines, the last few change orders on the job, and the company's products and services to our AI provider, to draft the change order. It runs only when someone taps Autofill or records a video note.
  • Video notes send the sound, in short pieces, to a speech-to-text provider to write down what was said. The sound is not kept, and the words are not logged.
  • Forwarded emails and their attachments are read by our AI provider to draft a change order.
  • Ask Changed sends the question and the conversation to our AI provider to answer from our help articles. Changed does not keep the conversation.

Nothing the AI drafts goes to a customer until someone on the team sends it.

Photos and videos

Photos, videos and logos are stored at unlisted web addresses so the customer's page, emails and PDF can show them. Anyone with one of those addresses can open it. A video uploaded and then thrown away before its change order was saved may stay in storage until we clear it out.

Analytics in Changed

The customer's page and its PDF are never recorded by product analytics or session replay, and the private link to that page is removed from every error report and analytics event before it is sent. Signatures, and what customers see or type, are never recorded anywhere outside Changed's own database.

How long, in Changed

An owner can delete the company in Settings. It closes at once: the team loses access, Jobber, Quo and connected assistants are disconnected, and customers' links stop working. Nothing in Jobber is deleted. We keep the company's records for 60 days so you can ask for an export, then erase them, and the part for every app describes backups and what the law makes us keep.

Matched

Matched (itsmatched.com) links a company's Jobber account to its company card platform. It suggests a Jobber job for each card charge, and when a person confirms, it writes the expense and its receipt to that job. The part of this policy for every app applies to Matched too; this section adds what is particular to it.

What Matched collects

  • From your card platform (Float, Ramp or Brex), when you connect it: each charge's merchant, amount, date, cardholder, card, memo and category, the fields your crew fills in, your custom fields, and receipts. From Float, Matched also reads approved bills: the payee, amount, invoice number, memo, lines, payments and attachments. We keep the platform's key or token encrypted. Receipt images stay with the card platform; Matched keeps only the receipt's ID and fetches a short-lived link when someone opens it or when the expense goes to Jobber.
  • From your bank or American Express, if an owner connects one: the names and last digits of the cards they choose, and each posted charge on those cards (date, merchant, amount, currency, category, and the card member's name when the bank gives it). The owner signs in to the bank in our bank connection provider's own window, and Matched never sees the bank password. We keep the connection's access encrypted.
  • Statements you upload: each line's date, description and amount, and the file itself, stored encrypted, with card numbers cut to the last four digits.
  • From Jobber: the account's name; jobs with their number, title, status, client and property address; clients' names; team members' names, email addresses and whether each is an owner or admin; clock-ins; and expenses, to check charges against what is already in Jobber. Jobber also tells Matched when a job is created or changed, and when Matched is disconnected.
  • Written to Jobber: an expense on the job you confirm, with its title, description, date, amount and receipt, removed again if you take it out. Matched never changes a job's details, quotes or invoices.
  • Your team and your decisions: the people on your account and their roles, whose card is whose, which property or job each card option stands for, each match and who or what made it, and, if an owner turns on auto-accept, who turned it on, when, and which warning they saw.
  • Emails: invites, and the weekday Needs a job email to owners, with a record of each one sent and of who turned it off.
  • Connections: encrypted tokens for Jobber, your card platform and your bank connection. For AI assistants you connect, and keys for Matched's read-only API, we keep only a one-way hash of each token or key.
  • Help: questions you ask Ask Matched and its answers, with a short summary of your account (see AI in Matched below); support requests (name, email, message, the page, your browser, and a hash of your IP address); and feedback on help articles and answers.

Service providers for Matched

Matched uses kinds of providers from the part for every app, including: hosting and infrastructure; databases, which also keep uploaded statements; email, to send sign-in codes, invites, the Needs a job email and support replies; payments; error reports and product analytics; site analytics and page speed; AI processing for Ask Matched; and sign-in. The Service providers page names each one and where it is.

Matched also uses a bank connection provider, when it is switched on, so an owner can connect a bank card or American Express. The owner signs in to the bank in the provider's window, and the provider passes Matched the cards the owner chose and their posted charges. Plaid's end user privacy policy also applies to that connection.

Matched works with services you connect: Jobber, and your card platform, Float, Ramp or Brex, as described above. Matched only reads from your card platform and your bank; it writes nothing to them. If you connect your own AI assistant, such as Claude or ChatGPT, it can read your charges and matches and confirm or undo a match, as the person who connected it.

AI in Matched

  • Ask Matched, the help chat, sends your question, the conversation so far and a short summary of your account to our AI provider, to answer from our help articles. The summary holds the company's name, your role, your plan and the charges used this month, which connections are on and when each last synced, and the ten latest charges waiting for a job (merchant, amount, date, and Matched's suggestion and why). It holds no card numbers and no cardholders. Ask Matched only answers; it cannot change anything in your account. We keep the conversations with your account so we can answer follow-ups and improve our help articles, and anything we take from them to plan the product is counted and stripped of names and details first.
  • Job suggestions are worked out by Matched itself, from the job written on a charge, your crew's clock-ins, your jobs and your past choices. They are not sent to our AI provider. A person confirms each match, or an owner confirms in advance by turning on auto-accept for High confidence matches.

How long, in Matched

  • Disconnecting. When an owner disconnects Jobber, your card platform or a bank in Settings, Matched stops reading from it and deletes its token or key. For a bank, Matched also asks the bank connection provider to remove the connection. Charges, matches and what Matched already read stay with your company.
  • Changing Jobber accounts. Connecting your company to a different Jobber account clears the jobs, clients, clock-ins and expenses read from the old one.
  • Deleting the company. An owner can delete the company in Settings. That removes the company, its people and their sign-ins, connections and tokens, charges, matches, clock-ins, chats and statements, and removes bank connections at the provider. Nothing in Jobber or your card platform changes: expenses already sent stay on their jobs. Support requests and feedback are kept after a company is deleted, with the company link removed, so we can answer them.

Otherwise, the part for every app applies.

Dose

Dose (doseapp.ai) is our app for pool service companies on Jobber. Techs log water chemistry on their phones, Dose reads test strips from a photo, readings sync back to Jobber, and the office sees everything in a dashboard. Dose also has its own privacy policy at doseapp.ai/privacy. The part of this policy for every app applies to Dose too; this section adds what is particular to it.

What Dose collects

  • From Jobber, when the company installs Dose: visits and their instructions, job IDs, property addresses, client names, and team members' names, emails and roles. Dose does not store invoices, payments, quotes or message history.
  • Pools and readings: each pool's size, shape, surface, targets and address, and each reading with its chemistry and how confident the strip reader was.
  • Photos: test strip photos are sent to the AI providers to read and are not kept. An optional pool photo for each reading is stored. Both are resized and have their location data removed on the phone before they are sent.
  • Service reports: emailed to the pool owner's address, only after an admin confirms it. We keep the recipient, subject and report.
  • On your device: readings saved for working offline, until they sync.

Dose does not use your device's location.

Service providers for Dose

Besides those in the part for every app:

  • Railway: runs Dose's server. United States.
  • Upstash: a job queue. United States.
  • Cloudflare R2: stores pool photos and export files. United States.
  • SendGrid: sign-in emails, service reports and export links. United States.
  • Google (Gemini) and Anthropic: read test strip photos. Gemini reads first and Anthropic checks. United States.
  • Jobber: the integration itself. Canada and the United States.

How long, in Dose

When a company uninstalls Dose from Jobber, access stops, the admin is emailed a link to an export, and 30 days later everything is permanently deleted, including photos and Jobber tokens. An admin can also ask for deletion, which can be cancelled for 7 days. Export links work for 24 hours. A removed tech's past readings stay attributed to them.

Crews Out

Crews Out (crewsout.com) is our app for time off on a crew that works in Jobber. Someone on the crew asks for days off on their phone and sends the request to their approver from their own WhatsApp or messages app. The approver approves or denies from a link, balances update, and approved time off can go on the Jobber schedule. The part of this policy for every app applies to Crews Out too; this section adds what is particular to it.

What Crews Out collects

From the company (the owner and the office):

  • Company details: the company name, its time zone, work days and holidays, the message app it uses (WhatsApp or Messages), whether time off goes on the Jobber schedule, and whether balances are kept in days or hours.
  • The crew: each person's name, mobile number, email address, start date, who approves their requests, whether they can approve, the message app they use, and whether they are switched on. These are typed in by the office or brought in from Jobber.
  • Time off types and balances: the types the company uses, how each is given (all at once, earned monthly or no limit, with carryover and more after some years), the policies and who is on them, starting balances, and each change the office makes to someone's balance, with its note and who made it. The person sees these notes.
  • Time off: each request's dates, part of a day or hours if any, type, status, any note the person adds, who decided it and when, a reason if it was not approved, where it stands on the Jobber schedule, and a history of what happened and who did it.
  • The office: who is in the office and their role, and for each office invite, who made it, the role it gives, and who used it and when.
  • Connections: the Jobber account's name and ID and the tokens Jobber issues, which we keep encrypted, and records of the AI assistants people have connected (we keep only a one-way hash of each assistant's tokens).

From someone on the crew who joins from their invite: the account they sign in with, and when they joined.

From Jobber, when the company connects it: the account's name, ID, country and when it was created, and each team member's name, email address, mobile number, time zone, whether they are the owner or an admin, whether they have an active Jobber seat, and when they were added to Jobber (used as a start date). Crews Out asks Jobber for permission to read clients only because Jobber requires it before it allows schedule items; Crews Out does not read clients, jobs, quotes or invoices.

Written to Jobber, only when "Show time off on the Jobber schedule" is on and only after a request is approved: one all day task assigned to that person, titled with their name and the type, with the request number. Crews Out moves the task when a change is approved and deletes it when the time off is cancelled. Jobber is told not to email the person about it. Crews Out edits and deletes only the tasks it created.

Messages are sent from your own phone

Crews Out never sends a WhatsApp message or a text. When someone asks for time off, approves it, cancels it, or invites someone, Crews Out opens WhatsApp or the messages app on their own phone with the words filled in, and they press send. The words can include the dates, the type, the note the person added, and a link back to Crews Out. The message goes through WhatsApp, Apple or their phone company, under that service's own terms. Crews Out never sees the message after that, never stores it and never reads replies.

People on a crew, and approvers

If you are on a crew that uses Crews Out, your employer added you, and the records about you are your employer's. We hold them for your employer as their service provider, and use them only to run Crews Out for them.

  • What others see. The office sees everything for the company. An approver sees the requests sent to them, and who else is off or has asked to be off on those days. People on the crew can see who is off in the coming days, and why.
  • Approve links. An approver does not need an account. Each approve link is made for one approver and one request, works only while they can approve, and works once. When it is used we record who decided, when, and the reason if one was given. The person who asked, and the office, see the decision.
  • When you leave. Your employer can switch you off. You then cannot open your page or ask for time off, and your links stop working. Your past requests stay in the company's history.

To see, correct or delete your information, ask your employer first. If you write to us at hello@crewcabstudios.com, we will pass your request to them and help them answer.

Service providers for Crews Out

Crews Out uses the kinds of providers in the part for every app that it needs, including hosting, a database, email to send sign-in codes and to bring "Talk to a person" messages to us, sign-in with Google, AI processing for the features below, and, when they are switched on, error reports, product analytics and page speed. Crews Out stores no files. The Service providers page names each one Crews Out uses and where it is.

Crews Out also works with services people connect: Jobber, as described above, and their own AI assistant, below. WhatsApp and the messages app on someone's phone are theirs, not our providers.

AI in Crews Out

  • Reading dates. When someone types when they want off, such as "Friday" or "July 14 to 18", the words they typed for the dates, today's date and the names of the company's time off types go to our AI provider to work out the dates. Their note is not sent. The person sees the dates and picks the type before anything is sent to an approver. Without our AI provider, built in rules read the dates.
  • Ask, the help chat for signed in people, sends the question, the last few turns of the conversation and the page they are on to our AI provider, to answer from our help articles. Crews Out does not keep the conversation, and its text is not logged.
  • AI assistants people connect (such as Claude, ChatGPT or Muse) work as the person who connected them, see what that person sees in Crews Out, and only after they press Allow. An assistant can ask for, change or cancel that person's time off, and hands back the message to send from their own phone. No assistant can approve or deny. Anyone can disconnect their own assistant, and the office can disconnect anyone's.

What AI reads is a suggestion that a person checks. Approving is always a person's tap.

Analytics in Crews Out

When error reports and product analytics are switched on, the private part of approve links, crew invites and office invites is removed from every error report and analytics event before it is sent. Approve pages, invite pages, the crew list and each person's own page are never recorded by session replay.

How long, in Crews Out

We keep a company's records while it is open. Anyone in the office can download them at any time, as spreadsheets or one file, in Settings, Company. Download your records never includes approve links, invite links or Jobber tokens.

An owner can delete the company in Settings. It closes at once: nobody can open it, approve links, crew invites and office invites stop working, connected assistants are turned off, and Jobber is told to remove Crews Out and its tokens are forgotten. Tasks already on the Jobber schedule stay there. We keep the company's records for 60 days so you can ask for an export or change your mind, then erase them, along with the accounts of people who were only on that company. The record of who agreed to our terms keeps the email address and loses the company. The part for every app describes backups and what the law makes us keep.

Disconnecting Jobber in Settings, or removing Crews Out from Jobber's side, ends the connection at once and forgets the tokens. The tasks already on the schedule stay in Jobber.

Weather X

Weather X (crewcabstudios.com/weatherx) is our app for Jobber companies whose work depends on the weather. Each morning it writes the forecast onto every job with a visit in the next 7 days, as a note in Jobber. When a visit is completed, it writes a second note with the last forecast and the weather that actually happened that day. It can also put each day's forecast on your Jobber schedule. The part of this policy for every app applies to Weather X too; this section adds what is particular to it.

What Weather X collects

  • Your Jobber connection, when an admin connects it: your Jobber account's ID and name, the permissions granted, and the tokens Jobber issues, which we keep encrypted.
  • Read from Jobber: visit dates and times, completion times, the job number and title each visit belongs to, and the map coordinates Jobber holds for the property. The coordinates are used to look up the weather and are not stored.
  • Stored for each visit: Jobber's IDs for the visit, the job and the note, the visit time, the job number and title, and the text of the weather notes we wrote.
  • Written to Jobber: one forecast note on each job, updated in place, and one note for each completed visit. If the forecast on the calendar is on, also one all-day item on each of the next 7 days of your schedule, titled with that day's forecast and removed when the day has passed. Weather X edits and removes only the notes and calendar items it created.
  • Your town: if an admin enters a town or postal code for the calendar forecast, we store the place it matched and its coordinates.
  • Your team: to let people open the Weather X page, we read your active Jobber team list: each person's name, email address and whether they are a Jobber admin. For the people who connect Weather X, or whom an admin gives access, we store their name, email address, Jobber user ID, role and when they last signed in. Removing someone's access deletes their record.
  • Signing in: with Google, or through Jobber for an account admin. From Google, Weather X asks only for your verified email address, to find your access. It does not ask for your name or picture.
  • Running the service: when each daily run and each notification from Jobber was handled, with counts and error codes.

What Weather X does not collect

Weather X does not read or store your clients' names, phone numbers, email addresses or street addresses. It does not ask Jobber for invoices, quotes, payments, expenses, timesheets or messages to clients. It does not use your device's location. It takes no payment today, so it holds no billing details.

Weather lookups

Forecasts and records of actual weather come from Open-Meteo. For each lookup we send a latitude, a longitude and a date range, and nothing else. No account name, job, client or address goes with it, and the request does not say which company it is for. If an admin enters a town for the calendar forecast, the text they typed is sent to Open-Meteo once, to find its coordinates. With no town entered, the calendar forecast is for the area where most of that week's visits are, worked out from the same coordinates. Open-Meteo is credited on every note, as its data licence (CC BY 4.0) requires.

The actual weather is Open-Meteo's analysis for that location and day. It is not a measurement taken at the property.

Service providers for Weather X

Weather X uses the kinds of providers in the part for every app that it needs, including hosting, a database, sign-in with Google, and a weather data provider for the lookups above. The Service providers page names each one Weather X uses and where it is.

Weather X works with one service you connect: Jobber, the integration itself.

How long, in Weather X

We keep a company's records for as long as Weather X is connected. When you disconnect, from the Weather X page or from Jobber, it stops reading your schedule and stops writing notes at once, and Jobber cancels the tokens it gave us. The notes already on your jobs stay in your Jobber account. They are your records, and we can no longer reach them. Disconnecting from the Weather X page removes the forecast items from your schedule first. Disconnecting from Jobber's side does not give us the chance, so up to 7 of them stay until you delete them.

After a disconnect we keep our own records so that you can reconnect the same account and carry on. To have them deleted, email hello@crewcabstudios.com and we will permanently delete your company's records, including the cancelled tokens, within 30 days. A signed-in session on the Weather X page lasts up to 30 days.

Crew Cab Studios
TermsPrivacyService providershello@crewcabstudios.com

Crew Cab Studios is operated by Crew Cab Ventures.
Edmonton, Alberta, Canada