Privacy policy

Information we collect

When you subscribe, the form sends the email address you enter, an optional specialty, the Device Pulse list identifier, the page and form location, a landing-page variant, available campaign parameters, and a randomly generated event identifier to the newsletter subscription service. Campaign parameters can include utm_source, utm_medium, utm_campaign, utm_content, and utm_term. The service may also receive technical information sent with a web request, such as IP address, user agent, referring page, and request time.

The current What Practices Are Buying component does not collect poll answers. A future research instrument may request voluntary professional and purchasing fields under a separate notice and consent. Those fields will not be added to an email subscription without documenting use, storage, access, retention, and deletion first.

Device Pulse does not ask for patient information, medical records, payment-card information, or clinical details. Do not submit protected health information through a newsletter form or reply.

How information is used

Subscription data is used to maintain the Device Pulse list, honor subscribe and unsubscribe requests, deliver authorized publication email, prevent duplicate active subscriptions, measure which pages and campaigns produce signups, diagnose abuse, and improve the publication. A failed welcome or delivery attempt should not reverse a valid subscription record.

The site uses Google Analytics 4 to measure page use and, when the subscription service reports a new or restored subscription, the newsletter_signup event. The event can include form location, landing variant, signup status, method, and campaign values. It should not fire for an address that is already subscribed.

Public issue, archive, shortlist, poll-intent, category, result-view, and sponsor-link interactions use controlled event names and parameters. These events can include page family, public question or sponsor identifiers, category ID, result state, item type, item count, and export method. They do not include an answer, email, notes, serial numbers, contract contents, or patient information. Editorial interaction events are separate from the newsletter signup conversion.

Advertising and audience matching

No Meta Pixel or Conversion API dataset is configured in the public site code as of the date above. If Device Pulse activates Meta advertising measurement, the policy will be updated before activation. The intended measurement design sends a browser Lead and a server Lead with the same event identifier so Meta can count one conversion.

If an existing-subscriber exclusion audience is created in the future, active subscriber emails may be normalized and hashed or uploaded through Meta's customer-list process to prevent ads from being shown to subscribers. That work requires the account owner's acceptance of platform terms. It will not be used to claim a subscriber relationship publicly. Previous Lead converters may also be excluded for a documented retention window.

Storage, sharing, and retention

The repository documentation identifies Cloudflare D1 as the subscription database and a Cloudflare Worker as the subscription endpoint. Google processes analytics data under its terms. Hosting and content delivery providers process request logs needed to serve and secure the site. Device Pulse does not sell subscriber email addresses.

The buyer shortlist stays in browser local storage. It contains a schema version plus stable public content identifiers, item types, saved times, and order. It has no notes field and is not sent to Device Pulse. Clearing browser data can remove it.

Subscription records are kept while a subscription is active and as needed to honor an unsubscribe, prevent unwanted reactivation, maintain security, or meet legal obligations. Campaign attribution should supplement the contact record rather than overwrite unrelated data. Temporary audience exports, if authorized, must be stored with restricted permissions and deleted after upload.

Your choices and contact

You may unsubscribe through the link included in an authorized email. Until the sending workflow is verified, contact the publisher through the professional profile linked on this page for access, correction, or deletion requests. Some records may be retained where needed to honor an opt-out or legal requirement.

Browser settings can limit cookies. Blocking analytics may reduce measurement but should not prevent access to public pages. A privacy request should identify the email address at issue without including patient or clinical information.

Children, security, and changes

Device Pulse is written for professional buyers and is not directed to children. Reasonable administrative and technical controls are used, but no internet service can promise perfect security. Material policy changes will be posted here with a new updated date before a new use begins where required.

Measurement controls

The signup code generates one event identifier for a submission and passes it with the subscription request. Google Analytics receives newsletter_signup only when the service identifies the result as subscribed or resubscribed. An already_subscribed result is not a new conversion. If Meta measurement is configured later, the same identifier should accompany the browser and server Lead copies so the platform can deduplicate them.

Campaign values are limited to the recognized UTM fields and short source labels. Device Pulse does not place an email address in an analytics event name, page URL, or public log. Debug and test-event codes are temporary controls and must be removed after validation.

International visitors and legal rights

The publication is operated for a U.S. professional audience, but public pages can be reached elsewhere. Privacy rights differ by location. A valid request for access, correction, deletion, restriction, or objection will be evaluated under the law that applies to the requester and the data. Identity may need to be verified before a request is completed.

Some service providers may process data in the United States or another country where they operate. Provider contracts and technical settings determine those transfers. This page will be updated if the publication adds a provider or use that changes the description materially.

Do not send sensitive information

A newsletter reply is not a secure channel for patient, employee, or transaction records. Do not send diagnoses, images, medical record numbers, dates of birth, payment details, passwords, equipment financing applications, or confidential contracts. If the publisher requests documentation for a correction, redact personal and confidential fields before sharing it and use an agreed secure channel.

Source suggestions should use public links where possible. A correction can often be investigated from an FDA record, SEC filing, study identifier, or manufacturer notice without collecting personal data from a reader or medical practice at any time.