Privacy policy

Google user data

A customer may connect a Google Calendar so the agent can offer times that are genuinely free and put the appointment on the calendar before it confirms it. Connecting one is optional, the customer authorizes it themselves, and until they do we read nothing from any Google account.

PsPro AI's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

• What we ask for.Five scopes and no more: sign-in, used to identify the Google account authorizing the connection; availability, used to read the free/busy windows on the calendar the customer picked; the calendar list, used to show them which of their calendars the account can write to so they can pick one; calendar events, used to create and cancel the appointments our agent books; and the account's email address, so the setup screen can show which Google account is connected rather than leaving the customer to guess. We do not ask for read access to the contents of a calendar, and the calendar connection does not request Gmail, Drive, Contacts, or any other Google service.
• Sending from Gmail. Separately from the calendar, a customer may connect a Gmail mailbox so the emails we send their own customers come from it, as described under Email from your own mailbox. That asks for three scopes and no more: sign-in, the account's email address, and permission to send email. We do not ask to read, search, label or delete anything in the mailbox, and the access the customer grants cannot do so.
• Signing in with Google. Separately from the calendar, anyone may sign in to PsPro AIwith their Google account. That asks for the account's name, email address and profile picture and nothing else, grants no access to the calendar or any other Google service, and is used only to sign the person in.
• What we can see.A free/busy read returns only the times a calendar is busy. The titles, guests, descriptions and locations of a customer's existing events are never returned to us, never shown to the agent, and never stored. This is a limit of what the customer grants us, not only of what we ask Google for: the access they authorize cannot read the contents of an existing event.
• What we do with it. Google user data is used only to provide and improve the feature the customer connected it for: for a calendar, checking availability, writing the appointment, and showing that appointment on their dashboard; for a Gmail mailbox, sending the emails about a customer's visits that would otherwise come from us.
• No advertising. Google user data is never used for advertising, and is never sold or transferred to anyone for advertising purposes.
• No model training. Google user data is not used to develop, improve, or train generalized or non-personalized artificial intelligence or machine-learning models, ours or anyone else's. The times the agent may offer are worked out from a free/busy read and are put in front of our model provider so it can offer one; that provider does not train its models on them, and no event details are included.
• No transfer. We do not transfer Google user data to others except as necessary to provide or improve this feature, to comply with applicable law, or as part of a merger or acquisition subject to this policy.
• Nobody reads it. No human at PsPro AIreads Google user data, except with the customer's explicit consent, where necessary for security purposes such as investigating abuse, to comply with applicable law, or where the data has been aggregated and de-identified.
• How it is held.The long-lived authorization Google issues is sealed with AES-256-GCM before it is written to our database and is never stored in readable form. Free/busy results are held for up to ten minutes so that a caller waiting on an answer is not made to wait for the same question to be asked of Google again; what is held is the start and end of each busy period and nothing about the events themselves. It is deleted once that period is up, and immediately when the customer changes calendars or disconnects. The connected account's email address and the name of the chosen calendar are erased when the customer disconnects.
• How to disconnect. Disconnect on the setup screen erases the stored authorization immediately and the agent stops booking; Disconnect on the Account page does the same for a Gmail mailbox, and emails go from us again. Access can also be withdrawn at any time from the Google account's own permissions page, which has the same effect.

Microsoft 365 calendar data

A customer on Office 365 or Outlook may instead connect a Microsoft 365 calendar, for exactly the same purpose: so the agent can offer times that are genuinely free and put the appointment on the calendar before it confirms it. Connecting one is optional, the customer authorizes it themselves, and until they do we read nothing from any Microsoft account.

• What we ask for.Three Microsoft Graph permissions and no more: read and write access to the customer's calendars, used to read when the calendar they picked is taken and to create and cancel the appointments our agent books; the basic profile of the signed-in account, so the setup screen can show which mailbox is connected rather than leaving the customer to guess; and permission to send mail as that mailbox, used only for the emails described under Email from your own mailbox. Connecting the calendar connects that mailbox too, unless the customer has already connected a different one. Nothing is requested that can read, move or delete a message, or reach files, contacts, Teams, the directory or any other Microsoft service.
• Signing in with Microsoft. Separately from the calendar, anyone may sign in to PsPro AIwith their work Microsoft account. That asks for the account's name and email address and nothing else, grants no access to the calendar, mail or any other Microsoft service, and is used only to sign the person in.
• What we can see. Microsoft offers no permission that returns availability alone, so the authorization a customer grants is necessarily wider than what we ask of it. The request is what is narrow: when we read the calendar we name the four fields we want — the start, the end, whether the time counts as busy, and whether the entry was cancelled — so the subjects, guests, descriptions and locations of a customer's existing events are never sent to us, never shown to the agent, and never stored. We never read the contents of an event, and nothing in the product does.
• What we do with it. Calendar data is used only to provide and improve the booking feature the customer connected it for: checking availability, writing the appointment, and showing that appointment on their dashboard. It is never used for advertising, never sold, and never used to develop, improve or train artificial intelligence or machine-learning models, ours or anyone else's.
• Nobody reads it. No human at PsPro AIreads it, except with the customer's explicit consent, where necessary for security purposes such as investigating abuse, to comply with applicable law, or where the data has been aggregated and de-identified.
• How it is held.The long-lived authorization Microsoft issues is sealed with AES-256-GCM before it is written to our database and is never stored in readable form. Busy periods are held for up to ten minutes so that a caller waiting on an answer is not made to wait for the same question to be asked again; what is held is the start and end of each busy period and nothing about the entries themselves. It is deleted once that period is up, and immediately when the customer changes calendars or disconnects. The connected mailbox's address and the name of the chosen calendar are erased when the customer disconnects.
• How to disconnect. Disconnect on the setup screen erases the stored authorization immediately and the agent stops booking. Access can also be withdrawn at any time from the Microsoft account's own app permissions page, or by a tenant administrator, both of which have the same effect.

Jobber data

A customer who runs their business on Jobber may connect their Jobber account so the agent can offer times their schedule is genuinely free and put the visit on it before it confirms it. Connecting one is optional, an administrator on the Jobber account authorizes it themselves on Jobber's own consent screen, and until they do we read nothing from any Jobber account.

Our app is configured with the narrowest set of permissions the booking feature needs, and Jobber data is used only to provide that feature to the customer who connected it. Jobber remains the system of record for everything in the account; we add a booking to it and read enough of it to know when not to.

• What we read.Three things and no more. The account's own name, so the setup screen can show which Jobber account is connected rather than leaving the customer to guess. The start and end times of what is already on the schedule — visits, assessments, tasks and events — so an hour that is already spoken for is never offered. And, at the moment a caller books, a search of the client list on the phone number or email address that caller gave, so the visit is filed under the client the business already has rather than a duplicate of them; that search returns at most five records, and of those only their identifiers, phone numbers, email addresses and the identifiers of their properties. We do not read quotes, invoices, payments, payroll or reports, and we do not read the titles, descriptions, notes, addresses or client details of anything already on the schedule.
• What we write.The client, job and visit for an appointment the agent booked, and nothing else. The caller's name, their phone number, their email address where they gave one, the address they gave and what they said they need are sent, because a visit in Jobber is filed under the client it is for and a crew has to be told where to go. Where a booking is cancelled we remove the visit we created; where it is moved, that visit comes off and a new one goes on at the new time. We do not alter a client, job or visit we did not create, with one exception: where a caller gives an email address, we read the email addresses already on the client record the visit is filed under and add theirs if it is not among them, so the business can reach the person it is about to visit.
• What we do with it. Jobber data is used only to provide and improve the booking feature the customer connected it for: checking what is free, writing the visit, cancelling it if the caller cancels, and showing that visit on their dashboard.
• No sale, no advertising. Jobber data is never sold, never shared with anyone but the subprocessors named below who operate our infrastructure, and never used for advertising by us or by anyone else.
• No model training. Jobber data is not used to develop, improve or train generalized or non-personalized artificial intelligence or machine-learning models, ours or anyone else's. The free windows the agent may offer are worked out from the start and end times above before the model is asked to offer one; the contents of a customer's schedule are not put in front of it.
• How it is held. The authorization Jobber issues is sealed with AES-256-GCM before it is written to our database and is never stored in readable form. Refresh token rotation is on, so each refresh replaces the token that was spent. What we keep beside it is the Jobber account identifier, the account name, and the identifiers of the client, job and visit we created, so a booking can be found again and taken back off the schedule.
• How to disconnect. Either side works, and both have the same effect. Disconnect on our setup screen erases the stored authorization immediately, hands the grant back to Jobber, and the agent stops booking. Disconnecting our app from Jobber's own connected apps page invalidates every token at Jobber and notifies us, and on that notice we erase what we hold and mark the connection inactive. Visits already written to the schedule stay there, because they belong to the business rather than to us.
• Nobody reads it. No human at PsPro AIreads a customer's Jobber data, except with their explicit consent, where necessary for security purposes such as investigating abuse, or to comply with applicable law.
• Not affiliated. Jobber is a trademark of Octopusapp Inc., d/b/a Jobber. This integration is built and operated by PsPro AI; we are not affiliated with, endorsed by or sponsored by Jobber, and their handling of the data held in a Jobber account is governed by their own privacy policy rather than this one.

Email from your own mailbox

When an appointment is moved or cancelled, PsPro AI emails the customer's own customer at the address they gave, to tell them. A customer may connect their own mailbox so that email comes from their address and replies go to their inbox. Connecting one is optional and is done on the Account page; until they do, the email comes from us, with replies sent to the business.

• Gmail and Outlook. The customer signs in with Google or Microsoft and grants permission to send email as that mailbox, plus its email address so the Account page can show which mailbox is connected. Nothing else is requested. Connecting a Microsoft 365 calendar grants the same permission for that mailbox at the same time. We cannot read, search, move or delete any message in the mailbox, and we do not ask to.
• Any other provider (SMTP). The customer enters their mail server's name and port, a username and password, and the address to send as. Before anything is saved we send a test email through that server to the person entering the details, so a mistake is found then rather than on a customer's email. The connection is always encrypted and the server's certificate is checked. A password used here can be used by a mail server for more than sending, which is why many providers offer an app password limited to this; we use it only to send.
• What is sent.Only the emails described above: the recipient's address, the business's name, the new and previous time of the visit, and its location where one is recorded, plus the test email when SMTP details are saved. Copies may appear in the mailbox's own Sent folder, which is the provider's doing and is governed by its own privacy policy. We keep no copy of the message.
• What we do with it.The mailbox connection is used only to send those emails. It is never used for advertising, never sold, and never used to develop, improve or train artificial intelligence or machine-learning models, ours or anyone else's. No human at PsPro AIuses it, except with the customer's explicit consent, where necessary for security purposes such as investigating abuse, or to comply with applicable law.
• How it is held.The Google or Microsoft authorization, or the SMTP password, is sealed with AES-256-GCM before it is written to our database, is never stored in readable form, and is never shown again, including to the customer. Beside it we keep the mailbox's address and, for SMTP, the server name, port and username. Our audit log records when a mailbox was connected, disconnected or stopped working, and for SMTP the server name and port; it never records the password.
• How to disconnect. Disconnect on the Account page erases the stored authorization or password, the mailbox's address and the server details immediately, and emails go from us again. Connecting a different mailbox does the same to the one it replaces. Gmail and Outlook access can also be withdrawn from the Google or Microsoft account's own permissions page; changing an SMTP password at the provider has the same effect for SMTP.

Payment data and Stripe

Payments are processed by Stripe. When you provide personal data in connection with PsPro AI's payment features, Stripe receives that personal data and processes it in accordance with Stripe's Privacy Policy. Stripe has published an updated Privacy Policy that takes effect on November 20, 2026.

• Our own fees.When a customer subscribes, we send Stripe the name and billing email address on the account. Card details are entered on Stripe's own page and are never sent to or stored by us.
• Connecting Stripe.A customer who connects a Stripe account for deposits is sent to Stripe's hosted pages, where Stripe collects the bank details, tax identification and identity information it requires. None of it reaches us. We send Stripe the business name and the email address of the person connecting, and we keep the Stripe account identifier and whether it can take payments.
• Paying a deposit.A caller asked for a deposit pays on a Stripe page, on the business's own Stripe account. The caller's card details, and anything else that page asks for, go to Stripe and not to us; we learn only whether the deposit was paid. The page names the business and the amount, and nothing about the caller's address or the service booked.

SMS and text messaging program

Program. PsPro AI operates an appointment and lead follow-up messaging program. When you submit a form on our website and provide your mobile number with consent, you may receive SMS and MMS text messages from us to confirm your request, ask qualifying questions, answer service questions, and schedule appointments.

Consent. You opt in by checking the unchecked SMS and call consent box and submitting your mobile number on either our contact form or our account signup form. These are the only ways we collect messaging consent, the box is never pre-ticked, and one tick covers both text messages and phone calls. Each opt-in is recorded with the wording you were shown and the time you gave it.

It is optional. The box is optional on both forms. Leaving it clear does not stop you sending an enquiry or opening an account — we reply to the email address you gave instead — and consent to receive text messages is not a condition of any purchase.

What it applies to. Your opt-in is recorded against your phone number rather than against the form you gave it on, so you are asked once rather than every time. If you opted in at signup and later send us an enquiry from the same number, we may answer it by text without asking again. If that number has no opt-in on record, nothing is sent to your phone.

Message frequency. Message frequency varies based on your interaction with us.

Quiet hours.A message we start is held outside the quiet-hours window set on the account it is sent for and goes out when that window opens. The default window is 9:00pm to 8:00am in that account's own timezone. A reply to a message you sent, the text after a call we could not answer, and the acknowledgement of a form you have just submitted are answers to something you did, and are not held.

Rates. Message and data rates may apply.

Opt-out. You can opt out at any time by replying STOP to any message. After you reply STOP, we will send a single confirmation and no further messages will be sent unless you re-subscribe. Because the opt-in covered both channels, replying STOP also withdraws it for calls.

Help. Reply HELP for assistance, or contact us at info@psproai.com or +1 (385) 331-0984.

No sharing of mobile data. No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Mobile opt-in data and consent are never shared or sold to third parties or lead generators. This includes text messaging originator opt-in data and consent, which will not be shared with any third parties.