Cookie Policy

1. Scope

This Cookie Policy explains how WE AS WEB S.R.L. uses cookies and similar technologies on https://weasweb.com. It should be read with the Privacy Policy.

“Cookies” are small files stored by a browser. Similar technologies include local storage, software development kits, pixels, and identifiers that store information on or access information from a device. This Policy uses “cookies” as a convenient collective term unless a distinction matters.

2. Our consent rule

Strictly necessary technology may operate without analytics consent only where it is genuinely necessary to deliver the Website, protect it, or remember a privacy choice requested by you.

Analytics is optional. The PostHog analytics library, requests, identifier, storage, and event capture do not start until you make an affirmative “Accept analytics” choice. Continuing to browse, scrolling, silence, closing a banner, accepting the Terms, or using a pre-ticked control is not consent.

The first layer of the cookie notice provides equally prominent ways to accept or reject analytics. A settings view explains the category and provider. Refusing analytics does not block Website content or the contact form.

3. Technologies we use

3.1 Strictly necessary preference record

Name or key

waw_cookie_consent

Provider

WE AS WEB S.R.L.

Purpose

remember whether analytics was accepted or rejected, the notice version, and the time of the choice; apply that choice; and avoid asking on every page.

Data

category choice, timestamp, version, and a limited preference identifier where necessary.

Duration

up to 180 days, unless deleted sooner or reset because the notice or purpose materially changes.

Category

strictly necessary. It does not itself enable PostHog analytics and is not used for advertising.

3.2 PostHog first-party analytics record — only after consent

Name or key

a first-party PostHog persistence record using the key pattern ph_<project_token>_posthog, held in both browser local storage and a first-party cookie.

Providers

WE AS WEB S.R.L. as controller; PostHog as processor.

Purpose

assign a random pseudonymous browser identifier so consented page views and selected events can be counted without identifying the visitor by name or contact details.

Data

pseudonymous identifier and limited analytics state. Contact-form values and identifiable person profiles are excluded.

Duration

up to 180 days, subject to earlier deletion or reset when you withdraw, clear browser data, or use a blocking control.

Category

analytics; off by default and used only after consent.

3.3 PostHog analytics requests — only after consent

Provider endpoint

PostHog Cloud EU, hosted in Frankfurt, using the EU ingestion endpoint configured for the project.

Library delivery

the PostHog analytics library is bundled into this Website and served from weasweb.com, not fetched from a third-party content-delivery network. If you reject analytics, or before you choose, your browser makes no request to PostHog or any other analytics host at all.

Purpose and data

the consented page views described in Section 3.5 of the Privacy Policy.

Retention

raw events up to 12 months; longer-lived statistics only after they no longer identify or single out a visitor.

Category

analytics; off by default and used only after consent.

4. Analytics features that are not approved

Under this Policy, WE AS WEB does not approve or enable PostHog autocapture, session replay, heatmaps, surveys, automatic exception or error capture, form capture, element-text capture, advertising tracking, cross-site tracking, identifiable person profiles, identify calls, or enrichment that joins analytics to contact-form or CRM data.

We also do not approve raw IP retention or GeoIP enrichment for Website analytics. Any later proposal to enable a new feature requires a documented assessment, data minimization, an updated inventory and notice, and a new choice where law requires it.

Analytics events are additionally filtered in your browser before they are sent, against a fixed list of the fields set out in Section 3.5 of the Privacy Policy. Anything outside that list is removed rather than transmitted. That filter specifically removes advertising and click-tracking identifiers that other websites commonly collect — for example Google, Meta, Microsoft, LinkedIn, TikTok, Reddit, and similar click IDs — together with campaign parameters and the full browser user-agent string, none of which we collect or use. Because the filter works from a fixed list rather than a list of exclusions, a future version of the analytics software cannot quietly introduce a new field into what we collect.

5. How to make or change a choice

On the first eligible visit, use “Accept analytics” or “Reject analytics” in the cookie notice. You may also open the detailed settings before choosing.

At any time, open “Cookie Settings” in the Website footer to review or change the choice. Switching analytics off will stop future capture and clear or reset the PostHog analytics identifier and related analytics storage under our control. A strictly necessary record may remain to remember the rejection and prevent analytics from restarting.

You can also delete cookies or local storage through browser settings. If you delete the preference record, the Website may ask again. Browser controls can block more broadly, but some settings may also remove necessary preferences or affect unrelated websites.

6. Legal basis

For optional analytics storage or access on a device, we rely on prior consent under Article 5(3) of Directive 2002/58/EC as implemented by Article 4(5) of Romanian Law no. 506/2004. For the related processing of personal data, we rely on consent under Article 6(1)(a) GDPR.

The strictly necessary preference record is used only to provide and remember the privacy choice you requested and to support compliance. It is not repurposed for analytics, advertising, or profiling.

7. Renewal and proof of consent

We will ask again after the preference expires or sooner if the analytics purpose, provider, data categories, or technology changes materially. We may retain a minimal record of a consent or withdrawal for the period described in the Privacy Policy to demonstrate compliance and honor the choice. That record does not authorize analytics after withdrawal.

8. Changes to this Policy

We will update this Cookie Policy and the live inventory when relevant technology, purposes, providers, or retention periods change. A material expansion of optional tracking will not be activated on the basis of an earlier consent that is no longer specific or informed.

9. Contact

Questions or requests about cookies and analytics may be sent to: