Jatter is built around a simple principle: personalized AI should not require giving up control of your personal data.
To provide personal answers, Jatter can learn from your chats, your notes and—with your explicit permission—websites you use, including pages inside logged-in accounts. Your notes, browsing history, memory and learned website data are protected with client-side encryption. Your chats are never stored in plaintext. We apply strict data-retention controls to service providers, and we never use your data to train AI models.
We also believe trust requires being candid about what is not yet private by design. This page explains what Jatter learns, how your data is protected, where it is processed, and the limitations we are still working to address.
What’s changed
This page was updated on October 13, 2026. Since the previous version:
- Notes are now client-side encrypted.
- Browsing history is now client-side encrypted.
- Chats are never stored in plaintext. Chat content is in plaintext only in transit while it is processed, and is never written to a database in plaintext.
- Jatter now has memory. It is derived from your chats and notes and, only if you opt in, from your browsing activity and learned web pages. Memory is client-side encrypted, and you can view, export, and delete it at any time.
Unencrypted notes and browsing history are no longer listed among our current privacy limitations.
What does Jatter learn?
Jatter learns from your chats and notes to build a memory that makes its answers more personal. If you opt in, it can also learn from your browsing activity and from web pages inside your logged-in accounts.
For example, you might grant Jatter permission to learn pages from a financial, medical, school, or other personal website so that it can later help answer questions using information from those pages.
Permission to learn authenticated pages is granted on a website-by-website basis. Jatter does not learn authenticated pages from a website unless you have authorized it to do so.
When does Jatter learn a page?
Jatter learns an authenticated web page only when:
- You have granted Jatter permission to learn from that website.
- You open or navigate to a page on that website while signed in.
Granting permission does not give Jatter unrestricted access to your account. Jatter learns pages as you visit them; it does not independently browse through the account on your behalf.
How does Jatter’s memory work?
Memory is what Jatter knows about you so it can give answers that fit your life. It is client-side encrypted, and you can see, manage, export, or delete all of it at any time.
Where memory comes from
- By default: your chats and your notes.
- Only if you opt in: your browsing activity and the authenticated web pages Jatter has learned.
If you do not opt in, Jatter does not derive memory from your browsing activity or learned web pages.
How memory is protected
Your memory is client-side encrypted before it is stored. Jatter’s servers do not have access to its unencrypted contents.
Your control over memory
You always have full access to and control over your memory. You can:
- View everything Jatter remembers about you.
- Delete individual memories.
- Export your memory.
- Delete all of your memory at once.
What is client-side encrypted?
Jatter uses client-side encryption for:
- Your notes.
- Your browsing history.
- Your memory.
- Data learned from authenticated websites, after processing is complete.
Client-side encryption means this data is encrypted using keys controlled on your device before it is stored. Jatter’s servers do not have access to its unencrypted contents.
Chats are never stored in plaintext. A chat turn exists in plaintext only while it is in transit for processing. Chat plaintext is never written to a database.
Client-side encryption does not mean data stays encrypted during every stage of processing. Chats and authenticated web pages must currently be handled temporarily in unencrypted form so Jatter can generate responses, learn their contents, and update your memory. The next section explains when that happens.
Where third-party services are involved, we use providers and contractual safeguards intended to minimize retention and prevent secondary uses of the data.
When is data temporarily unencrypted?
Processing chat responses
Your chat must be temporarily unencrypted when it is sent to the hosted large language model used to generate a response. It exists in plaintext only in transit for this processing and is never stored in plaintext in a database.
The chat is sent without information intended to directly identify you. The AI provider may temporarily retain this anonymized data for security, abuse prevention, and compliance purposes.
It is not used to:
- Train AI models.
- Build an advertising profile about you.
- Track your activity across Jatter.
Learning authenticated web pages
Information from an authenticated web page must currently be processed temporarily in unencrypted form before the learned data can be encrypted and stored.
The retained learned data is client-side encrypted after processing.
We are working toward moving more of this learning process onto your device—particularly on desktop—so that the exposure of unencrypted authenticated data can be minimized or, where technically possible, eliminated.
Building and using memory
To derive memory, Jatter temporarily processes the relevant content in unencrypted form: your chats and notes, and—only if you opt in—your browsing activity and learned web pages. When your memory or notes help answer a question, relevant portions are temporarily included in the request sent to the model.
The resulting memory is client-side encrypted before it is stored.
Open-web reasoning
Jatter may send relevant portions of a chat to a web search service when current or open-web information is needed to answer a question.
Data sent to this service is covered by a zero-data-retention policy. It is not retained by the service after processing.
What is not currently client-side encrypted?
The following data is not currently protected with client-side encryption:
- User profile and account data.
- Chats while they are temporarily in transit for processing.
- Authenticated website data while it is temporarily being processed.
- Content temporarily processed to build or use your memory.
Some user profile information must remain accessible to Jatter’s systems so we can operate your account, provide the service, manage subscriptions, and support account recovery and deletion.
What data does Jatter retain?
Depending on how you use the product, Jatter may retain:
- Client-side encrypted chats.
- Client-side encrypted notes.
- Client-side encrypted browsing history.
- Client-side encrypted memory.
- Client-side encrypted data learned from authenticated websites.
- User profile and account data.
We retain this information to provide features such as conversation history, personalized answers, memory, notes, browsing functionality, account management, and synchronization across supported devices.
What data is sent to AI and search providers?
Large language model provider
Jatter sends anonymized, temporarily unencrypted chat content to the hosted large language model used to generate responses and to build your memory.
The provider may temporarily retain this data for security and compliance purposes. It may not use Jatter user data to train its models or track individual Jatter users.
When your memory, your notes, or information learned from an authenticated website is needed to answer a question, relevant portions may also be included in the request sent to the model.
Web search provider
When a question requires open-web research or reasoning, relevant chat content may be sent to our web search provider.
All Jatter user data sent to this service is subject to a zero-data-retention policy.
Does Jatter train AI models on user data?
Never.
Jatter does not use your chats, memory, browsing activity, notes, learned website data, or profile information to train AI models.
We also require the AI services used by Jatter not to use Jatter user data for model training.
Does Jatter sell user data?
No.
Jatter does not sell your personal data.
We do not operate an advertising business based on tracking your browsing behavior, and we do not share your personal information with advertisers for targeted advertising.
Can users export and delete their data?
Yes.
You can delete:
- Individual chats.
- Notes.
- Individual memories, or all of your memory at once.
- Data learned from authenticated websites.
- Browsing history.
You can export your memory at any time.
You can also delete your Jatter account. When an account is deleted, Jatter deletes the user data associated with that account, subject to any limited information we may be legally required to retain.
Because some third-party providers may temporarily retain anonymized data for security and compliance purposes, deletion from Jatter may not immediately remove data held within a provider’s limited compliance-retention window.
What are Jatter’s current privacy limitations?
Jatter is designed to improve privacy beyond the conventional model of AI personalization, but the system is not yet private in every respect.
Authenticated website learning requires temporary unencrypted processing
Although retained learned data is client-side encrypted, authenticated web pages must currently be processed temporarily in unencrypted form.
We plan to move more of this processing onto your device over time—at least on desktop, and potentially on mobile—so that the exposure of authenticated data can be reduced or eliminated where possible.
Chats and memory require temporary unencrypted processing
Chats exist in plaintext only in transit, and are never stored in plaintext. But they, and the content used to build and apply your memory, must currently be temporarily unencrypted to use a hosted large language model.
The AI provider may temporarily retain anonymized chats for security and compliance purposes. We are working toward placing this processing under a full zero-data-retention policy in the future.
Our direction
Privacy is not a feature we consider finished. It is an architectural direction.
Since this page was first published, we have extended client-side encryption to notes, browsing history, and memory, and stopped storing chat plaintext entirely. Our goal is to keep moving more personal-data processing onto your device, reduce the amount of information exposed during processing, and give you more precise control over what Jatter learns and remembers.
We will continue updating this page as Jatter’s privacy architecture evolves.