AstraOne

Loading

light
In-Image Ads

Discover a new kind of ad placement 

We have created a unique advertising placement integrated into the visual content.

arrow
In the Spotlight!

Your ad won't go unnoticed!

light

Technology that sees

Our technology identifies the moment when the user’s attention is focused on the image.

100% visibility

When an image is 100% viewable, the ad is served. This way we make the ad appear as a new object on the page, so it catches the most of user’s attention.

Hit the target

This technology takes us (allows us to reach) to a whole new level of advertising visibility.

Computer Vision

Technology that sees

Our technology can see and recognise any graphics the same way as a human eye does.

In milliseconds on page load AstraVision analyses the images on the page, corresponds the received data to the data of the semantic textual content analysis and serves the relevant ad.

Capacity of our AI: LOGO IDENTIFICATION
Capacity of our AI: FACIAL RECOGNITION
Capacity of our AI: IDENTIFICATION OF THE OBJECTS
left
Full engagement!

Only contextually relevant advertising

In-Image Ads, as a new ad placement have a lot of potential, but are also full of unique features. To make the most of them, we’ve created a strategic lab that allows you to push the envelope of this new opportunity!

light light
670

Successful advertising campaigns

Structure

Integration into contextually relevant content Dynamic creative that displays your ad Interactive animation targeting relevant image categories.

Integration into contextually relevant content Dynamic creative that displays your ad Interactive animation targeting relevant image categories.

Integration into contextually relevant content Dynamic creative that displays your ad Interactive animation targeting relevant image categories.

right

Full-service approach
The goal is 100% efficiency

Variety
of creatives 

Strategy development 

Leading
Publishers

100% 
Transparent reports AdLoox

100%
Visibility 

100% 
Brand Safety

Our partners and achievements

Short-listed for The WARC Awards

150+  Leading advertisers 

Partnership with the largest digital sales house 

How can we help you?

Advertising enquiry Publisher enquiry

By clicking the "Contact us" button, you consent to the Terms of the Privacy Policy.

Application has been sent successfully! Our manager will contact you soon!

Data Protection Policy of astraone.io

Scope of policy

This Privacy Policy applies to all of the services offered by AstraOne LLC and its affiliates, including Hybrid Adtech Inc, Hybrid Adtech GmbH, Hybrid Adtech sp. z o.o. and services offered on third-party sites, such as advertising services.


Policy operational date

This policy will be effective starting on May 25, 2018.


Policy prepared by

astraone.io’s data protection team.


Date approved by Board/ Management Committee

This policy has been approved by astraone.io’s Chief Executive Officer, Dmitry Cheklov.

1. Introduction

astraone.io (either of entities mentioned in “Scope of policy” above) is committed to conducting its business in accordance with all applicable Data Protection laws and regulations and in line with the highest standards of ethical conduct. This policy sets forth the expected behaviours of astraone.io’s Employees and Third Parties in relation to the collection, use, retention, transfer, disclosure and destruction of any Personal Data belonging to an astraone`io (i.e. the Data Subject). Personal Data is any information (including opinions and intentions) which relates to an identified or Identifiable Natural Person. Personal Data is subject to certain legal safeguards and other regulations, which impose restrictions on how organisations may process Personal Data. An organisation that handles Personal Data and makes decisions about its use is known as a Data Controller. astraone.io, as a Data Controller, is responsible for ensuring compliance with the Data Protection requirements outlined in this policy. astraone.io’s leadership is fully committed to ensuring continued and effective implementation of this policy, and expects all astraone.io Employees and Third Parties to share in this commitment. Any breach of this policy will be taken seriously and may result in disciplinary action or business sanction.

2. Definitions and Interpretation
  • 2.1 In these Controller Terms:
  • “Affiliate” means an entity that directly or indirectly controls, is controlled by, or is under common control with, a party.
  • “Controller Data Subject” means a data subject to whom Controller Personal Data relates.
  • “Controller Personal Data” means any personal data that is processed by a party under the Agreement in connection with its provision or use (as applicable) of the Controller Services.
  • “Controller Services” means the applicable following services: Astraone Console, Astraone Reports, Astraone Insights.
  • “Data Protection Legislation” means, as applicable: (a) the GDPR; and/or (b) the Federal Data Protection Act of 19 June 1992 (Switzerland).
  • “GDPR” means Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC.
  • “hybrid.ai” means astraone.io Entity that is party to the Agreement.
  • “astraone.io Entity” means Targetix LLC, Kontektno-mediynye tekhnologii LLC, Gibrid LLC, Hybrid Adtech Inc., Hybrid Adtech GmbH.
  • “Privacy Shield” means the EU-U.S. Privacy Shield legal framework and the Swiss-U.S. Privacy Shield legal framework.
  • “Terms Effective Date” means, as applicable:
    • (a) 25 May 2018, if Customer clicked to accept or the parties otherwise agreed to these Controller Terms before or on such date; or
    • (b) the date on which Customer clicked to accept or the parties otherwise agreed to these Controller Terms, if such date is after 25 May 2018.
  • “Employee” means an individual who works part-time or full-time for astraone.io under a contract of employment, whether oral or written, express or implied, and has recognised rights and duties. Includes temporary employees and independent contractors.
  • “Third Party” means an external organisation with which astraone.io conducts business and is also authorised to, under the direct authority of astraone.io, Process the Personal Data of astraone.io Advertisers.
  • “Personal Data” means any information (including opinions and intentions) which relates to an identified or Identifiable Natural Person.
  • “Advertiser” means any past, current or prospective hybrid.ai customer.
  • “Identifiable Natural Person” means anyone who can be identified, directly or indirectly, in particular by reference to an identifier such as an identification number, location data, an online identifier, or one or more factors specific to the physical, physiological, economic, cultural or social identity of that natural person.
  • “Data Controller” means a 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.
  • “Data Subject” means the identified or Identifiable Natural Person to which the data refers.
  • “Process, Processed, Processing” means any operation or set of operations performed on Personal Data or on sets of Personal Data, whether or not by automated means. Operations performed may include collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction.
  • “Data Protection” means the process of safeguarding Personal Data from unauthorised or unlawful disclosure, access, alteration, Processing, transfer or destruction.
  • “Data Protection Authority” means an independent Public Authority responsible for monitoring the application of the relevant Data Protection regulation set forth in national law.
  • “Data Processors” means a natural or legal person, Public Authority, Agency or other body which Processes Personal Data on behalf of a Data Controller.
  • “Consent” means any freely given, specific, informed and unambiguous indication of the Data Subject’s wishes by which he or she, by a statement or by a clear affirmative action, signifies agreement to the Processing of Personal Data relating to him or her.
  • “Special Categories of Data” means Personal Data pertaining to or revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, trade-union membership; data concerning health or sex life and sexual orientation; genetic data or biometric data.
  • “Third Country” means any country not recognised as having an adequate level of legal protection for the rights and freedoms of Data Subjects in relation to the Processing of Personal Data.
  • “Profiling” means any form of automated processing of Personal Data where Personal Data is used to evaluate specific or general characteristics relating to an Identifiable Natural Person. In particular to analyse or predict certain aspects concerning that natural person’s performance at work, economic situations, health, personal preferences, interests, reliability, behaviour, location or movement.
  • “Binding Corporate Rules” means the Personal Data protection policies used for the transfer of Personal Data to one or more Third Countries within a group of undertakings, or group of enterprises engaged in a joint economic activity. Personal Data Breach A breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, Personal Data transmitted, stored or otherwise Processed.
  • “Encryption” means the process of converting information or data into code, to prevent unauthorised access.
  • “Pseudonymisation” means data amended in such a way that no individuals can be identified from the data (whether directly or indirectly) without a “key” that allows the data to be re-identified.
  • “Anonymisation” means data amended in such a way that no individuals can be identified from the data (whether directly or indirectly) by any means or by any person.
3. Policy
  • 3.1 Governance
  • 3.1.1 Policy Dissemination & Enforcement
    The management team of each astraone.io Entity must ensure that all astraone.io Employees responsible for the Processing of Personal Data are aware of and comply with the contents of this policy. In addition, each astraone.io Entity will make sure all Third Parties engaged to Process Personal Data on their behalf (i.e. their Data Processors) are aware of and comply with the contents of this policy. Assurance of such compliance must be obtained from all Third Parties, whether companies or individuals, prior to granting them access to Personal Data controlled by hybrid.ai.
  • 3.1.2 Data Protection by Design
    To ensure that all Data Protection requirements are identified and addressed when designing new products or processes and/or when reviewing or expanding existing systems or processes, each of them must go through an approval process before continuing. Each astraone.io Entity must ensure that a Data Protection Impact Assessment (DPIA) is conducted, for all new and/or revised products or processes for which it has responsibility. Where applicable, the Information Technology (IT) department, as part of its IT system and application design review process, will assess the impact of any new technology uses on the security of Personal Data.
  • 3.1.3 Compliance Monitoring
    To confirm that an adequate level of compliance that is being achieved by all astraone.io Entities in relation to this policy, the management of astraone.io will carry out an annual Data Protection compliance audit for all such Entities. Each audit will, as a minimum, assess:
    • Compliance with Policy in relation to the protection of Personal Data, including:
      • Compliance with Policy in relation to the protection of Personal Data, including:
        • The assignment of responsibilities
        • Raising awareness
        • Training of Employees
      • The effectiveness of Data Protection related operational practices, including:
        • Data Subject rights
        • Personal Data transfers
        • Personal Data incident management
        • Personal Data complaints handling
        • The level of understanding of Data Protection policies and Privacy Notices
        • The currency of Data Protection policies and Privacy Notices
        • The accuracy of Personal Data being stored
        • The conformity of Data Processor activities
        • The adequacy of procedures for redressing poor compliance and Personal Data Breaches
        Key business stakeholders from each astraone.io Entity, will devise a plan with a schedule for correcting any identified deficiencies within a defined and reasonable time frame. Any major deficiencies identified will be reported to and monitored by the hybrid.ai Executive Management team.
  • 3.2 Data Protection Principles

astraone.io has adopted the following principles to govern its collection, use, retention, transfer, disclosure and destruction of Personal Data:


  • Principle 1: Lawfulness, Fairness and Transparency
    Personal Data shall be processed lawfully, fairly and in a transparent manner in relation to the Data Subject. This means, astraone.io must tell the Data Subject what Processing will occur (transparency), the Processing must match the description given to the Data Subject (fairness), and it must be for one of the purposes specified in the applicable Data Protection regulation (lawfulness).
  • Principle 2: Purpose Limitation
    Personal Data shall be collected for specified, explicit and legitimate purposes and not further Processed in a manner that is incompatible with those purposes. This means astraone.io must specify exactly what the Personal Data collected will be used for and limit the Processing of that Personal Data to only what is necessary to meet the specified purpose.
  • Principle 3: Data Minimisation
    Personal Data shall be adequate, relevant and limited to what is necessary in relation to the purposes for which they are Processed. This means astraone.io must not store any Personal Data beyond what is strictly required.
  • Principle 4: Accuracy
    Personal Data shall be accurate and, kept up to date. This means astraone.io must have in place processes for identifying and addressing out-of-date, incorrect and redundant Personal Data.
  • Principle 5: Storage Limitation
    Personal Data shall be kept in a form which permits identification of Data Subjects for no longer than is necessary for the purposes for which the Personal Data is Processed. This means hybrid.ai must, wherever possible, store Personal Data in a way that limits or prevents identification of the Data Subject.
  • Principle 6: Integrity & Confidentiality
    Personal Data shall be Processed in a manner that ensures appropriate security of the Personal Data, including protection against unauthorised or unlawful Processing, and against accidental loss, destruction or damage. astraone.io must use appropriate technical and organisational measures to ensure the integrity and confidentiality of Personal Data is maintained at all times.
  • Principle 7: Accountability
    The Data Controller shall be responsible for, and be able to demonstrate compliance. This means astraone.io must demonstrate that the six Data Protection Principles (outlined above) are met for all Personal Data for which it is responsible.
  • 3.3 Data Collection
  • 3.3.1 Purposes of Data Collection
    We may collect the following categories of information for the purposes explained below.
  • Advertiser website activity: This is data about your browsing activity on the Advertiser's website. For example, which pages you visited and when, and what items you placed into your online shopping cart.
  • Device and browser information: This is technical information about the device or browser you use to access the Advertiser's website. For example, your device's IP address, cookie string data and (in the case of mobile devices) your device type and mobile device's unique identifier such as the Apple IDFA or Android Advertising ID.
  • Ad data: This is data about the online ads we have served (or attempted to serve) to you. It includes things like how many times an ad has been served to you, what page the ad appeared on, and whether you clicked on or otherwise interacted with the ad.
  • Data from Advertising Partners: This is data that we receive from other digital advertising companies that we work with (“Advertising Partners”) to help us deliver ads to you and recognize you across browsers and devices. This may include pseudonymous advertiser identifiers that some Advertisers or other third party ad platforms choose to share with us, such as your "Customer ID" with an Advertiser. We may work with these Advertising Partners to synchronize their unique, anonymous identifiers to our own to enhance data points about a particular unique browser or device.

    We use this data to help our Advertisers identify and serve ads to you that are more relevant to you. We also use this data to operate, improve and enhance our services including enhancing the data points we or our Advertising Partners have about a particular user, browser, or device, or to target, optimize, cap, or synchronize advertising.
  • 3.3.2 Data Sources
  • Personal Data should be collected only from the Data Subject unless one of the following apply:

  • The nature of the business purpose necessitates collection of the Personal Data from other persons or bodies.
  • The collection must be carried out under emergency circumstances in order to protect the vital interests of the Data Subject or to prevent serious loss or injury to another person.
    If Personal Data is collected from someone other than the Data Subject, the Data Subject must be informed1 of the collection unless one of the following apply:
  • The Data Subject has received the required information by other means.
  • The information must remain confidential due to a professional secrecy obligation.
  • A national law expressly provides for the collection, Processing or transfer of the Personal Data.
    Where it has been determined that notification to a Data Subject is required, notification should occur promptly, but in no case later than:
  • One calendar month from the first collection or recording of the Personal Data.
  • At the time of first communication if used for communication with the Data Subject.
  • At the time of disclosure if disclosed to another recipient.
  • 3.3.3 Data Subject Consent
  • Each hybrid.ai Entity will obtain Personal Data only by lawful and fair means and, where appropriate with the knowledge and Consent of the individual concerned. Where a need exists to request and receive the Consent of an individual prior to the collection, use or disclosure of their Personal Data, astraone.io is committed to seeking such Consent. astraone.io business representatives, shall establish a system for obtaining and documenting Data Subject Consent for the collection, Processing, and/or transfer of their Personal Data.
  • Each astraone.io Entity will refer to OpenRTB Advisory – GDRP in order to receive a Consent from Third Parties. This advisory, therefore, focuses on how active versions of OpenRTB will signal GDPR applicability and convey the consent string, which is treated as a single unit of data to be conveyed throughout a real-time bidding transaction.
  • 3.3.4 Data Subject Notification
  • Each astraone.io Entity will, when required by applicable law, contract, or where it considers that it is reasonably appropriate to do so, provide Data Subjects with information as to the purpose of the Processing of their Personal Data. When the Data Subject is asked to give Consent to the Processing of Personal Data and when any Personal Data is collected from the Data Subject, all appropriate disclosures will be made, in a manner that draws attention to them, unless one of the following apply:
  • The Data Subject already has the information
  • A legal exemption applies to the requirements for disclosure and/or Consent.

The disclosures may be given orally, electronically or in writing. If given orally, the person making the disclosures should use a suitable script or form approved in advance by the Office of Data Protection. The associated receipt or form should be retained, along with a record of the facts, date, content, and method of disclosure.


  • 3.4 Data Use
  • 3.4.1 Data Processing
  • astraone.io provides targeted advertising services for our advertiser clients ("Advertisers"). When Identifiable Natural Person visits a website operated by an Advertiser or a third party site where we could serve an ad to you, we may collect some or all of the data described in 3.3.1. hybrid.ai uses that data as well as other data described below to help Advertisers provide ads to Identifiable Natural Persons that are more relevant to them.
  • astraone.io uses the Personal Data of its Contacts for the following broad purposes:

    • The general running and business administration of hybrid.ai Entities.
    • To provide advertising services to astraone.io customers.
  • The use of a Advertiser’s information should always be considered from their perspective and whether the use will be within their expectations or if they are likely to object. For example, it would clearly be within a Advertiser’s expectations that their details will be used by hybrid.ai to respond to a Advertiser request for information about the products and services on offer. However, it will not be within their reasonable expectations that astraone.io would then provide their details to Third Parties for marketing purposes. Each astraone.io Entity will Process Personal Data in accordance with all applicable laws and applicable contractual obligations. More specifically, astraone.io will not Process Personal Data unless at least one of the following requirements are met:

    • The Data Subject has given Consent to the Processing of their Personal Data for one or more specific purposes.
    • Processing is necessary for the performance of a contract to which the Data Subject is party or in order to take steps at the request of the Data Subject prior to entering into a contract.
    • Processing is necessary for compliance with a legal obligation to which the Data Controller is subject.
    • Processing is necessary in order to protect the vital interests of the Data Subject or of another natural person.
    • Processing is necessary for the performance of a task carried out in the public interest or in the exercise of official authority vested in the Data Controller.
    • Processing is necessary for the purposes of the legitimate interests pursued by the Data Controller or by a Third Party (except where such interests are overridden by the interests or fundamental rights and freedoms of the Data Subject, in particular where the Data Subject is a child).
  • There are some circumstances in which Personal Data may be further processed for purposes that go beyond the original purpose for which the Personal Data was collected. When making a determination as to the compatibility of the new reason for Processing, guidance and approval must be obtained from the hybrid.ai representative before any such Processing may commence.
  • In any circumstance where Consent has not been gained for the specific Processing in question, astraone.io will address the following additional conditions to determine the fairness and transparency of any Processing beyond the original purpose for which the Personal Data was collected:

    • Any link between the purpose for which the Personal Data was collected and the reasons for intended further Processing.
    • The context in which the Personal Data has been collected, in particular regarding the relationship between Data Subject and the Data Controller.
    • The nature of the Personal Data, in particular whether Special Categories of Data are being Processed, or whether Personal Data related to criminal convictions and offences are being Processed.
    • The possible consequences of the intended further Processing for the Data Subject.
    • The existence of appropriate safeguards pertaining to further Processing, which may include Encryption, Anonymisation or Pseudonymisation.
  • 3.4.2 Special Categories of Data
  • astraone.io will only Process Special Categories of Data (also known as sensitive data) where the Data Subject expressly consents to such Processing or where one of the following conditions apply:

    • The Processing relates to Personal Data which has already been made public by the Data Subject.
    • The Processing is necessary for the establishment, exercise or defence of legal claims.
    • The Processing is specifically authorised or required by law.
    • The Processing is necessary to protect the vital interests of the Data Subject or of another natural person where the Data Subject is physically or legally incapable of giving consent.
    • Further conditions, including limitations, based upon national law related to the Processing of genetic data, biometric data or data concerning health.
  • In any situation where Special Categories of Data are to be Processed, prior approval must be obtained from the Office of Data Protection and the basis for the Processing clearly recorded with the Personal Data in question. Where Special Categories of Data are being Processed, MetaPrivacy will adopt additional protection measures. Each MetaPrivacy Entity may also adopt additional measures to address local custom or social expectation over the Processing of Special Categories of Data.
  • 3.4.3 Children’s Data
  • Children are unable to Consent to the Processing of Personal Data for information services. Consent must be sought from the person who holds parental responsibility over the child. However, it should be noted that where Processing is lawful under other grounds, Consent need not be obtained from the child or the holder of parental responsibility. Should any astraone.io Entity foresee a business need for obtaining parental consent for information society services offered directly to a child, guidance and approval must be obtained from the hybrid.ai representative before any Processing of a child’s Personal Data may commence.
  • 3.4.4 Data Quality
  • Each astraone.io Entity will adopt all necessary measures to ensure that the Personal Data it collects and Processes is complete and accurate in the first instance, and is updated to reflect the current situation of the Data Subject.
  • The measures adopted by astraone.io to ensure data quality include:
    • Correcting Personal Data known to be incorrect, inaccurate, incomplete, ambiguous, misleading or outdated, even if the Data Subject does not request rectification.
    • Keeping Personal Data only for the period necessary to satisfy the permitted uses or applicable statutory retention period.
    • The removal of Personal Data if in violation of any of the Data Protection principles or if the Personal Data is no longer required.
    • Restriction, rather than deletion of Personal Data, insofar as:
      • a law prohibits erasure.
      • erasure would impair legitimate interests of the Data Subject.
      • the Data Subject disputes that their Personal Data is correct and it cannot be clearly ascertained whether their information is correct or incorrect.
  • 3.4.6 Digital Marketing
  • As a general rule hybrid.ai will not send promotional or direct marketing material to an astraone.io website visitors or platform users through digital channels such as mobile phones, email and the Internet, without first obtaining their Consent. Any astraone.io Entity wishing to carry out a digital marketing campaign without obtaining prior Consent from the Data Subject must first have it approved by astraone.io representative. Where Personal Data Processing is approved for digital marketing purposes, the Data Subject must be informed at the point of first contact that they have the right to object, at any stage, to having their data Processed for such purposes. If the Data Subject puts forward an objection, digital marketing related Processing of their Personal Data must cease immediately and their details should be kept on a suppression list with a record of their opt-out decision, rather than being completely deleted. It should be noted that where digital marketing is carried out in a ‘business to business’ context, there is no legal requirement to obtain an indication of Consent to carry out digital marketing to individuals provided that they are given the opportunity to opt-out.
  • 3.5 Data Retention
  • We retain the identifiable data we collect directly for targeting purposes for 12 months, after which time we employ measures to delete it. However for identifiable data that we hold on behalf of an Advertiser such as their email address list, we may retain it for a longer period and not delete it until we no longer require it to provide services to the Advertiser or the Advertiser asks us to delete it.
  • Identifiable data collected for other purposes is held no longer than necessary for our business purposes or to meet legal requirements.
  • 3.6 Data Subject Requests
  • Each astraone.io Entity will establish a system to enable and facilitate the exercise of Data Subject rights related to:
    • Information access.
    • Objection to Processing.
    • Objection to automated decision-making and profiling.
    • Restriction of Processing.
    • Data portability.
    • Data rectification.
    • Data erasure.
  • If an individual makes a request relating to any of the rights listed above, astraone.io will consider each such request in accordance with all applicable Data Protection laws and regulations. No administration fee will be charged for considering and/or complying with such a request unless the request is deemed to be unnecessary or excessive in nature. Data Subjects are entitled to obtain, based upon a request made in writing to a astraone.io representative and upon successful verification of their identity, the following information about their own Personal Data:
    • The purposes of the collection, Processing, use and storage of their Personal Data.
    • The source(s) of the Personal Data, if it was not obtained from the Data Subject;
    • The categories of Personal Data stored for the Data Subject.
    • The recipients or categories of recipients to whom the Personal Data has been or may be transmitted, along with the location of those recipients.
    • The envisaged period of storage for the Personal Data or the rationale for determining the storage period.
    • The right of the Data subject to:

      • object to Processing of their Personal Data.
      • lodge a complaint with the Data Protection Authority
      • request rectification or erasure of their Personal Data.
      • request restriction of Processing of their Personal Data.
      All requests received for access to or rectification of Personal Data must be directed to the astraone.io representative, who will log each request as it is received. A response to each request will be provided within 30 days of the receipt of the written request from the Data Subject. Appropriate verification must confirm that the requestor is the Data Subject or their authorised legal representative. Data Subjects shall have the right to require astraone.io to correct or supplement erroneous, misleading, outdated, or incomplete Personal Data.
  • 3.7 Law Enforcement Requests & Disclosures
  • In certain circumstances, it is permitted that Personal Data be shared without the knowledge or Consent of a Data Subject. This is the case where the disclosure of the Personal Data is necessary for any of the following purposes:
    • The prevention or detection of crime.
    • The apprehension or prosecution of offenders.
    • The assessment or collection of a tax or duty.
    • By the order of a court or by any rule of law.
  • If a astraone.io Entity Processes Personal Data for one of these purposes, then it may apply an exception to the Processing rules outlined in this policy but only to the extent that not doing so would be likely to prejudice the case in question. If any astraone.io Entity receives a request from a court or any regulatory or law enforcement authority for information relating to a astraone.io Advertiser, you must immediately notify the hybrid.ai representative who will provide comprehensive guidance and assistance.
  • 3.8 Data Protection Training
  • All astraone.io Employees that have access to Personal Data will have their responsibilities under this policy outlined to them as part of their staff induction training. In addition, each astraone.io Entity will provide regular Data Protection training and procedural guidance for their staff.
  • The training and procedural guidance set forth will consist of, at a minimum, the following elements:

    • The Data Protection Principles set forth in Section 4.2 above.
    • Each Employee’s duty to use and permit the use of Personal Data only by authorised persons and for authorised purposes.
    • The need for, and proper use of, the forms and procedures adopted to implement this policy.
    • The correct use of passwords, security tokens and other access mechanisms.
    • The importance of limiting access to Personal Data, such as by using password protected screen savers and logging out when systems are not being attended by an authorised person.
    • Securely storing manual files, print outs and electronic storage media.
    • The need to obtain appropriate authorisation and utilise appropriate safeguards for all transfers of Personal Data outside of the internal network and physical office premises.
    • Proper disposal of Personal Data by using secure shredding facilities.
    • Any special risks associated with particular departmental activities or duties.
    • 3.9 Data Transfers
    • We may transfer the information we collect about you to countries other than the country where we originally collected it for the purposes of storage and processing of data and operating our services. Those countries may not have the same data protection laws as your country. However, when we transfer your information to other countries, we will protect that information as described in this Privacy Notice and take steps, where necessary, to ensure that international transfers comply with applicable laws. For example, if we transfer your information from the European Economic Area to a country outside it, such as the United States, we will seek to take additional steps such as entering into EU compliant data transfer agreements with the data importer where necessary.
    • astraone.io Entities may transfer Personal Data to internal or Third Party recipients located in another country where that country is recognised as having an adequate level of legal protection for the rights and freedoms of the relevant Data Subjects. Where transfers need to be made to countries lacking an adequate level of legal protection (i.e. Third Countries), they must be made in compliance with an approved transfer mechanism astraone.io Entities may only transfer Personal Data where one of the transfer scenarios list below applies:

      • The Data Subject has given Consent to the proposed transfer.
      • The transfer is necessary for the performance of a contract with the Data Subject.
      • The transfer is necessary for the implementation of pre-contractual measures taken in response to the Data Subject’s request.
      • The transfer is necessary for the conclusion or performance of a contract concluded with a Third Party in the interest of the Data Subject.
      • The transfer is legally required on important public interest grounds.
      • The transfer is necessary for the establishment, exercise or defence of legal claims.
      • The transfer is necessary in order to protect the vital interests of the Data Subject.
  • 3.9.1 Transfers between hybrid.ai Entities
  • In order for astraone.io to carry out its operations effectively across it’s various hybrid.ai Entities, there may be occasions when it is necessary to transfer Personal Data from one astraone.io Entity to another, or to allow access to the Personal Data from an overseas location. Should this occur, the astraone.io Entity sending the Personal Data remains responsible for ensuring protection for that Personal Data.
  • astraone.io handles the transfer of Personal Data between astraone.io Entities, where the location of the recipient Entity is a Third Country, using the Binding Corporate Rules transfer mechanism. Binding Corporate Rules provide legally binding, enforceable rights on Data Subjects with regard to the Processing of their Personal Data and must be enforced by each approved hybrid.ai Entity, including their Employees. When transferring Personal Data to another astraone.io Entity located in a Third Country, you must:

    • Only transfer the minimum amount of Personal Data necessary for the particular purpose of the transfer (for example, to fulfil a transaction or carry out a particular service).
    • Ensure adequate security measures are used to protect the Personal Data during the transfer (including password-protection and Encryption, where necessary).
  • 3.9.2 Transfers to Third Parties
  • Each astraone.io Entity will only transfer Personal Data to, or allow access by, Third Parties when it is assured that the information will be Processed legitimately and protected appropriately by the recipient. Where Third Party Processing takes place, each hybrid.ai Entity will first identify if, under applicable law, the Third Party is considered a Data Controller or a Data Processor of the Personal Data being transferred.
  • Where the Third Party is deemed to be a Data Controller, the astraone.io Entity will enter into, in cooperation with the Office of Data Protection, an appropriate agreement with the Controller to clarify each party’s responsibilities in respect to the Personal Data transferred.
  • Where the Third Party is deemed to be a Data Processor, the astraone.io Entity will enter into, in cooperation with the Office of Data Protection, an adequate Processing agreement with the Data Processor. The agreement must require the Data Processor to protect the Personal Data from further disclosure and to only Process Personal Data in compliance with astraone.io instructions. In addition, the agreement will require the Data Processor to implement appropriate technical and organisational measures to protect the Personal Data as well as procedures for providing notification of Personal Data Breaches.
  • When a hybrid.ai Entity is outsourcing services to a Third Party (including Cloud Computing services), they will identify whether the Third Party will Process Personal Data on its behalf and whether the outsourcing will entail any Third Country transfers of Personal Data. In either case, it will make sure to include, in cooperation with the Office of Data Protection, adequate provisions in the outsourcing agreement for such Processing and Third Country transfers. MetaPrivacy has a ‘Standard Provisions for Outsourcing Agreement’ document that should be used for guidance.
  • 3.10 Complaints Handling
  • Data Subjects with a complaint about the Processing of their Personal Data, should put forward the matter in writing to the Office of Data Protection. An investigation of the complaint will be carried out to the extent that is appropriate based on the merits of the specific case. The hybrid.ai representative will inform the Data Subject of the progress and the outcome of the complaint within a reasonable period. If the issue cannot be resolved through consultation between the Data Subject and the hybrid.ai representative, then the Data Subject may, at their option, seek redress through mediation, binding arbitration, litigation, or via complaint to the Data Protection Authority within the applicable jurisdiction.
  • 3.11 Breach Reporting
  • Any individual who suspects that a Personal Data Breach has occurred due to the theft or exposure of Personal Data must immediately notify astraone.io representative providing a description of what occurred. Notification of the incident can me made via e-mail , by calling , or by using the anonymous incident reporting form at . astraone.io representative will investigate all reported incidents to confirm whether or not a Personal Data Breach has occurred. If a Personal Data Breach is confirmed, the astraone.io representative will follow the relevant authorised procedure based on the criticality and quantity of the Personal Data involved. For severe Personal Data Breaches, the astraone.io management will initiate and chair an emergency response team to coordinate and manage the Personal Data Breach response.
4. Application of these Controller Terms
  • 4.1 Application of Data Protection Legislation
  • These Controller Terms will only apply to the extent that the Data Protection Legislation applies to the processing of Controller Personal Data.
  • 4.2 Application to Controller Services
  • These Controller Terms will only apply to the Controller Services for which the parties agreed to these Controller Terms (for example: (a) the Controller Services for which Customer clicked to accept these Controller Terms; or (b) if the Agreement incorporates these Controller Terms by reference, the Controller Services that are the subject of the Agreement).
5. Roles and Restrictions on Processing
  • 5.1 Independent Controllers
  • Each party:

    • (a) is an independent controller of Controller Personal Data under the Data Protection Legislation;
    • (b) will individually determine the purposes and means of its processing of Controller Personal Data; and
    • (c) will comply with the obligations applicable to it under the Data Protection Legislation with respect to the processing of Controller Personal Data.
  • 5.2 Restrictions on Processing
  • Section 4.1 (Independent Controllers) will not affect any restrictions on either party’s rights to use or otherwise process Controller Personal Data under the Agreement.
6. Data Transfers
  • 6.1 Transfers of Data Out of the European Economic Area and Switzerland
  • Either party may transfer Controller Personal Data outside the European Economic Area and Switzerland if it complies with the provisions on the transfer of personal data to third countries in the Data Protection Legislation.
7. Privacy Shield Onward Transfer Provisions
  • 7.1 Application of Section 7
  • Sections 7.2 (Use of Data Provider Personal Data) and 7.3 (Protection of Data Provider Personal ata) will only apply to the extent that:

    • (a) a party (the “Data Recipient”) processes Controller Personal Data that is made available by the other party (the “Data Provider”) in connection with the Agreement (such Controller Personal Data, “Data Provider Personal Data”);
    • (b) the Data Provider or its Affiliate is certified under Privacy Shield; and
    • (c) the Data Provider notifies the Data Recipient of such Privacy Shield certification in writing.
  • 7.2 Use of Data Provider Personal Data
    • (a) Pursuant to the onward transfer principle under Privacy Shield, the Data Recipient will only use Data Provider Personal Data in a manner consistent with the consent provided by the relevant Controller Data Subjects.
    • (b) To the extent the Data Provider fails to obtain consent from the relevant Controller Data Subjects as required under the Agreement, the Data Recipient will not be in breach of Section 6.2(a) if it uses Data Provider Personal Data consistent with the required consent.
  • 7.3 Protection of Data Provider Personal Data
    • (a) The Data Recipient will provide a level of protection for Data Provider Personal Data that is at least equivalent to that required under Privacy Shield.
    • (b) If the Data Recipient determines that it cannot comply with Section 6.3(a), it will: (i) notify the Data Provider in writing; and (ii) either cease processing the Data Provider Personal Data or take reasonable and appropriate steps to remedy such non-compliance.
8. Liability
  • If the Agreement is governed by the laws of:
    • (a) a state of the United States of America, then, notwithstanding anything else in the Agreement, the total liability of either party towards the other party under or in connection with these Controller Terms will be limited to the maximum monetary or payment-based amount at which that party’s liability is capped under the Agreement (for clarity, any exclusion of indemnification claims from the Agreement’s limitation of liability will not apply to indemnification claims under the Agreement relating to the Data Protection Legislation); or
    • (b) a jurisdiction that is not a state of the United States of America, then the liability of the parties under or in connection with these Controller Terms will be subject to the exclusions and limitations of liability in the Agreement.
9. Priority
  • 9.1 Effect of these Controller Terms
  • If there is any conflict or inconsistency between the terms of these Controller Terms and the remainder of the Agreement then, subject to Sections 4.2 (Restrictions on Processing) and 8.2 (Processor Terms), the terms of these Controller Terms will govern. Subject to the amendments in these Controller Terms, the Agreement remains in full force and effect.
  • 9.2 Processor Terms
  • These Controller Terms will not affect any separate terms between astraone.io and Customer reflecting a controller-processor relationship for a service other than the Controller Services.
10. Changes to these Controller Terms
  • 10.1 Changes to Controller Services in Scope
  • astraone.io may only change the list of potential Controller Services at astraone.io/data_protection_policy
    • (a) to reflect a change to the name of a service;
    • (b) to add a new service; or
    • (c) to remove a service where either: (i) all contracts for the provision of that service are terminated; or (ii) astraone.io has Customer’s consent.
  • 10.2 Changes to Controller Terms
  • astraone.io may change these Controller Terms if the change:
    • (a) is as described in Section 10.1 (Changes to Controller Services in Scope);
    • (b) is required to comply with applicable law, applicable regulation, a court order or guidance issued by a governmental regulator or agency; or
    • (c) does not: (i) seek to alter the categorisation of the parties as independent controllers of Controller Personal Data under the Data Protection Legislation; (ii) expand the scope of, or remove any restrictions on, either party’s rights to use or otherwise process Controller Personal Data; or (iii) have a material adverse impact on Customer, as reasonably determined by astraone.io.
  • 10.3 Notification of Changes
  • If astraone.io intends to change these Controller Terms under Section 10.2(b) and such change will have a material adverse impact on Customer, as reasonably determined by astraone.io, then astraone.io will use commercially reasonable efforts to inform Customer at least 30 days (or such shorter period as may be required to comply with applicable law, applicable regulation, a court order or guidance issued by a governmental regulator or agency) before the change will take effect. If Customer objects to any such change, Customer may terminate the Agreement by giving written notice to astraone.io within 90 days of being informed by astraone.io of the change.