Seegnals shows a cookie banner on seegnals.com and asks before setting anything beyond the cookies strictly necessary for the site to work. The banner offers three categories; the table below lists what each one covers and, where relevant, which specific tool it controls.
Strictly necessary: always on
These keep the site and your session working and are exempt from consent under the ePrivacy Directive, so there is no toggle for them.
| Cookie | Purpose | Duration |
|---|---|---|
| Supabase session cookies | Keep you signed in to your workspace at app.seegnals.com | Session / refresh-token lifetime |
c1_consent | Remembers the choice you make in the cookie banner, so we don't ask on every page | 12 months, then we ask again |
Analytics: only after you say yes
Covers how pages get read and, on the marketing pages and our sign-in screens only, session recordings, so we can see where the site is confusing without watching anyone who is signed in and working.
| Tool | What it does | Cookies it sets | Duration |
|---|---|---|---|
| Google Analytics 4 (via Google Tag Manager) | Page views, traffic sources, on-site behaviour | _ga, _ga_* | Up to 2 years |
| Microsoft Clarity | Session recordings and click/scroll heatmaps, on seegnals.com and the app's sign-in pages only | _clck, _clsk | Up to 1 year (_clck), 1 day (_clsk) |
Clarity never runs inside your signed-in workspace (app.seegnals.com/app/**), regardless of this consent choice. Those screens show your prospects' names, addresses and the replies they sent you. That is personal data belonging to third parties you are the controller of, under our Data Processing Agreement. Recording those screens would mean sending that data to a sub-processor not named in the DPA, so the code that loads Clarity is written to never do it there, rather than merely configured not to.
Marketing: only after you say yes
Reserved for advertising tags configured inside Google Tag Manager, for example Google Ads or LinkedIn conversion tracking, if we start running paid campaigns. None are enabled at the time of writing. If that changes, this table will list the tool and its cookies before it starts running, the same way Analytics is listed above.
A choice with nothing behind it yet
The consent banner and the categories above are live today. The Google Tag Manager container and Microsoft Clarity project they are wired to are not created yet. That is on our own to-do list. Until they exist, saying "yes" to Analytics sets no additional cookie beyond what this page already lists, because there is nothing configured to load. When we do turn them on, no code change is needed for this promise to keep holding: they load only behind the same consent check described here.
Managing and withdrawing consent
Use the "Cookie settings" link in the footer of any page to reopen the banner and change your answer at any time. Withdrawing is as easy as giving consent. You can also block or delete cookies through your browser settings; doing that for the Supabase session cookie will simply log you out of the app.
We will ask again after 12 months, or sooner if we change what a category covers. For example, if we start running actual marketing tags, we treat that as a new question and ask again, rather than adding it silently to a category you already agreed to.
Contact
Creathink One · Warsaw
Email: privacy@seegnals.com