Interim Cookie Policy. The production sign-in cookie inventory remains pending verification. This notice describes the currently identified application cookies and browser storage and may be updated as verification is completed.
Prospexe is operated by Robert Christopher Link, trading as Prospexe (“we”, “us” or “our”). This policy explains our use of cookies and related browser storage on www.prospexe.co.uk and within the Prospexe application (together, the “Service”).
It should be read alongside our Privacy Policy. Cookie settings are available at Cookie preferences. For questions, email info@prospexe.co.uk.
1. Cookies and similar technologies
Cookies are small pieces of information stored by your browser. Depending on their settings, they are sent with requests to the site or domain that set them. Cookies can support authentication, security and preferences.
Local storage and session storage also hold information in your browser. Unlike cookies, their contents are not automatically sent with every request, although the application may use stored information when carrying out a requested action.
This policy covers these forms of browser storage. Storing information in a customer’s Prospexe account or database is different from storing it on a browser; our Privacy Policy and applicable customer terms explain that processing.
2. Cookies currently identified in the application
2.1 Cookie-choice record
Name: telelink_cookie_preferences.
Purpose: remembers whether you chose “Essential only” or “Allow sidebar preference”, so the Service can honour that choice and avoid repeatedly asking while it remains valid.
Duration: up to 90 days from saving or changing the choice.
When set: after either choice is selected. Choosing “Essential only” therefore still saves this record of your choice; it is not the optional sidebar-state cookie.
2.2 Optional sidebar preference
Name: sidebar_state.
Purpose: remembers whether the sidebar component is open or closed.
Duration: up to 7 days from the most recent write of this cookie.
When set: only when you have allowed the sidebar preference and the relevant sidebar setting is changed. Selecting “Essential only” clears the existing sidebar cookie and withdraws permission to write it.
Some other workspace display settings are stored separately in local storage, as explained in section 3. The sidebar-cookie choice does not disable all browser-based display settings.
2.3 Workspace-selection cookie
Name: telelink_workspace_selection.
Purpose: retains the signed workspace selection used in the workspace-selection flow. It helps the Service handle the workspace you requested; it is not an advertising or analytics cookie.
Duration: up to 12 hours from setting the selection.
When set: when the workspace-selection flow is used. It is restricted to the /api/workspace-selection path. It is marked Secure and HttpOnly and uses SameSite=Lax. HttpOnly means application JavaScript cannot read its contents.
These durations describe each cookie’s expiry setting, not a promise that all associated account information is deleted when a cookie expires. Some cookie names retain the application’s legacy “telelink” prefix.
2.4 Authentication cookies — inventory pending
The Service uses Replit-managed Clerk authentication for sign-in and account security. Authentication cookies and related technologies support that service and are separate from the optional sidebar preference.
The exact production cookie names, domains and expiry settings have not yet been verified. This section will be updated from the active production configuration and observed cookie metadata before the inventory is finalised. No provider-wide example cookie list or assumed lifetime is presented here as the Service’s verified inventory.
2.5 Analytics and advertising technologies
If Replit-hosted analytics is enabled in Publishing, Replit injects the Umami tracker into the published Service. It automatically records page views and selected custom events. Our custom events use fixed event names and do not include contact details, account or record identifiers, or free-form user content.
Umami describes its tracker as operating without cookies or cross-site tracking; see the Umami documentation. We do not use advertising cookies or pixels.
The cookie controls on this Service manage only the optional sidebar-preference cookie. They do not enable, disable or provide a choice about analytics, which is controlled separately through Replit Publishing settings. Before enabling analytics, we will review the applicable lawful basis and any consent requirements. See the Privacy Policy and Replit’s privacy policy for further information.
If we introduce such technologies, we will update this policy and implement any required notices and consent controls before using them.
3. Local and session storage in the workspace
3.1 Local storage
The application uses local storage for some workspace preferences and local caches. Examples include theme and display choices, sidebar layout, dashboard and record-layout settings, radio preferences, notification or dismissed-message markers, and some email-signature settings or draft content.
These uses are distinct from website analytics or advertising. Some stored information may nevertheless be personal or work-related; it should not be assumed that all browser storage contains only anonymous data.
Local-storage entries do not have one shared expiry period. They can remain until the application removes or replaces them, you clear the website’s browser data, or the browser removes them. Some settings also have account-held copies and may be restored when you sign in again.
3.2 Session storage
The application uses session storage to retain temporary workspace context, such as selected projects or campaigns, page filters, the current email tab or mailbox, and navigation between records.
Session storage normally lasts for the browser tab’s session. Browser restore or duplication features can affect how long it remains available. We do not assign every session-storage item a fixed number of hours or days.
3.3 Scope of the cookie controls
The “Essential only” and “Allow sidebar preference” controls manage the optional sidebar-state cookie. They do not switch off all local or session storage used by the workspace, and they do not manage essential authentication cookies.
You can clear or restrict browser storage using your browser’s site-data settings. Doing so may reset preferences, lose locally saved draft content or interrupt a workflow. Clearing browser data does not itself delete the information stored in your Prospexe account or a customer organisation’s records.
4. Managing your choices
Where no valid cookie choice has been saved, the Service presents “Essential only” and “Allow sidebar preference” controls. The dedicated Cookie preferences page presents the controls directly rather than adding a duplicate banner.
You can change the choice at Cookie preferences at any time. Selecting “Essential only” withdraws the optional sidebar-cookie choice and removes that cookie. Withdrawal does not affect the lawfulness of earlier processing based on a valid choice.
These controls do not enable or disable Replit-hosted analytics. Analytics, if enabled, is managed separately through Replit Publishing settings.
The cookie choice is saved in the current browser. A different device, browser or cleared browser profile may require a new choice. The Service may ask again after the saved choice expires.
You can also delete or block cookies and other site data through your browser settings. Blocking cookies needed for authentication can prevent sign-in. Browser settings may apply to other sites as well as Prospexe.
5. Provider services and external websites
Clerk supplies the managed authentication service. Its cookies on the Service must be identified from the active setup, rather than assumed from cookies used on Clerk’s own website or dashboard.
Customer organisations may choose their own email, voice, messaging or other integrations. Cookies or storage on a provider’s independently operated pages are subject to that provider’s own information and controls. The Prospexe sidebar-cookie choice does not manage those external pages.
Any provider cookies or similar technologies actually installed on the Prospexe site must be reflected in the relevant notice and controls where required. This notice does not claim that a complete audit of every customer-selected integration has been carried out.
6. Personal data and privacy
Cookies and browser storage may contain identifiers, preference information, authentication tokens or other personal data. Our Privacy Policy explains our controller processing and the distinction between that processing and Customer Data handled on customer instructions.
For privacy enquiries, contact info@prospexe.co.uk. Requests concerning Customer Data should normally be addressed to the responsible customer organisation.
7. Changes to this policy
We may update this policy when our browser-storage practices, providers or legal requirements change. We will update the date at the top.
Before introducing a new non-essential use that requires consent, we will provide appropriate information and obtain that consent.
8. Contact us
Robert Christopher Link, trading as Prospexe.
Email: info@prospexe.co.uk.