Cookie Policy
How we use cookies, browser storage, analytics, and similar technologies across revisepilot.com.
Effective Date: April 19, 2026
This Cookie Policy applies to NexGen Language Editing, LLC and its brand RevisePilot. The frontends share one policy family and core platform architecture. Some technologies described below may only appear on selected frontends, products, or rollout stages. If we introduce a new non-essential tracker, we will update this policy and, where required, collect consent first.
1. Technologies We Use
We use a mix of cookies, session storage, local storage, server logs, and tracking pixels to run the service, secure accounts, remember preferences, measure traffic where permitted, and manage email communications.
2. Strictly Necessary Technologies
| Name / Type | Where Used | Purpose | Typical Duration |
|---|---|---|---|
aee_refresh cookie |
Authenticated frontends | Keeps the refresh-token flow working so users can stay signed in securely. | Up to 7 days, or removed sooner on logout. |
authToken and refreshToken in sessionStorage |
Interactive account areas | Maintains authenticated browser state during the current browser session. | Until the tab or browser session ends, or earlier if cleared. |
aee-theme in localStorage |
All frontends | Remembers light or dark mode preference. | Until changed or cleared. |
aee-cookie-consent in localStorage |
Frontends that offer analytics consent controls | Stores whether you accepted or rejected optional analytics. | Until changed or cleared. |
These technologies are used because the service cannot function reliably or securely without them, or because they store a preference you directly request.
3. Optional Analytics Technologies
On frontends where we use Google Analytics, the Google tag runs in a privacy-protective consent mode. Until you choose to allow analytics, it sends only aggregated, cookieless measurement signals and does not store analytics cookies or read advertising identifiers on your device. When you allow analytics, the cookies and identifiers below are enabled. If you reject analytics, no analytics cookies or identifiers are ever set, and if your browser sends a Global Privacy Control signal the tag is disabled entirely.
| Provider | Purpose | Examples | Typical Duration |
|---|---|---|---|
| Google Analytics / Google Tag | Measures page views, traffic sources, and aggregate site performance. | _ga, _ga_*, related provider-set identifiers |
Provider-controlled; commonly up to 2 years. |
4. Email Tracking
Marketing and lifecycle emails may include a tracking pixel and tracked links so we can understand whether a message was opened, clicked, or unsubscribed. This helps us measure campaign performance, detect deliverability problems, and maintain suppression lists.
5. How to Control Cookies and Similar Technologies
- Use the preference controls on this page to allow or reject optional analytics where available.
- Adjust browser settings to block or delete cookies and browser storage.
- Use private browsing mode or clear local storage/session storage if you do not want preferences remembered on a device.
- Use email unsubscribe links or account settings to manage marketing email tracking going forward.
6. Relationship to the Privacy Policy
This Cookie Policy should be read together with our Privacy Policy and Terms of Service. If those documents conflict, the more specific notice about the technology in question controls.
7. Contact
Questions about cookies or consent can be sent to privacy@revisepilot.com.