Skip to content

Menu

LexBlog, Inc. logo
NetworkSub-MenuBrowse by SubjectBrowse by PublisherJoin the NetworkGet StartedSubscribeSupportContact
Search
Close

Key Data Privacy Considerations for Vendor Management

By John Gotaskie on June 29, 2020
Email this postTweet this postLike this postShare this post on LinkedIn

Key takeaways from my partner, Odia Kagan’s recent presentation titled “Service Providers v. Data Processors: What Should Your Agreement Address?”  with Lexology and Exterra:

  • As the “business,” the “buck stops with you” as it relates to liability to the individual customer respecting processing their data.
  • Between you and your service provider/data processor, you can and should impose liability for tasks that you are engaging them to do for you.
  • To comply with your legal obligations under the General Data Protection Regulation, California Consumer Privacy Act and other data protection laws, be sure to perform due diligence on the vendor and ensure that they can deliver to the standard you need.
  • When performing the due diligence, cover both information security (How will you protect my data from unauthorized access?) AND privacy (What are you allowed to do with my data?)
  • Enter into a data processing agreement with your vendor. GDPR and CCPA have different requirements. You need to make sure that your concerns are addressed.

You can watch a recording of the really outstanding presentation at your convenience via this webinar link.

  • Posted in:
    Privacy and Cybersecurity
  • Blog:
    Franchise Law Update
  • Organization:
    Fox Rothschild LLP
  • Article: View Original Source

Call us at 1-800-913-0988 or email sales@lexblog.com.

Facebook LinkedIn Twitter RSS
The Library at LexBlog
  • About LexBlog
  • The Field We Built
  • Library at LexBlog
  • Our Beliefs
  • Our Team
  • Contact LexBlog
  • Disclaimer
  • Editorial Policy
  • Terms of Service
  • Get Started
  • Publishing Solutions
  • Compass
  • Submit a Request
  • Support Center
  • System Status
Copyright © 2026, LexBlog, Inc. All Rights Reserved.
Law blog design & platform by LexBlog LexBlog Logo