Linx

Cookie Policy

This English version is a translation provided for convenience. The binding version of this document is the Hebrew original, which prevails in the event of any conflict or discrepancy. This policy explains which cookies and similar technologies Linx Tech ("LINX", "we") uses, on the LINX site (linxcard.me, including the store, checkout and the dashboard) and on the customer pages that run on LINX (linxcard.me/s/... addresses and customers' own domains): what each one does, how long it is kept, and how to choose, change and withdraw. Everything else we process is described in the Privacy Policy. Version: 1.5 · Last updated: October 10, 2026

1. What cookies and similar technologies are

• Cookie: a small text file a site stores in your browser, which is sent back with later requests to that site. • Local storage (localStorage): data a site stores in your browser that stays after the browser is closed, until it is deleted. • Tab storage (sessionStorage): like local storage, but deleted when the tab is closed. • Vendor pixels and scripts: a vendor's code (for example Google's or Meta's) loaded into a page. It can write cookies and storage, and it sends data to the vendor. • First party and third party: a first-party cookie or storage key sits on the domain of the page you are on (linxcard.me, or the page owner's domain), even when an outside vendor wrote it (for example Google's _ga). A third-party cookie sits on the vendor's own domain (for example clarity.ms, tiktok.com or linkedin.com). LINX can neither read nor delete third-party cookies. Below, "cookies" covers all of these.

2. Three categories

1. Necessary. What the service cannot work or stay safe without: sign-in, cart and checkout, security, language and accessibility, remembering your cookie choice, and technical error reports. Always on, no consent needed. 2. Statistics. Tools that show how the site is used: Google Analytics, Microsoft Clarity, Sentry recordings and performance tracing, and LINX's own usage data. On customer pages: the page owner's Google Analytics, and recognising a returning visit to the page. Consent only. 3. Marketing and embedded content. Advertising measurement and tailored ads: the Meta pixel and Conversions API, and ad click ids. On customer pages: the page owner's Meta, TikTok and LinkedIn. Also showing embedded content (outside providers' videos, maps and players, section 8) without a press on each one. Consent only. There is also anonymous measurement: counting visits to customer pages for the page owner, and measuring page load speed. It stores and reads nothing in your browser, so it is not a category you choose, but you can object to it (section 4). How it works: section 5.

3. Your choice

• Before you choose, no statistics or marketing tool loads and no identifier is written to your browser. Only necessary cookies and anonymous measurement run. Ignoring the banner keeps you in this state. • The banner has two equal buttons, "Accept all" and "Necessary only", with the "Customize" link beside them. "Customize" lets you choose each category separately, with no switch turned on in advance. • The banner appears after a short scroll or after 8 seconds, so it does not cover the page the moment it opens. Until you choose, no statistics or marketing tool is loaded. • The LINX site and each customer page ask separately. A choice on the LINX site does not apply to a customer page, and a choice on one customer page does not apply to another page or to the LINX site. • On a customer page, the banner appears only if the page owner switched on a statistics or marketing tool, and it names only the tools the page really runs. A page with no such tools shows no banner, and LINX counts its visits the anonymous way only. • Your choice is kept in your browser for 12 months, then we ask again. We also ask again sooner if we add a vendor, a purpose or a category. A change of wording alone does not trigger a new question. • Global Privacy Control: if your browser sends this signal, marketing cookies are off, whatever choice is stored.

4. How to change or withdraw

The "Cookie settings" link ("הגדרות עוגיות" on Hebrew pages) is at the bottom of every page of the LINX site, on the checkout page, in the dashboard menu, and at the bottom of every customer page. It opens the settings with your current choice. There you can switch each category on or off, and choose "Do not measure my visit" (on the LINX site) or "Do not count my visits" (on a customer page). When you switch a category off: 1. The new choice is saved and recorded (section 10). 2. The category's tools are told that consent was withdrawn, and stop. 3. The category's cookies and storage, as listed in the tables in section 11, are deleted from this browser, on every domain form (www.linxcard.me and .linxcard.me, or the page owner's domain). 4. The page reloads once. In the second between the click and the reload, a tool that was already running may send data it collected while consent was in force. After the reload it does not load. Cookies a vendor keeps on its own domain (table 11.4) cannot be deleted by LINX. You can delete them in your browser settings or with the vendor. You can also block or delete any cookie in your browser settings, but blocking necessary cookies and storage may break sign-in, the cart and checkout.

5. What runs without consent

5.1 Necessary cookies and storage

The full list is table 11.1. None of them is an advertising identifier and none tracks you across sites. Among them: • Sign-in: Supabase keeps your session in localStorage (sb-*), not in a cookie. • Your cookie choice (linx_consent for the LINX site, and linx_consent:s:<page id> for each customer page separately). • The embedded-content providers you chose to load (linx_media:*, for each page separately): after you press a video or a map, more content from the same provider on that page loads without another press (section 8). • Cart and checkout. • Secure card tap: a 15-minute cookie proving that you arrived from a real tap. • Ambassador discount: an ambassador code from a link (?ref=) is held in the page's memory for this visit only. It is stored for 30 days only if you press "להחלת ההנחה" (apply the discount), and it is sent to us at purchase so the ambassador is credited. The arrival through the link is counted as a number (code, page, time), with no IP address and no browser details. • Chat: the conversation id is created only when you open the chat. • Language, accessibility, and a signed-in user's dashboard state (drafts, display, closed notices).

5.2 Error reports (Sentry)

When an error occurs on a page, a cleaned technical report is sent to Sentry (Functional Software, United States): the error, where in the code it happened, the page and the browser. No screen recording, no user details, nothing stored in the browser. Sentry recordings and performance tracing are statistics and run only with consent (section 6).

5.3 Anonymous measurement: counting visits to customer pages

A page owner sees how many people viewed the page, clicked links, saved the contact and sent an enquiry. LINX counts this for the owner with no cookie, storing and reading nothing in your browser, except your cookie choice (and, for someone signed in to LINX, their session; see "Our visits and yours" below). What is sent. With each view or action the browser sends LINX's server: the page, the kind of event, the arrival channel (NFC tap, QR or link), campaign tags from the address (utm), the site that referred you (its base address only, no path and no parameters), the device type and the browser's user-agent string. The daily key. To tell visitors apart within one day, the server computes a key in memory: an HMAC-SHA256 of the page, the IP address and the user-agent string, with a random "salt" for that day. The key differs for every page and changes every day, so a person who reads two pages, or the same page on two days, gets keys that are unrelated. The IP address is not stored. The salt is deleted 30 minutes after midnight (Israel time), and from then on nobody, LINX included, can link that day's keys to an address or to another day. This is why "visitors" on the owner's dashboard is an estimate: someone who returns on another day is counted again. What is stored. The page, the event, the arrival channel, the campaign tags, the referring site, the device type, the user-agent string (to filter out bots and to break visits down by device and browser), an approximate city and country from our server's headers (no outside location service), the daily key, and the arrival id of a tap if there was one. View and tap records are deleted after 90 days. By your choice on that page: State · What happens | Before a choice, or a page with no banner · Counted with the daily key, as described above | "Necessary only" · The visit is counted as a number only: no key, no referring site and no city (country only). It counts as a view, not as a visitor | "Do not count my visits" · Nothing is sent | Statistics consent on the page · In addition, an id for this page only is stored in your browser (linx_visitor_id:s:<page id>, up to 13 months), which recognises a returning visit to this page | Three more details. • Arrival id: after a card tap, the server adds a one-time arrival id to the page address. The page holds it in memory only and uses it to connect the tap to the view and to an enquiry. It is sent in every state except an objection. • An enquiry you send is always saved, because it is your request. It is linked to the visit it came from, by the arrival id or the daily key, on the same page and within 30 minutes. • Our visits and yours: if you are signed in to LINX and visit your own page, the browser attaches your user id from the existing session, so that your visit is not counted as a visitor of yours. The IP address is also checked, in memory only, against LINX's own list of addresses, so that our team's tests are not counted.

5.4 Anonymous measurement: page speed

After a page loads, the browser sends LINX's server the load timings, the kind of page (a group, not the full address), the browser family, and an Israel-or-abroad flag. No cookie, no identifier, no IP address. A "signed in or not" flag is sent only with statistics consent on the LINX site. The measurement stops after "Necessary only" or an objection.

5.5 Requests to vendors without cookies

• Google Fonts: the fonts of the site and of customer pages load from Google, so Google receives your IP address and browser details on every page load, before any choice too. No cookie is written. • Cloudflare Turnstile: on some forms, an anti-bot check that runs in a frame from Cloudflare's domain.

5.6 Event invitation pages

Event invitation pages and the mailing-list unsubscribe page store no information about the visitor on the device, so they show no banner.

6. On the LINX site: statistics and marketing, consent only

Statistics: • Google Analytics 4 (Google): statistics only. Google's advertising features (ad storage, Google signals, ad personalisation) are off, even after "Accept all". Its cookies are kept for up to 13 months. • Microsoft Clarity (Microsoft): usage recording (clicks, scrolling, movement) to improve the site. Input fields are masked, and on the checkout, contact, sign-in, registration and cancellation pages the whole page is masked. Clarity is loaded without Microsoft's advertising sync (Bing), with its ad storage off. • Sentry (Functional Software): screen recording of some visits, with text masked, and performance tracing, to find faults. Only on LINX's own pages, never on customer pages. • LINX's own usage data: page and button events on the site and in the dashboard, stored by us. A visit id for the tab, the campaign that first brought you (up to 13 months) and the campaign tags of the visit. No permanent visitor id. Marketing: • Meta pixel and Conversions API (Meta Platforms): measure whether LINX advertising brought you, and let LINX show you its ads. The pixel writes _fbp. If you arrived by clicking a Meta ad, _fbc is written too. Events sent through LINX's server (Conversions API) are sent only with marketing consent, and carry the event, the page, the IP address, browser details and Meta's cookie ids. Your email, phone number and name are not sent (Advanced Matching is off). Up to 90 days. • Ad click ids (fbclid, gclid) are kept for the visit only with marketing consent.

7. Customer pages

• Who is responsible. A customer page belongs to its owner. The tools the owner switched on, Google Analytics (statistics) and Meta, TikTok or LinkedIn (marketing), are the owner's: for them the page owner is the controller of the data, and LINX runs them on the owner's behalf as part of the service. • Only after consent on that page. The owner's Google Analytics loads only after statistics consent, and Meta, TikTok and LinkedIn only after marketing consent. • The owner's Google Analytics writes cookies under its own name (lxo_*) and on the page's path, not shared with the LINX site or with any other page. Google's advertising features are always off in it, even with marketing consent. Only a Google Analytics id (starting with G-) is loaded. • The owner's Meta writes _fbp and _fbc. On pages under linxcard.me, _fbp is one cookie for the whole domain: it is shared by the customer pages where you accepted marketing, and by the LINX site if you accepted marketing there. It is read only on a page where you gave consent, and withdrawing marketing on any of them deletes it. • The owner's Conversions API. If the owner connected it, an enquiry you send through the form passes through LINX's server to Meta on the owner's behalf, including the email and phone number from the form in hashed form, the IP address and browser details. Only if you accepted marketing on that page. • The owner's TikTok and LinkedIn write the keys in table 11.3, and cookies on their own domains (table 11.4). • LINX's own advertising. LINX's pixel does not run on customer pages, and LINX sends Meta no advertising event from customer pages, also not when you send a form. • LINX statistics on a customer page: with statistics consent on the page, an id that recognises a returning visit to this page only (section 5.3). • A customer's own domain: the same rules. The cookies sit on the owner's domain.

8. Embedded content

YouTube videos (in the privacy-enhanced youtube-nocookie.com player), Vimeo (with its "do not track" setting), Facebook videos and feeds, Google Maps, Spotify, SoundCloud, booking calendars (such as Calendly and Cal.com) and Google's document viewer on customer pages, and the films on LINX's home page and /videos: all of these are shown as an image with a line naming the vendor, and do not load before you say yes. There are two ways to say yes: • A press. Pressing a video, a map or a player loads it. The press is remembered for that vendor on that page (linx_media:*, 12 months), so more content from the same vendor on the page, now and on your next visit, loads without another press, and a video loaded that way does not start by itself. A press on one page does not apply to any other page. • Marketing consent on that page ("Accept all", or the "Marketing and embedded content" switch under "Customize"): the page's embedded content loads without a press. Global Privacy Control switches this way off, not the press. Video galleries on customer pages, and the films on LINX's home page and /videos, always wait for a press, to keep the page light. "Necessary only", or withdrawing marketing on a page, also forgets the presses remembered on it. YouTube preview images are served from LINX's server, so YouTube receives no request before then. Once the content loads, the vendor receives your IP address and browser details and may set its own cookies under its own policy. Those cookies are outside "Cookie settings".

9. Tapping an NFC card

When you tap a LINX NFC card or scan a LINX QR code, our server sends you on to the page and records the tap: the card, the time, the device and browser type, an approximate city and country, and, on cards that support it, the chip's tap counter, to detect reuse of an old link. To tell tappers apart, the server derives an id from the IP address, the card and the date. The id changes every day and differs for every card, so it does not link taps across different cards or different days. The IP address itself is not stored. Nothing is stored in the browser, except the secure-tap cookie (15 minutes) on secure cards. The data is deleted after 90 days.

10. The record of your consent

Every choice and every change is recorded by LINX, so that we can show which choice you made and when: a random id of the choice (the same id stored in your browser), the site or page, the version of the question, the answers (statistics, marketing, objection to anonymous measurement), where it was made (banner or settings), the browser family (for example Chrome/Android) and the time. No IP address and no full user-agent string. The id is attached to what marketing tools send, so that every send is tied to the choice that allowed it. The record is kept for 36 months, then deleted.

11. Tables

"Where": the LINX site, customer pages, or both. A * at the end of a name means any key that starts that way.

11.1 Necessary (always on)

Name · Type · Provider · Purpose · Lifetime · Party · Where | linx_consent · localStorage · LINX · Your cookie choice on the LINX site (choice id, version, answers and time) · 12 months · First · LINX site | linx_consent:s:<page id> · localStorage · LINX · Your choice on one customer page · 12 months · First · Customer pages | linx_media:* · localStorage · LINX · The embedded-content providers you pressed on a page, so more of their content on that page loads without a press · 12 months · First · Both | Consent keys from before October 2026 · localStorage · LINX · Read once: a refusal is kept as a refusal, an old consent does not count · Deleted on the first load · First · Both | sb-* · localStorage · LINX (Supabase) · Your sign-in session · While you are signed in (refreshes) · First · Both | linx_secure_session · Cookie · LINX · Proof of a secure card tap · 15 minutes · First · Both | linx_secure_session_* · Cookie · LINX · Old per-card tap proof, no longer written · Expired · First · Both | linx_cart · localStorage · LINX · Shopping cart · Until the order is complete · First · Both | checkout_* · localStorage, sessionStorage · LINX · Checkout form state · Until the order is complete, or until the tab closes · First · Both | pending_* · localStorage · LINX · An order awaiting payment confirmation · Until the payment returns · First · Both | cookie_consent_approved · sessionStorage · LINX · Terms acceptance in progress. Despite the name, unrelated to cookies · Until the tab closes · First · Both | linx_oauth_*, linx_auth_* · sessionStorage · LINX · Sign-in in progress, and protection against sign-in faults · Until the tab closes · First · Both | linx_auth_storage_failed · localStorage · LINX · Marks a session that failed to save · Until the next sign-in · First · Both | linx_login_recorded_* · localStorage · LINX · When this browser last recorded your sign-in in the security log, so several open tabs record one sign-in once · Until the next sign-in · First · Both | linx_scan_return_v1 · sessionStorage · LINX · Returns a card owner to their tap after sign-in · Until the tab closes · First · Both | linx_role_cache_v1, linx_tier_cache_v1 · localStorage · LINX · Fail-safe copy of the signed-in user's role and plan · Until sign-out · First · Both | linx_shell_reload, linx_chunk_reload_times · sessionStorage · LINX · Stop a failed load from reloading in a loop · Until the tab closes · First · Both | linx_deploy_reloaded_* · sessionStorage · LINX · A new version of the site reloaded this tab once, and must not do it again · Until the tab closes · First · Both | __linx_probe · sessionStorage · LINX · Checks that storage works · Deleted at once · First · Both | linx_user_lang · localStorage · LINX · The language you chose · Until changed · First · Both | a11y_prefs, accessibility-settings · localStorage · LINX · Accessibility settings · Until changed · First · Both | a11y_fab_hidden · sessionStorage · LINX · The accessibility button was hidden in this tab · Until the tab closes · First · Both | sidebar:state · Cookie · LINX · Dashboard side menu open or closed · 7 days · First · LINX site | linx_ambassador_ref · localStorage · LINX · An ambassador discount you chose to apply ("להחלת ההנחה") · 30 days · First · Both | linx_ref · Cookie · LINX · An ambassador discount you chose to apply ("להחלת ההנחה") · 30 days · First · Both | linx-public-sales-agent-session · sessionStorage · LINX · A sales chat conversation, once you open it · Until the tab closes · First · LINX site | linx-ai-session-* · sessionStorage · LINX · The page's AI chat conversation, once you open it · Until the tab closes · First · Customer pages | linx_exchange_prompted · sessionStorage · LINX · The contact-exchange prompt was shown once · Until the tab closes · First · Customer pages | linx_access_code, linx_access_pages, linx_investor_access_code · localStorage · LINX · An access code you typed for a private page, and the pages it opened · Until changed · First · Both | linx_oauth_pending · localStorage · LINX · A social account connection in progress · Until the connection completes · First · Both | linx_lite_card_design_v1, linx_campaign_card_handoff_v1 · localStorage · LINX · A guest's card design, kept for the sign-up that follows · Until sign-up · First · Both | linx_home_redirect_seen, linx_referral_banner_dismissed · sessionStorage · LINX · The language redirect ran once; the referral banner was closed · Until the tab closes · First · Both | popup_dismissed_* · localStorage · LINX · A site notice you closed · Until changed · First · Both | evt_portal_token · localStorage, sessionStorage · LINX · Sign-in to an event portal · Until sign-out, or until the tab closes · First · LINX site | evt_agenda_stars:* · localStorage · LINX · Agenda items a guest starred · Until changed · First · LINX site | linx_event_*, linx_manager_event_id, linx_simulated_manager · sessionStorage · LINX · Event control room simulator state · Until the tab closes · First · LINX site | linx_offline_scans_* · localStorage · LINX · Event check-ins not yet synced · Until synced · First · LINX site | admin_sidebar_collapsed, org_sidebar_collapsed, linx-design-panel-width, linx.campaignWizard.draft.v1, linx_asset_meta_cache_*, linx_cal_status_*, linx_campaign_draft_*, linx_design_recent_colors, linx_followup_status_*, linx_last_agent_site, linx_last_agent_tab, linx_mkscripts_meta_v1, linx_palette_editor_panels, linx_push_opted_out_v1, linx_sheet_watchdog, linx_studio_ai_assets, linx_admin_copilot_history, linx_tags_view_mode, linx_wa_custom_links, tracking_dismissed_*, dismissed_tracking_*, LINX_PRO_USERS · localStorage · LINX · A signed-in user's dashboard state (drafts, display, closed notices). Never used for measurement · Until changed · First · Dashboard | linx.analytics.*, linx.nag.*, wizlab_seeded · sessionStorage · LINX · A signed-in user's dashboard state. Never used for measurement · Until the tab closes · First · Dashboard | linx.nag.* · localStorage · LINX · How many visits the signed-in user made, and when this device last put off the install or notifications prompt, so notices are spaced out. Never used for measurement · Until changed · First · Dashboard | linx_setup_collapsed_*, linx_setup_rec_dismissed_*, linx_designcard_dismissed_*, linx_upsell_dismissed_*, linx_campaign_bind_done_* · localStorage · LINX · The setup tips panel was collapsed, and suggestions or notices the signed-in user closed, per user (or per event guest) · Until changed · First · Dashboard | linx:email-signature:v1:* · localStorage · LINX · An email signature the signed-in user is still editing · Until it is sent or cleared · First · Dashboard | linx_design_history_v* · sessionStorage · LINX · Undo and redo in the page editor, while it is open · Until the tab closes · First · Dashboard

11.2 Statistics (consent only)

Name · Type · Provider · Purpose · Lifetime · Party · Where | linx_visitor_id:s:<page id> · localStorage · LINX · Recognises a returning visit to one customer page only · 13 months · First · Customer pages | linx_visitor_id · localStorage · LINX · The former visitor id, shared by every page. No longer written · Deleted on the first load · First · Both | linx_ft_v1 · localStorage · LINX · The campaign that first brought you to the LINX site · 13 months · First · LINX site | linx_utm_params · sessionStorage · LINX · The visit's campaign tags (ad click ids only with marketing consent) · Until the tab closes · First · LINX site | landing_session_id · sessionStorage · LINX · Groups the page views of one visit to the LINX site · Until the tab closes · First · LINX site | sentryReplaySession · sessionStorage · Sentry (Functional Software) · Usage recording to find faults · Until the tab closes · First · LINX site | _ga, _ga_* · Cookie · Google Analytics · LINX site statistics, no advertising features · 13 months · First · LINX site | _gid · Cookie · Google Analytics · Statistics, if Google Analytics writes it · 24 hours · First · LINX site | _gat* · Cookie · Google Analytics · Request throttling, if Google Analytics writes it · 1 minute · First · LINX site | _clck · Cookie · Microsoft Clarity · Usage recording with masked fields · 12 months · First · LINX site | _clsk · Cookie · Microsoft Clarity · Usage recording with masked fields · 1 day · First · LINX site | _cltk · sessionStorage · Microsoft Clarity · Usage recording with masked fields · Until the tab closes · First · LINX site | lxo_* (lxo_<8 characters>_ga, lxo_<8 characters>_ga_<id>) · Cookie · The page owner's Google Analytics · The page owner's statistics, on their page's path only, not shared with LINX · 13 months · First · Customer pages

11.3 Marketing (consent only)

Name · Type · Provider · Purpose · Lifetime · Party · Where | _fbp · Cookie · Meta · Ad measurement. Written by Meta's pixel, never by LINX · 90 days · First · Both | _fbc · Cookie · Meta · The Meta ad click that brought you · 90 days · First · Both | lastExternalReferrer, lastExternalReferrerTime · localStorage · Meta · The last outside site you came from, as Meta's pixel records it · Until deleted · First · Both | _gcl_* · Cookie · Google Ads · Google advertising cookies. No LINX tool writes them (Google's advertising features are always off); if any remain from before, withdrawing marketing deletes them · 90 days · First · Both | _ttp · Cookie · TikTok (the page owner's) · TikTok's visitor id for the page owner's advertising, on the page's domain · 13 months · First · Customer pages | _tt_enable_cookie · Cookie · TikTok (the page owner's) · Whether TikTok may use its cookies on this page · 13 months · First · Customer pages | ttcsid, ttcsid_<pixel id> · Cookie · TikTok (the page owner's) · The current visit, as TikTok counts it for the page owner's pixel · 13 months · First · Customer pages | ttclid · Cookie · TikTok (the page owner's) · The TikTok ad click that brought you, only after such a click · 1 day · First · Customer pages | tt_test_id · Cookie · TikTok (the page owner's) · TikTok's test-events tool, only from its test link · Until the browser closes · First · Customer pages | tt_sessionId · sessionStorage · TikTok (the page owner's) · TikTok's visit id for this tab · Until the tab closes · First · Customer pages | tt_pixel_session_index · sessionStorage · TikTok (the page owner's) · TikTok's page count in this visit · Until the tab closes · First · Customer pages | tt_appInfo · sessionStorage · TikTok (the page owner's) · Device platform and system version, as TikTok reads them · Until the tab closes · First · Customer pages | tt_adInfo · sessionStorage · TikTok (the page owner's) · The TikTok ad you came from, after an ad click · Until the tab closes · First · Customer pages | ttoclid · sessionStorage · TikTok (the page owner's) · TikTok's click id from the page link, after an ad click · Until the tab closes · First · Customer pages | tt_auto_zip_code · sessionStorage · TikTok (the page owner's) · A postcode TikTok infers, United States visitors only · Until the tab closes · First · Customer pages | tt_hold_events · sessionStorage · TikTok (the page owner's) · Events TikTok holds while consent is pending · Until the tab closes · First · Customer pages | _tt_event_builder · sessionStorage · TikTok (the page owner's) · TikTok's event builder tool, when the owner uses it · Until the tab closes · First · Customer pages | value_currency_rule · sessionStorage · TikTok (the page owner's) · TikTok's rules for reading prices off the page · Until the tab closes · First · Customer pages | parameter_inference_rule · sessionStorage · TikTok (the page owner's) · TikTok's rules for reading event details off the page · Until the tab closes · First · Customer pages | li_adsId · localStorage · LinkedIn (the page owner's) · LinkedIn's advertising id for this browser · Until deleted · First · Customer pages | li_adsId · Cookie · LinkedIn (the page owner's) · The same id, as a cookie, only when the browser blocks localStorage · 180 days · First · Customer pages | li_fat_id · Cookie · LinkedIn (the page owner's) · The LinkedIn ad click that brought you, only after such a click · 30 days · First · Customer pages | li_giant · Cookie · LinkedIn (the page owner's) · A LinkedIn ad click id, only after such a click · 7 days · First · Customer pages | li_hem · localStorage · LinkedIn (the page owner's) · A hashed email, only when a page hands LinkedIn one. LINX pages never do · Until deleted · First · Customer pages

11.4 Cookies on the vendor's domain (third party; LINX cannot delete them)

Name · Domain · Provider · Category · Purpose · Lifetime · Where | CLID · clarity.ms · Microsoft Clarity · Statistics · Clarity's id on Microsoft's domain · 12 months · LINX site | _ttp · tiktok.com · TikTok · Marketing · TikTok's visitor id, set on TikTok's domain when its script loads · 13 months · Customer pages | li_gc · linkedin.com · LinkedIn · Marketing · Your cookie choice on LinkedIn itself. The tag reads it; LINX pages never write it · 6 months · Customer pages | bcookie · linkedin.com · LinkedIn · Marketing · LinkedIn's browser id, set when the tag reports · 12 months · Customer pages | lidc · linkedin.com · LinkedIn · Marketing · Routing between LinkedIn's servers, set when the tag reports · 1 day · Customer pages | __cf_bm · linkedin.com · LinkedIn (its network provider) · Marketing · Bot check, set when the tag reports · 30 minutes · Customer pages | MUID · bing.com, clarity.ms · Microsoft Advertising · Marketing · Microsoft's advertising sync. LINX pages do not trigger it; listed because visiting clarity.ms or bing.com directly may set it · 13 months · Not on LINX pages | SRM_B · bing.com · Microsoft Advertising · Marketing · As MUID · 13 months · Not on LINX pages | Cookies that embedded content vendors (section 8) set after you press are not in the tables, because each vendor sets them under its own policy. The vendors in these tables may process data outside Israel, including in the United States. Details in the Privacy Policy.

12. Changes to this policy

We update this policy when we add a tool, remove one or change how it is used. When we add a vendor, a purpose or a category, the banner asks you again.

13. Contact

For questions about this policy and about privacy: Email: support@linxcard.me Phone: 053-3443330