Cookie Policy

1.What this policy covers

1.1 This Cookie Policy describes how SDRclose, a product of BiopharmaWatch LLC, uses cookies and similar browser storage on www.sdrclose.com and in the SDRclose web application (together, the "Site"). It should be read with our Privacy Policy, which describes how we handle personal information more broadly.

1.2 It applies to visitors to the website and to signed-in users of the application. It does not cover websites we link to, or the third-party services described in section 3 and section 5, which operate under their own policies.

1.3 This policy is a notice rather than a contract. Where it overlaps with the Terms of Service or the Data Processing Addendum, those documents take precedence in the order set out in the Terms of Service.

2.Cookies and browser storage explained

2.1 A cookie is a small text file that a website places in the browser and reads back on later visits, so the site can recognize a returning browser, keep a user signed in or remember a setting.

2.2 Browser storage, often called local storage or session storage, does a similar job. The data stays in the browser and is read by the site's own code when needed, rather than being sent with every request. Privacy laws generally treat cookies and browser storage alike, and this policy covers both.

2.3 Stored items fall into four common categories: strictly necessary items, without which the service cannot work; functional items that remember a user's choices; analytics items that measure how a site is used; and advertising items that follow people across sites to build profiles. SDRclose uses only the first two, and every item we set is first-party, meaning it is set by the Site itself and not by another domain.

3.What we store and why

3.1 The table below lists everything SDRclose stores in the browser, together with the cookies a user may encounter on the hosted pages of our payment processor. We update it whenever the service changes.

4.What we do not use

4.1 We do not set advertising cookies, and we do not allow advertising networks to place cookies or pixels on the Site. We do not embed third-party analytics trackers, session-recording tools, heat maps or social media plug-ins that report visitor activity to another company.

4.2 We do not take part in cross-site or cross-device tracking, we do not build advertising profiles, and we do not sell or share personal information for cross-context behavioral advertising.

4.3 Because we set no non-essential cookies, the Site displays no consent banner. There is nothing to accept or reject: the items in section 3 are either required for the service to work or serve only to remember a user's own choices.

4.4 Because we do not track visitors across sites, we take no additional action in response to a Do Not Track signal or to an opt-out preference signal such as Global Privacy Control. There is no tracking, sale or sharing for such a signal to stop.

5.Third-party content delivery

5.1 To load quickly and consistently, the Site serves some web fonts and some front-end libraries from third-party content delivery providers rather than from our own servers.

5.2 When a browser requests one of these files, the provider receives what any web server receives in order to respond: the requesting IP address, the file requested and browser details such as the user agent. The provider processes that information under its own privacy terms.

5.3 We attach no identifier of ours to these requests. The provider does not receive the session token, the account identity or any information about what a user does inside the application, and we receive no analytics about individual visitors in return.

5.4 A visitor who prefers not to load these files can block third-party requests in the browser or with an extension. The website remains readable, although fonts fall back to the browser's defaults and some parts of the application may not display as designed.

6.Tracking in email sent through SDRclose

6.1 Separately from anything stored in the browser, the platform can record when a message sent by a customer is opened and when a link inside it is clicked. That tracking concerns email a customer sends to its own prospects, not visitors to the Site, and is described in the Privacy Policy at section 10.

6.2 Tracking is controlled by the customer. The account-level default is off, and a customer can enable it for each sequence separately. Where it is enabled, the customer, as the controller of that outreach, is responsible for the tracking and for describing it in its own privacy notice.

6.3 Where tracking is on, an open is recorded when the recipient's mail client loads remote images, and a click is recorded when a tracked link is followed. Each event is stored with a timestamp against the prospect record for that campaign only, and is not combined across customers, sold or used for advertising.

6.4 A recipient who does not want to be tracked can set their mail client not to load remote images, and can use the unsubscribe link in any message, which removes them from the sequence permanently.

7.Your choices

7.1 Browser settings. Every major browser lets a user view, block and delete cookies and browser storage, for all sites or for specific ones. Clearing storage for the Site signs the user out; signing in again issues a new session token, and interface preferences return to their defaults. In a private or incognito window, both items are deleted when the window closes.

7.2 Third-party content and payment pages. Requests to content delivery providers can be blocked as described in section 5. Choices about cookies on the payment processor's hosted pages are made on those pages, under its own policy.

7.3 Email tracking. Customers turn open and click tracking on or off per sequence in the application. Recipients can decline remote images or unsubscribe as described in section 6.

7.4 Privacy rights. Rights to access, correct or delete personal information, and how to exercise them, are set out in the Privacy Policy and summarized in the Privacy Center.

8.Changes to this policy

8.1 We may update this policy when the service changes, when a stored item is added or removed, or when the law requires. The effective date at the top of the page shows when the current version took effect.

8.2 If we ever introduce a cookie or stored item that is neither strictly necessary nor functional, we will update this policy and, where the law requires, obtain consent before it is set. We give notice of material changes in the application or by email to the account address before they take effect.

9.How to contact us

9.1 Questions about this policy, about anything stored in the browser, or about tracking in a message received through SDRclose can be sent through the contact form on our website. Data protection matters are handled by the SDRclose team, which responds by written message during business hours, in English.

9.2 This policy is published by BiopharmaWatch LLC, the operator of SDRclose. Our other legal documents are collected on the Legal page.