Version 1.2Laatst bijgewerkt 29 August 2026page0-lead-notice-v1

Privacy and Cookie Policy.

1. Who is responsible for your personal data?

TAKTIS is the controller responsible for the processing of personal data described in this Privacy and Cookie Policy.


Trading name: TAKTIS Legal form: Commanditaire vennootschap
Registered office: Emiel Clausstraat 26
Enterprise number:  BE0793564423

Privacy contact: [email protected]

In this policy, "TAKTIS", "we", "us" and "our" refer to the legal entity identified above.

Page0 is the AI-assisted chat, lead-intake and meeting-booking system used on the TAKTIS website.

2. Scope of this policy

This policy explains how we process personal data when you:

  • Visit the TAKTIS website
  • Use the Page0 chat
  • Submit your contact details through Page0
  • Ask us to contact you
  • Request information, a proposal or a discovery call
  • Book a meeting
  • Interact with website analytics after consenting through Cookiebot

This policy also explains how Page0 uses artificial intelligence, how company enrichment works, which cookies are used and how you can exercise your privacy rights.

External websites and services linked from our website may have their own privacy policies. TAKTIS is not responsible for how independent third parties process personal data on their own websites.

3. Privacy at a glance

Page0 has been designed so that its basic functionality works without analytics or marketing consent.

In particular:

  • Page0 does not set a cookie merely because the widget appears on a page.
  • Visitors can use the chat without providing their identity.
  • A strictly necessary session cookie is created only after the visitor sends a first message or opens the booking form.
  • Anonymous chat messages are deleted after 30 days of inactivity.
  • Chat messages are processed by OpenAI to generate responses.
  • A person becomes a lead only after deliberately submitting contact details.
  • Lead information is stored in Page0 and synchronized with our Twenty CRM.
  • Twenty receives an AI-generated summary and a link to the Page0 conversation, not a copy of the complete transcript.
  • Page0 currently enriches company information only.
  • Page0 does not currently perform person-level enrichment.
  • Page0 does not create advertising audiences.
  • Page0 stores campaign attribution only after Statistics consent, and advertising click identifiers only after Marketing consent.
  • Page0 does not subscribe visitors to marketing emails.
  • Page0 does not sell personal data.
  • Page0 does not perform cross-site profiling.
  • Lead scores and classifications are advisory only.
  • No decision producing legal or similarly significant effects is made solely by Page0.

4. Personal data we process and why

4.1 Website delivery and security

When you access our website, our hosting and security infrastructure may process technical information needed to deliver and protect the website.

This may include:

  • IP address
  • Date and time of the request
  • Requested page or resource
  • Browser and device information
  • Error and security logs
  • Information used to prevent abuse, fraud or unauthorized access

We process this information to:

  • Deliver the website
  • Maintain availability and performance
  • Diagnose technical problems
  • Detect malicious or abusive activity
  • Protect our systems and visitors

The legal basis is our legitimate interest in operating a secure and reliable website, under Article 6(1)(f) GDPR. Where processing is necessary to comply with a legal obligation, Article 6(1)(c) GDPR may also apply.

Technical security logs are retained only for the period reasonably necessary for security, incident investigation and legal compliance.

We use Cookiebot, provided by Usercentrics, to:

  • Ask for and record your cookie choices
  • Prevent optional analytics and marketing technologies from loading before consent
  • Allow you to change or withdraw your consent
  • Maintain evidence of consent choices where legally required

Cookiebot may set a strictly necessary cookie or similar identifier to remember your consent selection.

We process this information because it is necessary to comply with our legal obligations regarding cookies and consent. We may also rely on our legitimate interest in documenting and respecting visitor choices.

You can change or withdraw your cookie choices at any time through the Cookiebot privacy control available on the website.

4.3 Loading the Page0 widget

The Page0 embed.js script:

  • Does not load analytics or advertising trackers
  • Does not make unrelated third-party tracking requests
  • Does not set cookies merely because the page loads
  • Does not create a lead merely because the widget is shown
  • Does not start company enrichment merely because the widget is shown

The Page0 widget may therefore load as necessary website functionality before you make a Cookiebot choice.

When you send your first Page0 message or open the booking form, Page0 sets the following cookie:

NameProviderPurposeCategoryDuration
public_session_tokenPage0Maintains the chat or booking session requested by the visitorNecessary24 hours

The cookie is HTTP-only, which means it cannot be read by ordinary browser-side JavaScript.

It is used only to:

  • Maintain the active Page0 session
  • Associate consecutive messages with the correct conversation
  • Complete the booking process
  • Protect the session against unauthorized access

It is not used for:

  • Advertising
  • Analytics
  • Cross-site tracking
  • Long-term visitor profiling
  • Building advertising audiences

The cookie is strictly necessary to provide the chat or booking functionality requested by the visitor. It therefore does not require analytics or marketing consent.

4.5 Anonymous Page0 conversations

You can chat with Page0 without providing your name, email address or other direct contact details.

When you use the chat anonymously, we process:

  • The messages you submit
  • The responses generated by Page0
  • The current conversation context
  • A random session or conversation identifier
  • The page or service context needed to answer your question
  • Minimal technical and security information

We process this information to:

  • Answer questions about TAKTIS
  • Explain our services and Academy offerings
  • Help identify a relevant service or next step
  • Maintain conversational context
  • Prevent misuse and protect Page0
  • Diagnose technical failures

For general informational conversations, the legal basis is our legitimate interest in offering a useful, secure and interactive information service under Article 6(1)(f) GDPR.

Where your conversation concerns a possible project, proposal, service or other commercial engagement, processing may also be necessary to take steps at your request before entering into a contract, under Article 6(1)(b) GDPR.

Anonymous conversations that never become leads are automatically deleted after 30 days of inactivity.

4.6 Use of OpenAI

Page0 uses OpenAI technology to understand messages and generate answers.

When you send a message, the following may be sent to OpenAI:

  • The content of your message
  • Relevant preceding messages
  • Instructions needed to generate an appropriate response
  • Relevant TAKTIS content or service information
  • Personal data that you voluntarily include in the conversation

OpenAI processes this information on our behalf as a service provider under its business terms and data processing arrangements.

We do not use Page0 conversations to train our own general-purpose AI models.

OpenAI states that business and API data is not used to train its models by default unless the customer expressly opts in. OpenAI also provides a data processing addendum covering processor obligations and international transfers.

Please do not submit information through Page0 that is unnecessary for your enquiry, particularly:

  • Passwords or access credentials
  • Payment-card details
  • Government identification numbers
  • Medical information
  • Sensitive employment information
  • Confidential information belonging to another person
  • Special-category personal data unless strictly necessary

4.7 Pseudonymized Page0 usage events

Page0 records a limited set of server-side usage events to maintain and improve the reliability of the service.

These events may contain:

  • A keyed, one-way HMAC hash derived from the IP address
  • Browser family
  • Country code
  • Referring domain
  • Event type
  • Date and time
  • Page or service context
  • Technical success or failure status

These events do not contain:

  • Chat messages
  • Conversation transcripts
  • Names
  • Email addresses
  • Phone numbers
  • Company contact details
  • Enrichment results
  • Advertising click identifiers

The referrer is reduced to the referring domain. Page paths, query strings and potentially sensitive URL parameters are not included as referrer information.

We use these events to:

  • Detect abuse and unusual activity
  • Diagnose failures
  • Measure service reliability
  • Understand aggregate Page0 usage
  • Improve the chat and booking experience

The legal basis is our legitimate interest in securing, monitoring and improving Page0 under Article 6(1)(f) GDPR.

The IP-derived hash is removed after 90 days. The remaining event record is retained for up to 12 months, after which it is deleted or aggregated so that it is no longer linked to an individual session.

These events are not used for advertising or cross-site profiling.

4.8 Submitting an enquiry and becoming a lead

You become an identified lead only when you deliberately submit a Page0 form or otherwise provide contact details and request a follow-up.

We may collect:

  • First name and last name
  • Email address
  • Phone number, if provided
  • Company name
  • Business email domain
  • Job title, if provided
  • Your enquiry or requested service
  • The Page0 conversation
  • Language and timezone
  • Relevant page and campaign context
  • Preferred contact method
  • Requested meeting or next step

Your name and email address are normally required when you ask us to contact you. Phone number, company and job title may be optional unless needed for a specific request.

Without sufficient contact information, we may be unable to:

  • Reply outside the active chat
  • Send a requested proposal
  • Arrange a discovery call
  • Create a meeting invitation
  • Follow up on your enquiry

We process lead data to:

  • Understand your request
  • Respond to your enquiry
  • Assess whether TAKTIS can assist
  • Prepare a proposal or discovery call
  • Maintain the requested business correspondence
  • Avoid asking you to repeat information
  • Manage the potential business relationship

Where you request information, a proposal, a meeting or another step relating to a possible engagement, the legal basis is Article 6(1)(b) GDPR, taking steps at your request before entering into a contract.

We also rely on our legitimate interest under Article 6(1)(f) GDPR to manage genuine inbound business enquiries, maintain relevant CRM records and organize follow-up communication.

4.9 Page0 storage and Twenty CRM

When you submit an enquiry, the following is stored in Page0:

  • Contact details
  • Full Page0 conversation
  • Lead status
  • Relevant company information
  • Booking information
  • Enrichment results
  • Audit and processing metadata

Page0 sends the following to our Twenty CRM:

  • Contact details
  • Company details
  • An AI-generated summary of the enquiry
  • Service interest
  • Relevant lead status and attribution information
  • A link back to the Page0 conversation

The raw Page0 conversation transcript is not copied into Twenty CRM.

Authorized TAKTIS users can follow the CRM link to review the conversation in Page0 where necessary to understand or respond to the enquiry.

AI-generated summaries may contain errors or incomplete interpretations. They are treated as working notes and may be corrected by our team or at your request.

4.10 Follow-up communication

We may use the contact information you provide to send communications directly related to your enquiry, such as:

  • A response to your question
  • A requested proposal
  • Additional information about the service you asked about
  • Meeting invitations
  • Scheduling updates
  • Clarifying questions
  • Operational follow-up concerning the requested service

These are enquiry-related or pre-contractual communications. They are not treated as general marketing subscriptions.

Page0 does not currently contain a newsletter or promotional email opt-in. Submitting an enquiry does not subscribe you to marketing emails.

Accepting Cookiebot marketing cookies also does not subscribe you to marketing emails.

4.11 Company enrichment

After you submit an identified business enquiry, Page0 may supplement the information you provide with relevant publicly available information about your company.

The company information may include:

  • Company name
  • Official website and domain
  • Industry
  • Company description
  • Approximate company size
  • Headquarters or business location
  • Publicly described products or services
  • Other relevant company context needed to understand the enquiry

The information is obtained using the company name, company website or business email domain provided by you.

Sources may include:

  • The company's official website
  • Public company registers
  • Publicly accessible business directories
  • Public company profiles
  • Other reputable public business sources

We use company enrichment to:

  • Verify which company the enquiry concerns
  • Better understand the company's activities
  • Route the enquiry to the appropriate service
  • Prepare a more relevant response
  • Reduce unnecessary follow-up questions
  • Assess whether TAKTIS is likely to be able to assist

The legal basis is our legitimate interest under Article 6(1)(f) GDPR in understanding and responding efficiently to genuine inbound B2B enquiries.

The enrichment is limited to information relevant to the professional enquiry. It is not used to make decisions producing legal or similarly significant effects.

You may object to company enrichment by contacting us through the privacy address identified in this policy.

4.12 Person-level enrichment is currently disabled

Page0 does not currently enrich individual leads with:

  • Public LinkedIn profiles
  • Inferred seniority
  • Professional biographies
  • Additional role information from third-party sources
  • Personal social-media information
  • Private contact details

Page0 currently performs company-level enrichment only.

We will update this Privacy Policy and the Page0 first-layer notice before enabling person-level enrichment.

We will not use person-level enrichment merely because the current first-layer notice is broad enough to mention it. The public policy and actual product configuration must remain aligned.

4.13 Booking a meeting

When you use Page0 to book a meeting, we may process:

  • Name and email address
  • Company and job title, if provided
  • Timezone
  • Selected date and time
  • Meeting subject
  • Relevant conversation or enquiry summary
  • Calendar availability
  • Meeting link
  • Booking status

The information is used to:

  • Display suitable availability
  • Create the requested meeting
  • Send a calendar invitation
  • Notify the relevant TAKTIS representative
  • Manage rescheduling or cancellation
  • Diagnose failed booking attempts

Depending on the relevant TAKTIS representative, the meeting may be created using:

  • Microsoft 365 or Outlook Calendar
  • Google Calendar

The legal basis for creating and administering the requested meeting is Article 6(1)(b) GDPR.

Technical information about failed booking attempts is processed based on our legitimate interest in diagnosing booking failures and maintaining a reliable service.

Failed booking-attempt logs are deleted after 90 days.

4.14 Website analytics

We use Google Analytics 4 and Microsoft Clarity only after you consent to the Cookiebot Statistics category.

Google Analytics 4

Google Analytics may process information such as:

  • Online and cookie identifiers
  • Approximate location
  • Device and browser information
  • Pages visited
  • Referral and campaign information
  • Website events
  • Session and engagement information

We do not intentionally send Page0 messages, names, email addresses, phone numbers or complete lead-form data to Google Analytics.

The legal basis is your consent under Article 6(1)(a) GDPR.

Our Google Analytics user-level and event-level retention setting is configured to 14 months. Google currently allows standard GA4 properties to be configured for two or fourteen months of user-level and event-level retention.

Microsoft Clarity

Microsoft Clarity helps us understand how visitors interact with the website by providing information such as:

  • Click and scroll behaviour
  • Device and browser information
  • Navigation patterns
  • Session recordings
  • Heatmaps
  • Technical interaction signals

Page0 message content, Page0 forms, contact details and other sensitive input fields must be masked or excluded from Clarity collection.

The legal basis is your consent under Article 6(1)(a) GDPR.

Microsoft currently retains Clarity playback data for 30 days, while click, heatmap and certain labelled or retained session data may be kept for up to nine months.

Under Belgian guidance, analytical cookies require prior consent, including when they are first-party analytics cookies.

4.15 Campaign attribution and advertising click identifiers

When you consent to the Cookiebot Statistics category, Page0 may record how your visit reached our website and attach that context to an enquiry you later submit:

  • Campaign parameters in the page address (utm_source, utm_medium, utm_campaign, utm_content, utm_term and our own campaign identifiers)
  • The first page of your visit
  • The domain of the referring website

This attribution is held in your browser session only and is stored on our systems exclusively as part of an identified lead, at the moment you deliberately submit your contact details. Anonymous visitors leave no attribution data on our systems. We use it to understand which channels and campaigns produce genuine enquiries.

When we run advertising campaigns and you consent to the Cookiebot Marketing category, the same mechanism may additionally capture advertising click identifiers (gclid, gbraid, wbraid, fbclid, li_fat_id, msclkid). These identifiers are assigned by the advertising platform when you click an advertisement. We use them to:

  • Attribute an enquiry to the specific advertising campaign that produced it
  • Measure and report the effectiveness of our advertising
  • Report a resulting conversion back to the advertising platform concerned (for example Google Ads, LinkedIn or Meta) so campaigns can be evaluated and optimized

The legal basis for both is your consent under Article 6(1)(a) GDPR. You can withdraw consent at any time through the Cookiebot privacy control; withdrawal stops new collection and removes attribution held in your browser. Attribution already attached to a submitted enquiry follows the retention of that lead.

Click identifiers are not used to build advertising audiences, are not combined with data from other websites, and are not synchronized to our CRM.

5. Where personal data comes from

We obtain personal data from the following sources.

Directly from you

This includes:

  • Messages you submit
  • Contact details
  • Company information
  • Job title
  • Meeting preferences
  • Information included in your enquiry
  • Corrections or updates you provide

Generated through your interaction

This includes:

  • Session and conversation identifiers
  • Technical logs
  • Pseudonymized usage events
  • Page and service context
  • Booking status
  • AI-generated summaries
  • Lead classifications

Public company sources

After you become an identified business lead, we may obtain relevant company information from public sources, as described under company enrichment.

Service providers

Booking and communication providers may return information such as:

  • Calendar availability
  • Meeting creation status
  • Delivery or booking errors

Analytics providers

When you consent, Google Analytics and Microsoft Clarity provide website usage and interaction information.

6. Our legitimate interests

Where we rely on Article 6(1)(f) GDPR, our legitimate interests include:

  • Operating a secure and reliable website
  • Providing an interactive Page0 information service
  • Preventing fraud and misuse
  • Responding to genuine inbound business enquiries
  • Managing B2B contacts and potential opportunities
  • Understanding the company making an enquiry
  • Avoiding duplicate or irrelevant follow-up questions
  • Improving service reliability
  • Establishing, exercising or defending legal claims

We limit this processing by:

  • Allowing anonymous chat
  • Starting enrichment only after deliberate lead submission
  • Restricting enrichment to company information
  • Avoiding sensitive personal data
  • Avoiding advertising uses
  • Avoiding marketing subscriptions
  • Applying retention periods
  • Providing an objection mechanism
  • Keeping human oversight over lead scoring and qualification

Legitimate interest is a permitted GDPR legal basis only when the processing is necessary and the controller's interests are not overridden by the individual's rights and freedoms.

7. Who receives personal data?

Personal data may be accessed or processed by the following recipients.

Authorized TAKTIS personnel

Authorized TAKTIS staff and contractors may access data where necessary to:

  • Answer enquiries
  • Prepare proposals
  • Arrange meetings
  • Manage the CRM
  • Maintain Page0
  • Investigate security incidents
  • Handle privacy requests

Access is limited according to role and operational need.

OpenAI

OpenAI processes conversation content and relevant context to generate Page0 responses.

Twenty CRM

Our Twenty CRM environment stores identified contacts, company information, lead information, AI-generated summaries and links to Page0 conversations.

Hosting and infrastructure providers

Our website, Page0, databases, backups and related services may be hosted or supported by selected infrastructure providers.

Email provider

Our email provider processes contact and message information when we send or receive communications relating to your enquiry.

Calendar providers

Google or Microsoft may process meeting information when a meeting is scheduled using their calendar services.

Cookiebot

Usercentrics processes consent and cookie-management information through Cookiebot.

Analytics providers

When you consent:

  • Google processes Google Analytics information.
  • Microsoft processes Microsoft Clarity information.

Professional advisers and authorities

We may disclose information to:

  • Legal advisers
  • Accountants or auditors
  • Insurers
  • Courts
  • Regulators
  • Law-enforcement authorities

We do this only where necessary to comply with law, protect our rights or respond to a valid legal request.

We do not sell personal data.

8. International transfers

Some service providers may process personal data outside the European Economic Area.

Where personal data is transferred to a country that has not been recognized as providing an adequate level of protection, we use appropriate safeguards where required, such as:

  • European Commission adequacy decisions
  • European Commission Standard Contractual Clauses
  • Contractual data-protection obligations
  • Technical and organizational safeguards
  • Transfer-risk assessments where appropriate

OpenAI's data processing addendum includes processor terms and Standard Contractual Clause arrangements for relevant international transfers.

You may contact us for additional information about the transfer safeguards applicable to your personal data.

9. Retention periods

We retain personal data only as long as necessary for the relevant purpose.

DataRetention
public_session_token24 hours
Anonymous Page0 conversation that does not become a lead30 days after inactivity
IP-derived HMAC hash in Page0 usage events90 days
Remaining Page0 usage event data12 months
Failed booking-attempt logs90 days
Identified lead, Page0 conversation, AI summary and company enrichment24 months after the last substantive interaction
Successful booking information in Page0Same retention as the associated lead
Campaign attribution and advertising click identifiers on an identified leadSame retention as the associated lead
Google Analytics user-level and event-level data14 months
Microsoft Clarity playback data30 days
Microsoft Clarity click and heatmap dataUp to 9 months
Cookiebot consent informationAccording to the Cookiebot configuration and the period necessary to document consent
Minimal privacy-request and deletion audit recordFor the period necessary to demonstrate compliance and handle legal claims

A substantive interaction includes, for example:

  • A reply to an enquiry
  • A discovery call
  • A proposal
  • A meaningful follow-up
  • A renewed request
  • A project discussion

Routine automated messages do not automatically restart the lead-retention period.

If a lead becomes a customer, information required for the customer relationship, invoicing, accounting, contractual obligations or legal claims may be retained under separate customer and statutory retention periods.

We may delete information earlier when:

  • It is no longer necessary
  • The enquiry is clearly irrelevant or invalid
  • You successfully exercise a right to erasure or objection
  • The information is inaccurate and cannot be corrected
  • Continued processing is no longer lawful

We may retain limited information for longer where required by law or necessary to establish, exercise or defend legal claims.

10. Deleting a Page0 lead

When an identified lead is permanently deleted from Page0, the operational deletion process removes:

  • The lead record
  • Contact details
  • Conversation
  • Messages
  • Enrichment data
  • Booking logs linked to the lead
  • Associated operational records, except minimal compliance audit information

A corresponding record in Twenty CRM must also be permanently deleted where erasure applies.

Moving a Twenty record to the CRM trash is not treated as completed erasure. The record must be permanently removed from the trash where a valid erasure request requires permanent deletion.

We may retain a minimal audit entry showing:

  • That a deletion request was received
  • When it was completed
  • Which systems were addressed
  • Whether a legal exception applied

The audit entry does not retain the deleted conversation or enrichment profile.

11. What Page0 does not do

Page0 does not currently:

  • Create advertising audiences
  • Send lead information to advertising platforms, beyond the consent-based conversion reporting described in section 4.15
  • Store advertising click identifiers without Marketing consent (section 4.15)
  • Subscribe leads to a newsletter
  • Send unrelated promotional emails
  • Sell personal data
  • Trade personal data
  • Perform cross-site tracking
  • Build consumer-interest profiles
  • Perform person-level lead enrichment
  • Use private social-media information
  • Intentionally process sensitive personal data for lead qualification
  • Make decisions with legal or similarly significant effects solely by automated means

Page0 may calculate an advisory lead score or classification. This helps organize follow-up but does not automatically determine:

  • Whether TAKTIS will work with you
  • The price you receive
  • Your eligibility for a service
  • Whether a proposal is issued
  • Any contractual or legal outcome

A human remains responsible for material business decisions.

12. Your privacy rights

Depending on the circumstances, you have the right to:

  • Ask whether we process your personal data
  • Obtain access to your personal data
  • Receive a copy of relevant personal data
  • Correct inaccurate or incomplete data
  • Request deletion
  • Request restriction of processing
  • Object to processing based on legitimate interests
  • Object specifically to company enrichment
  • Withdraw consent for analytics cookies
  • Receive portable data where the portability right applies
  • Lodge a complaint with a supervisory authority
  • Obtain human review where a qualifying automated decision would otherwise apply

Withdrawing consent does not affect processing that was lawful before withdrawal.

The right to deletion is not absolute. We may retain limited information where required for:

  • Legal obligations
  • Fraud or security investigations
  • Establishing, exercising or defending legal claims
  • Documenting that an objection or deletion request was honored

We normally respond to a privacy-rights request within one month. Where a request is particularly complex or numerous, the GDPR may allow an extension of up to two additional months, provided that we inform you within the first month.

We may ask for information reasonably necessary to verify your identity before giving access to or deleting personal data.

To exercise a right, contact:

[PRIVACY EMAIL ADDRESS]

Please include enough information for us to identify the relevant Page0 conversation, lead or CRM record. Do not send a copy of an identity card unless we specifically request it and explain why it is necessary.

13. Complaints

Please contact us first so that we can investigate and address your concern.

You also have the right to contact or lodge a complaint with the Belgian Data Protection Authority:

Belgian Data Protection Authority Rue de la Presse 35 / Drukpersstraat 35 1000 Brussels Belgium Email: [email protected]

The Belgian Data Protection Authority provides a formal complaint procedure for individuals who believe that their personal data has been processed unlawfully.

14. Security

We use appropriate technical and organizational measures intended to protect personal data against:

  • Unauthorized access
  • Accidental loss
  • Improper alteration
  • Unauthorized disclosure
  • Misuse
  • Destruction

Measures may include:

  • Restricted access
  • Authentication and authorization controls
  • Encryption in transit
  • Logging and audit trails
  • Data minimization
  • Retention controls
  • Backup and recovery procedures
  • Separation of public chat, enrichment and CRM functions
  • Review of third-party service providers

No internet service can guarantee absolute security. Please avoid submitting information that is not needed for your enquiry.

15. Cookies and similar technologies

Cookies are small data files stored or accessed on a device.

We divide cookies and similar technologies into the following Cookiebot categories:

Necessary

Technologies required to:

  • Deliver the website
  • Remember cookie choices
  • Protect website security
  • Maintain a Page0 session requested by the visitor
  • Complete a meeting booking requested by the visitor

Necessary technologies cannot be switched off through the cookie banner when they are genuinely required to provide the requested service.

Preferences

Technologies used to remember optional visitor choices, such as language or display preferences.

Page0 does not currently use an optional long-term preference cookie.

Statistics

Technologies used to understand website usage, including:

  • Google Analytics 4
  • Microsoft Clarity

These are activated only after statistics consent.

Marketing

Technologies used for advertising, remarketing or cross-site measurement.

With Marketing consent, advertising technologies may be used for campaign measurement: Page0 may store advertising click identifiers as described in section 4.15, and advertising tags (for example Google Ads, the LinkedIn Insight Tag or the Meta pixel) may load through our tag manager. None of these load before Marketing consent.

Other parts of the TAKTIS website may use marketing technologies in the future only after the relevant Cookiebot consent and an update to this policy and the live Cookie Declaration.

Belgian guidance states that analytical cookies generally require prior consent, while strictly necessary cookies may be used where genuinely needed to provide a service requested by the visitor.

The Cookiebot Cookie Declaration displayed below lists the cookies and trackers currently detected on the website, including:

  • Cookie name
  • Provider
  • Purpose
  • Expiry
  • Type
  • Cookiebot category

The declaration also allows you to inspect, change or withdraw your current cookie choice.

[EMBED COOKIEBOT COOKIE DECLARATION HERE]

Cookiebot's declaration is automatically updated based on its website scans and can be embedded in an existing privacy policy or placed on a dedicated cookie page.

17. Current Page0 cookie entry

The Page0-specific entry that should appear in Cookiebot is:

FieldValue
Namepublic_session_token
ProviderPage0
CategoryNecessary
PurposeMaintains the chat or booking session deliberately started by the visitor
TriggerFirst submitted chat message or opening of the meeting-booking form
Expiry24 hours
TypeHTTP-only session cookie
Tracking useNone
Advertising useNone
Analytics useNone

Suggested Cookiebot description:

Maintains the Page0 chat or booking session started by the visitor. The cookie is created only after the visitor sends a first message or opens the booking form. It expires after 24 hours and is not used for analytics, advertising or cross-site tracking.

18. Page0 first-layer privacy notice

The following notice should be displayed immediately before a visitor submits identifying contact details.

page0-lead-notice-v1

By sharing your business contact details, you ask TAKTIS to respond to your enquiry. We will store your details and conversation in Page0 and record your contact details, an AI-generated summary and a link to the conversation in our CRM. We may supplement the information you provide with relevant publicly available information about your company so that we can better understand and follow up your request. Read our Privacy Policy for more information about the data we use, retention, recipients and your rights.

The notice must:

  • Be visible before submission
  • Link to this policy
  • Be available in the language of the Page0 interface
  • Not contain a preselected marketing checkbox
  • Not state that the visitor "agrees" to all processing
  • Record the notice version shown to the lead

If person-level enrichment is enabled in the future, the first-layer notice must be revised and assigned a new version before the feature is activated.

19. Changes to this policy

We may update this policy when:

  • Page0 functionality changes
  • New service providers are introduced
  • Retention periods change
  • Person-level enrichment is enabled
  • Advertising or marketing functionality is introduced
  • Legal or regulatory requirements change

The current version and effective date will be published at the top of this page.

Material changes may also be communicated through the website, Page0 interface or another appropriate channel.

20. Contact

Questions about this policy or our processing of personal data can be sent to:

TAKTIS [LEGAL ENTITY NAME] [REGISTERED ADDRESS] [ENTERPRISE NUMBER] [PRIVACY EMAIL ADDRESS]