Cookie Policy for AmericaVoxPop.com
This Cookie Policy outlines how AmericaVoxPop LLC ("we," "us," or "our") employs cookies and similar tracking technologies on our membership-based platform, AmericaVoxPop.com. By using our services, you consent to the deployment of cookies as described below. For comprehensive details on data handling, review our Privacy Policy.
1. Definition and Purpose of Cookies
Cookies are small text files stored on your device (computer, smartphone, or tablet) when accessing websites. These files enable platforms like AmericaVoxPop.com to authenticate users, retain preferences, and enhance security for membership accounts. They are integral to delivering personalized experiences, such as saved login credentials and tailored content recommendations.
2. Categories of Cookies and Storage Technologies
2.1 Essential Authentication Cookies
Critical for core membership functionalities:
Critical for core membership functionalities:
- accessToken (HttpOnly cookie): Authenticates API requests. Expires after 1 hour, or 7 days if "Remember Me" is selected at login.
- refreshToken (HttpOnly cookie, path restricted to /api/auth): Used to obtain new access tokens without re-entering credentials. Expires after 30 days, or at browser session end if "Remember Me" is not selected.
- csrfToken (JS-readable cookie): Protects against cross-site request forgery attacks. Expires after 4 hours.
These cookies cannot be disabled without breaking authentication and platform functionality.

2.2 Performance Analytics Cookies
Collect aggregated data to optimize service delivery:
Collect aggregated data to optimize service delivery:
- Google Analytics 4: Tracks traffic patterns, feature usage, and demographic trends via
_ga(2-year lifespan) and_gid(24-hour lifespan) cookies.
Analytics data is anonymized and never linked to individual member profiles.
2.3 Browser Storage (Session & Local Storage)
The following data may be stored locally in your browser (not transmitted as cookies):
The following data may be stored locally in your browser (not transmitted as cookies):
- Session storage: Temporary navigation state such as redirect paths after login. This data is cleared when the browser tab is closed.
- Local storage: Cross-tab synchronization signals (e.g., logout events) to keep your session consistent across browser tabs. No authentication tokens or personal data are stored in local storage.
3. Cookie Lifespan and Governance
| Cookie / Storage | Duration | Purpose |
|---|---|---|
| accessToken | 1 hour (7 days with Remember Me) | Authenticate API requests |
| refreshToken | 30 days (session-only without Remember Me) | Obtain new access tokens without re-login |
| csrfToken | 4 hours | Prevent cross-site request forgery |
_ga (Google Analytics) | 2 years | Distinguish unique visitors |
_gid (Google Analytics) | 24 hours | Distinguish unique visitors (short-term) |
4. Managing Cookies
Essential cookies (authentication) cannot be disabled without breaking core platform functionality. If you disable these cookies, you will not be able to log in or use member features.
Google Analytics cookies can be opted out of via:
- Your browser's cookie settings (Chrome, Firefox, Safari, Edge)
- The Google Analytics Opt-out Browser Add-on
No cookies on this site collect sensitive information (e.g., political views, biometric data). We do not use advertising or retargeting cookies.

5. Third-Party Data Sharing
Cookie and analytics data is never sold. Anonymized or necessary data may be shared with the following service providers:
- Google Analytics: Anonymized website traffic analysis
- Sentry: Error monitoring and application stability (collects technical error data, not personal information)
- AWS: Cloud infrastructure and secure data storage
- QuickBooks: Payment processing for subscription billing
All partners are contractually bound to handle data in accordance with applicable privacy laws.
6. Policy Updates and Member Notification
Revisions are posted quarterly, with material changes communicated via:
- Email alerts: Sent to active members 10 days prior to implementation.
- Version history: Accessible in the Policy Archive.



