← MeridianDesk

MeridianDesk: Privacy Notice

Last updated: October 25, 2026

Publisher: Aubora SAS (a company in formation), France.
Contact: contact@aubora.co

How MeridianDesk handles data. In short: patient data stays on the prescriber's Mac. Clause 15 covers the details given on aubora.co to request the download, and clause 16 the optional check for new versions.

1. Purpose of this notice. This notice explains how the MeridianDesk application handles data on the prescriber's Mac. MeridianDesk is local-only software: it runs on the prescriber's computer and is designed so that patient data never leaves that computer. Clauses 15 and 16 cover two separate matters: the details a prescriber gives on aubora.co to download the application, and the optional check for new versions.

2. Data handled by the application. MeridianDesk imports a data file that a patient has exported from the Meridian application. That file may contain identifiable health information relating to the patient. The application reads this file, recomputes an estimated pharmacokinetic curve for review, and displays the result. MeridianDesk is read-only with respect to the patient's own data: it cannot alter, add to, or delete data on the patient's phone.

3. Where data is stored. Imported files and the application's working data are stored locally on the prescriber's Mac, within the user's Application Support directory and related local storage. No copy is created on any server controlled by Aubora.

4. No transmission to Aubora or to third parties. MeridianDesk does not transmit patient data, imported files, or computed results to Aubora or to any third party. The processing takes place entirely on the prescriber's Mac.

5. No analytics or telemetry. MeridianDesk collects no analytics, no usage telemetry, no tracking identifiers, and no behavioral data, and sends Aubora no information about how the application is used. The only request the application makes to a server is the optional update check described in clause 16, which carries no patient data.

6. The prescriber is the data controller. Because the prescriber decides to import identifiable patient data onto their own Mac and to process it for the purposes of a consultation, the prescriber is the data controller for that data within the meaning of the General Data Protection Regulation (GDPR). Aubora provides the software only; it does not receive or process the patient data and is therefore neither the controller nor a processor of that data. The prescriber remains bound by their professional secrecy obligations and by applicable data-protection law, including, in France, the Code de la santé publique.

7. Special-category data. Health data is a special category of personal data under Article 9 of the GDPR and benefits from reinforced protection. The prescriber, as controller, is responsible for identifying an appropriate legal basis and an applicable condition for processing such data, and for handling it in accordance with law and professional rules.

8. Rights of the data subjects. Patients hold the rights granted by data-protection law, including the rights of access, rectification, erasure, restriction, and objection, subject to the conditions and limits set by law. Because Aubora holds no patient data, Aubora cannot act on any such request. The prescriber, as controller and holder of the data, is responsible for receiving and answering these requests directly.

9. Retention and deletion. The prescriber controls how long imported files and computed results are kept. Deleting a patient file through the ordinary means of the operating system, or through the application where it offers this, removes that file from the prescriber's Mac. Aubora keeps no copy and therefore performs no retention on the prescriber's behalf.

10. Security recommendations. The prescriber is responsible for the security of the device on which patient data is stored. Aubora recommends enabling FileVault full-disk encryption, protecting the Mac user account with a strong password, keeping the operating system up to date, and limiting physical and logical access to the device.

11. Optional calendar access. If, and only if, the prescriber enables the "patients seen today" feature, MeridianDesk reads the Mac's local calendar solely to match patient names. This access is local: no calendar content is stored by the application or transmitted to Aubora or to any third party.

12. International transfers. Because processing takes place locally on the prescriber's Mac and no data is sent to Aubora or to any third party, MeridianDesk performs no transfer of patient data, including any transfer outside the European Union or the European Economic Area.

13. Supervisory authority. A patient who considers that their data has been handled unlawfully may contact the competent supervisory authority. In France, that authority is the Commission nationale de l'informatique et des libertés (CNIL).

14. Publisher and contact. MeridianDesk is published by Aubora SAS (société en formation), Paris, France. For questions about the application, contact contact@aubora.co. Questions from patients about the handling of their own data should be addressed to the prescriber, who is the data controller. Until Aubora is registered, the controller's obligations described in clauses 15 and 16 are carried by its founder, as section 1 of the aubora.co privacy policy explains.

15. Requesting the download on aubora.co. This clause concerns the prescriber's own details, not patient data, and is separate from the application, which sends no patient data and no usage data (clauses 4 and 5). To download MeridianDesk, a prescriber fills in a form on aubora.co with their name, professional email address, profession or role and country, and confirms that they accept the Terms of Use and the Health Disclaimer. Aubora is the controller of these details. They are used to provide the download, to know which professionals have requested MeridianDesk, and to reply to them. The legal bases are the steps taken at the prescriber's request before the licence applies (Article 6(1)(b) of the GDPR) and, for keeping a record of the request, Aubora's legitimate interest in knowing that software reserved for professionals reaches them (Article 6(1)(f) of the GDPR). The form is handled by a function hosted by Vercel Inc., which stores nothing, and the details are sent by email to contact@aubora.co through Resend, an email delivery service; both act as Aubora's processors. The message is kept for 24 months in Aubora's mailbox, which runs on Google Workspace, and Resend keeps a copy for no more than 30 days. To limit abuse, the function counts requests per IP address, held in hashed form and in memory only, and drops each count after ten minutes; it writes nothing to disk, and ordinary server logs are described in the aubora.co privacy policy. Vercel, Resend and Google are established in the United States and certified under the EU-U.S. Data Privacy Framework, so these transfers rest on the European Commission's adequacy decision of 10 July 2023. The prescriber may exercise the rights of access, rectification, erasure, restriction, objection and portability by writing to privacy@aubora.co, and may lodge a complaint with the CNIL. These details are needed to process the request: without them, the form does not start the download.

16. Checking for updates. MeridianDesk can check for new versions through Sparkle, a standard macOS update component. It checks nothing until the prescriber has agreed: on the second launch it asks whether to check automatically, and the choice can be made or changed at any time under Settings, Updates. When automatic checks are on, the application downloads the list of available versions from aubora.co at most once a day while it is open; the "Check for Updates…" command and the "Check now" button do the same on request. Like any web request, each check discloses the Mac's IP address and technical details such as the application's name and version; it carries no patient data, no imported file, no calendar content and no identifier. When the prescriber accepts an update, the new version is downloaded from Vercel Blob storage (public.blob.vercel-storage.com), and its signature is verified before it installs. Aubora is the controller of this processing, which serves only to offer corrections and new versions to the prescribers who want them; the legal basis is Aubora's legitimate interest in doing so (Article 6(1)(f) of the GDPR). Vercel Inc. hosts aubora.co and the Blob storage as Aubora's processor and keeps server logs of these requests for the limited period described in the aubora.co privacy policy. Vercel is established in the United States and certified under the EU-U.S. Data Privacy Framework, so this transfer rests on the European Commission's adequacy decision of 10 July 2023. The prescriber may object at any time by turning automatic checks off, may exercise their other rights by writing to privacy@aubora.co, and may lodge a complaint with the CNIL.