Cashplannr
Solution · pick your layer
Budgeting
Target line on your real cashflow
→
Cashflow forecasting
Always know where your cash is going
→
Reporting
Your monthly report, automatic
→
Multi-entity
Cash and forecast per company, together
→
AI-powered
Cassy talks to your own numbers
→
Cashplannr vs. Excel
What a spreadsheet structurally can't do
→
Sectors · find your numbers
Real Estate Development
Per project, per phase · for developers
→
Construction
Site tracking through to payment
→
Staffing
DSO + payroll buffer + margin per contract
→
Other sectors
Cashplannr works sector-independent
→
For advisers Pricing About Contact
Log in Book a call →
Solution ▼
Solution · pick your layer
Budgeting
Target line on your real cashflow
Cashflow forecasting
Always know where your cash is going
Reporting
Your monthly report, automatic
Multi-entity
Cash and forecast per company, together
AI-powered
Cassy talks to your own numbers
Cashplannr vs. Excel
What a spreadsheet structurally can't do
Sectors ▼
Sectors · find your numbers
Real Estate Development
Per project, per phase · for developers
Construction
Site tracking through to payment
Staffing
DSO + payroll buffer + margin per contract
Other sectors
Cashplannr works sector-independent
For advisers Pricing About Contact Log in
Book a call →
Legal

Cashplannr Data Processing Agreement

Version of October 31, 2026 current

Translation. In case of discrepancy, the Dutch text prevails.

This data processing agreement implements Article 28 of Regulation (EU) 2016/679 (“the GDPR”). It forms part of every Agreement between Cashplannr BV, Zeitje 5, 9681 Maarkedal, CBE 0741.779.289 (“the Processor”), and the customer that signs the Order Form (“the Controller”). Capitalised terms have the meaning given in Cashplannr’s general terms and conditions.

Article 1. Application, subject matter and duration

1.1. This agreement applies as soon as the Controller signs an Order Form that refers to it. That signature, including electronically, constitutes written acceptance within the meaning of Article 28(9) GDPR.

1.2. The Processor processes personal data on behalf of the Controller in the provision of the Platform and the Implementation. If the Controller also contracts for Affiliated Companies, it acts on their behalf and is responsible for their instructions.

1.3. The nature and purpose of the processing, the categories of data subjects and of personal data, and the duration are set out in Annex A. The Order Form may supplement that description for the specific activity of the Controller.

1.4. This agreement applies for as long as the Agreement is in force and for as long as the Processor processes personal data for the Controller.

Article 2. Instructions

2.1. The Processor processes the personal data solely on documented instructions from the Controller. The Agreement, the settings that the Controller selects in the Platform and the use of the Platform by its Users constitute such instructions.

2.2. If the Processor is legally required to carry out processing outside those instructions, it informs the Controller in advance, unless that law prohibits this on important grounds of public interest.

2.3. The Processor immediately informs the Controller if, in its opinion, an instruction infringes the GDPR or other data protection rules.

2.4. The Processor does not process the personal data for its own purposes and does not use it to train language models. Fully anonymised and aggregated data, from which no data subject or customer is identifiable, is not personal data; the Processor may use it as provided in Article 9.3 of the general terms and conditions.

Article 3. Confidentiality

3.1. The Processor ensures that persons under its authority who have access to the personal data are bound by confidentiality and are given access only to the extent required by their task.

Article 4. Security

4.1. The Processor takes appropriate technical and organisational measures as referred to in Article 32 GDPR. Annex B describes the measures as at the date of this version.

4.2. The Processor may adapt the measures to the state of the art, provided that the level of security does not decrease.

4.3. The Controller is responsible for managing the accounts of its Users, for the choice of strong passwords and for activating two-factor authentication where it is available.

Article 5. Sub-processors

5.1. The Controller gives general authorisation to engage sub-processors. Annex C contains the sub-processors as at the date of this version. The Processor keeps the current list up to date and provides it on request.

5.2. The Processor gives notice of the addition or replacement of a sub-processor at least thirty days in advance. Within that period, the Controller may object, stating reasons, on data protection grounds. The Parties then seek a solution in good faith. The Processor may, among other things, propose to disable the relevant feature for the Controller or to use an alternative. If there is no solution after thirty days, the Controller may terminate the Agreement for the part that cannot be provided without that sub-processor, without compensation and with a pro rata refund of the fee paid in advance for that part.

5.3. The Processor imposes on each sub-processor, by contract, data protection obligations that are essentially equivalent to those of this agreement, as required by Article 28(4) GDPR. It remains liable to the Controller for the performance by the sub-processor as for its own acts, within the limits of Article 12.

Article 6. Transfers and language models

6.1. The database and the backups of the Platform are hosted within the European Economic Area (EEA).

6.2. Personal data is transferred outside the EEA, or accessed from outside the EEA, only by the sub-processors in Annex C, on the basis of an adequacy decision of the European Commission, including the EU-US Data Privacy Framework, or of the standard contractual clauses of the European Commission, supplemented by appropriate measures where necessary.

6.3. For AI Features, the Processor transmits only the data necessary for the task concerned. Names of counterparties, account numbers, email addresses and telephone numbers are pseudonymised beforehand: they are replaced by neutral labels. For as long as this is not possible for an AI Feature, that feature is disabled and is only activated at the express written request of the Controller.

6.4. For language models, the Processor uses the suppliers’ business services, under which submitted data is not used to train models. On request, it provides a description of the measures applied. At the Controller’s request, it disables the AI Features.

Article 7. Rights of data subjects

7.1. Taking into account the nature of the processing, the Processor provides reasonable assistance with requests from data subjects under Articles 15 to 22 GDPR.

7.2. If the Processor receives such a request directly, it does not respond to it itself but forwards it to the Controller without delay.

7.3. Assistance that requires significant effort and does not result from a failure by the Processor may be charged at the day rate of the Order Form, after a prior estimate.

Article 8. Personal data breaches

8.1. The Processor notifies the Controller of any personal data breach without undue delay, and in any event within forty-eight hours of becoming aware of it.

8.2. The notification contains, to the extent known, the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed, and a contact person. Missing information is provided in phases.

8.3. The Controller decides on notification to the supervisory authority and to the data subjects. The Processor provides reasonable assistance in this regard.

Article 9. Data protection impact assessment

9.1. Taking into account the nature of the processing and the information available to it, the Processor provides reasonable assistance with a data protection impact assessment and with a prior consultation of the supervisory authority. Article 7.3 applies mutatis mutandis.

Article 10. Information and audit

10.1. The Processor makes available the information necessary to demonstrate compliance with Article 28 GDPR, primarily through documentation, descriptions of measures and written answers to questions.

10.2. If that information is reasonably insufficient, the Controller may have an audit carried out no more than once per calendar year. It gives thirty days’ notice of this. The audit takes place during office hours, without unreasonably disrupting the Processor’s operations and without access to data of other customers. Following a personal data breach, an additional audit may take place.

10.3. The auditor is not a competitor of the Processor and is bound by confidentiality. The Controller bears the costs, including the Processor’s time at the day rate, unless the audit demonstrates a material failure by the Processor.

Article 11. Return and deletion

11.1. After the end of the Agreement, the Controller may request an export of the data in a commonly used structured format for a period of thirty days.

11.2. After that period, the Processor deletes the personal data from the production environment within ninety days. Data in backups is deleted in accordance with the backup rotation in Annex B and, until then, is no longer accessible for ordinary use.

11.3. The Processor may retain personal data for longer to the extent that a statutory retention obligation requires this, and solely for that purpose.

Article 12. Liability, order of precedence and law

12.1. Liability under this agreement is subject to the limitations of Article 15 of the general terms and conditions. Those limitations apply to all claims under this agreement and the rest of the Agreement together. They are without prejudice to the mandatory rights of data subjects under Article 82 GDPR.

12.2. In the event of conflict, this agreement takes precedence over the general terms and conditions as regards the processing of personal data, except for liability, for which Article 12.1 applies.

12.3. This agreement is governed by Belgian law. The courts that have jurisdiction under the general terms and conditions also have jurisdiction over disputes concerning this agreement.

Annex A. Description of the processing

Nature and purpose. Hosting and making available a platform for cash planning, budgeting and financial reporting per company, per project and for a group. This includes importing data from Third-Party Systems of the Controller, managing user accounts, the Implementation, support, AI Features in accordance with Article 6.3, backups, security and recovery.

Categories of data subjects.

  • Users of the Controller and of its external advisers.
  • Contact persons and representatives of customers, suppliers and other business relations, to the extent that they appear in the source data.
  • Natural persons who themselves act as a customer, supplier or other business relation.
  • Additional categories as stated in the Order Form.

Categories of personal data.

  • Of Users: name, email address, job title, login credentials in hashed form, login and activity logs.
  • Of business relations: name, address, enterprise and VAT number, contact details, payment terms.
  • Transaction and payment data: invoice and accounting entry data, amounts, due dates, account numbers and bank transactions.
  • Data that the Controller enters itself, such as descriptions and planned payments.
  • Additional categories as stated in the Order Form.

Special categories. No special categories of personal data within the meaning of Article 9 GDPR and no data relating to criminal convictions are processed. The Controller does not enter such data into the Platform.

Duration. The duration of the Agreement, followed by the export and deletion periods of Article 11.

Annex B. Technical and organisational measures

As at the date of this version.

AreaMeasure
HostingThe production environment runs at DigitalOcean in the Frankfurt data centre (Germany), within the EEA. The database runs on a separate server of the Processor in the same data centre, accessible only from the private network of the Platform and protected by a firewall. Connections to the database are encrypted via TLS, with verification of the server certificate.
TransportAll connections to the Platform are encrypted using TLS. Integrations with Third-Party Systems run over encrypted connections and via authorisation in those systems; the Processor does not store any passwords of the Controller for those systems.
Access to the infrastructureRestricted to the administrators designated by the Processor, currently the managing director, exclusively via SSH keys; password authentication is disabled.
Access within the PlatformRoles for administrator, user and partner. A User sees only the companies for which they have rights. Two-factor authentication is available.
Support accessEmployees and subcontractors of the Processor are given access to customer environments only to the extent required by their task and are contractually bound by confidentiality.
PasswordsPasswords of Users are stored in hashed form.
Backup and recoveryDaily automatic backups of the database, stored outside the database server and within the EEA, with tiered retention: all backups for seven days, then one per day up to sixteen days, one per week up to eight weeks, one per month up to four months and one per year up to two years. In addition, DigitalOcean takes a weekly copy of the entire database server, and point-in-time recovery within the last seven days is possible. Recovery is tested periodically.
LoggingLogins and relevant actions in the Platform are logged and retained for 180 days.
Data segregationThe data of each customer is logically segregated per environment.
Language modelsOnly the data necessary for a specific task is sent to the language model, after pseudonymisation in accordance with Article 6.3. Business APIs of the suppliers, without training on submitted data.
VulnerabilitiesOperating system security updates are applied automatically. Critical updates of application dependencies are applied as soon as possible after publication, others regularly. A first external penetration test is in preparation.
IncidentsSecurity incidents are recorded, assessed for impact and handled in accordance with Article 8.

Annex C. Sub-processors

As at the date of this version. Changes are communicated in accordance with Article 5.2.

Sub-processorServiceData locationTransfer mechanism
DigitalOcean LLCHosting of the application, database and backupsFrankfurt, Germany (EEA)Standard contractual clauses or EU-US Data Privacy Framework, for any access from the US
OpenAI Ireland Ltd. / OpenAI, L.L.C.Language models for suggestions, categorisation and the assistantEU and USStandard contractual clauses or EU-US Data Privacy Framework; data pseudonymised beforehand
Anthropic Ireland, Limited / Anthropic PBCLanguage models for suggestions, categorisation and the assistantEU and USStandard contractual clauses or EU-US Data Privacy Framework; data pseudonymised beforehand
Mailgun Technologies Inc.Sending of system and support messagesEUStandard contractual clauses, for any access from the US
Functional Software Inc. (Sentry)Error monitoringEUStandard contractual clauses, for any access from the US

All versions

  • October 31, 2026 current
Terms and conditions → Privacy policy →
Cashplannr

Proactive AI cash management for entrepreneurs and finance leads. Cashplannr watches your cashflow continuously and pings you the moment something shifts.

hello@cashplannr.com
Office
Cashplannr BV
Ottergemsesteenweg-Zuid 713
B-9000 Gent
Company number: BE 0741.779.289
Pitchdrive-backed
Product
  • Homepage
  • Budgeting
  • Cashflow forecasting
  • Reporting
  • Multi-entity
  • Cassy
  • Cashplannr vs. Excel
  • For Real Estate Development
  • For Construction
  • For Staffing
  • Other sectors
  • Pricing
  • Book a demo
Company
  • About us
  • For advisers
  • Contact
Resources
  • Integrations
  • Blog
  • Developers
  • API documentation
  • Privacy
  • Terms
  • Data processing agreement
  • Security
© 2026 Cashplannr BV · VAT BE 0741.779.289 · Hosted in EU
NL FR EN
Analytics cookies.We use Google Analytics to understand how the site is used. No advertising, no cross-site tracking. Do you accept?