Updated Dec 03rd, 2022 – The following Privacy Policy (“Privacy Policy”) applies to the Black Pearl Group Service (“The Service”).
1. Types of Information Stored and Transmitted
The Service is owned by Black Pearl Group Limited (“BPG”). BPG operate but not limited to an outbound email management and branding service (“The Service”). Types of information stored and/or transmitted include:
1.1. Company and User Details. Information about Customers (including but not limited to address, phone number, contact persons), End-Users (including but not limited to contact information, job title), Branding Features, email recipient delivery details and delivery information are stored in Service databases so that the Service can apply html formatting to outbound emails that are sent and management information to Customer.
1.2. Financial Information. Financial information that is collected is used to verify, identity and to bill Customer for the Service as applicable.
1.3. Email content. CONTENT OF DELIVERED EMAIL IS NOT STORED OR RETAINED BY BPG. Undeliverable email is stored by BPG for a maximum of 6 hours while in a re-sending cycle before it is deleted.
1.4. Demographic and profile data. Demographic and profile data may be collected by BPG to tailor BPG web site, Admin Console, Help Centre or any requested email communications, and to display information that is more relevant to Customer.
1.5. Google Analytics Advertiser Features. BPG uses Google Analytics in conjunction with their Re-targeting function. First party cookies are only used for this function outside of the BPG application.
2. Ownership of Data
As per Section 7.3 of terms and Conditions Agreement BPG acknowledges that the Customer owns Customer Data.
3. Retrieval of Data
Customer can access, modify and delete Customer Data via Admin Console. If the service is Terminated BPG will provide Customer access to, and the ability to export, the Customer Data for a commercially reasonable period of time at BPG’s then-current rates for the applicable Services. After a commercially reasonable period of time, BPG will delete Customer Data by removing pointers to it on BPG’s active servers and overwriting it over time; and upon request each party will promptly use commercially reasonable efforts to return or destroy all other Confidential Information, if any.
4. Confidential Nature of Customer Data
4.1. Protection. BPG will protect Customer Data with the same standard of care it uses to protect its own. BPG will not disclose the Customer Data, except to Affiliates, employees and agents who need to know it and who have agreed in writing to keep it confidential.
4.2. View-ship. BPG will NOT examine the content of Customer email messages without Customer consent except if:4.2.1.The New Zealand Department of Internal Affairs deems the Customer and/or End-User to be in possible violation of New Zealand law.4.2.2. BPG management deem it necessary to stop or resolve an Emergency Security Issue.
5. Customer Administration of the Services
Customer may specify one or more Administrators through the Admin Console who will have the rights to access Admin Account(s) and to administer the End User Accounts. Customer is responsible for: (a) maintaining the confidentiality of the password and Admin Account(s); (b) designating those individuals who are authorized to access the Admin Account(s); (c) ensuring that contact information for Customer’s designated Administrators is accurate and kept up- to-date in the Admin Console and (d) ensuring that all activities that occur in connection with the Admin Account(s) comply with the Terms and Conditions Agreement.
6. General Security
All facilities used to store and process Customer Data will adhere to reasonable security standards. BPG has implemented at least industry standard systems and procedures to ensure the security and confidentiality of Customer Data, protect against anticipated threats or hazards to the security or integrity of Customer Data and protect against unauthorized access to or use of Customer Data.
7. Email Communications
Customer email address is used to only send information that the Customer has requested. BPG allows you to elect to receive, or not receive, certain information from BPG. BPG adheres strictly to permission-based email policy.
8. Payment
Payments are made securely online via Credit Card or Direct Credit. BPG keep records of Customer billing information in a secure database to facilitate future payments. All Customer credit card details are stored securely to meet PCI DSS compliance.
9. Alterations to Privacy Policy
If BPG makes a material change to the Privacy Policy BPG will inform Customer via a Notification Email Address or the Admin Console, provided that Customer has subscribed with BPG to be informed about such change.
Addendum to Terms and Conditions of Service Agreement – European Union General Data Protection Regulation
This Data Processing Addendum (DPA”) constitutes an addendum to Black Pearl Mail’s Terms and Conditions of Service Agreement (the Agreement), and forms part of the Agreement between Black Pearl Mail, a New Zealand Company, Company Office Number 4064918, with offices at Ground Floor 25 Victoria Street, Petone, Lower Hutt, 5012, New Zealand (“BPG”) and the entity agreeing to these terms (“Customer”). It is effective from the date of notification to Customer. By their continued use of BPG’s services, the Customer accepts and agrees to the terms of this addendum.
1. Definitions
All capitalized terms not defined in this DPA will have the meanings set forth in the Agreement. Terms used but not defined in this DPA, such as “controller,” “data subject,” “personal data,” “processing,” and “processor” will have the same meaning as set forth in the EU Data Protection Law.
“Affiliate” means an entity that directly or indirectly controls, is controlled by or is under common control with an entity.
“Agreement” means BPG’s Terms and Conditions of Service Agreement, which govern the provision of the Services to Customer, as such terms may be updated by BPG from time to time.
“Data Protection Laws” means all data protection and privacy laws applicable to the processing of personal data under the Agreement, including, where applicable, EU Data Protection Law
“EU Data Protection Law” means (i) prior to 25 May 2018, Directive 95/46/EC of the European Parliament and of the Council on the protection of individuals with regard to the processing of personal data and on the free movement of such data (“Directive”) and on and after 25 May 2018, Regulation 2016/679 of the European Parliament and of the Council on the protection of natural persons with regard to the processing of personal data and on the free movement of such data (General Data Protection Regulation) (“GDPR”); and (ii) Directive 2002/58/EC concerning the processing of personal data and the protection of privacy in the electronic communications sector and applicable national implementations of it (as may be amended, superseded or replaced).
“EEA” means the European Economic Area, United Kingdom and Switzerland.
“Privacy Shield Principles” means the Privacy Shield Principles (as supplemented by the Supplemental Principles) contained in Annex II to the European Commission Decision C(2016)4176 of 12 July 2016 (as may be amended, superseded or replaced).
“Security Incident” means any unauthorized or unlawful breach of security that leads to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of or access to Customer data.
“Services” means any product or service provided by BPG to Customer pursuant to the agreement.
“Subprocessors” means the other processors that are used by BPG to process Personal Data.
“Subscriber Data” means any personal data that BPG processes on behalf of Customer as a processor in the course of providing Services, as more particularly described in this DPA.
2. Relationship with the Agreement
2.1 The parties agree that except for the changes made by this DPA, the Agreement remains unchanged and in full force and effect. If there is any conflict between this DPA and the Agreement, this DPA shall prevail to the extent of that conflict.
2.2 Any claims brought under or in connection with this DPA shall be subject to the terms and conditions, including but not limited to, the exclusions and limitations set forth in the Agreement.
2.3 Customer further agrees to fully indemnify BPG for any regulatory penalties incurred or damages sought by end users against BPG in relation to the Subscriber Data that arise as a result of, or in connection with, Customer’s failure to comply with its obligations under this DPA or any applicable Data Protection Laws.
2.4 No one other than a party to this DPA, its successors and permitted assignees shall have any right to enforce any of its terms.
2.5 This DPA shall be governed by and construed in accordance with governing law and jurisdiction provisions in the Agreement, unless required otherwise by applicable Data Protection Laws.
3. Scope and Applicability of this DPA
3.1 This DPA applies where and only to the extent that BPG processes Subscriber Data that originates from the EEA or that is otherwise subject to EU Data Protection Law on behalf of Customer as a processor in the course of providing Services pursuant to the Agreement.
3.2 Part A and Exhibits A and B of this DPA shall apply to the processing of Subscriber Data within the scope of this DPA from the Effective Date.
3.3 Part B shall apply to the processing of Subscriber Data within the scope of the DPA from and including 25th May 2018. For the avoidance of doubt, Part B shall apply in addition to, and not in substitution for, the terms in Part A.
Part A: General Data Protection Obligations
4. Roles and Scope of Processing
4.1 Role of the Parties. As between BPG and Customer, Customer is controller of Subscriber Data, and BPG shall process Subscriber Data only as a processor acting on behalf of Customers.
4.2 Customer Processing of Subscriber Data. Customer agrees that (i) it shall comply with its obligations as a controller under Data Protection Laws in respect of its processing of Subscriber Data and any processing instructions it issues to BPG; and (ii) it has provided notice and obtained (or shall obtain) all consents and rights necessary under Data Protection Laws for BPG to process Subscriber Data and provide the Services pursuant to the Agreement and this DPA.
4.3 BPG Processing of Subscriber Data. BPG shall process Subscriber Data only for the purposes described in this DPA and only in accordance with Customer’s documented, lawful instructions. The parties agree that this DPA and the Agreement set out the Customer’s complete and final instructions to BPG in relation to the processing of Subscriber Data and processing outside the scope of these instructions (if any) shall require prior written agreement between Customer and BPG.
4.4 Details of Data Processing.
(a) Subject matter: The subject matter of the data processing under this DPA is the Subscriber Data.
(b) Duration: As between BPG and Customer, the duration of the data processing under this DPA is until the termination of the Agreement in accordance with its terms.
(c) Purpose: The purpose of the data processing under this DPA is the provision of the Services to the Customer and the performance of BPG’s obligations under the Agreement (including this DPA) or as otherwise agreed by the parties.
(d) Nature of the processing: BPG provides email messaging, analytics technology and other related services, as described in the Agreement.
(e) Categories of data subjects: Any individual accessing and/or using the Services through the Customer’s account (“Users”); and any individual: (i) whose email address is included in the Customer’s Distribution List; (ii) whose information is stored on or collected via the Services, or (iii) to whom Users send emails or otherwise engage or communicate with via the Services (collectively, “End Users”).
(f) Subscriber and Users: Identification and contact data (name, address, title, contact details, username); financial information (credit card details, account details, payment information); employment details (employer, job title, geographic location, area of responsibility);
(g) End Users: identification and contact data (name, date of birth, gender, general, occupation or other demographic information, address, title, contact details, (including email addresses), personal interests or preferences (including purchase history, marketing preferences and publicly available social media profile information); IT information (IP addresses, usage data, cookies data, online navigation data, location data, browser data); financial information (credit card details, account details, payment information).
4.5 BPG Data rights; Notwithstanding anything to the contrary in the Agreement (including this DPA), Customer acknowledges that BPG shall have a right to use and disclose data relating to the operation, support and/or use of the Services for its legitimate business purposes, such as billing, account management, technical support, product development and sales and marketing. To the extent any such data is considered personal data under Data Protection Laws, BPG is the controller of such data and accordingly shall process such data in accordance with this BPG Privacy Policy and Data Protection Laws.
4.6 Tracking Technologies. Customer acknowledges that in connection with the performance of the Services, BPG employs the use of cookies, unique identifiers, web beacons and similar tracking technologies (“Tracking Technologies”). Customer shall maintain appropriate notice, consent, opt-in and opt-out mechanisms as are required by Data Protection Laws to enable BPG to deploy Tracking Technologies lawfully on, and collect data from, the devices of End Users.
5. Subprocessing
5.1 Authorized Subprocessors. Customer agrees that BPG may engage Subprocessors to process Subscriber Data on Customer’s behalf. The Subprocessors currently engaged by BPG and authorized by Customer are listed in Exhibit A.
5.2 Subprocessor Obligations. BPG shall:
(i) enter into a written agreement with the Subprocessor imposing data protection terms that require the Subprocessor to protect the Subscriber Data to the standard required by Data Protection Laws; and
(ii) remain responsible for its compliance with the obligations of this DPA and for any acts or omissions of the Subprocessor that cause BPG to breach any of its obligations under this DPA.
6. Security
6.1 Security Measures. BPG shall implement and maintain appropriate technical and organizational security measures to protect Subscriber Data from Security Incidents and to preserve the security and confidentiality of the Subscriber Data, in accordance with BPGs security standards described in this DPA (“Security Measures”).
6.2 Updates to Security Measures. Customer is responsible for reviewing the information made available by BPG relating to data security and making an independent determination as to whether the Services meet Customer’s requirements and legal obligations under Data Protection Laws. Customer acknowledges that the Security Measures are subject to technical progress and development and that BPG may update or modify the Security Measures from time to time provided that such updates and modifications do not result in the degradation of the overall security of the Services purchased by the Customer.
6.3 Customer Responsibilities. Notwithstanding the above, Customer agrees that except as provided by this DPA, Customer is responsible for its secure use of the Services, including securing its account authentication credentials, protecting the security of Subscriber Data when in transit to and from the Services and taking any appropriate steps to securely encrypt or backup any Subscriber Data uploaded to the Services.
6.4 BPG Disclaimer. BPG accepts no liability for breaches of Subscriber Data that are the fault of Customer. Furthermore, Customer agrees to fully indemnify BMP for any claims or penalties incurred as a result of Customer’s negligence, or failures to comply with its obligations under this DPA.
7. Compliance Verification
7.1 BPG’s Verification of Compliance. Upon reasonable request, BPG will verify its compliance with this DPA, provided that Customer shall not exercise this right more than once per year.
8. International Transfers
8.1 Data Centre Locations. BPG may transfer and process Subscriber Data anywhere in the world where BPG, its Affiliates or its Subprocessors maintain data processing operations. BPG shall at all times provide an adequate level of protection for the Subscriber Data collected, transferred, processed, or retained in accordance with the requirements of Data Protection Laws.
8.2 Alternative Transfer Mechanism. The parties agree that the data export solution identified in Section 8.2 shall not apply if and to the extent that BPG adopts an alternative data export solution with Customer for the lawful transfer of personal data (as recognized under EU Data Protection Laws) outside of the EEA (“Alternative Transfer Mechanism”), in which event, the Alternative Transfer Mechanism shall apply instead (but only to the extent such Alternative Transfer Mechanism extends to the territories to which personal data is transferred).
Part B: GDPR Obligations from 25 May 2018
9. Additional Security
9.1 Confidentiality of processing. BPG shall ensure that any person who is authorized by BPG to process Subscriber Data (including its staff, agents and subcontractors) shall be under an appropriate obligation of confidentiality (whether a contractual or statutory duty).
9.2 Security Incident Response. Upon becoming aware of a Security Incident, BPG shall notify Customer without undue delay and shall provide timely information relating to the Security Incident as it becomes known or as is reasonably requested by Customer.
10. Changes to Subprocessors
10.1 Customer request for information about, or the addition of Subprocessors. BPG shall (i) provide an up-to-date list of the Subprocessors it has appointed upon written request from Subscriber; and (ii) notify Customer (for which email shall suffice) if it adds Subprocessors at least 10 days prior to any such changes.
10.2 Customer objections to a new Subprocessor. Customer may object in writing to BPG’s appointment of a new Subprocessor within five (5) calendar days of such notice, provided that such objection is based on reasonable grounds relating to data protection. In such event, the parties shall discuss such concerns in good faith with a view to achieving resolution. If this is not possible, Customer may suspend or terminate the Agreement (without prejudice to any fees incurred by Customer prior to suspension or termination).
11. Return or Deletion of Data
11.1 Upon termination or expiration of the Agreement, BPG shall (at Customer’s election) delete or return to Customer all Subscriber Data (including copies) in its possession or control, save that this requirement shall not apply to the extent BPG is required by applicable law to retain some or all of the Subscriber Data, which Subscriber Data BPG shall securely isolate and protect from any further processing, except to the extent required by applicable law.
12. Cooperation
12.1 Requests for Subscriber Data. The Services provide Customer with a number of controls that Customer may use to retrieve, correct, delete or restrict Subscriber Data, which Customer may use to assist it in connection with its obligations under the GDPR, including its obligations relating to responding to requests from data subjects or applicable data protection authorities. To the extent that Customer is unable to independently access the relevant Subscriber Data within the Services, BPG shall (at Customer’s expense) provide reasonable cooperation to assist Customer to respond to any requests from individuals or applicable data protection authorities relating to the processing of personal data under the Agreement. In the event that any such request is made directly to BPG, BPG shall not respond to such communication directly without Customer’s prior authorization, unless legally compelled to do so. If BPG is required to respond to such a request, BPG shall promptly notify Subscriber and provide it with a copy of the request unless legally prohibited from doing so.
12.2 Law Enforcement Authority Demands. If a law enforcement agency sends BPG a demand for Subscriber Data (for example, through a subpoena or court order), BPG shall attempt to redirect the law enforcement agency to request that data directly from Customer. As part of this effort, BPG may provide Customer’s basic contact information to the law enforcement agency. If compelled to disclose Subscriber Data to a law enforcement agency, then BPG shall give Customer reasonable notice of the demand to allow Customer to seek a court order or other appropriate remedy unless BPG is legally prohibited from doing so.
12.3 Information for other purposes
To the extent BPG is required under EU Data Protection Law, BPG shall (at Customer’s expense) provide reasonably requested information regarding the Services to enable the Customer to carry out data protection impact assessments or prior consultations with data protection authorities as required by law.
Schedule A List of BPG Subprocessors
These Subprocessors set out below provide cloud hosting and storage services; content delivery and review services; assist in providing customer support; as well as incident tracking, response, diagnosis and resolution services.
| Subprocessor | Location | Subprocessing Activities |
| USA | Email services, Product analytics | |
| Microsoft 365 | USA | Email services |
| Azure | USA | Mail transport services, database services, application hosting, CDN hosting |
| AWS Amazon | Worldwide | CDN Hosting |
| Zoho | USA | Customer Support, CRM |
| Windcave | New Zealand | Payment Processor |
| PayPal | USA | Payment processor |
| Subprocessor | Location | Subprocessing Activities |
|---|---|---|
| USA | Email services, Product analytics | |
| Microsoft 365 | USA | Email services |
| Azure | USA | Mail transport services, database services, application hosting, CDN hosting |
| AWS Amazon | Worldwide | CDN Hosting |
| Zoho | USA | Customer Support, CRM |
| Windcave | New Zealand | Payment Processor |
| PayPal | USA | Payment processor |
Cookie consent
This website uses cookies.
We use cookies to personalise content and ads, to provide social media features and to analyse our traffic.
Cookies are small text files that can be used by websites to make a user’s experience more efficient.
The law states that we can store cookies on your device if they are strictly necessary for the operation of this site. For all other types of cookies we need your permission.
This site uses different types of cookies. Some cookies are placed by third party services that appear on our pages.
You can at any time change or withdraw your consent from the Cookie Declaration on our website.
Learn more about who we are, how you can contact us and how we process personal data in our Privacy Policy.
Please state your consent ID and date when you contact us regarding your consent.
Your consent applies to the following domains: pearldiver.io
Your consent ID: Rol3cl8ZIKd+c4Q0Lmk9EhU86XfSEc2hnExU6W1YzvlDyrZQb+U98A==Consent date: Thursday, November 30, 2023 at 01:24:24 PM MST
Cookie declaration last updated on 11/21/23 by Cookiebot:
Necessary (25)
Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.
| Name | Provider | Purpose | Expiry | Type |
|---|---|---|---|---|
| __cf_bm [x2] | Calendly pearldiver.io | This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. | 1 day | HTTP Cookie |
| __cfruid | Calendly | This cookie is a part of the services provided by Cloudflare – Including load-balancing, deliverance of website content and serving DNS connection for website operators. | Session | HTTP Cookie |
| __stripe_mid | Stripe | This cookie is necessary for making credit card transactions on the website. The service is provided by Stripe.com which allows online transactions without storing any credit card information. | 1 year | HTTP Cookie |
| __stripe_sid | Stripe | This cookie is necessary for making credit card transactions on the website. The service is provided by Stripe.com which allows online transactions without storing any credit card information. | 1 day | HTTP Cookie |
| _ab | Calendly | This cookie is necessary for making credit card transactions on the website. The service is provided by Stripe.com which allows online transactions without storing any credit card information. | Session | HTML Local Storage |
| _calendly_session | Calendly | If consent is given by the visitor, this cookie allows the website to add events into the visitor’s calendar. | 21 days | HTTP Cookie |
| _mf | Calendly | This cookie is necessary for making credit card transactions on the website. The service is provided by Stripe.com which allows online transactions without storing any credit card information. | Session | HTML Local Storage |
| bcookie | Pending | 1 year | HTTP Cookie | |
| bscookie | Pending | 1 year | HTTP Cookie | |
| checkForPermission | Beeswax | Determines whether the user has accepted the cookie consent box. | 1 day | HTTP Cookie |
| CookieConsent | Cookiebot | Stores the user’s cookie consent state for the current domain | 1 year | HTTP Cookie |
| hex (10) | Zoho | Registers which server-cluster is serving the visitor. This is used in context with load balancing, in order to optimize user experience. | Session | HTTP Cookie |
| id | Calendly | Pending | Session | HTML Local Storage |
| li_gc | Pending | 180 days | HTTP Cookie | |
| m | Stripe | Determines the device used to access the website. This allows the website to be formatted accordingly. | 400 days | HTTP Cookie |
| omScrollHeight | OptinMonster | Saves the user’s screen size in order to adjust the size of images on the website. | Session | HTML Local Storage |
| PHPSESSID | pearldiver.io | Preserves user session state across page requests. | Session | HTTP Cookie |
| rc::a | Zoho | This cookie is used to distinguish between humans and bots. This is beneficial for the website, in order to make valid reports on the use of their website. | Persistent | HTML Local Storage |
| rc::c | Zoho | This cookie is used to distinguish between humans and bots. | Session | HTML Local Storage |
| referrer_user_id | Calendly | Necessary for the website’s booking functionality. | 14 days | HTTP Cookie |
| replayStorage#chunkUploads | Calendly | Control cookie used in connection to the website’s Content Delivery Network (CDN). | Persistent | IndexedDB |
| replayStorage#events | Calendly | Control cookie used in connection to the website’s Content Delivery Network (CDN). | Persistent | IndexedDB |
| replayStorage#pendingCaptures | Calendly | Control cookie used in connection to the website’s Content Delivery Network (CDN). | Persistent | IndexedDB |
| test_cookie | Pending | 1 day | HTTP Cookie |
Preferences (2)
Preference cookies enable a website to remember information that changes the way the website behaves or looks, like your preferred language or the region that you are in.
| Name | Provider | Purpose | Expiry | Type |
|---|---|---|---|---|
| data/guide.gif/#-#-#-#-# | Calendly | Pending | Session | Pixel Tracker |
| lidc | Pending | 1 day | HTTP Cookie |
Statistics (30)
Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.
| Name | Provider | Purpose | Expiry | Type |
|---|---|---|---|---|
| _ga [x2] | Registers a unique ID that is used to generate statistical data on how the visitor uses the website. | 2 years | HTTP Cookie | |
| _ga_# [x2] | Used by Google Analytics to collect data on the number of times a user has visited the website as well as dates for the first and most recent visit. | 2 years | HTTP Cookie | |
| _hjAbsoluteSessionInProgress | Hotjar | This cookie is used to count how many times a website has been visited by different visitors – this is done by assigning the visitor an ID, so the visitor does not get registered twice. | 1 day | HTTP Cookie |
| _hjFirstSeen | Hotjar | This cookie is used to determine if the visitor has visited the website before, or if it is a new visitor on the website. | 1 day | HTTP Cookie |
| _hjIncludedInSessionSample_# | Hotjar | Collects statistics on the visitor’s visits to the website, such as the number of visits, average time spent on the website and what pages have been read. | 1 day | HTTP Cookie |
| _hjSession_# | Hotjar | Collects statistics on the visitor’s visits to the website, such as the number of visits, average time spent on the website and what pages have been read. | 1 day | HTTP Cookie |
| _hjSessionUser_# | Hotjar | Collects statistics on the visitor’s visits to the website, such as the number of visits, average time spent on the website and what pages have been read. | 1 year | HTTP Cookie |
| _hp2_# | Heap Analytics | Collects data on the user’s navigation and behavior on the website. This is used to compile statistical reports and heatmaps for the website owner. | 1 day | HTTP Cookie |
| _hp2_id.# | Heap Analytics | Collects data on the user’s navigation and behavior on the website. This is used to compile statistical reports and heatmaps for the website owner. | 1 year | HTTP Cookie |
| _hp2_ses_props.# | Heap Analytics | Collects data on the user’s navigation and behavior on the website. This is used to compile statistical reports and heatmaps for the website owner. | 1 day | HTTP Cookie |
| _omappvp | OptinMonster | This cookie is used to determine if the visitor has visited the website before, or if it is a new visitor on the website. | 11 years | HTTP Cookie |
| _omappvs | OptinMonster | This cookie is used to determine if the visitor has visited the website before, or if it is a new visitor on the website. | 1 day | HTTP Cookie |
| _tt_enable_cookie | Tiktok | Used by the social networking service, TikTok, for tracking the use of embedded services. | 1 year | HTTP Cookie |
| 1 | Calendly | Registers data on visitors’ website-behaviour. This is used for internal analysis and website optimization. | Session | HTML Local Storage |
| ajs_anonymous_id | Segment | This cookie is used to identify a specific visitor – this information is used to identify the number of specific visitors on a website. | 1 year | HTTP Cookie |
| ajs_anonymous_id | Calendly | This cookie is used to count how many times a website has been visited by different visitors – this is done by assigning the visitor an ID, so the visitor does not get registered twice. | Persistent | HTML Local Storage |
| AnalyticsSyncHistory | Pending | 30 days | HTTP Cookie | |
| data/ptm.gif/4cfbcefc-fcf9-4b66-5dc6-9b0d81bb07a9 | Calendly | Registers statistical data on users’ behaviour on the website. Used for internal analytics by the website operator. | Session | Pixel Tracker |
| dd_cookie_test_# | Calendly | Registers data on visitors’ website-behaviour. This is used for internal analysis and website optimization. | Session | HTTP Cookie |
| gaLocalStorageVisitKey | us-an.gr-cdn.com | Sets a unique ID for the session. This allows the website to obtain data on visitor behaviour for statistical purposes. | Persistent | HTML Local Storage |
| gaVisitorUuid | us-an.gr-cdn.com | Registers statistical data on users’ behaviour on the website. Used for internal analytics by the website operator. | 1 year | HTTP Cookie |
| omSessionPageviews | OptinMonster | This cookie is used to identify the frequency of visits and how long the visitor is on the website. The cookie is also used to determine how many and which subpages the visitor visits on a website – this information can be used by the website to optimize the domain and its subpages. | Session | HTML Local Storage |
| omSessionStart | OptinMonster | Sets a timestamp for when the visitor entered the website. This is used for analytical purposes on the website. | Session | HTML Local Storage |
| omVisits | OptinMonster | This cookie is used to identify the frequency of visits and how long the visitor is on the website. The cookie is also used to determine how many and which subpages the visitor visits on a website – this information can be used by the website to optimize the domain and its subpages. | Persistent | HTML Local Storage |
| omVisitsFirst | OptinMonster | This cookie is used to count how many times a website has been visited by different visitors – this is done by assigning the visitor an ID, so the visitor does not get registered twice. | Persistent | HTML Local Storage |
| pendo_cd | Calendly | Registers statistical data on users’ behaviour on the website. Used for internal analytics by the website operator. | Session | HTML Local Storage |
| tuid | a.usbrowserspeed.com | Pending | 1 year | HTTP Cookie |
| userleap.ids | Calendly | This cookie is set to make split-tests on the website, which optimizes the website’s relevance towards the visitor – the cookie can also be set to improve the visitor’s experience on a website. | Persistent | HTML Local Storage |
Marketing (36)
Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.
| Name | Provider | Purpose | Expiry | Type |
|---|---|---|---|---|
| __podscribe_did | Amazon | Pending | 1 year | HTTP Cookie |
| __podscribe_pearldiver_landing_url | Amazon | Pending | 1 year | HTTP Cookie |
| __podscribe_pearldiver_referrer | Amazon | Pending | 1 year | HTTP Cookie |
| __tld__ | Segment | Used to track visitors on multiple websites, in order to present relevant advertisement based on the visitor’s preferences. | Session | HTTP Cookie |
| _fbp [x2] | Meta Platforms, Inc. | Used by Facebook to deliver a series of advertisement products such as real time bidding from third party advertisers. | 3 months | HTTP Cookie |
| _gat | Used to send data to Google Analytics about the visitor’s device and behavior. Tracks the visitor across devices and marketing channels. | 1 day | HTTP Cookie | |
| _gcl_au | Used by Google AdSense for experimenting with advertisement efficiency across websites using their services. | 3 months | HTTP Cookie | |
| _gid | Used to send data to Google Analytics about the visitor’s device and behavior. Tracks the visitor across devices and marketing channels. | 1 day | HTTP Cookie | |
| _podscribe_did | podscribe.com | Pending | 1 year | HTTP Cookie |
| _podscribe_pearldiver_landing_url | podscribe.com | Pending | 1 year | HTTP Cookie |
| _podscribe_pearldiver_referrer | podscribe.com | Pending | 1 year | HTTP Cookie |
| _ttp [x2] | Tiktok | Used by the social networking service, TikTok, for tracking the use of embedded services. | 1 year | HTTP Cookie |
| ads/ga-audiences | Used by Google AdWords to re-engage visitors that are likely to convert to customers based on the visitor’s online behaviour across websites. | Session | Pixel Tracker | |
| ajs_group_id | Segment | This cookie is used to assign specific visitors into segments, this segmentation is based on visitor behavior on the website – the segmentation can be used to target larger groups. | Session | HTTP Cookie |
| ajs_group_id | Calendly | Collects data on visitors. This information is used to assign visitors into segments, making website advertisement more efficient. | Persistent | HTML Local Storage |
| ajs_user_id | Segment | This cookie is used to collect data on the visitor’s behavior on the website – this information can be used to assign the visitor to a visitor segment, based on common preferences. | Session | HTTP Cookie |
| ajs_user_id | Calendly | Collects data on visitors’ preferences and behaviour on the website – This information is used make content and advertisement more relevant to the specific visitor. | Persistent | HTML Local Storage |
| bito | Beeswax | Sets a unique ID for the visitor, that allows third party advertisers to target the visitor with relevant advertisement. This pairing service is provided by third party advertisement hubs, which facilitates real-time bidding for advertisers. | 13 months | HTTP Cookie |
| bitoIsSecure | Beeswax | Presents the user with relevant content and advertisement. The service is provided by third-party advertisement hubs, which facilitate real-time bidding for advertisers. | 13 months | HTTP Cookie |
| grUuidHasBeenSet | us-an.gr-cdn.com | Collects information on what products the visitor has viewed and the content of the shopping-cart. This is used to increase the website’s conversion rate through targeted advertisement and product promotions through emails. | Session | HTML Local Storage |
| h | Calendly | Collects data on user behaviour and interaction in order to optimize the website and make advertisement on the website more relevant. | Session | Pixel Tracker |
| IDE | Pending | 1 year | HTTP Cookie | |
| lastExternalReferrer | Meta Platforms, Inc. | Detects how the user reached the website by registering their last URL-address. | Persistent | HTML Local Storage |
| lastExternalReferrerTime | Meta Platforms, Inc. | Detects how the user reached the website by registering their last URL-address. | Persistent | HTML Local Storage |
| li_sugr | Pending | 3 months | HTTP Cookie | |
| pagead/landing | pearldiver.io | Collects data on visitor behaviour from multiple websites, in order to present more relevant advertisement – This also allows the website to limit the number of times that they are shown the same advertisement. | Session | Pixel Tracker |
| pendo_tabId | Calendly | Collects data on the user across websites – This data is used to make advertisement more relevant. | Session | HTML Local Storage |
| referrername | pearldiver.io | Pending | 7 days | HTTP Cookie |
| tt_appInfo | Tiktok | Used by the social networking service, TikTok, for tracking the use of embedded services. | Session | HTML Local Storage |
| tt_pixel_session_index | Tiktok | Used by the social networking service, TikTok, for tracking the use of embedded services. | Session | HTML Local Storage |
| tt_sessionId | Tiktok | Used by the social networking service, TikTok, for tracking the use of embedded services. | Session | HTML Local Storage |
| UserMatchHistory | Pending | 30 days | HTTP Cookie | |
| utm_medium | pearldiver.io | Collects information on user preferences and/or interaction with web-campaign content – This is used on CRM-campaign-platform used by website owners for promoting events or products. | 7 days | HTTP Cookie |
| utm_source | pearldiver.io | Determines how the user accessed the website. This information is used by the website operator in order to measure the efficiency of their marketing. | 7 days | HTTP Cookie |
Unclassified (6)
Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies.
| Name | Provider | Purpose | Expiry | Type |
|---|---|---|---|---|
| _pendo_guides_blocked.4cfbcefc-fcf9-4b66-5dc6-9b0d81bb07a9 | Calendly | Pending | Persistent | HTML Local Storage |
| _pendo_meta.01234567-89ab-cdef-0123-456789abcdef | Calendly | Pending | Persistent | HTML Local Storage |
| _pendo_visitorId.4cfbcefc-fcf9-4b66-5dc6-9b0d81bb07a9 | Calendly | Pending | Persistent | HTML Local Storage |
| cg_clo | Clickguard | Pending | Persistent | HTML Local Storage |
| cg_did | Clickguard | Pending | Persistent | HTML Local Storage |
| cg_sid | Clickguard | Pending | Persistent | HTML Local Storage |