Data processing agreement
Version 2026-11-10 · Last updated: 10 November 2026
1. Parties and purpose
This Data Processing Agreement is between:
- the Customer: the business named in the BERRYSAND order and account, represented by the person who accepted the service; and
- the Processor: BERRYSAND, Paxlaan 10, 2131 PZ Hoofddorp, the Netherlands, support@berrysand.com.
The Customer is the controller of the personal data described in Schedule 1. BERRYSAND processes that data on the Customer’s behalf to provide the website, communication and related services.
This agreement is part of the service agreement and applies as long as BERRYSAND or one of its subprocessors holds personal data on the Customer’s behalf, including any deletion period. For the processing it covers, this agreement takes priority over the General Terms. Mandatory law takes priority over this agreement.
2. Scope
“Customer Personal Data” means personal data processed on the Customer’s instructions within the activities in Schedule 1. Terms such as “controller”, “processor” and “personal data breach” have the meaning given in the GDPR.
BERRYSAND’s own account administration, billing, tax records and legal compliance are covered by its Privacy Policy, not by this agreement.
Not every organisation involved in the service is a subprocessor. Domain registries, payment organisations and app stores, for example, have their own legal role.
If the Customer is itself a processor for another controller, it must tell BERRYSAND before placing that controller’s personal data in the service.
3. Instructions
The service agreement, this agreement, the saved settings in the Customer’s account and the actions the Customer takes in the service are the Customer’s documented instructions. These include publishing, handling messages and booking requests, approving reviews, notification choices and the agreed deletion rules.
BERRYSAND processes Customer Personal Data only on these instructions, including for transfers outside the European Economic Area, unless the law requires otherwise. Where allowed, BERRYSAND tells the Customer about such a legal requirement first.
BERRYSAND tells the Customer straight away if it believes an instruction breaks data protection law, and may pause that instruction until the matter is resolved. BERRYSAND never uses Customer Personal Data for its own advertising or other unrelated purposes.
Further instructions can be sent to support@berrysand.com. If an instruction requires work outside the agreed service, the parties first agree whether it is possible and any reasonable cost. Costs are never used to block a mandatory obligation.
4. Customer responsibilities
The Customer decides the purposes of the processing and must have a legal ground for it. The Customer gives visitors correct privacy information, obtains any required consent, gives lawful instructions and answers requests from individuals.
The Customer reviews the standard privacy page and cookie banner before publishing and adapts them where needed. Adding an advertising tag is not consent from visitors.
The Customer collects only what its business needs, avoids unnecessary sensitive information, approves reviews responsibly and protects its login details. The service is not designed for medical records or other special categories of data.
5. Confidentiality and access
BERRYSAND limits access to Customer Personal Data to people who need it to provide, secure or support the service. These people are bound by confidentiality.
BERRYSAND administrators have technical access to the database. Access is used only when needed for the agreed processing.
Mailbox contents are kept by the email service. BERRYSAND does not store mailbox passwords.
6. Security
BERRYSAND takes appropriate technical and organisational measures, taking into account the risks, the nature of the processing, the state of technology and the costs. The measures are described in Schedule 2.
BERRYSAND may update its measures, as long as the level of protection does not go down. It regularly reviews whether the measures are still effective.
Security is shared: the Customer decides what it collects and publishes, and protects its own devices, login details and any copies it downloads.
7. Subprocessors
The Customer gives general permission for BERRYSAND to use subprocessors. The current list of subprocessors, with their function, processing locations and transfer safeguards, is available to customers on request at support@berrysand.com.
BERRYSAND informs the Customer by email at least 30 calendar days before adding or replacing a subprocessor for Customer Personal Data. The Customer can object within that period on reasonable data protection grounds.
The parties will try to find a solution for a valid objection. If none is found, the Customer can end the service for the affected website before the new processing starts, receive a proportional refund of unused prepaid fees, and ask for its data to be returned or deleted.
BERRYSAND imposes written data protection obligations on each subprocessor before it processes Customer Personal Data, and remains responsible to the Customer for the subprocessor’s performance.
8. Transfers outside the European Economic Area
Some subprocessors are based in, or provide support from, countries outside the European Economic Area, including the United States.
BERRYSAND only transfers Customer Personal Data outside the European Economic Area with a valid legal basis, such as an adequacy decision of the European Commission (including the EU-U.S. Data Privacy Framework) or the European Commission’s standard contractual clauses, with additional measures where needed. Details are available on request.
9. Help with requests from individuals
BERRYSAND helps the Customer answer requests for access, correction, deletion, restriction, objection and data portability, as far as possible given the nature of the processing.
If BERRYSAND receives such a request directly, it forwards it promptly to the Customer where the Customer can be identified. BERRYSAND does not decide on the request itself unless the Customer asks it to or the law requires it.
The Customer can delete messages, bookings and reviews in the app. There is no export button, but on request BERRYSAND provides the Customer’s messages, bookings and reviews in a spreadsheet (CSV) file, after checking identity and scope. A request is never refused because there is no export button.
10. Personal data breaches
BERRYSAND informs the Customer without undue delay after becoming aware of a personal data breach involving Customer Personal Data. BERRYSAND does not wait for a full investigation before sending a first notice.
As information becomes available, BERRYSAND describes the nature and scope of the breach, the types and approximate number of people and records involved, the likely consequences, the measures taken or planned, and a contact person. Information can be provided in stages.
BERRYSAND takes reasonable steps to contain the breach, keep evidence, investigate, limit harm and support the Customer. BERRYSAND keeps a record of every breach.
The Customer decides whether it must notify a supervisory authority or the people involved. BERRYSAND does not do this on the Customer’s behalf unless agreed in writing or required by law.
11. Assessments and audits
BERRYSAND gives reasonable help with data protection impact assessments, prior consultations and security obligations, taking into account the nature of the processing and the information available.
BERRYSAND makes available the information needed to show that it complies with this agreement. If that information is not enough, BERRYSAND allows and contributes to proportionate audits by the Customer or an independent auditor bound by confidentiality.
Audits are arranged with reasonable notice, limit disruption, and protect other customers’ information and system security. This does not prevent an urgent investigation or access by a supervisory authority.
Each party bears its own costs. Any charge for exceptional help must be reasonable and agreed in advance. BERRYSAND never charges for fixing its own breach of this agreement.
12. Return and deletion of data
At the end of the service, the Customer can choose deletion or return of Customer Personal Data, subject to legal retention obligations. A request for return should be made before the deletion date. BERRYSAND provides the data through support in a commonly used format. This does not give rights to BERRYSAND’s software or templates.
The standard deletion rules are:
| Event | What happens |
|---|---|
| Unpaid, unfinished website | Deleted after 45 days without activity; reminder seven days before. |
| Cancellation at the end of the paid period | Website offline at the end of the period; data kept for 30 days, with mailboxes still working; website data and mailboxes then deleted; reminder seven days before. |
| Delete now or deleting the account | Website data and mailboxes deleted immediately. The Customer should ask for a copy before choosing this. |
| Failed payment | Website and mailboxes paused on day 28, incoming email still received; reminder on day 81; website data and mailboxes deleted on day 88 if payment is still open. |
If a valid return request arrives before deletion and has not yet been completed, BERRYSAND makes sure the automatic deletion does not prevent the return. Any short extension is documented and used only to complete the return.
Technical backups can contain copies for the limited period described in Schedule 2. These copies stay protected and are not used for normal purposes. If a backup is ever restored, the deletion rules are applied again. Backups are not a recovery service for content the Customer deleted by accident.
After return or deletion, BERRYSAND deletes the remaining Customer Personal Data unless the law requires it to be kept, and confirms this on request.
Deleting a website does not delete its domain at the registry. Domain owner and registry records have their own legal basis.
13. Termination and liability
If processing can no longer continue lawfully, the parties look for a solution straight away and limit the processing where needed. A serious or unresolved breach of this agreement can justify ending the affected service.
The General Terms apply to liability between the parties, as far as the law allows. They do not limit the rights of individuals or the powers of supervisory authorities.
Obligations needed to protect remaining data, such as confidentiality and deletion, continue after the service ends for as long as needed.
14. Contact and law
Send privacy instructions and breach reports to support@berrysand.com. BERRYSAND uses the email address of the Customer’s account for notices.
Dutch law applies, subject to mandatory data protection rules. The dispute rules of the General Terms apply.
Schedule 1: Description of the processing
| Item | Description |
|---|---|
| Subject | Hosting and managing business websites, with their messages, booking requests, reviews, statistics, email and related features. |
| Duration | From the first processing until return or deletion, including the deletion and backup periods in this agreement. |
| Operations | Collecting, sending, storing, organising, retrieving, displaying, publishing chosen content, moderation by the Customer, delivering messages, support access, preparing copies and deleting. |
| Purposes | Providing the website and communication features chosen by the Customer, delivering notifications and responses, providing statistics, and keeping these services secure and working. |
| People involved | Website visitors, prospective and existing customers, reviewers, correspondents, people shown or mentioned in uploaded content, and business contacts whose data the Customer provides. |
| Messages | Name, email address, optional phone number and message. |
| Booking requests | Name, email address, optional phone number, chosen service, requested date and time, message and status. |
| Reviews | Name, rating, review text and approval status. No email address is needed. |
| Website content | Business contact details, texts, logos and photos, as far as they identify people. Visitors cannot upload files through the forms. |
| Statistics | Only after the visitor accepts on the cookie banner: a daily changing code made from the IP address, browser and date; the page or source the visitor came from; and the device type. The IP address itself is not stored in the statistics. |
| Mailbox addresses, email contents and metadata handled by the email service, and the information needed to send system emails and notifications. | |
| Sensitive data | Not asked for in the standard forms. Free text, email and photos can still contain it. |
Schedule 2: Security measures
BERRYSAND uses at least the following measures:
- Encrypted connections (HTTPS) for all parts of the service.
- Account passwords stored only as hashes.
- Database rules that separate each customer’s records.
- Administrator keys kept only on the server, never in the app.
- Mailbox passwords never stored by BERRYSAND.
- Limits and hidden anti-spam fields on all forms.
- Access to production systems only for authorised people, with two-step login on administrator accounts.
- Technical backups kept by our hosting providers for a limited period for disaster recovery, then overwritten.
- A breach procedure: record the incident, contain it, assess who and what is affected, inform affected customers without undue delay, and keep a record.
Schedule 3: Subprocessors and locations
The current list of subprocessors, with their function, processing locations and transfer safeguards, is available to customers on request at support@berrysand.com. Changes are announced as described in section 7.