Cookie and storage policy

1. What the website currently uses

The website uses Vercel Web Analytics to produce anonymised aggregate information about page views, routes, referring pages and general device or location characteristics. Vercel states that this service does not use cookies and does not associate the recorded page views with an identifiable visitor. We have not added Google Analytics, advertising pixels or remarketing technology.

The website uses Tally to display the short seller and buyer enquiry forms. Tally stores identifiers in browser local storage when an embedded or standalone form loads. The site also captures first-touch source, entry-page and supplied campaign values in temporary JavaScript memory so they can reach a form after navigation within the website. This memory ends on refresh or another full page load, and session-storage persistence remains disabled in the current launch configuration.

Hosting and security providers may process request information in server logs. Server-side logs are covered by the privacy policy; they are not automatically cookies or browser storage.

2. Technologies identified in the current implementation

• RESPONDENT — Tally local storage: A Tally respondent identifier created when a Tally form loads. It supports operation of the form service. Local storage can remain until it is cleared by the browser, the user or the provider. Tally controls the precise lifecycle of this key.
• FORM_SESSION_xXK0kr — Tally local storage: A form-session identifier for the Confidential Seller Enquiry. It is created by Tally when that embedded or standalone form loads and supports the requested form session.
• FORM_SESSION_QK61Bl — Tally local storage: A form-session identifier for the Confidential Buyer Enquiry. It is created by Tally when that embedded or standalone form loads and supports the requested form session.
• strudwick:first-touch-attribution — Strudwick Capital session storage: Optional storage for source, first landing path and UTM campaign values during a browser-tab session. It is disabled by default. Before a later deployment enables it, Strudwick Capital will reassess the applicable requirements, implement any required user controls and update this policy to describe its use accurately.
• URL attribution values: The first captured source, entry path in originPage and supplied UTM values may be held in temporary page memory and added to a Tally form URL for corresponding hidden fields. This in-memory handling is not browser storage and ends when the document is reloaded or closed. Tally processes the values when the form loads.
• Vercel Web Analytics: A first-party analytics script records anonymised aggregate page-view information. Vercel identifies a visitor for a limited period using a hash derived from the incoming request rather than a cookie, and states that the hash is automatically reset. The service does not write the Strudwick Capital first-touch attribution values to browser storage.

3. Why these technologies are used

The Tally local-storage identifiers are used to provide and maintain the enquiry form session requested by the visitor. The forms may not operate as intended if this storage is blocked. The current implementation treats this form-session storage as necessary for the requested form functionality.

Persistent first-touch attribution is a measurement feature rather than a prerequisite for sending an enquiry. It is therefore disabled by default and is not classified here as strictly necessary. A first-touch set can still be forwarded after client-side navigation using temporary page memory without retaining it in cookies, local storage or session storage.

Vercel Web Analytics is used to understand aggregate website traffic and page use. It operates without analytics cookies and is separate from the first-touch values forwarded to an enquiry form.

4. Embedded and standalone forms

The seller and buyer forms are hosted by Tally and are embedded in this website from tally.so. Loading an embedded form makes a direct connection to Tally. The same form service and storage may be used when you open a standalone form at forms.strudwickcapital.com.

Tally publishes its own privacy and cookie information about its service. Strudwick Capital remains responsible for explaining how it uses enquiry responses and for configuring its forms and providers appropriately.

• Read Tally’s privacy and cookie notice Opens Tally’s website.

5. Your choices

You can clear or block cookies and browser storage in your browser settings. Blocking Tally’s form-session storage may stop an embedded or standalone enquiry form from working correctly. You can instead contact us by email if you prefer not to use the form.

If we later introduce analytics cookies, advertising, remarketing or other non-essential storage, we will update this policy and provide the consent or objection controls required for that technology before enabling it.

• Send an enquiry by email

6. Changes and contact

We may update this policy when the website, forms, providers or legal requirements change. The latest version will be published here with its update date.

Questions about cookies, storage or privacy can be sent to contact@strudwickcapital.com.

• Contact Strudwick Capital about privacy