RIVOCEO / POLICIES & TRUST
Cookies & browser storage
What browser-held information does in RivoCEO, and what clearing it will—and will not—remove.
Draft preparedLocal storage is different from a cookie sent with a request.
Clearing site data can remove saved sessions and selections.
Browser cleanup does not remove a professional dataset record.
On this page 5 sections
Two kinds of browser storage
A cookie is a value a browser can send with website requests. Local storage keeps values for a website origin in the browser. RivoCEO’s current interface uses local storage for account-related information, cart selections, saved audience filters, and support-session continuity.
Local-storage values generally remain until the application removes them or you clear the site’s data. This is different from promising a fixed expiry for every stored item.
Account, audience, and checkout state
Account storage helps the interface recognize a returning session. Saved filters preserve an audience selection; cart and payment-reference storage help continue a purchase flow where those features are enabled. A saved selection is not evidence that payment completed.
Some internal keys retain legacy names from the shared application code. A key’s name does not, on its own, identify a recipient of information. Use the browser’s storage tools for this site’s origin to see and remove the stored entries.
Private support-session information
The support interface can retain a conversation identifier and access token, together with the supplied name and reply address. A private conversation link can grant access to that conversation. Treat it as sensitive and do not post it publicly.
Clearing this information can remove the browser’s route back to a conversation. It does not by itself delete the conversation from a server. The support backend must be connected and tested before the site can represent this workflow as available.
External services and optional tracking
Authentication, embedded payment features, and abuse-prevention services may introduce additional storage when enabled. Their actual use must be checked in the deployed site, including any tags added through hosting settings or a tag manager.
This draft does not assert that advertising trackers are installed, nor that the deployed site is tracker-free. A final inventory must identify actual purposes, providers, and durations. Optional storage that requires consent must not be treated as necessary merely because it is useful to the business.
Your browser controls
You can inspect, block, or clear site data using your browser settings. Doing so may sign you out, clear a cart, remove saved filters, or interrupt a support session. On a shared device, sign out and avoid leaving private links accessible to the next user.
Deleting browser data is not an account-deletion request and does not remove your professional record from the audience dataset. Use the verified rights-request channel for those separate actions.
Read the related policies before choosing an audience or placing an order.