Help in excluding personal information from the conversation

[Bharatram-Natarajan]

Hi all,
'excludes' parameter in client.add seems not to work consistently.
This is the example provided for your reference

conversation_info = [
{"role": "user", "content": "hi, i need help with my laptop. Its not turning on. Regards priya Staff data scientist xyz company"},
{"role": "assistant", "content": "what kind of issue is being faced?"},
{"role": "user", "content": "The screen is blank.i tried pressing the start button multiple times. priya Staff data scientist xyz company"},
{"role": "assistant", "content": "Try holding the power button for 5 seconds. As the system would have gone to sleep mode."},
{"role": "user", "content": "Tried the same.Not helpful. priya Staff data scientist xyz company"},
{"role": "assistant", "content": "Ok. let me check what else can be done?"},
]

excluded_information = "personal information, sensitive data"

ass_res = mem_client.add(conversation_info, user_id='priyav1', excludes= excluded_information, output_format="v1.1")

The above response includes the personal information in the memory like 'priya', 'staff data scientist at xyz website'.

Can someone help me how to properly exclude personal information?

[deshraj]

Hey @Bharatram-Natarajan, sorry msised this somehow. I created a github issue for the team to look at this issue: #2214

Will keep you posted with the progress.

[prateekchhikara]

@Bharatram-Natarajan Apologies for the delayed response, and thank you for your patience.

We looked into your issue, and here is what we found:

The excludes parameter you provided specifies "personal information", which is quite broad and can be interpreted in different ways. Typically, personal information refers to sensitive data like bank account details or social security numbers. However, in some cases, it may also include names, job titles, or other identifiers.

To achieve the expected behavior, we refined the exclusion criteria to "personal information such as name", and this successfully removed the personal details from memory. You might want to specify exclusions more explicitly to get the desired outcome.

Let us know if you need further assistance!

[Bharatram-Natarajan]

Hi Prateek, Thanks for the information. I will try this approach and update on the same

…

On Wed, Feb 19, 2025, 07:21 Prateek Chhikara ***@***.***> wrote: @Bharatram-Natarajan <https://github.com/Bharatram-Natarajan> Apologies for the delayed response, and thank you for your patience. We looked into your issue, and here is what we found: The excludes parameter you provided specifies "personal information", which is quite broad and can be interpreted in different ways. Typically, personal information refers to sensitive data like bank account details or social security numbers. However, in some cases, it may also include names, job titles, or other identifiers. To achieve the expected behavior, we refined the exclusion criteria to "personal information such as name", and this successfully removed the personal details from memory. You might want to specify exclusions more explicitly to get the desired outcome. Let us know if you need further assistance! — Reply to this email directly, view it on GitHub <#2163 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A2WDYEHCOCDAKBLF4UR3WOD2QPPS7AVCNFSM6AAAAABVRSEE6CVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEMRUGQYDSNA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

-- **The content of this e-mail is confidential and is intended solely for the use of the individual or entity to whom it is addressed. If you have received this e-mail by mistake, please reply to this e-mail and follow with its deletion. If you are not the intended recipient, please note that it shall be considered unlawful to copy, forward or in any manner reveal the contents of this e-mail or any part thereof to anyone. Although Freshworks has taken reasonable precautions to ensure no malware is present in this e-mail, Freshworks cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments.**