Privacy policy

Last updated: 2 November 2026

This policy explains how Traffic Architect handles personal information when you visit trafficarchitect.com, contact us or follow a link to book a call.

Who is responsible for your information

The website operator and contact details are:

Traffic Architect
Kleine Dreef
Belgium
Website: https://trafficarchitect.com
Email: hamid@trafficarchitect.com
Phone number: +32498474694

Use the privacy contact above for questions or requests about your information.

Information we process and why

• Website delivery and security. Our hosting and security systems process connection information, such as IP addresses, requested pages, request times and browser information, to deliver the website, investigate faults and prevent abuse. We rely on our legitimate interests in operating and protecting the site.
• Enquiries and bookings. If you contact us or arrange a call, we process the contact details and information you provide to respond and organise the conversation. Depending on the request, this is to take steps you request before a contract or for our legitimate interests in handling business enquiries.
• Optional analytics. With statistics consent, we use analytics cookies and interaction data to understand which pages and workflows visitors find useful. Consent is the basis for optional analytics cookies and our custom interaction events.
• Privacy choices and limited measurement. We remember and communicate your consent choice. The current Google Consent Mode configuration also sends limited cookieless measurement signals, described below. We rely on our legitimate interests in administering privacy preferences and understanding aggregate website use for this limited processing. You may object by contacting us.
• Legal requests. We process information where necessary to meet applicable legal obligations or establish, exercise or defend legal claims.

Google Analytics, Tag Manager and Search Console

Google Analytics 4 (GA4) measures website use. Depending on your consent and browser, measurement can include pages and page titles, traffic sources, approximate location, device and browser information, session information and cookie-based identifiers. These identifiers can distinguish visits and are not treated as completely anonymous.

Enhanced measurement is enabled for supported interactions such as outbound links and PDF downloads. Our additional events are booking_click, with the position of the clicked booking link, and workflow_example_select, with the selected homepage example. These custom events send the page path and predefined labels, rather than form contents. A booking-link click is not a confirmed appointment or qualified opportunity.

Google Tag Manager (GTM) deploys the configured tags. Its current Traffic Architect interaction listener sends the two custom events only when statistics consent is allowed. The legacy Datafa.st, LinkedIn Insight, RB2B and Vector tags in this container are paused. Google signals and user-provided data collection are not enabled in the GA4 property. Logged-in WordPress users are excluded from GA4 measurement.

Google Search Console supplies search-performance and indexing reports and is linked to the GA4 web stream. This connection does not place an additional Search Console measurement tag on the website.

Important: Deny does not block every request to Google. Google Consent Mode is currently used in its advanced configuration. When analytics storage is denied, Google may still receive cookieless signals containing consent state and basic visit or technical information, including browser information, screen resolution and an IP address involved in the connection. Google can use these signals for measurement and modelling. Optional analytics cookie storage is denied and our two custom events stop; this is different from preventing all Google network requests. See Google’s consent mode reference.

Google states that, for EU, UK and Swiss traffic, Analytics uses IP addresses to derive geographic information and then discards them before logging the measurement data. This does not mean that an IP address is never transmitted during the connection. See Google’s regional data and privacy information.

Cookies and your choices

Complianz and the WP Consent API manage choices on this WordPress site. Necessary consent cookies remember your decision; statistics cookies support optional analytics. Google Analytics uses cookies such as _ga and stream-specific _ga_* cookies. Google’s cookie documentation explains their purposes and standard lifetimes. Our Cookie policy explains the site’s consent controls.

Choose Accept or Deny in the popup. The popup closes after either choice and the decision is remembered for up to 365 days. It may be requested again if you clear cookies, use another browser or device, or a consent update is required.

There is no floating consent tab. Use Cookie preferences in the website footer to reopen the choices, change statistics consent or withdraw it. The footer control is available on desktop and mobile. Withdrawal affects future consent-based processing; it does not change the lawfulness of earlier processing. Cookies already stored can remain until they expire or you remove them through your browser, even when their use has been disabled.

Providers, external links and international processing

Authorised people operating Traffic Architect and providers supporting hosting, security, measurement and scheduling can process relevant information. This website uses Hostinger for hosting and Google services for the measurement described above. We may also disclose information where legally required or necessary to handle a legal claim.

The booking buttons lead to Google Calendar. If you follow a booking link, information you submit to that service is also handled under its privacy terms. External services such as LinkedIn have their own privacy policies.

Google operates internationally, so data may be processed outside your country, including in the United States. Google’s international transfer information describes the frameworks and contractual safeguards it uses where applicable. You can also read Google’s privacy policy, its information about data from partner sites and Hostinger’s privacy policy. Contact us for further information about processing relevant to your request.

How long information is kept

The current GA4 property retains event-level data for two months and user-level data for 14 months. Its reset-on-new-activity setting is enabled, so subsequent activity can refresh the user retention period. These controls do not apply to most standard reports based on aggregated data. Cookie lifetimes are separate from Analytics report retention.

Consent preferences are remembered for up to 365 days. We retain enquiries, booking correspondence and related business records for as long as needed to handle the request or relationship, and longer where applicable legal obligations or legal claims require it. Technical records are retained according to their operational and security purpose and the relevant provider settings.

Your rights and how to contact us

Depending on applicable law and the circumstances, you can request access, correction, deletion, restriction or portability of your personal information, object to processing based on legitimate interests, and withdraw consent. Use the privacy contact at the top of this page. We may ask for information needed to verify the request and locate relevant records; do not send passwords or sensitive account credentials.

You can also complain to a competent data protection authority, including the authority where you live or work or where you believe an infringement occurred. The European Data Protection Board’s authority directory lists EEA authorities.

Changes to this policy

We update this page when the website’s processing changes. The date above identifies the latest revision. Where a change requires a new consent choice, we will ask for it through the consent controls.