The GDPR and CCPA
are the de facto standards
that define the rules
concerning the collection
and processing of
personally identifiable
information, and our
product team knows the
relevant sections of these
agreements inside and out.
We didn’t have to alter
our Pulse or the product
roadmap because Pulse was
designed from the ground
up not to require
Personally Identifiable
Information (PII).
We don’t collect or
traffic in PII,
period.
If you install
Pulse, we receive only an
approximate latitude and
longitude and timestamp
for your visitors.
Depending on your specific
integration, we receive
this data from either your
Content Management System
(CMS), or from Google
Analytics.
We take the
approximate latitude and
longitude you send us, and
we return information
about that
neighborhood. We
return demographic
attributes such as median
income and home ownership
rate, as well as
information about what
people in that
neighborhood talk publicly
about online using
Geosocial
Listening.
Geosocial Listening
is a process by which
geotagged, public posts on
social media are stripped
of any identifying
information, and then
clustered using machine
learning. Interesting
clusters are analyzed and
labeled by a team of data
scientists and
ethnographers. We don’t
have access to, nor do we
need, household-level data
for this to work.
It’s also important to
point out that the body of
data we use for Geosocial
Listening isn’t your data,
it’s publicly
available.
We look for
patterns in your traffic
data indicating
naturally-occuring
clusters and use them to
help your marketing team
better understand your
audience. We also
watch for organic pulses
in traffic and look for
changes in those interest
segments.
For more
information, please refer
to our Pulse
License
Agreement, Pulse
Terms of
Use,
and our GDPR
Compliance
Statement.
And of course, if
you have any questions
don’t hesitate to contact
us!