Centralux
ENTRY 05 · COVENANT OF PRIVACY FOLIO 05 OF 06

Covenant of Privacy

This is a website with no accounts, no shop, no forms and no analytics. Almost everything below is a description of things that do not happen — which is the point, and which is why it is short enough to read.

EFFECTIVE 27 AUGUST 2026/ CENTRALUX AI LLC/ APPLIES TO CENTRALUX.AI
§ 5.1

Scope and who is responsible

This covenant is issued by Centralux AI LLC, a North Carolina limited liability company at 109 Hay St Suite 202, Fayetteville, NC 28301 (“Centralux”, “we”). It covers the website at centralux.ai and the booking page at book.centralux.ai.

It does not cover data we process on behalf of a client under an engagement — that is governed by the written agreement for that engagement, and is described separately at § 5.7. It also does not cover third-party websites reached by a link from here.

§ 5.2

What this site collects by itself

Nothing that identifies you is collected by us from a visit to this site. Specifically:

Two technical exceptions, stated plainly. Serving a website means two other parties see the request. Cloudflare hosts these pages and processes your IP address, user-agent and request metadata in its logs to deliver the site and protect it from abuse. Google Fonts serves the three typefaces used here, and receives your IP address and user-agent as an unavoidable consequence of delivering the font files. Neither is used by us to identify you, and neither is combined with anything else we hold. Google Fonts is the only external resource this site loads.

§ 5.3

What you send us deliberately

There are exactly two ways to send us information, and both require you to choose to.

§ 5.3.1

Email

If you write to contact@centralux.ai we receive your email address, your name if you sign it, and whatever you chose to put in the message, including attachments. Our mail is hosted on Google Workspace. Please do not send credentials, passwords or access tokens by email — we will never ask for them this way.

§ 5.3.2

Booking a call

Booking at book.centralux.ai uses Cal.com as our scheduling processor. To hold the appointment it collects the name and email address you enter, the time you select, your time zone, anything you type into the notes field, and — if you choose a phone call rather than video — the number you provide for that purpose. A calendar invitation is then created in our Google Workspace calendar, and a video link is generated by Google Meet if that is the option you picked. The booking page is operated by Cal.com and is subject to its own cookie and privacy practices in addition to this covenant.

§ 5.4

What it is used for

§ 5.5

Processors and retention

The complete list of third parties that can see anything connected with this site, and how long each kind of record is kept.

ProcessorRoleWhat it can see
Cloudflare Hosting and content delivery for centralux.ai IP address, user-agent, requested URL and timestamp, in delivery and security logs
Google Fonts Serves the three typefaces used on these pages IP address and user-agent when the font files are requested
Cal.com Scheduling for book.centralux.ai Name, email, selected time, time zone, notes, and a phone number only if you choose a phone call
Google Workspace Business email and calendar The content of correspondence with contact@centralux.ai and the resulting calendar entries
Correspondence that did not lead to an engagementKEPT 24 MONTHS
Booking records for calls held or cancelledKEPT 24 MONTHS
Records connected to a paid engagementKEPT 7 YEARS
Host delivery and security logsPER CLOUDFLARE POLICY

The seven-year figure on engagement records is the accounting and tax retention period, not a preference. Anything outside that obligation is deleted on request.

§ 5.6

Your requests

Write to contact@centralux.ai from the address you corresponded or booked with, and say what you want: a copy of what we hold about you, a correction, or deletion. We will act within 30 days and confirm in writing what was done.

We may keep the minimum needed to satisfy a legal or accounting obligation, and will tell you specifically what that is rather than refusing in general terms. If you are unsatisfied with the outcome, say so in reply — that goes to the same person and is not routed to a queue.

§ 5.7

Client data under an engagement

A different thing entirely from website visitors, governed by the engagement agreement. Summarised here because it is the question that actually matters to a prospective client.

§ 5.8

Children, jurisdiction and changes

Index of entries

Six entries in one book

BOOK DIGEST RECORDED ON ENTRY 01
FolioEntryContentsStatus
01Statement of PositionThe thesis, the two columns, the four covenants, the engagement model.posted
02Schedule of ServicesFour service lines in full: what each is, what you receive, how it is delivered, where it fits.posted
03The FirmWhat the company is, where it operates, how it charges, and what it refuses to do.posted
04CorrespondenceBusiness contact record, booking, and exactly what happens on a discovery call.posted
05Covenant of PrivacyYou are hereWhat this site collects (almost nothing), who processes it, and how to have it removed.posted
06Articles of EngagementTerms of service: engagement, fees, credentials, intellectual property, liability, governing law.posted

Attestation of contents

FOLIO 05 OF 06
SHA-256 — this entry
computing…
 
No data leaves your browser.

How to reproduce it.

Take the <main> element of this page, read its textContent, collapse every run of whitespace to a single space, trim the ends, encode as UTF-8, and take the SHA-256, computed with crypto.subtle.digest.

A privacy policy that can be edited quietly is worth less than one that cannot. The digest of the whole book is recorded on Entry 01.