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

  1. 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).
  2. 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.
  3. Constara processes personal data only to provide the services described in Annex II. It processes it for no purpose of its own.
  4. 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.

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.