On this page
SQrL (pronounced as "squirrel") is an AI-powered co-pilot built by SingleStore that answers your questions and helps you code faster (in the context of SingleStoreDB).
In the Question and Answer mode, SQrL can answer questions and provide code suggestions for both the SingleStoreDB Cloud and SingleStoreDB Self-Managed deployments.
SQrL is designed to provide immediate and relevant responses to SingleStoreDB-related questions.
SQrL may sometimes return reasonable-sounding but inaccurate responses.
You can use SQrL in the Question and Answer mode on the SQrL website even if you are not a member of any SingleStoreDB organization.
In the Question and Answer mode, SQrL answers the user's queries (questions).
To use SQrL in Turbo mode for faster responses, enable the Turbo mode toggle switch.
You can also provide feedback on SQrL responses to help improve its accuracy.
To share a SQrL discussion, select Share.
Select Clear to clear the current discussion.
This section focuses on privacy practices, data collection, data security, and data retention in the context of SQrL only.
SingleStore collects and processes data from SQrL to provide the service.
SingleStore collects prompts, answers, and user engagement metadata from SQrL as follows:
A prompt is the contextual information that SQrL gets when a user asks a question/query.
Prompts are transmitted in real-time and retained to improve our product and documentation on questions asked by users.
SingleStore retains responses/answers from SQrL to improve the user experience of our product.
User Engagement Metadata
When you use SQrL, it collects user engagement data.
This data consists of usage information and events generated while interacting with SQrL. These events include, but not limited to: user actions like Thumbs up or Thumbs down, feedback, and feature engagement.
SingleStore shares the data collected from the SQrL discussions with the following AI providers (via API):
The data shared with these AI providers is NOT used to train their AI models.
Refer to Security for information.
Last modified: November 14, 2023