Terms and privacy

Crews Out is run by Crew Cab Ventures, in Edmonton, Alberta. Two documents cover how you use it:

• Terms of Service: the terms for every app we run, then the Crews Out addendum on time off, balances, messages, Jobber and AI.
• Privacy Policy: what we collect, who else handles it, and how to see, fix or delete it. The Crews Out section comes first.

The Service providers page names the companies that handle information for Crews Out today, what each does and where it is. All three are linked at the bottom of the home page and the help center. While the Crews Out addendum is reviewed, the Terms page says it is a draft.

How you agree

There's no box to check. Under Continue with Google and Email me a code on the sign-in page is one line: "By continuing, you agree to the Terms of Service and Privacy Policy." The same line is under Join on an invite and under the buttons that start a company. Carrying on is agreeing, and Crews Out records who agreed, to which version, and when. Your crew agrees the same way when they join from their invite.

When we change a document, a short note shows once at the top of Crews Out and says which one changed. Tap Close, or carry on. Nothing stops you working.

What Crews Out keeps about your crew

• Their name, mobile number and email, from Jobber or from you.
• Their requests: the dates, the type, their note, and who approved or denied it and when.
• Their balances, as you set them.

You confirm you have their permission to add them. Crews Out doesn't read anyone's WhatsApp or texts: messages go from people's own phones, and Crews Out only fills in the words.

Who can see what

• The office (owners and office staff) sees everything for your company.
• An approver sees the requests waiting for an answer, and who else is off on those days.
• A crew member sees only their own time off.

Nobody at another company sees anything of yours.

Your data

To get a copy, correct something, or ask us to delete it, see Export your data or close your account, or write to the address in the Privacy Policy. For a security problem, see Security.