Cookie Policy

Version: 1.2 Last updated: 16 September 2026 Effective date: 16 September 2026

1. Introduction

This Cookie Policy explains how CRUD INFOSYSTEMS PRIVATE LIMITED, operating under the brand name The cRUD Company (“The cRUD Company”, “cRUD”, “Company”, “we”, “us” or “our”), uses cookies and similar technologies in connection with:

www.thecrudcompany.com and thecrudcompany.com;
cRUD Webinar;
cRUD applications;
account and authentication interfaces;
webinar pages;
registration interfaces;
replay and on-demand interfaces;
other websites or digital services that link to this Cookie Policy.

This Cookie Policy should be read together with our:

Privacy Policy;
Terms of Service;
Communications & Consent Policy;
and any contextual cookie or privacy notices presented within the Services.

Our Privacy Policy is available at:

https://www.thecrudcompany.com/trust-center/privacy-policy

2. What are cookies?

Cookies are small pieces of information stored on or associated with a browser or device when a user visits a website or uses an online service.

Cookies can perform functions such as:

keeping a user signed in;
maintaining sessions;
remembering preferences;
protecting accounts;
remembering cookie choices;
measuring website activity;
diagnosing technical problems;
supporting product functionality.

Not every technology performing these functions is technically a “cookie.”

For convenience, this Policy may use the term “cookies and similar technologies” to include technologies such as:

browser cookies;
local storage;
session storage;
device or browser identifiers;
pixels;
tags;
software development kit identifiers;
comparable browser or application technologies.

3. Scope

This Policy applies to cookies and similar technologies controlled by cRUD or placed in connection with our Services.

It may also apply where third-party service providers place or access technologies on our behalf.

It does not govern technologies independently deployed by:

customer websites;
external websites linked from cRUD;
third-party platforms independently selected by customers;
customer-controlled integrations;
social networks or streaming platforms independently operated by third parties.

Those third parties may maintain their own cookie and privacy policies.

cRUD intends to follow the following principles when using cookies and similar technologies:

Use technologies for defined purposes.
Avoid unnecessary tracking.
Distinguish essential functionality from optional tracking.
Provide understandable information about material technologies.
Provide choices where consent or preference management is appropriate.
Avoid pre-selecting optional consent where affirmative consent is required.
Record material cookie preferences where appropriate.
Avoid describing technologies as anonymous if they can reasonably identify or relate to an individual.
Update this Policy when our actual technology materially changes.

5. Categories of technologies we may use

Depending on the relevant cRUD property and functionality, cookies and similar technologies may fall into the following categories:

Strictly necessary cookies
Security cookies
Authentication and session cookies
Preference and functionality cookies
Analytics and performance cookies
Communications-related technologies
Marketing or advertising technologies, if introduced
Third-party integration technologies

Not every category is necessarily used at all times.

6. Strictly necessary cookies

Strictly necessary technologies are required for basic operation of a website, application or requested functionality.

They may be used for purposes including:

loading application functionality;
maintaining essential application state;
routing traffic;
maintaining secure sessions;
fraud prevention;
preventing request forgery;
processing required privacy choices;
remembering cookie preferences;
maintaining system integrity.

Because these technologies are necessary to provide functionality requested by the user or protect the Service, disabling them may make some or all of the Service unusable.

Where applicable law permits, we may use strictly necessary technologies without requesting optional marketing or analytics consent.

7. Authentication cookies

Authentication technologies may be used to:

identify a signed-in session;
keep a user logged in;
validate session state;
associate requests with the correct Account;
enforce logout;
support session expiry;
prevent unauthorized access.

Authentication cookies may contain or reference:

session identifiers;
opaque authentication identifiers;
signed tokens;
session expiry information.

We do not intentionally place readable passwords inside cookies.

8. Session cookies

Some cookies exist only during a browser session.

They may be deleted when:

the browser is closed;
the user logs out;
the session expires;
security controls invalidate the session.

Session cookies may support:

navigation;
authentication;
temporary form state;
security;
webinar participation;
account administration.

9. Persistent cookies

Some cookies or browser-storage entries may remain after a browser session ends.

Persistent technologies may be used to remember:

preferences;
cookie choices;
trusted-session states;
language;
timezone;
selected Organization or workspace;
interface settings;
other persistent functionality.

Their duration should be proportionate to their purpose.

10. Security cookies

Security-related technologies may help us:

detect suspicious authentication;
identify repeated failed login attempts;
prevent abuse;
enforce rate limits;
protect against request manipulation;
protect session integrity;
detect automated attacks;
investigate security incidents.

Security technologies may be considered necessary to protect cRUD and its users.

11. Preference cookies

Preference technologies may remember choices such as:

language;
timezone;
display settings;
previously selected workspace;
interface preferences;
notification settings;
accessibility settings;
cookie preferences.

Some preference functionality may not work if these technologies are disabled.

12. Analytics and performance technologies

With the visitor's permission, the cRUD Company website uses Google Analytics 4, delivered through the Google Tag Manager web container, to understand how visitors use the website.

Depending on the page and visitor interaction, this measurement may include:

page views and page titles;
the first occasion on which approximately 90 per cent of a page becomes visible;
clicks leading to another website;
downloads of supported file types;
starts, progress milestones and completions for supported YouTube videos;
referral and campaign information;
browser, device category and language information;
approximate geographic information;
pseudonymous analytics identifiers; and
aggregate website-use trends.

Site-search measurement and automatic form-interaction measurement are disabled. Google Signals, advertising storage, advertising user data and advertising personalisation are also disabled.

We do not configure website analytics to collect submitted form contents, authenticated product account information or information entered into search fields.

We use this information to understand website usage, improve navigation and content, evaluate resources and diagnose measurement problems.

Google Tag Manager is the delivery mechanism that loads the analytics configuration. The container itself is not loaded before the visitor selects “Accept analytics”. Google Analytics 4 is the service that ultimately receives the approved information.

13. Personal data and analytics

Google Analytics may receive a pseudonymous cookie identifier, session information, page title, a controlled version of the current page address, referrer information, event timestamps, browser and device information, language information and interaction-event details.

The current page address sent through our Google Analytics configuration removes the URL fragment and removes query parameters except for the following approved campaign parameters:

utm_id
utm_source
utm_medium
utm_campaign
utm_source_platform
utm_term
utm_content

These campaign parameters must not contain names, email addresses, account identifiers, confidential information or other personal data.

Other analytics fields can contain URLs. For example, a referrer or the destination of an outbound link or file download may contain query parameters supplied by another website. We therefore avoid intentionally placing personal data in public website URLs or destination links.

Google may process an Internet Protocol address to determine approximate location and route the analytics request. Google states that the individual IP address is discarded before the information is logged in Google Analytics.

Analytics information should be treated as pseudonymous rather than inherently anonymous.

14. Optional analytics

Google Analytics 4 is optional on the company website. Before it loads, the visitor may:

accept analytics; or
reject optional analytics.

The choice is recorded locally in the visitor's browser and may be changed later through the “Cookie settings” link in the website footer.

We may distinguish between:

essential operational telemetry; and
optional behavioural analytics.

Operational telemetry necessary for maintaining security, reliability or requested functionality may be treated differently from optional analytics.

When analytics consent has been granted, enhanced measurement is configured for:

page views;
scroll reach;
outbound clicks;
supported file downloads; and
supported YouTube video engagement.

Site search and automatic form interactions remain disabled.

Video-engagement measurement requires a supported YouTube player with the JavaScript API enabled. The website uses YouTube's privacy-enhanced embed domain and creates the player only after the visitor chooses to play the video.

15. Marketing and advertising technologies

At the date of this Policy, cRUD does not intend this Policy to imply that we use third-party behavioural advertising technology unless such technology is actually deployed.

If we introduce technologies for:

advertising;
retargeting;
cross-site behavioural tracking;
advertising attribution;
audience matching;
advertising personalization,

we will update this Policy and provide any consent or choice mechanisms required by applicable law before or when such functionality is introduced.

16. We will not invent tracking vendors

A vendor will not be listed in this Cookie Policy merely because it is common in SaaS products.

Google Analytics 4 is implemented on the company website and is described in the cookie list below. This Policy does not by itself mean that cRUD uses:

Meta Pixel;
LinkedIn Insight Tag;
Hotjar;
Microsoft Clarity;
Mixpanel;
PostHog;
Segment;
other tracking systems.

A service should be listed only after it has actually been implemented or formally approved for production use.

This reflects The cRUD Company's broader policy that planned capabilities and provider abstractions must not be presented as production-verified functionality.

17. Product analytics

cRUD may generate first-party product telemetry relating to use of cRUD Webinar.

Such telemetry may include:

feature usage;
page navigation;
webinar management actions;
system errors;
operational events;
user-interface interactions;
performance information.

Where associated with an identifiable Account, this information may constitute personal data.

It will be processed in accordance with our Privacy Policy.

18. Webinar attendee technologies

When an Attendee enters a webinar experience, browser technologies may be used for purposes such as:

validating attendee access;
maintaining webinar session state;
remembering authorized access;
maintaining waiting-room state;
live-room functionality;
replay access;
preventing unauthorized entry;
remembering webinar-related preferences.

These technologies may be necessary to provide the webinar experience.

19. Registration interfaces

Registration pages may use technologies necessary to:

maintain form state;
prevent duplicate submissions;
prevent automated abuse;
preserve referral or attribution information;
remember consent choices;
manage session state.

Where registration attribution information is collected, its treatment will be described in this Policy, the Privacy Policy or an appropriate contextual notice.

20. UTM and attribution information

cRUD Webinar may preserve campaign attribution information supplied through URLs, such as:

UTM source;
UTM medium;
UTM campaign;
UTM term;
UTM content;
referral source.

This information may be associated with:

registration;
webinar attendance;
campaign analytics.

It may therefore become associated with an identifiable registrant.

Customers using such information remain responsible for their own lawful use of the resulting data.

On the cRUD Company website, the page address sent to Google Analytics retains only the approved campaign parameters listed in section 13. All other query parameters and the URL fragment are removed before the address is sent.

The company website uses a necessary browser-local storage entry to remember:

whether a cookie banner has been shown;
consent granted;
consent denied;
selected categories;
preference timestamp;
applicable consent version.

Without retaining a preference record, users might be repeatedly asked to make the same selection.

A cookie used solely to remember cookie preferences may therefore itself be treated as necessary.

Where appropriate, a cookie preference record may include:

anonymous or user identifier;
categories allowed;
categories denied;
consent version;
timestamp;
source;
subsequent preference change.

Authenticated users' cookie preferences may in some circumstances be associated with their Account.

Selecting “Accept” in a cookie interface does not give cRUD unrestricted permission to process personal data for unrelated purposes.

Cookie consent, where used, applies only to the categories and purposes described at the time of the choice.

Separate processing activities remain governed by our Privacy Policy and applicable law.

24. Required versus optional technologies

Our cookie interface may distinguish between:

Required / Necessary

These may include technologies needed for:

authentication;
security;
session operation;
requested functionality;
cookie preference storage.

These may not be switchable through ordinary cookie preferences if disabling them would prevent the Service from functioning properly.

Optional

Depending on our production configuration, these may include:

analytics;
performance measurement;
marketing;
personalization beyond what is necessary.

Where an optional category requires consent, it should not activate until appropriate permission has been obtained.

The company website presents an analytics consent bar before Google Analytics is loaded. It provides:

Accept analytics
Reject optional

The website does not make rejection materially harder than acceptance.

26. Rejecting optional cookies

Rejecting optional cookies should not prevent users from accessing basic functionality that does not depend on those optional technologies.

However, certain optional features may operate differently where their supporting technology is disabled.

Visitors can revisit their analytics choice through the “Cookie settings” link in the website footer.

Changes should apply prospectively.

28. Withdrawal

Where a cookie category is based on consent, a user may withdraw consent.

After withdrawal:

new optional tracking should cease where technically applicable;
technologies already stored may need to be removed or allowed to expire;
data previously lawfully collected may remain subject to applicable retention requirements.

29. Browser controls

Most browsers allow users to:

view cookies;
delete cookies;
block cookies;
block third-party cookies;
restrict storage.

The exact controls depend on the browser.

Users should understand that blocking all cookies may prevent:

signing in;
maintaining sessions;
webinar participation;
remembering preferences;
other cRUD functionality.

30. Local storage

cRUD may use browser local storage for functionality requiring data to persist locally on a device.

Potential uses include:

interface preferences;
non-sensitive application state;
preference records;
technical functionality.

Local storage may persist until:

the application removes it;
a defined expiry occurs;
the user clears browser data.

31. Session storage

Session storage may be used for temporary data that generally remains only for the duration of a browser tab or session.

It may help maintain:

navigation state;
temporary form information;
transient application state.

32. Pixels and tags

If deployed, pixels or tags may be used to measure:

email delivery;
page views;
conversions;
campaign effectiveness.

They should be described in this Policy where materially relevant.

We do not commit that such tracking is currently active merely because the platform technically supports email analytics.

33. Email tracking technologies

Certain email systems may support information such as:

delivery;
bounce;
complaint;
link interaction;
open status.

Technical accuracy varies by email client and privacy technology.

We should therefore not treat every email-open event as definitive proof that a human read a message.

Operational information about email delivery may be collected even where optional marketing analytics are disabled if necessary for:

deliverability;
bounce handling;
complaint handling;
suppression management;
anti-abuse controls.

34. Webinar organizer tracking

Customers may use cRUD features to understand webinar campaign performance.

cRUD may provide organizers with information including:

registration source;
UTM parameters;
attendance;
engagement;
replay activity.

This platform analytics functionality is governed primarily by the Privacy Policy and Customer's own responsibilities.

The existence of a Cookie Policy does not eliminate the organizer's responsibility to provide appropriate disclosures about its own use of attendee information.

35. Third-party technologies

cRUD may rely on third-party providers for functions such as:

hosting;
content delivery;
authentication;
video infrastructure;
payment;
analytics;
customer support;
security.

A third party may set or access a technology where required to provide its functionality.

Where that provider acts on cRUD's behalf, information about the relevant service provider may be provided by cRUD where applicable.

The website also uses services that are not activated for general behavioural analytics.

Firebase Hosting delivers the website and necessarily receives normal web-request information.

Web3Forms receives information that a visitor chooses to submit through a website form.

An email-domain validation service hosted through GitHub Pages may receive a request for a short, hash-derived data shard when email-domain validation runs. The validation process does not send the visitor's complete email address, email local part, full domain name or complete domain hash to that service. The hosting provider still receives normal connection information associated with the request.

On pages containing published YouTube content, a thumbnail service may receive a request when the thumbnail is displayed. The YouTube privacy-enhanced player is created only after the visitor chooses to play the video. YouTube may then receive ordinary connection and playback information independently of Google Analytics consent.

These functional requests should not be presented as Google Analytics activity.

36. No payment-provider technologies

cRUD does not use online checkout, hosted payment pages or third-party payment providers. Payments to cRUD are made by bank transfer or UPI against an invoice.

No cookies or similar technologies are used by payment providers in connection with payments to cRUD.

37. Live audio/video providers

Where a third-party live-media provider supports cRUD Webinar, browser technologies may be necessary to:

authenticate room access;
maintain media sessions;
support network connectivity;
maintain session state.

These technologies may be technically necessary for the requested live webinar functionality.

38. Embedded content

A webinar page may contain embedded or linked third-party content.

Examples could include:

video;
external media;
social content;
external forms.

Where third-party embedded content is actually introduced, that provider may independently place technologies or receive information from the user's browser.

cRUD cannot necessarily control independent third-party technologies.

39. Customer-created links

Webinar organizers may include links to external websites.

When a user follows such a link, the destination site's own cookie and privacy practices apply.

The cRUD Cookie Policy does not govern the independent site's technologies.

40. Data collected through cookies

Depending on the technology, information may include:

cookie identifier;
session identifier;
IP address;
timestamp;
browser;
device category;
language;
page URL;
referrer;
feature event;
Account ID;
Organization ID;
webinar ID;
registration ID;
preference settings.

Not every cookie contains every category.

We may process information generated through cookies or similar technologies to:

provide requested functionality;
authenticate users;
maintain sessions;
secure Accounts;
prevent abuse;
remember choices;
measure performance;
understand Service usage;
improve products;
maintain attribution;
fulfill communication preferences;
comply with legal obligations.

42. Relationship to the DPDP framework

Where information collected through a cookie or similar technology constitutes digital personal data, its processing may be subject to India's Digital Personal Data Protection framework.

The DPDP Rules, 2025 were formally notified in November 2025 with phased commencement. Rules addressing several substantive operational obligations will become effective according to the commencement schedule specified in those Rules. (MeitY)

cRUD intends to structure its privacy notices and consent mechanisms so they can operate consistently with that framework as applicable.

Where consent is relied upon for processing personal data through optional cookies, the associated request should identify the relevant purpose with reasonable clarity.

Consent to one optional category should not automatically be interpreted as consent to materially unrelated processing.

44. Essential service communications are separate

Cookie preferences do not control essential service email.

For example, disabling analytics cookies does not mean cRUD must stop sending:

password resets;
security warnings;
transactional emails;
webinar confirmations;
billing notices;
legally required communications.

Email communication preferences are governed separately by our Communications & Consent Policy.

A user accepting optional analytics cookies does not automatically consent to receive promotional email.

Likewise:

marketing email consent does not automatically authorize advertising cookies;
acceptance of Terms does not automatically authorize optional tracking.

These are separate choices where applicable.

46. Logged-in versus logged-out users

Certain cookie usage may differ depending on whether a user is:

logged out;
signing up;
signed in;
attending a webinar through a unique access link.

Signed-in Services may need additional session and security technologies.

47. Unique attendee links

cRUD Webinar may use unique access links for Attendees.

Where an Attendee accesses such a link, the Service may use browser/session technologies to:

validate the link;
establish an attendee session;
maintain access;
prevent unauthorized reuse;
enforce webinar-specific permissions.

This may involve information linked to an identifiable attendee.

48. Passwordless access

Where passwordless access is used, a browser session may be created after a valid access link is verified.

The browser may then receive a cookie or similar session mechanism required to maintain access.

Such a technology may be strictly necessary.

49. Fraud and abuse prevention

Cookies or technical identifiers may be used to detect:

automated registrations;
unusual activity;
Account circumvention;
repeated abuse;
security attacks;
suspicious authentication;
malicious request patterns.

Where appropriate and permitted by law, this data may contribute to enforcement decisions.

50. Domain-level enforcement

Where an Account or Organization is suspended or banned for serious abuse, cRUD may use legitimate technical controls to prevent circumvention.

These controls may involve:

Account identifiers;
domain information;
security records;
session records;
fraud indicators.

Such anti-abuse functionality is governed by the Terms of Service, Acceptable Use Policy and Privacy Policy rather than ordinary optional cookie preferences.

Different technologies may have different lifetimes.

They may be:

session-only;
short-term;
persistent for a defined period.

Retention should be proportionate to the function.

Information subsequently transferred into operational records may be retained according to the relevant Data Retention & Deletion Policy rather than the browser cookie's expiry period.

52. Deleting browser cookies does not delete account data

Deleting cookies from a browser may:

sign the user out;
clear preferences;
remove stored browser identifiers.

It does not necessarily delete:

cRUD Account information;
webinar registrations;
billing records;
server logs;
Customer Content;
other personal data maintained in cRUD systems.

Requests concerning those records are governed by our Privacy Policy and Privacy Rights process.

A cookie expiring does not necessarily mean all information previously associated with that cookie is simultaneously erased.

For example, security events or transaction records may need to remain for:

security;
fraud prevention;
legal obligations;
audit;
dispute resolution.

Conversely, a cookie being stored in a browser does not authorize cRUD to retain associated server data indefinitely.

54. Children

cRUD Accounts are intended primarily for adults and professional/business users.

Where a service directed at or involving children could use cookies or similar technologies, additional privacy requirements may apply.

We may limit optional tracking in such contexts or restrict the relevant use entirely.

Our treatment of children's data is described further in our Privacy Policy.

55. International users

Users may access cRUD from jurisdictions with their own cookie or tracking rules.

Where mandatory local law imposes additional requirements, we may:

present region-specific consent controls;
disable certain technologies;
adjust available cookie categories;
provide additional notices.

The presence of a global Cookie Policy does not override mandatory local law.

56. European or other jurisdiction-specific requirements

If cRUD begins actively targeting or serving users in jurisdictions with additional cookie-consent requirements, we may implement jurisdiction-specific controls.

This may include prior consent for specified non-essential storage or access technologies.

This Policy does not represent that cRUD is currently subject to every foreign privacy regime merely because a person can technically visit the website from another country.

The company website uses the following browser storage and cookies:

Technology	Provider	Purpose	Duration
`crud.analytics-consent.v1`	The cRUD Company	A browser `localStorage` entry, not an HTTP cookie. Records whether optional analytics was accepted or rejected, the consent version and the time of the choice.	Until the visitor clears browser storage or cRUD changes the consent version.
`_ga`	Google Analytics	Distinguishes visitors for website analytics after consent.	Up to 2 years under Google's default configuration.
`_ga_TXCPDTE9L5`	Google Analytics	Maintains session state for measurement ID `G-TXCPDTE9L5` after consent.	Up to 2 years under Google's default configuration.

The cRUD Company consent preference is stored locally in the visitor's browser. It records the visitor's analytics choice and the applicable consent-policy version. It does not identify an account or contain contact information.

The _ga and measurement-specific _ga_ cookies may be created only after analytics consent has been granted. Google documents these cookies as being used to distinguish visitors and maintain analytics session information, with a possible duration of up to two years.

Google Tag Manager and Google Analytics do not load before analytics consent. Advertising storage, advertising user data, advertising personalisation and Google Signals remain disabled.

The current-page address sent to Google Analytics removes fragments and arbitrary query parameters while retaining only the approved campaign parameters listed in this policy.

Cookie names, durations and runtime behaviour will be verified again on the final custom domain before launch and after material analytics changes.

The cRUD Webinar product cookie and storage inventory remains under production verification.

58. First-party cookies

A first-party cookie is generally set in connection with the domain the user is visiting.

cRUD may use first-party technologies for:

authentication;
security;
preferences;
first-party analytics;
application functionality.

59. Third-party cookies

Google provides Google Analytics 4 on the company website. When a visitor accepts analytics, Google may receive technical information such as the page address, referrer, device and browser characteristics and IP-derived information in order to provide website measurement.

Google Analytics is not used by this website for behavioural advertising, advertising personalization or audience matching.

60. No guarantee regarding third-party browser behaviour

Browser companies and operating systems may change how they:

block third-party cookies;
partition cookies;
delete cookies;
limit tracking;
treat private browsing.

Accordingly, cRUD cannot guarantee that all described browser functionality behaves identically across every device/browser.

61. Global privacy controls and browser signals

Where legally required or reasonably supported, we may consider recognized browser privacy signals.

Because technical standards and legal requirements continue to evolve, we may update how such signals are handled.

Where cookies contain security-sensitive identifiers, cRUD may use controls such as:

secure transmission;
Secure cookie attributes;
HttpOnly attributes;
SameSite controls;
signed or opaque identifiers;
limited lifetimes;
session revocation.

The exact technical implementation may change as security architecture develops.

63. Sensitive information should not be stored unnecessarily

We aim not to place unnecessarily sensitive information directly into readable browser cookies.

Where a secure identifier can reference server-side data instead, that approach may be preferred.

64. Policy changes

We may update this Cookie Policy because of:

changes in technology;
new vendors;
new Services;
changes in cookies;
changes in analytics;
changes in law;
changes in consent requirements.

Each published version will include a version number and effective date.

Where we introduce materially different optional tracking or marketing technologies, we may:

update this Policy;
update cookie preference categories;
request a new choice where required;
notify users as appropriate.

Previously granted consent should not be treated as authorization for materially unrelated tracking beyond the scope of the original consent.

66. Version history

The canonical Cookie Policy is maintained at:

https://www.thecrudcompany.com/trust-center/cookie-policy

cRUD applications must link to this canonical website URL in a new browser tab and must not maintain a separate app-hosted Cookie Policy. Retired in-app legal routes should redirect to the canonical URL.

67. Contact us

Questions about this Cookie Policy or our use of cookies and similar technologies may be sent to:

Privacy

privacy@thecrudcompany.com

General enquiries

hello@thecrudcompany.com

Company

CRUD INFOSYSTEMS PRIVATE LIMITED Operating under the brand name The cRUD Company

Unit 101, OXFORD TOWERS 139, HAL Old Airport Road Kodihalli, Bengaluru, Karnataka 560008 India

This document is published by CRUD INFOSYSTEMS PRIVATE LIMITED, Unit 101, Oxford Towers, 139 HAL Old Airport Road, Kodihalli, Bengaluru, Karnataka 560008, India.

Return to Trust Center.