TrekMail — Cookies and Similar Technologies Policy
Effective Date: January 29, 2026
Last Updated: September 4, 2026
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 supplements the TrekMail Privacy Policy and explains the technologies used on the Sites. Selecting “Okay” records your choice to allow the limited analytics and advertising-measurement technologies described below, in addition to technologies necessary to operate and secure the Sites. This choice does not waive any privacy right or authorize processing where applicable law requires an additional choice or control.
2. Definition of Cookies and Technologies
For purposes of this Policy, these technologies include:
-
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;
- Remember a device you have explicitly marked as "trusted" so that we can reduce repeated two-factor authentication (2FA) prompts on that device. This trusted-device token persists until it expires (typically up to 90 days) or until you revoke the device from your security settings;
- 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, Drive view preferences, billing currency preference, and Webmail interface preferences.
Examples of functional storage we may use include:
| Technology | Purpose | Typical Duration |
|---|---|---|
| Drive view preference | Remembers whether Drive is displayed in grid or list view. | Until cleared by you or your browser. |
| Webmail theme preference | Remembers your selected Webmail appearance preference. | Until cleared by you or your browser. |
| Account recovery prompt state | Remembers whether you dismissed certain account-recovery prompts. | Until cleared by you or your browser. |
| Currency preference | Remembers your selected billing currency. | Typically 30 days. |
C. Performance and Analytics Cookies
We use these Cookies to collect information about how users interact with our Sites. Depending on the technology, this information may be aggregated or associated with a browser, device, session, campaign, or account identifier. We use it 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. Their use remains subject to applicable law and the controls described in Section 5. We may use the following:
-
Meta (Facebook) Pixel: We deploy the Meta Pixel, which sets the
_fbpcookie (first-party, browser-generated identifier) and may read the_fbccookie (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
_gaand_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. - Other Advertising Measurement: Where enabled, Microsoft Advertising, Quora, and OpenAI advertising tools may process limited campaign, click, page, event, device, network, country, transaction, or matching information to attribute registrations, trials, checkouts, and purchases to advertising campaigns. We do not provide the contents of emails, contacts, calendars, or Drive files to these providers for advertising purposes.
No Sale of Customer Content: TrekMail does not sell Customer Content or provide the contents of emails, contacts, calendars, or Drive files to advertising providers. The technologies described above are used for site analytics, campaign measurement, attribution, and related fraud prevention.
E. Affiliate Attribution Cookies
When a visitor clicks an affiliate referral link, TrekMail may set a first-party, cryptographically signed (HMAC-SHA256) attribution cookie to record the referring affiliate. This cookie is used to attribute a subsequent signup or purchase to the correct affiliate for commission purposes. It persists for the applicable attribution window described by the relevant affiliate program or campaign. The cookie contains a signed affiliate identifier rather than the visitor's name or email address.
In addition, if you arrive via a link from an Admitad publisher, TrekMail may store an _admitad_uid value on our domain to attribute a subsequent purchase to that publisher. If you complete a purchase, we may transmit a server-side conversion postback containing the order identifier, attribution value, and commission-relevant data, but not your full name or email address. Admitad processes this information in accordance with its 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) are loaded from the public jsDelivr Content Delivery Network (
cdn.jsdelivr.net). This is a non-tracking, open-source CDN used solely for performance. It may receive your IP address and User-Agent as part of standard HTTP requests. It does not set cookies or track you for advertising purposes.
Third-party providers process information under their own terms and privacy practices where they act independently. TrekMail remains responsible for its own selection, configuration, and use of these technologies to the extent required by applicable law. We encourage you to review the relevant provider privacy policies.
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. TrekMail Cookie Notice
TrekMail displays a concise notice describing necessary technologies and the limited analytics and advertising measurement enabled after you select “Okay.” You may also use browser or device controls described above; blocking some technologies may affect measurement or certain Service functions. Where applicable law requires an additional choice or control, that legal requirement continues to apply.
C. Browser and Device Privacy Signals
Browsers and devices may offer "Do Not Track" (DNT), Global Privacy Control (GPC), cookie blocking, or similar signals. These controls may affect browser-based technologies but may not affect information already associated with an account, transaction, security event, or support request. Where applicable law grants a right relating to a particular use of personal information, a request may be submitted through the methods described in Section 8.
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 may modify this Policy from time to time. A revised Policy becomes effective when posted unless a later effective date is stated.
- Notice: For material changes, we may provide additional notice (such as a banner on the dashboard or an email notification).
- Prior Information: Where required by applicable law, we will seek any consent required before applying a materially different use to information collected under an earlier notice.
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:
- Current Customers: Submit a support ticket via the secure TrekMail dashboard (Preferred Method).
-
Postal Mail:
TrekGuider Inc.
Attn: TrekMail Legal Department
1207 Delaware Ave, #2058
Wilmington, DE 19806
United States
Creating a basic TrekMail account to use the Support Center is free. Please include sufficient detail in your correspondence to allow us to verify your identity and address your specific concern.