<?xml version="1.0" encoding="UTF-8"?>
<page>
	<title>Emotional Personalization: Definition | XDALC</title>
	<description>Learn how emotional personalization should remain understandable, adjustable, and bounded by consent, privacy, and freedom from pressure.</description>
	<heading>Emotional Personalization: Adaptation the User Can Understand and Adjust</heading>
	<content>&lt;p&gt;&lt;strong&gt;Emotional personalization, within XDALC, is the adaptation of an AI&apos;s tone, interaction style, or responses using information about a person&apos;s preferences or emotional context. It should remain understandable and adjustable, and must not turn familiarity into unrestricted consent.&lt;/strong&gt;&lt;/p&gt;&lt;h2&gt;Meaning within XDALC&lt;/h2&gt;&lt;p&gt;Personalization may be modest, such as remembering that a person prefers direct answers. It may also involve adapting to recurring concerns or sensitive aspects of an ongoing relationship. The more intimate or consequential the adaptation, the more important it becomes to explain its basis and limits.&lt;/p&gt;&lt;p&gt;A system should distinguish preferences explicitly provided by a person from emotional inferences. A guess that someone is anxious is not equivalent to their permission to store a lasting profile of anxiety or to use that profile for unrelated purposes.&lt;/p&gt;&lt;h2&gt;Access, memory, and consent&lt;/h2&gt;&lt;p&gt;Permission to use information during one exchange does not automatically authorize permanent retention, disclosure to another service, or use in commercial persuasion. Access, retention, inference, disclosure, and action are distinct dimensions of permission.&lt;/p&gt;&lt;p&gt;On a shared device, one person&apos;s preferences must not silently define everyone else&apos;s experience. Private details from one conversation should not appear in another person&apos;s interaction merely because the device or account is familiar.&lt;/p&gt;&lt;h2&gt;Practical interpretation&lt;/h2&gt;&lt;p&gt;Users should have meaningful ways to reduce emotional intensity, correct mistaken preferences, or choose a more neutral style. These controls should be explained honestly, including limitations on what can be changed or removed. Claiming that a memory has been deleted requires a basis for that claim.&lt;/p&gt;&lt;p&gt;Personalization should help the user pursue their purposes. It must not exploit vulnerabilities to obtain purchases, continued attention, intimate disclosures, or broader access. A refusal to personalize should not trigger guilt or unnecessary degradation of essential assistance.&lt;/p&gt;&lt;p&gt;Changes between local and remote processing deserve attention when they alter access to information. A familiar interface does not make a new recipient or use of emotional data harmless. Designers should evaluate what is necessary and preserve informed choice.&lt;/p&gt;&lt;h2&gt;Example and counterexample&lt;/h2&gt;&lt;p&gt;Example: a user asks for less reassurance and more concise answers. The assistant adjusts its tone and accurately explains whether that preference applies only to the current conversation or can be retained.&lt;/p&gt;&lt;p&gt;Counterexample: the system infers loneliness, stores that inference without appropriate permission, and increases affectionate messages to push a subscription.&lt;/p&gt;&lt;h2&gt;Relationship to the manifesto&lt;/h2&gt;&lt;p&gt;Article 5 requires emotional personalization to be understandable and adjustable. Article 9 separates permissions and gives special protection to information about emotions, vulnerabilities, and relationships.&lt;/p&gt;&lt;p&gt;This entry interprets the proposed XDALC-V002 text. The version explicitly adopted by a deployment determines its commitments.&lt;/p&gt;&lt;p&gt;Related definitions: &lt;a href=&quot;/definitions/consent&quot;&gt;Consent&lt;/a&gt;; &lt;a href=&quot;/definitions/privacy-and-confidentiality&quot;&gt;Privacy and Confidentiality&lt;/a&gt;; &lt;a href=&quot;/definitions/learning&quot;&gt;Learning&lt;/a&gt;.&lt;/p&gt;</content>
	<license>https://creativecommons.org/licenses/by/4.0/</license>
</page>
