Last updated: April 6, 2026
This Cookie Policy explains how Krickets LLC ("we," "our," or "us") uses cookies, software development kits (SDKs), device identifiers, and similar tracking technologies on our website kricketsllc.com ("Website") and our mobile applications ("Apps"). This policy should be read alongside our Privacy Policy.
There are several types of tracking technologies used across websites and mobile applications. Below is an overview of each:
Cookies are small text files placed on your device (computer, tablet, or smartphone) by a website you visit. They are widely used to make websites function correctly, improve efficiency, and provide reporting information to site owners. Cookies can be "first-party" (set by the website you are visiting) or "third-party" (set by a domain other than the one you are visiting).
Pixels (also known as web beacons, tracking pixels, or clear GIFs) are tiny, transparent images—typically 1×1 pixel—embedded in web pages, emails, or advertisements. When your browser or email client loads the pixel, it sends a request to the server that hosts the image, allowing the server to log the request and collect data such as your IP address, the time the content was viewed, the type of browser or email client used, and whether specific content (such as an email) was opened.
Local storage (also called "HTML5 storage" or "Web Storage") allows websites to store data in your browser that persists even after you close the browser window. Unlike cookies, local storage data is not automatically transmitted to servers with every request. It can store larger amounts of data and is often used for caching, user preferences, and offline functionality.
Session storage is similar to local storage but is scoped to a single browser tab or window. Data stored in session storage is automatically deleted when the tab or window is closed. It is commonly used for temporary data such as form entries, page state, or navigation context within a single browsing session.
SDKs are packages of code that app developers integrate into mobile applications to provide specific functionality—such as analytics, crash reporting, advertising, authentication, or push notifications. SDKs can collect and transmit data from your device, including device identifiers, usage events, crash logs, and network information. In mobile apps, SDKs serve a similar purpose to cookies on websites and are the primary mechanism for tracking and analytics.
Traditional HTTP cookies are designed for web browsers and do not function within native mobile applications. Instead, our Apps rely on SDKs and device-level identifiers to provide analytics, crash reporting, and other essential services. SDKs are embedded directly in the application code and communicate with third-party servers to transmit data. While the mechanism differs from browser cookies, the purpose is comparable: understanding usage patterns, diagnosing issues, and improving the user experience.
Our Apps may access or collect the following device identifiers, depending on your platform and privacy settings:
Our Apps integrate the Firebase SDK provided by Google. Firebase Analytics automatically collects certain events (such as app opens, screen views, and session starts) and allows us to log custom events related to feature usage. Data collected by Firebase includes:
Firebase Analytics data is processed by Google and is subject to Google's Firebase privacy documentation.
We use Firebase Crashlytics (or a comparable service) to collect crash reports and diagnostic data when our Apps encounter errors. This data helps us identify and resolve bugs. Crash reports may include:
Crash reporting data does not intentionally include personally identifiable information; however, stack traces may occasionally contain user-generated data if it was in scope at the time of the error.
When you grant permission for push notifications, our Apps receive a device token from Apple Push Notification Service (APNs) or Firebase Cloud Messaging (FCM). This token is a unique, opaque string that identifies your specific device and app installation for the purpose of delivering push notifications. Tokens may be refreshed periodically by the operating system. We store these tokens on our servers solely to send you notifications. If you revoke notification permissions, we will no longer be able to send push notifications to your device, and we will remove or deactivate the token.
These cookies are essential for the Website to function and cannot be disabled in our systems. They are usually set only in response to actions you take that amount to a request for services, such as setting your privacy preferences, logging in, or filling out forms. You can configure your browser to block or alert you about these cookies, but some parts of the Website may not function as a result.
| Cookie Name | Purpose | Duration |
|---|---|---|
| __session | Maintains your authenticated session state across page requests | Session |
| __csrf_token | Protects against Cross-Site Request Forgery (CSRF) attacks by validating form submissions | Session |
| __lb | Used for server-side load balancing to route your requests to the same backend instance | Session |
| __secure_ref | Ensures secure connections and validates the origin of requests | Session |
These cookies allow us to measure and analyze how visitors use our Website so that we can improve its performance and content. All data collected by these cookies is aggregated and anonymous. If you do not allow these cookies, we will not be able to include your visit in our statistics.
| Cookie Name | Provider | Purpose | Duration |
|---|---|---|---|
| _ga | Google Analytics | Distinguishes unique users by assigning a randomly generated number as a client identifier. Included in every page request to calculate visitor, session, and campaign data. | 2 years |
| _gid | Google Analytics | Stores and updates a unique value for each page visited. Used to count and track pageviews. | 24 hours |
| _gat | Google Analytics | Throttles the request rate to Google Analytics servers, limiting data collection on high-traffic sites. | 1 minute |
| _ga_<container-id> | Google Analytics 4 | Used to persist session state for GA4 measurement. | 2 years |
These cookies enable the Website to provide enhanced functionality and personalization. They may be set by us or by third-party providers whose services we have added to our pages. If you do not allow these cookies, some or all of these features may not function properly.
We may allow third-party advertising partners to set cookies on our Website to build a profile of your interests and serve relevant advertisements on other websites and platforms. These cookies do not store directly identifiable personal information but rely on uniquely identifying your browser and device. Even if you do not allow these cookies, you will still see advertisements, but they will be less relevant to you.
If we deploy advertising cookies in the future, this section will be updated with specific cookie names, providers, purposes, and durations.
We integrate third-party services that may set their own cookies on our Website or collect data through SDKs in our Apps. We do not control these third-party cookies or the data collected by third-party SDKs. Below is a detailed overview of the third-party services we use:
| Cookie | Purpose | Expiry |
|---|---|---|
| _ga | Distinguishes unique visitors by assigning a randomly generated client ID. Used to calculate visitor counts, session counts, and campaign metrics. | 2 years from last activity |
| _gid | Stores a unique ID for each page visited during a 24-hour period. Used to group pageviews into sessions and track user behavior within a single day. | 24 hours |
| _gat | Rate-limits requests to Google Analytics collection servers. Does not store user information. | 1 minute |
Google Analytics data is processed by Google LLC. For more information, see Google's Privacy Policy and Google Analytics Data Safeguards.
Firebase is a suite of development tools provided by Google. We use the following Firebase services, which may collect data through SDKs embedded in our Apps:
For details, see Firebase Privacy and Security documentation.
If our Apps or Website display advertisements, we may use Google AdSense (for web) or Google AdMob (for mobile). These services use cookies and mobile advertising identifiers (IDFA or GAID) to serve personalized or contextual advertisements. Key technologies include:
You can manage ad personalization at Google Ad Settings.
If applicable, we may use the Meta Pixel (formerly Facebook Pixel) on our Website. The Meta Pixel is a snippet of JavaScript code that places a cookie on your browser to:
The Meta Pixel transmits data to Meta Platforms, Inc. For more information, see Meta's Privacy Policy.
Our Website loads typefaces from Google Fonts. When you visit a page that uses Google Fonts, your browser establishes a direct connection to Google's servers to download the font files. In doing so, Google receives your IP address, the referring page URL, and standard browser metadata (user agent, language). Google states that it does not use this data for profiling or targeted advertising. For details, see Google Fonts Privacy FAQ.
Session cookies are temporary and are stored in your browser's memory only for the duration of your browsing session. They are automatically deleted when you close your browser (or, in some cases, after a period of inactivity). Session cookies are used for essential functions such as maintaining login state, preserving items in a shopping cart, and preventing CSRF attacks.
Persistent cookies remain on your device for a predetermined period or until you manually delete them. They survive browser restarts and device reboots. Below are the specific durations for persistent cookies used on our Website:
| Cookie | Type | Duration |
|---|---|---|
| _ga | Analytics | 2 years from last activity |
| _gid | Analytics | 24 hours |
| _gat | Analytics | 1 minute |
| _ga_<container-id> | Analytics (GA4) | 2 years |
| NID | Advertising (Google) | 6 months |
| IDE | Advertising (DoubleClick) | 13 months (or 24 hours in consent-required regions) |
You can control and manage cookies through your browser settings. Below are instructions for the most common browsers:
Starting with iOS 14.5, Apple requires apps to request your permission before tracking your activity across other companies' apps and websites. When our App requests access to your IDFA, you will see a system prompt asking you to allow or deny tracking. You can change this setting at any time:
On Android devices, you can manage your advertising identifier and ad personalization preferences:
You can prevent Google Analytics from collecting data about your visits to our Website by installing the Google Analytics Opt-Out Browser Add-On. This add-on instructs the Google Analytics JavaScript running on websites not to send visit information to Google Analytics.
You can opt out of interest-based advertising from participating companies through the following industry programs:
For mobile apps, you can download the DAA's AppChoices tool at https://youradchoices.com/appchoices to manage ad preferences on your device.
Both iOS and Android provide mechanisms to limit the use of your device's advertising identifier:
| Platform | Setting | Effect |
|---|---|---|
| iOS 14.5+ | Settings > Privacy & Security > Tracking > Disable "Allow Apps to Request to Track" | IDFA returns all zeros; apps cannot track across apps/websites |
| iOS (pre-14.5) | Settings > Privacy > Advertising > Limit Ad Tracking | IDFA returns all zeros; limited ad targeting |
| Android 12+ | Settings > Privacy > Ads > Delete advertising ID | GAID permanently removed from device |
| Android (pre-12) | Settings > Google > Ads > Opt out of Ads Personalization | Apps see GAID but cannot use it for ad personalization |
You have the right to decide whether to accept or reject cookies and tracking technologies. However, disabling them may affect your experience:
Do Not Track (DNT): Do Not Track is a preference you can set in your browser to signal to websites that you do not want to be tracked. There is currently no universally accepted standard for how websites should respond to DNT signals. At this time, our Website does not alter its data collection or tracking practices in response to DNT signals. We will update this policy if a formal standard is adopted and we implement support for it.
Global Privacy Control (GPC): Global Privacy Control is a browser-level signal that communicates your privacy preferences to websites you visit. Unlike DNT, GPC is recognized under certain privacy laws, including the California Consumer Privacy Act (CCPA) as amended by the California Privacy Rights Act (CPRA), and the Colorado Privacy Act. When we detect a valid GPC signal, we treat it as a request to opt out of the sale or sharing of personal information (as those terms are defined under applicable law) for the device and browser from which the signal is sent.
We may update this Cookie Policy from time to time to reflect changes in the cookies and tracking technologies we use, changes in the law, or changes in our business practices. When we make material changes, we will update the "Last updated" date at the top of this page. We encourage you to review this Cookie Policy periodically. If changes are significant, we may also provide additional notice such as an in-app notification or a prominent notice on our Website.
Your continued use of our Website or Apps after any changes to this Cookie Policy constitutes your acceptance of the updated policy.
If you have any questions, concerns, or requests regarding this Cookie Policy or our use of cookies and tracking technologies, please contact us: