Log Activation: February 2026
To optimize your interface display and ensure stable navigation through THE APFZONE, our terminal deploys localized data trackers known as “Cookies.” These are small text beacons stored directly within your local hardware storage matrix.
By continuing to access our network relays, you authorize our synthetic monitoring units to deploy these telemetry trackers.
CORE OPERATIONAL BEACONS (Essential Cookies)
These tracking beacons are mandatory. Without them, the ship’s basic computer systems cannot function properly:
- Access Terminals: If you log into your account, a temporary beacon tracks your session state so you stay authenticated as you move across different pages.
- Security Modules: These prevent malicious script injections and secure your transmissions when using our sub-space contact streams.
- Consent Loggers: A secure, self-hosted record managed by WPConsent to remember your tracker preferences.
ARCHIVE MANAGEMENT BEACONS (Functional Cookies)
These trackers streamline your browsing experience and remember user settings:
- The Xenomorph Codex: These ensure that your interactions with our database plugin and PDF reading paths run efficiently without breaking.
THIRD-PARTY SECTOR TRANSMISSIONS (External Cookies)
We do not host invasive corporate advertising scripts, but our deep-space platform connects with global networks:
- Facebook Planetary Relays: When you click our secure links to bridge over to our 13-Year-Old Facebook Group Core Hub, Meta may deploy their own tracking beacons inside your browser to manage your social media connection.
DETECTED TARGET BEACONS (Active Cookie Registry)
Our automated defense sensors regularly scan the website layout to catalog every active cookie. The dynamic table below displays a real-time manifest of all active tracking frequencies detected within this sector.
Essential
Essential cookies enable basic functions and are necessary for the proper function of the website.
| Name | Description | Duration |
|---|
| wpconsent_preferences | This cookie is used to store the user's cookie consent preferences. | 30 days |
Comments
These cookies are needed for adding comments on this website.
| Name | Description | Duration |
|---|
| comment_author | Used to track the user across multiple sessions. | Session |
| comment_author_email | Used to track the user across multiple sessions. | Session |
| comment_author_url | Used to track the user across multiple sessions. | Session |
Login
These cookies are used for managing login functionality on this website.
| Name | Description | Duration |
|---|
| wordpress_logged_in | Used to store logged-in users. | Persistent |
| wordpress_sec | Used to track the user across multiple sessions. | 15 days |
| wordpress_test_cookie | Used to determine if cookies are enabled. | Session |
Statistics
Statistics cookies collect information anonymously. This information helps us understand how visitors use our website.
Google Analytics
Google Analytics is a powerful tool that tracks and analyzes website traffic for informed marketing decisions.
Learn more| Name | Description | Duration |
|---|
| _gac_ | Contains information related to marketing campaigns of the user. These are shared with Google AdWords / Google Ads when the Google Ads and Google Analytics accounts are linked together. | 90 days |
| __utma | ID used to identify users and sessions | 2 years after last activity |
| __utmt | Used to monitor number of Google Analytics server requests | 10 minutes |
| __utmb | Used to distinguish new sessions and visits. This cookie is set when the GA.js javascript library is loaded and there is no existing __utmb cookie. The cookie is updated every time data is sent to the Google Analytics server. | 30 minutes after last activity |
| __utmc | Used only with old Urchin versions of Google Analytics and not with GA.js. Was used to distinguish between new sessions and visits at the end of a session. | End of session (browser) |
| __utmz | Contains information about the traffic source or campaign that directed user to the website. The cookie is set when the GA.js javascript is loaded and updated when data is sent to the Google Anaytics server | 6 months after last activity |
| __utmv | Contains custom information set by the web developer via the _setCustomVar method in Google Analytics. This cookie is updated every time new data is sent to the Google Analytics server. | 2 years after last activity |
| __utmx | Used to determine whether a user is included in an A / B or Multivariate test. | 18 months |
| _ga | ID used to identify users | 2 years |
| _gali | Used by Google Analytics to determine which links on a page are being clicked | 30 seconds |
| _ga_ | ID used to identify users | 2 years |
| _gid | ID used to identify users for 24 hours after last activity | 24 hours |
| _gat | Used to monitor number of Google Analytics server requests when using Google Tag Manager | 1 minute |
🛑 ADJUSTING CLOAKING CAPABILITIES
You remain in full control of your signal tracking. You can alter your security clearances or revoke your consent choices at any time directly through the floating widget tab deployed on your screen. Alternatively, you may clear your hardware cache manually through your local web browser settings:
Navigate to your browser’s Settings → Privacy & Security → Cookies to wipe your local cache clean.
Warning: Cloaking your terminal entirely by disabling cookies may cause certain structural grids, automated login forms, or PDF readings within the Xenomorph Codex to malfunction.
For deeper tactical data clarity regarding your files, review our full Classified Data Protocols.
