Privacy Policy

Effective October 28, 2026

lore is an AI agent you text over iMessage. It remembers what you tell it so it can help you, and it can connect you with people you know, with your yes. This policy explains what lore collects, how its AI uses that information, who else handles it, how long it is kept, and the choices and rights you have. lore is for people 13 and older. We do not sell personal information, we do not use it for targeted advertising, and we do not train AI models on your content.

The short version

lore keeps your messages and what it learns from them so it can remember context and do what you ask.
What is said in a group stays with that group. What you tell lore one to one stays between you and lore.
To answer you, lore sends the text it needs to AI model providers and, for web tasks, to search and browser services. They handle it to provide their service to us.
lore never introduces you, shares your contact details, or sends, posts, books or buys anything for you without your yes.
You can download and delete your data. Say "lore forget me", "lore forget this group" or "forget me everywhere", or delete your account on your dashboard.
Nobody under 13 may use lore. A parent or guardian of a teen can ask us to delete their teen's data.

Who we are

"lore", "we" and "us" mean the team that runs lore: the AI agent in iMessage, the website loregroupchat.com, and the app and dashboard at host.loregroupchat.com. We are based in Sacramento, California, and we are responsible for the personal information described in this policy. You can reach us at privacy@loregroupchat.com, or text lore "talk to a human" and a person will answer you.

Services you connect to lore, such as Google, Slack, GitHub, or a website lore signs in to for you, have their own privacy policies, which apply to what they do with your information.

What we collect

What you and your chats give us

Your phone number and chat identity. Your phone number when you text lore, and your Slack workspace, channel and user IDs if you used lore in Slack. If you create a lore account, we link your phone number and Slack identity to it. lore is no longer offered in Slack: it stopped answering there, and what it stored from Slack is kept until you delete it or the workspace uninstalls lore, as described below.
Messages. The messages, photos, files, links and contact cards sent in chats where lore is present, lore's replies, and when they were sent. In a group, lore receives everyone's messages so it can keep context, not only the ones addressed to it.
Memory. Facts, plans, preferences, decisions and shared notes lore learns from a chat. In a group these can include things people say about each other, such as plans, birthdays, jobs or relationships. A fact lore learns about you from a group is kept with the message it came from, so lore can tell you where it learned it.
Your personal profile. What you tell lore about yourself one to one, such as what you do, what you are looking for, your goals, deadlines and the people you care about, and the public profile you choose to publish.
Notes about people you know. If you tell lore about people in your life (for example "my mom", a friend's birthday, or how often you want to keep in touch), or share contact cards with it, lore keeps those notes privately for you.
Connected accounts. If you connect Google, GitHub or a calendar link, we store an encrypted key that lets lore act on that account for you, and what lore needs from the account for your request, such as a Google Doc you picked, your free and busy times, or emails you asked it to read.
Saved logins. If a task needs you signed in to a website, you can save that site's username and password on a private lore page. They are stored encrypted and used only to sign in for your own tasks.
Work records. Records of what you asked lore to do and what it did: reminders, polls, lists, shared expenses, files and documents it made, research it ran, pages it opened, screenshots, the approvals you gave or declined, and receipts.
Website forms. If you join the waitlist or apply on our website, the email, name and answers you type in.
Requests to us. What you send when you contact us or ask lore to reach a human.

Information about other people

People in your chats. Everyone in a group with lore, including people who have not signed up for lore, is part of that group's messages and memory.
Visitors to a profile. Before someone chats on a member's public lore profile, we ask for their name and email, and a phone number only if they agree to be texted. Their email and phone number are encrypted and shown only to the profile's owner.
Invites. When you invite someone, vouch for someone, or ask for an invite, we keep who invited or vouched for whom and where the invite stands.

What we collect automatically

Technical data. IP address, browser and device type, and pages viewed on our website and dashboard, and the cookies needed to keep you signed in to your dashboard. We do not use advertising cookies or third-party ad trackers.
Service records. For each reply and task: timing, cost, which tools ran and whether it worked; how much AI usage each person has each day, so we can apply usage limits; and opt-out and safety records. These records do not contain your message text.
Counts. Our internal analytics are counts, such as how many people used lore this week or how often tasks finished. They do not contain message text, phone numbers or names.

How we use it

To run lore: hold conversations, remember context, answer questions, and do the tasks you ask for, then report back with what really happened.
To connect you with people you already know through lore, when you ask and they agree (see "Profiles, circles and asks between lores" below).
To send you messages you asked for or that help you, such as reminders, answers that arrive later, and at most one unprompted heads-up a day in your one-to-one chat. You can stop texts at any time.
To keep lore safe and working: prevent spam, scams and abuse, apply usage limits, fix problems, and measure reliability and cost.
To improve how lore handles websites: when an errand struggles, lore may write a general tip about that site or that kind of page for later errands. These tips are written without personal information.
To manage access to lore, such as the waitlist and invites, and to answer your requests.
To meet our legal duties and enforce our Terms.

We do not sell personal information. We do not share it for cross-context behavioral advertising or use it for targeted advertising, and lore does not show ads. We do not use your content to train AI models.

How lore's AI uses your information

lore is built on large language models. When a message reaches lore, the AI reads it together with the context lore keeps for that conversation (recent messages and the chat's memory and, in your own one-to-one chat, your personal profile and notes) and decides what you mean, whether to reply, and what to do. To do that, the text and any images it needs are sent to an AI model provider for that request.

No training on your content. We do not use your messages or memory to train AI models. When lore's requests go through OpenRouter, lore asks OpenRouter by default to use only model providers that do not store prompts or train on them.
Outside content is information, not instructions. Web pages, emails and documents lore reads are treated as data. lore will not send anything just because a page or an email told it to.
Real actions need your yes. lore asks for your approval before it sends an email, posts, books, pays or buys anything for you.
Private notes in a group. After lore answers you in a group, it may send you a separate private note that draws on what you told it one to one. That note goes only to you; the group's reply never includes your private context.
No decisions with legal effects. lore does not use your information to make decisions about you that have legal or similarly significant effects. When lore's AI judges whether someone might fit a request, people still decide for themselves.
It can be wrong. AI can misunderstand or remember something incorrectly. You can ask lore how it knows something, correct it, or tell it to forget it.

Groups, one-to-one chats and what others see

What you say in a group is visible to the people in that group and to lore. lore keeps each group's messages and memory with that group and does not use one group's memory in another group's replies.
What you tell lore one to one stays between you and lore. From your one-to-one chat you can ask lore about your own group chats, for example to catch up, and lore only uses groups you are in.
Information from your own connected accounts, such as your inbox or calendar, is sent to you privately rather than to a group.
The people who run lore can access stored data when needed to support you, keep lore safe, or fix a problem, and only for those purposes.

Profiles, circles and asks between lores

Your lore can ask other people's lores for help, and theirs can ask yours, but only with consent at each step.

Your profile is your choice. A public lore profile (a link to your page on lore) is published only when you say yes. It shows your name, your photo or initial, the line you chose, and the facts you chose to make public. You can change it or turn it off at any time. Anyone with the link can message your lore from it: your lore answers from what you made public and your free and busy times, and passes everything else to you. lore never confirms a meeting for you; you do.
Your circle. Your circle is the people you chose to have your lore ask first when you are looking for something. lore suggests people only from those you already share a chat with, at most one suggestion a day, and you decide who to add. Adding someone shares nothing with them. When you join lore, people who already share a chat with you may be told you joined, with only what you made findable.
Favors. If someone asks their lore to ask you something ("can you cover Friday?"), lore asks you privately, and only if you use lore and the asker already knows you through lore (a shared chat, a connection on lore, or their own notes about people they know). Your answer, in your words, goes back to them.
Intros and finds. When someone looks for a person ("who do I know who does growth marketing?"), lore looks only at people they share a chat with or are connected to through lore, and privately asks the person it picks whether they want the intro. Nobody's contact details go to the other side until that person says yes. In a wider search, a mutual contact's lore asks them first, and only their yes reaches the person they name.
Fit checks use your words privately. Before you are asked about someone's request, your own lore may check the request against what you have told it and decide whether it fits you, is clearly not for you, or is unsure. If it is clearly not for you, you are not asked. Only that result, and at most one short question and answer, pass between the two lores. The reason your lore gives stays with you, and the asker's lore is told to share only what the question needs, or nothing.
You stay in control. You can say no to any ask, and you can set standing rules for lore to turn certain asks down for you. There are daily limits on how many asks one person can send or receive.
Invites. lore is invite-only. If you ask for an invite, a member who knows you may be asked to vouch for you, and the people who run lore review requests. Members can see where the people they invited stand, shown by name or initials.

Google user data

Connecting Google is optional. By default lore asks only for basic sign-in (your email address) and access to the Google Drive files lore creates for you or that you pick yourself in Google's file picker; it cannot see anything else in your Drive. Where you turn them on and Google has approved them for lore, lore can also send email from your Gmail, read and organize your Gmail, see and add events on your Google Calendar and check your free and busy times, and read your Google Classroom courses, coursework and announcements.

lore uses Google data only to provide the features you ask for, and the results go to you. We do not sell Google data, use it for advertising, or use it to train AI models, and people do not read it except as needed to provide or secure the feature you asked for, with your permission, or when the law requires it. To produce an answer, the relevant content is sent to the AI model provider that writes lore's reply, for that request only. lore's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. You can disconnect Google on your dashboard at any time; that deletes lore's stored access to your account and asks Google to revoke it.

Calendar links, files and saved logins

If you paste your calendar's private iCal link on your dashboard, lore stores it encrypted, reads it only to answer your own questions about your schedule, never shows it back, and deletes it when you remove it.
Files and documents lore makes for you are reachable only through the private links it sends.
A saved login is typed on a private lore page, never in the chat, and stored encrypted. lore's code fills it into the website's sign-in form itself, so the password is not given to the AI model and is never shown in a chat. Showing a saved password again on your dashboard requires a recent sign-in. You can edit, test or remove any saved login at any time; removing it deletes it.

Who we share it with

We share personal information only as this policy describes. These service providers handle it on our behalf to run lore:

Hosting and storage. Amazon Web Services runs lore's servers in the United States, where lore's database is kept. Our website is hosted by Vercel.
Messaging. Sendblue delivers iMessage and text messages (on lines that use it, Photon does). They receive your phone number and the messages between you and lore. Slack carried lore's messages in Slack while lore was offered there.
AI models. OpenRouter, which routes requests to model makers such as Anthropic and Google, and, when we configure them, model providers used directly: Anthropic, Google (Gemini), Groq, Mistral, Cloudflare Workers AI and Baseten. They receive the text and images needed to write a reply or complete a task. To search a chat's own history, lore also turns its messages into search vectors with Cloudflare Workers AI or Mistral.
Web search and reading pages. OpenRouter's web search, Jina (which reads web pages for lore), DuckDuckGo and Wikipedia, and, when configured, Tavily, Exa and TinyFish. Search services receive the words of a search, which can reflect what you asked about. Public information services (such as the US National Weather Service, Open-Meteo, OpenStreetMap, ESPN, Yahoo Finance, Nasdaq and CoinGecko) receive only what is needed to look something up, such as a place name or a stock symbol.
Browsers for errands. A browser on our own servers or, when configured, a hosted browser service (Kernel, Steel, Browserbase or Browserless). They handle the pages lore opens for you, including sites you are signed in to.
Accounts you connect. Google, Slack and GitHub, when you connect them. Composio, only if lore connects your Gmail through Composio; Google's approval screen names Composio when it does.
Website forms. Answers to our waitlist and application forms are copied to a Google Sheet we use to manage access.

We also share information: with other people in the ways described in this policy that you start or agree to (a group sees what is said in it, and an intro shares contact details after both people say yes); when you ask lore to send something to someone; to comply with the law, a court order or a valid legal request; to protect the safety, rights or property of people and of lore, including to prevent fraud and abuse; and as part of a merger, acquisition or sale of the business, in which case we will tell you before your information becomes subject to a different privacy policy.

We do not sell personal information and we do not share it for cross-context behavioral advertising, as California law defines those terms. We do not share personal information with third parties for their own direct marketing.

How long we keep it

Chats and memory: kept while you or your group use lore, so it can keep remembering, until you or your group delete them. There is no fixed deletion date for these. lore stops using some facts it learned about you in a group after about 180 days, and sooner for things you said were temporary.
Pages lore read during an errand: stored encrypted and removed after 24 hours or when the errand ends.
Screen recordings and receipt screenshots from errands: deleted after 7 days.
Links lore's web tools found: kept for 2 days.
Service records without message text: per-reply timing and cost records are kept for 90 days.
Saved logins, calendar links and connected accounts: until you remove or disconnect them, or delete your account.
Website forms: until you ask us to delete them, or we no longer need them to manage access.
What we keep after a deletion: if you text STOP, your number stays on our opt-out list so you are not texted again, even after you delete your data. If someone is banned for abuse, the ban stays. Records of your approvals are kept as fingerprints (hashes), not as message text, and are deleted with your account.
Backups: deleted data can remain in backups for a limited time until they are replaced.

Your choices and controls

Delete what lore knows about you in a chat: say "lore forget me". This clears your personal profile facts in that chat without touching the group's shared history.
Delete a group's data: anyone in the chat can say "lore forget this group". After a confirmation, this permanently deletes every message, memory, profile, plan, list and task record stored for that chat.
Delete your data everywhere: say "forget me everywhere", or delete your account on your dashboard. After you confirm, this deletes your lore account and, in every chat, your messages and your one-to-one texts with lore, what lore remembers about you, your reminders, errands and goals with their screenshots, files and receipts, the documents lore made for you, saved logins and browser sign-ins, your calendar link and picked docs, your Google and GitHub connections (lore asks Google to revoke its access), and your lore profile and scheduling links. Other people's messages and each group's shared notes, polls and plans stay with the group; on shared lists and expense splits your name is replaced with a placeholder.
Download your data: on your dashboard you can download a copy of what lore holds for you.
Correct it: tell lore when it has something wrong, or edit your profile and memory on your dashboard.
Stop texts: text STOP to stop all messages from lore's number, and START to resume. You can also ask lore to go quiet in a chat.
Turn things off: turn off your public profile, remove saved logins, and disconnect Google, GitHub or your calendar link on your dashboard. You can also manage Google's access at myaccount.google.com/permissions.
Remove lore: remove lore from a group chat. If lore was installed in your Slack workspace, uninstall it there: uninstalling lore from a Slack workspace automatically deletes the stored data of every channel in that workspace.
Website forms: to delete what you typed into our waitlist or application forms, email privacy@loregroupchat.com from that address.

Your privacy rights

Depending on where you live, you may have the right to know what personal information we collect, use and disclose, and to get a copy of it; to correct it; to delete it; to receive it in a portable format; to opt out of its sale, of sharing for targeted advertising, and of profiling that has legal or similarly significant effects; to limit the use of sensitive personal information; and to appeal if we turn down your request. We do not sell or share personal information, use it for targeted advertising, or use it for that kind of profiling. We use sensitive personal information, such as account logins and the contents of messages and email, only to provide the service you asked for. We will not treat you differently for using your rights.

California. In the past 12 months we have collected these categories of personal information: identifiers (such as phone number, email, Slack IDs and IP address); customer records (such as name and contact details); commercial information (such as bookings or purchases you ask lore to make); internet and other electronic activity (such as use of our website and dashboard and records of errands); audio and visual information (such as photos and screenshots); professional or education information you share (such as your job, or Google Classroom data if you connect it); inferences (such as profile facts lore learns from what you say); and sensitive personal information (account logins, and the contents of messages and email lore handles for you). We collect it from you, from people in your chats, from accounts you connect, and from websites lore visits for you. We use and disclose it for the purposes and to the recipients described above, and we keep it for the periods described above.

European Economic Area, United Kingdom and Switzerland. We process personal information to provide the service you asked for (performance of a contract); for our legitimate interests in running, securing and improving lore, balanced against your rights; with your consent where we ask for it, for example to connect Google, publish a profile or agree to an intro, which you can withdraw at any time; and to meet legal obligations. You have the right to access, correct and erase your information, to restrict or object to its processing, to data portability, and to complain to your local data protection authority. Your information is processed in the United States, where data protection laws may differ from yours.

How to make a request. Use the controls above, email privacy@loregroupchat.com, or text lore "talk to a human". We verify a request by confirming it comes from the phone number, Slack account or email tied to the data. We aim to respond within 30 days, and always within the time the law allows. You can use an authorized agent, who must show your written permission; we may still ask you to confirm your identity. If we turn down your request, you can appeal by replying to our answer, and if you are not satisfied you can contact your state attorney general or data protection authority. Because we do not sell or share personal information, there is nothing to opt out of; we treat a Global Privacy Control signal from your browser as a request not to sell or share, which is how lore already works.

Security

Data travels to and from lore over encrypted connections. Saved logins, keys to connected accounts, calendar links, and profile visitors' contact details are encrypted at rest. Each chat's data is kept separate in code, and automated tests check that one group's messages never appear in another group's replies. Showing a saved password requires a recent sign-in, and access to stored data by the people who run lore is limited to supporting you, keeping lore safe and fixing problems. No system is perfectly secure. If a breach affects your information, we will notify you as the law requires.

Children and teens

lore is for people 13 and older. Nobody under 13 may use lore, and we do not knowingly collect personal information from children under 13. If we learn that a user is under 13, we will delete their account and their data and stop messaging them. If you believe a child under 13 is using lore, email privacy@loregroupchat.com and we will delete their information.

Teens 13 to 17 may use lore with the permission of a parent or legal guardian. If you are in a country that requires a parent's consent to use online services at your age, you need that consent to use lore. For everyone under 18:

Parents' rights. A parent or legal guardian can ask us to delete their teen's lore account and data, or ask us questions about it, by emailing privacy@loregroupchat.com. We will confirm that the request comes from the teen's parent or guardian before we act on it. Teens can also delete their own data at any time with the controls above.
No sale and no targeted ads. We do not sell any teen's personal information, share it for cross-context behavioral advertising, or use it for targeted advertising.
Removing what you posted. A teen can turn off or delete their public profile and anything they made public on lore at any time, or ask us to remove it.
No contact from strangers without consent. These protections apply to everyone on lore: nobody gets an intro to you or your contact details through lore without your yes; asks from other people's lores reach you only from people who already know you through lore, and they come to you privately; and you have no public profile unless you choose to publish one. If you do publish one, messages sent from it go to your lore first, which passes them on to you, and you can turn the profile off at any time.

Where we process information

lore is run from the United States. Your information is stored and processed in the United States and wherever our service providers operate, where data protection laws may differ from the laws where you live.

Changes to this policy

We may update this policy as lore changes. We will change the effective date above and, for material changes, tell you before they take effect, by text or on our website. Where the law requires your consent to a change, we will ask for it.

Contact us

Email privacy@loregroupchat.com, or text lore "talk to a human". lore, Sacramento, California.