Privacy Policy

• Your message (up to 4,000 characters)
• The last 8 turns of the conversation (up to 2,000 characters each)
• Your settings: chosen agent, Chat or Swarm mode
• In Swarm mode, the browser sends several steps (plan, run, review, combine) that include your message and the AI’s intermediate drafts
• Attachments you add (optional): photos and images, resized in your browser and sent as JPEG (up to 4), and the text of documents (PDF, Word .docx, Excel .xlsx, PowerPoint .pptx, text and code files; up to 40,000 characters; for spreadsheets, also the column totals your browser calculated). The text is extracted in your browser; the original files are not uploaded. For a scanned PDF with no text, up to 3 page images are sent instead.
• In Swarm mode, images go only to the planning step. The other steps get a short description of the attachments and document excerpts of up to 12,000 characters.
• Requests with attachments are sent to QSI’s AI services, never to the backup providers.
• Attachment contents are sent only with the message you attach them to. Later messages in the same chat include only the names of earlier attached files as part of the recent conversation.

• Your voice, streamed from your browser through QSI’s voice relay to QSI’s AI services while voice mode is open, and QSI’s spoken replies streamed back
• Instructions and settings for the conversation, prepared by our server: QSI’s speaking style, your chosen voice (Rads or Mayur), agent, voice-input language and live-voice speed, and, if you start voice mode inside an existing chat, the last messages of that chat (as text) so QSI knows the context: your browser sends up to the last 8 turns of up to 1,200 characters each, and our server uses all of them, with or without an account
• A written transcript of both sides, produced by the AI service and shown on screen as captions (on by default; you can turn them off)
• For everyone, with or without an account: web searches run by the AI service during the conversation, based on what you said, when you ask about something time-sensitive. The only location hint QSI gives the AI service is country India and time zone Asia/Kolkata.
• For everyone, with or without an account: text cards shown on screen during voice (such as steps, lists, drafts and links), created by the AI and saved with the transcript in your browser only. Check links before opening them.
• For everyone, with or without an account: document cards when you ask for a PDF, Word, PowerPoint or Excel file during voice. The AI service writes the document’s text and sends it through QSI’s voice relay to your browser, which shows download buttons; the file itself is made on your device. Document cards are saved with the transcript in your browser only.
• For everyone, with or without an account: the text of files you share with the file button during voice (PDF, Word .docx, Excel .xlsx, CSV, PowerPoint .pptx or text files; up to 40,000 characters per file and 5 files per voice session). Your browser reads the file and sends only its text, with the file name and a short description such as the number of pages, sheets or slides, and for spreadsheets the column totals your browser calculated, through QSI’s voice relay to QSI’s AI services. The original file is not uploaded. Scanned PDFs and pictures can’t be shared in voice. Only the file’s name and a short description (such as the number of pages, sheets or rows) are saved with the transcript in your browser; like other chat messages, that line is sent as recent conversation if you continue the chat or start voice mode again in it.

No audio, no transcripts, no web searches, no cards, no documents and no shared files. Our server only gives your browser a short-lived, single-use access code that only QSI’s voice relay can read; the audio never passes through our server, live-voice web searches are run by the AI service itself, cards and document text come from it through the relay to your browser, and the text of files you share goes from your browser through the relay to it. The recent chat text and settings listed above pass through our server to prepare the instructions, as with a normal chat message, and are not saved.

When voice mode ends, the transcript, any cards or documents shown on screen and the names (with a short description) of files you shared are saved as normal messages marked “Voice” in your browser’s chat history only. To enforce the daily limits, our server keeps usage counters: see “Rate limiting & security” below.

• Your picture request (up to 1,000 characters), typed in the chat or in Picture mode. In the chat, your browser sends a message to QSI’s picture check only when it looks like a clear request for a picture, or for a change to a photo you added; if QSI’s safety check finds it isn’t one, it is answered as a normal chat message instead (see “Chat & Swarm” above), and QSI keeps only a note that a check was made (the time, whether it was about a picture or a photo, and the coded keys for your account), not your message or photo. If you ask for a change to your last picture, QSI makes a new picture from a combined description, so your browser also sends back the English description of that last picture.
• The result of QSI’s safety check of your description against the picture rules in our Terms, and an English description of the picture that QSI writes from yours, with a one-line caption in your language (for screen readers)
• The finished picture (a JPEG of about 1 megapixel: 1024 × 1024 pixels for a new picture, the shape of your photo for a photo edit), its label and its picture ID (see “Labels on pictures” below this table)
• Your account, because only logged-in members can make pictures, and the usage counts described under “Rate limiting & security” below
• Photo edits (for the logged-in members they are offered to): the photo you add (one at a time), which your browser first makes smaller (at most 1,536 pixels on its longest side) and saves as a new JPEG file, which leaves out the location (GPS), camera and other details stored in the original file; your description of the change; and your confirmation that you may edit the photo and that the people in it agreed. QSI doesn’t edit photos that show anyone who is, or may be, under 18.
• Like other messages, your picture requests and their captions are saved in your chat history in your browser, and can be part of the recent conversation sent with your later chat messages.

QSI’s safety check has two steps: a word list on our server, then one of QSI’s AI services, which receives your request (and, for a photo edit, a copy of your photo at most 1,024 pixels on its longest side), checks it and writes the English description (it never goes to the backup services). A request the word list refuses is not sent on. Only the English description, the picture settings, a coded identifier for your account and, for a photo edit, your photo (at most 1,536 pixels on its longest side) go to the third-party AI picture provider (see section 3), which makes the picture. After QSI labels an edited photo, and before your browser can collect it, the same provider’s free safety check also checks it for sexual, violent and self-harm content.

Your photo (photo edits): not saved by QSI. QSI’s code never saves the photo you add. Our server checks it and has the edit made while holding it only in its working memory, for a few seconds up to about 2 minutes, and drops it as soon as the edit has been made. While the photo is being received, our web server and its PHP software may briefly hold it in temporary files, which they delete when the request ends; QSI also removes PHP’s copy as soon as the photo has been read, and deletes any PHP temporary file left behind (for example after a server fault) once it is more than 15 minutes old. Your browser keeps the photo you added with the chat, in its own storage on this device (IndexedDB, under qsi-v2-pictures), so you can compare it with the result or make the edit again, until you delete that chat or use Settings → “Clear all”.

The picture: only until your browser collects it. A picture takes from a few seconds to about 2 minutes. Meanwhile your browser checks back with our server, and the finished picture waits in a private file there. It is deleted as soon as your browser collects it; a picture that is never collected is deleted in an automatic clean-up once it is 1 hour old. After that QSI has no copy, so download the pictures you want to keep. Your browser keeps your pictures with the chat, in its own storage on this device (IndexedDB, under qsi-v2-pictures), until you delete that chat or use Settings → “Clear all”. It also remembers when it last showed you the picture rules (qsi.v2.picnotice).

A record of each picture request: yes, for 180 days. Unlike chats, our server keeps a record of every picture request, including refused ones, because India’s IT Rules require us to be able to trace AI-generated pictures and deal with complaints. Each record holds: the time; your description (and the earlier description, if you asked for a change); the result of the safety checks; the English description sent to the picture provider; the picture ID; a fingerprint (SHA-256 hash) of the finished picture and of the file the provider returned; technical details such as the picture’s size, how long it took and what it cost; and two coded keys for your account: a hash of your random account number and a keyed hash of your email address, so that a complaint can still be matched to an account after it is deleted. It also records whether you asked in the chat or in Picture mode, and any report you send us about a picture (a report ID, the picture’s ID, the reason you chose and your note). Our Grievance Officer reviews every report and is told about it by a short email (at busy times, several reports in one email) with the report ID, the picture’s ID, the reason, the time and the coded key for your account; that email never contains your note, the picture, its description or your email address. A message typed in the chat that QSI’s safety check finds isn’t a request for a picture or a photo edit is not kept: only a note that a check was made, with the time, whether it was about a picture or a photo, and the two coded keys. For a photo edit, the record also holds: a fingerprint (SHA-256 hash) of your photo as uploaded and as sent; a short visual fingerprint (a 64-bit “perceptual hash”) of your photo and of the edited picture, which helps match copies that were resized or re-saved but can’t be turned back into a picture; the photo’s size; your confirmation; the yes/no results of QSI’s check of the photo (how many people it shows, and whether anyone may be under 18 or a well-known person, is shown with nudity, or whether it shows a document or a news event; QSI does not identify anyone); the kind of change; and the result of the final check of the edited picture. It never holds the picture itself, your photo, your IP address or your email address in readable form. See section 6 for how long each part is kept.

• In Coder mode you can turn on Agent and describe a task (up to 4,000 characters). Alpha Core then works on the files of that chat (the files in its code answers and text files you attached) by itself, in steps, until the task works or a limit is reached. Nothing is sent before you tap Start.
• At the start, your browser sends the task, a list of the project’s files (names, sizes and line counts) and, if they fit (on the preview, up to 40 files and 40 KB together), the text of the files. Files whose names suggest passwords or keys (for example .env, key and credentials files) are never read or sent: only their names, sizes and line counts. If you carry on from an earlier task, that task’s summary and what was left go with it. Pictures are not used.
• At each step, the AI asks for actions; your browser carries them out on your device and sends back the results: file lists and searches of the project, the text of the files the AI reads (up to 12,000 characters each), whether its changes worked, and what your code printed when it ran (up to about 4,000 characters per run), at most 16,000 characters per step. The code runs only in your browser, in the same sandbox as the Run button, with no internet access. (Alpha Core’s web search and web page reads, described next, are run by our server, not by your code or your browser.)
• Before anything is sent, your browser replaces values that look like passwords or keys (in the task, the files and the results) with placeholders; the real values stay in your browser and are put back into the files you download. Our server checks again for such values. It can’t recognise every secret, so don’t put passwords, keys or other people’s personal data in a project.
• Web search and web pages (in every Agent mode task, where this is available to your account; there is no box to tick for each task, and the start sheet says so before you press Start): the AI can ask our server to search the web or to read one public web page. For a search, the words the AI chose (they can come from your task and your files) are sent from our server to the AI service QSI uses for web search (see “Web search” in this section and section 3), which returns short summaries and the addresses of pages. For a page, our server fetches the address the AI chose, from our server’s internet address, not yours; it fetches only ordinary public web addresses (it refuses private, internal and numeric addresses and any address that was not in your task, a search result or a link on a page already read), follows the site’s robots.txt, and sends no cookies, no login and none of your data to the site. The site sees our server’s address and a request from “QSI-Agent”. Our server turns the page into plain text (about 12,000 characters at a time) and passes it, as text the AI must treat as information and not as instructions, to the AI processing partner that works on Agent mode tasks. A web page can contain text meant to trick the AI: QSI tells the AI to treat page text only as information, lists each page it read in the task and shows you the first words the AI was given from it. Because the web tools can be used in any Agent mode task, don’t put anything in a task that you wouldn’t want to leave QSI.
• All of this goes through our server to the AI processing partner that works on Agent mode tasks (see section 3), with QSI’s instructions and a random code for your account (not your email, and not reversible) so the partner can spot misuse. As in Coder mode, QSI’s instructions include the name and preferred language from your optional profile, and your city and state only while “Use my city for local answers” is on. Your email address and your Memory notes are not sent.
• In your browser: the task message and a plain-text summary of its result are saved in your chat history; Agent mode’s own data is saved in your browser’s storage on this device (IndexedDB, under qsi-agent): the project’s files, the task’s working copy and step list, the table of hidden values while the task is unfinished, and, after the task ends, the files it changed (with your real values put back) and its step list, so you can review, download or undo the changes. Your browser also remembers that you saw Agent mode’s first-use note (qsi.v2.agmIntro); starting a task that needs Python counts as agreeing to the Python download (qsi.v2.pyok, see “Running code” above).
• You can start a task from a .zip of your project (up to 5 MB and 300 text files). Your browser opens the zip on your device; QSI doesn’t receive the zip. Binary and very large files, files with unsafe paths and files in folders such as .git and node_modules are not used by Agent mode, and the text files that are used are handled like any other project files. Your browser keeps a copy of the zip (in a storage of its own next to Agent mode’s, qsi-agent-zip), without files that hold keys or can run by themselves (such as .env or .git) and without node_modules, so you can download the finished project; it is removed with the chat (at the latest the next time Agent mode starts in your browser), by “Clear all”, or when you log out and remove QSI’s data from this device, and only the newest 10 are kept.
• Agent mode isn’t available in a Temporary chat.

An encrypted copy of the task, for a short time. While a task runs, our server keeps the conversation with the AI processing partner (your task, the file text that was sent, the AI’s replies and the results your browser sent back) in a private file outside the public web folder, encrypted (AES-256-GCM) with a key made for that task. Only your browser holds the key, which it sends with each step, so our server can read the copy only while it handles a step. QSI deletes the copy about an hour after the task ends (when it finishes, when you stop it or when it reaches a limit), and no later than about a day after the task started; these deletions run in QSI’s automatic clean-ups, while QSI is in use.

A task record, deleted with the copy: the task’s state, step and answer counts, times and costs, and short codes made from test results and error messages (never your files or your task text), linked to your account by the same one-way code as Coder mode’s counts. While you have an unfinished task, a pointer under that code says which task it is; an empty marker file named with that code stops two tabs from starting a task at the same time.

A record of the web pages Agent mode reads: yes, for one year. India’s rules require us to keep logs of how personal data is processed for at least one year, to be able to trace the use of our systems and to deal with abuse complaints, so our server records each web page request that Agent mode sends to a website (including one it then refuses, for example because the website’s robots.txt asks it not to read the page) in a private file outside the public web folder: the time, the one-way code for your account (as for Coder mode’s counts), the website’s name (not the rest of the address), the internet address of the website’s server, whether it worked, how many bytes came back and how long it took. An address that Agent mode refuses without sending anything (for example a private, internal or numeric address, or one that was not in your task, a search result or a page it read) is recorded by a short code for the reason only, without the address. Each web search is recorded too (the time, the one-way code, how long it took and what it cost), without the search words. QSI keeps no copy of a page’s text beyond the task: it sits in the task’s encrypted copy and is deleted with it. QSI also keeps each website’s robots.txt rules (not its pages) for about an hour so it doesn’t ask again.

Counts, like Coder mode’s: under that one-way code, how many Agent mode answers you used this paid month and today, how many tasks you started today, how many web searches and page reads you used this paid month and today, how many refused address requests you made today (to spot attempts to reach private addresses), and how many answers you used in the last hour (a task Alpha Core refuses also counts toward Coder mode’s daily refusal count); and site-wide counts of running tasks, of the preview’s spending today and this month, daily counts and a daily summary, which identify no one. See section 6 for how long each is kept.

• Your notes (at most 40, each up to 160 characters, plus an optional “About you” text of up to 300 characters): kept only in your browser’s local storage under qsi.v2.mem. followed by a code for your account, encrypted (AES-GCM) with a key our server gives your browser only while you are logged in. Your browser also keeps a list of chats waiting for a Memory update (qsi.v2.mem.pending. plus the same code: chat numbers only, never text), whether you marked this browser as a shared device (qsi.v2.mem.shared) and when you last chose “Not now” on the Memory offer (qsi.v2.mem.card).
• To write or change notes: after some messages, or when you ask QSI to remember or forget something, your browser sends your recent messages in that chat (only yours: never QSI’s answers, the text of attachments or shared files, search results or picture requests; at most 3,000 characters) and your current notes through our server to QSI’s AI services, which suggest changes. Our server checks every suggestion against its own rules and signs the notes it allows, so only notes it checked can be sent back later. Every change is shown under the answer, with Undo. A note you type, edit or add from a file is checked and signed by our server the same way, without the AI service.
• When you chat, use Swarm or start live voice: the notes that matter for your message (up to about 1,200 characters in a chat, 800 in Swarm and 600 in live voice, and up to 2,000 when you ask what QSI remembers) are sent with it to QSI’s AI services (never to the backup AI services), with QSI’s rules for using them. Live voice uses only notes about your name, languages, place, work, studies, interests and projects. Answers that used your notes are part of the chat and are sent with later messages in that chat, like any chat message.
• On our server: a record that you turned Memory on or off, when, the version of this policy you agreed to, a key number that changes when you turn Memory off or delete all notes, and, if QSI turned Memory off because you said you are under 18, when that happened.

No. Files are made on your device, in your browser, and saved straight to your device. They are not sent to QSI’s server or to anyone else. QSI adds no name, logo or tracking to them; the only file information it sets is the title.

If you tap Share, the file goes to the app you pick, under that app’s own policies. If you choose Print, your browser’s own print feature makes the PDF or prints it, and it may add its own header or footer (such as the page address and date) and put the browser’s name in the PDF’s properties.

With a QSI natural voice (Rads or Mayur), the text is sent to an AI text-to-speech service QSI uses. To save cost, the resulting audio is cached on our server for up to 24 hours, in a temporary file named by a code computed from the voice, language and text. It contains no IP address or other identifier, but it is a spoken copy of the answer, so it contains whatever the answer said.

If you choose Browser voice, or if the QSI voice is unavailable, your browser’s or operating system’s speech feature is used instead, and QSI’s server does not receive the text. Some browsers use online voices that send the text to the browser maker (for example Google or Microsoft) under its own policies.

• Your email address, checked either by Google or by a 6-digit code we email you
• If you use Google: your Google account ID and the name on your Google account (never your Google password)
• When your account was created, when you last logged in, and how you log in (Google, email code or both)
• Your confirmation that you are 18 or older and agree to this Privacy Policy, with the policy version and the time; if you later accept an updated version (QSI asks before your first photo edit if you agreed to an earlier one), that version and the time instead
• A login cookie (qsi_sid) with a random code, of which our server keeps only a one-way hash, with the times the login was created, last used and expires
• While a login code is pending: a keyed hash of the code (never the code itself), its expiry time and the number of wrong tries; and, for 24 hours, the times codes were sent to that address and the times wrong codes were entered for it (so we can send at most 10 codes a day to one address and pause email login for an address after 15 wrong codes)
• Usage counts for your account (see “Rate limiting & security” below)

Yes, in private files on our server, outside the public web folder. Your chats are still not stored and are not linked to your account, apart from the record of each picture request (see “Making pictures and photo edits” above), Agent mode’s short-lived, encrypted task copy (see “Agent mode” above), a careful answer while it waits for your browser to collect it, kept with the hash of your random account number (see “Chat & Swarm” above), and a child-safety report from Companions (see “Child-safety reports (Companions)” above). Login-code emails are sent through our host’s mail server.

From these files our server also keeps a private member list (a spreadsheet file in the same private folder) so we can run and support QSI: each member’s email address, name, sign-up and last-login dates, login method, and today’s usage counts (chat messages, Swarm runs, messages with attachments, pictures and live-voice minutes). It never contains chats. It is updated when members sign up or log in and every few minutes while QSI is in use, and your row is removed when you delete your account.

Your account stays until you delete it (Settings → Account → Manage → Delete account) or ask us to. Your registration data is kept for 180 days after you close your account. See “Your account” in section 6 for what that record holds. Login sessions end 30 days after you last used QSI while logged in, or when you log out. Login codes expire after 10 minutes.

• The name you would like QSI to call you (2 to 40 letters)
• Your preferred language, if you choose one
• Your city and your state or union territory (or “Outside India”), if you give them, and whether you turned on “Use my city for local answers”
• When you last saved it

Yes, in your account’s file on our server, outside the public web folder (unlike Memory notes, which stay in your browser). It is not in our member list and is never shown to anyone else. If a Memory note gives another name or language, QSI uses the name (and the language, if you chose one) in your profile.

You can change or delete it at any time in your account (Settings → Account → Manage → Your profile). Deleting your account deletes it too.

• Your QSI account, and the state or union territory you choose when you buy (and, only if you ask for a business invoice, the GSTIN and the business’s legal name and address you give), for your GST tax invoice
• If you buy from outside India (only where QSI offers it): your country, and the name and billing address you give, which an export invoice must show, and when you confirmed that you are buying from outside India and that the billing address is outside India; no state or GSTIN
• From Razorpay, our payment aggregator: the IDs of your subscription, payments, invoices, refunds and any chargebacks, their status, amounts and dates, and the months you have paid for, and, for a purchase from outside India, whether each payment was made with a card issued outside India (this decides the tax on its invoice)
• The numbers of the GST tax invoices and credit notes we give your payments
• How much of this month’s Pro boost you have used (a small counter)
• Your card, UPI and bank account details are entered only in Razorpay’s payment window (or in your UPI app or bank), never on QSI’s own pages. QSI never stores them, and never receives your full card number, UPI PIN or net banking password (see section 3).

Yes, in private files on our server, outside the public web folder, linked to your account’s ID rather than your email address. We also keep a private list of our GST invoices and credit notes (number, date, state, GSTIN and business name if given, amounts; for a purchase from outside India, the country and the name you gave) for our accountant and tax returns.

Payment and invoice records are kept for about 8 years (GST law: 72 months from the due date of the annual return for the year of the payment), even if you delete your account. Deleting your account first stops auto-renew. The boost counter starts again each paid month.

• Email address
• Source (which sign-up form you used)
• IP address
• Browser user agent (browser and device type)
• Sign-up time and status
• Consent record: that you agreed, the time you agreed, and the policy version you agreed to

• Chat: a SHA-1 hash of your IP address (for IPv6, only the first 64 bits), plus the times of your recent requests and counts of your chat messages and Swarm runs per day. While QSI works on a careful answer for you (see “Chat & Swarm” above), the times of your browser’s checks for it are kept under the same hash or, if you are logged in, under the hash of your random account number (a 1-minute window). The hash is not salted, so it could be matched back to the IP address: this is not anonymous.
• Waitlist (closed): your IP address itself (used as the file name) and the times of any sign-up attempts (maximum 5 per hour)
• Voice and attachments: the same hashed IP address and request times, kept in separate temporary files (voice input: a 60-second window, plus a count of voice inputs per day; read-aloud: 60-second window, plus a count of read-aloud characters per day; attachments: 10-minute window, plus a count of messages with attachments per day), plus site-wide daily counters and a daily read-aloud character count that do not identify anyone.
• Live voice: the same hashed IP address (as the file name; if you are logged in, a hash of your account number instead), with a random session number, the start time, when its temporary access code expires and the seconds of voice time reserved and used for each voice session today (starts are also limited to 6 per 10 minutes), plus a site-wide count of voice seconds used today and a list of open voice sessions. While your voice session is open, that site-wide list also links its session number to your hashed IP address and, if you are logged in, the hash of your account number, so the session can still be ended correctly if your IP address changes and one network can’t hold more than two voice sessions at a time; the link is dropped once the session has ended.
• If you are logged in: the per-day counts (chat messages, Swarm runs, messages with attachments, voice input, read-aloud characters and live-voice seconds) are kept under a SHA-1 hash of your random account number instead of your IP address, so your higher limits follow your account. So that one network can’t create many accounts, members on the same IP address also share a ceiling of three times the member limits, kept under the hashed IP address, and at most 5 new accounts can be created from one IP address per day.
• Login: the hashed IP address with the times of login-code requests (up to 10 per hour), code checks and Google logins (up to 20 per hour each), plus a site-wide count of login emails per day that does not identify anyone. Each time you open QSI, it asks our server whether you are logged in; the times of these login checks and of other login requests are also kept under the hashed IP address (up to 300 checks and 120 other login requests per 10 minutes).
• Pictures (members only): under the hash of your random account number, how many pictures you have made today, how many picture requests have reached the second step of our safety check today, how many our word list refused today, and the times of your recent progress checks (1-minute windows); under the hashed IP address, how many pictures members on the same network have made today (one network can make at most five times the member limit) and the times of your recent picture requests (1-minute windows); and site-wide counts of pictures, picture requests and refused requests per day and a total of picture costs per month, which do not identify anyone. While a picture is being made, our server also keeps a short job record with the hash of your account number, the hashed IP address, the picture ID, the English description and the caption; it is deleted when your browser collects the picture, or otherwise in the automatic clean-up once it is 1 hour old. For photo edits (members offered them), also: how many photo edits you have made today; how many refused photo-edit requests counted against you today and in the current 30-day period (several in a day, or many in 30 days, pause photo edits); how many of your photo edits our checks stopped today after they were made (3 stop photo edits until the next day); while a photo edit is being started, an empty lock file named with the hash of your account number; and only when it applies, a note under the hash of your account number (and, when picture making is paused for review or turned off, also under a keyed hash of your email address) saying that photo edits are paused, or that picture making is paused or turned off, and until when. Site-wide counts of photo edits and photo checks per day do not identify anyone.
• Web search (answers that use the AI service’s own web search): under the hash of your random account number, how many such answers you got today; under the hashed IP address, how many members on the same network got today (one network can get at most three times the member limit); and site-wide counts per day, a total of their estimated cost per month and a daily summary (answers, searches, cost and failures), which do not identify anyone.
• Agent mode (members it is offered to): in a temporary file named with the one-way code for your account (see “Coder mode”), the times of your recent Agent mode requests (a 1-minute window, at most 30 requests a minute); each task also counts as one chat message of the day. Agent mode’s other counts are described in its row above.
• A site-wide daily request count that does not identify anyone

• Contact form: name, email address, subject, message, IP address and time
• Deletion-request form: email address, reason, feedback, IP address and time

Google handles this under its own privacy policy. We never see your Google password. If you never open the login window, your browser does not contact Google for QSI.

Google Privacy Policy

The relay passes live-voice data between your browser and QSI’s AI services. It does not store the audio or the conversation, and we have turned its request logs off.

Cloudflare privacy policy

Razorpay is an RBI-authorised payment aggregator. It processes your payments, your UPI AutoPay, card or bank mandate (eMandate) and each renewal, and may email or message you about them, under its own privacy policy; it may set its own cookies in its payment window. For UPI AutoPay and cards, your UPI app or bank also sends you the notices RBI requires before and after each charge.

Razorpay’s answers and notifications to QSI’s server about your payments also include details such as your email address, mobile number and how you paid (for example your UPI ID, the last 4 digits of your card or your bank’s name). QSI doesn’t use or keep them: it keeps only the IDs, statuses, amounts and dates listed in section 2, and never receives your full card number, UPI PIN or net banking password.