Who we are
Our website address is: https://scrib.works
Comments
When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.
An anonymised string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service Privacy Policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.
Media
If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.
Embedded content from other websites
Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.
Who we share your data with
If you request a password reset, your IP address will be included in the reset email.
How long we retain your data
If you leave a comment, the comment and its metadata are retained indefinitely. This is so we can recognise and approve any follow-up comments automatically instead of holding them in a moderation queue.
For users that register on our website (if any), we also store the personal information they provide in their user profile. All users can see, edit, or delete their personal information at any time (except they cannot change their username). Website administrators can also see and edit that information.
What rights you have over your data
If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Where your data is sent
Visitor comments may be checked through an automated spam detection service.
Cookies
If you leave a comment on our site you may opt in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year. If you visit our login page, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser. When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed. If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.
Analytics cookies
Google Analytics 4
The GA4 JavaScript tags use first-party cookies to distinguish unique users as well as unique sessions from a single user.
The following table describes each cookie set by GA4 JavaScript tags. To learn more about the data that Analytics collects, see Safeguarding your data.
| Cookie name | Default expiration time | Description |
|---|---|---|
| _ga | 2 years | Used to distinguish users. |
| _ga_<container-id> | 2 years | Used to persist session state. |
When linked to a Google Ads account, GA4 JavaScript tags set additional cookies used to provide Google Ads with a more reliable way to measure interactions customers have with your business. For more details on these cookies, see Our advertising and measurement cookies.
Advertising cookies
Meta
When the Meta Pixel is installed on a website, and the Pixel uses first-party cookies, the Pixel automatically saves a unique identifier to an _fbp cookie for the website domain if one does not already exist.
ClickID is a Meta-generated parameter that is passed with the URL of an advertiser’s website when a user clicks an ad on Facebook and/or Instagram. When Meta Pixel is installed on the website, Meta Pixel automatically stores ClickID value in the _fbc browser cookie once available.
LinkedIn Insights
LinkedIn enables third party sites to include some of its services such as Insight Tag, post embeds, Apply with LinkedIn and Sign In with LinkedIn. These services use a subset of cookies listed in the following table.
Cookies LinkedIn drops on third party sites
| Cookie Name | Domain | Purpose | Expiration | Provider |
| bcookie | .linkedin.com | Browser Identifier cookie to uniquely indentify devices accessing LinkedIn to detect abuse on the platform and diagnostic purposes | 1 year | |
| bscookie | .www.linkedin.com | Used for remembering that a logged in user is verified by two factor authentication and has previously logged in | 1 year | |
| JSESSIONID | .www.linkedin.com | Used for Cross Site Request Forgery (CSRF) protection and URL signature validation | Session | |
| lang | .linkedin.com | Used to remember a user’s language setting to ensure LinkedIn.com displays in the language selected by the user in their settings | Session | |
| lidc | .linkedin.com | To facilitate data center selection | 24 hours | |
| sdsc | .linkedin.com | Signed data service context cookie used for database routing to ensure consistency across all databases when a change is made. Used to ensure that user-inputted content is immediately available to the submitting user upon submission | Session | |
| li_gc | .linkedin.com | Used to store consent of guests regarding the use of cookies for non-essential purposes | 6 months | |
| li_mc | .linkedin.com | Used as a temporary cache to avoid database lookups for a member’s consent for use of non-essential cookies and used for having consent information on the client side to enforce consent on the client side | 6 months | |
| UID | scorecardresearch.com | Cookie used for market and user research | 720 days | Scorecard research |
| UserMatchHistory | linkedin.com | LinkedIn Ads ID syncing | 30 days | |
| AnalyticsSyncHistory | .linkedin.com | Used to store information about the time a sync took place with the lms_analytics cookie | 30 days | |
| lms_ads | .linkedin.com | Used to identify LinkedIn Members off LinkedIn for advertising | 30 days | |
| lms_analytics | .linkedin.com | Used to identify LinkedIn Members off LinkedIn for analytics | 30 days | |
| li_fat_id | Various, first party domain | Member indirect identifier for Members for conversion tracking, retargeting, analytics | 30 days | |
| li_sugr | .linkedin.com | Used to make a probabilistic match of a user’s identity | 90 days | |
| _guid | linkedin.com | Used to identify a LinkedIn Member for advertising through Google Ads | 90 days | |
| BizographicsOptOut | .linkedin.com | Used to determine opt-out status for non-members | 10 years | |
| li_giant | Various, first-party domain | Indirect indentifier for groups of LinkedIn Members used for conversion tracking | 7 days | |
| oribi_cookie_test | Various, first-party domain | To determine if tracking can be enabled on current domain | Session | Oribi |
| oribili_user_guid | Various, first-party domain | Used to count unique visitors to a website | 1 year | Oribi |
| ln_or | Various, first-party domain | Used to determine if Oribi analytics can be carried out on a specific domain | 1 day | Oribi |
| ar_debug | Various, first-party domain | Supports Google attribution reporting API integration to mitigate signal loss | Session |
A full list of cookies used by LinkedIn can be found on their website.