RRackor
Sign in
Legal

Privacy Policy

Last updated: October 3, 2026 · Rackor Labs LLC

This policy explains what information Rackor collects when you use Rackor Model Intelligence or Betty, how we use and share it, and the choices you have. In short: we host your data for you, we never train models on your content, and we never sell your personal information.

1. Introduction

Rackor Labs LLC ("Rackor," "we," "us," or "our") is a Massachusetts limited liability company. We provide two hosted products (together, the "Services," and each a "Service"):

  • Rackor Model Intelligence ("RackorMI"): a web platform that lets you run and track large language model (LLM) benchmarks against any OpenAI-compatible model endpoint. You connect your own model endpoints (a base URL and API key, for example llama.cpp, vLLM, Ollama, OpenRouter, OpenAI, and other hosted providers), then choose or author versioned benchmarks and run them while keeping full transcripts, scores, and head-to-head comparisons. Rackor never resells inference or hosts models; you always bring your own endpoint and key.
  • Betty, hosted at betty.rackor.com: a personal memory manager for AI agents. Betty stores the people, organizations, facts, events, tasks, and notes you choose to keep, and lets AI apps you connect (such as Claude.ai, ChatGPT, or Claude Code) read and write that memory through the Model Context Protocol ("MCP") on your instruction. You can view, edit, export, and archive everything in your memory from the Betty web app. On the Betty Assistant plan, you can also email or text Betty to save to your memory and to ask about it.

Our marketing website is rackor.com. Each Service has its own accounts; a RackorMI account and a Betty account are separate. This Privacy Policy describes how we collect, use, disclose, and protect personal information in connection with the Services and our websites. It applies to visitors to rackor.com, to account holders of either Service, and to individuals whose information is submitted to us in connection with a Service. By using a Service, you acknowledge the practices described in this policy. This policy should be read together with our Terms of Service.

2. Workspaces, roles, and individual accounts

RackorMI is organized around workspaces. Where a workspace is administered by an organization (for example, your employer), that organization controls the workspace and its content, and we process workspace content on its behalf. If you are a member of such a workspace, requests concerning workspace content (benchmarks, transcripts, run results) may need to be directed to your workspace owner or admin, and we may refer your request to them. Your individual account details remain subject to your own rights under this policy.

Betty accounts belong to one person. There are no workspaces, teams, or shared accounts, and no other Betty user can see your memory. Because Betty is built to hold information about the people and organizations in your life, see the section on information about other people below.

3. Information we collect

Information you provide to us

We collect the information you give us directly, including:

  • Account details. Your name (RackorMI), email address, and password. Passwords are stored only as a cryptographic hash; we never store your password in plain text.
  • Billing details. Subscription plan, billing contact, and payment information. Payments are processed by Stripe (see the section on how we share information). Rackor does not store full payment-card numbers.
  • Communications. Information you provide when you contact us for support, respond to surveys, or otherwise communicate with us.

For RackorMI, we also collect:

  • Workspace and organization information. Details about the workspace you create or join, its members, and their roles (owner, admin, or member).
  • Benchmark content you author. The questions, prompts, sampling settings, scorer configuration, and related materials you create or upload to run benchmarks.
  • Connection settings. The endpoint URLs and API keys you supply so the Service can send prompts to the model endpoints you choose to connect.

For Betty, we also collect:

  • Memory content. The people, organizations, other entities, facts, events, tasks, and notes in your memory, whether you entered them in the web app, a connected AI app recorded them on your instruction, or you imported them from an export. Each record keeps its history: superseded facts, archived records, and earlier versions of notes, events, and tasks remain stored. Facts, events, tasks, and note revisions show who wrote them (the connected app or API token by name, you, or an import). Names, summaries, and profile details keep only their latest version.
  • Connected apps and tokens. The AI apps you authorize through OAuth and the API tokens you create, together with the name of each app and when it last connected. Tokens are stored only as a cryptographic hash.
  • Referrals. Your personal referral code, and, when an account is created through a referral link, which account referred it. We use this to add the referral months described in our Terms of Service and to apply their limit. We do not tell the person who referred you anything about your account beyond the number of months they have earned.
  • Betty Assistant email. If you use Betty Assistant, your private Betty Assistant address, any other email addresses of yours that you confirm, the emails you send to it (including the text of emails you forward), and Betty's replies. Attachments are ignored.
  • Betty Assistant text messaging. If you text Betty, the mobile number you link, your consent record (when you agreed to receive texts and the words you agreed to), the texts you send and Betty's replies, whether you have opted out, and your PIN, which we store only as an argon2id hash. A text that contains only your PIN is checked and then discarded at once.
  • Information about other people. Memory content is usually about people other than you: names, contact details, employers, preferences, birthdays, and what happened when. You decide what to store. See the section on information about other people below.

Information collected automatically

When you use a Service, we automatically collect certain information, including:

  • Prompts and transcripts (RackorMI). The prompts sent to the endpoints you connect and the responses and transcripts returned from them, along with the scores and run results generated when a benchmark runs.
  • Agent activity (Betty). A log of the requests each connected app or API token makes (which tool or endpoint, the app's name, and when), and one entry for each message Betty Assistant answers, used to operate and secure Betty. It does not record the content of requests. Your account shows when each app last connected, and your Home screen shows what apps wrote. This log is kept with your account and removed when you delete it.
  • Usage and log data. Records of actions taken in the Services, feature usage, timestamps, and diagnostic and error logs.
  • Device and connection data. Technical information such as IP address, browser type, and similar device and network information used to operate and secure the Services.

We use only strictly necessary session cookies for authentication and security. We do not use advertising cookies or third-party analytics. See the Cookies section below.

How we protect API keys, tokens, and connection secrets

RackorMI. We treat the endpoint URLs, API keys, and connection secrets you provide as highly sensitive. API keys and connection secrets are envelope-encrypted using AES-256-GCM and are write-only: after you save a key, only the last four characters are ever shown back to you. Connection secrets are never written to our logs, and Authorization headers and keys are redacted from any stored request or transcript.

Betty. Session cookies, API tokens, and the OAuth tokens issued to connected apps are stored only as SHA-256 hashes; the raw token is shown to you once and never stored. Tokens are accepted only in request headers, never in URLs, so they do not land in access logs. You can disconnect an app or revoke a token at any time from your account settings, which takes effect immediately.

4. How we use information

We use the information we collect for the following purposes:

  • Providing and operating the Services: creating and managing accounts and workspaces; for RackorMI, connecting your endpoints, running benchmarks, and storing transcripts, scores, and comparisons; for Betty, storing your memory, searching it, serving it to the apps you connect, and reading and answering the emails and texts you send to Betty Assistant.
  • Billing and account management: processing subscriptions and credit usage, calculating taxes, and maintaining billing records.
  • Support and communications: responding to your requests and sending account, verification, password-reset, security, and billing-related messages.
  • Security, fraud prevention, and legal compliance: protecting the Services and our users, detecting and preventing abuse, and complying with applicable law.
  • Maintaining and improving the Services: diagnosing problems, understanding how features are used in aggregate, and developing new features.
  • Community features (RackorMI): publishing benchmark versions to the community as described below, consistent with your plan and your choices.

We do not use your prompts, transcripts, questions, scores, or memory content to train any models. See the next two sections for details.

5. RackorMI: prompts, transcripts, and connected-endpoint data

RackorMI sends the prompts in a benchmark run to the endpoints you connect. Because you bring your own endpoint and API key, the provider operating that endpoint (for example, OpenAI or OpenRouter) receives the prompts you send and processes them under its own terms and privacy policy, not this one. We encourage you to review the policies of any provider you connect.

Some AI-assisted features that Rackor operates directly (such as AI-generated benchmark questions) do not use a connected endpoint. Instead, they route to a default model provider that Rackor configures, currently OpenRouter, which processes that content as our subprocessor under our agreement with it. Content sent through these features is not used to train any models.

Your customer content, including the questions, prompts, transcripts, and scores associated with your workspace, is not used to train any models. Your own transcripts and per-question results always remain visible to you and stay private to your workspace.

Community publishing

RackorMI includes an optional community corpus where users can share benchmark versions. Whether sharing happens automatically or only deliberately depends on your plan:

  • Community-visible plans (Free, Free-with-card, and Individual). When a user publishes a benchmark version, it is automatically listed to the community. We display a notice at the point of publishing so this is clear before you act.
  • Private plans (Pro and Enterprise). Sharing to the community happens only deliberately, when a workspace admin chooses to publish.

When a benchmark version is shared to the community, the following is made available:

  • the prompt template and sampling defaults;
  • the scorer type (but not the full scorer configuration);
  • the question rows, with the answer key sealed and never published;
  • the publisher's username; and
  • an aggregate leaderboard.

The following is never shared to the community:

  • the gold or expected answers and accepted-answer lists (the "sealed answer key");
  • the full scorer configuration;
  • transcripts; and
  • per-question pass/fail results.

To be clear about what this means: answer keys are not published. A user's own transcripts and per-question results always stay visible only to that user and remain private to the workspace.

Unpublishing. You (or your workspace admin) can unpublish a benchmark version at any time from the Service, which removes it from the community listing. Copies that other users made while it was published may persist in their workspaces, and cached or archived copies outside our control may remain available. If you want your username removed from a past publication, contact privacy@rackor.com.

Connected AI apps

Betty exposes your memory to the AI apps you choose to connect. Apps such as Claude.ai and ChatGPT connect through OAuth after you approve access on a consent screen; Claude Code and other developer tools connect with an API token you create. Once connected, an app can search, read, and write your memory through MCP whenever you use it. Every request is made by the app on your behalf, and Betty records which app or token wrote each fact, event, task, and note revision. Over MCP, a connected app can supersede a fact but cannot delete, archive, or merge records. An API token can also use Betty's REST API, which can archive and merge records, remove aliases, and export or import your memory; it cannot delete your account or manage your tokens.

A connected app is operated by a third party (for example, Anthropic for Claude.ai and Claude Code, or OpenAI for ChatGPT). Whatever that app reads from your memory is processed by its operator underits own terms and privacy policy, not this one. We encourage you to review the policies of any app you connect. Rackor does not send your memory to any app except in response to a request from an app you have authorized. Betty does not connect to your calendar, contacts, or mailbox. Betty Assistant receives only the emails and texts you send to it, and it reads your Betty memory to save what they say and to answer your questions.

Semantic search

Betty's keyword search runs entirely within Betty. Semantic search, which finds records by meaning, is a feature of Betty Standard and Betty Assistant. To provide it, Betty sends the text of each record in your memory, and each search query, to OpenRouter, which returns numeric vectors from an embeddings model; Betty stores them alongside your records. For longer searches, Betty may also send the query and the closest matching records to a ranking model through OpenRouter. OpenRouter processes this text as our subprocessor, and Betty's requests go only to model providers that keep no data (zero data retention). Every new account has Betty Standard for its first 30 days, and for any referral months, so semantic search is on during that time. On the Free plan, nothing from your memory is sent to OpenRouter: your records and your queries stay in Betty. When your free time ends or you cancel, semantic search stops and no further text is sent.

Your memory content is not used to train any models, by Rackor, OpenRouter, or the model providers it uses.

Betty Assistant: email and text messages

Betty Assistant is part of the Betty Assistant plan. When you email or text it, an AI model reads your message and uses Betty's own tools, in your account only, to save what it describes and to look up what you ask about. The model is reached through OpenRouter, which receives the text of your email or text (including any email you forward) and the memory content those tools return. The model never receives the text of your notes; replies link to a note instead. As with semantic search, these requests go only to model providers that keep no data (zero data retention) and do not train on it. Resend receives the emails you send to your Betty Assistant address and sends Betty's replies. Bird delivers and receives texts, and sends the code that links your number, so it receives your mobile number and the content of your texts and Betty's replies.

Betty reads an email only when it comes from your account's address or another address of yours that you confirmed, and your email provider has signed it. A text, on the other hand, shows only the number it came from, and a number can be faked or moved to another phone. So until you text your PIN, Betty only saves from your texts, and its reply lists only what it saved. After the right PIN, it answers questions by text for the unlock time you choose. Betty replies only to your own email address or your linked number, and it ignores texts from numbers that are not linked.

No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging opt-in data and consent are not shared with any third parties, except service providers that deliver the messages. You can text STOP at any time to stop all texts, as described in our Terms of Service.

Information about other people

Betty is designed to hold information about the people and organizations you interact with. You decide what goes into your memory, and Rackor stores and serves it on your behalf as a service provider. You are responsible for storing information about other people only where you are permitted to do so, and for keeping it accurate. If someone contacts us about information a Betty user holds about them, we may refer them to that user, and we will respond as required by applicable law.

7. How we share information

We do not sell personal information, and we do not share personal information for cross-context behavioral advertising. We share information only in the limited circumstances described below.

No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging opt-in data and consent are not shared with any third parties, except service providers that deliver the messages. Nothing else in this section changes that.

Service providers (subprocessors)

We rely on a small number of vendors to operate the Services. Each processes information on our behalf and under contractual obligations to protect it:

  • Cloud hosting (both Services). The applications and databases are hosted on Heroku (a Salesforce company) in the United States.
  • Web hosting and delivery (both Services). Cloudflare hosts rackor.com and provides content delivery and network security for the Services' websites.
  • Payments (both Services). Stripe processes payments and subscriptions. For RackorMI, Stripe Tax also handles sales-tax calculation. Rackor does not store full payment-card details.
  • Transactional email (both Services). Resend sends account, verification, password-reset, and billing emails on our behalf, and, for Betty Standard, the task reminder and digest emails, which are on by default and can be turned off in your account. Those emails include the task, event, and birthday details they remind you about. For Betty Assistant, Resend also receives the emails you send to your Betty Assistant address and sends Betty's replies.
  • Default AI inference (RackorMI). For AI-assisted features that Rackor operates directly (such as AI-generated questions), OpenRouter routes requests to model providers on our behalf. This does not apply to the endpoints you connect yourself, which you operate under your own agreements.
  • Semantic search (Betty Standard). OpenRouter converts memory text and search queries into vectors, and may rank search results, as described in the Betty section above. Betty accounts on the Free plan do not use it.
  • Betty Assistant inference. OpenRouter routes the emails and texts you send to Betty Assistant, and the memory content Betty's tools return, to an AI model, as described in the Betty section above.
  • Text messaging (Betty Assistant). Bird (formerly MessageBird) delivers and receives Betty Assistant texts and sends the code that links your number. It receives your mobile number and the content of your texts and Betty's replies.
  • Company email (both Services). Google Workspace hosts our email and internal communications, including messages you send to rackor.com addresses such as privacy@rackor.com.

We maintain a current list of subprocessors at rackor.com/legal/subprocessors and will update that page before adding or replacing a subprocessor.

Apps and endpoints you connect

The model endpoints you connect to RackorMI and the AI apps you connect to Betty are your choice and act on your instruction. They are not our subprocessors. Information they receive is governed by their own terms, as described in sections 5 and 6.

Legal and safety disclosures

We may disclose information if we believe in good faith that it is necessary to comply with a law, regulation, legal process, or governmental request; to enforce our Terms of Service; or to protect the rights, property, or safety of Rackor, our users, or others. Where legally permitted, we will notify affected users before disclosing their information in response to legal process.

Business transfers

If Rackor is involved in a merger, acquisition, financing, reorganization, or sale of all or part of its assets, information may be transferred as part of that transaction, subject to this policy. Text messaging opt-in data and consent are not transferred to anyone other than the service providers that deliver the messages.

Community sharing (RackorMI)

Where you or your workspace publish a benchmark version to the community, the limited information described in section 5 is made available to other users, consistent with your plan and choices. Betty has no community or sharing features; your memory is visible only to you and the apps you connect.

8. Cookies

We use only strictly necessary cookies: specifically, a session cookie used for authentication and security. We do not use advertising cookies, we do not use third-party analytics, and we do not engage in cross-context behavioral advertising. Because these cookies are essential to providing the Services, they are not used for tracking you across other websites, and disabling them may prevent you from signing in or using a Service.

Because we do not sell or share personal information or use cookies for tracking, browser-based opt-out preference signals such as Global Privacy Control do not change how the Services operate; there is no sale or sharing to opt out of.

9. Data retention and deletion

We retain personal information for as long as needed to provide the Services and for the legitimate and legal purposes described in this policy. Specific retention periods include:

  • RackorMI transcripts are retained according to your plan: Free, 30 days; Pro and Enterprise, 365 days; Individual, indefinitely. After the applicable period (where one applies), transcripts are pruned. You can also delete transcripts and runs manually at any time before the retention period ends, or at any time on plans with indefinite retention.
  • RackorMI scores and aggregate results are kept for as long as the associated workspace exists, so historical comparisons remain accurate.
  • Betty memory content is kept for as long as your account exists. Betty does not prune your memory on a schedule. When a fact is superseded or a record is archived, the earlier version stays in your history so you and your agents can see what changed. You can export your entire memory at any time as a zip containing a readable Markdown copy and a JSON copy that can rebuild the account.
  • Betty Assistant messages. The text of the emails and texts you send to Betty Assistant, and of its replies, is kept for 30 days after the last message in that conversation, then cleared. A message Betty ignores keeps no text, and its record is deleted after 30 days. Betty keeps a record of each answered message (when it came, whether it was an email or a text, the number a text came from, and what Betty saved) until you delete your account. These messages are not part of your export. What Betty Assistant saved to your memory stays in your memory like anything else. Resend and Bird keep their own records of the messages they deliver, under their own retention policies.
  • Your linked phone. Removing your phone in the app deletes the linked number, its consent record, and your PIN (records of answered texts keep the number, as above), and Betty ignores texts from that number from then on. Texting STOP stops all texts to your number until you text START.
  • Usage, diagnostic, and connection logs are retained for up to 12 months, then deleted or aggregated. Betty's per-account agent activity log is kept with the account and removed when the account is deleted.
  • Account and billing records are kept as needed to meet our legal, tax, and accounting obligations.

Account and workspace deletion. You can delete your account from your account settings, and a RackorMI workspace owner can delete a workspace. Deleting a Betty account erases your memory, its history, your connected apps and tokens, and the agent activity log, and cancels any Betty subscription. It also deletes your Betty Assistant address, other addresses, linked phone, consent record, PIN, and messages. We keep a one-way hash of the Betty account's email address, with no other data and no link to the deleted account, so that each email address receives the 30 days of Betty Standard described in our Terms of Service only once. When you delete an account, we delete or de-identify the associated personal information within 30 days, except for records we are legally required to keep (such as billing and tax records) and limited backup copies, which are overwritten on our standard backup cycle. RackorMI benchmark versions previously published to the community are handled as described in the Community publishing section.

10. Security

We use technical and organizational measures designed to protect personal information. Our primary datastore for each Service is PostgreSQL. Data in transit is protected with TLS, and data at rest is encrypted.

RackorMI. Sessions are managed server-side and stored in Postgres. The session cookie carries only an opaque token; we store a SHA-256 hash of that token and never the raw token. Sessions are revocable, and a member's authority is re-derived on every request, so removing or demoting a workspace member takes effect immediately. As noted above, API keys and connection secrets are envelope-encrypted with AES-256-GCM, are write-only, and are never logged.

Betty. Passwords and Betty Assistant PINs are hashed with argon2id. Session cookies, API tokens, and OAuth tokens are stored only as SHA-256 hashes and are never accepted in URLs. Every request is scoped to the signed-in account, and requests from origins we have not allowed are refused. Writes to notes and events are version-checked, so a connected app working from a stale copy cannot overwrite an edit you made. Betty does not currently apply field-level encryption to memory content beyond the protections of the hosting platform.

We maintain a written information security program consistent with the Massachusetts data-security regulations (201 CMR 17.00). If a security incident affects your personal information, we will notify you and the relevant regulators as required by applicable law, including the Massachusetts breach-notification statute (M.G.L. c. 93H).

No method of transmission or storage is completely secure, and we cannot guarantee absolute security.

11. Your privacy rights

Depending on where you live and applicable law, you may have rights to access, correct, update, or delete personal information we hold about you, and to request a copy of certain information in a portable format. You can exercise many of these choices directly in the Services (for example, by editing your account or workspace settings, exporting your Betty memory, or deleting your account) or by contacting us at privacy@rackor.com.

We extend the core rights described in this section (access, correction, deletion, and portability) to all users of the Services, regardless of where you live. We will respond to verifiable requests within 45 days (extendable once, with notice, where the law allows). If we decline a request in whole or in part, we will explain why, and where applicable law provides an appeal process, you may appeal by replying to our response; we will answer appeals in writing within 60 days. In some cases we may need to retain certain information to comply with our legal obligations or for legitimate business purposes, such as maintaining billing records.

We will not discriminate against you for exercising any of these rights.

12. US state privacy rights (including California)

This section supplements the rest of this policy for residents of US states with comprehensive privacy laws, including the California Consumer Privacy Act as amended by the California Privacy Rights Act (the "CCPA"). Some of these laws apply only to businesses that meet certain revenue or data-volume thresholds; we honor the rights below for all US residents regardless of whether a given law applies to us.

Categories of personal information we collect

In the preceding twelve months, we have collected the following categories of personal information:

  • Identifiers: such as name, email address, mobile number (for Betty Assistant texting), and IP address.
  • Commercial information: such as subscription plan, credit usage, and billing records.
  • Internet or other electronic network activity: such as usage, log, and device data, and the Betty agent activity log.
  • Customer content: the benchmark content, prompts, transcripts, and scores you submit or generate through RackorMI, and the memory content you or your connected apps store in Betty, and the emails and texts you send to Betty Assistant, which may include personal information about other people.
  • Account credentials: a hashed password; for RackorMI connected endpoints, encrypted API keys and connection secrets; for Betty, hashed API and OAuth tokens and a hashed Betty Assistant PIN.

Purposes and sources

We collect this information from you directly, from the apps and endpoints you connect, and automatically through your use of the Services, and we use it for the business purposes described in the How we use information section. We disclose personal information to the service providers listed in the How we share information section for those business purposes. We retain each category for the periods described in the Data retention and deletion section.

No sale or sharing; no sensitive-PI profiling

We do not sell personal information and we do not share personal information for cross-context behavioral advertising, as those terms are defined by the CCPA and similar state laws. We do not use or disclose sensitive personal information for the purpose of inferring characteristics about you, and we do not engage in profiling that produces legal or similarly significant effects.

Your rights

Depending on your state, you have the right to:

  • know and access the personal information we have collected about you;
  • request deletion of your personal information, subject to legal exceptions;
  • request correction of inaccurate personal information;
  • obtain a portable copy of personal information you provided to us;
  • opt out of the sale or sharing of your personal information and of targeted advertising (although, as noted, we do not sell or share personal information or engage in targeted advertising); and
  • appeal a refusal to act on your request, where your state's law provides an appeal right.

We will not discriminate against you for exercising any of these rights. To submit a request, email privacy@rackor.com. We will take steps to verify your identity before acting on a request. You may use an authorized agent to submit a request on your behalf; we may require the agent to provide proof of authorization and may ask you to verify your own identity directly.

13. International users

The Services are operated from the United States, and the information we collect is processed and stored in the United States. If you access a Service from outside the United States, you understand that your information will be transferred to and processed in the United States, where data-protection laws may differ from those in your jurisdiction. The Services are designed for a United States audience. If we later offer the Services in the European Union or the United Kingdom, we will add region-specific terms (such as a GDPR/UK GDPR notice) as required.

14. Children's privacy

The Services are intended for adults and are not directed to children. You must be at least 18 years old to use a Service. We do not knowingly collect personal information from anyone under 18. If we learn that we have collected such information, we will take steps to delete it.

15. Changes to this policy

We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date at the top of this page. For material changes, we will provide advance notice (for example, by email or a prominent notice in the Services) before the changes take effect. Non-material changes take effect when posted. Your continued use of a Service after an update means you acknowledge the revised policy.

16. Contact us

If you have questions about this Privacy Policy or our privacy practices, contact us at privacy@rackor.com or by mail at:

Rackor Labs LLC
82 Wendell Lane, Ste 100
Pittsfield, MA 01201
United States