Data Processing Agreement

Data Processing Agreement

Pre-completed data processing agreement under Article 28 of the GDPR between the Customer and Workflows by AI AB, trading under the WiseGent brand.

Last updated: 22 May 2026

Data Processing Agreement - WiseGent

Parties

Controller

The Customer under the main agreement, subscription, quotation, order, order form, or customer account governing the use of WiseGent.

The Customer’s company registration number, address, and contact person are the details provided in the main agreement, customer account, or written communications with WiseGent.

Processor

Workflows by AI AB, trading under the WiseGent brand

Company registration number: 556930-9387

Address: Tegelbrukets väg 41, 195 59 Märsta, Sweden

Data protection contact: [email protected]

The Controller and Processor are referred to below collectively as the “Parties” and individually as a “Party”. This Agreement takes effect on the date the Customer electronically accepts the Main Agreement and this Data Processing Agreement, for example through registration, an order, agreed onboarding, or other documented acceptance.

1. Background and purpose

The Parties have entered into, or intend to enter into, an agreement under which the Supplier provides WiseGent, a cloud-based SaaS platform for cleaning and service companies (the “Main Agreement”).

Under the Main Agreement, the Supplier processes personal data on behalf of the Customer. This Data Processing Agreement governs that processing and is intended to meet the requirements of the GDPR, in particular Article 28, and other applicable data protection legislation.

If the Main Agreement conflicts with this Data Processing Agreement, this Data Processing Agreement prevails with respect to the processing of personal data on behalf of the Customer.

2. Definitions

Terms used in this Data Processing Agreement that are defined in the GDPR have the same meaning as in the GDPR, unless expressly stated otherwise.

“Sub-processor” means a third party engaged by the Supplier to process personal data on behalf of the Customer.

“Applicable Data Protection Legislation” means the GDPR, the Swedish Act (2018:218) containing supplementary provisions to the EU General Data Protection Regulation, and regulations and decisions issued by a competent supervisory authority.

3. Subject matter, duration, and instructions

The subject matter, nature and purpose of the processing, types of personal data, and categories of data subjects are set out in Schedule 1.

This Data Processing Agreement remains in force for as long as the Supplier processes personal data on behalf of the Customer under the Main Agreement.

The Supplier may process personal data only in accordance with the Customer’s documented instructions, this Data Processing Agreement and its schedules, and written updates agreed by the Parties.

If the Supplier considers an instruction to be contrary to Applicable Data Protection Legislation, it shall inform the Customer without undue delay.

If EU or national law requires the Supplier to process personal data other than as instructed by the Customer, the Supplier shall inform the Customer of that requirement before processing, unless the law prohibits such notice.

4. Processor obligations

The Supplier shall:

  • process personal data only in accordance with the Customer’s documented instructions;
  • ensure that persons authorised to process personal data are bound by an appropriate confidentiality obligation;
  • implement appropriate technical and organisational security measures under Article 32 of the GDPR, as described in Schedule 2;
  • comply with the conditions for engaging Sub-processors under Clause 6;
  • assist the Customer, taking into account the nature of the processing, in responding to data subject rights under the GDPR;
  • assist the Customer with its obligations under Articles 32–36 of the GDPR to the extent the Supplier has relevant information;
  • at the Customer’s choice, delete or return personal data after the end of processing as set out in Clause 12;
  • provide information needed to demonstrate compliance with Article 28 of the GDPR and contribute to audits under Clause 9.

5. Confidentiality

The Supplier shall ensure that employees, consultants, and other persons processing personal data under its authority are bound by contractual confidentiality or a statutory duty of secrecy.

The confidentiality obligation continues after this Data Processing Agreement ends.

6. Sub-processors

The Customer gives the Supplier general written authorisation to engage the Sub-processors listed in Schedule 2, to the extent the relevant feature or integration is used for the Customer.

The Supplier shall inform the Customer of planned additions or replacements of Sub-processors at least thirty (30) days in advance, allowing the Customer to object.

If the Customer has reasonable grounds to object, the Parties shall work together to find a commercially reasonable solution. If no solution is reached, the Customer may terminate the part of the Main Agreement affected by that Sub-processor.

The Supplier shall impose on the Sub-processor, by written agreement, data protection obligations equivalent to those in this Data Processing Agreement.

The Supplier remains liable to the Customer for the Sub-processor’s processing in accordance with Article 28(4) of the GDPR.

7. Security of processing

The Supplier shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk. The measures are described at a high level in Schedule 2 and shall be adapted to the nature of the service, available technology, and actual risk.

Security measures that depend on third-party capabilities, such as encryption, logging, strong authentication, or physical security, are applied to the extent they are available and controllable in the relevant system or provider environment.

8. Personal data breaches

The Supplier shall notify the Customer without undue delay after becoming aware of a personal data breach involving the Customer’s personal data. Where practicable, notification will normally be made within twenty-four (24) hours after the breach is confirmed.

To the extent available, the notice shall describe the nature of the breach, the categories and approximate number of data subjects and personal data records concerned, likely consequences, measures taken or proposed, and a contact point for further information.

If all information cannot be provided at once, it shall be provided in phases without undue delay.

The Supplier shall assist the Customer with information reasonably needed to comply with Articles 33–34 of the GDPR.

9. Review, audit, and inspection

At the Customer’s request, the Supplier shall provide information necessary to demonstrate compliance with Article 28 of the GDPR and this Data Processing Agreement.

Audits shall be notified in writing at least thirty (30) days in advance, take place during normal business hours, and be conducted in a way that does not unreasonably disrupt the Supplier’s operations or compromise other customers’ confidentiality or security.

The Customer shall bear its own costs. The Supplier is entitled to reasonable compensation for its time and expenses, unless the audit is prompted by a personal data breach caused by the Supplier.

The Customer may accept relevant third-party certifications, security documentation, or summaries from the Supplier instead of an on-site audit, if they provide sufficient insight into the processing concerned.

10. Transfers to third countries

Personal data may be transferred outside the EU/EEA only in accordance with Chapter V of the GDPR, for example on the basis of an adequacy decision, the European Commission’s Standard Contractual Clauses, or another lawful transfer mechanism with any necessary supplementary measures.

The Supplier aims to keep primary operations and storage within the EU/EEA. Any processing involving third countries, such as support, logging, email delivery, or global cloud services, is described in Schedule 2.

11. Assistance to the Customer

Taking into account the nature of the processing and the information available, the Supplier shall assist the Customer with:

  • data subject requests under Articles 12–22 of the GDPR;
  • security of processing under Article 32 of the GDPR;
  • handling personal data breaches, including notifications under Article 33 and communications to data subjects under Article 34 of the GDPR;
  • data protection impact assessments under Article 35 of the GDPR;
  • prior consultation with a supervisory authority under Article 36 of the GDPR, where relevant.

The Supplier is entitled to reasonable compensation for assistance beyond its mandatory obligations under Article 28 of the GDPR, unless the assistance is required because of the Supplier’s breach of contract.

12. Return and deletion

When this Data Processing Agreement ends, the Supplier shall, at the Customer’s written choice, return or delete personal data processed on the Customer’s behalf.

Active customer data shall be deleted or returned within thirty (30) days after this Data Processing Agreement ends, unless otherwise agreed in writing or retention is required by law.

Personal data in backups, technical logs, or audit logs is deleted through the normal rotation and retention cycles. Such copies are not actively used for other purposes and are protected against unauthorised access. Activity logs are normally deleted after 180 days, and backups may be retained for up to twenty-four (24) months under the backup cycle.

At the Customer’s request, the Supplier shall confirm in writing that deletion has been completed in accordance with this Clause.

13. Liability and compensation

The Parties’ liability and obligations to pay compensation under this Data Processing Agreement are governed by the Main Agreement and Applicable Data Protection Legislation.

Where the Main Agreement does not address the matter, Article 82 of the GDPR and the general principles of Swedish law apply.

Each Party is responsible for administrative fines imposed on it by a supervisory authority, unless mandatory law provides otherwise.

14. Amendments and supplements

Amendments and supplements to this Data Processing Agreement must be made in writing to be binding.

If legislation, practice, or the service’s actual processing changes, the Parties shall in good faith amend this Data Processing Agreement to the extent necessary.

15. Governing law and disputes

This Data Processing Agreement is governed by Swedish law, excluding its conflict-of-law rules.

Disputes arising out of this Data Processing Agreement shall be resolved under the dispute resolution procedure set out in the Main Agreement. If the Main Agreement has no such provision, the dispute shall be decided by the Swedish general courts, with Stockholm District Court as the court of first instance.

16. Signatures and acceptance

This Data Processing Agreement forms an integral part of the Main Agreement and is accepted electronically through registration, an order, agreed onboarding, or other documented acceptance. The Supplier may retain records of acceptance, including the document version, time of acceptance, document URL, document hash, IP address, user agent, and relevant account information. If the Parties have signed a separate version of this Data Processing Agreement, that version applies to the extent it expressly differs from this published version.

Schedule 1 – Instructions for processing personal data

A. Subject matter of the processing

The Supplier’s provision, operation, support, and maintenance of WiseGent, a cloud-based SaaS platform for cleaning and service companies. The service includes, among other things, customer and staff administration, scheduling, work orders, mobile apps, time reporting, GPS-based clock-in and clock-out, key and address management, invoicing, RUT/ROT documentation, communications, and relevant integrations.

B. Duration of the processing

Processing takes place during the term of the Main Agreement and for any additional period required for support, export, return, deletion, logging, backup rotation, or statutory retention under this Data Processing Agreement.

C. Nature of the processing

Processing may include collecting, recording, organising, structuring, storing, adapting, altering, retrieving, consulting, using, exporting, transferring, restricting, deleting, and destroying personal data to the extent required to provide the Service.

D. Purposes of the processing

  • provide, operate, maintain, and support WiseGent;
  • manage users, permissions, authentication, and the customer portal/mobile apps;
  • administer customers, employees, jobs, work orders, schedules, and history;
  • enable time reporting, GPS-based clock-in and clock-out, deviation management, and route/travel-time calculations;
  • manage invoicing, quotes, payments, RUT/ROT documentation, direct debit, and financial integrations;
  • send transactional emails, SMS messages, push notifications, and chat messages according to the Customer’s configuration;
  • perform technical troubleshooting, security logging, incident management, backups, and system monitoring;
  • maintain and further develop the Service within the Customer’s instructions; general product development shall use aggregated or de-identified data where personal data is not necessary.

Generative AI services, including OpenAI or comparable AI providers, are not included in the standard instructions for processing the Customer’s personal data. Such features may be enabled for the Customer’s personal data only following separate written instructions or a separate schedule specifying the provider, data categories, transfers, and safeguards.

E. Types of personal data

  • identity and contact details: name, email address, phone number, job title, organisation, and customer number;
  • account and authentication data: usernames, hashed passwords, API tokens, session identifiers, passkeys, and one-time codes;
  • customer and household data: personal/company registration numbers, billing addresses, RUT/ROT documentation, invoice and payment history, direct debit references, and language information;
  • employee data: employment-related information, personal identity numbers, contact details, working hours, absences, payroll-related information, bank/clearing numbers, permissions, and work reports;
  • address and location data: service addresses, geographic coordinates, geofences, GPS-based check-in/check-out, travel-time and route data;
  • security and access data: key details and history, door codes, alarm codes, and instructions;
  • communications and content data: chat messages, email/SMS/push content, free-text fields, comments, notes, work orders, tasks, and support tickets;
  • operational data: bookings, jobs, damage reports, deviations, photos, files, attachments, reports, statistics, and logs;
  • technical data: IP address, user agent, device identifiers, push tokens, operating system, browser information, activity logs, and error/performance logs.

Special categories of personal data under Article 9 of the GDPR and personal data relating to criminal convictions and offences under Article 10 are not intended to be processed through the standard service. The Customer must not enter such data in free-text fields, files, or messages without a separate written agreement and instructions.

Swedish personal identity numbers and coordination numbers may be processed where needed for purposes such as RUT/ROT, payroll administration, identification, or invoicing under the Customer’s instructions.

F. Categories of data subjects

  • the Customer’s employees, consultants, managers, administrators, and other authorised users;
  • the Customer’s customers and end customers, household members, and persons eligible for RUT/ROT;
  • contact persons at the Customer’s customers, suppliers, and business partners;
  • relatives or contacts recorded as emergency or other contact persons;
  • prospects and individuals who submit booking or contact forms;
  • individuals mentioned in free text, chat, email, files, images, work orders, or incident/damage reports.

G. Geographic location of processing

Primary operations and storage take place within the EU/EEA, with Sweden as the principal operating and storage location where this follows from the selected hosting and storage environment. Sub-processors and any third-country processing are listed in Schedule 2.

H. Customer’s obligations and rights

As Controller, the Customer is responsible for ensuring that processing has a lawful basis, data subjects are informed, instructions to the Supplier are lawful and documented, and information entered into the Service is relevant and necessary for the Customer’s purposes.

The Customer may issue documented instructions, request assistance, receive information about Sub-processors, object to new Sub-processors, and audit the Supplier’s compliance with this Data Processing Agreement.

Schedule 2 – Technical and organisational security measures and approved Sub-processors

1. Technical and organisational security measures

Access control and permissions

  • Role-based access and permissions are used in the Service to limit access according to job responsibilities.
  • Individual accounts are used for administrative access where the Supplier controls account management.
  • Permissions must be removed or adjusted when employment, an assignment, or the need for access ends.

Authentication and account security

  • Passwords are stored as hashes and are not exposed in plain text in the application.
  • Strong authentication, passkeys, or MFA are used for critical systems where supported and enabled.
  • Sessions and tokens are managed for web, API, and mobile access.

Encryption and communications

  • External communications normally use TLS/HTTPS.
  • Particularly sensitive fields, such as door and alarm codes, may be protected with application-level encryption where supported by the Service.
  • Backups and stored data are protected using the encryption and access controls provided by the selected operating or storage environment.

Logging, monitoring, and traceability

  • The system logs relevant access, change, error, and security events for troubleshooting, operations, and incident management.
  • Logs are protected against unauthorised access and deleted under established rotation or retention procedures.
  • Error and performance monitoring may be used to detect operational issues and incidents.

Backups and continuity

  • Production data is backed up regularly in accordance with the operating environment’s backup strategy.
  • Where possible in the selected infrastructure, backups are stored separately from the active production environment.
  • Recovery and continuity procedures are tested or verified at a scale and frequency reasonable in relation to the risk.

Development and changes

  • Code changes are reviewed and handled under the established development process before release to production.
  • Development, test, and production environments are kept separate to the extent practically and technically possible.
  • Dependencies and third-party components are updated and reviewed as part of ongoing maintenance.

Personnel and incident management

  • Staff and consultants who process personal data are bound by confidentiality obligations.
  • The Supplier has procedures to identify, classify, manage, and report suspected personal data breaches.
  • Lessons from incidents and service disruptions are used to improve procedures and safeguards.

Data minimisation and supplier management

  • The Service shall process only the personal data needed for the agreed functionality and the Customer’s instructions.
  • Sub-processors are reviewed before processing personal data and are subject to written data protection agreements.
  • Transfers outside the EU/EEA must rely on a lawful transfer mechanism and supplementary measures where required.

2. Approved Sub-processors

The Customer approves the following Sub-processors to the extent the relevant feature, integration, or operational component is used for the Customer. The Supplier shall make an up-to-date list available and notify the Customer of changes under Clause 6 of this Data Processing Agreement.

Sub-processor Service / purpose Data categories Location and transfers
Vultr / The Constant Company, LLC Hosting virtual servers, databases, and storage for the WiseGent platform when the selected infrastructure is used. Customer data, user data, files, and technical logs. Primarily the EU/Stockholm region when selected. Support may be global; transfers are governed by the DPA and SCCs where required.
Amazon Web Services EMEA SARL / AWS Object storage (S3), backups, related cloud services, and any email or infrastructure components where AWS is used. Files, backup copies, technical metadata, and logs. EU regions, primarily Stockholm and/or Ireland depending on configuration. The AWS DPA and SCCs apply to transfers to third countries.
Postmark / ActiveCampaign, LLC Transactional email, delivery status, and error handling. Name, email address, message content, delivery metadata, and technical logs. EU/US, depending on service operations and support. Transfers outside the EEA are governed by the provider’s DPA and SCCs.
BulkGate s.r.o. SMS delivery and delivery status for notifications and communications. Phone number, message content, and delivery metadata. EEA/Czech Republic and carrier networks used to deliver SMS. Transfers are governed by a DPA where applicable.
Twilio Ireland Limited / Twilio Inc. SMS or telephony when Twilio is enabled for the Customer or in the relevant environment. Phone number, message content, call and delivery metadata, and technical logs. EU/US and global telecommunications networks. The Twilio DPA and SCCs apply to transfers to third countries.
Expo / 650 Industries, Inc. Push notifications to mobile apps. Push token, device metadata, and notification content. US/global infrastructure. Transfers are governed by the provider’s terms/DPA and SCCs where applicable.
Google Ireland Limited / Google LLC Google sign-in, maps, geocoding, distance calculations, and related Google Maps Platform services when these features are used. Name/email during OAuth, addresses, coordinates, routes, IP address, and technical metadata. EEA/US/global infrastructure. Google’s Data Processing Terms and SCCs apply to transfers to third countries.
Meta Platforms Ireland Limited / Meta Platforms, Inc. Facebook/Meta sign-in and public website components such as the pixel, only when enabled and applicable. OAuth identifiers, name/email depending on the sign-in method, cookie/pixel metadata, and technical events. EEA/US/global infrastructure. Meta’s terms and SCCs apply to transfers to third countries; marketing cookies require a separate legal basis/consent.
Cloudflare, Inc. Bot and spam protection through Turnstile, as well as network/security features where used. IP address, browser/device metadata, and verification metadata. EEA/US/global infrastructure. The Cloudflare DPA and SCCs apply to transfers to third countries.
Fortnox AB Accounting, invoicing, customer records, RUT/ROT, and financial administration when the integration is used. Customer and invoice details, personal identity numbers for RUT/ROT, addresses, payment status, and financial metadata. Sweden/EEA according to Fortnox operations. Transfers to third countries only under Fortnox’s terms/DPA.
Sentry / Functional Software, Inc. Error reporting, performance monitoring, and technical incident logs. Technical logs, user identifiers, IP address, browser/device data, and error context. Personal data in error reports must be minimised. EU/US, depending on project configuration. The DPA and SCCs apply to transfers to third countries.
Crisp IM SAS Chat, support communications, and customer conversations related to support when the Crisp widget or integration is used. Name, email address, chat messages, user identifiers, technical metadata, and any attachments sent in chat. EEA/France and support/infrastructure under Crisp’s terms. A DPA applies where Crisp acts as a processor.
WiseGent-operated PDF rendering service (pdf.wisegent.se) Generating PDFs from invoices, time reports, and similar HTML materials on WiseGent’s own subdomain. Invoice source data, time reports, customer/work details, and technical rendering metadata. Operated by WiseGent and covered by WiseGent’s infrastructure providers listed in this schedule. No transfer to a third country may take place without a valid transfer mechanism.
OpenStreetMap Foundation / tile.openstreetmap.org Map tiles in views displaying a map or geographic location when that feature is used. IP address, browser metadata, and map/tile requests associated with the area displayed. United Kingdom/EEA/global delivery through a public tile service. The Customer should avoid unnecessary exposure of sensitive addresses in external map views.

Generative AI providers, including OpenAI or equivalent providers, are not approved Sub-processors under these standard instructions. If AI features are to process the Customer’s personal data, the Parties must first agree on separate written instructions or a separate schedule.

3. Transfers to third countries

As a general rule, primary operations and storage take place within the EU/EEA. For some global providers, support, error reporting, email delivery, SMS, push notifications, or technical metadata may involve transfers outside the EU/EEA. Such transfers must be supported by a valid transfer mechanism under Chapter V of the GDPR, normally the European Commission’s Standard Contractual Clauses, together with relevant supplementary technical, organisational, and contractual measures.

4. Data protection contacts

Supplier contact

[email protected]

Customer contact

The Customer’s administrator, agreed contact person, or other contact designated by the Customer in WiseGent, the Main Agreement, or written communications with the Supplier.