Privacy

AiLucent Privacy Statement

Effective 18 October 2026.

1. Scope and defined terms

This statement describes the personal data collected by AiLucent LLC ("AiLucent", "we", "us") through two things, and the purposes for which that data is used.

The Site. The AiLucent website. Through the Site you may request an install token, create an account, and purchase a subscription.

The Agent. AiLucent Agent Desktop, the application installed on your own computer. The Agent reads the session files that your AI coding tools write on that computer, keeps its own copies of those files, and provides search, reading, export, and question-and-answer functions over them.

Three terms are used throughout and have the following meanings.

  • "Session History" means the session files your AI coding tools write on your computer, together with the supporting files described in section 4.
  • "the Local Store" means the Agent's own data directory on your computer, within your operating system user account.
  • "the Check-in" means the contact described in section 6.1.1, and "the Usage Measurements" means the optional fields described in section 6.1.2.

Statements in this notice describe the Site and the Agent as they operate on the effective date above. Where this notice describes a protective function, it states how that function is designed and what it does not detect.

2. Responsibility for personal data

2.1 Data for which AiLucent is responsible

AiLucent LLC is responsible for the personal data collected through the Site and through the Check-in. That data comprises: the email address you provide to obtain an install token; the record of your acceptance of the license agreement, together with the IP address and browser user-agent string recorded with it; your account record; your purchase and affiliate records; and the fields listed in sections 6.1.1 and 6.1.2.

AiLucent holds that data, uses it for the purposes stated in this notice, and may be contacted about it at privacy@ailucent.ai. We read that mailbox and we will reply.

2.2 Session History

Session History, and the copies of it the Agent keeps in the Local Store, reside in your operating system user account on your own computer. AiLucent does not receive Session History and has no means to reach it. AiLucent cannot produce, correct, or delete Session History on your behalf. You can, using the controls in the Agent.

The functions that read Session History and write copies of it to the Local Store transmit nothing. Section 6 identifies each function that transmits data from your computer and states what each one sends.

2.3 Where an organization has enrolled your computer

An organization may operate a Hub and enroll computers in it, as described at section 6.4. Where it does, that organization determines what is captured on the computers it enrolls, what synchronizes to its Hub, who may see it, and how long it is kept. It is responsible for that data and for notifying the people whose computers it enrolls, and questions about data held in its Hub are for that organization. That is so whether the organization runs the Hub itself or AiLucent runs it on the organization's instructions; where the organization runs its own, AiLucent does not receive what is synchronized to it at all.

3. Personal data collected through the Site

Personal data enters through three points. Each is stated below with the fields recorded, the purposes for which they are used, and the legal ground for each use (the basis on which privacy law permits it). Three grounds appear in this notice: the performance of a contract with you, a legal obligation to which AiLucent is subject, and a legitimate business interest of AiLucent's that does not override your own interests.

3.1 Install tokens

The Agent is unlocked with a single-use install token rather than an account. When you request a token from the download page, AiLucent records: the email address you submit; a randomly generated install identifier, which is not derived from your address; the leading characters of the token, so that support staff can identify it without access to the token itself; the platform you select, if any; and the times at which the token was created, first redeemed by an Agent, and last seen.

AiLucent does not retain the token. What is stored in its place cannot be converted back into the token. The token is disclosed to you once, by email, and cannot afterward be recovered from AiLucent's records.

The email address is used to deliver the token, to answer support requests concerning your installation, and to determine whether an issued token was redeemed. If you later purchase a subscription, the address is the means by which your installation is matched to that purchase. The legal ground for these uses is the performance of a contract: delivering what you requested and what you purchased.

On acceptance of the license agreement, AiLucent additionally records the version accepted, a checksum of that document, the time of acceptance, the IP address from which the request originated, and your browser's user-agent string. We keep the IP address and the user-agent to verify entitlement and to enforce the license terms. They are the most identifying items described in this notice, and they are recorded on every acceptance, both at token issuance and at first redemption by an Agent. The legal ground for keeping them is AiLucent's legitimate interest in verifying entitlement, enforcing the license, and preventing abuse of the token system.

This form transmits email to any address submitted to it and is therefore rate limited.

3.2 The Check-in from the Agent

Stated in full at section 6.1, together with the Usage Measurements and the country counting described there.

3.3 Accounts

Authentication is performed by our identity service, which holds your credentials. The Site does not receive your password. Following authentication, AiLucent retains a membership record containing your email address, its verification status, and the identifier assigned to you by the identity service, so that your subscription can be located on subsequent visits. The legal ground is the performance of a contract: operating the account you created and locating what you purchased.

At checkout, Stripe's payment page asks for your first and last name and reports them to AiLucent together with the purchase. AiLucent gives them to the identity service, which holds them with your account. If your account does not yet hold a name, the identity service asks for it when you sign in. AiLucent uses your name to identify you and to address you in emails about your account and your subscription. The Site receives your name from the identity service when you sign in, in order to show it on your account page. The legal ground is the performance of a contract: operating your account and administering your subscription.

Adding a telephone number to your account is optional. If you add one, the identity service holds it, and it is used only to protect sign-in to your account and to help you recover access to the account. The legal grounds are the performance of a contract and AiLucent's legitimate interest in keeping accounts secure.

If you set up an authenticator app as a second step at sign-in, the secret that links the app to your account is held by the identity service. It does not reach the Site.

Accounts are created through the identity service. The Site provides no separate registration route.

3.4 Purchases and the affiliate program

Payments are processed by Stripe. Card numbers do not reach AiLucent's servers. AiLucent records the fact of a purchase or downgrade: the time, the plan, the Stripe session identifier, and the billing email address reported by Stripe. The legal ground for recording a purchase is the performance of a contract; for retaining the record afterward, the legal obligations that attach to business and tax records.

AiLucent also records the state and the country of the billing address reported by Stripe. They are used to apply the renewal rights that the law of your state provides, and for tax. The legal grounds are the performance of a contract and the legal obligations that attach to subscription renewals and to tax.

If you arrive through an affiliate link, AiLucent records the referral code, the page on which you landed, and the time, and sets a cookie so that a single visit is not counted more than once. A purchase made within the attribution window is linked to that code so that the affiliate may be paid. AiLucent does not record your IP address for referral attribution. If you enroll as an affiliate, AiLucent stores the payout email address you provide. The legal ground for referral attribution is AiLucent's legitimate interest in operating the affiliate program and paying referrals correctly; for the payout address, the performance of the contract with the affiliate.

4. Data the Agent reads on your computer

The Agent reads Session History within the directories you have configured and within no other location. The default configuration specifies the session directories of the two tools supported on the effective date, within your own user profile: the Claude Code project directory and the Codex sessions directory. You may modify that list. Narrowing it is the control available to you over what the Agent reads, and the Agent reads nothing outside it.

For each session, the Agent reads the transcript and the supporting files written alongside it: the transcripts of subagents invoked by the session, their metadata files, saved tool outputs, and workflow journals. Supporting files are retained with their session and are not presented as conversations.

A transcript may contain the contents of your files. Where an AI coding tool reads a file and returns its contents into the conversation, that text forms part of the session and is read by the Agent. The Agent does not read your source tree; material that your assistant read out of your source tree forms part of the Session History that the Agent does read.

The Agent's access to the configured directories is read-only. It does not write to them, and it does not modify, repair, or reorganize the files or databases of any other application.

AiLucent does not receive the data described in this section, so no use by AiLucent arises for which a legal ground would be required. The grounds stated in this notice attach to the data AiLucent receives, at sections 3 and 6.

5. Data the Agent creates and stores on your computer

All data created by the Agent is written to the Local Store. The Local Store contains the following.

5.1 Captured copies of sessions

The Agent retains a compressed and encrypted copy of each session file it reads, and a further copy on each change to that file, so that Session History is designed to persist if the originating tool subsequently deletes or rewrites its files. You determine how many copies are retained per file; the default is three, and the setting accepts any value from one to one hundred. Retention of these copies is a core function of the Agent and cannot be disabled. The Agent displays what is retained and the disk space in use, and the quantity retained is bounded by your setting.

A captured copy is the session file as written, byte for byte, compressed and then encrypted. It is not scanned or modified on capture. Where a secret was present in the conversation, that secret is present in the copy. Captured copies are protected by encryption rather than by removal; removal of secrets occurs on transmission, as stated at section 6.5.

5.2 The index

An encrypted local database recording what the Agent has read: file names, project directory names, message counts, timestamps, session titles, and a short signature of each file's contents by which the Agent determines that a file has changed. The index enables Session History to be listed and searched without rereading every file.

5.3 Records of questions submitted to the Ask function

Each use of the Ask function causes the Agent to write a permanent local record comprising: your question as submitted; the answer in full; the projects and dates specified as the search scope; the limits in force; the passages placed before the model and their locations within your Session History; the text of those passages; the model that answered and whether its endpoint was on your computer; and the outcome.

The following apply to these records.

  • A record is written for every question, at every entitlement level, from first installation, including questions that returned no result and questions that failed.
  • The question and the answer are stored as submitted and returned. They are not scanned for secrets. Secret removal in the Agent occurs on transmission, and these records are not transmitted.
  • The Agent provides no function to delete these records. There is no deletion control, no expiry, and no automatic cleanup. The records reside in your own user account and you may remove them. A deletion control is in design.

5.4 Redaction records

Where the Agent replaces a detected secret before content leaves your computer, it records that a replacement occurred (the channel, the pattern category, and the count). It does not record the secret.

5.5 Index backups

Scheduled local snapshots of the index database, written on the schedule and to the directory you configure. Backups cover the index and do not include captured copies. The default is daily, with seven snapshots retained. Backups may be disabled.

Nothing in the Local Store is transmitted by the function that creates it. Transmission occurs only by the means stated in section 6. AiLucent does not receive the contents of the Local Store, so no legal ground on AiLucent's part attaches to them.

6. Transmission of data from your computer

Four functions of the Agent transmit data from your computer. The first comprises a mandatory part and an optional part. The remaining three operate only where you have set them up.

6.1 The check-in, the usage measurements, and promotional messages

A registered Agent contacts AiLucent on start and approximately once every twenty-four hours thereafter. That contact serves three purposes, which are separately governed. An Agent that has not been registered transmits nothing.

6.1.1 The check-in, which is required and cannot be disabled

The check-in identifies the installation and returns the entitlement associated with it, which is how an Agent learns the tier you have purchased. It cannot be disabled, because an Agent that cannot ask what you are entitled to cannot deliver what you paid for.

The check-in carries the following and no more.

  • A schema version number.
  • An install identifier, randomly generated at unlock and not derived from your email address.
  • A machine identifier, which denotes the individual computer. It is constant across reports from that computer and is the means by which two computers unlocked with the same token are distinguished. It contains no computer name, user name, or hardware serial number, and none of those can be derived from it.
  • The Agent version.
  • The operating system family (Windows, macOS, or Linux) and no more specific identification.
  • The time of transmission.

The check-in is pseudonymous, not anonymous. It contains no name and no email address. It is authenticated with your install token, and AiLucent's records associate that token with the email address used to obtain it. AiLucent is therefore able to associate a check-in with an email address. The machine identifier is constant for the life of the computer. The check-in carries no information about your work; it is not anonymous. The legal ground for the check-in is the performance of a contract: an Agent that cannot ask what you are entitled to cannot deliver what you paid for.

6.1.2 The usage measurements, which you may refuse

Where you permit them, the check-in additionally carries measurements. These contain counts, version strings, fixed categories, and times. They contain no free-text field: a value that cannot be expressed as a number, a rounded range, a version, or a fixed category is not included. The measurements comprise the following fields and no others.

  • Whether the installation is self-hosted or cloud.
  • The assistant formats detected on the computer, from a fixed list (on the effective date: Claude Code, Codex).
  • The number of files tracked, expressed as a rounded range such as "1k-10k" rather than an exact figure.
  • The number of secrets replaced prior to any transmission, expressed as a rounded range.
  • The number of hours the measurements cover.

Counts are expressed as rounded ranges rather than exact figures because an exact total may identify an individual organization.

Refusing the measurements. The Agent's Settings screen contains a switch, "Share usage measurements". With it off, the check-in carries no measurements, and the Agent does not compute them: the index is not read for this purpose at all. The legal ground for the measurements is AiLucent's legitimate interest in understanding how installations are used so that the product can be maintained and improved, an interest balanced by the rounded ranges, the absence of any free-text field, and this switch.

An organization deploying the Agent may also disable the measurements for an entire deployment, by configuration or by setting the environment variable AILUCENT_TELEMETRY=off. Where an organization has done so, the Settings switch displays as off and cannot be enabled on the individual computer.

6.1.3 Promotional messages, which you may refuse separately

The Agent displays a strip of product news and offers, which it retrieves from AiLucent. The Settings screen contains a second switch, "Show promotional messages". With it off, the Agent does not retrieve them. The legal ground is AiLucent's legitimate interest in telling its users about the product, balanced by this switch.

Update and security notices are not promotional messages, are not governed by that switch, and continue to be retrieved. That retrieval carries no identifier and no information about your work.

6.1.4 What AiLucent records when a check-in arrives

AiLucent records roughly where its installations are, so that it can decide where to operate servers.

When a check-in arrives, the connecting network address is converted, within that same request, into a country, a state or province, and a city. The address itself is then discarded. It is not written to any database, log, or error report. The conversion uses a data file AiLucent holds, so no other company receives your address.

What is kept is counts, and nothing else: how many check-ins arrived from each country on each date, and how many installations were in each place in each month, counting one installation once a month however often it connects. Neither record has any field in which an identifier of you, your installation, or your machine could be stored, and neither can be connected to the record of who checked in. Whether an installation has already been counted in a given month is decided from a separate record, which knows which installation was active and never knows where it was.

Three limits apply by design. The month is the finest grain, because a daily figure would let someone follow one installation's pattern. A city with fewer than five installations in a month is not shown on its own; it is reported as part of its state, and a state below the same threshold as part of its country. And city results are approximate, because network providers register addresses at regional offices, so a city indicates an area rather than an address.

Where a location cannot be determined, including an address on a private network, the check-in is counted as undetermined rather than discarded, so that the totals stay honest. The legal ground for the momentary use of the connecting address is AiLucent's legitimate interest in knowing roughly where its installations are so that it can decide where to operate servers, an interest served by counts alone, with the address itself discarded.

6.2 The Ask function

The Ask function searches Session History on your computer, selects matching passages, and transmits your question together with those passages to the model endpoint you have configured. The function does not operate until you configure an endpoint. The destination is determined by the address you enter, and the Agent distinguishes three cases.

  • An endpoint on your computer. Where the endpoint is a loopback address, which is the ordinary configuration for tools such as Ollama and LM Studio, the exchange remains on your computer and no data is placed on any network.
  • An endpoint elsewhere on your own network. Where the endpoint is a private network address or a .local name, the text leaves your computer and remains on your local network. Before transmission, the Agent identifies the destination and requires your confirmation. Where the connection is unencrypted, the confirmation states that fact.
  • An endpoint on the public internet. Installations as released refuse this. Transmission of conversation text to a model endpoint on the public internet requires an entitlement not offered in this release. No configuration and no acknowledgment permits it.

Accordingly, on the Agent as released, conversation text may reach a model endpoint you operate and may reach no model service on the public internet. Passages transmitted by the Ask function are subject to section 6.5.

6.3 Export and copying by you

You may export a conversation to a Markdown or text file, direct scheduled index backups to a directory of your choosing, and copy material out of the Local Store.

Exports are redacted by default, under the configuration stated at section 6.5. Where you elect to export without redaction, the file contains the conversation as held, and the Agent records that the export was taken without redaction.

Writing a file is not a transmission by the Agent; the file is written to your own computer and its subsequent movement is your act. It is included here because it is the means by which conversation text most commonly reaches another location.

6.4 Synchronization to a Hub, where you enroll the computer

A Hub is a server application that holds the conversation records of an organization's enrolled computers. A Hub may be operated by the organization that enrolls the computers, on its own infrastructure, or by AiLucent. Which of those applies to a given Hub is determined by its address, which is the address entered at enrollment. Where an organization operates its own Hub, AiLucent does not operate it, does not host it, and does not receive what is synchronized to it.

The Agent does not synchronize unless the computer is enrolled. Enrollment requires the address of a Hub, which is entered on the Agent's connect screen, together with a credential issued by that Hub. An Agent that is not enrolled indexes and searches locally and synchronizes nothing.

Where a computer is enrolled, each synchronization cycle sends the following to the Hub at the address entered.

  • Conversation content, redacted as described at section 6.5, including the content of conversations whose original files the AI tool has since deleted, where the captured copy is what is sent.
  • Conversation metadata: the file name, the project directory name, the session title, message counts, timestamps, and the file size and content signature. This includes the full path of the file on your computer, which on common operating systems contains your user name.
  • Information about the computer: the Agent version, a description of the operating system, and the number of files tracked.
  • Redaction records, stating that a secret was detected and where within the conversation it appeared. These records do not contain the secret.

Supporting files, the records of questions submitted to the Ask function, and index backups are not synchronized.

Who is responsible for data in a Hub. Where an organization enrolls your computer, that organization determines which directories are read, what synchronizes, who within the organization may see it, and how long it is retained. Those are the organization's decisions whoever operates the Hub, and so is the obligation to tell the people whose computers it enrolls what is captured and why. AiLucent does not give that notice on an organization's behalf, and is not in a position to: we do not know who is using a given computer or what they were told when it was issued. Where you work on a computer your organization enrolled and wish to know what is captured, ask your administrator. What the Agent is capable of capturing is described in this notice.

Where AiLucent operates the Hub, AiLucent holds the synchronized records and runs the service on the enrolling organization's instructions, and that organization remains the one deciding what is collected and who may see it. In that arrangement the legal ground for the processing is the organization's to establish, and AiLucent processes on its instructions. Where the organization operates its own Hub, AiLucent does not operate it, does not host it, and does not receive what is synchronized to it.

6.5 Removal of secrets before transmission

The Agent is designed to detect credentials and keys and to replace them with placeholders before content leaves your computer. This function operates on every channel capable of carrying conversation text out of the Agent: the Ask function, export to a file, and synchronization to a Hub. A single configuration setting governs all such channels.

Three qualifications apply to this function.

  • It is a design and not a result. Detection operates by matching patterns of known secret forms. It will not detect a secret in a form no pattern describes, a password written as prose, or a key entered in fragments. No automated detection identifies what it was not written to identify.
  • It is directed at secrets and not at personal information. A name, a medical record, a postal address, or an image within a tool output is not a credential and is not within the scope of this function. No function of the Agent reads a transcript and determines what within it is sensitive.
  • It may be disabled. Redaction is enabled by default and is a configuration setting. Where it is disabled, the channels above carry unredacted text, and the Agent states that redaction is not in operation.

No secret, and no value derived from a secret, is included in the Check-in or the Usage Measurements. The Usage Measurements carry only a rounded range representing the number of replacements.

7. Data not collected

The following are properties of the Agent's construction.

Never your conversations

No message text, prompt, answer, reasoning block, tool input, or tool output is included in the Check-in or the Usage Measurements. Conversation text leaves your computer only on the paths at sections 6.2 and 6.4, each of which you set up: a model endpoint you configure, which as released may not be on the public internet, and synchronization to a Hub in which you enroll the computer. Where you do neither, conversation text does not leave your computer.

Never your code or your file names

No source files, file names, project names, repository paths, or directory structures are included in any data AiLucent receives from the Agent. Neither the Check-in nor the Usage Measurements contains a free-text field.

Never your secrets

Credentials and keys are detected and replaced on your computer before content leaves it, subject to the qualifications at section 6.5. Neither a secret nor any value derived from one is included in the Check-in or the Usage Measurements.

8. Deletion of a conversation in your AI tool

Deleting a conversation within Claude Code or Codex deletes that tool's files. It does not delete the captured copies held in the Local Store; persistence against that deletion is the purpose of those copies. Following deletion by the tool, the captured copies are the remaining record of that conversation, and the Agent identifies the conversations that exist only as captured copies.

Captured copies may be removed by you. They reside in the Local Store, within your own user account. The Agent displays the disk space in use, and your retention setting bounds the number retained per file. Uninstalling the Agent leaves the Local Store in place, so that its removal is an act you take.

Where the computer is enrolled in a Hub, records already synchronized to that Hub are a separate copy. Removing a captured copy from the Local Store does not remove them, and their deletion is governed by the organization operating that Hub.

9. Matters for which you are responsible

9.1 What you capture

AI coding conversations frequently contain the personal data of persons other than you: material you entered, material your tools read from your files, and material written by colleagues, clients, patients, end users, or any person whose information passed through a file the assistant opened or a log it produced. The Agent reads the contents of the session files within the directories you configure. It does not assess those contents.

Whether you may capture and retain that material is your determination. It is governed by the law applicable to you, your agreement with your employer or client, and the professional duties to which you are subject. A clinician, a lawyer, a banker, a teacher, and a public employee are each subject to rules that AiLucent does not know and cannot verify. AiLucent does not make that assessment on your behalf, and nothing in this notice constitutes authorization to capture any material. Where you are not permitted to retain material, do not configure the Agent to read it. The configured directories are set by you and may be narrowed by you, and the Agent reads nothing outside them.

9.2 The contents of your transcripts

The redaction function is stated at section 6.5, together with the three qualifications that make it a design rather than a result. The assessment of what your transcripts contain is yours: what is appropriate to retain, what is appropriate to transmit to a model endpoint, and what ought not to have entered a conversation. Redaction is an assistive function and does not constitute clearance.

9.3 Destinations you select

Where a copy is written to a location you select, whether an exported file, a backup directory, or a transcript placed into a ticket, that location is yours. Its security, the persons able to reach it, its persistence, and whether another system copies it further are properties of that location and not of the Agent. The Agent cannot follow a file to a shared drive, a directory synchronized to a cloud account, a message, or removable media, and this notice makes no statement as to what occurs after a file is written. AiLucent and its parent and affiliates are not responsible for a destination you select.

9.4 Preservation is not a backup service

The Agent retains its own copies so that Session History is designed to persist where your AI tool deletes or rewrites its files. That design does not constitute a backup service and should not be relied upon as one.

The copies reside on your disk and a disk may fail. A copy you delete is not recoverable. Your retention setting bounds the versions retained per file, and reducing it removes older versions. A tool may write a session in a form the Agent cannot read, write it to a location you have not configured, or write nothing; material never captured cannot be preserved. An uninstall with the purge option, a cleanup utility, a reinstalled operating system, or any program with access to your files may remove the Local Store. AiLucent and its parent and affiliates do not warrant that any conversation will be captured, retained, or recoverable.

Retention of material you cannot afford to lose is your responsibility.

9.5 The tools whose files the Agent reads

Claude Code and Codex are the products of other companies. The locations in which they write sessions, the formats they use, their retention and pruning behavior, their terms, their pricing, and their continued availability are determined by those companies. Any of these may change without notice to you or to AiLucent, and a change may result in the Agent reading less than it previously read, reading differently, or being unable to read a tool until it is updated. Support for a tool describes the Agent's present operation and is not a commitment as to that tool's future behavior.

Your relationship with those companies is yours. What they collect from you, what they do with your conversations, and what they retain are governed by their terms and their privacy statements.

9.6 Answers returned by the Ask function

The Ask function locates passages within your Session History and transmits your question, together with those passages, to the model endpoint you configured. The answer is generated by that model and may be incomplete, outdated, or incorrect: the search may not locate the conversation containing the relevant material, and models state incorrect information in confident terms. An answer is a reference into your own Session History. It is not a finding, and it does not constitute advice from AiLucent, whether legal, medical, financial, security, or engineering. Material on which you intend to rely should be verified against the conversation itself. The Agent identifies the conversations on which an answer drew.

10. Cookies

The Site sets cookies for the following purposes.

  • Authentication. A session cookie maintaining your signed-in state for up to twenty-four hours of activity. It is required for the Site to function once you hold an account.
  • Security. Short-lived cookies protecting forms against cross-site request forgery and protecting the sign-in exchange.
  • Affiliate attribution. Where you follow an affiliate link, a cookie persisting for thirty days records the code with which you arrived, so that a subsequent purchase may be credited and a single visit is not counted repeatedly. It is set on arrival, without a prior prompt, and is classified in our code as strictly necessary, so no consent prompt is presented.

No third-party analytics or advertising script runs on the Site. There is no tracking pixel, no advertising network, and no cross-site profiling. No cookie-consent mechanism is presented, as each cookie above is required for the Site to function or to attribute a referral. Where measurement outside that category is introduced, a consent mechanism will be introduced with it.

11. Service providers and location of processing

AiLucent uses the following service providers, each for a single function, and each receives only the data that function requires.

  • DigitalOcean: hosts the Site, its databases, and the files available for download, and accordingly holds, as hosting provider, the records described in this notice.
  • Stripe: processes payments and holds card details, which AiLucent does not receive.
  • Mailgun: delivers install tokens and account email.
  • Our identity service: holds sign-in credentials and the name and any telephone number on your account, and verifies email addresses.

None of these providers receives the content of your conversations, your code, or your file names. AiLucent operates no advertising network, no data brokerage, and no error-tracking service.

All four are United States companies and process this data in the United States. AiLucent does not offer a European processing option. Where the location of processing is material to you, raise it with us before purchase.

12. Your rights, your choices, and how to contact us

Refusing the usage measurements. Turn off "Share usage measurements" in the Agent's Settings screen. An organization deploying the Agent may disable the measurements for an entire deployment by configuration or by setting AILUCENT_TELEMETRY=off. The check-in described at section 6.1.1 continues in either case, and section 6.1.1 states what it carries.

Refusing promotional messages. Turn off "Show promotional messages" in the Agent's Settings screen. Update and security notices are unaffected.

Your rights over the data AiLucent holds. For the data for which AiLucent is responsible, described at section 2.1, you may ask AiLucent for any of the following.

  • A copy of the data held about you.
  • Correction of data that is inaccurate.
  • Erasure of the data.
  • Restriction of its use: AiLucent keeps the data but stops using it.
  • A copy in a commonly used, machine-readable form, for yourself or to carry to another provider.
  • An end to a particular use to which you object.

You also have the right to complain to a privacy regulator. In Europe that is the supervisory authority of the country where you live, where you work, or where the matter you are complaining about occurred, and you may complain to it directly, without asking AiLucent first.

How to ask, and what happens next. Write to privacy@ailucent.ai and identify the email address concerned so that the records can be located. To confirm that a request comes from the person concerned, AiLucent replies to the email address already on the record, the same method by which install tokens are delivered. You will receive a substantive answer within one month. Where a record must be kept despite a request (for example, a purchase record retained under tax law, or a record needed in connection with a legal claim), the answer states what was not done and the reason, and the record is kept but no longer used.

Data AiLucent cannot act on. Session History resides on your computer, and AiLucent has no means of access to it (section 2.2); the controls in the Agent are the means of producing, copying, or deleting it. Records synchronized to an organization's Hub are governed by that organization (section 2.3), and requests concerning them should go to its administrator.

Email you receive. Addresses collected as described in this notice are used to deliver what was requested, being your install token or email concerning your account and purchase, and to answer support requests concerning that installation. AiLucent does not send marketing email to them.

13. Commitments

  • AiLucent does not include conversation content, file names, or free text in the Check-in or the Usage Measurements.
  • AiLucent does not sell or share your data with advertisers or data brokers, and operates no advertising network and no cross-site profiling.
  • AiLucent does not send marketing email to the addresses collected as described in this notice.

14. Relationship to other documents, and rights not affected

Nothing in this notice reduces rights you hold that cannot be waived under the law applicable to you. Nothing in this notice limits the responsibility of AiLucent LLC and its parent and affiliates for gross negligence, willful misconduct, fraud, or death or personal injury. Where a statement in this notice is broader than applicable law permits, it applies to the extent permitted and no further, and the remainder of the notice is unaffected.

This notice describes the handling of data. It is not a contract. The obligations of each party are set out in the End User License Agreement governing the software installed on your computer and in the Terms of Service governing accounts and purchases. Where this notice and either of those documents address the same subject, they are drafted to be consistent; where they are not, the document you accepted governs the obligations of each party.

15. Changes to this notice

This notice is dated. Where the data collected changes, this notice and the date above are amended. The version published here is the current version.

16. Contact

Privacy inquiries: privacy@ailucent.ai
Legal notices: legal@ailucent.ai
All other inquiries: ailnctsupport@ailucent.ai

AiLucent LLC
30 N Gould St Ste R
Sheridan, Wyoming 82801
United States of America