Anaemia

Red cell physiology

Red cell mass increases by 25-30% but not enough to counter dilutional increase in plasma volume (50%) leading to a drop in haemoglobin (JPAC)
Iron deficiency is a problem despite a relative macrocytosis in pregnancy therefore can be misleadingly normocytic
Iron deficiency can cause maternal fatigue and emotional disturbance, and if profoundly deplete, an increased risk of pre-term delivery and delayed development in the newborn (JPAC)
Early replenishment of iron protects the mother and unborn child, and decreases the need for transfusions
Folate demands increase but these are usually well met by recommended folate supplementation for neural tube defects, in the absence of causes for malabsorption
Prophylactic iron supplementation is recommended in areas with a high prevalence of malnutrition (WHO Iron and Folate Supplementation guidance) but not in routine UK practice due to the risk of high haemoglobin levels and side-effects of the iron replacement

The approach to assessing a pregnant woman with anaemia is as follows;

Further investigation is indicated as per BCSH guidance if haemoglobin is below the following thresholds;
- 1st trimester; Hb <110
- 2nd/3rd trimester; Hb <105
- Postpartum; Hb <100
Check ferritin and replace if deficient (BCSH suggest <30 as a threshold for treatment)
Consider other causes than pregnancy alone if anaemia more profound than expected with physiological changes e.g malabsorption, coeliac etc
Dietary changes can be attempted first line if deficiency not severe or woman too symptomatic. Advice includes;
- Eat iron rich foods such as red meats, fish and poultry
- Phytate in cereals and tannins in tea decrease iron absorption and should be avoided at meal times
- Vitamin C increases iron absorption-take around meals to enhance iron absorption
If dietary iron advice is not appropriate, iron should be replaced orally as first-line and should be continued 6 weeks post-partum. If not tolerated, dose can be reduced and if still not tolerated IV iron can be used after the first trimester (JPAC)
Check B12 and folate although unlikely to be folate deficient if taking supplementation and B12 deficiency rare in pregnancy
- Folate should be replaced with 5mg daily if deplete (JPAC)
If an acute drop in Hb consider bleeding or other less common causes such as HELLP syndrome/ microangiopathy. These are normally associated with thrombocytopenia and a very unwell patient (JPAC)
Transfusion, if needed, should be with CMV negative products
All blood given to pregnant women or women of childbearing age should be matched for ABO, Rh type and K (rather than standard ABO and D) due to the risk of formation of antibodies which could cause haemolytic disease of the foetus and newborn in subsequent pregnancies (or less commonly during the current pregnancy)

Specific references;

Thrombocytopenia

Quick tip; Most experts recommend a lower limit of normal for platelets in pregnancy as 100 ×10⁹/L

Large studies have shown 12% of pregnant woman can have a platelet count less than 150×10⁹/L by late pregnancy.¹ Therefore, most experts recommend the lower limit of normal for platelets in pregnancy to be classed as 100-115 ×10⁹/L.^2,3

Thrombocytopenia between 100-150 ×10⁹/L will not usually affect the woman’s pregnancy. However, as a rule of thumb platelet counts of <80 ×10⁹/L will have an impact on the ability to have an epidural and platelets <50 ×10⁹/L will have implications for caesarean section and spontaneous vaginal delivery.⁴

Common causes (not an exhaustive list):

Gestational thrombocytopenia
Usually occurs in the third trimester and causes mild thrombocytopenia i.e platelets 100-150×10⁹/L, but they can go as low as 70 ×10⁹/L³. This is caused by normal physiological dilutional effects and increased platelet destruction and accounts for approximately 75% of thrombocytopenia in pregnancy.
The platelet count should improve to normal by 12 weeks post-partum.
Platelet counts of <70 ×10⁹/L should prompt further investigation as gestational thrombocytopenia doesn’t typically cause platelets <70 ×10⁹/L. A platelet count of <100 ×10⁹/L may also merit referral to allow preparation for delivery/neuraxial anaesthesia.
Acute viral infections
Medications
Check full medication history. Consider heparin induced thrombocytopenia (HIT) if the patient is on treatment dose low molecular weight heparin in pregnancy with new onset thrombocytopenia within 5-10 days.
Falsely low count caused by platelet clumping in EDTA or presence of large platelet causing analyser to underestimate platelet count- best ruled out by a blood film and then repeat platelet count in citrate (blue coag tube).
B12 and/or folate deficiency
Immune thrombocytopenia
Caused by platelet destruction due to platelet auto-antibodies. Thrombocytopenia can vary from mild to very severe (e.g <5 ×10⁹/L). Patients with ITP require monitoring during pregnancy and after delivery, and may require treatment - there is a higher risk of maternal bleeding when the platelet count is <50 ×10⁹/L at delivery. There is a risk of thrombocytopenia in the newborn which is importantly not proportional to maternal platelet count e.g Mother’s platelet count could be 70 ×10⁹/L and foetus’s could be <5 ×10⁹/L and vice versa.
ITP accounts for approximately 5% of cases of thrombocytopenia in pregnancy and is a diagnosis of exclusion.
Antiphospholipid syndrome and SLE
Disseminated intravascular coagulation
In pregnancy most often occurs in sepsis or haemorrhage.
Thrombotic thrombocytopenic purpura
There is an increased risk of TTP in pregnancy. It is a life-threatening condition with low platelets, haemolytic anaemia, renal impairment, neurological symptoms and fever but not all need to be present for a diagnosis. TTP can present at any time in the pregnancy. Needs urgent obstetric and haematology review.
Pre-eclampsia
Pre-eclampsia is a disease occurring in the second half of pregnancy (after 20 weeks gestation), and conventionally characterised by pregnancy-induced hypertension, with proteinuria and often oedema. Needs urgent obstetric review.
HELLP (haemolysis, elevated liver enzymes and low platelets) syndrome
This usually presents in women who have pre-eclampsia or eclampsia, therefore occurs in the last half of the pregnancy. 70% of cases present before delivery, peaking between 27 and 37 weeks of gestation but it can occur earlier or later. 30% of women with HELLP syndrome present postpartum, usually within 48 hours of delivery. Requires urgent obstetric review.
Rare causes;
Acute fatty liver- tends to present in late pregnancy with nausea, vomiting and abdominal pain, fevers, headache and jaundice. Needs urgent obstetric review.
Hereditary thrombocytopenia accounts for <1% thrombocytopenia in pregnancy.
Type 2b Von Willebrand disease.
Bone marrow disorders- Women can still present with leukaemia or lymphoma in pregnancy.

Work up

History
Is the patient well?
Any recent viral infections?
Change to medication?
Patient history of previous thrombocytopenia inside/outside pregnancy?
Family history of bleeding problems both inside or outside of pregnancy?
Does the patient have a personal history of bleeding problems outside of pregnancy?
Gestation at onset can gives clues to aetiology (not an exhaustive list)
Anytime; ITP, TTP.
Second and third trimesters; Gestational thrombocytopenia.
After 20 weeks; Pre-eclampsia, HELLP.
After 35 weeks; Fatty liver of pregnancy/HELLP/Pre-eclampsia.
Examination
Any bruises or petechia? More likely to be relevant if large bruises or raised from skin.
Any lymphadenopathy?
Any features of underlying connective tissue disease?
Investigation
- Repeat FBC if first instance of low platelets to confirm.
- Blood film- (please add clinical details including gestation to aid film interpretation) for B12/folate deficiency/giant platelets/platelet clumping/red cell fragmentation.
- Send a citrate (blue coag tube) for FBC if there is platelet clumping on the film, or a flow cytometry sample if large/giant platelets are seen for an “immuno-platelet count”.
- U+E for renal impairment- TTP/HUS.
- LFTs- check for high bilirubin in haemolysis (TTP, HUS) or deranged LFTs in HELLP/acute fatty liver.
- Coagulation screen (DIC).
- Autoantibody screen +- Double stranded DNA.
- Blood pressure and urine dipstick for protein.
- HIV, Hep B and Hep C testing.

Action required

If the patient is otherwise well, with no evidence of other possible aetiologies and the other FBC parameters and blood film, U+E and LFTs and baseline observations are all normal then a patient with platelets >100 ×10⁹/L will need to be informed their platelet count is low and it will need to be monitored during the pregnancy at least every 4 weeks.

Platelet counts of <100 ×10⁹/L only occur in approx. 1% of pregnant woman so referral for specialist investigation in secondary care is then appropriate (check local guidance for referral threshold).

If the patient is unwell with thrombocytopenia or is bleeding in association with thrombocytopenia then they require urgent assessment.

An FBC should be performed at 12 weeks post-partum to ensure the thrombocytopenia has resolved as gestational thrombocytopenia should have resolved by this time- consider onwards referral if the thrombocytopenia is still persistent and the cause unknown.

References

Boehlen F, Hohfeld P, Extermann P et al. Platelet count at term pregnancy: a reappraisal of the threshold. Obstetrics and Gynecology 2000; 95:29–33.

Pavord, S., & Hunt, B. (Eds.). (2010). The Obstetric Hematology Manual. Cambridge: Cambridge University Press. p5

ASH Quick reference 2013 Clinical practice guide on thrombocytopenia in pregnancy. A Rajasekhar et al.

Estcourt, L. J., Birchall, J. , Allard, S. , Bassey, S. J., Hersey, P. , Kerr, J. P., Mumford, A. D., Stanworth, S. J., Tinegate, H. and , (2017), Guidelines for the use of platelet transfusions. Br J Haematol, 176: p377 doi:10.1111/bjh.14423

The contents of these pages were created with great care. For the accuracy, completeness and timeliness of content, we can not take any responsibility. As a service provider we are responsible according §7 1 TMG for own contents on these pages under the general laws. According to §8 to 10 TMG we are not obligated as a service provider to monitor transmitted or stored information, or to investigate circumstances that indicate illegal activity. Obligations to remove or block the use of information under the general laws remain unaffected. However, a relevant liability is only possible from the date of knowledge of a specific infringement. Upon notification of such violations, we will remove the content immediately.

Privacy Policy of Buku Haematology

This Application collects some Personal Data from its Users.

This document can be printed for reference by using the print command in the settings of any browser.

Owner and Data Controller

Buku Haematology - Newcastle - United Kingdom

Owner contact email: bukuhaem@gmail.com

Types of Data collected

Buku Haematology (The Owner) records no personally identifiable data. The following usage data are collected by default by the host of our App, AppYourself GmbH. This data is then managed as per their privacy policy below.

System Version
Smartphone model
Hardware ID (https://help.pushwoosh.com/hc/en-us/articles/360000365023-What-is-a-HWID-)
Opening of each module together with the time of the action
Date of register

Data will only be shared by AppYourself in accordance with their Privacy Policy.

Buku Haematology (owned by Buku Tech Ltd) retain none of this data. We can see our user traffic, country of access and modules accessed. Unique identifiers are generated for each user by the AppYourself system to show the number of times the App is accessed and which modules are viewed by individuals. No further information about the individual is given.

AppYourself privacy policy

We (Buku Haematology) have removed those elements that we have chosen not to include in the App (such as Facebook integration for example). Please contact privacy@appyourself.net if you have any questions about personal data storage.

Among the types of Personal Data that this Application collects, by itself or through third parties, there are: Cookies; Usage Data; various types of Data; unique device identifiers for advertising (Google Advertiser ID or IDFA, for example); Storage permission; geographic position.

Complete details on each type of Personal Data collected are provided in the dedicated sections of this privacy policy or by specific explanation texts displayed prior to the Data collection.

Personal Data may be freely provided by the User, or, in case of Usage Data, collected automatically when using this Application.

Unless specified otherwise, all Data requested by this Application is mandatory and failure to provide this Data may make it impossible for this Application to provide its services. In cases where this Application specifically states that some Data is not mandatory, Users are free not to communicate this Data without consequences to the availability or the functioning of the Service.

Any use of Cookies – or of other tracking tools – by this Application or by the owners of third-party services used by this Application serves the purpose of providing the Service required by the User, in addition to any other purposes described in the present document and in the Cookie Policy, if available.

Mode and place of processing the Data

Methods of processing

In some cases, the Data may be accessible to certain types of persons in charge, involved with the operation of this Application (administration, sales, marketing, legal, system administration) or external parties (such as third-party technical service providers, mail carriers, hosting providers, IT companies, communications agencies) appointed, if necessary, as Data Processors by the Owner. The updated list of these parties may be requested from the Owner at any time.

Legal basis of processing

The Owner may process Personal Data relating to Users if one of the following applies:

Users have given their consent for one or more specific purposes. Note: Under some legislations the Owner may be allowed to process Personal Data until the User objects to such processing (“opt-out”), without having to rely on consent or any other of the following legal bases. This, however, does not apply, whenever the processing of Personal Data is subject to European data protection law;
provision of Data is necessary for the performance of an agreement with the User and/or for any pre-contractual obligations thereof;
processing is necessary for compliance with a legal obligation to which the Owner is subject;
processing is related to a task that is carried out in the public interest or in the exercise of official authority vested in the Owner;
processing is necessary for the purposes of the legitimate interests pursued by the Owner or by a third party.

In any case, the Owner will gladly help to clarify the specific legal basis that applies to the processing, and in particular whether the provision of Personal Data is a statutory or contractual requirement, or a requirement necessary to enter into a contract.

Retention time

Personal Data shall be processed and stored for as long as required by the purpose they have been collected for.

The Owner records no personal data, and therefore usage data is the only data retained, and this is retained by AppYourself.

Once the retention period expires, Personal Data shall be deleted. Therefore, the right to access, the right to erasure, the right to rectification and the right to data portability cannot be enforced after expiration of the retention period.

The purposes of processing

The Data concerning the User is collected for the following purposes: Analytics, Hosting and backend infrastructure, Data transfer outside the EU, Device permissions for Personal Data access, Displaying content from external platforms, Infrastructure monitoring, Registration and authentication, and Location-based interactions.

For specific information about the Personal Data used for each purpose, the User may refer to the section “Detailed information on the processing of Personal Data”.

Detailed information on the processing of Personal Data

Key facts about data control by AppYourself;

The servers used by AppYourself are located in Europe (and thus protected by GDPR) and the US.
The data is hosted on AWS infrastructure, but AWS does not store any user-related data. User-related data is stored by AppYourself in Google Firebase. The storage is located in USA.
Although the Google Firebase server (based in the US) is not secured by GDPR they operate under the EU-US privacy shield. For more information about cloud-sided encryption see; https://firebase.google.com/support/privacy#data_encryption. Google Firebase is also compliant with ISO27001. For more information see; https://firebase.google.com/support/privacy#firebase_is_certified_under_major_privacy_and_security_standards
User data is stored for up to 90 days after App subscription is terminated. Furthermore, users have the right to delete their profile at any time. By doing so, their account is irretrievably deleted.
In case of a data breach by AppYourself, this can be reported via https://iapp.org/resources/article/how-to-notify-your-dpa-of-a-data-breach/

Personal Data is collected for the following purposes and using the following services:

Analytics

The services contained in this section enable the Owner to monitor and analyze web traffic and can be used to keep track of User behavior.

Google Analytics for Firebase (Google LLC)

Google Analytics for Firebase or Firebase Analytics is an analytics service provided by Google LLC.

In order to understand Google's use of Data, consult Google's partner policy.

Firebase Analytics may share Data with other tools provided by Firebase, such as Crash Reporting, Authentication, Remote Config or Notifications. The User may check this privacy policy to find a detailed explanation about the other tools used by the Owner.

This Application uses identifiers for mobile devices and technologies similar to cookies to run the Firebase Analytics service.

Users may opt-out of certain Firebase features through applicable device settings, such as the device advertising settings for mobile phones or by following the instructions in other Firebase related sections of this privacy policy, if available.

Personal Data processed: Cookies; unique device identifiers for advertising (Google Advertiser ID or IDFA, for example); Usage Data.

Place of processing: United States – Privacy Policy. Privacy Shield participant.

Data transfer outside the EU

Any data collected by AppYourself is transferred in keeping with these statements.

The Google Firebase services used to store and transfer data provide HTTPS encryption during information transit. Data encryption is also provided for cloud data storage. See https://firebase.google.com/support/privacy#data_encryption for more information.

Data transfer from the EU and/or Switzerland to the U.S based on Privacy Shield (this Application)

If this is the legal basis, the transfer of Personal Data from the EU or Switzerland to the US is carried out according to the EU - U.S. and Swiss - U.S. Privacy Shield.

In particular, Personal Data is transferred to services that self-certify under the Privacy Shield framework and therefore guarantee an adequate level of protection of such transferred Data. All services are listed within the relevant section of this document and those that adhere to Privacy Shield can be singled out by checking their privacy policy and possibly also by specifically checking for Privacy Shield adherence in the official Privacy Shield List. Privacy Shield also specifically guarantees rights to Users which can be found in its most current form on the website run by the US Department of Commerce.

Personal Data may be transferred from within the EU or Switzerland to the U.S. to services that are not, or not anymore, part of Privacy Shield, only based on other valid legal grounds. Users can ask the Owner to learn about such legal grounds.

Personal Data processed: various types of Data.

Data transfer to countries that guarantee European standards (this Application)

If this is the legal basis, the transfer of Personal Data from the EU to third countries is carried out according to an adequacy decision of the European Commission.

The European Commission adopts adequacy decisions for specific countries whenever it considers that country to possess and provide Personal Data protection standards comparable to those set forth by EU data protection legislation. Users can find an updated list of all adequacy decisions issued on the European Commission's website.

Personal Data processed: various types of Data.

Device permissions for Personal Data access

This Application requests certain permissions from Users that allow it to access the User's device Data as described below.

Device permissions for Personal Data access (this Application)

This Application requests certain permissions from Users that allow it to access the User's device Data as summarized here and described within this document.

Personal Data processed: Storage permission.

Hosting and backend infrastructure

This type of service has the purpose of hosting Data and files that enable this Application to run and be distributed as well as to provide a ready-made infrastructure to run specific features or parts of this Application. Some of these services work through geographically distributed servers, making it difficult to determine the actual location where the Personal Data are stored.

Firebase Cloud Functions (Google LLC)

Firebase Cloud Functions is a hosting and backend service provided by Google LLC.

Personal Data processed: Usage Data; various types of Data as specified in the privacy policy of the service.

Place of processing: United States – Privacy Policy. Privacy Shield participant.

Firebase Cloud Firestore (Google LLC)

Firebase Cloud Firestore is a hosting and backend service provided by Google LLC.

Personal Data processed: Usage Data; various types of Data as specified in the privacy policy of the service.

Place of processing: United States – Privacy Policy. Privacy Shield participant.

Firebase Realtime Database (Google LLC)

Firebase Realtime Database is a hosting and backend service provided by Google LLC.

Personal Data processed: Usage Data; various types of Data as specified in the privacy policy of the service.

Place of processing: United States – Privacy Policy. Privacy Shield participant.

Firebase Cloud Storage (Google LLC)

Firebase Cloud Storage is a hosting service provided by Google LLC.

Personal Data processed: Usage Data; various types of Data as specified in the privacy policy of the service.

Place of processing: United States – Privacy Policy. Privacy Shield participant.

Interoute (Interoute Communications Limited.)

Interoute is a hosting service provided by Interoute Communications Limited.

Personal Data processed: various types of Data as specified in the privacy policy of the service.

Place of processing: United Kingdom – Privacy Policy.

Infrastructure monitoring

This type of service allows this Application to monitor the use and behavior of its components so its performance, operation, maintenance and troubleshooting can be improved.

Which Personal Data are processed depends on the characteristics and mode of implementation of these services, whose function is to filter the activities of this Application.

Sentry (Functional Software, Inc. )

Sentry is a monitoring service provided by Functional Software, Inc. .

Personal Data processed: various types of Data as specified in the privacy policy of the service.

Place of processing: United States – Privacy Policy.

Managing contacts and sending messages

This type of service makes it possible to manage a database of email contacts, phone contacts or any other contact information to communicate with the User.

These services may also collect data concerning the date and time when the message was viewed by the User, as well as when the User interacted with it, such as by clicking on links included in the message.

Firebase Cloud Messaging (Google Inc.)

Firebase Cloud Messaging is a message sending service provided by Google, Inc. Firebase Cloud Messaging allows the Owner to send messages and notifications to Users across platforms such as Android, iOS, and the web. Messages can be sent to single devices, groups of devices, or specific topics or User segments.

Personal Data processed: various types of Data as specified in the privacy policy of the service.

Place of processing: United States – Privacy Policy. Privacy Shield participant.

Further information about Personal Data

Push notifications

This Application may send push notifications to the User.

Unique device identification

This Application may track Users by storing a unique identifier of their device, for analytics purposes or for storing Users' preferences.

The rights of Users

Users may exercise certain rights regarding their Data processed by AppYourself.

In particular, Users have the right to do the following:

Withdraw their consent at any time. Users have the right to withdraw consent where they have previously given their consent to the processing of their Personal Data.
Object to processing of their Data. Users have the right to object to the processing of their Data if the processing is carried out on a legal basis other than consent. Further details are provided in the dedicated section below.
Access their Data. Users have the right to learn if Data is being processed by the Owner, obtain disclosure regarding certain aspects of the processing and obtain a copy of the Data undergoing processing.
Verify and seek rectification. Users have the right to verify the accuracy of their Data and ask for it to be updated or corrected.
Restrict the processing of their Data. Users have the right, under certain circumstances, to restrict the processing of their Data. In this case, the Owner will not process their Data for any purpose other than storing it.
Have their Personal Data deleted or otherwise removed. Users have the right, under certain circumstances, to obtain the erasure of their Data from the Owner.
Receive their Data and have it transferred to another controller. Users have the right to receive their Data in a structured, commonly used and machine readable format and, if technically feasible, to have it transmitted to another controller without any hindrance. This provision is applicable provided that the Data is processed by automated means and that the processing is based on the User's consent, on a contract which the User is part of or on pre-contractual obligations thereof.
Lodge a complaint. Users have the right to bring a claim before their competent data protection authority.

Cookie Policy

This Application uses Cookies and other Identifiers. To learn more, the User may consult the Cookie Policy.

Additional information about Data collection and processing

Legal action

The User's Personal Data may be used for legal purposes by the Owner in Court or in the stages leading to possible legal action arising from improper use of this Application or the related Services.

The User declares to be aware that the Owner may be required to reveal personal data upon request of public authorities.

Additional information about User's Personal Data

In addition to the information contained in this privacy policy, this Application may provide the User with additional and contextual information concerning particular Services or the collection and processing of Personal Data upon request.

System logs and maintenance

For operation and maintenance purposes, this Application and any third-party services may collect files that record interaction with this Application (System logs) use other Personal Data (such as the IP Address) for this purpose.

Information not contained in this policy

More details concerning the collection or processing of Personal Data may be requested from the Owner at any time. Please see the contact information at the beginning of this document.

How “Do Not Track” requests are handled

This Application does not support “Do Not Track” requests.

To determine whether any of the third-party services it uses honor the “Do Not Track” requests, please read their privacy policies.

Changes to this privacy policy

The Owner reserves the right to make changes to this privacy policy at any time by notifying its Users on this page and possibly within this Application and/or - as far as technically and legally feasible - sending a notice to Users via any contact information available to the Owner. It is strongly recommended to check this page often, referring to the date of the last modification listed at the bottom.

Should the changes affect processing activities performed on the basis of the User’s consent, the Owner shall collect new consent from the User, where required.

Definitions and legal references

Personal Data (or Data)

Any information that directly, indirectly, or in connection with other information — including a personal identification number — allows for the identification or identifiability of a natural person.

Usage Data

Information collected automatically through this Application (or third-party services employed in this Application), which can include: the IP addresses or domain names of the computers utilized by the Users who use this Application, the URI addresses (Uniform Resource Identifier), the time of the request, the method utilized to submit the request to the server, the size of the file received in response, the numerical code indicating the status of the server's answer (successful outcome, error, etc.), the country of origin, the features of the browser and the operating system utilized by the User, the various time details per visit (e.g., the time spent on each page within the Application) and the details about the path followed within the Application with special reference to the sequence of pages visited, and other parameters about the device operating system and/or the User's IT environment.

User

The individual using this Application who, unless otherwise specified, coincides with the Data Subject.

Data Subject

The natural person to whom the Personal Data refers.

Data Processor (or Data Supervisor)

The natural or legal person, public authority, agency or other body which processes Personal Data on behalf of the Controller, as described in this privacy policy.

Data Controller (or Owner)

The natural or legal person, public authority, agency or other body which, alone or jointly with others, determines the purposes and means of the processing of Personal Data, including the security measures concerning the operation and use of this Application. The Data Controller, unless otherwise specified, is the Owner of this Application.

This Application

The means by which the Personal Data of the User is collected and processed.

Service

The service provided by this Application as described in the relative terms (if available) and on this site/application.

European Union (or EU)

Unless otherwise specified, all references made within this document to the European Union include all current member states to the European Union and the European Economic Area.

Cookies

Small sets of data stored in the User's device.

Legal information

This privacy statement has been prepared based on provisions of multiple legislations, including Art. 13/14 of Regulation (EU) 2016/679 (General Data Protection Regulation).

This privacy policy relates solely to this Application, if not stated otherwise within this document.

Latest update: May 17, 2018

Cookie Policy of Buku Haematology

Cookies and other Identifiers consist of portions of code placed on the User’s device that assist the Owner in providing the Service according to the purposes described.

Some of the purposes for which Identifiers are used may also require the User's consent. Whenever consent is given, it can be freely withdrawn at any time following the instructions provided in this document.

Activities strictly necessary for the operation of this Application and delivery of the Service

This Application uses Cookies or other Identifiers to carry out activities that are strictly necessary for the operation or delivery of the Service and, therefore, do not require Users to consent. Users can disable such Identifiers by modifying their browser or device settings as described in more detail within this document, but this may affect core operational functions or result in the unavailability of the Service.

Other activities

Experience enhancement

This Application uses Cookies or other Identifiers to provide a personalized user experience by improving the quality of preference management options, and by enabling interaction with external networks and platforms.

Measurement

This Application uses Cookies or other Identifiers to measure traffic and analyze User behavior with the goal of improving the Service.

Analytics

The services contained in this section enable the Owner to monitor and analyze web traffic and can be used to keep track of User behavior.

Google Analytics for Firebase (Google LLC)

Google Analytics for Firebase or Firebase Analytics is an analytics service provided by Google LLC.

In order to understand Google's use of Data, consult Google's partner policy.

This Application uses identifiers for mobile devices and technologies similar to cookies to run the Firebase Analytics service.

Personal Data processed: Cookies, unique device identifiers for advertising (Google Advertiser ID or IDFA, for example) and Usage Data.

Place of processing: United States – Privacy Policy. Privacy Shield participant.

How to provide or withdraw consent

Users can provide or withdraw consent to the use of Cookies and other Identifiers by setting their preferences within the cookie notice or by updating such preferences via the relevant consent-preferences widget accordingly, if available.

Additionally, Users can manage preferences regarding Identifiers directly from within their own device settings and prevent – for example – the storing of third-party Identifiers. It is also possible, via relevant browser or device features, to delete previously stored Identifiers, including those used to remember the User’s initial consent. Users can, for example, find information about how to manage Identifiers in the most commonly used browsers at the following addresses: Google Chrome, Mozilla Firefox, Apple Safari and Microsoft Internet Explorer.

With regard to any Identifiers stored by third parties, Users can manage their preferences and withdraw their consent by clicking the related opt-out link (where provided), by using the means indicated in the third party's privacy policy, or by contacting the third party.

Notwithstanding the above, Users are hereby informed that they may follow the instructions provided by YourOnlineChoices (EU), the Network Advertising Initiative (US) and the Digital Advertising Alliance (US), DAAC (Canada), DDAI (Japan) or other similar services. Such initiatives allow Users to select their tracking preferences for most of the advertising tools. The Owner thus recommends that Users make use of these resources in addition to the information provided in this document.

Owner and Data Controller

Buku Haematology - Newcastle - United Kingdom

Owner contact email: bukuhaem@gmail.com

Since the storing of third-party Cookies and other Identifiers through the services used within this Application cannot be technically controlled by the Owner, any specific references to Identifiers stored by third parties are to be considered indicative. In order to obtain complete information, the User is kindly requested to consult the privacy policies of the respective third-party services listed in this document.

Given the objective complexity surrounding technologies related to Cookies and other Identifiers, Users are encouraged to contact the Owner should they wish to receive any further information on the use of such Identifiers by this Application.

Definitions and legal references

Personal Data (or Data)

Usage Data

User

The individual using this Application who, unless otherwise specified, coincides with the Data Subject.

Data Subject

The natural person to whom the Personal Data refers.

Data Processor (or Data Supervisor)

The natural or legal person, public authority, agency or other body which processes Personal Data on behalf of the Controller, as described in this privacy policy.

Data Controller (or Owner)

This Application

The means by which the Personal Data of the User is collected and processed.

Service

The service provided by this Application as described in the relative terms (if available) and on this site/application.

European Union (or EU)

Unless otherwise specified, all references made within this document to the European Union include all current member states to the European Union and the European Economic Area.

Cookie

Cookies are Identifiers consisting of small sets of data stored in the User's browser.

Identifier

Any technology - including Cookies - that allows for the storing of information, or the accessing of already-stored information, on the User’s device.

Legal information

This privacy statement has been prepared based on provisions of multiple legislations, including Art. 13/14 of Regulation (EU) 2016/679 (General Data Protection Regulation).

This privacy policy relates solely to this Application, if not stated otherwise within this document.

Buku Medicine

Anaemia

Thrombocytopenia