This policy explains what NearSync keeps on your device when you use this website, and what it does not. It supplements the Privacy Policy.
Cookies only if you say yes
Opening a page on nearsync.ai sets no cookies. A small banner asks whether we may use cookies for two purposes, analytics and advertising, and each is a separate choice. Under Choose it also shows what the site keeps on your device without cookies, as Necessary and Functional (see below). If you decline, or do not answer, none are set and no Google or Meta script is loaded. Nothing here follows you to another site unless you say yes to advertising.
The cookies, if you agree
Analytics. If you accept analytics, we load Google Tag Manager, which runs Google Analytics and Microsoft Clarity. They set:
| Cookie | Set by | What it is for | Kept for |
|---|---|---|---|
_ga |
Google Analytics | Tells one visitor’s visits apart from another’s | 2 years |
_ga_<property ID> |
Google Analytics | Keeps track of the current visit | 2 years |
_clck |
Microsoft Clarity | Tells one visitor’s visits apart from another’s | 1 year |
_clsk |
Microsoft Clarity | Joins the pages of one visit into one recording | 1 day |
CLID |
Microsoft Clarity (on its own domain) | Tells visitors apart across sites that use Clarity | 1 year |
MUID, SRM_B, MR, ANONCHK, SM |
Microsoft (bing.com, and Clarity on its own domain) | Microsoft’s identifiers for a browser, used by Clarity | up to 13 months (MR 7 days, ANONCHK and SM the same day) |
Google receives the pages you open and how you move between them, with your consent. Google explains how it uses data from sites that use its services.
Clarity records how you move through a visit: scrolling, clicks and where the pointer goes, so we can see where pages confuse people. All text on the page and everything you type is hidden in the recording before it leaves your browser, and the chat and the contact form are hidden entirely. Microsoft explains how Clarity handles data.
Advertising. If you accept advertising, Google Tag Manager also loads Google Ads’ conversion linker, for our ads on Google, the Meta Pixel, for our ads on Facebook and Instagram, LinkedIn’s Insight Tag, for our ads on LinkedIn, Dealfront (formerly Leadfeeder), which tells us which companies visit, and Saava’s visitor pixel (delivr.ai), which tells us who visits and what they do here. They set:
| Cookie | Set by | What it is for | Kept for |
|---|---|---|---|
_gcl_au |
Google Ads | Tells one visitor’s visits apart from another’s, so Google can tell us which ads brought them | 3 months |
_gcl_aw |
Google Ads | Records the ad you clicked, only when you arrive from one of our Google ads | 3 months |
GCL_AW_P |
Google (google.com) | Google’s copy of the ad you clicked, only when you arrive from one of our Google ads | 3 months |
_fbp |
Meta Pixel | Tells one visitor’s visits apart from another’s, so Meta can show our ads to people who visited and tell us which ads brought them | 3 months |
_fbc |
Meta Pixel | Records the ad you clicked, only when you arrive from one of our ads | 3 months |
fr |
Meta (facebook.com) | Meta’s identifier for a browser, so it can show our ads to people who visited | 3 months |
ln_or |
LinkedIn Insight Tag | Notes that the tag has already run today, so it is not sent twice | 1 day |
li_sugr, bcookie, bscookie, lidc, UserMatchHistory, AnalyticsSyncHistory, li_fat_id, __cf_bm |
LinkedIn (linkedin.com) | Recognise your browser, so LinkedIn can show our ads to people who visited and tell us which ads brought them; __cf_bm tells people from bots |
up to 1 year (lidc 1 day, __cf_bm 30 minutes) |
_lfa |
Dealfront | Tells one visitor’s visits apart from another’s, so the pages of a visit are counted once | 2 years |
Google receives the ad you came from and whether you then sent us a form or clicked to sign up, with your consent. If you are signed in to a Google account that allows personalised ads, Google can also link your visit to that account (Google signals), which gives us totals such as age range and interests, never who you are. It explains how it uses data from sites that use its services. Meta receives the pages you open on nearsync.ai and the ad you came from, with your consent. If you are signed in to Facebook or Instagram in the same browser, Meta can link this to your account. Meta explains how it uses data from its business tools. LinkedIn receives the same, and if you are signed in to LinkedIn it can link this to your account; it explains how in its cookie policy. LinkedIn shows us only totals, such as the industries and job titles of visitors, never who you are.
Dealfront looks up which company your internet address belongs to and shows us that company’s name and the pages its visitors opened. If you also send us a form (contact, demo booking, programme application, cost report, chat or newsletter), Dealfront receives your email address, and your first and last name when you gave them, so the visit is linked to you and not only to your company. Dealfront and Saava (below) are the only companies other than NearSync that receive your email address itself, and only if you accepted advertising. Dealfront explains how it handles data.
Saava’s pixel sets no cookies of its own. It sends Saava (through delivr.ai) the pages you open, what you click and the words on it, how far you scroll, text you copy, the videos you play, and, when you send a form, everything you type into a form except passwords and card numbers. Saava uses this to work out who you are, including from data it holds about people, and tells us. This happens only if you accepted advertising. Our website blocks the pixel from loading anything from other companies’ sites, so no other company is told about your visit through it.
When we add another tag, we will list its cookies here and ask everyone again.
The campaign you arrived from. If you accept analytics or advertising, ns-src in session storage keeps the campaign tags and ad click codes in the link you arrived on (for example utm_source=linkedin, or the gclid Google adds to its ads), the page you landed on, and the site that sent you. If you then send us a form, they go with it, so we know which campaign brought you; they are never sent to an ad platform. Your browser deletes ns-src when you close the tab, and we delete it if you take back your yes. Without that yes nothing is kept, and a form sends only what is in the address of the page you send it from.
If you then sign up. With analytics or advertising accepted, a Sign up link on this site also carries your answer to the banner, the campaign details above, and the identifiers Google Analytics (_ga) and Meta (_fbp, _fbc) set here. When your trial starts, and again when you first pay, NearSync tells Google Analytics (only if you accepted analytics; it passes this on to Google Ads only if you also accepted advertising) and Meta and LinkedIn (only if you accepted advertising) that it happened. Meta and LinkedIn also receive a scrambled (hashed) copy of your email address, so they can match the sign-up to the ad you saw; they never receive the address itself. If you declined, a Sign up link carries nothing and nobody is told.
How we count visits
We count visits with Vercel Web Analytics, run by our hosting provider. It sets no cookies and stores nothing on your device. For each page you open it records the page, the site that sent you, your country, your device and browser type, and any campaign tag in the link you followed (for example utm_source=linkedin). We see these as counts, not as a profile of you, and we use them to learn which pages people find and where they come from.
We also measure how quickly our pages load and respond, with Vercel Speed Insights, run by the same provider. It sets no cookies and stores nothing on your device either. It records the page, how long it took to show and to respond, and your device type and country, as timings rather than anything about you.
What we store on your device
Cookies are not the only way a site can keep something on your device, so here is the full list of what this one keeps. Cookie choices at the bottom of any page shows it in two groups: Necessary, which is always on, and Functional, which you can switch off.
Necessary
These make something you asked for work, so they have no switch. Neither tracks you.
Your cookie choice. When you answer the banner, ns-consent in local storage keeps your answer and the date, so the banner does not ask on every page. It is never sent to us. After a year, or when we add a new kind of tag, the banner asks again.
The help chat’s session. The first time you open the chat in the corner, the site saves ns-wc-token in local storage. It is a random code that holds no personal details, and it lets the chat recognise you if you come back to the same conversation. It is sent to our chat service as the conversation’s reference, and your browser keeps it until you clear your site data.
Functional
These remember what you asked the site to remember. They stay on your device and are never sent to us. Functional is on unless you switch it off in Cookie choices; switching it off deletes all of them at once, and the site then stops saving them.
Your theme. Clicking the light and dark switch saves ns-theme in local storage, so the site opens the way you left it. Nothing is saved until you click it.
A flag that stops the logo animating twice. The first page you open plays a short animation on the NearSync mark. ns-mm-folded in session storage stops it replaying on every page after that, and your browser deletes it when you close the tab. With Functional off, the mark appears without the animation.
Your startup programme application, as you type it. The NearSync for Startups and NearSync Emirati Founders applications save your answers in local storage as nearsync-apply-<programme>-v1 while you fill them in, so leaving the page does not lose them. They include what you typed, such as your name, email and company. They are deleted when you send the application, and never sent to us before that.
Your cost comparison. The calculator on the compare page saves the tools and numbers you enter as nearsync-compare-v1 in local storage, so they are there when you come back. They are kept for 30 days and deleted when you press “Start over”. Only pressing Send in the calculator sends anything to us.
Your company details, if you ask. The quotation, invoice, HR document, minutes and email signature generators can remember your company name, address, TRN, phone, email, bank details, logo, and the name and title of the person who signs your letters. One entry, ns-sales-company in local storage, is shared by all of them. It is saved only when you tick “Remember my company details on this device”, and deleted when you untick that box or press “Forget my details”.
Your choice on the help page. If you pick a department or seniority under “Common for your role” on the help page, ns-help-role in local storage keeps that pick so the page opens with it next time. Clicking the selected choice again, or pressing the clear button, deletes it.
Which customer quotes you have seen. As you scroll, a short quote from a customer can rise in, at most once every five minutes. ns-proof in local storage keeps when the last one showed, which ones you have seen, and whether you closed them (closing stops them for a day). With Functional off, the quotes do not appear.
With ns-src under Analytics above, these are every key this site writes to local or session storage, and none of them is used to track you.
Changing your choice
Use Cookie choices at the bottom of any page to see your answer and change it. If you take back a yes, we delete the Google Analytics and Meta Pixel cookies on this site and stop loading the scripts. Declining is as easy as accepting: both buttons sit side by side and do the same amount of work.
Necessary storage and our cookieless visit counting do not wait for your answer. Functional storage is on from the start, because each item is something you asked for and none leaves your device; you can switch it off in Cookie choices at any time.
The help chat
The chat button in the corner is served by our own backend. It sets no cookies. Its only item on your device is the session code described above. What you type into it is covered by the Privacy Policy.
Signing in to the product
Signing in at app.nearsync.tech stores a session token on your device so you stay signed in as you move between pages. This is strictly necessary, because without it there is no way to remain signed in. It is not used for tracking or advertising.
Your browser controls
Your browser can block or clear site storage at any time. Since nothing here is needed for the pages to work, clearing it costs you your cookie choice, the chat’s link to an earlier conversation, and everything under Functional: your theme, unsent application and calculator answers, any company details you asked the tools to remember and your help-page choice.
Changes
We will update this page if what we store changes, and date it accordingly.
Contact
Questions: privacy@nearsync.ai.
Questions about this document? Write to legal@nearsync.ai. Company details are on the Imprint.