Privacy

Privacy notice.

This notice explains how mdsiren.com handles information when you visit the site, follow a paid-search signup link, previously joined the waitlist or contact .mdSiren. Last updated .

Website scope onlyThis marketing website does not accept document uploads or create product accounts. Signup and product use happen in the separate .mdSiren application.

Who is responsible

The website’s data controller.

Joseph Waddington is the controller for the limited personal data described here. You can contact the controller at the address below.

support@mdsiren.com

Data and purpose

What may be processed when you use the site.

Website delivery and security

The services used to host and protect the website receive the technical request information needed to return a page, keep the service secure and diagnose faults. This can include an IP address, browser or device information, requested URL and request time.

Paid-search signup attribution

If a paid-search landing address contains one valid Google click identifier and selected campaign fields, the site can add only those bounded values to the .mdSiren app’s signup address. The website sends no page-view or CTA-click event. If the app creates a genuinely new account, the app may use the click identifier to report one signup conversion to Google Ads. A visit, signup-page view or returning sign-in is not reported as a new account.

Waitlist and product updates

If you previously joined the waitlist, we process your email address, any broad use case you choose, the signup placement, selected UTM campaign values in the page URL and the version of the consent wording. Loops also records the status needed to manage email confirmation, delivery and unsubscribes. This is used to confirm your request, send product updates and manage your preferences. Please do not submit documents, credentials, sensitive information or another person’s personal data.

Email enquiries

If you email .mdSiren, the sender details and message you provide are used to answer your enquiry. Do not send documents, credentials or sensitive project content.

Why this information is used

Technical request information is used for the legitimate interests of delivering and protecting the website. Limited paid-search attribution is used for the legitimate interests of understanding whether paid-search spend produces new product accounts without adding site-wide behavioural tracking. Enquiry emails are used to respond to the request you chose to make. Waitlist and product updates are based on your consent. Under the former waitlist flow, a signup remained pending until its email confirmation link was used. Product-update emails include an unsubscribe option, and a previous repeat submission did not override an existing opt-out. You can withdraw from product updates at any time using an unsubscribe link or by emailing support@mdsiren.com.

How long data is kept

We do not maintain a separate visitor analytics database. Enquiry emails are kept while needed to respond and record the outcome. The website does not retain a separate copy of signup-attribution values; the application’s notice covers any values received after you follow a signup link. A confirmed waitlist record is kept until you opt out or the list is discontinued. Unconfirmed records are not used for product updates and are removed after a periodic review when they are no longer needed to complete confirmation or protect the list from misuse. After an opt-out, the minimum suppression record may be retained to make sure no further marketing email is sent, subject to legal requirements.

Email processor

Loops processes prior waitlist records and update emails.

The previous waitlist form sent your email address, optional use case, signup metadata and the technical request information needed to process the submission to Loops (Astrodon Corporation), our email-service processor. Loops is based in the United States, and its current subprocessor list identifies United States processing. Loops states that it has certified under the UK Extension to the EU–U.S. Data Privacy Framework and uses contractual or other legally recognised safeguards, including Standard Contractual Clauses where applicable.

The former waitlist used Loops’ double-opt-in flow, so each signup started as Pending and was not subscribed unless the address was confirmed. Loops stores the signup source, consent-version reference and optional use case with the contact. This site does not keep a separate submission history or consent database. Confirmation emails did not use open or click tracking. Later product-update emails may record delivery, opens and link clicks unless that measurement is disabled in Loops.

Cookies and browser storage

No site-wide tracker or advertising storage.

We have not added analytics scripts, advertising cookies or other non-essential browser storage to mdsiren.com. The signup-link helper reads only allowed values already present in the landing-page address and does not create a cookie or browser-storage entry. If .mdSiren introduces non-essential technology, this notice will be updated and consent requested where required.

Your choices and rights

You can ask about personal data connected with you.

Depending on the circumstances, UK data-protection law may give you rights to access, correct, erase or restrict personal data, object to some processing, receive portable data or obtain a copy. You can withdraw waitlist consent at any time using an email unsubscribe link or by contacting us. Withdrawal does not affect processing already carried out lawfully before it.

Make a privacy request

Product boundary

The application has separate privacy information.

This notice covers mdsiren.com only. If you follow an attributed signup link, the application receives the allowed values and owns any completed-account conversion reporting to Google Ads. Historic waitlist preferences remain separate from product sign-in and account deletion. The .mdSiren application owns its account, document-processing, storage, retention and deletion information.