PestRouting

Dayem Solutions UG (haftungsbeschränkt)
Otto-Lilienthal-Straße 36
71034 Böblingen
Germany

Email: hello@pestrouting.com
Support: support@pestrouting.com

1. Scope

This page applies to PestRouting, including:

pestrouting.com;
app.pestrouting.com;
the PestRouting web application;
routing optimization and scheduling features;
FieldRoutes and other customer-authorized integrations;
audits, simulations, dashboards and analytics;
customer support, monitoring and operational services.

Where Dayem Solutions processes Customer Personal Data on behalf of a business customer, Dayem Solutions acts as processor and may use subprocessors in accordance with the Data Processing Agreement.

Some services listed below may not be classic subprocessors for Customer Personal Data in all cases. Certain providers may act as independent controllers, payment providers, customer-authorized integrations or operational third-party services depending on the context.

2. Current Subprocessors and Service Providers

Provider	Purpose	Data Processed	Location / Transfer Notes
Hetzner	Hosting, server infrastructure and database hosting	Customer Data, application data, database data, server logs, technical metadata	Finland / European Union
Hostinger	Business email hosting	Business contact data, email communication, support communication, email metadata	Depending on provider setup; safeguards apply where required
Resend	Transactional and service-related email delivery	Email address, name, company, message content, delivery metadata, service notification data	Depending on provider setup; safeguards apply where required
PostHog EU Cloud	Product analytics, usage insights, debugging and product improvement	User or tenant identifiers, event data, page views, interactions, technical metadata and limited personal data where necessary for debugging or support	European Union cloud setup
HubSpot	CRM, lead management, sales communication and customer relationship management	Business contact data, demo request data, communication history, CRM notes, customer relationship data	Depending on provider setup; safeguards apply where required
Cal.com	Appointment scheduling, demo booking, onboarding and customer calls	Name, email address, company, meeting details, booking data and calendar-related metadata	Depending on provider setup; safeguards apply where required
Sentry	Error monitoring, debugging and application reliability	Error messages, stack traces, user or account identifiers, technical metadata, browser/device data and limited contextual data needed to fix errors	Depending on provider setup; safeguards apply where required
Laravel Nightwatch	Application monitoring, performance monitoring, debugging and reliability	Technical request data, performance data, application events, error context, user or tenant identifiers and operational metadata	Depending on provider setup; safeguards apply where required
Google Maps / Google Places APIs	Address autocomplete, address completion, geocoding, mapping and route-related functionality	Address search input, selected addresses, coordinates or location-related data, IP address and technical metadata	May involve international transfers; safeguards apply where required
Paddle	Payment processing, invoicing, tax handling, billing support, subscriptions, refunds and chargebacks	Billing data, subscription data, payment status, invoice data, tax data, refund and cancellation data	Paddle acts as Merchant of Record or reseller and may process payment-related data under its own terms and privacy documentation

3. Customer-Authorized Integrations

The following services are generally not subprocessors controlled by Dayem Solutions. They are third-party systems connected, authorized or controlled by the customer.

Provider	Role	Purpose	Data Processed
FieldRoutes	Customer-authorized third-party integration	Source and destination system for FieldRoutes data, operational sync and write-back functionality	Customer, service-location, appointment, subscription, employee, office, route, appointment-slot, service-type and skill data authorized by the customer

FieldRoutes is generally controlled by the customer. The customer is responsible for ensuring that FieldRoutes may be connected to PestRouting and that the relevant data may be processed by PestRouting.

4. Potential Future Service Providers

The following provider is not currently active for PestRouting but may be enabled in the future.

Provider	Potential Purpose	Potential Data Processed	Status
Cloudflare	Security, CDN, performance, DDoS protection and traffic routing	IP address, request metadata, security logs, traffic data and technical metadata	Not currently enabled; may be added in the future

If Cloudflare or another material provider is enabled and processes Customer Personal Data, this page will be updated accordingly.

5. Services Not Intended to Process Customer Data

The following tools may be used internally but are not intended to process Customer Personal Data from PestRouting customers:

Provider	Purpose	Customer Data Use
GitHub	Source code management and development workflow	Not intended for Customer Data, FieldRoutes data or production personal data

Developers and support personnel should avoid adding Customer Personal Data, FieldRoutes data, production logs or customer-specific personal data to internal development tools unless explicitly approved and protected by appropriate safeguards.

6. International Transfers

Some providers may process personal data outside the European Economic Area.

Where personal data is transferred outside the European Economic Area, Dayem Solutions relies on appropriate transfer mechanisms where required, such as:

an adequacy decision by the European Commission;
the EU-U.S. Data Privacy Framework where applicable;
Standard Contractual Clauses;
additional safeguards where required;
another lawful transfer mechanism under applicable data protection laws.

7. Subprocessor Change Notice

Dayem Solutions may update this list from time to time.

Where required under the Data Processing Agreement, Dayem Solutions will inform customers of intended material changes concerning the addition or replacement of subprocessors by:

updating this page;
providing in-app notice;
sending email notice; or
using another reasonable notice method.

Customers may object to a new subprocessor on reasonable data protection grounds within 30 days after notice, as described in the Data Processing Agreement.

8. Data Processing Agreement

Where Dayem Solutions processes Customer Personal Data on behalf of a customer, such processing is governed by the Data Processing Agreement unless another valid data processing agreement has been concluded.

The Data Processing Agreement describes:

the subject matter and duration of processing;
the nature and purpose of processing;
categories of personal data;
categories of data subjects;
customer instructions;
security measures;
subprocessors;
international transfers;
deletion and return of data;
audit and information rights.

9. Contact

For questions about subprocessors, third-party services or data protection, please contact: