Data Processing Agreement
ValueRoom ApS · CVR 46900790 · Njalsgade 21F, 2., DK-2300 Copenhagen S. Version 2026-11-19, published 19 November 2026.
Part of the terms of service (clause 14.1). The providers are also listed at /subprocessors.
Standard Contractual Clauses
For the purposes of Article 28(3) of Regulation 2016/679 (the GDPR)
between
The Customer: the organization that accepted the ValueRoom Terms of Service, as named in its ValueRoom account
(the data controller)
and
ValueRoom ApS
CVR 46900790
Njalsgade 21F, 2.
DK-2300 Copenhagen S
Denmark
(the data processor)
each a 'party'; together 'the parties'
HAVE AGREED on the following Contractual Clauses (the Clauses) in order to meet the requirements of the GDPR and to ensure the protection of the rights of the data subject.
2. Preamble
2.1. These Contractual Clauses (the Clauses) set out the rights and obligations of the data controller and the data processor, when processing personal data on behalf of the data controller.
2.2. The Clauses have been designed to ensure the parties' compliance with Article 28(3) of Regulation 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data and repealing Directive 95/46/EC (General Data Protection Regulation).
2.3. In the context of the provision of the ValueRoom service, the data processor will process personal data on behalf of the data controller in accordance with the Clauses.
2.4. The Clauses shall take priority over any similar provisions contained in other agreements between the parties.
2.5. Four appendices are attached to the Clauses and form an integral part of the Clauses.
2.6. Appendix A contains details about the processing of personal data, including the purpose and nature of the processing, type of personal data, categories of data subject and duration of the processing.
2.7. Appendix B contains the data controller's conditions for the data processor's use of sub-processors and a list of sub-processors authorised by the data controller.
2.8. Appendix C contains the data controller's instructions with regards to the processing of personal data, the minimum security measures to be implemented by the data processor and how audits of the data processor and any sub-processors are to be performed.
2.9. Appendix D contains provisions for other activities which are not covered by the Clauses.
2.10. The Clauses along with appendices shall be retained in writing, including electronically, by both parties.
2.11. The Clauses shall not exempt the data processor from obligations to which the data processor is subject pursuant to the General Data Protection Regulation (the GDPR) or other legislation.
3. The rights and obligations of the data controller
3.1. The data controller is responsible for ensuring that the processing of personal data takes place in compliance with the GDPR (see Article 24 GDPR), the applicable EU or Member State data protection provisions and the Clauses.
3.2. The data controller has the right and obligation to make decisions about the purposes and means of the processing of personal data.
3.3. The data controller shall be responsible, among other, for ensuring that the processing of personal data, which the data processor is instructed to perform, has a legal basis.
4. The data processor acts according to instructions
4.1. The data processor shall process personal data only on documented instructions from the data controller, unless required to do so by Union or Member State law to which the processor is subject. Such instructions shall be specified in appendices A and C. Subsequent instructions can also be given by the data controller throughout the duration of the processing of personal data, but such instructions shall always be documented and kept in writing, including electronically, in connection with the Clauses.
4.2. The data processor shall immediately inform the data controller if instructions given by the data controller, in the opinion of the data processor, contravene the GDPR or the applicable EU or Member State data protection provisions.
5. Confidentiality
5.1. The data processor shall only grant access to the personal data being processed on behalf of the data controller to persons under the data processor's authority who have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality and only on a need to know basis. The list of persons to whom access has been granted shall be kept under periodic review. On the basis of this review, such access to personal data can be withdrawn, if access is no longer necessary, and personal data shall consequently not be accessible anymore to those persons.
5.2. The data processor shall at the request of the data controller demonstrate that the concerned persons under the data processor's authority are subject to the abovementioned confidentiality.
6. Security of processing
6.1. Article 32 GDPR stipulates that, taking into account the state of the art, the costs of implementation and the nature, scope, context and purposes of processing as well as the risk of varying likelihood and severity for the rights and freedoms of natural persons, the data controller and data processor shall implement appropriate technical and organisational measures to ensure a level of security appropriate to the risk.
The data controller shall evaluate the risks to the rights and freedoms of natural persons inherent in the processing and implement measures to mitigate those risks. Depending on their relevance, the measures may include the following:
a. Pseudonymisation and encryption of personal data;
b. the ability to ensure ongoing confidentiality, integrity, availability and resilience of processing systems and services;
c. the ability to restore the availability and access to personal data in a timely manner in the event of a physical or technical incident;
d. a process for regularly testing, assessing and evaluating the effectiveness of technical and organisational measures for ensuring the security of the processing.
6.2. According to Article 32 GDPR, the data processor shall also – independently from the data controller – evaluate the risks to the rights and freedoms of natural persons inherent in the processing and implement measures to mitigate those risks. To this effect, the data controller shall provide the data processor with all information necessary to identify and evaluate such risks.
6.3. Furthermore, the data processor shall assist the data controller in ensuring compliance with the data controller's obligations pursuant to Articles 32 GDPR, by inter alia providing the data controller with information concerning the technical and organisational measures already implemented by the data processor pursuant to Article 32 GDPR along with all other information necessary for the data controller to comply with the data controller's obligation under Article 32 GDPR.
If subsequently – in the assessment of the data controller – mitigation of the identified risks require further measures to be implemented by the data processor, than those already implemented by the data processor pursuant to Article 32 GDPR, the data controller shall specify these additional measures to be implemented in Appendix C.
7. Use of sub-processors
7.1. The data processor shall meet the requirements specified in Article 28(2) and (4) GDPR in order to engage another processor (a sub-processor).
7.2. The data processor shall therefore not engage another processor (sub-processor) for the fulfilment of the Clauses without the prior general written authorisation of the data controller.
7.3. The data processor has the data controller's general authorisation for the engagement of sub-processors. The data processor shall inform in writing the data controller of any intended changes concerning the addition or replacement of sub-processors at least 30 days in advance, thereby giving the data controller the opportunity to object to such changes prior to the engagement of the concerned sub-processor(s). Longer time periods of prior notice for specific sub-processing services can be provided in Appendix B. The list of sub-processors already authorised by the data controller can be found in Appendix B.
7.4. Where the data processor engages a sub-processor for carrying out specific processing activities on behalf of the data controller, the same data protection obligations as set out in the Clauses shall be imposed on that sub-processor by way of a contract or other legal act under EU or Member State law, in particular providing sufficient guarantees to implement appropriate technical and organisational measures in such a manner that the processing will meet the requirements of the Clauses and the GDPR.
The data processor shall therefore be responsible for requiring that the sub-processor at least complies with the obligations to which the data processor is subject pursuant to the Clauses and the GDPR.
7.5. A copy of such a sub-processor agreement and subsequent amendments shall – at the data controller's request – be submitted to the data controller, thereby giving the data controller the opportunity to ensure that the same data protection obligations as set out in the Clauses are imposed on the sub-processor. Clauses on business related issues that do not affect the legal data protection content of the sub-processor agreement, shall not require submission to the data controller.
7.6. If the sub-processor does not fulfil his data protection obligations, the data processor shall remain fully liable to the data controller as regards the fulfilment of the obligations of the sub-processor. This does not affect the rights of the data subjects under the GDPR – in particular those foreseen in Articles 79 and 82 GDPR – against the data controller and the data processor, including the sub-processor.
8. Transfer of data to third countries or international organisations
8.1. Any transfer of personal data to third countries or international organisations by the data processor shall only occur on the basis of documented instructions from the data controller and shall always take place in compliance with Chapter V GDPR.
8.2. In case transfers to third countries or international organisations, which the data processor has not been instructed to perform by the data controller, is required under EU or Member State law to which the data processor is subject, the data processor shall inform the data controller of that legal requirement prior to processing unless that law prohibits such information on important grounds of public interest.
8.3. Without documented instructions from the data controller, the data processor therefore cannot within the framework of the Clauses:
a. transfer personal data to a data controller or a data processor in a third country or in an international organization
b. transfer the processing of personal data to a sub-processor in a third country
c. have the personal data processed in by the data processor in a third country
8.4. The data controller's instructions regarding the transfer of personal data to a third country including, if applicable, the transfer tool under Chapter V GDPR on which they are based, shall be set out in Appendix C.6.
8.5. The Clauses shall not be confused with standard data protection clauses within the meaning of Article 46(2)(c) and (d) GDPR, and the Clauses cannot be relied upon by the parties as a transfer tool under Chapter V GDPR.
9. Assistance to the data controller
9.1. Taking into account the nature of the processing, the data processor shall assist the data controller by appropriate technical and organisational measures, insofar as this is possible, in the fulfilment of the data controller's obligations to respond to requests for exercising the data subject's rights laid down in Chapter III GDPR.
This entails that the data processor shall, insofar as this is possible, assist the data controller in the data controller's compliance with:
a. the right to be informed when collecting personal data from the data subject
b. the right to be informed when personal data have not been obtained from the data subject
c. the right of access by the data subject
d. the right to rectification
e. the right to erasure ('the right to be forgotten')
f. the right to restriction of processing
g. notification obligation regarding rectification or erasure of personal data or restriction of processing
h. the right to data portability
i. the right to object
j. the right not to be subject to a decision based solely on automated processing, including profiling
9.2. In addition to the data processor's obligation to assist the data controller pursuant to Clause 6.3., the data processor shall furthermore, taking into account the nature of the processing and the information available to the data processor, assist the data controller in ensuring compliance with:
a. The data controller's obligation to without undue delay and, where feasible, not later than 72 hours after having become aware of it, notify the personal data breach to the competent supervisory authority, the supervisory authority competent for the data controller (for a data controller established in Denmark, the Danish Data Protection Agency, Datatilsynet), unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons;
b. the data controller's obligation to without undue delay communicate the personal data breach to the data subject, when the personal data breach is likely to result in a high risk to the rights and freedoms of natural persons;
c. the data controller's obligation to carry out an assessment of the impact of the envisaged processing operations on the protection of personal data (a data protection impact assessment);
d. the data controller's obligation to consult the competent supervisory authority, the supervisory authority competent for the data controller (for a data controller established in Denmark, the Danish Data Protection Agency, Datatilsynet), prior to processing where a data protection impact assessment indicates that the processing would result in a high risk in the absence of measures taken by the data controller to mitigate the risk.
9.3. The parties shall define in Appendix C the appropriate technical and organisational measures by which the data processor is required to assist the data controller as well as the scope and the extent of the assistance required. This applies to the obligations foreseen in Clause 9.1. and 9.2.
10. Notification of personal data breach
10.1. In case of any personal data breach, the data processor shall, without undue delay after having become aware of it, notify the data controller of the personal data breach.
10.2. The data processor's notification to the data controller shall, if possible, take place within 24 hours after the data processor has become aware of the personal data breach to enable the data controller to comply with the data controller's obligation to notify the personal data breach to the competent supervisory authority, cf. Article 33 GDPR.
10.3. In accordance with Clause 9(2)(a), the data processor shall assist the data controller in notifying the personal data breach to the competent supervisory authority, meaning that the data processor is required to assist in obtaining the information listed below which, pursuant to Article 33(3)GDPR, shall be stated in the data controller's notification to the competent supervisory authority:
a. The nature of the personal data including where possible, the categories and approximate number of data subjects concerned and the categories and approximate number of personal data records concerned;
b. the likely consequences of the personal data breach;
c. the measures taken or proposed to be taken by the controller to address the personal data breach, including, where appropriate, measures to mitigate its possible adverse effects.
10.4. The parties shall define in Appendix C all the elements to be provided by the data processor when assisting the data controller in the notification of a personal data breach to the competent supervisory authority.
11. Erasure and return of data
11.1. On termination of the provision of personal data processing services, the data processor shall be under obligation to delete all personal data processed on behalf of the data controller and certify to the data controller that it has done so unless Union or Member State law requires storage of the personal data.
12. Audit and inspection
12.1. The data processor shall make available to the data controller all information necessary to demonstrate compliance with the obligations laid down in Article 28 and the Clauses and allow for and contribute to audits, including inspections, conducted by the data controller or another auditor mandated by the data controller.
12.2. Procedures applicable to the data controller's audits, including inspections, of the data processor and sub-processors are specified in appendices C.7. and C.8.
12.3. The data processor shall be required to provide the supervisory authorities, which pursuant to applicable legislation have access to the data controller's and data processor's facilities, or representatives acting on behalf of such supervisory authorities, with access to the data processor's physical facilities on presentation of appropriate identification.
13. The parties' agreement on other terms
13.1. The parties may agree other clauses concerning the provision of the personal data processing service specifying e.g. liability, as long as they do not contradict directly or indirectly the Clauses or prejudice the fundamental rights or freedoms of the data subject and the protection afforded by the GDPR.
14. Commencement and termination
14.1. The Clauses shall become effective on the date of both parties' signature.
14.2. Both parties shall be entitled to require the Clauses renegotiated if changes to the law or inexpediency of the Clauses should give rise to such renegotiation.
14.3. The Clauses shall apply for the duration of the provision of personal data processing services. For the duration of the provision of personal data processing services, the Clauses cannot be terminated unless other Clauses governing the provision of personal data processing services have been agreed between the parties.
14.4. If the provision of personal data processing services is terminated, and the personal data is deleted or returned to the data controller pursuant to Clause 11.1. and Appendix C.4., the Clauses may be terminated by written notice by either party.
14.5. Signature
On behalf of the data controller
Accepted electronically by the person who accepted the ValueRoom Terms of Service for the data controller. That person's name, the date and time, and the version of the terms and of these Clauses accepted are recorded in the data controller's ValueRoom account and are shown to the data controller on request.
On behalf of the data processor
| Name | Jason Stewart |
| Position | Director, ValueRoom ApS |
| Date | 19 November 2026 |
| Signature | Signed electronically by Jason Stewart for ValueRoom ApS by publishing this version |
15. Data controller and data processor contacts/contact points
15.1. The parties may contact each other using the following contacts/contact points:
15.2. The parties shall be under obligation continuously to inform each other of changes to contacts/contact points.
For the data controller: the administrator of the data controller's ValueRoom account, at the email address on that account.
For the data processor:
| Name | Jason Stewart |
| Position | Director |
| Telephone | Not used. Contact is in writing. |
| hello@valueroom.app |
Appendix A — Information about the processing
A.1. The purpose of the data processor's processing of personal data on behalf of the data controller is:
To provide the ValueRoom service to the data controller: a workspace in which the data controller's sales and customer success team, and the people it invites from its own customers and prospects, agree a plan, confirm steps and outcomes, share content and messages, and use AI assisted features over the data controller's own workspace data.
A.2. The data processor's processing of personal data on behalf of the data controller shall mainly pertain to (the nature of the processing):
Hosting, storage, display, transmission and analysis of the data controller's workspace data, namely:
- the team's workspace and the rooms the data controller opens for its customers and prospects, each reached by an invited person through a personal link;
- the record of what was confirmed, by whom and when, which is kept append only;
- email the service sends on the data controller's behalf (room links, invitations, follow ups the data controller's users approve, approval links);
- data brought in from systems the data controller chooses to connect (a CRM, a support desk, an issue tracker, a meeting notes tool, a product usage feed);
- AI features: the text a feature needs is sent to the AI sub-processor to produce the output the user asked for. A free text question that an invited person asks the room's assistant is answered and is not stored by the data processor, and is never shown to the data controller;
- where the data controller uses them: hosted meetings, meeting recordings and their transcription. A recording hosted by the service starts only after the other side has confirmed consent in the product;
- where the data controller's users connect an AI assistant of their own: read access for that assistant to the rooms that user may already see, and proposals from it that a user must approve. That assistant's provider is the data controller's own supplier and not a sub-processor.
A.3. The processing includes the following types of personal data about data subjects:
- Business contact and identity data: name, work email address, employer, job title or role, profile photo where a person adds one.
- Sign in data: password stored only as a hash, access links and codes stored only as hashes, single sign on identifiers where the data controller uses single sign on.
- Room content: steps and milestones, confirmations with the person and time, comments, notes, messages, documents and files the parties upload, decisions and reactions.
- Room activity: when a room was opened, which sections were viewed and for how long, downloads. This is shown to both sides of the room.
- Where meetings are used: voice and image in recordings, transcripts with speakers named, the record of who consented to a recording.
- Data from connected systems, as the data controller chooses: CRM records for companies, contacts and deals; the text of emails, notes, calls, tickets and transcripts held in those systems; product usage figures per customer account.
No special categories of personal data (Article 9 GDPR), no data about criminal convictions (Article 10 GDPR), no payment card data and no data about children are intended or permitted (Appendix D.4).
A.4. Processing includes the following categories of data subject:
- the data controller's own users (its employees and others it gives a seat);
- people at the data controller's customers, prospects and partners whom it invites into a room or names in room content;
- people who appear in the content the data controller uploads or brings in from a connected system.
A.5. The data processor's processing of personal data on behalf of the data controller may be performed when the Clauses commence. Processing has the following duration:
For as long as the data controller has a ValueRoom account, and after that until the deletion described in Appendix C.4 is complete.
Appendix B — Authorised sub-processors
B.1. Approved sub-processors
On commencement of the Clauses, the data controller authorises the engagement of the following sub-processors:
Always used:
| Name | Company registration | Address | Description of processing |
|---|---|---|---|
| Vercel Inc. (including Vercel Blob) | Delaware, United States, no. 5857312 | 440 N Barranca Ave #4133, Covina, CA 91723, United States | Hosting and compute for the application; storage of uploaded files, content and meeting recordings. Region: Frankfurt, Germany |
| Databricks, Inc. (Neon; its affiliate Neon, LLC) | United States company | 160 Spear Street, San Francisco, CA 94105, United States | The Neon database: all workspace data at rest, encrypted. Region: Frankfurt, Germany |
| Anthropic, PBC, which performs the inference and issues the invoices for the account; and Anthropic Ireland, Limited, where Anthropic's published commercial terms make it the contracting entity for a customer in the EEA | United States; Ireland | 548 Market St, PMB 90375, San Francisco, CA 94104, United States; 6th Floor, South Bank House, Barrow Street, Dublin 4, D04 TR29, Ireland | AI inference for every AI feature, through one metered code path. Receives the text a feature needs. Not used to train models. Deleted by Anthropic within 30 days. Processed in the United States |
| Plus Five Five, Inc. (Resend) | United States company | 2261 Market Street #5039, San Francisco, CA 94114, United States | Sending the service's email: recipient name and address, the message. Delivery logs kept 30 days. Processed in the United States |
| Functional Software, Inc. d/b/a Sentry | United States company | 45 Fremont Street, 8th Floor, San Francisco, CA 94105, United States | Error diagnostics when something breaks: the stack trace, the route, an identifier for grouping. No page content, no IP address, no request body. Kept 30 days. Region: Frankfurt, Germany |
Used only when the feature is switched on:
| Name | Company registration | Address | Description of processing |
|---|---|---|---|
| Upstash, Inc. | Delaware, United States | Upstash publishes no postal address in its agreement, terms or privacy policy; notices go to support@upstash.com | Rate limit counters keyed by a scrambled form of an email or IP address that cannot be read back. EU region. Only when enabled |
| WorkOS, Inc. | United States company | 548 Market St, PMB 86125, San Francisco, CA 94104, United States (its notice address) | Single sign on and directory sync for the data controller's users. Only when the data controller uses single sign on. Processed in the United States |
| Daily, Co. (Daily.co) | United States company | 548 Market St., Suite 39113, San Francisco, CA 94104-5401, United States | Live meeting audio and video; recordings in Daily's own storage until the service retrieves them. Only when the data controller uses hosted meetings. Live call media passes through Daily's call servers, which are not fixed to a region and may be outside the EU. Recordings are stored in the United States |
| AssemblyAI Inc. | United States company | 169 Madison Ave STE 38365, New York, NY 10016, United States | Speech to text of a recorded meeting, on its EU endpoint. Not used to train its models. Audio deleted within 48 hours; deletion of a transcript begins at 30 days. Account and usage records, and file names seen by its own monitoring providers, are in the United States; its support staff outside the EU may reach a file when asked to troubleshoot. Only when the data controller uses transcription |
The data controller shall on the commencement of the Clauses authorise the use of the abovementioned sub-processors for the processing described for that party. The data processor shall not be entitled – without the data controller's explicit written authorisation – to engage a sub-processor for a 'different' processing than the one which has been agreed upon or have another sub-processor perform the described processing.
The same list is kept current at https://valueroom.app/subprocessors.
Systems the data controller connects to its own workspace (for example its CRM, support desk, issue tracker or meeting notes tool) and an AI assistant a user connects are the data controller's own suppliers. They are not sub-processors of the data processor.
B.2. Prior notice for the authorisation of sub-processors
The data processor gives notice of a new or replaced sub-processor at least 30 days in advance, by email to the address on the data controller's account and by updating the published list. The data controller may object in writing within that period on reasonable data protection grounds. What follows an objection is in Appendix D.6.
Appendix C — Instruction pertaining to the use of personal data
C.1. The subject of/instruction for the processing
The data processor's processing of personal data on behalf of the data controller shall be carried out by the data processor performing the following:
Providing the ValueRoom service as described in the ValueRoom Terms of Service and in Appendix A. The data controller's instructions are: the Terms of Service and these Clauses; what the data controller and its users set up and do in the service (opening rooms, inviting people, connecting or disconnecting a system, switching a feature on or off, setting a retention period, erasing a person, exporting data); and any further instruction the parties agree in writing.
C.2. Security of processing
The level of security shall take into account:
That the processing concerns business contact data and the working record between a company and its business customers; that it may include the text of business conversations and, where the data controller uses the meeting features, voice and image; that no special categories of personal data are intended or permitted; and that the service holds many organizations' data in one system, so separation between organizations is the central risk.
The data processor shall hereafter be entitled and under obligation to make decisions about the technical and organisational security measures that are to be applied to create the necessary (and agreed) level of data security.
The data processor shall however – in any event and at a minimum – implement the following measures that have been agreed with the data controller. Each is marked: enforced (built into the product and checked by automated tests that block a release when they fail) or provider (supplied by the hosting or database sub-processor). The data processor holds no third party security certification and does not claim one.
Pseudonymisation and encryption of personal data
- Data is encrypted in transit (TLS) and at rest in the database (provider).
- Passwords are stored only as hashes. Room access links, one time codes and ingest secrets are stored only as hashes; the raw value is never stored (enforced).
- Credentials for systems the data controller connects are stored encrypted (enforced).
- When a person is erased, their identity is replaced by a placeholder (enforced).
Ongoing confidentiality, integrity, availability and resilience
- Every read and write in the team's workspace is limited to the signed in user's own organization. Separation between organizations is proven by an automated test with two organizations, not assumed (enforced).
- Inside an organization, access to a room follows the user's role (enforced).
- A person invited to a room reaches that one room only, through a personal link tied to that room (enforced).
- The data processor's own operator panel cannot read room content. This is a restriction in the code, tested, and not only a rule for staff (enforced).
- The record of confirmations and the audit records are append only in the database: an attempt to change or delete an entry is rejected (enforced).
- Questions an invited person asks the room's assistant are not stored. AI usage is counted per organization, month and feature only, with no person, room or content (enforced).
- Protection against overload and automated attack at the hosting layer (provider); rate limits on sign in and on every write an invited person can make (enforced).
Restoring availability and access after an incident
- The database provider keeps encrypted backups with point in time recovery, for a window of 7 days (provider).
- The application is deployed from version controlled code and can be redeployed or rolled back (provider).
Regular testing and evaluation of the measures
- The automated checks behind every measure marked enforced (separation between organizations, room access, what an invited person can see, retention and deletion, the append only record, security headers) run before every release and block it when one fails (enforced).
Access to data online
- Users sign in with a password or, where the data controller uses it, single sign on with directory sync so a leaver loses access (enforced). Repeated failed sign in attempts are throttled per account (enforced).
- Direct access to the production database and to the hosting accounts is limited to the data processor's management, at present one person. Those accounts (hosting, database, source code and email sending) are protected by two step sign in with an authenticator app, and the mailboxes used to sign in to and recover those accounts are protected by two step verification.
Protection during transmission
- TLS on every connection (provider). Security headers and a content security policy are set in one place and checked against real responses (enforced). Background jobs refuse to run without a valid secret (enforced).
Protection during storage
- Encryption at rest (provider). Uploaded files and recordings are kept in private storage and served only through the service's own checks, never by a public address (enforced).
Physical security of locations
- The data processor runs no servers of its own. Personal data is held in the data centres of the hosting and database sub-processors, whose physical security is covered by their own independent audit reports.
Home and remote working
- The data processor's personnel work remotely. Workspace data is reached through the service and the sub-processors' consoles only, and is not copied to tools outside the list in Appendix B.
Logging
- Each organization has an audit log of administrative changes, visible to its administrators (enforced).
- The data processor's own operator actions (creating, suspending or deleting an organization, a plan change) are written to an append only record (enforced).
- Hosting request logs are kept at most one day; error events 30 days; email delivery logs 30 days.
C.3. Assistance to the data controller
The data processor shall insofar as this is possible – within the scope and the extent of the assistance specified below – assist the data controller in accordance with Clause 9.1. and 9.2. by implementing the following technical and organisational measures:
- Erasure. An administrator of the data controller can erase a person in the service. The person's identity is replaced by a placeholder and their access is removed. What they confirmed stays on the record, attributed to an erased person (Appendix D.5). The erasure is written to the organization's audit log.
- Access and portability. An administrator can export the organization's full structured record set in a machine readable form at any time, at no charge.
- Rectification. The data controller's users can correct data in the service. A confirmation is corrected by a new entry that supersedes the earlier one.
- Requests sent to the data processor. If a data subject writes to the data processor about data in the data controller's workspace, the data processor does not answer the substance. It forwards the request to the data controller without undue delay and tells the person it has done so.
- Where a request cannot be met with these tools, the data processor gives reasonable help on a written request, without undue delay.
- A personal data breach. The notice under Clause 10 states, as far as then known: what happened and when; the kinds of data and the categories and approximate number of people and records concerned; the likely consequences; what has been done and what is proposed; and a contact. It may be given in stages as facts become known. Where the breach began at a sub-processor, the data processor passes on that sub-processor's notice with its own assessment.
- Impact assessments and prior consultation. The data processor provides these Clauses and their appendices, the published trust page and the published list of sub-processors, and answers reasonable written questions about the processing.
C.4. Storage period/erasure procedures
During the service, the data controller decides how long data is kept: it can set a retention period for raw text brought in from connected systems, after which that text is permanently removed in place; it can erase a person; and it can export at any time.
When the data controller's account ends, the data processor offers the export, waits 30 days (or the period agreed in a signed order), and then permanently deletes the organization's database records and stored files in accordance with Clause 11.1. The data processor confirms the deletion in writing on request. What remains is a record without content that the deletion happened and when.
Deleted data may remain in the database provider's encrypted backups for 7 days and then expires. Backups are used only for disaster recovery. If a restore brings back data deleted under this clause, the data processor deletes it again.
C.5. Processing location
Processing of the personal data under the Clauses cannot be performed at other locations than the following without the data controller's prior written authorisation:
- Frankfurt, Germany: the application (Vercel), the database (Neon, a Databricks company), stored files (Vercel Blob), error diagnostics (Sentry).
- The European Union: rate limit counters (Upstash, when enabled); meeting transcription (AssemblyAI's EU endpoint, when used).
- The United States: AI inference (Anthropic); the service's email (Resend); and, when the data controller uses them, single sign on (WorkOS) and hosted meetings (Daily.co). Support and operations staff of the providers with a region in the EU may reach data from the United States.
- Denmark: the data processor's own personnel, working remotely.
C.6. Instruction on the transfer of personal data to third countries
The data controller instructs the data processor to transfer personal data to the sub-processors in Appendix B that are established in, or process in, the United States, to the extent needed for the processing described for each. The basis for each transfer under Chapter V GDPR is:
| Sub-processor | Basis for the transfer |
|---|---|
| Vercel Inc. | EU-U.S. Data Privacy Framework (listed active, read 13 Nov 2026) and standard contractual clauses in Vercel's data processing addendum |
| Databricks, Inc. (Neon) | EU-U.S. Data Privacy Framework (listed active, covering Neon, LLC, read 13 Nov 2026) and standard contractual clauses in Databricks' data processing addendum |
| Anthropic | Standard contractual clauses, in Anthropic's data processing addendum. Anthropic is not listed in the Data Privacy Framework (read 13 Nov 2026) |
| Plus Five Five, Inc. (Resend) | EU-U.S. Data Privacy Framework (listed active, re-certification under review, read 13 Nov 2026) and standard contractual clauses in Resend's data processing addendum |
| Functional Software, Inc. (Sentry) | EU-U.S. Data Privacy Framework (listed active, read 13 Nov 2026), with standard contractual clauses as the fallback in Sentry's data processing addendum |
| Upstash, Inc. | EU-U.S. Data Privacy Framework (listed active, read 13 Nov 2026), with standard contractual clauses as the fallback in its data processing addendum |
| WorkOS, Inc. | Standard contractual clauses, in WorkOS's data processing addendum. WorkOS states no Data Privacy Framework certification |
| Daily, Co. | EU-U.S. Data Privacy Framework (listed active, read 13 Nov 2026), with standard contractual clauses as the fallback in its data processing addendum |
| AssemblyAI Inc. | Standard contractual clauses, in AssemblyAI's data processing addendum. AssemblyAI was not found on the official Data Privacy Framework list on 13 Nov 2026 |
The entries marked "listed active" were read on the official list on 13 Nov 2026.
If the data controller does not in the Clauses or subsequently provide documented instructions pertaining to the transfer of personal data to a third country, the data processor shall not be entitled within the framework of the Clauses to perform such transfer.
C.7. Procedures for the data controller's audits, including inspections, of the processing of personal data being performed by the data processor
The data processor has not obtained an auditor's report from an independent third party and does not claim one. The parties have agreed the following instead.
On request, the data processor makes available the information needed to show compliance with Article 28 GDPR and the Clauses: these Clauses and their appendices, the published trust page, the list of the automated checks behind each measure marked enforced in C.2 with a dated record of their latest run, a summary of the sub-processors' audit reports, and answers to a security questionnaire.
Where that information is not enough to show compliance, the data controller or an independent auditor it appoints (bound to confidentiality and not a competitor of the data processor) may audit the data processor's processing of the data controller's personal data, including by inspection of the systems used for it. An audit is limited to the data controller's own data and must be carried out so that no other organization's data can be reached. Unless a personal data breach affecting the data controller or a supervisory authority requires otherwise, an audit takes place at most once in twelve months and on 30 days' written notice.
The data controller's costs of an audit are borne by the data controller. The data processor sets aside the time needed for the data controller to carry it out.
C.8. Procedures for audits, including inspections, of the processing of personal data being performed by sub-processors
The data processor reads each sub-processor's independent audit report or certification before engaging it and when it is replaced, and gives the data controller a summary on request. Where the data controller shows that this is not enough to establish that a sub-processor processes in accordance with the Clauses, the data processor uses the audit rights it has under its agreement with that sub-processor and passes on the result. The data processor remains fully responsible for the sub-processor's compliance.
Appendix D — The parties' terms of agreement on other subjects
D.1. How these Clauses are entered into. The data controller enters into these Clauses when a person authorised to act for it accepts the ValueRoom Terms of Service, which refer to these Clauses. That acceptance is the data controller's signature for Clause 14.1. The data processor's signature is given once for each published version.
D.2. Relation to the Terms of Service. These Clauses are part of the agreement described in clause 1.1 of the Terms of Service. For the processing of personal data on the data controller's behalf, these Clauses come first (Clause 2.4). The limits and exclusions of liability in the Terms of Service apply between the parties to claims under these Clauses, to the extent the law allows. Nothing here limits a data subject's rights or either party's liability to a data subject or a supervisory authority under the GDPR.
D.3. An instruction the data processor believes is unlawful. When the data processor has informed the data controller under Clause 4.2, it may pause the processing concerned until the data controller confirms or changes the instruction in writing. The data processor is not in breach of the Terms of Service for pausing on this ground.
D.4. Data that does not belong in the service. The service is not designed for special categories of personal data, data about criminal convictions, payment card data or data about children. The data controller will not submit such data and will tell its users and the people it invites not to.
D.5. The record of confirmations after an erasure. The record of what was confirmed is append only. When a person is erased, the person is replaced by a placeholder and the facts they confirmed stay on the record, attributed to an erased person. The data controller accepts this as its instruction and reflects it in the information it gives to data subjects.
D.6. Objection to a new sub-processor. If the data controller objects under Appendix B.2, the parties work in good faith to resolve it, including by the data processor not using the new sub-processor for the data controller where that is practical. If it is not resolved before the change takes effect, the data controller may end its account, and a paying data controller receives a refund of prepaid fees for the unused period.
D.7. The data processor as controller of its own records. The data processor is itself the controller of the data it needs to run its own business: the contact and billing details of the people who sign up for or administer an account, its contract and payment records, counts of usage without content, and its support correspondence. That processing is described in the privacy notice at https://valueroom.app/privacy and is outside these Clauses.
D.8. Changes to the appendices. The data processor may update Appendix B under Clause 7.3 and Appendix B.2. Other changes to these Clauses or their appendices are made as the Terms of Service provide for changes to the agreement, and never so as to reduce the measures in Appendix C.2.
D.9. Help beyond the tools in the service. The help described in Appendix C.3 through the service's own tools is included in every plan.