SAP Joule vs. sevdesk: data protection per plan

yes (the SAP Trust Center lists the 'Data Processing Agreement for Cloud Services, SAP Support and SAP Services', including GERMAN v.11-2024 (DACH) and ENGLISH v.10-2024, as a PDF; content not read, PDF retrieval blocked by bot protection (403))

yes (the SAP Trust Center lists the 'Data Processing Agreement for Cloud Services, SAP Support and SAP Services', including GERMAN v.11-2024 (DACH) and ENGLISH v.10-2024, as a PDF; content not read, PDF retrieval blocked by bot protection (403))

yes (data processing agreement under Art. 28(3) GDPR, publicly available as a PDF, version Offenburg 04.07.2025; according to the help centre it is concluded digitally and does not need to be returned; applies to all customers, as according to the terms sevdesk only contracts with businesses)

yes (data processing agreement under Art. 28(3) GDPR, publicly available as a PDF, version Offenburg 04.07.2025; according to the help centre it is concluded digitally and does not need to be returned; applies to all customers, as according to the terms sevdesk only contracts with businesses)

yes (data processing agreement under Art. 28(3) GDPR, publicly available as a PDF, version Offenburg 04.07.2025; according to the help centre it is concluded digitally and does not need to be returned; applies to all customers, as according to the terms sevdesk only contracts with businesses)

yes (data processing agreement under Art. 28(3) GDPR, publicly available as a PDF, version Offenburg 04.07.2025; according to the help centre it is concluded digitally and does not need to be returned; applies to all customers, as according to the terms sevdesk only contracts with businesses)

Responsible AI FAQ: customer data 'can be used to improve existing AI features and functionalities of the SAP cloud service to which the customer has subscribed' (subject to the contract and DPA); use for new AI features only under the 'product development schedule'; customers 'can monitor in which SAP solutions their data might be used and opt out in the SAP for Me interface'. No sharing with LLM/image model providers for training. Joule documentation: conversation logs are stored only with the consent of the global account admin (Joule Booster); analysis to improve Joule only after anonymisation; special categories of personal data are not processed for this purpose.

Responsible AI FAQ: customer data 'can be used to improve existing AI features and functionalities of the SAP cloud service to which the customer has subscribed' (subject to the contract and DPA); use for new AI features only under the 'product development schedule'; customers 'can monitor in which SAP solutions their data might be used and opt out in the SAP for Me interface'. No sharing with LLM/image model providers for training. Joule documentation: conversation logs are stored only with the consent of the global account admin (Joule Booster); analysis to improve Joule only after anonymisation; special categories of personal data are not processed for this purpose.

No explicit statement on training AI models with customer data. Help article "Belege erfassen" (recording receipts): the automatic receipt recognition is continuously learning and improves with every uploaded receipt. Receipt capture product page: booking category suggestions learn from the user's assignments. DPA section 3(6): operational data may be used anonymously and in aggregated form for evaluation purposes and, where applicable, for error analysis and further development of the products; section 2(2): statistical use only anonymised and aggregated. Whether this includes model training across customer accounts and whether an opt-out exists is not described.

No explicit statement on training AI models with customer data. Help article "Belege erfassen" (recording receipts): the automatic receipt recognition is continuously learning and improves with every uploaded receipt. Receipt capture product page: booking category suggestions learn from the user's assignments. DPA section 3(6): operational data may be used anonymously and in aggregated form for evaluation purposes and, where applicable, for error analysis and further development of the products; section 2(2): statistical use only anonymised and aggregated. Whether this includes model training across customer accounts and whether an opt-out exists is not described.

No explicit statement on training AI models with customer data. Help article "Belege erfassen" (recording receipts): the automatic receipt recognition is continuously learning and improves with every uploaded receipt. Receipt capture product page: booking category suggestions learn from the user's assignments. DPA section 3(6): operational data may be used anonymously and in aggregated form for evaluation purposes and, where applicable, for error analysis and further development of the products; section 2(2): statistical use only anonymised and aggregated. Whether this includes model training across customer accounts and whether an opt-out exists is not described.

No explicit statement on training AI models with customer data. Help article "Belege erfassen" (recording receipts): the automatic receipt recognition is continuously learning and improves with every uploaded receipt. Receipt capture product page: booking category suggestions learn from the user's assignments. DPA section 3(6): operational data may be used anonymously and in aggregated form for evaluation purposes and, where applicable, for error analysis and further development of the products; section 2(2): statistical use only anonymised and aggregated. Whether this includes model training across customer accounts and whether an opt-out exists is not described.

Joule documentation 'Data Centers Supported by Joule': data centres including Frankfurt (EU01 Converge Cloud, EU10 AWS, EU11 AWS 'EU access only', EU30 GCP) and Amsterdam (EU20 Microsoft Azure), each with 'Subprocessor Region' Europe; also USA, Brazil, UAE, India, Japan, Australia, Singapore. Joule can be consumed from a different data centre than the business application (cross consumption); according to SAP, assessing transfer restrictions is the customer's responsibility. Responsible AI page: with third-party foundation models, data are sent to the model provider for processing only and are not stored there; location of these model providers: not publicly documented.

Joule documentation 'Data Centers Supported by Joule': data centres including Frankfurt (EU01 Converge Cloud, EU10 AWS, EU11 AWS 'EU access only', EU30 GCP) and Amsterdam (EU20 Microsoft Azure), each with 'Subprocessor Region' Europe; also USA, Brazil, UAE, India, Japan, Australia, Singapore. Joule can be consumed from a different data centre than the business application (cross consumption); according to SAP, assessing transfer restrictions is the customer's responsibility. Responsible AI page: with third-party foundation models, data are sent to the model provider for processing only and are not stored there; location of these model providers: not publicly documented.

Sub-processor list (as of 10.04.2024): hosting with Amazon Web Services EMEA SARL, data hosted exclusively in Germany, access from third countries for support purposes conceivable; TOMs: AWS Frankfurt data centres; security page: hosting with AWS (no location stated); FAQ on the online banking page: receipts are stored 'in a certified data centre with server location in Germany' (translated). DPA section 2(3): processing in principle in the EU/EEA, outside only after prior notice and subject to Art. 44 et seq. GDPR. Where the AI features (receipt recognition, bank reconciliation, AI agent Sevi) are processed and whether external AI providers are used for them is not documented.

Sub-processor list (as of 10.04.2024): hosting with Amazon Web Services EMEA SARL, data hosted exclusively in Germany, access from third countries for support purposes conceivable; TOMs: AWS Frankfurt data centres; security page: hosting with AWS (no location stated); FAQ on the online banking page: receipts are stored 'in a certified data centre with server location in Germany' (translated). DPA section 2(3): processing in principle in the EU/EEA, outside only after prior notice and subject to Art. 44 et seq. GDPR. Where the AI features (receipt recognition, bank reconciliation, AI agent Sevi) are processed and whether external AI providers are used for them is not documented.

Sub-processor list (as of 10.04.2024): hosting with Amazon Web Services EMEA SARL, data hosted exclusively in Germany, access from third countries for support purposes conceivable; TOMs: AWS Frankfurt data centres; security page: hosting with AWS (no location stated); FAQ on the online banking page: receipts are stored 'in a certified data centre with server location in Germany' (translated). DPA section 2(3): processing in principle in the EU/EEA, outside only after prior notice and subject to Art. 44 et seq. GDPR. Where the AI features (receipt recognition, bank reconciliation, AI agent Sevi) are processed and whether external AI providers are used for them is not documented.

Sub-processor list (as of 10.04.2024): hosting with Amazon Web Services EMEA SARL, data hosted exclusively in Germany, access from third countries for support purposes conceivable; TOMs: AWS Frankfurt data centres; security page: hosting with AWS (no location stated); FAQ on the online banking page: receipts are stored 'in a certified data centre with server location in Germany' (translated). DPA section 2(3): processing in principle in the EU/EEA, outside only after prior notice and subject to Art. 44 et seq. GDPR. Where the AI features (receipt recognition, bank reconciliation, AI agent Sevi) are processed and whether external AI providers are used for them is not documented.

• Infrastructure according to the Joule data centre table: Amazon Web Services, Microsoft Azure, Google Cloud Platform, Converge Cloud (depending on the selected data centre)

• Infrastructure according to the Joule data centre table: Amazon Web Services, Microsoft Azure, Google Cloud Platform, Converge Cloud (depending on the selected data centre)

• Amazon Web Services EMEA SARL, German branch (external data centre, hosting; data only in Germany)
• EMAILBRIEF GmbH, Mutterstadt (sending invoices by post)
• Termitel GmbH, Ettlingen (handling customer phone enquiries)
• Twilio Inc. (SendGrid, Inc.), Dublin (sending emails; EU-U.S. Data Privacy Framework and standard contractual clauses)
• AI-specific sub-processors: not publicly documented (list as of 10.04.2024 names none)

• Amazon Web Services EMEA SARL, German branch (external data centre, hosting; data only in Germany)
• EMAILBRIEF GmbH, Mutterstadt (sending invoices by post)
• Termitel GmbH, Ettlingen (handling customer phone enquiries)
• Twilio Inc. (SendGrid, Inc.), Dublin (sending emails; EU-U.S. Data Privacy Framework and standard contractual clauses)
• AI-specific sub-processors: not publicly documented (list as of 10.04.2024 names none)

• Amazon Web Services EMEA SARL, German branch (external data centre, hosting; data only in Germany)
• EMAILBRIEF GmbH, Mutterstadt (sending invoices by post)
• Termitel GmbH, Ettlingen (handling customer phone enquiries)
• Twilio Inc. (SendGrid, Inc.), Dublin (sending emails; EU-U.S. Data Privacy Framework and standard contractual clauses)
• AI-specific sub-processors: not publicly documented (list as of 10.04.2024 names none)

• Amazon Web Services EMEA SARL, German branch (external data centre, hosting; data only in Germany)
• EMAILBRIEF GmbH, Mutterstadt (sending invoices by post)
• Termitel GmbH, Ettlingen (handling customer phone enquiries)
• Twilio Inc. (SendGrid, Inc.), Dublin (sending emails; EU-U.S. Data Privacy Framework and standard contractual clauses)
• AI-specific sub-processors: not publicly documented (list as of 10.04.2024 names none)

Included in the price of the SAP cloud subscription; no surcharge according to the pricing page (subscription prices not recorded)

AI surcharge: AI Units as a shared consumption currency (SKU 8019164), purchased annually, expire after 12 months; price per AI Unit: not publicly documented (price list via sales); Custom-built AI (Joule Studio) free of charge in operation until the end of 2026 (pricing page)

EUR 0 ("permanently free", no credit card); according to the help centre applied automatically after the 14-day trial, unlimited in time; no add-ons bookable, limited support.

List price EUR 11.90 per month billed monthly, EUR 9.90 per month for 12 months (billed annually), EUR 8.90 per month for 24 months, each plus VAT; 1 user, additional users via add-on at EUR 5.90 per month. On the retrieval date the pricing page also showed promotional prices ("up to 50% discount"); according to terms section 1.5, discounts only apply to first bookings by new customers for the minimum term, renewals at regular prices.

List price EUR 25.90 per month billed monthly, EUR 22.90 per month for 12 months, EUR 19.90 per month for 24 months, each plus VAT; 1 user, more via add-on at EUR 5.90 per month. On the retrieval date the pricing page also showed promotional prices ("up to 50% discount"); according to terms section 1.5, discounts only apply to first bookings by new customers for the minimum term, renewals at regular prices.

List price EUR 34.90 per month billed monthly, EUR 30.90 per month for 12 months, EUR 27.90 per month for 24 months, each plus VAT; 1 user, more via add-on at EUR 5.90 per month. On the retrieval date the pricing page also showed promotional prices ("up to 50% discount"); according to terms section 1.5, discounts only apply to first bookings by new customers for the minimum term, renewals at regular prices.

yes (Joule Base and Embedded AI at no additional cost; 'no AI Units required'; availability varies by SAP solution)

yes (agents and extended AI services based on consumption; SAP-delivered agents 0.02 AI Units per agent action; Joule for Consultants 35 AI Units per user per month)

no (pricing page: the free plan covers 3 (e-)invoices per month, contacts, products and support material; AI-supported receipt capture and the AI agent Sevi are only listed for paid plans)

yes (AI agent Sevi in support, according to the pricing page in all three paid plans; AI-supported receipt capture and online banking reconciliation only from the Buchhaltung plan)

yes (AI-supported receipt capture reading date, amount, receipt number and supplier and suggesting the booking category; AI-supported matching of bank payments to invoices and receipts; AI agent Sevi; suggestions must be reviewed and confirmed by the user)

yes (all AI features from Buchhaltung; additionally cost centres, management accounts (BWA) and REST API)