Termly Customer Success Stories: SiteCare

18:24 Events & Conversations

Managing website privacy compliance can be challenging for WordPress agencies and their clients, especially as privacy laws and requirements continue to evolve.

In this customer success interview, Ryan Sullivan, Chief of Staff at SiteCare, joins Sarah Warner, Manager of Strategic Partnerships at Termly, to discuss how SiteCare uses Termly to simplify privacy policy generation, cookie consent management, and ongoing compliance tasks.

Read the transcript

0:07
Today I'm joined by Ryan Sullivan, Chief of Staff at SiteCare, an industry-leading provider of managed WordPress services. SiteCare helps businesses keep their sites secure,

0:15
fast, and optimized for performance, SEO, and accessibility. They've made Termly a part of their own operations and now recommend it to their clients as well. Let's hear why. Hi, Ryan. Thanks

0:23
for joining us. Can you give us a quick intro?

Yeah. So you summed it up pretty well, but we are a WordPress support and maintenance company

0:30
primarily that touches lots of different parts of WordPress. So everything from performance optimization to accessibility fixes to lots of, we found

0:39
ourselves doing lots of legacy WordPress upgrades and compatibility testing and things that way. And it's really what we've focused on for the last 10 years

0:47
or more. So that's kind of the area where we've dialed in, and that's what we do every day.

0:52
Fantastic. And who are your main clients?

0:55
That is a very good question. So, we have a lot of clients, right? So, when we very first started out, the majority of our clients kind of fit into the

1:04
small business, a lot of them very small businesses. That's evolved quite a bit over the years. Now we find ourselves working with still plenty of

1:11
small businesses, but, you know, more in the medium-sized business and enterprise, and specifically in some relatively highly regulated spaces. So, things like

1:20
IT and healthcare and finance. Those are some of the areas where we find kind of concentrations or pockets of clients, and

1:27
that's what makes up the bulk of our client base today.

1:31
Fantastic. So, with so much of your work focused on performance, SEO, security, how important has data privacy become both for your team and for the clients that you support?

1:41
You know, it's become essential. Clients are asking more questions about privacy than they ever have before. Usually it kind of trickles down from legal, their

1:49
legal departments wanting to know, "Hey, are we in a good spot with this?" And, you know, those legal departments are asking the questions because of compliance

1:57
concerns with things like GDPR and CCPA and some of the other privacy laws that are out there. And there's a few.

2:04
Yeah, there's a few, and we know there are going to be a lot more, right? Like, always, always changing landscape. So that's something that we've just seen a lot

2:11
more.

Yeah, a lot more conversations about.

Yeah, absolutely. And before Termly, how were you and your clients managing privacy compliance? What was the approach?

2:20
We kind of found ourselves in the middle of it mainly because we did have clients start to ask these types of questions, and the solutions that were being used, frankly, were just like, they

2:29
were patchwork, right? Like, there's free plugins you can get on, you know, you can get on the WordPress.org repository.

2:36
There are a whole bunch of different platforms that aren't, they're kind of CMS agnostic. They're kind of meant to work with lots of different platforms.

2:43
We just found ourselves in a place of a client would say, "Oh, our legal team sent us this script from some random service that they signed up for. We need

2:51
this to be implemented." And it would be some kind of complex API integration just to get a consent banner and privacy policy displaying on their website,

2:59
right? It just felt like there were way too many pieces involved.

3:02
Yeah. So when you're looking at, like, the challenges or the gaps that kind of pushed you to look for a standardized, better solution, would you say that simplicity, ease of use, all of those

3:09
kinds of things were kind of the most important, or were there any other challenges that prompted you to solve this for your clients?

3:16
Yeah, so simplicity and ease of use were two huge ones. Typically speaking, when there's some kind of internal or external mandate coming to put good

3:25
compliance practices in place, clients want it done yesterday. And when that happens, it's like, okay, well, we understand you want this done quickly,

3:32
but the solution that you've handed to us is not a straightforward thing to implement the way that it, it's just not

3:40
straightforward to implement. So there was, like, just the speed to implementation, but also cost. Like, cost, frankly, was something that especially a lot of the clients and the

3:47
small business clients, it's like there are a lot of solutions out there that, you know, have a monthly fee with a comma in it to do those two

3:55
very basic things of, like, literally having a dynamic privacy policy and displaying consent banners and managing

4:03
cookies. And it's like, those never felt like great options to recommend either.

4:09
Yeah, yeah. So affordability really being a priority for your clients. Of course, that makes total sense. Tell me more about the questions that you get from your customers, from your clients.

4:16
What are they asking about data privacy, about compliance?

4:18
Typically, it's pretty surface-level stuff, and it depends on the organization, right? So if it is a larger organization, there's typically some

4:26
kind of internal mandate that says, you know, and they'll have, you know, hundreds of web properties for some of these larger organizations, right? And

4:33
they'll say, "Okay, internal mandate says we need to be compliant with whatever regulation, and we need to

4:41
have these elements in place on all of our websites by X date." In those types of situations, the details are probably

4:48
a little bit more granular. Like, it needs to adhere or apply to, you know, some particular specification, or it needs to

4:55
pass. And we have some clients who, you know, those rules change regionally, right? And they want the website to kind of handle all that dynamically. But with a lot of

5:04
clients, it's more driven by, "I read a headline where somebody like me got sued for not being compliant, and I just

5:12
want to do whatever I need to not get sued." And so a lot of the conversations start like that.

5:18
That's what I hear from other partners as well, is a question from clients are like, "How do we just avoid that, minimize risk, and check those boxes for limiting the

5:27
legal vulnerabilities?" So what made you decide to choose Termly, not just for SiteCare, but as something that you'd recommend to your clients? Was there, like, a specific moment that solidified

5:35
the decision, or was it a gradual buildup and, you know, the straw that finally broke the camel's back, or?

Yeah, really for us, especially in the type of work we do, solutions that are

5:44
reliable and repeatable are extremely valuable to us. So, we were just seeing enough volume of conversations and

5:50
tickets around this to say, "Okay, what can be our go-to solution that covers most of the needs of our clients?" We have some clients that are in some

5:59
really weird industries or, you know, they have some very complex configurations and setups. And we've kind of come to know that there isn't a one-size-fits-all solution for every

6:08
single edge case. But Termly, from everything that we were looking at, Termly was, like, covering more than 90% of all the potential use cases that

6:16
could come up. And so that's when we decided to standardize, build some workflows around it, build some client language around it, and really make

6:23
it something that's kind of just our immediate go-to when we get requests that fit into, that match most of the other requests related to this type of work.

6:32
Gotcha. Okay. So tell us a little bit more about how you're using Termly today, both for your own business, for SiteCare, and then across all of the WordPress sites that you manage. Is it

6:41
more on the consent management side or more on the policy generation, or what would you say? And I understand each client has their own kind of specific use case, but for the majority of them,

6:49
tell us a little bit more, like, how you're using Termly.

Yeah, I think the two features with Termly that get used more than any is definitely the policy generation. That was always a

6:58
really big sticking point before we found Termly because most of the solutions out there were strictly technical solutions, and it was bring

7:07
your own content, right? It was bring your own contract, bring your own policy to this technical solution. And that is a hard sticking point too, because then, you know, as the buyer, you're in a

7:16
situation where you're like, "Okay, well, now I have to go find not only an attorney, but an attorney that specializes in, you know, these different

7:23
privacy laws." And so there's just lots of friction and roadblocks. So the policy generation piece is super valuable, and then consent management is the other

7:31
piece that pretty much all of our clients who are using Termly adopt really quickly. You kind of see it everywhere now, but we saw a big

7:38
concentration initially in Europe, but that's really, you know, that's really come stateside for a lot of folks.

7:44
Yeah, that makes sense. Tell us a little bit about the workflow and the onboarding. How easy was it to integrate Termly into your processes? Do your clients find the setup process as smooth?

7:52
Yeah, I've got a couple of different anecdotes related to that. Trying to think of one case that came up that I think kind of illustrates the point really well is we had a client who was

8:02
using another tool. They had been using it. They actually hired a freelance developer to implement this other tool for them. They came to us after the

8:10
freelance developer had spent 18 billable hours getting everything set up and implemented, and it still wasn't working properly. Obviously, at that

8:18
point, the client was super frustrated, and they had spent thousands of dollars. And we were like, "No, no, no, no. Pause. Hit the brakes. Sign up here.

8:27
It's a few hundred bucks a year. Send us the login back, and we'll go through the onboarding on your behalf based on, you know, whatever criteria you've given us."

8:36
And the next day, the problem was solved for them, and they were just, like, totally. So, I mean, they were back to us

8:43
with their new Termly account within a few minutes, and they were just, they were totally covered in one day for something that they had been waiting

8:52
literally weeks on and spent thousands of dollars on. I mean, that's just to say, like, the onboarding workflow and the implementation workflow is just

9:00
so much easier than, well, than anything else we've tried.

9:02
Wow, what an incredible story. What was their, what was that client's feedback? What was the reaction when you said, "Hey, we can solve this for you in place so quickly?"

They were annoyed.

9:11
They were pretty.

9:13
Yeah, they were like, "How come I didn't know about this before?" You know, that kind of sentiment.

9:17
Obviously not annoyed with us, but really happy that we had this recommendation for them. But then they're, like, just frustrated because it was

9:24
like, "How did I end up in this situation in the first place?" It's been a great, a great answer for them.

9:28
Yeah, wow. So recommended kind of by default on all new projects and clients when you are onboarding new clients. Tell me how the

9:37
policy generation works, like what's the process as far as with the agency?

9:41
Are clients invited in to create their privacy policy entirely on their own, or do you help with that?

Yeah, we typically do it just kind

9:50
of under their direction, right? So that's kind of the role we play. So lots of times we'll just go through the onboarding with them on a Zoom, take their guidance on the questions that the onboarding wizard is asking.

10:00
And then the other thing that is, I know this isn't a direct answer to your question, but one of the things that's, like, become really helpful is the fact

10:06
that Termly auto-updates its policies as well. So when there's some kind of regulation change or there's some kind of changes that does have an impact on

10:15
the client, like, they aren't going back to their attorney every three months for revisions, and they don't even have to think about it really, right? Like, that's the, to me, that's the big thing, is

10:24
like, I can just.

How often do I need to?

Yeah.

10:27
Yeah, I can just, like, mentally check that off and know it's sorted. So it's not just the initial policy generation, but the ongoing

10:34
upkeep of it as well that our clients have really bought into.

Would you say that that's the feature that has the biggest impact for you and your

10:42
clients, like the auto-updating and the notification for privacy law changes, or is there something else that's had kind of the biggest impact?

10:51
Well, I think, you know, I think if you're thinking about it strictly from a business perspective, that's the piece that seems to feel most like a blanket

10:59
for the client that makes them feel good. From a technical implementation standpoint, the thing that I think has become extremely useful is the

11:08
automated script detection that essentially scans the website and says, "Here are the things that you are using for tracking on your website," and then

11:16
giving us on the user side the ability to, you know, organize those into the types of data we want to allow collection from before consent is given

11:24
or after. That's something that with other tools is a lot more complicated process. Typically requires manual code-level review of, "Here are the things that

11:33
are collecting data on the website."

11:35
So the automation, big time saver.

Yeah.

11:37
Yeah, the set it and forget it. It's meant to be no longer top of mind for you. And so that sounds like that's been a significant value. That's great. Tell

11:46
me a little bit about some of the measurable benefits that you've experienced in using Termly and recommending it to your clients of, like, saving time or saving cost, reducing the

11:53
legal risk, of course, but improving trust or, you know, for SiteCare itself, expanding on your service offerings. What are kind of the

12:01
biggest benefits that come to mind?

It does save us time. It also, I really think a benefit that, and this is something that we, like, sell with our

12:10
services too, is this idea of reduced uncertainty. Just knowing that something is handled. Termly very much checks that box. And the last thing is it has

12:17
improved our trust with clients. Like that story I told you originally, that client, like, they've gotten out of the game of looking for freelancers to do

12:26
random things for them. When they need a solution for something, they come to SiteCare and say, "What's the best tool for us to be able to do ABCD?" And

12:33
that's been a huge benefit for us. Once we can create that mental shift for the client and get them to trust us enough

12:40
to ask us what best practices look like and what is the best way to do a thing, like, that solidifies our relationship with them for a very long time.

Yeah,

12:49
it's a great thing to be able to offer expertise and guidance on everything from SEO or page speed all the way over to legal things like privacy compliance.

12:57
So that's really a significant value-add.

12:59
That's really, that's amazing. Tell me a little bit about what kind of feedback you've gotten from clients after implementing Termly.

13:05
Yeah, I would say, I would say less intimidated. It's something that on the surface is very overwhelming because there are legal components, there are

13:13
technical components, there are, you know, a lot, there's a lot of FOMO, you know, there's a lot of, like, FUD out there. Just articles that are saying, "Here's why

13:21
you should be scared," and all these types of things. And that's what they find when they start doing their research around it. And it creates a

13:28
scenario where they just feel like it's taken care of, and it's something that doesn't have to be a scary proposition. It's something that

13:36
they can, I mean, we've had some clients say to us, "I think I might have even been able to set that up myself." And that level of confidence

13:45
after feeling so overwhelmed, that goes from one end of the spectrum to the other in terms of how the client perceives a potential challenge with their website.

13:55
Yeah, yeah, absolutely. So you really are taking that kind of challenge or, you know, intimidating speed bump as they look at privacy and go, "Oh my

14:02
gosh, I kind of don't really know what to do." And then you're giving them that guidance. Here's the solution. And then they're coming away from it saying, "That was easy enough. Maybe I could have even

14:09
done it myself." And then understanding that SiteCare, you know, is positioned to be the expert on that and give them the guidance on it and say, you know, recommending solid solutions.

14:18
So that's great. What would you say to other WordPress professionals or site owners who haven't yet prioritized privacy compliance? They're still trying to manage it all manually, or maybe they

14:27
don't, they aren't aware of the solutions that are out there, that are still in that kind of, like, scary, intimidated space.

14:34
It's risky. It's like, you know, not filing your taxes year after year and then just hoping you never get audited type of thing, right? Like, eventually that type of problem does

14:43
catch up to you. My recommendation would be to, you know, just give Termly your money, get this thing sorted out, and move on with your life.

14:51
You know, that's, and it's way easier than filing your taxes, too. So it doesn't have to be as scary as it doesn't. It really doesn't. Like, it really doesn't have to be a scary

15:00
proposition. But in my mind now, just because I have worked in this space for as long as I have, it's the kind of thing that not addressing it is actually

15:08
a lot scarier because I have seen the court documents. I've seen real copies of real lawsuits. And not just, like, you

15:15
know, there are lawsuits, but there are also just, like, you can create a lot of customer dissatisfaction by not

15:22
taking privacy seriously. And customers are more aware than they ever have been.

15:27
So when they come and they make a, you know, when they want to know how their data is being used and you don't have a clear answer for that or you don't have a policy that clearly addresses that,

15:36
that's a deterioration of trust, and that's something that you're going to end up, you know, you're going to take a hit on that in lots of different ways. Either they don't come back to the

15:44
website or they don't buy the product you're selling or lots of other smaller things that aren't at the scale of a lawsuit, but, you know, it's death by a thousand paper cuts. Really.

15:52
Yeah, yeah. I'm so glad that you mentioned that because really building trust through transparent privacy practices, it's so huge and often overlooked. So I'm really glad that you

16:00
brought that up. Are there any WordPress-specific considerations that you would consider, that you'd like to note? Of Termly's over two million

16:09
users, a vast percentage of them, of course, are WordPress sites. Can you think of anything, either challenges or opportunities, that would be unique to the WordPress community?

16:17
Yeah, depending on how data is stored within your CMS, a request for deletion may be more complicated to actually make

16:25
happen than it seems on the surface. You just understand, like, when a client makes a purchase on your e-commerce site, where all of their personal and private

16:33
data is stored in that workflow, and if they come to you and say, "I want all of my data deleted from your database," understanding what's really involved in

16:41
that. So that either needs to be very clear in your privacy policy, or that we need to find more clear ways on what that data removal process looks like.

16:50
I can hop in with some good news on the data discovery and deletion front. We are actually, we're in the process of developing an end-to-end solution for

16:58
that specifically. So that'll entail, you know, the data mapping, eventual integration with third parties for discovery, automation around

17:06
management of those requests when those users do submit the form and say, "Hey, I want all my data deleted." Just simplifying that entire process. So that's in the works, and that's

17:15
kind of exciting there. So I'll throw that in.

17:17
Super exciting. Yeah, yeah. And the other one I was going to bring up is more for developers, but depending on how you're managing a website, there's a good chance that

17:24
there are replicas or copies of the website in different places. Like, a very common example is staging sites, right?

17:32
And really, in any non-production environments, most privacy policies are going to have something along the, there's going to be some kind of data

17:40
anonymization that should be happening in non-production environments. So just something to be aware of for engineers or developers who are working

17:48
with these secondary or tertiary, you know, environments is, are you managing data in a way that does comply with the customer's privacy policy by making sure

17:56
that, you know, the data you're working with is anonymized and protected?

18:00
Yeah, that's a great point. I'm so glad you brought that up. Well, Ryan, thanks so much for showing us how SiteCare has really turned privacy compliance into a

18:08
very significant value-add, both for your business and your clients. It's been great to chat with you and get an understanding of how SiteCare has really fine-tuned clients' experience around data privacy. Like you said, just taking

18:16
compliance from a challenge and really turning it into an opportunity.

Enter Your Website URL

In order to help you create a cookie solution that is GDPR and Cookie Law compliant, we must first scan your website for cookies.