This policy explains the cookies and similar technologies used on realatic.com. Realatic is run by Technix Infotech LLP, Noida, Uttar Pradesh, India. Our Privacy Policy explains everything else we do with personal data.

1. What cookies are

A cookie is a small text file a website saves in your browser. "Local storage" and "session storage" work in a similar way. Some are needed for the site to work. Others help us count visits or measure our ads.

2. The three kinds we use

  • Necessary — keep the site and our forms working.
  • Analytics — Google Analytics counts visits and shows which pages help.
  • Marketing — the Meta Pixel, Google Ads, Google Tag Manager and our own ad-attribution cookie measure our ads, show our ads to past visitors, and remember which ad brought you here.

All three start when you open a page on our website. We do not show a cookie banner.

3. How to turn them off

  • Your browser. Block or delete cookies, or use private browsing. Blocking third-party cookies and trackers stops most Analytics and Marketing tools. Deleting cookies removes the ones already set.
  • Do Not Track. If your browser sends a Do-Not-Track signal, our ad-attribution cookie rt_ad is never set.
  • Meta. Manage how Meta uses data for ads in your Meta ad preferences.
  • Google. Manage Google ads in My Ad Center, or install the Google Analytics opt-out add-on.

Blocking Necessary cookies or storage may stop parts of the site, such as our forms, from working.

4. The cookies we use

Below is every cookie and storage item we found on realatic.com. Meta and Google may also read or set cookies on their own websites (such as facebook.com, google.com or doubleclick.net), for example if you are logged in to them. Their policies cover those.

Necessary

Name Provider Purpose How long
realatic_agent, realatic_agent_details, realatic_commission_invoice_agent
Local storage
Realatic Remember the details you typed into our free tools, so you don't have to type them again. They stay on your device. Until you clear them

Analytics

Name Provider Purpose How long
_ga
Cookie
Google Analytics A random ID that lets Google Analytics tell visits apart. Up to 2 years (Chrome caps it at 400 days)
_ga_6K9ZNQSCKE
Cookie
Google Analytics Keeps track of your current visit (session) for Google Analytics. Up to 2 years (Chrome caps it at 400 days)

Marketing

Name Provider Purpose How long
rt_ad
Cookie
Realatic Remembers which ad or website first brought you to us (campaign tags, Facebook or Google click id, landing page, referring site), so that if you sign up on app.realatic.com we know which ad worked. No name, email or phone. 90 days
rt_ad
Session storage
Realatic Keeps the Facebook or Google click id for this visit and sends it with an enquiry you submit. Until you close the tab
rl_touch
Session storage
Realatic Remembers the page you landed on, the site that sent you and any campaign tags for this visit, so if you send us an enquiry our team knows where it came from. It includes the Google Ads click id if the link had one. Sent to us only with a form you submit. Until you close the tab
_fbp
Cookie
Meta Identifies your browser to Meta so it can measure and improve our Facebook and Instagram ads. 90 days
_fbc
Cookie
Meta Stores the Facebook click id when you arrive from one of our Facebook or Instagram ads. 90 days
lastExternalReferrer, lastExternalReferrerTime, multiFbc
Local storage
Meta Remember the last outside site that sent you and recent Facebook click ids, for ad measurement. Until you clear them
_gcl_au
Cookie
Google Ads Links your visit to our Google Ads so we can count sign-ups and enquiries that came from an ad. 90 days
_gcl_aw (and other _gcl_* cookies)
Cookie
Google Ads Stores the Google Ads click id (gclid) when you arrive from one of our Google ads. 90 days
_gcl_ls
Local storage
Google Ads Keeps Google Ads conversion-linking data. Until you clear it

5. Our app (app.realatic.com)

Sign-up and the Realatic app run on app.realatic.com. The app uses its own Necessary cookies, for example sb-…-auth-token (keeps you signed in; it can be split into several numbered parts) and rl_device (a random id for your browser, used to spot one login being shared across many computers; up to 400 days). The app can read the rt_ad cookie, because it is set for the whole realatic.com domain.

On app.realatic.com, the Meta Pixel, Google Analytics and Google Ads run only on the home and sign-up pages, not inside the signed-in app, and set the same kinds of cookies as this site. Inside the signed-in app, Vercel Web Analytics counts page views without cookies, and PostHog product analytics keeps an id in your browser's local storage when your organisation allows it. See section 3.6 of our Privacy Policy.

6. Changes and contact

If we add or change a cookie, we will update this page. Questions? Write to our Grievance Officer at support@realatic.com.