Data Privacy and Cookie Policy FAQ

Modified on Wed, 30 Aug, 2023 at 10:09 AM

Confer With is a UK-based supplier of real-time, video commerce platform services.

 

We at Confer With take the protection of personal data very seriously and strictly adhere to the rules laid out by data protection laws and the General Data Protection Regulation (GDPR-EU and GDPR-UK) and these feed into our Cookie and Privacy Policies. 


 

Common Questions

 

  • What’s the name of your website-technology/ technologies and should the client share information on this to Customers e.g. cookies, pixels etc.?
  • How is your technology categorized from a Cookie Policy perspective? (Necessary for the video-consultation | Functional | Performance | Statistics | Marketing)
    • Essential or Functional
      The cookie we place is to keep a shopping basket saved during the checkout process. This is only used to link a Confer With call to a sale so you can understand the effectiveness of the platform. The ratio of Calls vs Sales provides a key metric for our clients which is Conversion Rate - the number of Calls vs the Number of Sales.
        

Note : The platform will function without this however this will negate the ability to provide conversion rates back to the client.
  

  • Please give detailed descriptions of each implemented technology and their purposes of personal data processing :
    • Confer With Widget / SDK (deployed on your website)
      • This is used to launch the connection between the Customer and the Expert and the Customer's video call runs from this from their browser. 
      • This does not track personal data but does log the IP address which is used to drive the location based routing and also to allow us to block callers if needed. This is the only information captured about a customer by default.
      • Why are callers blocked? How do you (pre-)qualify an inappropriate caller?
        • Callers can be blocked at the request of the Customer or by the Expert. 
        • Prequalification is based purely upon a request by the Client to block any nuisance caller 

    • Expert Web Portal / Expert Mobile App Or Tablet App
      • No personal data is captured. Used to allow the Expert to login (via app or desktop) to serve the customer. 

    • Expert and Customer Surveys
      • The client controls what questions are asked to the Expert and Customer. By default, we would ask no question where the answer contains personally identifiable information (PII).
          
  • Do you track the website-users? If so, what are the tracking-outcomes? 
    • We don’t track website users, or their journey through your website and we do not profile customers relevant to GDPR Article 22. We place a cookie which stores a Confer With CallID only, once a call has happened (and only if a call happens). Subsequently, when a purchase is made by the Customer, we check for this cookie presence and report the contents back to Confer With (the CallID ) to allow us to link a sale to the call. This is still anonymous.
        
  • Please name the personal data (categories) for each processing purpose. 
    • Categories of data subjects whose personal data is processed

      Current and previous customers and Experts using our platform to take calls on behalf of our customer.

      [consumers, Current or previous customers, employees, staff, contractors, agents and other staff]

    • Categories of personal data processed

      • Category of Data subject: Customers

        • Type of Personal Data processed: IP Address, Browser information.

        •  Purpose of Personal Data processing: Legitimate interest to facilitate access to the Confer With platform only & access subject to confidentiality undertakings.

      • Category of Data subject: Employee.

        • Type of Personal Data processed: Name, Email (optional) and Profile picture (optional).

        • Purpose of Personal Data processing: Legitimate interest to facilitate access to the Confer With platform only & access subject to confidentiality undertakings.

        • Confer With would store employee names and email address as part of their Confer With accounts so they can access the system and receive emails from it. Emails can be set to generic inboxes if the Client chooses.

    • All calls into Confer With are anonymous by design hence, by default, we do not capture Customer data or store the video call.


      The exceptions are : 

      • IP address from the inbound call from the customer we capture and we create a digital footprint. These facilitates blocking calls e.g. Inappropriate caller etc and allows us to route to the local Expert. 

      • If the Customer chooses to add a Customer / Expert Survey and capture PI data. 

      • if the Customer chooses to pass further information to Confer With when a call starts (e.g. an authenticated Customer reference) 

      • Confer With can store any information passed to it when a call starts e.g. a CustomerID or Reference if they are authenticated.

In all cases, Confer With would be acting as a Data Processor only with the exception of the data necessary to link an anonymous call to a sale.
  

  • Is the technology 1st or 3rd party?
    • The platform technology is 1st party, we own our own IP. 
    • We use 3rd party technology for 
      • Our Datacentre
      • Common 3rd party components (e.g. Operating Systems etc) 
      • Communication Provider - Vonage as our webRTC provider
          
  • Who will receive the personal data from each technology?
    • All data is stored within Confer With and is available to relevant Client employees via our reporting. We do not share this with any third parties for any purposes.
        
  • Where is the personal data stored? (incl. inside or outside the EU/ EEA)
    • All data is stored inside the region you are deployed in UK,EU OR US (London, Frankfurt or Virgina depending on preference)
       
       
  • Storage/ retention periods for each technology
    • Event logs are held for 7 years by default however this can be altered if Client requires.

 

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article