COOKIE POLICY AND SETTINGS
Your browser choices, with the details visible.
The supplied publication offers one optional category: remembering article reading positions. It is off until you choose it. Reading articles, using the planning tools and following ordinary navigation do not require this optional feature.
Storage inventory
The following inventory describes the supplied publication code reviewed September 30, 2026. It does not claim to enumerate every service on a separately configured host. Browser restrictions or later software changes can affect the observed result.
| Item / source | Purpose and category | Trigger and duration | Removal or limitation |
|---|---|---|---|
| por_privacy_v1 / this site | First-party preference cookie; necessary to remember a choice. Stores version, reading yes/no and choice time. | Written when you save, accept or reject a choice; browser expiry up to 180 days. | A new choice replaces it. Browser site-data settings can delete it; deletion means choices must be made again. |
| por_reading_v1 / this site | Optional localStorage record; up to 30 relative article paths, position ratios and timestamps. | Enabled only after optional reading consent. Entries older than 180 days are ignored; cleanup occurs when the feature runs. | Rejecting/withdrawing attempts deletion. Raw localStorage may remain until cleanup runs or you clear it; browser restrictions can block removal. |
| Planning-tool selections / current page | Temporary page state for comparing workstreams and organizing readiness questions. | No cookie, localStorage or sessionStorage writes in the supplied tool code; browser restoration may retain form values. | No saved tool record to withdraw. These controls do not request employee data. |
| Outbound video/source links / destination provider | Navigation to the chosen external source; no embedded player category. | Request occurs when you follow the link. Destination storage and duration are governed there and not verified here. | No provider player loads in this publication. Our settings do not delete destination-side records. |
What the choices mean
- Accept all optional: enable the one supplied optional reading-position feature.
- Reject non-essential: keep reading storage off and attempt to remove any saved reading record.
- Manage preferences: inspect the reading option and save its selected state.
The necessary preference cookie is not presented as an optional switch. Closing the settings panel without saving does not grant consent. An absent, malformed or expired valid choice leaves optional reading storage off.
Reopen or withdraw
Cookie Settings is available from the persistent control and the footer on public pages. Reopening shows the saved reading choice when it can be read. Turn reading positions off and save, or choose Reject non-essential. The feature stops future writes and removes its local record where browser access permits.
This does not remove emails, server logs, WordPress administrative cookies or another website’s storage. Use browser site-data controls for local data you want removed, and the appropriate service or publisher for other records. Clearing site data also removes the saved preference.
If JavaScript or storage is unavailable
Without JavaScript, the articles and server-rendered planning information remain readable, optional reading-position saving does not run and the settings link leads to this policy. Previously saved browser data can be removed through the browser’s site-data settings.
If a cookie choice cannot be saved, the interface reports that failure and keeps optional storage off on that page. If localStorage is blocked, the feature cannot save reading positions. A browser may prevent the site from removing previously saved data; use browser settings rather than assuming a failed request erased it.
Other technology and verification limits
No sessionStorage writes, advertising events, analytics events or embedded video requests are part of these supplied reader features. That statement is limited to their code. WordPress login, added plugins, the server, a CDN or security services may behave differently and need their own inventory.
The detection basis for this inventory is inspection of the supplied preference and planning scripts and their storage keys, event triggers and request paths. A live host’s complete network, cookie and server-record inventory is not established by this page. The publisher should keep disclosures aligned with the deployed configuration.
For publisher and correspondence details, see the Privacy Policy. Questions: morgenjonl@corps.com.