Effective 21 October 2026 · version 2026-10-21
Cookies
The few cookies we set, and why there is no banner.
ShareSign sets the cookies needed to provide the service, first-party analytics cookies and one that remembers which version of a page you were shown. None are used for advertising or for tracking you across other sites.
| Cookie | Purpose | Lifetime |
|---|---|---|
| Sign-in session (set by our identity provider) | Keeps you signed in | Until you sign out, or 7 days |
ss_ws |
Remembers which workspace you were using | 1 year |
__clerk_redirect_count |
Prevents sign-in redirect loops | Seconds |
ss_discovery |
Remembers the first public page, campaign labels and referring domain seen in this browser, so we can understand which routes lead to useful work and paid businesses | 1 year |
ss_vid |
A random number that shows you the same version of a page each time you visit | 1 year |
Signers who are not account holders receive no cookies beyond those needed to load the page. Your browser's own storage may remember a signature style you chose; that never leaves your device.
We measure how the site and the app are used (pages reached, buttons pressed, where people give up) with PostHog. It sets a first-party cookie on sharesign.co that lasts a year, so a returning visitor is recognised as the same visitor; it sends through our own domain; it never carries a signing link, a document id, or anything you typed into a field; and it never records your screen.
We sometimes show two versions of a page to find out which serves people better, for example where a film sits on a page. ss_vid is a random number, set when you first open one of our public pages, so you see the same version on every visit, and so we can count how many people who saw each version went on to sign up. It holds nothing about you, only our servers can read it, and it is never set on a signing page.
The discovery cookie is set only on public pages for browsers, not on signing or private guest pages. It contains no document contents, private links or email address. When you create a workspace, its creator’s recorded source can be associated with that workspace. A partner code remains a separate record, and an unknown source stays unknown.