Trust and data
Know what may proceed, what waits and why.
The delivery contract
What we deliver is set out in writing before work starts. The entry audit is contracted only through an audit order form that both parties accept in writing. A pilot or ongoing service runs under a signed proposal and contract, and the proposal names the job, the scope, the evidence, the owner, the limits, the cap and the measurement method. You choose the goal and approve consequential exceptions. We design, connect and operate the scoped system and maintain its agreed boundaries. Before any access to personal data, both parties sign the data processing agreement set out below.
Company facts
Constara is the trading name of Neotoma, Inc., a Delaware corporation (United States), Delaware Division of Corporations file number 10621405. Its registered office is 131 Continental Dr, Suite 305, Newark, New Castle County, Delaware 19713, USA. The list that follows gives the legal entity, the data location, the providers and the clinic data statement, each with its verification status.
What is verified
- Legal entity
- Neotoma, Inc.Confirmed
- Data location
- This site is hosted on Fly.io in its Amsterdam region (the Netherlands). Whatever the region, Fly.io states that these are held or processed in the United States: volume snapshots (in AWS S3 us-east-1), control plane data (accounts, organizations, app and release configuration, and secrets), platform logs, metrics, proxy traces, container images and image builds. It also states that inbound TLS connections terminate at the Fly.io edge nearest the connecting device. Email sits on Google Workspace, which may process data in any country where Google or its subprocessors maintain facilities.Confirmed
- Subprocessors
- Fly.io, Inc. (United States): hosting, in the Amsterdam region (the Netherlands), with the processing Fly.io states takes place in the United States whatever the region: volume snapshots (in AWS S3 us-east-1), control plane data, platform logs, metrics, proxy traces, container images and image builds. Google (Google Workspace): email. No model provider or message-sending provider is engaged for client data yet; Annex IV of the data processing agreement names each one before it receives any.Confirmed
- Provider retention and no-training terms
- Fly.io makes application logs available for 7 days and deletes its separate archive copy in the United States after 30 days. Sampled request traces used for troubleshooting include visitors' IP addresses. Fly.io processes them in the United States and keeps them for up to 60 days. Fly.io's published security questionnaire states that, under its data processing addendum, it deletes customer data within 30 days after its services to us end. Its own residual encrypted backup copies are deleted within 90 days. Deletion by Google (Google Workspace): within a maximum of 180 days of the deletion instruction or, at the end of the term, of the end of a recovery period of up to 30 days, unless the law requires Google to keep the data, under sections 6.1 and 6.2 of its Cloud Data Processing Addendum. No model provider is engaged for client data yet, so its retention and no-training terms are not stated here; Annex IV of the data processing agreement names each one before it receives any, and clause A1 requires the strictest setting its contract offers.Confirmed
- Clinic data statement
- We are given no access to a clinic's personal data before the data processing agreement is signed. Clinical records, diagnoses, test results, prescriptions and medical histories are excluded. In the first pilot, free-text health content is excluded too: a message that contains it goes to the clinic's staff without drafting by an agent. Any outbound message that mentions or implies a treatment, condition, test result or clinical matter always needs individual approval by the clinic's staff.Confirmed
The record
Under the data processing agreement, once it is signed, every action the system takes on a client's data (read, draft, approval, send, write-back) is recorded with time, actor and source in an append-only record the client can inspect (Annex III). Each approval is recorded too: who approved, when and which version (clause A3). Approval and action logs are kept for 12 months (Annex II, section 7). The figures used for invoicing are aggregated and contain no data that identifies a person (clause A2). These are undertakings to a client who has signed, confirmed before each signature. They do not describe this website.
Before any data access
- This agreement (the DPA) is entered into between the client named in Annex I as controller (the Client) and Neotoma, Inc., trading as Constara, as processor (Constara).
- It forms part of the service agreement, proposal or order form under which Constara provides the audit, pilot or ongoing service (the Service Agreement). Under Clause 4, the Clauses in Part 2 prevail over the Service Agreement on any data-protection matter.
- Constara processes personal data only to provide the services described in Annex II. It processes it for no purpose of its own.
- Effective date: the earlier of signature and the first time Constara is given access to personal data held by the Client. No access before signature. This includes any audit with data access (clause A5); the standard entry audit involves no access.
Data processing agreement
Constara offers this data processing agreement to clients before it is given access to any personal data. It uses the European Commission's standard contractual clauses between controllers and processors (Implementing Decision (EU) 2021/915). The agreement is in Spanish and English; if they differ, the Spanish version prevails. Status: A template. No access to personal data happens before it is signed, and each measure in Annex III is confirmed against the service before each signature.
Part 2. Standard contractual clauses (Implementing Decision (EU) 2021/915)
- Options chosen: Clause 1(a) Option 1 (GDPR). Clause 5 (docking clause) included. Clause 7.7(a) Option 2 (general written authorisation). Clause 8(c)(4) Option 1. Clause 9 Option 1. References to Regulation (EU) 2018/1725 are kept where the official text uses "and/or". They have no effect, because neither party is an EU institution.
SECTION I — Clause 1 – Purpose and scope
- (a) The purpose of these Standard Contractual Clauses (the Clauses) is to ensure compliance with Article 28(3) and (4) of Regulation (EU) 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).
- (b) The controllers and processors listed in Annex I have agreed to these Clauses in order to ensure compliance with Article 28(3) and (4) of Regulation (EU) 2016/679 and/or Article 29(3) and (4) of Regulation (EU) 2018/1725.
- (c) These Clauses apply to the processing of personal data as specified in Annex II.
- (d) Annexes I to IV are an integral part of the Clauses.
- (e) These Clauses are without prejudice to obligations to which the controller is subject by virtue of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.
- (f) These Clauses do not by themselves ensure compliance with obligations related to international transfers in accordance with Chapter V of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.
Clause 2 – Invariability of the Clauses
- (a) The Parties undertake not to modify the Clauses, except for adding information to the Annexes or updating information in them.
- (b) This does not prevent the Parties from including the standard contractual clauses laid down in these Clauses in a broader contract, or from adding other clauses or additional safeguards provided that they do not directly or indirectly contradict the Clauses or detract from the fundamental rights or freedoms of data subjects.
Clause 3 – Interpretation
- (a) Where these Clauses use the terms defined in Regulation (EU) 2016/679 or Regulation (EU) 2018/1725 respectively, those terms shall have the same meaning as in that Regulation.
- (b) These Clauses shall be read and interpreted in the light of the provisions of Regulation (EU) 2016/679 or Regulation (EU) 2018/1725 respectively.
- (c) These Clauses shall not be interpreted in a way that runs counter to the rights and obligations provided for in Regulation (EU) 2016/679 / Regulation (EU) 2018/1725 or in a way that prejudices the fundamental rights or freedoms of the data subjects.
Clause 4 – Hierarchy
- In the event of a contradiction between these Clauses and the provisions of related agreements between the Parties existing at the time when these Clauses are agreed or entered into thereafter, these Clauses shall prevail.
Clause 5 – Docking clause
- (a) Any entity that is not a Party to these Clauses may, with the agreement of all the Parties, accede to these Clauses at any time as a controller or a processor by completing the Annexes and signing Annex I.
- (b) Once the Annexes in (a) are completed and signed, the acceding entity shall be treated as a Party to these Clauses and have the rights and obligations of a controller or a processor, in accordance with its designation in Annex I.
- (c) The acceding entity shall have no rights or obligations resulting from these Clauses from the period prior to becoming a Party.
SECTION II – OBLIGATIONS OF THE PARTIES — Clause 6 – Description of processing(s)
- The details of the processing operations, in particular the categories of personal data and the purposes of processing for which the personal data is processed on behalf of the controller, are specified in Annex II.
Clause 7 – Obligations of the Parties
7.1. Instructions
- (a) The processor shall process personal data only on documented instructions from the controller, unless required to do so by Union or Member State law to which the processor is subject. In this case, the processor shall inform the controller of that legal requirement before processing, unless the law prohibits this on important grounds of public interest. Subsequent instructions may also be given by the controller throughout the duration of the processing of personal data. These instructions shall always be documented.
- (b) The processor shall immediately inform the controller if, in the processor's opinion, instructions given by the controller infringe Regulation (EU) 2016/679 / Regulation (EU) 2018/1725 or the applicable Union or Member State data protection provisions.
7.2. Purpose limitation
- The processor shall process the personal data only for the specific purpose(s) of the processing, as set out in Annex II, unless it receives further instructions from the controller.
7.3. Duration of the processing of personal data
- Processing by the processor shall only take place for the duration specified in Annex II.
7.4. Security of processing
- (a) The processor shall at least implement the technical and organisational measures specified in Annex III to ensure the security of the personal data. This includes protecting the data against a breach of security leading to accidental or unlawful destruction, loss, alteration, unauthorised disclosure or access to the data (personal data breach). In assessing the appropriate level of security, the Parties shall take due account of the state of the art, the costs of implementation, the nature, scope, context and purposes of processing and the risks involved for the data subjects.
- (b) The processor shall grant access to the personal data undergoing processing to members of its personnel only to the extent strictly necessary for implementing, managing and monitoring of the contract. The processor shall ensure that persons authorised to process the personal data received have committed themselves to confidentiality or are under an appropriate statutory obligation of confidentiality.
7.5. Sensitive data
- If the processing involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person's sex life or sexual orientation, or data relating to criminal convictions and offences ("sensitive data"), the processor shall apply specific restrictions and/or additional safeguards.
7.6. Documentation and compliance
- (a) The Parties shall be able to demonstrate compliance with these Clauses.
- (b) The processor shall deal promptly and adequately with inquiries from the controller about the processing of data in accordance with these Clauses.
- (c) The processor shall make available to the controller all information necessary to demonstrate compliance with the obligations that are set out in these Clauses and stem directly from Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725. At the controller's request, the processor shall also permit and contribute to audits of the processing activities covered by these Clauses, at reasonable intervals or if there are indications of non-compliance. In deciding on a review or an audit, the controller may take into account relevant certifications held by the processor.
- (d) The controller may choose to conduct the audit by itself or mandate an independent auditor. Audits may also include inspections at the premises or physical facilities of the processor and shall, where appropriate, be carried out with reasonable notice.
- (e) The Parties shall make the information referred to in this Clause, including the results of any audits, available to the competent supervisory authority/ies on request.
7.7. Use of sub-processors
- (a) GENERAL WRITTEN AUTHORISATION: The processor has the controller's general authorisation for the engagement of sub-processors from an agreed list. The processor shall specifically inform in writing the controller of any intended changes of that list through the addition or replacement of sub-processors at least 30 days in advance, thereby giving the controller sufficient time to be able to object to such changes prior to the engagement of the concerned sub-processor(s). The processor shall provide the controller with the information necessary to enable the controller to exercise the right to object.
- (b) Where the processor engages a sub-processor for carrying out specific processing activities (on behalf of the controller), it shall do so by way of a contract which imposes on the sub-processor, in substance, the same data protection obligations as the ones imposed on the data processor in accordance with these Clauses. The processor shall ensure that the sub-processor complies with the obligations to which the processor is subject pursuant to these Clauses and to Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.
- (c) At the controller's request, the processor shall provide a copy of such a sub-processor agreement and any subsequent amendments to the controller. To the extent necessary to protect business secret or other confidential information, including personal data, the processor may redact the text of the agreement prior to sharing the copy.
- (d) The processor shall remain fully responsible to the controller for the performance of the sub-processor's obligations in accordance with its contract with the processor. The processor shall notify the controller of any failure by the sub-processor to fulfil its contractual obligations.
- (e) The processor shall agree a third party beneficiary clause with the sub-processor whereby - in the event the processor has factually disappeared, ceased to exist in law or has become insolvent - the controller shall have the right to terminate the sub-processor contract and to instruct the sub-processor to erase or return the personal data.
7.8. International transfers
- (a) Any transfer of data to a third country or an international organisation by the processor shall be done only on the basis of documented instructions from the controller or in order to fulfil a specific requirement under Union or Member State law to which the processor is subject and shall take place in compliance with Chapter V of Regulation (EU) 2016/679 or Regulation (EU) 2018/1725.
- (b) The controller agrees that where the processor engages a sub-processor in accordance with Clause 7.7. for carrying out specific processing activities (on behalf of the controller) and those processing activities involve a transfer of personal data within the meaning of Chapter V of Regulation (EU) 2016/679, the processor and the sub-processor can ensure compliance with Chapter V of Regulation (EU) 2016/679 by using standard contractual clauses adopted by the Commission in accordance with of Article 46(2) of Regulation (EU) 2016/679, provided the conditions for the use of those standard contractual clauses are met.
Clause 8 – Assistance to the controller
- (a) The processor shall promptly notify the controller of any request it has received from the data subject. It shall not respond to the request itself, unless authorised to do so by the controller.
- (b) The processor shall assist the controller in fulfilling its obligations to respond to data subjects' requests to exercise their rights, taking into account the nature of the processing. In fulfilling its obligations in accordance with (a) and (b), the processor shall comply with the controller's instructions
- (c) In addition to the processor's obligation to assist the controller pursuant to Clause 8(b), the processor shall furthermore assist the controller in ensuring compliance with the following obligations, taking into account the nature of the data processing and the information available to the processor:
- (1) the 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') where a type of processing is likely to result in a high risk to the rights and freedoms of natural persons;
- (2) the obligation to consult the competent supervisory authority/ies 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 controller to mitigate the risk;
- (3) the obligation to ensure that personal data is accurate and up to date, by informing the controller without delay if the processor becomes aware that the personal data it is processing is inaccurate or has become outdated;
- (4) the obligations in Article 32 of Regulation (EU) 2016/679.
- (d) The Parties shall set out in Annex III the appropriate technical and organisational measures by which the processor is required to assist the controller in the application of this Clause as well as the scope and the extent of the assistance required.
Clause 9 – Notification of personal data breach
- In the event of a personal data breach, the processor shall cooperate with and assist the controller for the controller to comply with its obligations under Articles 33 and 34 of Regulation (EU) 2016/679 or under Articles 34 and 35 of Regulation (EU) 2018/1725, where applicable, taking into account the nature of processing and the information available to the processor.
9.1 Data breach concerning data processed by the controller
- In the event of a personal data breach concerning data processed by the controller, the processor shall assist the controller:
- (a) in notifying the personal data breach to the competent supervisory authority/ies, without undue delay after the controller has become aware of it, where relevant/(unless the personal data breach is unlikely to result in a risk to the rights and freedoms of natural persons);
- (b) in obtaining the following information which, pursuant to Article 33(3) of Regulation (EU) 2016/679, shall be stated in the controller's notification, and must at least include:
- (1) 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;
- (2) the likely consequences of the personal data breach;
- (3) 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.
- Where, and insofar as, it is not possible to provide all this information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
- (c) in complying, pursuant to Article 34 of Regulation (EU) 2016/679, with the obligation to communicate without undue delay 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.
9.2 Data breach concerning data processed by the processor
- In the event of a personal data breach concerning data processed by the processor, the processor shall notify the controller without undue delay after the processor having become aware of the breach. Such notification shall contain, at least:
- (a) a description of the nature of the breach (including, where possible, the categories and approximate number of data subjects and data records concerned);
- (b) the details of a contact point where more information concerning the personal data breach can be obtained;
- (c) its likely consequences and the measures taken or proposed to be taken to address the breach, including to mitigate its possible adverse effects.
- Where, and insofar as, it is not possible to provide all this information at the same time, the initial notification shall contain the information then available and further information shall, as it becomes available, subsequently be provided without undue delay.
- The Parties shall set out in Annex III all other elements to be provided by the processor when assisting the controller in the compliance with the controller's obligations under Articles 33 and 34 of Regulation (EU) 2016/679.
SECTION III – FINAL PROVISIONS — Clause 10 – Non-compliance with the Clauses and termination
- (a) Without prejudice to any provisions of Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725, in the event that the processor is in breach of its obligations under these Clauses, the controller may instruct the processor to suspend the processing of personal data until the latter complies with these Clauses or the contract is terminated. The processor shall promptly inform the controller in case it is unable to comply with these Clauses, for whatever reason.
- (b) The controller shall be entitled to terminate the contract insofar as it concerns processing of personal data in accordance with these Clauses if:
- (1) the processing of personal data by the processor has been suspended by the controller pursuant to point (a) and if compliance with these Clauses is not restored within a reasonable time and in any event within one month following suspension;
- (2) the processor is in substantial or persistent breach of these Clauses or its obligations under Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725;
- (3) the processor fails to comply with a binding decision of a competent court or the competent supervisory authority/ies regarding its obligations pursuant to these Clauses or to Regulation (EU) 2016/679 and/or Regulation (EU) 2018/1725.
- (c) The processor shall be entitled to terminate the contract insofar as it concerns processing of personal data under these Clauses where, after having informed the controller that its instructions infringe applicable legal requirements in accordance with Clause 7.1 (b), the controller insists on compliance with the instructions.
- (d) Following termination of the contract, the processor shall, at the choice of the controller, delete all personal data processed on behalf of the controller and certify to the controller that it has done so, or, return all the personal data to the controller and delete existing copies unless Union or Member State law requires storage of the personal data. Until the data is deleted or returned, the processor shall continue to ensure compliance with these Clauses.
Part 3. Additional clauses (Clause 2(b): they add safeguards and do not contradict the Clauses)
A1. No processing for Constara's own purposes. Constara does not use the Client's personal data for its own purposes. That covers training or fine-tuning AI models, benchmarking, marketing, product improvement, and any service to another client. Constara uses every model provider at the strictest setting its contract offers, so that the provider does not train on the data or retain it beyond what the service needs. Annex IV names that setting for each model provider before it receives any of the Client's data.
A2. Fee measurement on aggregated figures. The fee depends on verified incremental profit, so Constara needs measurement figures. Constara calculates those figures on the Client's instruction, as part of the service it provides to the Client. The figures used for invoicing are aggregated (counts, sums, rates per period and unit) and contain no data that identifies a person. Constara does not keep person-level data for billing.
A3. Human approval of outbound messages. No message is sent to a person in the Client's name unless one of the following applies:
- (i) a member of the Client's staff named in Annex II has approved that message; or
- (ii) the message follows a template the Client has approved in writing and contains no data concerning health.
- Any outbound message that mentions or implies a treatment, condition, test result or clinical matter always needs individual approval by Client staff. Constara keeps a record of each approval (who approved, when, and which version).
A4. Health data. See Annex II, section 3. Clinical records, diagnoses, test results, prescriptions and medical histories are excluded. The Client must not give Constara access to systems or folders that hold them. In the first pilot, free-text health content is also excluded: a message that contains it goes to the Client's staff without drafting by an agent. If health data reaches Constara anyway (for example, inside a free-text enquiry), Constara does not copy it into any structured record and deletes it on the schedule in Annex II.
A5. Audit phase (read-only). This clause applies only to an audit with data access that is expressly agreed under this DPA. The standard entry audit is contracted through the audit order form; it involves no access to the Client's systems or records and needs no DPA. During a paid audit with access, Constara's access is read-only and limited to the sources listed in Annex II, section 9. Any working copy is kept outside the permanent record, holds only minimised data, and is deleted within 10 working days after the audit report is delivered. Constara confirms the deletion in writing.
A6. Breach notification time. "Without undue delay" in Clause 9.2 means that Constara notifies the Client's contact in Annex I within 48 hours of becoming aware of the breach, so that the Client can give its own notice to the AEPD within 72 hours. Constara sends further information as it becomes available.
A7. Return and deletion at the end of the service. On termination, the Client chooses one of the following:
- (a) Return. Constara returns the Client's personal data in a structured, commonly used, machine-readable format (JSON or CSV). Records written back to the Client's own systems during the service are already in the Client's hands.
- (b) Deletion. Constara deletes the data without returning it.
- Constara then deletes all remaining copies in the systems it controls, and instructs each sub-processor to delete the copies it holds, within 30 days of termination. Encrypted backups in the systems Constara controls expire on their normal rotation, no later than 35 days after that deletion, so no copy remains in those systems more than 65 days after termination. The systems Constara controls are the data, volumes and snapshots it can itself configure, delete or set to expire. A provider's own residual encrypted backups, and any other copy held in a sub-processor's own systems or backups, follow that provider's published terms, which can take longer. Annex IV states each provider's limit; where a provider publishes none, Annex IV says so and Constara gives no date for that copy. Constara certifies in writing the deletion from the systems it controls and the instruction given to each sub-processor. Constara does not use the option in art. 33.3 LOPDGDD to keep blocked copies after the end of the service.
A8. The Client's systems. The Client grants access to its own channels (email inbox, booking system, web forms, messaging accounts) under its own accounts and contracts with those providers. Those providers are the Client's processors, not Constara's sub-processors. Constara uses only the access the Client grants, with the lowest privilege that works. Constara does not keep the Client's passwords in readable form.
A9. Records of processing. Constara keeps the record of processing activities that Article 30(2) GDPR requires of processors.
A10. Liability. Each party's total liability to the other under this DPA and the Service Agreement is capped at the fees paid or payable by the Client in the 12 months before the event that gives rise to the claim. The cap does not apply where the law does not allow liability to be limited, including wilful misconduct (dolo) and gross negligence. It does not affect data subjects' rights under Article 82 GDPR, or the supervisory authority's powers.
A11. Governing law and courts. This DPA is governed by Spanish law. The courts of Barcelona have jurisdiction, without prejudice to data subjects' rights and to the supervisory authority's powers.
A12. Applicable data protection law. The GDPR and Spain's Organic Law 3/2018 (LOPDGDD) apply to Neotoma, Inc.'s processing under this DPA. Sub-processors in Annex IV may process personal data outside the EEA, under the safeguard stated there for each (Clause 7.8).
Annex I – List of parties
Controller(s):
- 1. Name: [CLIENT: legal name]; Address: [CLIENT]; Tax ID (NIF/CIF): [CLIENT]; Contact person's name, position and contact details: [CLIENT]; Data protection officer, if any: [CLIENT]; Signature and accession date: …
- 2. [CLIENT: other group entities, if they accede under Clause 5]
Processor(s):
- 1. Name: Neotoma, Inc., trading as Constara; Incorporated in: Delaware, United States. Registered office: 131 Continental Dr, Suite 305, Newark, New Castle County, Delaware 19713, USA; Tax ID: none in Spain (Neotoma, Inc. is a United States company); Contact person: Mark Hendrickson, founder. Privacy contact: privacy@constara.ai; Data protection officer: not appointed (not required); Signature and accession date: …
Annex II – Description of the processing
1. Categories of data subjects whose personal data is processed
- People who contact the Client with an enquiry through the channels listed in section 9 (prospective customers or patients).
- Existing customers or patients of the Client who are due a follow-up or recall that the Client has listed (for example, a periodic check-up or service renewal).
- People acting for them (for example, a parent booking for a child), only as far as their contact details appear in the enquiry.
- The Client's staff who use the service to approve messages or review results (name, work contact, approval actions).
2. Categories of personal data processed
- Identity and contact: name; phone number; email address; messaging handle; preferred language; preferred contact times.
- Enquiry content: the text of messages and the replies sent; date, time and channel; message identifiers.
- Booking status: enquiry state (new, answered, followed up, booked, attended, no-show, cancelled, lost); appointment date and time; site or location.
- Minimal service context: the type of service asked about, in the Client's own service categories (for example, "first visit", "cleaning", "check-up"); recall due date and recall category.
- Approval and audit trail: who approved which message, and when; the system's record of the actions it took.
- Aggregated measurement data: counts and amounts per period and unit (not personal data once aggregated; see clause A2).
- Not processed: clinical records, diagnoses, test results, prescriptions, medical histories, payment card data, identity documents, and data on children beyond a contact name given by the adult making the booking.
3. Sensitive data processed (if applicable) and the restrictions or safeguards applied
- Data concerning health may arise incidentally in two ways: the fact that a person contacts a health clinic, together with the type of service they ask about; health details a person chooses to write in a free-text message. In the first pilot, a free-text message with health content goes to the Client's staff without drafting by an agent (clause A4).
- Safeguards: (a) Strict purpose limitation: answering and following up the enquiry or recall only; (b) Minimisation: service context is reduced to the Client's service category. Free-text health details are not copied into structured fields; (c) Human approval: individual approval by Client staff of any outbound message that mentions or implies a health matter (clause A3); (d) Access restriction: access is limited to Constara's named personnel (currently the founder), to automated agents operating the service under Constara's control, and to the Client's named approvers, and each access is logged; (e) No onward transfer beyond the sub-processors in Annex IV. No model training (clause A1); (f) Shorter retention for message content (section 7); (g) Encryption in transit and at rest (Annex III).
4. Nature of the processing
- Reading enquiries and recall lists from the Client's channels and systems, through access the Client grants.
- Structuring them into a record.
- Drafting replies and follow-ups, with the help of AI models.
- Submitting drafts for approval where required.
- Sending approved messages through the Client's own channels.
- Writing results (booking status, notes) back to the Client's systems.
- Producing aggregated measurement reports of incremental bookings.
- During an audit with data access (clause A5) only: read-only review of samples to design the service and the measurement method.
5. Purposes for which the personal data is processed on behalf of the controller
- (a) Answering and following up the Client's enquiries and recalls on the Client's own channels until they are booked or closed.
- (b) Writing the results back to the Client's systems.
- (c) Measuring incremental bookings and the related profit for the Client, using aggregated figures.
- (d) During an audit with data access: assessing the recurring work, its sources and its measurability.
6. Duration of the processing
- Audit with data access: from signature until the audit working copy is deleted (clause A5).
- Pilot and ongoing service: for the term of the Service Agreement, then until return or deletion under clause A7.
7. Retention during the service
- Message content (text of enquiries and replies): 90 days after the enquiry is closed, then deleted from the systems Constara controls, whose backups expire as in Annex III; a provider's own copies follow clause A7 and Annex IV. Booking status and dates remain in the Client's own systems.
- Structured enquiry record (contact, status, service category, dates): for the term of the service, or earlier deletion on the Client's instruction.
- Approval and action logs: 12 months, for accountability and dispute resolution.
- Aggregated measurement figures: for the term of the Service Agreement plus the period needed for invoicing and tax purposes (they contain no personal data).
8. Processing by sub-processors.
- Subject matter, nature and duration follow sections 4 to 7. Each sub-processor's role is described in Annex IV.
9. Client channels and systems in scope
- [CLIENT: e.g. web-form inbox, shared email address, booking software, WhatsApp Business account, phone-call log]
10. Client staff authorised to approve messages
- [CLIENT: names and roles]
Annex III – Technical and organisational measures
- On signature, Constara undertakes to have the following measures in place for the Client's data and to keep them in place for as long as it processes that data. Constara confirms each measure against the service before each signature.
- Encryption in transit. All connections use TLS 1.2 or higher, including to the Client's systems, to sub-processors and between Constara components.
- Encryption at rest. Data volumes and backups are encrypted at rest by the hosting provider. Application secrets (access tokens to the Client's systems) are kept in an encrypted secrets store and are never written to logs or source code.
- Separation between clients. Each Client's data is held in a logically separate store and is not used in any other Client's service.
- Identification and authorisation. Personal accounts for each Constara person, with no shared logins. Multi-factor authentication on hosting, code, email and model-provider accounts. Least-privilege access to the Client's systems: read-only during an audit with data access, and only the scopes needed during the service. Access is reviewed at each change of personnel and at least every 6 months.
- Personnel. Access by people is currently limited to the founder. Automated agents that operate the service act under credentials Constara controls, only within the access set out in this annex, and each of their actions is recorded as set out under Logging and accountability. Any future staff or contractor signs a confidentiality undertaking before access and receives data-protection instructions.
- Logging and accountability. Every action the system takes on the Client's data (read, draft, approval, send, write-back) is recorded with time, actor and source in an append-only record that the Client can inspect. Administrative access is logged.
- Human control. Approval rules as in clause A3. The Client can stop the service's sending at any time.
- Data minimisation. Only the fields listed in Annex II, section 2 are structured. Service context is reduced to the Client's categories. Excluded data (Annex II) is not ingested.
- Retention and deletion. Automatic deletion from the systems Constara controls on the periods in Annex II, section 7. Deletion at the end of the service as in clause A7, with written certification.
- Availability and recovery. Daily encrypted backups in the systems Constara controls, retained for no more than 35 days. A provider's own residual encrypted backups follow clause A7 and Annex IV. A documented restore procedure, tested at least once before the first client goes live and then every 6 months.
- Testing and review. Security settings are reviewed before each significant change. Dependencies are kept up to date. These measures are reviewed at least once a year.
- Configuration. Default settings are the restrictive ones: sending is off until approval rules are configured, and access is read-only until write-back is agreed.
- Physical security. No Client personal data is stored on paper or on unencrypted local devices. Laptops use full-disk encryption and screen lock. Data-centre physical security is the hosting provider's (Annex IV).
- Model providers. Contractual no-training and minimal-retention settings as in clause A1. Only the data needed for each drafting task is sent to the model.
Assistance to the controller (Clauses 8 and 9):
- Data subject requests: Constara forwards any request it receives to the Client within 3 working days, and can export or delete a person's data within 10 working days of the Client's instruction.
- Breaches: notice within 48 hours (clause A6), with the information listed in Clause 9.2 and a timeline of the incident.
- DPIA: Constara gives the Client a description of the processing, the data flows and these measures, and answers its questions.
Annex IV – List of sub-processors (agreed list under Clause 7.7(a), Option 2)
- This list is part of a template. Before each signature, Constara confirms each provider, the entity that contracts, its location, its data-processing terms, its published deletion limit and the transfer safeguard. At signature, the list holds no provider whose data processing agreement Constara has not accepted.
- 1. Name: Fly.io, Inc. Address / location: United States. Service: Application hosting, storage and backups. Data processed: All Annex II data. Processing location and transfer safeguard: the Amsterdam region (the Netherlands); safeguard, for that region and for the United States processing stated in the next item: the EU-US Data Privacy Framework, under which Fly.io, Inc. states that it is certified (COMPLIANCE-3), and, for any transfer the Framework does not cover, the Commission's 2021/914 standard contractual clauses (Module 2, controller to processor) in Fly.io's data processing addendum. Deletion from its systems: within 30 days of the end of Fly.io's services to Constara and, for its own residual encrypted backup copies, within a maximum of 90 days, according to Fly.io's published security questionnaire (section 10.1 and Annex I.B of its data processing addendum). That clock is Fly.io's own: it runs from the end of Fly.io's services to Constara, which is not the end of Constara's service to the Client. The same questionnaire describes a separate security detection pipeline that takes in fleet and application telemetry, with longer retention and no published figure (INFRASEC-12). Fly.io confirmed in writing on 4 Nov 2026, about Constara's application, that this pipeline holds records about its own infrastructure and corporate systems, not that application's logs. Fly.io publishes no limit for it, and Constara gives no date for any copy held there.
- 1, continued. Whatever the region, Fly.io states in its published security questionnaire (DATA-6, COMPLIANCE-6 and COMPLIANCE-23) that these are held or processed in the United States: volume snapshots (in AWS S3 us-east-1), control plane data (accounts, organizations, app and release configuration, and secrets), platform logs, metrics, proxy traces, container images and image builds; and that inbound TLS connections terminate at the Fly.io edge nearest the connecting device. Fly.io makes application logs available for 7 days and deletes its separate archive copy in the United States after 30 days. Sampled request traces used for troubleshooting include visitors' IP addresses. Fly.io processes them in the United States and keeps them for up to 60 days (section 2(a) of the privacy notice).
- 2. Name: Model provider, not yet engaged for client data. Constara names it here, with its address, processing location, transfer safeguard and published deletion limit (or that it publishes none), before it receives any of the Client's data. Service: Drafting replies and follow-ups; classifying enquiries. Data processed: Enquiry content and the minimal context needed for each task.
- 3. Name: Message-sending provider, not yet engaged for client data. Constara names it here, with its address, processing location, transfer safeguard and published deletion limit (or that it publishes none), before it receives any of the Client's data. Service: Sending service notifications or reports, where messages are not sent through the Client's own channels. Data processed: Recipient address and message content.
- 4. Name: Google LLC (Google Workspace). Address / location: Mountain View, California, United States. Service: Email for Constara's mailboxes. Data processed: Personal data in correspondence about the service (for example, a forwarded data subject request). Processing location and transfer safeguard: any country where Google or its subprocessors maintain facilities (section 10.1 of Google's published Cloud Data Processing Addendum); safeguard: the EU-US Data Privacy Framework, under which Google LLC states that it is certified, and, where that does not apply, the standard contractual clauses that addendum incorporates. Deletion from its systems: within a maximum of 180 days of the deletion instruction or, at the end of the term, of the end of a recovery period of up to 30 days, unless the law requires Google to keep the data, under sections 6.1 and 6.2 of Google's published Cloud Data Processing Addendum.
- Description of responsibilities: each sub-processor acts only for the service described. Constara stays fully responsible to the Client under Clause 7.7(d).
Signatures
- For the Client (controller): ……………… Name, position, date
- For Neotoma, Inc., trading as Constara (processor): ……………… Mark Hendrickson, founder, date
Privacy on this page
Campaign tags in a link (for example utm_source) are part of the page address, so they reach our hosting provider with the page request, as any address does. The site does not read or store them.
Campaign tags and pixels
This site uses no cookies, and no other technology that stores information on your device or reads it to identify or track you (local storage, pixels or fingerprinting). Its scripts read only three things: your browser's display preferences (data saver, reduced motion, and light or dark theme), to decide how the page draws itself and whether animations play; the part of the address after the # sign, to open the tab a link points to; and the size of the window, to keep a tooltip on screen. That reading stays in your browser and does not reach us. That is why we do not ask for consent or show a cookie banner. If we ever add a technology that is not strictly necessary, we will ask for your consent first, as Article 22(2) LSSI requires, and list it here.
Requests and legal review
To exercise a data protection right, write to privacy@constara.ai and say which right you are exercising. We reply within one month, which can be extended by two further months in complex cases, and you can complain to the Spanish Data Protection Agency (AEPD). If your request concerns data we process for a client, we forward it to that client within 3 working days. You can ask at the same address for a copy of a provider's transfer safeguard. The data processing agreement is published on this page so that you and your own legal adviser can read it before signing. It is in Spanish and English; if they differ, the Spanish version prevails.
