Privacy Policy

• Name, company, job role, and contact details
• Project requirements, goals, files, links, and business context
• Communication history and support requests
• Billing or administrative information where required
• Whatever you type into a form on this site. It is emailed to the mailbox that handles that kind of message, and a copy is kept as a private entry inside this site’s own database so a delivery failure never loses your message
• Your IP address and the time of the request, written to our web server’s log and, for the admin login page, to a security log that blocks repeated failed attempts
• Which pages you read and how you move through them — but only through the analytics tools in section 06, and only after you have said yes to them

• To respond to enquiries and schedule consultations
• To prepare proposals, roadmaps, estimates, and project plans
• To deliver website, marketing, BPO, branding, automation, or support services
• To maintain security, records, reporting, and service quality
• To improve our website, content, and client experience

We use reasonable technical and organizational safeguards, role-based access, and responsible communication practices. Sensitive project access should be shared only through approved channels.

We do not sell personal information. We may share information with trusted service providers, collaborators, or legal authorities only when necessary to deliver services, support security, or comply with law.

Section 07 lists the companies that receive anything at all, and what each one receives.

You may request access, correction, or deletion of personal information by contacting legal@ovelit.com. Some records may be retained where required for legal, contractual, accounting, or legitimate business reasons.

For cookies and tracking, your choice is the banner you saw on your first visit. You can reopen it at any time from Cookie settings in the footer of any page, and change your answer in either direction.

A cookie is a small file this site, or a service it loads, asks your browser to keep. Two kinds are set here, and they are not treated the same.

Strictly necessary. These keep the site working: your session, the light or dark theme you picked, the security token that protects a form you submit, and one cookie named ovh_consent that remembers the answer you gave the banner. That last one lasts six months, holds nothing but the word granted or denied, and exists so we do not have to ask you again on every page.

Everything else. The four services below are loaded by Google Tag Manager, and none of them — not the script, not the cookie, not a single request to their servers — happens before you choose Accept. Google’s Consent Mode is set to denied in the head of every page before any tag exists, and the Tag Manager container itself is held back until your answer arrives.

• Google Tag Manager (container GTM-5FXB4WFD) — not a measurement tool itself, but the loader that brings in the three below.
• Google Analytics 4 (property G-FYGGKP3BFW) — which pages are read, how visitors move through the site, and where they leave. Cookies _ga and _ga_FYGGKP3BFW, plus _gcl_au where a visit needs to be attributed to an advert.
• Microsoft Clarity — how a page is actually used: mouse movement, clicks, scrolling and rage-clicks, which Microsoft can replay to us as a recording of your session. Cookies _clck and _clsk.
• Meta pixel — tells Meta that a visit happened, so advertising we run on Facebook and Instagram can be measured and audiences built from it. Cookies _fbp and _fbc.

Most of what happens to your information happens on our own server: a copy of your form submission is kept there, security logs are written there, backups are made there. None of that leaves our systems.

The list below is the part that does leave them — the companies that receive something, and what each one receives.

• Our hosting provider stores the site, its database and its backups. Its web server keeps a log of requests, including IP addresses, as every web server does.
• Our email delivery provider receives outgoing mail from the site — form notifications and replies — and delivers it.
• Google, Microsoft and Meta receive the analytics and advertising data described in section 06, and only after you have accepted it.

We hold personal information for defined reasons rather than by default:

Enquiry records are kept while a conversation is active and for a reasonable period afterwards in case you come back to us.

Project records are kept for the life of the engagement and then for the period our accounting and contractual obligations require. Records that no longer serve any of these purposes are deleted.

• To answer an enquiry you sent us, and to follow up on it
• To prepare and deliver work you have engaged us for, under a contract
• To meet accounting, tax and record-keeping obligations that apply to us
• To keep the website and our systems secure
• To send you information you have asked to receive, which you can stop at any time
• To measure how the site is used — and this one, unlike the others, rests entirely on your consent and stops the moment you withdraw it

Depending on where you live, you may have the right to ask us for a copy of the personal information we hold about you, to have it corrected if it is wrong, to have it deleted, to restrict or object to how we use it, and to receive it in a portable format.

When we deliver services that involve your customers’ personal data — support queues, form submissions, CRM records, marketing lists — you remain the controller of that data and we act as your processor.

That relationship is set out in a written data processing agreement signed before any data reaches us, covering what we may do with the data, how it is secured, who else may touch it, and what happens to it at the end of the engagement.

We update this policy when our practices change or when new services introduce new processing. The date at the top of the page shows when it was last revised. Material changes will be described here rather than made silently.

If we ever add a tracking service that is not named in section 06, the banner will ask you again rather than assume your old answer covers it.

This policy describes how we handle information. It is not legal advice, and it does not replace the specific terms of any agreement you have signed with us.

Any question about this privacy policy, or any request to see, correct or delete the information we hold about you, should go to legal@ovelit.com. Please tell us what you are asking for and how you would like us to reply.

We confirm receipt of every request and respond within the timescale the law sets for us. If a request needs identity verification before we can act on it, we will explain exactly what we need and why.

Two mailboxes are published, and both are read every working day:

• General questions, enquiries and support — support@ovelit.com
• Privacy, legal and data requests — legal@ovelit.com