QuotifyYour browser and choices
Cookies & browser storage
Updated 11 November 2026
The storage and measurement used by Quotify’s marketing website, and what you can control in your browser.
What this page covers
This notice covers yourquotify.com, Quotify’s marketing website. Cookies store small values in your browser; local storage and session storage can hold similar information. The rules and your choices concern all of these technologies, not only files called cookies.
The separate application at app.yourquotify.com also uses storage for sign-in, account features and measurement. Its full service privacy policy provides more information.
Your available controls
Some marketing pages load analytics and advertising measurement when they open. The marketing website currently has no site-wide cookie settings panel. These Privacy and Cookies pages do not load those measurement scripts.
You can restrict cookies and other storage through your browser and use its tracking protections. Browser controls can limit collection, but blocking third-party cookies alone does not block every first-party identifier or measurement request.
- Manage cookies and site data in Chrome.
- Clear cookies and site data in Firefox.
- For Safari, use the browser’s Privacy settings and Manage Website Data controls.
To remove stored marketing-site identifiers, clear site data for yourquotify.com, including cookies and local storage. Removing shared domain cookies may also affect the application. Clearing storage does not delete information already received by Quotify or a measurement provider, and scripts can recreate storage on a later visit unless your browser blocks it.
For information already received by us, or to object to its use, email Reuben@yourquotify.com. Reading this notice or continuing to browse is not consent.
Cookies and browser storage in the marketing website
The following names and lifetimes are identified in the website’s deployed code. They may be present only after a particular page or action. A cookie’s stated lifetime is a maximum set by the code; browser limits and clearing site data can shorten it.
| Name or pattern | Purpose and category | Storage and duration |
|---|---|---|
qfy_attr | Campaign parameters and advertising click identifiers used when moving to signup. Advertising attribution. | First-party cookie; 90 days. |
quotify_visitor_id | Recognise the same browser for website journey measurement. Analytics. | First-party cookie; 400 days. |
quotify-visitor-id-v1 | Store the website visitor identifier. Analytics. | Local storage; no automatic expiry in the deployed helper. |
quotify-attribution-v2 and quotify-first-page-visited-v1 | Record campaign/referrer and first-page information. Analytics and advertising attribution. | Local storage; no automatic expiry in the deployed helper. |
quotify-journey-created-v1:* and quotify-google-conversion-v1:* | Avoid duplicate website journey or conversion reports. Analytics / advertising measurement. | Persistent browser flags; no automatic expiry in the deployed helper. |
_prism_vid | DPOM Nebula visitor identifier. Website/campaign measurement. | Local storage; no automatic expiry in the deployed script. |
_prism_sid and _prism_exp | DPOM Nebula session identifier and expiry. Website/campaign measurement. | Local storage; the script writes a 30-minute session-reuse deadline. Stored keys are not automatically deleted. |
Local storage persists until removed by the site, your browser or you; it does not have a cookie-style automatic expiry. Some integration-specific duplicate flags can also use session storage, which normally ends with the browsing session.
Measurement services
Different marketing pages load different integrations. Existing homepage integrations include Google Analytics / Google Ads, PostHog and DPOM measurement. The names above describe Quotify and DPOM storage identified in the code; they are not an exhaustive list of values a vendor SDK may create in every browser.
| Service | Information and purpose |
|---|---|
| Google Analytics / Firebase Analytics and Google Ads | Measure visits, interactions and campaign/conversion activity. Google tags may use identifiers with names such as _ga* and _gcl*. Availability and lifetime depend on the tag configuration and browser. See Google’s privacy information. |
| PostHog | Measure website visits and interactions. Its configuration includes page-leave and interaction measurement, heatmaps and session recording capability; actual recording depends on the service configuration. PostHog can use browser identifiers with the ph_* pattern. Its website integration sends usage information to PostHog’s EU ingestion endpoint; that endpoint alone does not mean every part of processing stays in the EU. |
| DPOM Sentinel and Nebula | Website and campaign measurement, including page URLs, referrers, browser/device information and visit or interaction data. Nebula code also supports interaction heatmaps and session recording. |
Ad click identifiers and campaign parameters can arrive in the address of a landing page. A script can read these even if third-party cookies are blocked. Some measurement runs through network requests as well as browser storage.
The separate account and project application
The application has its own sign-in and feature storage. Its privacy policy lists sign-in session cookies, display preferences and analytics/advertising identifiers. Clearing or blocking necessary application storage can sign you out or stop account features working. Read the full service privacy policy before using those controls.
Website browser controls do not delete account records or reverse server-side reports already sent to another service. For account and project data requests, the full service policy gives hello@yourquotify.com.
Questions and updates
Quotify is operated by APEXSGMC LIMITED. For a question about marketing-site cookies or personal information, email Reuben@yourquotify.com. Our Privacy notice explains the organisation, enquiry data and your rights.
We will update this notice when the marketing website’s integrations or controls change. The date above identifies this version.