Privacy policy
How your information is handled when you use RaLHF and our website.
Last updated 30 October 2026
The short version
Your library
You choose the context you add. We store it in the cloud and process it so you and your authorized AI apps can use it. You can review, export or delete it.
How it is used
Bot Food does not use your context for advertising or model training. Cloud and AI providers help run the service. The AI apps you connect have their own privacy terms.
Encryption and processing
Your cloud library is encrypted in storage and during transfer. Our systems can read it to organize it and provide context to your AI. This is not end-to-end encryption.
Account and diagnostics
Your account requires an email address. The app reports crashes and basic usage events. Google Analytics runs only if you accept it in the cookie banner. A simple visit counter runs for everyone and stores nothing that identifies you.
Who we are
RaLHF is made by Bot Food Corporation, a company based in Toronto, Canada. We are responsible for the personal information under our control. Our practices are designed to comply with the Personal Information Protection and Electronic Documents Act (PIPEDA) in Canada and corresponding provincial privacy legislation.
For anything in this policy, write to info@botfood.ai.
Conversations with your AI
Your conversations with AI apps are not automatically added to your library. You can choose to add them as a source.
What we do collect
When you create an account. Your email address.
When you use RaLHF. The context you add to your cloud library, so we can serve it to you and the AI apps you authorize. It is encrypted in transit and at rest, but readable by our systems, as explained below.
If you contact us. Whatever you put in the message, so we can answer it.
The newsletter form. Signup forms load from MailerLite when you visit the website. MailerLite receives your IP address and browser information and may use cookies to operate the form. If you subscribe, it also processes the details you submit.
Google Analytics, with your consent. We use Google Analytics to understand pages visited and how visitors arrive. Cookie preferences control analytics. Read the cookie policy for details and use Cookie settings in the footer to change your choice.
Visit counts, for everyone. The website keeps daily totals of page views, unique visitors, the pages people arrive on, the site or campaign they came from, and clicks on the download and newsletter buttons. It uses no cookies and nothing is stored in your browser. To count unique visitors, your IP address and browser details are combined with a random value that changes every day and turned into a one-way code. Only the code is kept, for up to two days. The daily value is deleted at midnight Toronto time, so codes cannot be linked across days or traced back to you. We never store your IP address or browser details. These counts run whether or not you accept analytics cookies.
Crash reports and usage analytics
RaLHF reports errors and basic product analytics so we can find crashes and understand which features people actually use. We use Sentry for error reporting and Amplitude for product analytics.
What this covers: which screens and features are opened, whether an action succeeded or failed, app version, operating system and device type, and the technical detail of any crash.
Diagnostic reporting is separate from the library storage and AI processing described in this policy.
Why we use it
- To run your account and deliver the features you use
- To answer your questions and fix problems you report
- To meet legal and tax obligations
We do not use your information to build advertising profiles, and we do not sell it. Bot Food does not use your context to train AI models. The AI apps you connect have their own terms for the context they receive.
Who we share it with
We use service providers for cloud hosting, AI-assisted connection setup and context organization, email delivery, error reporting and product analytics. These services receive the information needed for their role. If you join our mailing list, MailerLite processes your signup information.
Some of these providers operate outside Canada, which means your information may be processed in other countries and may be subject to the laws of those countries.
We will disclose information if required by law.
How your cloud library is processed
Your library is encrypted in cloud storage and during transfer. Our systems read it to organize it and provide relevant context to the AI apps you authorize. This is not end-to-end encryption.
Connected AI requests are checked against your account and library permissions. RaLHF also processes context to operate and organize your library, including through AI service providers. Bot Food does not sell your context or use it to train models. Connected AI apps handle what they receive under their own terms.
You can review, export, or delete your context from your account.
When you connect an AI
You choose which AI apps can access your library and can revoke that access at any time. Their privacy policies govern the context they receive. Disconnecting an AI stops future access; it does not erase copies already received.
How long we keep it
We keep your account information and library while your account is open, subject to your deletion choices. Account deletion revokes access and starts removal of saved content. Backup copies and records needed for legal, tax or accounting purposes have separate retention requirements. Deletion cannot recall copies already shared or sent to another AI.
Your rights
You can export or delete your library from your RaLHF account without asking us.
For any information we do hold, you can ask us to show you what it is, correct it, or delete it. Write to info@botfood.ai. If you are in the European Economic Area or the United Kingdom you have rights under the GDPR including access, rectification, erasure, restriction, portability and objection. If you are a California resident you have rights under the CCPA including the right to know, delete, and opt out of sale. We do not sell personal information.
Security
Your cloud library is encrypted in storage and during transfer. Access to production systems is restricted to staff who need it, authenticated, and logged. Context requests are checked against the authenticated account and its library permissions. No system is perfectly secure, and we will notify affected users and the relevant regulator if a breach occurs that presents a real risk of significant harm.
Changes
We will post any changes here with a new date at the top. If a change materially reduces the protection of information we already hold, we will ask before applying it to that information.