Source
Consent & visitor tracking — found from sitemap — ABsmartly
Checked for ABsmartly on 1 Oct 2026
- Page
- https://absmartly.com/gdpr-and-hipaa-compliance-policy
- Checked
- 1 Oct 2026, 10:28 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:6e390a20f43ecdc05271df4493043c19cb72987d82609741b0ca02efb0180102
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
GDPR HIPAA commitment Report an error
“At ABsmartly we take our responsibilities under the General Data Protection Regulation (GDPR) very seriously. In addition to our obligations deriving from the GDPR and to further our business we've voluntarily committed to the Health Insurance Portability and Accountability Act (HIPAA).”
-
Dsar processing time Report an error
“Requests made must be complied within one month of receipt and immediately forwarded to the DPO and are processed free of charge.”
-
Data controller role Report an error
“As the Data Controller, ABsmartly is responsible for establishing policies and procedures in order to comply with data protection law.”
-
Dpia conducted Report an error
“a Data Protection Impact Assessment (DPIA) is carried out;”
-
Third party DPA required Report an error
“agree to a written data processing agreement;”
-
Privacy by design Report an error
“ABsmartly has to ensure that by default only personal data which is necessary for each specific purpose is processed.”
-
Policy review frequency Report an error
“ABsmartly will continue to review the effectiveness of this policy to ensure it is achieving its stated objectives on at least an annual basis and more frequently if required taking into account changes in the law and organizational or security changes.”
-
Policy last updated Report an error
“This policy was last updated on 30 April 2021.”
-
Eea transfer safeguards Report an error
“the particular country provides appropriate safeguards such as binding corporate rules, standard contractual clauses approved by the European Commission, an approved code of conduct or a certification mechanism;”
-
Marketing consent required Report an error
“A data subject’s prior consent is required for electronic direct marketing (for example, by email, text, or automated calls).”
-
Staff training Report an error
“ABsmartly is required to ensure that all staff members are adequately trained and compliance with the GDPR/ HIPAA is possible. We also regularly test our policies, systems, and processes to assess and ensure compliance.”
-
Sdk deidentification Report an error
“For this reason, all Personal Data, Personal Identity information and Personal Health Information processed is de-identified using state of the art technical, and physical safeguards and operate a firm system of policies, confidentiality agreements, digital safeguards, and procedures to ensure the highest level of administrative protection.”
-
Device media controls Report an error
“It is the policy of ABsmartly to ensure the privacy and security of Personal Data, Personal Identity Information, and Personal Health Information in the maintenance, retention, and eventual destruction/disposal of such media.”
-
Entity Report an error
“ABsmartly B.V. Keizersgracht 520 H 1017 EK, Amsterdam The Netherlands”
-
Breach documentation Report an error
“Article 33(5) requires that ABsmartly must maintain documentation on data breaches, their nature, and remedial action taken.”
-
Data flow mapping Report an error
“ABsmartly uses to identify the elements of personal data that are being processed, data flow, and mapping tools.”
-
Record keeping Report an error
“The GDPR/HIPAA requires ABsmartly to keep full and accurate records of all data processing activities.”
-
Subprocessors page Report an error
“Subprocessors”
-
Footnote about origin Report an error
“ABsmartly is a leading experimentation platform built for smart teams by the folks who architected the A/B testing tool at Booking.com.”
3 facts read from this page are not shown because they could not be confirmed on the page as captured.