TrekMail — Cookie Policy

1. Introduction

This Cookie Policy ("Policy") explains how TrekMail ("TrekMail," "we," "us," or "our") collects, uses, stores, and discloses information via cookies, web beacons, local storage, and other similar tracking technologies (collectively, "Cookies") when you visit our websites, use our applications, or interact with our products and services (collectively, the "Services" or "Sites").

This Policy is incorporated by reference into and is subject to the TrekMail Privacy Policy and Terms of Service. By accessing or using the Sites, you consent to the data practices described in this Policy, except where explicit consent is required by applicable law.

2. Definition of Cookies and Technologies

We strictly define the technologies covered by this Policy to ensure transparency and legal compliance.

• Cookies: Small text files containing a unique string of alphanumeric characters that are placed on your device (computer, smartphone, tablet) by your web browser.
  • Session Cookies: Temporary cookies that disappear after you close your browser.
  • Persistent Cookies: Cookies that remain on your device after you close your browser and may be used by your browser on subsequent visits to the Sites.
• Local Storage objects (LSOs): Data stored locally in your browser (e.g., HTML5 Local Storage) used to store content information and preferences.
• Server Logs: Files that record system activity, including IP addresses, browser types, and other technical data (note: while not "cookies," we treat this data with similar care regarding security and performance monitoring).

3. Categories and Purposes of Use

We use Cookies for specific, legitimate business purposes. We categorize these Cookies as follows:

A. Strictly Necessary (Essential) Cookies

These Cookies are fundamentally required for the operation of the Sites and cannot be switched off in our systems. They are necessary to:

• Authenticate users and maintain secure login sessions;
• Protect against fraud, abuse, and unauthorized access;
• Enable load balancing and ensure site reliability;
• Process user inputs (e.g., filling out forms or shopping carts).

Legal Note: Under most jurisdictions (including the US and EU), we do not require your consent to deploy Strictly Necessary Cookies.

B. Functional (Preference) Cookies

These Cookies allow the Sites to remember choices you make to provide enhanced, personalized features. This includes:

• Language or regional settings;
• User Interface (UI) customizations (e.g., dark mode vs. light mode);
• Retention of dashboard configurations.

C. Performance and Analytics Cookies

We use these Cookies to collect information about how users interact with our Sites. This data is aggregated and anonymized to help us improve the functionality and performance of our Services. We may use these technologies to:

• Analyze traffic patterns and server load;
• Identify popular or problematic pages;
• Debug technical issues.

D. Marketing, Advertising, and Conversion Tracking Cookies

TrekMail uses certain cookies and tracking technologies to measure the effectiveness of its marketing efforts and attribute conversions. These technologies are subject to cookie consent where required by applicable law (see Section 5 below). We use the following:

• Meta (Facebook) Pixel: We deploy the Meta Pixel, which sets the _fbp cookie (first-party, browser-generated identifier) and may read the _fbc cookie (click identifier set when a user arrives via a Facebook ad). The Pixel transmits page view and conversion event data (such as registration, checkout, and purchase events) to Meta Platforms, Inc. In addition, we use the Meta Conversions API to transmit server-side events with hashed identifiers (email, name, external ID) for conversion attribution. Meta processes this data as an independent controller under its own Data Policy.
• Google Analytics 4 (GA4): We use GA4 for website analytics and conversion tracking. GA4 sets cookies (such as _ga and _ga_*) to distinguish unique visitors and track session activity. We also transmit server-side events (such as purchase events) via the GA4 Measurement Protocol using a stored client identifier. Google processes analytics data in accordance with its Privacy Policy.

No Ad Network Participation: TrekMail does not participate in real-time bidding (RTB) advertising exchanges, does not sell personal data to advertising networks, and does not deploy retargeting or behavioral advertising cookies beyond the conversion tracking technologies described above.

E. Affiliate Attribution Cookies

When a visitor clicks an affiliate referral link, TrekMail sets a first-party, cryptographically signed (HMAC-SHA256) attribution cookie to record the referring affiliate. This cookie is used solely to attribute the visitor's subsequent signup to the correct affiliate for commission purposes. The cookie uses the SameSite=Lax attribute and persists for the duration of the attribution window (typically 30 days). No personal data is stored in the cookie itself; it contains only a signed affiliate identifier.

In addition, if you arrive via a link from an Admitad publisher, Admitad's tracking script sets a _admitad_uid cookie on our domain (httpOnly, Secure). This cookie is used to attribute a subsequent purchase to the Admitad publisher for commission purposes. If you complete a purchase, we transmit a server-side conversion postback to Admitad containing the order identifier and commission-relevant data. No full personal details (name, email) are included in the postback. The _admitad_uid cookie is managed by Admitad in accordance with their Privacy Policy.

4. Third-Party Technologies and Liability Disclaimer

You acknowledge that certain features of the Sites rely on services provided by third parties. These third parties may set their own Cookies or use similar technologies.

• Security & Anti-Abuse: We may use providers (e.g., Google reCAPTCHA) to detect bots and prevent automated abuse.
• Social Login Authentication: When you use social login (Google, Facebook, X/Twitter, or Microsoft), the authentication provider may set cookies or use similar technologies during the OAuth flow. These cookies are managed by the respective provider according to their privacy policies.
• Payment Processing: If you engage in financial transactions, third-party payment processors may deploy Cookies to prevent fraud and process payments securely.
• Embedded Content: External resources (e.g., video players, social media widgets) may utilize their own tracking mechanisms.
• CDN Performance Assets: Certain UI libraries (such as Chart.js for dashboard charts and QRious for QR-code generation in two-factor authentication setup) are loaded from public Content Delivery Networks — specifically Cloudflare CDN (cdnjs.cloudflare.com) and jsDelivr (cdn.jsdelivr.net). These are non-tracking, open-source CDNs used solely for performance. They may receive your IP address and User-Agent as part of standard HTTP requests. They do not set cookies or track you for advertising purposes.

Disclaimer: TrekMail does not control these third-party Cookies, and their use is governed exclusively by the privacy policies of the respective third parties. TrekMail expressly disclaims liability for the data collection practices of these third-party entities. We encourage you to review their privacy policies regarding their use of Cookies.

5. Your Choices and Controls

You retain control over how Cookies are managed on your device.

A. Browser Settings

Most web browsers allow you to manage Cookies through their settings preferences. You can typically:

• Delete all existing Cookies;
• Block all Cookies;
• Block third-party Cookies only.

Warning: Blocking Strictly Necessary Cookies will result in the inability to log in or use core features of the TrekMail Services.

B. Preference Center (Where Applicable)

If legally required in your jurisdiction, we will provide a "Cookie Preference Center" or banner allowing you to opt-in or opt-out of non-essential Cookies (such as Analytics).

C. Global Privacy Control (GPC) and "Do Not Track"

Various browsers offer "Do Not Track" (DNT) or Global Privacy Control (GPC) signals.

• Our Response: Where required by state or federal law (such as under the California Consumer Privacy Act (CCPA) as amended by CPRA), TrekMail recognizes valid GPC signals as a request to opt-out of the "sale" or "sharing" of personal information.
• Limitation: Because there is no universal industry standard for DNT signals, we may not respond to all DNT mechanisms unless required by applicable law.

6. Data Retention

Cookies have different lifespans. Session Cookies expire when you close your browser. Persistent Cookies remain on your device for a set period specified in the Cookie or until you manually delete them. We limit the lifespan of our persistent Cookies to what is reasonably necessary for the purposes outlined in Section 3.

7. Updates to This Policy

We reserve the right, at our sole discretion, to modify or replace this Policy at any time. Any changes will be effective immediately upon posting the revised Policy on the Sites.

• Notice: For material changes, we may provide additional notice (such as a banner on the dashboard or an email notification).
• Acceptance: Your continued use of the Sites following the posting of any changes constitutes your acceptance of those changes.

8. Contact Information and Legal Inquiries

We do not maintain public telephone lines for legal compliance issues. To verify your identity and ensure a secure audit trail, all inquiries regarding this Policy must be submitted in writing.

If you have questions or wish to exercise your rights:

1. Current Customers: Submit a support ticket via the secure TrekMail dashboard (Preferred Method).
2. General Inquiries: Use the official contact form available on our website.
3. Postal Mail:
   TrekGuider Inc.
   Attn: TrekMail Legal Department
   1207 Delaware Ave, #2058
   Wilmington, DE 19806
   United States

Please include sufficient detail in your correspondence to allow us to verify your identity and address your specific concern.