Privacy Policy

This privacy policy applies to the Servicebay apps for mobile devices and the Servicebay web application at app.servicebay.io (hereby referred to as "Application"), the Servicebay website (servicebay.io), and the Servicebay developer platform (developer.servicebay.io, including the Servicebay API and connections to other apps and AI assistants) that are provided by SK Digital (ABN 37 580 963 803) (hereby referred to as "Service Provider"), the business name of Sebastian Karl Klopfer, a sole trader in Australia, as a commercial service. This service is intended for use "AS IS".

Website (servicebay.io)

The Servicebay website uses Google Analytics 4 to understand how visitors use the site. Google Analytics collects information such as pages visited, time spent on pages, and how you arrived at the site. This helps the Service Provider improve the website experience. IP addresses are anonymized before processing. For more information, see Google's Privacy Policy and Google Analytics Privacy.

The Servicebay website also uses Meta Pixel (Facebook Pixel) to measure the effectiveness of advertising, understand visitor actions, and deliver targeted ads. Meta Pixel collects information such as pages visited and actions taken on the site. For more information, see Meta's Privacy Policy.

The Servicebay website also uses PostHog to record which pages are visited and which signup and lead actions are taken. PostHog loads only after you accept the cookie banner. It records pages visited and the events signup_cta_click and generate_lead. It does not receive the contact-form message or your email address. Session recording is not used. For more information, see PostHog's Privacy Policy.

When you arrive on the Servicebay website through a partner's link, PromoteKit, which runs the Servicebay partner programme, sets a referral cookie so that the partner who referred you is credited (PromoteKit's Privacy Notice). Whatever you choose in the cookie banner, the website also keeps the partner's id from that link in your browser's local storage for 60 days and adds it to links from the website to the Servicebay web application (app.servicebay.io), so that the referral reaches the Application when you sign up.

When you come to the Servicebay website from an ad or a campaign link, the website keeps the link's campaign tags (its UTM parameters) in your browser's local storage and, whatever you choose in the cookie banner, adds them to the website's links for creating a Servicebay account, so that the Application keeps them with your organisation. The link may also carry the ad's click id (gclid from Google, fbclid from Meta, ttclid from TikTok). Until you answer the cookie banner, the website keeps the click id only in memory and never stores it in your browser. If you reload the page you arrived on, the website reads the click id from that page's address again; if you close the website, or reload a page whose address does not carry the click id, before you answer, the click id is gone. If you accept, the website stores the click id in your browser's local storage and adds it to its links for creating a Servicebay account; if you decline, it forgets the click id. Once you have answered, the website also adds your answer, accepted or declined, to every link from the website to the Servicebay web application (app.servicebay.io), and the Application keeps that answer with the organisation you then create there. If you create an organisation in the Application after opening it from one of those links with your answer accepted, the Application sends a trial start event to Google Analytics (through the GA4 Measurement Protocol) and to Meta (through the Meta Conversions API), so that the Service Provider can measure which ads lead to sign-ups. Each event carries the campaign tags and only that network's own click id: the gclid goes only to Google, the fbclid only to Meta, and the ttclid to neither. The event to Google also carries the organisation's Servicebay id; the event to Meta carries that id only as a one-way hash (SHA-256), never the id itself. The Application sends neither event for an organisation created without an accepted answer, for example when you declined cookies, did not answer the cookie banner, or signed up in a mobile app.

These website analytics and advertising cookies are loaded only after you accept them in the cookie banner shown on your first visit. If you decline, Google Analytics, Meta Pixel, PostHog, and PromoteKit are not loaded, no related cookies are set, the website forgets the ad's click id, and the Application sends no trial start event for an organisation you create; only the essential cookies needed to run the site remain. Your choice is saved on your device, and you can change it at any time by clearing this site's cookies and site data in your browser, which will display the banner again.

Information Collection and Use

The Application collects information when you download and use it. This information may include information such as:

  • Your device's Internet Protocol address (e.g. IP address)
  • The pages of the Application that you visit, the time and date of your visit, the time spent on those pages
  • The time spent on the Application
  • The operating system you use on your mobile device

When you use features that require it, the Application may collect your device's approximate location. Location is used only to support payment features (for example, Tap to Pay and card-reader connectivity required by our payment processor) and to attach job-site addresses to service tickets you create. Servicebay does not use location for advertising or unrelated tracking.

The Service Provider may use the information you provided to contact you from time to time to provide you with important information, required notices and marketing promotions.

For a better experience, while using the Application, the Service Provider may require you to provide us with certain personally identifiable information, including but not limited to email, first name, last name, address, phone number, business name, business address. The information that the Service Provider request will be retained by them and used as described in this privacy policy.

Third Party Access

The Application shares account and usage information with the providers listed below so the Service Provider can run and improve the service. The Service Provider may share your information with third parties in the ways that are described in this privacy statement.

Please note that the Application utilizes third-party services that have their own Privacy Policy about handling data. Below are the links to the Privacy Policy of the third-party service providers used by the Application:

  • Google Play Services
  • Google Analytics for Firebase
  • Firebase (Auth, Firestore, Cloud Functions, Messaging, Storage)
  • Sentry
  • Stripe
  • PostHog
  • PromoteKit
  • Meta (Facebook)
  • Cloudflare (Servicebay sign-in for connected apps and the connection service)
  • Vercel (Servicebay developer site and API)
  • Upstash (request rate limiting)
  • Resend (email delivery: the recipient's email address, the message and its attachments for the emails the Application sends, such as quotes, invoices, job updates, payment reminders, team invitations, shared forms, data exports and account emails, and for messages sent through the website's contact form and free tools)
  • Google Calendar (only if you connect it; see Calendar Sync)
  • Microsoft (Outlook Calendar) (only if you connect it; see Calendar Sync)
  • Xero (only if your organisation's admin connects it: your customers' names, email addresses, phone numbers and addresses, and your invoices with their line items, tax and PDF copy, payments, refunds, and Stripe payouts and fees; payments, contact changes and items recorded in Xero come back into Servicebay)
  • Intuit QuickBooks (only if your organisation's admin connects it: the same data as for Xero, and payments, contact changes and items recorded in QuickBooks come back into Servicebay)

Product analytics

The Application uses PostHog to measure how the product is used: creating an account, creating a job, sending an invoice, inviting a team member, and how often the Application is opened. PostHog receives the signed-in user's account id, name, and email, and the id and name of the organisation they are working in. It does not receive customer names, customer email addresses, job notes, or invoice contents. Session recording is not used. See PostHog's privacy policy.

The Service Provider may disclose User Provided and Automatically Collected Information:

  • as required by law, such as to comply with a subpoena, or similar legal process;
  • when they believe in good faith that disclosure is necessary to protect their rights, protect your safety or the safety of others, investigate fraud, or respond to a government request;
  • with their trusted services providers who work on their behalf, do not have an independent use of the information we disclose to them, and have agreed to adhere to the rules set forth in this privacy statement.

Payments & Subscriptions

Servicebay uses Stripe to process subscription billing and, where enabled, to process payments that organisations collect from their own customers. Payment card details are entered into and handled by Stripe and are not stored on Servicebay's servers. Servicebay receives limited billing information such as subscription status, plan tier, seat counts, billing interval, and the brand and last four digits of a card, in order to manage your subscription. Stripe's handling of payment data is governed by Stripe's Privacy Policy.

Partner referrals

If you arrive at the Servicebay web app through a Servicebay partner's link, the Application keeps that partner's referral code: it is saved with your organisation when you create it, or sent with your subscription checkout. If the Servicebay website set PromoteKit's referral cookie after you accepted cookies there, the Application reads PromoteKit's referral id from that cookie and keeps it the same way. When your organisation subscribes, the referral is passed to Stripe with the subscription and saved on your organisation's Stripe customer record, so that PromoteKit, which runs the Servicebay partner programme, can credit the partner, and so that a first subscription gets the partner discount. For this, PromoteKit receives the subscription's billing details from Stripe, such as the business name, billing email and payments. A partner's promo code you enter when subscribing is passed to Stripe with the subscription the same way, so that PromoteKit can credit that partner. The Application itself does not load PromoteKit or set its cookie. The partner's code is part of the web address you arrive on, so PostHog also receives it with that page view (see Product analytics). See PromoteKit's privacy policy.

Connected Apps and AI Assistants

Admins of a Servicebay organisation on a Pro plan or trial can connect Servicebay to other apps and AI assistants. Examples are the Google Gemini app and Google Search (through Google's Connected Apps platform), AI tools that use the Model Context Protocol (MCP), and integrations built on the Servicebay API. A connection is made only when an admin signs in to Servicebay and approves it. It is limited to the organisation and permissions the admin approves.

What a connected app can access. When you ask a connected app something, it requests the matching records from Servicebay and uses them to answer you. The Google Gemini and Google Search connection is read-only and can access:

  • customers: name, business name, email address, phone numbers, address, notes, customer type and preferred contact method;
  • jobs: job number, status, customer contact details, device, service requested, service notes and address, whether a technician is assigned, schedule, and warranty details;
  • your job status list;
  • appointments: title, time, technician name, location and notes;
  • quotes and invoices: number, title, customer, line items, discounts, amounts, dates, payment or acceptance status, and the message on the document.

It cannot create, change or delete anything in Servicebay. It cannot see payment card details (Stripe holds those), passwords, team members or organisation settings. Other connected apps can use only the permissions the admin approved when connecting them, which may include making changes.

Servicebay does not receive your conversation with the assistant. It receives only the request the assistant makes, for example a job number, a customer name to search for, or a date range.

What Servicebay stores. For each connection, Servicebay stores which user connected which organisation, which app, the permissions granted, when the connection was made and last used, and the security tokens the app uses, kept in hashed or encrypted form. Servicebay also records requests made through connections in your organisation's activity log: the time, the app, the kind of record requested, whether the request succeeded, and the IP address it came from. Your organisation's admins can see this log. Entries are deleted automatically after 90 days. These records are used to run, secure and troubleshoot connections, and for no other purpose.

What the connected app does with your data. Once Servicebay returns data to a connected app, the app's provider handles it under its own privacy policy. For the Gemini app and Google Search, see the Gemini Apps Privacy Hub and Google's Privacy Policy. Servicebay does not keep a copy of the records it returns to a connected app, and does not sell data shared through connections or use it for advertising.

Disconnecting and deleting. You can disconnect at any time. From Google, open your Google Account connections and remove Servicebay. Google then tells Servicebay, and the connection stops working immediately. In Servicebay, an organisation admin can revoke any connected app at developer.servicebay.io/develop/connected-apps. A connection also ends automatically if the admin who made it is removed from the organisation or deactivated. When a connection is disconnected or revoked, Servicebay deletes it, along with its security tokens and any permission changes an admin made to it. A connection that stops working on its own, such as a Google connection unused for 30 days or a connection whose expiry date has passed, is deleted automatically within about two days. Activity log entries are deleted automatically after 90 days. Disconnecting does not delete your Servicebay data, such as customers, jobs, quotes and invoices; see Account Deletion below. To have any other connection records deleted, contact [email protected]. Step-by-step instructions are in Connect Servicebay to Google Gemini and Search.

Calendar Sync (Google Calendar and Outlook Calendar)

Each member of a Servicebay organisation can choose to put their Servicebay jobs in their own Google Calendar or Outlook Calendar (Microsoft), or both. Nothing is synced until that member connects their own Google or Microsoft account in Settings → Calendar Sync and approves access on Google's or Microsoft's sign-in page. For a Microsoft 365 work or school account, the organisation's IT admin may have to approve Servicebay first. Admins of a Servicebay organisation can turn Google Calendar or Outlook Calendar off for the whole organisation.

What goes into your calendar. Calendar sync works one way, from Servicebay to your calendar. Servicebay makes a separate Servicebay calendar in your Google or Microsoft account and puts a copy of each of these in it:

  • the jobs assigned to you, or every job in your organisation if you choose All Jobs (not available to viewers);
  • the calendar events assigned to you in Servicebay, unless you turn off Include my calendar events.

A job's copy contains the job number, the customer's name, the service requested, the job status, the customer's phone number, the date and time, a link to the job in Servicebay and, for a job done at the customer's site, the job's address. An event's copy contains its title, notes, date and time. Copies are made for jobs and events from the start of the current week up to a year ahead. When a job or event is changed, reassigned or deleted in Servicebay, its copy is updated or deleted. Nothing is read back from your calendar into Servicebay, and a change you make to a copy in your calendar is replaced the next time that job or event changes in Servicebay. Once a copy is in your calendar, Google or Microsoft holds it under its own privacy policy (Google's Privacy Policy, Microsoft Privacy Statement), and anyone you share that calendar with can see it.

What Servicebay can access in your Google or Microsoft account.

  • Google Calendar: Servicebay asks Google for your email address and for permission to make its own calendars and manage the events in them (the Google Calendar scope calendar.app.created). With this permission Servicebay cannot see your other calendars or their events.
  • Outlook Calendar: Servicebay asks Microsoft for your email address and for permission to read and write your calendars (the Microsoft Graph permission Calendars.ReadWrite), the narrowest Microsoft permission that lets an app make a calendar of its own. Servicebay uses it only for the calendar it made: it creates, updates and deletes that calendar and the copies in it. To find that calendar again, it looks only for a calendar with that calendar's name that carries Servicebay's own marker. It does not read the events in your other calendars, and does not copy or store anything from them.

With either, Servicebay also receives a security token that lets it keep your calendar up to date while you are not using Servicebay.

What Servicebay stores. For each connection, Servicebay stores the email address and account id of the Google or Microsoft account you connected, the security tokens that let it update your calendar (encrypted), the id of the calendar it made, the ids of the copies it made, the time zone of the device you connected from, and the connection's status, such as when it last synced. These records are kept while the connection exists. A connection you start but do not finish is deleted after about an hour. Your organisation's admins can see each member's calendar connection, such as the connected account and whether it is syncing, but not the contents of that member's calendar. These records are used to run, secure and troubleshoot calendar sync, and for no other purpose.

Google user data. Servicebay's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Servicebay uses the information it receives from Google only to put your jobs in your Google Calendar and keep them up to date. It does not sell it, use it for advertising, or transfer it to anyone, except to the providers that host Servicebay as needed to run calendar sync, or as required by law. It does not use it to develop, improve or train artificial intelligence or machine learning models. People at Servicebay do not read it unless you ask them to (for example, for support), it is needed for security, or the law requires it. Servicebay treats the information it receives from Microsoft the same way.

Disconnecting and deleting. You can disconnect Google Calendar or Outlook Calendar at any time in Settings → Calendar Sync. Servicebay then deletes the Servicebay calendar it made in your account, with the copies in it, and its stored security tokens and connection records. For Google, it also revokes Servicebay's access, unless the same Google account is still connected to Servicebay elsewhere (for example, through another organisation). The same happens when an admin disconnects your calendar, when an admin turns that calendar off for the organisation, and when you leave the organisation. You can also remove Servicebay's access from your Google Account connections, your personal Microsoft account's app permissions, or, for a work or school account, My Apps. Sync then stops, but Servicebay can no longer delete its calendar in your account: delete it there yourself, and disconnect in Servicebay to delete the stored records. Disconnecting does not delete your Servicebay data, such as customers and jobs; see Account Deletion below.

Opt-Out Rights

You can stop all collection of information by the Servicebay mobile apps by uninstalling them, using the standard uninstall process of your mobile device or app store. Uninstalling does not delete your Servicebay account. To stop collection by the web application (app.servicebay.io), delete your account as described in Account Deletion below. On the Servicebay website, you can decline analytics and advertising cookies in the cookie banner, as described in Website (servicebay.io).

If your organisation has connected Servicebay to another app or AI assistant, your organisation's admin can stop that sharing at any time by disconnecting it, as described in Connected Apps and AI Assistants.

If you have connected Google Calendar or Outlook Calendar, you can stop calendar sync at any time by disconnecting it, as described in Calendar Sync.

Data Retention Policy

The Service Provider will retain User Provided data for as long as you use the Application and for a reasonable time thereafter.

Account Deletion

You may permanently delete your Servicebay account at any time from within the Application: Settings → Privacy & Data → Delete Account. You may also request account deletion by contacting [email protected]. Deletion removes your user account and associated personal data from Servicebay's systems, subject to any data your organisation retains for its own business records (for example, jobs or invoices created while you were a team member).

Children

The Service Provider does not use the Application to knowingly solicit data from or market to children under the age of 13.

The Application does not address anyone under the age of 13. The Service Provider does not knowingly collect personally identifiable information from children under 13 years of age. In the case the Service Provider discover that a child under 13 has provided personal information, the Service Provider will immediately delete this from their servers. If you are a parent or guardian and you are aware that your child has provided us with personal information, please contact the Service Provider ([email protected]) so that they will be able to take the necessary actions.

Security

The Service Provider is concerned about safeguarding the confidentiality of your information. The Service Provider provides physical, electronic, and procedural safeguards to protect information the Service Provider processes and maintains.

Changes

This Privacy Policy may be updated from time to time for any reason. The Service Provider will notify you of any changes to the Privacy Policy by updating this page with the new Privacy Policy. You are advised to consult this Privacy Policy regularly for any changes, as continued use is deemed approval of all changes.

This privacy policy is effective as of 2026-11-20

Your Consent

By using the Application, you are consenting to the processing of your information as set forth in this Privacy Policy now and as amended by us.

Contact Us

If you have any questions regarding privacy while using the Application, or have questions about the practices, please contact the Service Provider via email at [email protected].

Service Provider: SK Digital, the business name of Sebastian Karl Klopfer (sole trader), Australia. ABN 37 580 963 803.



Start free trial — 30 days, no credit card. Servicebay on iOS, Android, and Web.