Cookie notice: draft.

This draft covers the cookies and localStorage used by the inspected application source as of 6 October 2026. Cookies accompany relevant requests; localStorage stays in the browser for this site’s origin. Bounded isolated SDK checks have been completed, but they do not verify the public deployment or its complete third-party storage inventory.

Necessary session functions, requested theme and language preferences and optional analytics serve different purposes. Accepting analytics is not required to send an ordinary inquiry or to choose a calendar action. The privacy draft explains server records and conditional providers; this browser inventory does not set their retention periods.

The session cookie is named parxed_session on loopback and __Host-parxed_session on non-loopback origins, with Secure on HTTPS. It contains a random token used for access to private application data and protection of requests. The code sets HttpOnly, SameSite=Lax, Path=/ and no Domain attribute; analytics consent does not control this necessary function. These are source settings, not a production-security certification.

The current session route uses a fixed 24-hour lifetime from creation. Reusing an active session does not renew that deadline; the cookie receives its remaining lifetime. Expiry or removal can end access to session-protected records but does not delete retained inquiries, linked audits, bookings or AI records.

localStorage parxed-theme stores light or dark for your selected appearance. Choosing the system theme removes this key. localStorage parxed-locale stores en, lv or ru after a language-link choice and can restore that preference on a bare-root visit; explicit language and deeper routes remain authoritative. Neither key stores contact details or form messages.

Both preference keys have no application time-based expiry. They remain until removed, replaced or cleared by the browser; that is a description of the code, not an approved indefinite retention policy. Browser site-data controls can clear them and reset the saved choices.

localStorage parxed.analytics.consent stores yes or no for optional analytics. parxed.analytics.ga4-consent.v1 separately stores yes or no for Google-provider analytics. Both have no time-based expiry. Missing or unreadable preferences deny collection. When external analytics is configured, both keys must be yes; an earlier local-only acceptance does not authorize Google. Accepting in the current local-only profile leaves the Google key at no.

With consent, localStorage parxed.analytics.events holds the last 100 event records. This is a count limit, with no age limit or TTL. Events describe actions such as starting an audit, submitting an inquiry, selecting services or changing language. Payloads use limited language, route, service, option and source identifiers, schema version and demo/live mode. They contain no event timestamp, contact or session ID, contact fields, messages, audit text, full URL, query or fragment.

The local analytics sink itself makes no external request, but visitor activity should not be described as anonymous merely because contact fields are excluded. Rejecting or withdrawing writes no to the consent keys and removes the event key when browser writes succeed. Storage failure denies collection on the current page; clearing stored choices requires a fresh opt-in.

The inspected site configuration does not enable Google Analytics 4. If valid configuration is supplied, the application requests Google’s tag only after both analytics consent keys permit it. The adapter disables advertising consent, Google signals and advertising personalization; configuration acceptance requires evidence that Enhanced Measurement is disabled. Bounded isolated SDK checks and saved property settings do not establish acceptance of the final public deployment.

The adapter requests host-only analytics cookies with a parxed prefix, a 180-day lifetime (15,552,000 seconds) and cookie_update:false, so renewal is not requested. The withdrawal code targets parxed_ga and parxed_ga_<measurement-ID suffix>. These are configured or anticipated names and settings, not a verified emitted-cookie inventory. Actual SDK cookies, values, lifetimes and removal need provider testing.

Google may process network and SDK identifiers in addition to the application’s restricted events. The adapter omits query strings, fragments and contact text from authored event parameters; that does not guarantee anonymity. The 180-day cookie setting is not Google Analytics property retention. The owner saved two-month event and user retention and disabled reset on new activity in the selected property. Those account settings do not establish public activation, provider contracts, transfer safeguards or provider-side deletion; those arrangements remain subject to final review.

If configured, Cal.com content loads after an explicit calendar action for a saved request; an external calendar link may also be chosen. Inline loading passes an opaque booking reference and exposes ordinary browser/network metadata. The application does not prefill contact details or audit text, but information you enter directly into Cal is processed there.

Calendar loading and navigation are independent of optional analytics consent. Analytics permission is not general permission for calendar processing or all third-party storage. Cal’s actual cookies, browser storage, attendee fields and retention need separate inventory and review before publication; they have not been verified by this source inspection.

Use the site’s analytics preferences to accept, reject or later withdraw optional analytics. Ordinary inquiries remain available after refusal. These controls concern analytics, not marketing consent. No marketing subscription is offered at launch. You can also clear this origin’s cookies and localStorage in browser settings, which can reset preferences and session access.

Withdrawal stops subsequent application analytics, clears pending analytics commands and attempts to remove local events and the configured Google cookies. Blocked browser writes can prevent storage removal. Withdrawal does not change the lawfulness of consent-based processing before withdrawal, recall completed requests or automatically erase data already held by Google, Cal or another provider.

Production cookies, external SDK behavior and the effect of controls still require verification, alongside the missing facts shown on this page. Contact hello@parxed.co with storage or privacy questions. This remains an unapproved draft; browser clearing does not erase retained server records.