ChabadLabs builds tools for shluchim. Some of them hold notes about real people, congregants, families, donors. This page says plainly what is stored, for how long, who can see it, and how to get it out or get it deleted.
Last updated 22 October 2026. Applies to this website and to the Chabad connector (mcp.chabadlabs.ai and mcp.shluchimexchange.ai). The Shluchim Exchange web app is a separate service and is not covered by this page. ChabadLabs is a project of Merkos 302, Inc. Merkos 302 also publishes a privacy policy for its websites generally; where that policy and this page differ, this page governs for this website and the connector.
An internal identifier linked to your sign-in account. Sign-in is handled by our identity provider, which holds your sign-in credentials.
Notes about people you work with, files, and scheduled tasks, stored under your account. Today an assistant such as Claude or ChatGPT cannot save notes or files on the connector. The Shluchim Exchange app can create scheduled tasks here, and we describe notes and files on this page in advance, so that nothing about them changes when they open. A note may hold a person's name, email address and phone number, and what you have recorded about them, which can include their religious life, their family and their health. This is the most sensitive material we hold, because much of it describes people who are not our users. You can see what is stored under your account, remove a record from view, and ask us to erase it.
One line per tool call: the time, your identifier, which tool, a one-way hash of the question, how many results, how long it took, whether it succeeded, which AI client you used (Claude, ChatGPT, our own Shluchim Exchange app, and so on) and which of our addresses you connected to. The connector's application records hold no IP address and no text of your question. We use these records to run the service: rate limits, abuse prevention, and counting which tools get used so we can improve them. We also use them, in aggregate, to see which tools and skills work well, so we can improve them for everyone.
Written answers. When you ask for a written, cited answer rather than a plain source lookup, the question you asked and the answer produced are kept by our Torah content service, so that the answer can be reopened, checked, corrected and improved.
This website uses Umami for visit counts, a service designed to work without cookies. We do not sell data. Neither this website nor the connector shows advertising, and we use no advertising cookies or tracking pixels.
If you use the connector without an account, the connector's application records hold no IP address and no text of your question. In place of your address we keep a short keyed code: a truncated, keyed, pseudonymous identifier made from your network address and a secret only we hold. It stays the same while that secret is in use, which is what lets us count requests and apply rate limits; without the secret it cannot be turned back into an address. In place of your question we keep a one-way fingerprint of it. The same question always gives the same fingerprint, so repeated questions can be matched, and a very short or common question could in principle be guessed from its fingerprint. We treat these records as pseudonymous, not anonymous.
Visitors without an account can use the read-only lookup tools. Saved notes, files and schedules are served only to signed-in accounts.
On every search, with or without an account, your question is passed to our Torah content service so it can be answered. If you have no account, that service does not send the question to an AI model provider while it searches. If you are signed in and the question is written mostly in Latin letters, the service sends it to Anthropic, through Amazon Web Services, to translate it, and for some questions sends it there again to draft a passage to search with. A question written mostly in Hebrew is not sent to a model provider during a search. Choosing which part of the library to search stays on the service's own servers. When it writes a cited answer, it sends the question out. Section 06 names the providers.
Notes, files and schedules are kept while your account is open. Archiving is a view setting, not deletion. When an account is closed, write to us and our staff delete everything tied to it by hand; there is no automatic purge yet, and we will tell you when it is done.
Kept as long as needed to run the service; there is no fixed retention period yet, and we will state one here when there is. Counts that contain no per-person rows (for example, how often a tool was used in a month) may be kept longer.
An upload that is started and never completed becomes eligible for deletion after 24 hours and is removed by an automatic storage rule within about two days.
Written answers and feedback. The question and answer of a written answer, and any feedback you send on an answer, are kept by our Torah content service for as long as needed to check and improve answers; there is no fixed period yet. Ask us and our staff delete them, by hand.
Information that no longer identifies you or anyone you work with (counts, patterns, and know-how with the identifying details removed) may be kept after your account is closed, because it cannot be traced back to a person.
Export. Ask us and our staff will put together an archive of everything tied to your account (your saved notes, your files, your schedules and your usage records, and the written answers and feedback kept by our Torah content service and in our feedback spreadsheet) and send it to you. This is done by hand today, not by a button. Write to ai@merkos302.com.
Deleting your account. On a verified request our staff permanently delete everything tied to your account, including uploaded files, the written answers and feedback kept by our Torah content service, and any copy in our feedback spreadsheet, and confirm to you when it is done. There is no automatic deletion yet.
If you are not our user and you are in someone's notes. A shliach using our tools may have saved notes about you. For permanent deletion, write to us at ai@merkos302.com: we will tell the shliach who holds the record and, if they do not act, permanently delete it ourselves; today our staff do this by hand. Removing a record from view is not the same as erasing it, and when you ask us to erase it we mean permanent deletion.
The shliach who saved a record controls it. We hold it on their behalf.
Staff access to production data is limited to fixing an incident, investigating abuse, running a migration, or meeting a legal obligation. We protect what we hold with the controls we actually run: all traffic to the connector travels over HTTPS; the database and file storage are encrypted at rest; the credentials that open them are held in a secrets store and used by the running service and a small number of operators; service logs are kept for one week and database backups for seven days, so a deleted record can survive in a backup for up to a week. No system is perfectly secure, and we do not promise that ours is. If you believe your account has been compromised, write to us.
How we use what we learn. We use information about how the service is used (the skills, instructions, templates and workflows you create, which tools you use and how, and the feedback you give) to operate, improve and develop the service and new features. Details that identify you or the people you work with are removed before anything is reused for others.
What we never use this way: your notes about people, and anything in your files or elsewhere that describes a third party. Those are used only to serve you.
De-identified, aggregated information (counts and patterns that cannot be traced to a person) is not personal information, and we may use and share it for any purpose, including research and reporting.
Our staff may review how the service is being used (including skills you create and feedback you give) to improve quality, provide support, or investigate abuse. The Chabad connector and the Shluchim Exchange app are both run by Merkos 302 and serve the same account; information moves between them, each under its own policy.
We use providers to run the service. They process data on our instructions and under contract, and currently include:
Hosting, database and file storage.
Sign-in and account identity.
Visit counts for this website; a service designed to work without cookies.
Answers source lookups and writes cited answers. It receives your question and an opaque identifier in place of your name or email. For written answers it keeps the question and the answer, as described above.
Our Torah content service sends your question, and the passages it finds, to an AI model provider to write a cited answer. During a search, it sends the question to Anthropic, through Amazon Web Services, only when you are signed in and the question is written mostly in Latin letters, to translate it and, for some questions, to draft a passage to search with. A search without an account, or of a question written mostly in Hebrew, does not send it. Today the provider is Anthropic, reached through Amazon Web Services. The service can be set to use others (Google's Gemini, or providers reached through OpenRouter, a routing service) and if that changes, this page changes with it. For a written answer, they receive the question and the passages, with an opaque identifier in place of your name or email.
If you send feedback on an answer, what you send (a rating or verdict, your comment, the answer or source you expected if you give one, and whether the feedback came from you or from the assistant) is kept with the answer by our Torah content service, and may also be copied to a private spreadsheet so we can find and fix bad answers.
Legal requests. We may disclose information when the law requires it (for example in response to a subpoena or court order) or when necessary to protect the rights or safety of our users, of the people in their notes, or of others.
If you connect our tools to an AI assistant such as Claude or ChatGPT, that assistant is run by its own company under its own privacy policy. What you type there is governed by their terms; what their assistant passes to our tools is covered by this page.
Privacy questions, export requests, deletion requests, or a correction to this page: ai@merkos302.com. By post: Merkos 302, Inc., 770 Eastern Parkway, Suite 302, Brooklyn, New York 11213.
ChabadLabs is a project of Merkos 302, Inc. Our tools are for adults doing the work of shlichus. They are not directed to children under 13, and we do not knowingly collect personal information from a child under 13; if you believe a child has given us information, write to us and we will delete it. We may email account holders about the service itself (changes, outages, new capabilities) and about Chabad programs and opportunities. If Merkos 302 reorganises or hands this service to another Chabad institution, your data goes with it under this policy.
Changes to this policy. When our practices change, this page changes and the date at the top moves; visitors using the connector without an account are covered by the notice on this page. Using the connector or this site after the date at the top means the current version applies.