Privacy Policy

When a tradesperson signs up to use TaskWright, we are the "controller" of their personal data (their name, business details, contact details, billing information, and so on). This means we decide how and why that data is used, and this policy explains how.

When a tradesperson uses TaskWright to manage their own customers (storing their clients' names, addresses, phone numbers, job details, etc.), the tradesperson is the "controller" of that data — they decide how it's used. We are the "processor", meaning we handle that data only on the tradesperson's instructions and on their behalf. Our responsibilities as a processor are set out in our Data Processing Agreement, which forms part of our Terms of Service with each operator.

• Name and business name
• Email address and phone number(s)
• Business address and service area
• Billing and payment details (processed securely by Stripe — we do not store full card details)
• Account settings, preferences, and content you create in the system
• Communications you send to us (e.g. support messages)
• Technical data: device/browser information, log data, and usage information

• Client names, addresses, email addresses, and phone numbers
• Job details, notes, quotes, invoices, and payment records
• Photos uploaded in connection with jobs or enquiries
• Message history (SMS/email) between the operator and their clients

• Analytics and cookie data (see the Cookies section)

If an operator chooses to connect their Google account, we request the following access using Google OAuth:

• Google Calendar — manage events — the https://www.googleapis.com/auth/calendar.events scope. We use this to create, update, and delete calendar events that represent the operator's own TaskWright job bookings, in the calendar the operator selects. We only create, update, or delete events that TaskWright Trades itself has created for the operator's jobs; we do not modify the operator's other personal or existing events.
• Google Calendar — read — the https://www.googleapis.com/auth/calendar.readonly scope. We use this to list the operator's calendars (so they can choose which one to sync to) and to read the times of their existing events, so we can show their busy periods within TaskWright Trades and help them avoid double-booking.
• Basic account information — the operator's email address and basic profile information (email, openid, profile scopes), used to identify the connected Google account.

• Writing job bookings to the calendar: When an operator books, reschedules, completes, or cancels a job in TaskWright Trades, we create, update, or delete a corresponding event in their chosen Google Calendar. These events contain minimal information — a short label, the client's first name only, the date, time and duration of the job, and a note directing the operator to manage the booking in TaskWright Trades. We do not include any other client details (such as surname, full name, address, phone number, email, or price) in the calendar event.
• Reading the calendar to show conflicts: We read the times of the operator's existing calendar events solely to display their busy periods on screen within TaskWright Trades, so they can see their commitments alongside their jobs when scheduling. This read information is used only for on-screen display and is not stored as part of the operator's TaskWright data or used to take any automated action.
• We request the narrowest access necessary for these features and do not access Google user data for any purpose other than providing the calendar-sync and conflict-display features described here.

Changes made directly in the operator's Google Calendar do not change the operator's jobs or clients in TaskWright Trades, and never trigger any message to the operator's clients. TaskWright Trades remains the source of truth for job bookings: if a TaskWright job event is changed or deleted directly in Google Calendar, TaskWright Trades restores it to match. Calendar data we read is used only to display conflicts on screen.

• We store the minimal information needed to keep job events in sync — specifically, the identifiers of the calendar events we have created for the operator's jobs (so we can update or remove them) and the operator's chosen calendar. We do not store the content of the operator's other personal calendar events.
• Calendar event times that we read to display busy periods are used for on-screen display and are not permanently stored; they are held only transiently to render the conflict view.
• Access and refresh tokens used to connect to Google are stored securely and are used only to provide the calendar feature.
• An operator can disconnect their Google account at any time, which revokes our access and stops any further reading or writing. They can also revoke access directly from their Google Account settings (myaccount.google.com → Security → Third-party access).

• We do not sell Google user data to anyone.
• We do not share, transfer, or disclose Google user data to third parties, except as necessary to provide the feature to the operator, to comply with applicable law, or as part of a merger or acquisition (in which case we would continue to protect it under this policy).
• We do not use Google user data for advertising, and we do not use it to train generalised or non-personalised artificial intelligence or machine learning models.
• We do not allow humans to read Google user data unless we have the operator's consent, it is necessary for security purposes (such as investigating abuse) or to comply with applicable law, or the data has been aggregated and anonymised.

TaskWright Trades' use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.