Data handling

From a LinkedIn profile we collect what anyone can see without logging in: name, headline, location, follower and connection counts, listed skills and current role, and recent public posts with their public engagement counts.

Nothing behind a connection wall. No private profile fields. No email or phone enrichment, which means we do not send a name to a third party to have a personal address or number looked up, and we do not buy lists. The only email address we hold for you is the one you typed when you signed up.

We never ask for your LinkedIn password and we cannot post as you. To confirm a profile belongs to the person claiming it, we ask them to place a short one-time code in their own LinkedIn headline, we read the public profile once to look for it, and then the code is discarded.

We do not automate against LinkedIn from a client's account, from a member of staff's account, or from the 8x company page. No connection requests, no messages, no likes, no follows, on anyone's behalf. A creator publishes their own post from their own profile, by hand.

Installing it is optional and nothing about being paid depends on it. It runs only when a creator clicks Refresh my stats, only from our site, and never on its own. It reads the impression counts and post identifiers on that creator's own LinkedIn analytics page and sends them to their own 8x dashboard.

It reads no browsing history, runs on no other website, stores nothing on the device, and takes no action on LinkedIn. Removing it stops it completely.

Personal data goes into a database. It is never committed to our source code, and neither are credentials or LinkedIn account details of any kind. What lives in the code is the schema, the aggregates and the analysis, never the rows.

Post metrics are kept as a time series: a new reading is a new row, and yesterday's number is not overwritten. So a figure we showed you last month is still the figure we showed you, and a history can be checked rather than taken on trust.

We read public profiles through several interchangeable upstream providers behind one client, because providers break and no single one of them is allowed to be load-bearing. Every call is logged and rate-limit aware, so how often we asked, and for what, is a matter of record rather than recollection.

Data collected in bulk lands in exactly the same place, through the same checks, as data collected through an API. There is no second path with looser rules.

Campaign links pass through us so a brand can tell which creator sent which visitors. When a link is used we record that it was used, when, and which site it came from. We do not store the visitor's IP address, we build no advertising profiles, and we sell nothing to data brokers.

A client can add our measurement script to their own site to count which visits led to a sign-up or an enquiry. It records that an action happened and which campaign link preceded it. It does not read form contents and it is not used to follow people across unrelated websites.

Campaign results are measured post by post, for a window we state, per creator. No blended averages and no “up to” claims. Money is shown as agreed, earned, on its way, or paid, and an estimate is never shown as money.

A figure we could not read is shown as a figure we could not read, never as a zero and never as a plausible default. A market benchmark we have not checked against our own collected data is labelled unverified until we have.

A creator can remove the extension, ask us to stop collecting from their profile, or close their account outright. Anyone can ask what we hold about them, ask for a copy, ask for a correction, or ask us to delete it.

Write to privacy@8x.business. The privacy policy sets out the rights behind those requests and how long we take.