Legal

Data Processing Agreement

This Data Processing Agreement (“DPA”) forms part of the Terms of Service or other applicable agreement between the customer (“Customer”, “Controller” or “you”) and Dayem Solutions UG (haftungsbeschränkt), Otto-Lilienthal-Straße 36, 71034 Böblingen, Germany (“Dayem Solutions”, “PestRouting”, “Processor”, “we”, “us” or “our”) regarding the use of PestRouting.

This DPA applies where Dayem Solutions processes personal data on behalf of the Customer in connection with PestRouting.

1. Parties and Roles

The Customer is the controller of Customer Personal Data.

Dayem Solutions acts as processor where it processes Customer Personal Data on behalf of the Customer for the purpose of providing PestRouting.

Where Dayem Solutions processes personal data for its own business purposes, such as website operation, sales, billing communication, customer relationship management, support management, security administration or legal compliance, Dayem Solutions acts as controller. Such processing is described in the Privacy Policy and is not governed by this DPA.

2. Definitions

“Agreement” means the Terms of Service, subscription agreement, order confirmation, checkout agreement or other agreement governing the Customer’s use of PestRouting.

“Customer Data” means all data provided to PestRouting by or on behalf of the Customer, including data imported from FieldRoutes or other customer-authorized integrations.

“Customer Personal Data” means any personal data contained in Customer Data and processed by Dayem Solutions on behalf of the Customer.

“Data Protection Laws” means all applicable data protection and privacy laws, including the EU General Data Protection Regulation (GDPR), the German Federal Data Protection Act (BDSG) and other applicable data protection laws.

“Subprocessor” means another processor engaged by Dayem Solutions to process Customer Personal Data on behalf of the Customer.

“Services” means PestRouting, including the website, application, routing optimization software, audits, simulations, dashboards, analytics, integrations, support and related services.

Capitalized terms not defined in this DPA have the meaning given to them in the Agreement.

3. Subject Matter and Duration of Processing

The subject matter of the processing is the provision of PestRouting to the Customer.

The processing includes importing, storing, analyzing, optimizing, displaying, syncing and, where enabled, writing back Customer Data from FieldRoutes or other customer-authorized systems.

The duration of the processing corresponds to the term of the Agreement and continues until Customer Personal Data is deleted, anonymized or returned in accordance with this DPA, the Agreement and applicable law.

4. Nature and Purpose of Processing

Dayem Solutions processes Customer Personal Data for the following purposes:

  • providing access to PestRouting;
  • importing and syncing data from FieldRoutes or other customer-authorized integrations;
  • analyzing appointment, route, technician, office, service-location and operational data;
  • generating routing recommendations, simulations and optimization outputs;
  • displaying dashboards, analytics and operational insights;
  • enabling route planning, scheduling analysis and related workflows;
  • writing data back to FieldRoutes or other connected systems where enabled and authorized by the Customer;
  • providing audits, demos, onboarding, implementation and support;
  • debugging, securing, monitoring and improving the Services;
  • maintaining integration credentials and technical system functionality;
  • complying with documented Customer instructions.

5. Categories of Personal Data

Customer Personal Data may include the following categories:

  • customer and service-location data, including customer names, service addresses, contact details and customer flags;
  • appointment data, including scheduled and completed appointments, dates, status and technician assignments;
  • subscription data, including recurring service agreements, service frequencies, contract details and cancellation reasons;
  • employee data, including technician and office-staff records, roles, active status and, where enabled, commission data;
  • office data, including branch and office locations;
  • route data, including planned and completed routes and assigned technicians;
  • appointment-slot or spot data, including time slots associated with routes;
  • service-type data, including service definitions and associated service durations;
  • skill data, including technician qualifications;
  • user account data, including names, email addresses, roles, permissions and activity logs;
  • integration data, including API keys, access tokens, refresh tokens, integration credentials, permission scopes and connection metadata;
  • support and error data, including support messages, screenshots, error reports, logs, user IDs, account IDs, technical metadata and debugging context.

The exact categories depend on the Customer’s configuration, enabled features, FieldRoutes permissions, integrations, API availability and future product development.

6. Categories of Data Subjects

Customer Personal Data may relate to:

  • the Customer’s employees;
  • technicians;
  • office staff;
  • administrative users;
  • dispatchers and route planners;
  • managers and business users;
  • the Customer’s customers and end customers;
  • service-location contacts;
  • other individuals whose data is contained in FieldRoutes or another customer-authorized system.

7. Customer Obligations

The Customer is responsible for:

  • determining the purposes and means of processing Customer Personal Data;
  • ensuring a valid legal basis for processing and sharing Customer Personal Data with PestRouting;
  • providing all legally required notices to data subjects;
  • ensuring that FieldRoutes or other third-party systems may be connected to PestRouting;
  • ensuring that Customer Personal Data is accurate, lawful and suitable for the intended processing;
  • ensuring that users are authorized and trained to use PestRouting appropriately;
  • reviewing and validating routing, scheduling and write-back outputs before operational use, unless automated execution is intentionally enabled;
  • responding to data subject requests where the Customer is the controller;
  • ensuring that no special categories of personal data are submitted unless expressly agreed in writing.

The Customer’s instructions to Dayem Solutions are documented in this DPA, the Agreement, the Customer’s configuration of the Services, integration settings, support requests and other written instructions accepted by Dayem Solutions.

8. Processor Obligations

Dayem Solutions shall:

  • process Customer Personal Data only on documented instructions from the Customer, unless required by Union or Member State law;
  • inform the Customer if, in our opinion, an instruction infringes Data Protection Laws, unless prohibited by law;
  • ensure that persons authorized to process Customer Personal Data are subject to confidentiality obligations;
  • implement appropriate technical and organizational measures as described in Annex 2;
  • use Subprocessors only in accordance with this DPA;
  • assist the Customer, taking into account the nature of the processing, with data subject requests where possible;
  • assist the Customer with compliance obligations relating to security, personal data breaches, data protection impact assessments and prior consultation, where applicable and reasonable;
  • delete, anonymize or return Customer Personal Data after the end of the Services as described in this DPA;
  • make available information reasonably necessary to demonstrate compliance with this DPA;
  • allow for and contribute to audits in accordance with this DPA.

9. Processing Instructions

Dayem Solutions will process Customer Personal Data only as necessary to provide, secure, maintain, support and improve PestRouting, and as otherwise instructed by the Customer.

The Customer authorizes Dayem Solutions to process Customer Personal Data for:

  • importing data from FieldRoutes or other customer-authorized integrations;
  • storing and displaying Customer Data in PestRouting;
  • performing optimization, simulation, analytics and routing calculations;
  • syncing data between PestRouting and connected systems;
  • writing data back to FieldRoutes or other connected systems where enabled;
  • providing support and troubleshooting;
  • monitoring application health and fixing errors;
  • maintaining security and preventing abuse;
  • using aggregated or anonymized data that no longer identifies individuals.

Dayem Solutions will not sell Customer Personal Data.

Dayem Solutions will not use identifiable Customer Personal Data for artificial intelligence model training.

As of the Last Updated date, Dayem Solutions does not process identifiable Customer Personal Data through artificial intelligence APIs or AI prompts.

10. Integration Credentials

Where necessary to provide the Services, Dayem Solutions may store API keys, access tokens, refresh tokens or similar credentials for FieldRoutes or other customer-authorized integrations.

Such credentials are processed only to provide the relevant integration, including data import, sync, processing and, where enabled, write-back functionality.

The Customer is responsible for ensuring that credentials are valid, authorized, appropriately scoped and provided by an authorized user.

The Customer may revoke or disable integration access through the relevant third-party system where available or by contacting support.

11. Writing Data Back to FieldRoutes and Other Systems

Depending on the Customer’s plan, settings and enabled features, PestRouting may write data back to FieldRoutes or other connected systems.

Such write-back actions may include:

  • new route or scheduling suggestions;
  • changed routes;
  • technician assignments;
  • appointment dates and times;
  • route, appointment or scheduling updates;
  • other changes supported by the connected system and enabled functionality.

The Customer authorizes Dayem Solutions to perform write-back actions where the Customer enables, approves, triggers, configures or otherwise authorizes such functionality.

The Customer remains responsible for reviewing, validating and authorizing operational changes and for the consequences of applying automated or manual changes in its own systems.

12. Confidentiality

Dayem Solutions shall ensure that persons authorized to process Customer Personal Data have committed themselves to confidentiality or are subject to an appropriate statutory obligation of confidentiality.

Access to Customer Personal Data is limited to persons who need such access for the provision, operation, support, security or maintenance of the Services.

13. Security Measures

Dayem Solutions shall implement appropriate technical and organizational measures designed to protect Customer Personal Data against accidental or unlawful destruction, loss, alteration, unauthorized disclosure or access.

The current technical and organizational measures are described in Annex 2.

The Customer acknowledges that technical and organizational measures may be updated from time to time, provided that the overall level of protection is not materially reduced.

14. Subprocessors

The Customer grants Dayem Solutions general authorization to engage Subprocessors for the provision, hosting, security, monitoring, support, analytics and improvement of PestRouting.

Current Subprocessors and relevant third-party service providers are listed in Annex 3 or on a Subprocessors page made available by Dayem Solutions.

Dayem Solutions shall impose data protection obligations on Subprocessors that are substantially equivalent to those set out in this DPA.

Dayem Solutions remains responsible for the performance of its Subprocessors to the extent required by Data Protection Laws.

Dayem Solutions will inform the Customer of intended material changes concerning the addition or replacement of Subprocessors by updating the Subprocessors page, providing in-app notice, email notice or another reasonable notice method.

The Customer may object to a new Subprocessor on reasonable data protection grounds within 30 days after notice. If the objection is reasonable, the parties will work in good faith to find a commercially reasonable solution. If no solution is available, the Customer may terminate the affected Services to the extent the new Subprocessor is required for those Services.

15. International Transfers

Dayem Solutions primarily hosts the core application and database infrastructure in the European Union.

Where Customer Personal Data is transferred outside the European Economic Area, Dayem Solutions will ensure that an appropriate transfer mechanism is in place where required by Data Protection Laws.

Such mechanisms may include:

  • 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 Data Protection Laws.

The Customer authorizes such transfers where necessary to provide the Services and where appropriate safeguards are in place.

16. Data Subject Requests

Taking into account the nature of the processing, Dayem Solutions shall reasonably assist the Customer by appropriate technical and organizational measures, insofar as possible, in fulfilling the Customer’s obligation to respond to requests from data subjects.

If Dayem Solutions receives a request directly from a data subject relating to Customer Personal Data, Dayem Solutions may redirect the data subject to the Customer or notify the Customer, unless prohibited by law.

Dayem Solutions will not independently respond to such requests except on documented instruction from the Customer or where required by law.

17. Personal Data Breach

Dayem Solutions shall notify the Customer without undue delay after becoming aware of a personal data breach affecting Customer Personal Data.

The notification will include, to the extent available:

  • a description of the nature of the breach;
  • the categories and approximate number of affected data subjects, where known;
  • the categories and approximate number of affected records, where known;
  • likely consequences of the breach, where known;
  • measures taken or proposed to address the breach;
  • information reasonably available to assist the Customer with its own notification obligations.

Dayem Solutions may provide information in phases as it becomes available.

A notification under this section does not constitute an admission of fault or liability.

18. Assistance with Compliance

Taking into account the nature of the processing and the information available to Dayem Solutions, Dayem Solutions shall reasonably assist the Customer with:

  • security obligations;
  • personal data breach assessments;
  • data protection impact assessments;
  • prior consultation with supervisory authorities where required;
  • documentation reasonably necessary to demonstrate compliance.

If such assistance requires significant effort beyond standard support, Dayem Solutions may charge reasonable fees unless the assistance is required due to a breach of this DPA by Dayem Solutions.

19. Deletion and Return of Data

After termination or expiry of the paid subscription, Customer Personal Data will generally be deleted or anonymized within 90 days after the end of the paid subscription term, unless longer retention is required by law or necessary for legitimate legal, billing, tax, security, compliance or dispute-resolution purposes.

The Customer may contact support@pestrouting.com to request data export or deletion assistance.

Data export or deletion assistance may depend on technical feasibility, security requirements, applicable law, the Customer’s plan and the available product functionality.

Backup copies, where applicable, may persist for a limited period and will be overwritten or deleted according to Dayem Solutions’ backup and retention procedures.

Dayem Solutions is not required to delete data that it is legally required to retain or that it processes as controller for legitimate legal, billing, tax, compliance or dispute-resolution purposes.

20. Audits and Information Rights

Dayem Solutions shall make available to the Customer information reasonably necessary to demonstrate compliance with this DPA.

The Customer may request reasonable documentation regarding Dayem Solutions’ technical and organizational measures, Subprocessors and processing activities.

Audits should be conducted primarily through documentation review, security questionnaires, certifications, policies or written responses.

On-site audits may be requested only where required by Data Protection Laws and where documentation review is insufficient.

Audits must be:

  • requested with reasonable prior notice;
  • conducted during normal business hours;
  • limited to once per calendar year unless a material breach or personal data breach justifies additional review;
  • conducted in a manner that does not unreasonably disrupt Dayem Solutions’ business operations or compromise the security or confidentiality of other customers;
  • subject to appropriate confidentiality obligations.

The Customer is responsible for its own audit costs. Dayem Solutions may charge reasonable fees for audit assistance that exceeds standard compliance documentation, unless the audit is required due to a breach of this DPA by Dayem Solutions.

21. Aggregated and Anonymized Data

Dayem Solutions may use aggregated, anonymized or otherwise non-identifying data to operate, analyze, improve, secure and develop PestRouting and related services.

Such data will not identify the Customer, the Customer’s customers, employees, technicians or other individuals.

Data that has been properly anonymized is not Customer Personal Data under this DPA.

22. Special Categories of Data

The Services are not intended for processing special categories of personal data, such as health data, biometric data, genetic data, religious beliefs, political opinions or similar sensitive data.

The Customer shall not submit special categories of personal data unless expressly agreed in writing and unless appropriate additional safeguards have been implemented.

23. Independent Controller Processing

Certain personal data may be processed by Dayem Solutions as controller, including:

  • website visitor data;
  • lead and demo request data;
  • customer relationship management data;
  • billing-related communication;
  • support management data;
  • business contact data;
  • legal and compliance records;
  • security administration data.

Such processing is governed by the Privacy Policy and is outside the scope of this DPA.

Paddle may act as Merchant of Record or reseller for payment transactions and may process payment, tax, invoice, refund and billing data under its own terms and privacy documentation.

FieldRoutes and other systems connected by the Customer are generally customer-authorized third-party integrations rather than Subprocessors controlled by Dayem Solutions.

24. Conflict

In the event of a conflict between this DPA and the Agreement regarding the processing of Customer Personal Data, this DPA shall prevail.

In all other matters, the Agreement remains applicable.

25. Liability

Liability between the parties is governed by the Agreement, unless mandatory Data Protection Laws provide otherwise.

Nothing in this DPA limits liability where such limitation is prohibited by applicable law.

26. Termination of this DPA

This DPA remains in effect for as long as Dayem Solutions processes Customer Personal Data on behalf of the Customer.

The obligations relating to confidentiality, deletion, audit documentation and protection of Customer Personal Data continue for as long as relevant Customer Personal Data remains in the possession or control of Dayem Solutions.

27. Contact

For privacy or data processing questions, please contact:

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

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

Annex 1: Details of Processing

Subject Matter

Provision of PestRouting as a B2B SaaS platform for routing optimization, scheduling analysis, operational planning, audits, simulations, dashboards, analytics, FieldRoutes integration and related support services.

Duration

For the duration of the Customer’s subscription or use of PestRouting, and thereafter until Customer Personal Data is deleted, anonymized or returned in accordance with the DPA, the Agreement and applicable law.

Nature of Processing

Collection, import, access, storage, hosting, organization, structuring, retrieval, consultation, analysis, calculation, optimization, simulation, display, synchronization, transmission, write-back, restriction, deletion and anonymization.

Purpose of Processing

Providing PestRouting, including route optimization, scheduling analysis, dashboards, audits, simulations, FieldRoutes sync, write-back functionality, technical support, debugging, monitoring, security and product operation.

Categories of Personal Data

Customer Personal Data may include:

  • customer names;
  • service addresses;
  • contact details;
  • customer flags;
  • appointment dates, times, status and assignments;
  • recurring service agreement data;
  • service frequency data;
  • contract details;
  • cancellation reasons;
  • technician and employee records;
  • roles and active status;
  • commission data where enabled;
  • office and branch data;
  • route data;
  • appointment-slot or spot data;
  • service-type data;
  • service-duration data;
  • skill and qualification data;
  • user names, emails, roles and permissions;
  • API keys, access tokens and refresh tokens;
  • technical logs, support data and error data.

Categories of Data Subjects

  • Customer’s employees;
  • technicians;
  • office staff;
  • dispatchers;
  • route planners;
  • managers;
  • administrative users;
  • Customer’s customers and end customers;
  • service-location contacts;
  • other individuals contained in Customer-authorized systems.

Processing Location

Core hosting and database infrastructure are currently hosted by Hetzner in Finland, within the European Union.

Other service providers may process data in the European Economic Area or in third countries subject to appropriate transfer mechanisms where required.

Annex 2: Technical and Organizational Measures

Dayem Solutions implements technical and organizational measures designed to protect Customer Personal Data. These measures may be updated over time.

1. Access Control

  • Access to production systems is restricted to authorized personnel.
  • Access is granted based on operational need.
  • User roles and permissions are used where available.
  • Access to Customer Personal Data is limited to personnel who need access for service provision, support, maintenance, security or legal purposes.
  • Credentials and integration tokens are handled with restricted access.

2. Authentication and Authorization

  • User accounts require authentication.
  • Administrative access is restricted.
  • Role-based or permission-based access controls are applied where available.
  • Customers are responsible for managing their own users, permissions and connected third-party accounts.

3. Transmission Security

  • Data is transmitted using TLS/SSL encryption where technically available.
  • API communication and application access are protected using standard transport encryption.
  • Customers should ensure that their own systems and endpoints use secure connections.

4. Hosting and Infrastructure Security

  • Core application and database infrastructure are hosted on Hetzner servers in Finland, within the European Union.
  • Infrastructure access is restricted to authorized personnel.
  • Server and application logs may be used for troubleshooting, monitoring and security.

5. Application Monitoring and Error Tracking

  • Sentry may be used for error monitoring and debugging.
  • Sentry PII collection settings are configured to reduce unnecessary personal data processing where possible.
  • Laravel Nightwatch may be used for application monitoring, performance monitoring and debugging.
  • Monitoring data is used to identify, investigate and fix errors and improve service reliability.

6. Product Analytics

  • PostHog EU Cloud may be used for product analytics, debugging and usage insights.
  • PostHog may process user, tenant, event and technical metadata where necessary for product operation, support, debugging or analytics.
  • Non-essential analytics are subject to consent where required.

7. Data Minimization

  • Dayem Solutions aims to process only data reasonably necessary to provide, secure, support and improve PestRouting.
  • Special categories of personal data are not intended to be processed.
  • Customers should avoid submitting unnecessary personal data.

8. Confidentiality

  • Personnel with access to Customer Personal Data are subject to confidentiality obligations.
  • Access is limited to persons who need it for service provision, support, maintenance, security or legal purposes.

9. Subprocessor Management

  • Subprocessors are selected based on operational need and suitable data protection safeguards.
  • Subprocessors processing Customer Personal Data are subject to contractual data protection obligations.
  • Subprocessor changes are handled in accordance with the DPA.

10. Incident Response

  • Dayem Solutions investigates suspected security incidents affecting Customer Personal Data.
  • Customers are notified without undue delay after Dayem Solutions becomes aware of a personal data breach affecting Customer Personal Data.
  • Incident information may be provided in phases as it becomes available.

11. Backup and Recovery

  • Dayem Solutions maintains or will implement backup and recovery procedures appropriate to the technical maturity and operational requirements of the Services.
  • Backup copies, where applicable, are retained only for a limited period and overwritten or deleted according to backup and retention procedures.
  • The Customer remains responsible for maintaining its own operational system of record, including FieldRoutes or other connected systems.

12. Data Retention and Deletion

  • Customer Personal Data is generally retained for the duration of the subscription.
  • After the end of the paid subscription term, Customer Personal Data is generally deleted or anonymized within 90 days unless longer retention is required by law or necessary for legitimate legal, billing, tax, security, compliance or dispute-resolution purposes.
  • Export or deletion assistance may be requested through support.

13. No AI Use with Identifiable Customer Data

  • Dayem Solutions does not currently process identifiable Customer Personal Data through AI APIs.
  • Dayem Solutions does not currently use identifiable Customer Personal Data in AI prompts.
  • Dayem Solutions does not use identifiable Customer Personal Data for AI model training.

Annex 3: Subprocessors and Relevant Third-Party Services

The following providers may be used to provide, operate, secure, monitor, support or improve PestRouting.

Hetzner

Purpose: Hosting, server infrastructure and database hosting.
Location: Finland / European Union.
Data: Customer Data, application data, database data, server logs and technical metadata.

Hostinger

Purpose: Email hosting and business email infrastructure.
Data: Business contact data, communication data, support communication and related metadata.

Resend

Purpose: Transactional and service-related email delivery.
Data: Email address, name, company, message content, delivery metadata and service notification data.

PostHog EU Cloud

Purpose: Product analytics, usage insights, debugging and product improvement.
Location: European Union cloud setup.
Data: User or tenant identifiers, event data, page views, interactions, technical metadata and limited personal data where necessary for debugging or support.

HubSpot

Purpose: CRM, lead management, customer relationship management and sales communication.
Data: Business contact data, demo request data, communication history, CRM notes and customer relationship data.
Note: HubSpot is generally used for sales and customer relationship processing, not for FieldRoutes operational data unless such data is intentionally included in support or customer communications.

Cal.com

Purpose: Appointment scheduling, demo booking, onboarding and customer calls.
Data: Name, email address, company, meeting details, booking data and calendar-related metadata.

Paddle

Purpose: Payment processing, invoicing, tax handling, billing support, subscriptions, refunds and chargebacks.
Data: Billing data, subscription data, payment status, invoice data, tax data and refund/cancellation data.
Note: Paddle acts as Merchant of Record or reseller for payment transactions and may process payment-related data under its own terms and privacy documentation.

Sentry

Purpose: Error monitoring, debugging and application reliability.
Data: Error messages, stack traces, user or account identifiers, technical metadata, browser/device data and limited contextual data needed to fix errors.
Note: PII collection settings are configured to reduce unnecessary personal data processing where possible.

Laravel Nightwatch

Purpose: Application monitoring, performance monitoring, debugging and reliability.
Data: Technical request data, performance data, application events, error context, user or tenant identifiers and operational metadata.

Google Maps / Google Places APIs

Purpose: Address autocomplete, address completion, geocoding, mapping and route-related functionality.
Data: Address search input, selected addresses, coordinates or location-related data, IP address and technical metadata.

Cloudflare

Purpose: Security, CDN, performance, DDoS protection and traffic routing, if enabled in the future.
Data: IP address, request metadata, security logs, traffic data and technical metadata.

FieldRoutes and Customer-Authorized Integrations

Purpose: Customer-authorized source and destination system for FieldRoutes data and operational sync.
Data: FieldRoutes data categories authorized by the Customer.
Note: FieldRoutes is generally a customer-authorized third-party integration rather than a Subprocessor controlled by Dayem Solutions.

Dayem Solutions may update this list from time to time in accordance with the Subprocessor clause in the DPA.

Annex 4: Customer Instructions

The Customer instructs Dayem Solutions to process Customer Personal Data as necessary to provide PestRouting, including:

  • importing data from FieldRoutes or other customer-authorized systems;
  • storing and displaying Customer Data;
  • performing routing analysis, optimization and simulations;
  • generating dashboards, analytics and recommendations;
  • syncing data with connected systems;
  • writing data back to FieldRoutes or other connected systems where enabled;
  • storing and using integration credentials;
  • providing support, onboarding and troubleshooting;
  • monitoring application performance and security;
  • fixing bugs and investigating errors;
  • deleting, anonymizing or returning data after termination according to the DPA;
  • using aggregated or anonymized data for product improvement.

Any additional instructions must be provided in writing and are subject to technical feasibility, legal permissibility and the Agreement.

Last updated: June 2026. See also our Privacy Policy and Terms of Service.