Legal
Cookie and Tracking Technologies Policy
1. About This Policy
LARA, CARA and EdviseMe are education, learning, assessment, counselling, admissions, career-guidance and artificial-intelligence services operated by Graztech Private Limited and/or Junom Global Private Limited.
This Cookie and Tracking Technologies Policy explains how we use cookies, pixels, tags, software development kits, local storage, server-side tracking and similar technologies when you access or use our websites, applications and related Services.
In this Policy:
- “LARA” means our AI-powered learning, tutoring, revision, assessment, examination-readiness and academic-support services.
- “CARA” means our AI-powered education, admissions, course, university, career and counselling services.
- “EdviseMe” means our broader education, admissions, career, counselling and related platform services.
- “Services” means LARA, CARA, EdviseMe and all associated websites, applications, dashboards, chatbots, APIs, messaging services, assessments, reports and related features.
- “we”, “us” and “our” refer to Graztech Private Limited and/or Junom Global Private Limited as the legal operator of the Services.
- “you” and “your” refer to a person who visits, accesses or uses the Services.
- “Young User” means a User aged 13 to 17 or another User treated as a child or minor under applicable law.
- “Tracking Technologies” means cookies and the other technologies described in this Policy.
This Policy applies to:
- withlara.ai and its subdomains;
- withcara.ai and its subdomains;
- edviseme.com and its subdomains;
- LARA, CARA and EdviseMe web and mobile applications;
- landing pages and campaign pages;
- parent, teacher, counsellor, school and institutional dashboards;
- embedded content;
- integrations; and
- any other Service that links to this Policy.
This Policy should be read together with our Privacy Policy at:
https://edviseme.com/legal/privacy
2. What Are Cookies?
Cookies are small text files or pieces of information stored on your browser, computer, mobile device or other device when you visit a website or use an online service.
Cookies may allow a website or application to:
- recognise a browser or device;
- keep a User signed in;
- remember settings;
- maintain a session;
- secure an account;
- understand how the Service is used;
- measure performance;
- attribute registrations or purchases to a campaign;
- limit repeated advertising; and
- provide relevant content or advertising where permitted.
Cookies may contain:
- a randomly generated identifier;
- session information;
- consent choices;
- language or display preferences;
- campaign information;
- security information;
- authentication information; or
- other limited technical data.
Cookies do not necessarily identify a person by name. However, cookie identifiers and associated information may constitute Personal Data when they can be linked to an individual, account, browser or device.
3. Other Tracking Technologies We Use
In addition to cookies, we may use the following technologies.
3.1 Pixels and Web Beacons
Pixels and web beacons are small pieces of code or images that can record when:
- a page is opened;
- an advertisement is viewed;
- a link is selected;
- an email is opened;
- a registration is completed;
- a purchase is made; or
- another defined event occurs.
Pixels may be used for analytics, attribution, conversion measurement and advertising where permitted.
3.2 Tags and Tag-Management Systems
Tags are pieces of code used to activate analytics, advertising, performance and other technologies.
We may use Google Tag Manager or another tag-management system to manage tags across our websites and applications.
A tag-management system may not itself perform all tracking described in this Policy. It may control when other analytics, advertising or functional technologies are activated.
3.3 Software Development Kits
Mobile and web applications may use software development kits, commonly called SDKs, to provide:
- application functionality;
- authentication;
- analytics;
- crash reporting;
- notifications;
- security;
- attribution;
- advertising; and
- other technical services.
3.4 Local and Session Storage
Browsers and applications may store information using:
- local storage;
- session storage;
- indexed databases;
- cached files; or
- similar device-storage mechanisms.
These technologies may store more information than a traditional cookie and may remain until deleted by the application, browser or User.
3.5 Device and Advertising Identifiers
Depending on your device, settings and permissions, we may process:
- mobile advertising identifiers;
- application instance identifiers;
- installation identifiers;
- browser identifiers;
- push-notification tokens;
- device identifiers; and
- similar identifiers.
You may be able to reset or restrict certain identifiers through your device settings.
3.6 Server-Side Tracking and Conversion APIs
We may send selected events directly from our servers to analytics, attribution or advertising providers.
Server-side tracking may be used to:
- improve measurement reliability;
- record registrations;
- attribute purchases;
- measure campaign performance;
- prevent duplicate events;
- reduce fraud; and
- support advertising optimisation where permitted.
Server-side tracking may occur without placing an additional cookie on your device. It is nevertheless covered by this Policy and our Privacy Policy.
Where consent is legally required for the purpose concerned, we will apply the relevant consent choice to server-side events.
3.7 Email Tracking Technologies
Subject to applicable law, marketing and service emails may contain technologies that allow us to understand whether:
- an email was delivered;
- an email was opened;
- a link was selected;
- a transaction followed the communication; or
- the email was rejected or marked as spam.
You may disable some email tracking by changing your email settings, blocking remote images or opting out of optional marketing.
3.8 Analytics and Interaction Technologies
Subject to applicable law and consent requirements, we may use:
- event analytics;
- click analytics;
- navigation-path analysis;
- heatmaps;
- scroll measurement;
- form-interaction analytics;
- error monitoring;
- performance monitoring;
- A/B testing; and
- session-replay or similar technologies.
Where session-replay or comparable tools are used, we take reasonable steps to mask or exclude:
- passwords;
- OTPs;
- payment-card information;
- bank details;
- private AI messages;
- academic answers;
- uploaded document content;
- counselling information; and
- other fields designated as sensitive.
3.9 Security and Fraud-Detection Signals
We may use device, browser, network and behavioural signals to:
- detect suspicious logins;
- prevent automated abuse;
- identify bots;
- prevent account takeover;
- enforce usage limits;
- detect payment fraud;
- protect our systems; and
- investigate security incidents.
We do not use security technologies to deliberately circumvent a User’s valid cookie or advertising choices.
4. First-Party and Third-Party Technologies
4.1 First-Party Technologies
First-party technologies are set or controlled by us through a domain or application operated by us.
They may be used for:
- account sessions;
- authentication;
- security;
- consent records;
- preferences;
- product functionality;
- analytics;
- subscription management; and
- Service administration.
4.2 Third-Party Technologies
Third-party technologies are provided or controlled by another organisation.
Third parties may receive information including:
- IP address;
- browser information;
- device information;
- cookie or device identifiers;
- page or screen information;
- campaign information;
- selected interaction events;
- approximate location;
- transaction information; and
- other information described in this Policy.
Depending on the provider and purpose, a third party may act as:
- our service provider or processor;
- an independent controller or business;
- a joint controller; or
- another legally recognised role.
Third-party processing may also be governed by that provider’s terms, privacy policy and cookie policy.
5. Categories of Tracking Technologies
We classify Tracking Technologies according to their principal purpose.
The actual technologies used may vary by:
- domain;
- application;
- User type;
- country;
- age;
- consent choice;
- device;
- subscription;
- feature; and
- technical configuration.
Our cookie-preference centre, where displayed, provides the then-current list of available categories and technologies.
5.1 Strictly Necessary Technologies
Strictly necessary technologies are required for the Services to operate or to provide a feature expressly requested by you.
They may be used to:
- maintain a secure session;
- authenticate a User;
- keep a User signed in;
- prevent account takeover;
- protect forms;
- prevent cross-site request forgery;
- route network traffic;
- balance server load;
- maintain shopping carts or checkout sessions;
- process payments;
- remember consent choices;
- prevent fraud;
- enforce security controls;
- comply with legal obligations; and
- deliver content and core functionality.
These technologies may be used without optional consent where permitted by applicable law because the relevant Service cannot function properly without them.
Disabling strictly necessary technologies through browser settings may cause parts of the Services to stop working.
Typical duration: From the duration of the session to approximately 24 months, depending on the function.
5.2 Functional and Preference Technologies
Functional technologies allow the Services to remember choices and provide enhanced features.
They may be used to remember:
- language;
- country;
- curriculum;
- grade;
- display settings;
- accessibility settings;
- selected preferences;
- previously used features;
- notification choices;
- account configuration; and
- embedded-content settings.
If you reject functional technologies, some preferences may not be remembered and certain optional features may not work as expected.
Typical duration: From the duration of the session to approximately 24 months.
5.3 Analytics and Product-Improvement Technologies
Analytics technologies help us understand how the Services are used.
They may collect information about:
- pages and screens viewed;
- buttons and links selected;
- navigation paths;
- session duration;
- broad location;
- browser and device type;
- referral source;
- assessment starts and completions;
- registration funnels;
- feature use;
- error events;
- application performance;
- subscription funnels;
- campaign source; and
- other interaction events.
We may use this information to:
- measure traffic;
- understand User journeys;
- improve navigation;
- identify technical problems;
- improve content;
- understand feature adoption;
- conduct A/B testing;
- improve accessibility;
- allocate infrastructure;
- develop new Services; and
- evaluate product performance.
Where required by applicable law, we will obtain consent before using non-essential analytics technologies.
Typical duration: From the duration of the session to approximately 24 months.
5.4 Performance and Reliability Technologies
Performance technologies help us:
- measure loading speed;
- detect crashes;
- identify failed requests;
- monitor application availability;
- diagnose network problems;
- detect browser compatibility issues;
- improve response time; and
- maintain Service reliability.
Some performance technologies may be strictly necessary. Others may be treated as optional analytics depending on their configuration and applicable law.
Typical duration: From the duration of the session to approximately 24 months.
5.5 Advertising and Marketing Technologies
Subject to applicable law and your choices, advertising technologies may be used to:
- measure advertising campaigns;
- attribute visits and registrations;
- attribute purchases and subscriptions;
- understand which advertisements led to actions;
- limit repeated advertising;
- create advertising audiences where lawful;
- show relevant advertisements;
- conduct remarketing or retargeting where lawful;
- optimise advertising delivery;
- prevent advertising fraud;
- measure reach and frequency; and
- improve marketing effectiveness.
Advertising providers may associate information collected through our Services with information they already hold about a browser, device or account.
Where required by law, advertising and marketing technologies will not be activated until valid consent has been provided.
Typical duration: From the duration of the session to approximately 24 months.
5.6 Social-Media and Embedded-Content Technologies
We may embed or link to content from:
- Facebook;
- Instagram;
- YouTube;
- LinkedIn;
- WhatsApp;
- X;
- video-hosting providers;
- map providers; or
- other external platforms.
Those providers may place or access cookies when:
- embedded content loads;
- you interact with a social button;
- you play a video;
- you share content;
- you are signed in to the third-party service; or
- the provider otherwise receives information through the integration.
Third-party technologies are governed by the relevant provider’s privacy and cookie practices.
Typical duration: Determined by the relevant third party and may range from the session duration to approximately 24 months or longer.
5.7 Consent and Privacy-Preference Technologies
We use technologies to:
- record whether you accepted or rejected optional categories;
- remember the date and version of your choice;
- communicate consent status to tags;
- apply regional settings;
- prevent the consent banner from appearing on every page; and
- demonstrate compliance with applicable law.
Consent technologies are generally treated as strictly necessary.
Typical duration: Usually between 6 and 24 months, after which we may request that you confirm your choices again.
6. Technologies and Providers We May Use
Depending on the Service, country and configuration, we may use technologies provided by the organisations listed below.
The inclusion of a provider in this Policy does not mean every provider is active on every page, application or User account.
6.1 Google Technologies
We may use Google services including:
- Google Tag Manager;
- Google Analytics;
- Google Ads conversion tracking;
- Google advertising technologies;
- Firebase;
- Google Cloud services;
- Google reCAPTCHA;
- Google Consent Mode; and
- similar Google technologies.
These services may process:
- IP address;
- browser and device information;
- page or screen information;
- referral and campaign information;
- cookie or application identifiers;
- approximate location;
- selected interaction events;
- registration events;
- subscription events;
- purchase events;
- application-performance information; and
- consent status.
Google Tag Manager may be used to control when other tags are activated.
Google Consent Mode may be used to communicate your analytics and advertising choices to Google technologies so that tags can adjust their behaviour.
6.2 Meta Technologies
We may use Meta services including:
- Meta Pixel;
- Meta Conversions API;
- Meta advertising attribution;
- Meta custom-audience tools where lawful;
- Facebook and Instagram integrations; and
- similar Meta business technologies.
These technologies may process:
- IP address;
- browser and device information;
- cookie identifiers;
- page information;
- referral and campaign information;
- selected interaction events;
- registration events;
- checkout events;
- purchase or subscription events; and
- other permitted conversion information.
Where consent is legally required, we will configure Meta technologies so that relevant information is not sent before the required consent is received.
We do not intentionally send Meta:
- private AI conversations;
- uploaded document contents;
- examination answers;
- detailed academic marks;
- counselling notes;
- psychometric answers;
- health information; or
- other sensitive educational information as advertising-event parameters.
6.3 Product Analytics and Experience Providers
We may use product-analytics, user-experience and performance providers, including services such as:
- Firebase Analytics;
- Mixpanel;
- PostHog;
- Segment;
- Microsoft Clarity;
- Hotjar;
- application-performance monitoring providers;
- crash-reporting providers; and
- similar services.
The providers actually active within a Service will depend on our current technical configuration and the choices available through our cookie-preference centre.
6.4 Cloud, Security and Infrastructure Providers
We may use cloud, content-delivery, authentication, security and infrastructure providers, including:
- Amazon Web Services;
- content-delivery networks;
- load-balancing services;
- identity providers;
- fraud-prevention services;
- security-monitoring services;
- CAPTCHA or bot-detection providers; and
- similar providers.
Some of these technologies may be strictly necessary for security and Service delivery.
6.5 Payment Providers
Payment processors and app stores may use cookies or similar technologies to:
- maintain checkout sessions;
- authenticate payments;
- detect fraud;
- remember payment choices;
- process subscriptions; and
- comply with financial regulation.
Their independent use of technologies may be governed by their own privacy and cookie notices.
6.6 Communications and Messaging Providers
Email, SMS, WhatsApp, push-notification and customer-support providers may use technologies to:
- deliver messages;
- verify delivery;
- measure engagement;
- detect failures;
- protect against fraud; and
- administer support.
7. Current Cookie Inventory
The precise names, providers, purposes and expiry periods of cookies may change as:
- providers update their technologies;
- we add or remove features;
- legal requirements change;
- security requirements change; or
- our technical configuration changes.
Where a cookie-preference centre is displayed, it will provide the most current available inventory of:
- cookie or technology name;
- provider;
- purpose;
- category;
- first-party or third-party status; and
- duration or expiry period.
The cookie-preference centre forms part of this Policy.
Where there is a difference between a general duration stated in this Policy and a specific duration shown in the live cookie inventory, the live inventory will govern the specific technology.
8. Why We Use Tracking Technologies
We may use Tracking Technologies to:
- provide and secure accounts;
- remember settings;
- maintain sessions;
- protect payment processes;
- detect fraud;
- prevent bots;
- provide requested functionality;
- understand how the Services are used;
- measure application performance;
- identify errors;
- improve user experience;
- develop new features;
- personalise educational content;
- provide age-appropriate experiences;
- measure marketing campaigns;
- attribute conversions;
- communicate with Users;
- enforce our Terms;
- comply with legal obligations; and
- protect our rights and systems.
9. Legal Basis for Using Tracking Technologies
The legal basis depends on:
- the technology;
- its purpose;
- your country;
- your age;
- your consent status;
- the Service concerned; and
- applicable law.
9.1 Strictly Necessary Technologies
We may use strictly necessary technologies where they are required to:
- provide a Service requested by you;
- maintain security;
- authenticate an account;
- remember privacy choices;
- process a transaction;
- prevent fraud; or
- comply with law.
Where permitted, these technologies may be used without optional consent.
9.2 Consent
We may rely on consent for:
- non-essential analytics;
- advertising cookies;
- advertising pixels;
- remarketing technologies;
- optional personalisation;
- social-media technologies;
- session replay;
- cross-site tracking; and
- other technologies where consent is required.
You may withdraw consent at any time through the available cookie-preference controls.
9.3 Other Lawful Grounds
In jurisdictions where prior cookie consent is not legally required for a particular activity, we may rely on another lawful ground, including:
- performance of a contract;
- legitimate interests;
- compliance with law;
- security;
- fraud prevention; or
- another ground recognised by applicable law.
Nothing in this section permits us to avoid consent where consent is legally required.
10. Your Consent Choices
Depending on your location and the applicable Service, you may be offered the following choices:
- Accept All
- Reject Non-Essential
- Manage Choices
- category-specific controls; or
- another legally appropriate consent mechanism.
Rejecting non-essential technologies does not disable strictly necessary technologies.
10.1 No Pre-Ticked Optional Consent
Where affirmative consent is required, optional categories will not be treated as accepted merely because:
- you continued browsing;
- you scrolled;
- you used the Service;
- a box was pre-selected;
- you accepted the Terms of Service; or
- you did not make a choice.
10.2 Changing Your Choices
You may change your choices at any time through the cookie settings or privacy controls made available on the relevant website or application.
A change generally applies to future processing.
Changing a choice does not automatically erase information lawfully collected before the change.
10.3 Device, Browser and Domain-Specific Choices
Consent and cookie choices may be specific to:
- the browser;
- device;
- application;
- domain;
- account;
- country; or
- cookie profile used when the choice was made.
You may need to make a new choice where you:
- use a different device;
- use another browser;
- clear cookies;
- use private-browsing mode;
- access another domain;
- reinstall an application; or
- reset device identifiers.
Where technically and legally appropriate, we may associate privacy choices with an account so that they can apply across more than one device or Service.
10.4 Withdrawal of Consent
You may withdraw consent as easily as reasonably practicable through the available privacy controls.
After withdrawal:
- relevant optional tags should stop collecting new information for the withdrawn purpose;
- some existing cookies may need to be deleted through your browser or device;
- previously collected information may be retained where legally permitted;
- aggregated reporting may remain; and
- strictly necessary technologies will continue to operate.
11. Browser and Device Controls
Most browsers allow you to:
- view cookies;
- block cookies;
- delete cookies;
- reject third-party cookies;
- clear website data;
- restrict local storage; and
- control permissions.
Mobile devices may allow you to:
- reset advertising identifiers;
- limit advertising personalisation;
- restrict application tracking;
- control location access;
- manage notification permissions; and
- delete application data.
Blocking all cookies may prevent the Services from:
- keeping you signed in;
- remembering settings;
- processing checkout;
- remembering consent choices;
- loading embedded features; or
- functioning correctly.
12. Global Privacy Control and Similar Signals
Where required by applicable law, we will treat a recognised opt-out preference signal, such as Global Privacy Control, as a request to opt out of applicable:
- sale;
- sharing;
- targeted advertising; or
- cross-context behavioural advertising for the relevant browser or device.
An opt-out signal may not automatically apply to:
- another browser;
- another device;
- a native application;
- another User profile; or
- processing that is exempt from the applicable opt-out right.
13. Do Not Track Signals
Some browsers transmit a “Do Not Track” signal.
There is no universally accepted technical or legal standard governing all Do Not Track signals.
We may not respond to a Do Not Track signal unless applicable law requires us to recognise that specific signal.
We will honour recognised opt-out preference signals where required by law.
14. Young Users and Age-Appropriate Advertising
We may use Tracking Technologies to show or measure age-appropriate advertising concerning LARA, CARA and EdviseMe for Users aged 13 to 17 where permitted by:
- applicable law;
- the relevant advertising platform;
- the User’s consent status; and
- any required parental authorisation.
Depending on the applicable rules, advertising may be selected using limited information such as:
- age range;
- broad geographic area;
- language;
- context;
- general page subject; and
- other criteria expressly permitted by law and platform rules.
We do not use a known Young User’s:
- private AI conversations;
- examination answers;
- uploaded documents;
- detailed academic marks;
- target marks;
- identified learning difficulties;
- counselling information;
- psychometric answers;
- scholarship information;
- health information; or
- other sensitive educational information to select advertisements.
Where prohibited by applicable law, we do not use Tracking Technologies to:
- behaviourally monitor a Young User for advertising;
- create an advertising profile from a Young User’s activity;
- use learning activity for personalised advertising;
- place a known Young User into a remarketing or retargeting audience;
- place a known Young User into a custom or lookalike advertising audience;
- share a known Young User’s Personal Data for targeted advertising; or
- direct targeted advertising to a Young User.
We may use limited and proportionate technologies for lawful:
- security;
- fraud prevention;
- Service operation;
- consent management;
- aggregate campaign measurement;
- attribution;
- reach measurement;
- conversion reporting; and
- understanding whether an advertisement led to a visit, registration or purchase.
Where local law prohibits tracking, behavioural monitoring or targeted advertising concerning children, we will restrict or disable the relevant technologies.
15. Educational Personalisation Is Different From Advertising Personalisation
We may use information about a Young User’s activity within the Services to:
- remember learning progress;
- recommend revision;
- adapt assessments;
- generate reports;
- identify mistakes;
- provide counselling;
- maintain security;
- improve the educational Service; and
- support authorised parents, teachers or institutions.
This educational personalisation is distinct from using the same information to select advertising.
We do not use sensitive educational activity to select advertisements for a known Young User.
16. Advertising and Campaign Measurement
Subject to applicable law and User choices, we may measure:
- advertisement impressions;
- advertisement selections;
- landing-page visits;
- registrations;
- assessment starts;
- assessment completions;
- checkout starts;
- purchases;
- subscription activations;
- campaign source;
- referral source;
- aggregate return on advertising spend;
- reach;
- frequency; and
- other conversion events.
Campaign information may be used to:
- understand which campaigns are effective;
- allocate marketing budgets;
- reduce repeated advertising;
- detect fraudulent traffic;
- improve campaign content;
- measure product demand; and
- optimise permitted advertising.
We may use browser-side and server-side technologies together to improve measurement and avoid duplicate event reporting.
17. Advertising Audiences and Retargeting
For eligible adult Users and visitors, and subject to applicable law and consent, we may:
- create advertising audiences;
- use custom audiences;
- conduct remarketing or retargeting;
- measure audience overlap;
- create similar or lookalike audiences;
- exclude existing Users from acquisition campaigns; and
- optimise advertisements for likely conversions.
Where required, we will provide an opt-out from sale, sharing or targeted advertising.
Known Young Users will be subject to the restrictions described in Section 14.
18. Enhanced Matching and Hashed Identifiers
For eligible adult Users, and where permitted by law, we may use enhanced matching, advanced matching or similar technology.
This may involve converting selected contact information, such as an email address or telephone number, into a cryptographic hash before it is transmitted to an advertising provider.
Hashing does not necessarily make information anonymous. Hashed identifiers may still be Personal Data.
We will use such technology only where:
- the information was lawfully collected;
- the use is permitted by law;
- the required notice has been provided;
- any required consent has been obtained; and
- applicable opt-out choices are respected.
We do not intentionally use known Young Users’ contact information for enhanced or advanced advertising matching where prohibited by applicable law or platform rules.
19. Sale and Sharing Under Certain Privacy Laws
We do not sell Personal Data in exchange for money.
Some privacy laws define “sale” or “sharing” broadly enough to include the disclosure of cookie, device or advertising information to advertising providers.
Where our use of advertising technologies is treated as sale, sharing, targeted advertising or cross-context behavioural advertising, eligible Users may opt out through:
- the cookie-preference centre;
- a Your Privacy Choices link;
- an applicable browser preference signal; or
- support@edviseme.com.
We do not knowingly sell Personal Data belonging to a known Young User for money.
We do not knowingly share a known Young User’s Personal Data for targeted advertising where prohibited by law.
20. Data Collected Through Tracking Technologies
Tracking Technologies may collect or generate:
- IP address;
- browser type;
- browser version;
- device type;
- operating system;
- screen size;
- language;
- time zone;
- cookie identifiers;
- device identifiers;
- application identifiers;
- advertising identifiers;
- approximate location;
- network information;
- page URL;
- page title;
- referral URL;
- campaign parameters;
- event name;
- event date and time;
- session duration;
- navigation paths;
- feature usage;
- error information;
- performance information;
- registration status;
- subscription status;
- transaction amount;
- currency;
- product or plan selected;
- consent status; and
- other permitted event parameters.
We do not intentionally place private chat text, document contents, passwords, OTPs, complete payment credentials or sensitive educational answers into advertising-event parameters.
21. How Long Tracking Information Is Retained
Retention varies by:
- category;
- provider;
- purpose;
- User choice;
- account status;
- legal requirements;
- browser settings; and
- technical configuration.
Cookies may be:
21.1 Session Cookies
Session cookies generally expire when you close the browser or end the application session.
21.2 Persistent Cookies
Persistent cookies remain until:
- their stated expiry date;
- deletion by the User;
- deletion by the provider;
- withdrawal of consent where technically applicable; or
- replacement through an updated cookie.
Persistent cookies used through our Services generally last from several days to approximately 24 months, although some third-party technologies may use different periods.
21.3 Server-Side and Analytics Records
Information generated through Tracking Technologies may be retained separately from the cookie itself.
Such records are retained according to:
- our Privacy Policy;
- the purpose of processing;
- User rights;
- provider settings;
- contractual requirements; and
- applicable law.
Deleting a cookie does not necessarily delete analytics or transaction records previously created from that cookie.
22. International Transfers
Tracking providers may process information in:
- India;
- the United States;
- the United Kingdom;
- the European Economic Area; and
- other countries.
Information may therefore be transferred to or accessed from countries with privacy laws different from those in your country.
Where required, we use or require appropriate transfer mechanisms, which may include:
- adequacy decisions;
- standard contractual clauses;
- approved UK transfer mechanisms;
- data-processing agreements;
- technical and organisational safeguards;
- transfer assessments; and
- other lawful mechanisms.
Further information is available in our Privacy Policy.
23. Third-Party Responsibility
Some third-party providers independently determine how they use information received through their technologies.
We do not control:
- the provider’s independent cookies;
- the provider’s retention periods;
- information already held by the provider;
- the provider’s account-level settings;
- the provider’s independent advertising systems; or
- the provider’s independent privacy practices.
You should review the privacy and cookie information supplied by relevant third parties.
Your choices on our Services may not automatically change preferences held directly within Google, Meta, an app store, a browser, a social platform or another third-party account.
24. Blocking and Deleting Technologies
You may block or delete cookies through:
- our cookie-preference centre;
- browser settings;
- device settings;
- application permissions;
- advertising-provider settings;
- operating-system privacy controls; or
- third-party opt-out tools.
Deleting cookies may:
- sign you out;
- reset settings;
- remove stored preferences;
- cause the consent banner to reappear;
- affect attribution;
- disable optional features; or
- require you to repeat previous selections.
25. Changes to This Policy
We may update this Policy to reflect:
- changes to the Services;
- changes in technology;
- changes in providers;
- new Tracking Technologies;
- changes in advertising practices;
- changes in legal requirements;
- security developments; or
- clarification of existing practices.
The updated Policy will display a revised “Last Updated” date.
Where required by law, we may:
- notify you of a material change;
- display the consent banner again;
- request renewed consent; or
- reset a particular consent choice.
Previous versions may be retained for audit, legal and compliance purposes.
26. Your Privacy Rights
Depending on your location, you may have rights to:
- receive information about Tracking Technologies;
- withdraw consent;
- object to processing;
- opt out of targeted advertising;
- opt out of sale or sharing as legally defined;
- request deletion;
- request access;
- correct associated account information;
- restrict certain processing;
- appeal a privacy decision; and
- complain to a regulatory authority.
Further information about privacy rights and how to exercise them is available in our Privacy Policy at:
https://edviseme.com/legal/privacy
27. Contact Us
Questions or requests concerning cookies and Tracking Technologies may be sent to:
LARA, CARA and EdviseMe Operated by Graztech Private Limited and/or Junom Global Private Limited Pentagon, Amrutha Valley Hyderabad – 500034 Telangana, India Email: support@edviseme.com Please use one of the following subject lines where appropriate:
- Cookie Question
- Cookie Consent Request
- Advertising Opt-Out
- Privacy Request
- Child Privacy Request
28. Grievance Officer
Privacy grievances concerning our use of Tracking Technologies may be submitted to:
Name: Rachael Kharshong Designation: Grievance Officer Address: Pentagon, Amrutha Valley, Hyderabad – 500034, Telangana, India Email: support@edviseme.com Please use the subject line:
Cookie and Tracking Grievance
29. Related Policies
This Policy should be read together with:
- the Privacy Policy at https://edviseme.com/legal/privacy;
- the Terms of Service at https://edviseme.com/legal/terms;
- the Acceptable Use Policy at https://edviseme.com/legal/acceptable-use;
- the Subscription, Cancellation and Refund Policy at https://edviseme.com/legal/subscriptions; and
- the Children and Young Users Privacy Notice at https://edviseme.com/legal/children.
Where there is a conflict concerning Tracking Technologies:
- applicable law will prevail;
- a specific notice shown at the point of collection will govern the processing it describes;
- the Children and Young Users Privacy Notice will govern child-specific processing;
- the live cookie-preference centre will govern the then-current technology inventory and consent choices; and
- this Policy will otherwise govern our general use of Tracking Technologies.