Privacy Policy
Last updated: 30 July 2026
PestDesk is field-operations software for pest control businesses. This policy explains what data we handle, why, how long we keep it, and the choices you have. It covers both the data you enter into PestDesk and data we retrieve from Google on your behalf.
1. Who we are
PestDesk ("PestDesk", "we", "us") provides the web application at app.pestdesk.app. We operate from Ontario, Canada.
For any privacy question, including access and deletion requests, contact [email protected].
2. Data we handle
Your account
When you sign up we store your email address and authentication identifiers, handled by Google Firebase Authentication. We do not store your password.
Your business records
PestDesk stores what you enter in order to run your business: company profile and branding, customers and their contact details and service addresses, jobs and appointments, pesticide application records, invoices and payment status, inventory, and message templates. This information belongs to you. We process it only to provide the service to you.
Google Local Services Ads data
If you choose to connect your Google account, PestDesk retrieves the Local Services Ads leads belonging to the Google Ads account you select. This includes the enquiry's type (call, message or booking), the service category, the consumer's name, phone number and email as provided to Google, the message and call history for that lead, and Google's own lead status, charge and credit information.
Connecting Google is entirely optional. PestDesk's other functions work without it.
Notifications
If you enable push notifications, we store the push subscription your browser generates for that device, so we can alert you when a new lead arrives. It contains no personal information beyond the device's push endpoint.
What we do not collect
PestDesk contains no advertising, no third-party analytics or tracking scripts, and no advertising or cross-site tracking cookies. We do not build profiles of you or your customers.
3. How we use Google user data
Limited Use. PestDesk's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements.
Specifically, data obtained through the Google Ads API is used only to provide the lead-management features you are using it for. We do not sell it, do not transfer it to third parties except as required to run the service or by law, do not use it for advertising, and do not use it to train generalised artificial-intelligence or machine-learning models. No human at PestDesk reads your lead data except where you specifically ask us to for support, or where required for security or legal reasons.
We request the https://www.googleapis.com/auth/adwords scope in order to:
- list the Google Ads accounts you already have access to, so you can choose which to connect;
- read the Local Services leads and lead conversations for that account;
- send replies that you compose, to the consumer, through Google;
- submit lead feedback and credit requests when you ask us to.
PestDesk never creates or modifies advertising campaigns, budgets, bids or account settings, and never accesses any Google Ads account other than the one you select.
4. Where your data is stored
| Provider | Purpose |
|---|---|
| Google Cloud / Firebase (Firestore, Authentication) | Your account and business records |
| Cloudflare (Pages, Workers, Workers KV) | Serving the application; the lead-sync service and its credentials |
| Google Ads API | Source of the Local Services lead data you ask us to retrieve |
These providers act as our processors and are bound by their own security and privacy commitments. Data may be processed on servers outside Canada, including in the United States.
5. Security
- All traffic is encrypted in transit using HTTPS/TLS.
- Each company's records are isolated, with database security rules that permit access only to that company's authenticated account.
- Google authorisation tokens are held server-side, encrypted at rest, and are never sent to the browser or exposed in application code.
- Every request to our lead-sync service is authenticated with a cryptographically verified identity token, and the account it may access is derived from that token rather than from the request.
No system is perfectly secure. If we become aware of a breach affecting your data, we will notify you and the relevant authorities as required by law.
6. How long we keep data
Your business records and retrieved leads are kept for as long as your account is active. If you close your account, or ask us to delete your workspace, we delete your data within 30 days except where we must retain something to comply with a legal obligation.
Disconnecting Google from within PestDesk deletes the stored authorisation token immediately. Leads already retrieved remain in your workspace until you delete them or close your account.
7. Your choices and rights
- Access and correction. Most of your data is visible and editable directly in the app. For anything else, contact us.
- Deletion. Ask us and we will delete your workspace.
- Withdrawing Google access. Use "Disconnect Google" in PestDesk, or revoke PestDesk at myaccount.google.com/permissions.
- Notifications. Turn push notifications off per device in the app, or in your browser settings.
- Complaints. Contact us first. You may also complain to the Office of the Privacy Commissioner of Canada.
8. Your obligations to your own customers
The customer and consumer information you hold in PestDesk belongs to the people it describes. You are the controller of that information and remain responsible for handling it lawfully, including having a proper basis for contacting them and honouring their requests.
9. Children
PestDesk is a business tool and is not directed at children. We do not knowingly collect information from anyone under 16.
10. Changes
We may update this policy as the service changes. The date at the top always reflects the current version. If a change materially affects how we handle your data, we will tell you in the app or by email before it takes effect.