ClariSpace
Sign inCreate account

Privacy policy

Last updated 12 October 2026

ClariSpace reads your own material to answer your own questions. This page says exactly what it reads, what it keeps, who else sees any of it, and how you take it back. Nothing here is boilerplate: every sentence describes what the product does today.

Who we are

ClariSpace (https://clarispace.in) is operated by its maker, Yashwanth, in India. For anything about your data, write to privacy@clarispace.in.

What we collect

Your account

Your email address, the name you choose, a password (stored only as a hash), your display preferences, and the times you sign in. If you add a passkey, its public key - the private half never leaves your device. A salted hash of each sign-in code - the code works for ten minutes, and the hash is deleted after two days. And a random token in a cookie that marks a browser you have signed in from, so a sign-in from a new one can be reported to you by mail. If you answer the optional question at sign-up - what you would ask ClariSpace first - that answer, read by ClariSpace's maker to learn what to build and never given to an AI model. The address is used to sign you in, to send the welcome mail, sign-in codes, password resets and new-browser notices; during early access its maker is also told it when your account is made and may write to you once, personally - a reply is never needed. It is used for nothing else.

What you type and what we answer

Your questions, the answers, the files you attach to a thread, and the files you choose to keep in the Library. Threads are yours to delete, and a retention policy in Settings can delete them on a schedule you set. Nothing is deleted by default.

Data from the services you connect

Connecting a service ("a bridge") gives ClariSpace a token that lets it read that service on your behalf. Tokens are encrypted at rest and are deleted the moment you disconnect the bridge. What each bridge reads, and what is kept:

  • Gmail (read, and send on your click): messages are read at the moment you ask a question that needs them and are not stored as a mailbox. What is kept is the least that lets a claim be checked: a subject line, a sender, a date, and the sentence a promise or a task was read from (for Radar, Circle and Tasks). A draft reply is sent only when you press Send.
  • Google Calendar (events): read for briefs, agendas, conflicts and free time. Events are not copied; a title, time and attendees may be kept as evidence for Radar. An event is created only when you press the button.
  • Google Docs and Sheets: read when you ask about a document or a sheet you have chosen. A change is applied only when you press Apply.
  • Google Drive (read, and files you pick): file names and the contents of files you ask about. A file enters the Library only when you choose to keep it.
  • Jira: issues, statuses and assignees, read when you ask. An issue is created or moved only when you press the button.

ClariSpace's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Google user data is used only to provide the features you see, is never used for advertising, is never sold, and is never read by a human except with your permission to resolve a problem you have raised.

Voice

When you use voice, the recording is sent to the speech provider to be turned into words and is not stored; the words and the spoken answer are kept in the thread like any other message.

Browser tabs

If you add the ClariSpace extension to Chrome or Firefox and ask about your open tabs, the extension opens a small window listing them. Only the tabs you tick there are read - their address, their title, the words on the page and any product details the page declares. Those go to the model provider you chose, to find the price and offers, and the page text is not stored; the comparison written from it, and the addresses and titles of the tabs read, are kept in the thread like any other answer. The extension reads nothing until you ask in ClariSpace and tick a tab, and it never reads cookies, passwords or what you type into a page.

Sharing a Space

When you share a Space, the people you invite can see every thread in it and its history - including anything an answer quoted from your mail or files - and its sources, and can download the files added to it. We send each of them one email from ClariSpace saying you shared it. Files you add to a Space are kept as you uploaded them so they can be downloaded, and are deleted when you delete them. You can remove someone, or stop sharing, at any time.

DevMode

DevMode works on a software project on your own computer, through a small program you download from clarispace.in and run in the project's folder (the DevMode bridge). It pairs once, with a six-digit code; the token it earns is kept on your computer, and only a hash of it on our server. The bridge reaches out to ClariSpace and ClariSpace never reaches in; commands run on your computer, never on our server.

  • What it reads: the names of the files and folders in the project; the files the engineer opens for a job, and what it searches for in them; the output of the commands it runs, and of the commands you type in its Terminal; screenshots of your own pages, taken on your computer, when it looks at them; and a summary of the machine - its name, the system and shell, the languages and package managers installed with their versions, and which build files the project has. It reads nothing outside the project's folder and never the contents of secrets files (.env files, keys, credentials), and known secret shapes in command output are masked before the model or the page sees them.
  • What goes to the model: your words, the images you attach, and what the engineer reads and runs, as above - sent to OpenAI to do the job you asked for. Your project is never uploaded as a whole.
  • What is kept on our server: each chat - what you and the engineer said, its steps, what it read, ran and looked at, its test runs and the images you attached; for every file it changed, the file before and after the change, so the change can be put back; and the machine's name, the project's folder path and the summary above.
  • How it goes: deleting a chat deletes all of it except the file changes, which stay so a file can still be put back. Forget this machine in DevMode deletes everything DevMode kept from that machine, the changes included. Settings → Data can also do it on a schedule you set. None of it touches the files on your computer.

Notes

Notes records a meeting from your microphone, in your browser, and only after you confirm that everyone in the meeting knows it is being recorded; the moment you confirmed is kept on the note. When you stop, the recording is sent once to OpenAI to be turned into words with speaker labels, and then discarded - it is never stored. What is kept is the transcript, the write-up (a summary, what was decided and who owes what), the meeting's name and, if you picked a calendar event, its invite list as it was when you started. A speaker's name is only ever inferred, from that list and what was said. Each person has a monthly limit on minutes, shown in Notes.

Who processes it

ClariSpace has no advertising, no analytics service and no trackers. It uses these processors:

  • OpenAI - the language models that write answers, the speech models that hear and speak. The question, the material needed to answer it and the conversation so far are sent for each answer. In DevMode, what the engineer reads and runs is sent the same way, and in Notes the recording is sent to be transcribed and the transcript to be written up. OpenAI's API terms do not permit training on this data.
  • xAI (Grok) - only if you choose it as your model, on the same terms.
  • Anthropic (Claude) - only if you choose Claude as your model. The question, the material needed to answer it and the conversation so far are sent to Anthropic for that answer; OpenAI still reads the question to work out what it is about. Anthropic's commercial terms do not permit training on this data.
  • Brave Search - when a question needs the live web, the search query (not your material) is sent to Brave.
  • Google and Atlassian - the services you connect, reached with your token, under their own policies.
  • Amazon Web Services - the server, in Mumbai, India, where ClariSpace runs and where your data is stored, over HTTPS.
  • Google Workspace - delivers the mail ClariSpace itself sends you: sign-in codes, password resets, new sign-in alerts and the welcome mail. It carries your address and that message, nothing from your connected accounts.

How long we keep it

  • Your account and its data: until you delete them.
  • Threads, the action record (Trail) and the model-call record (Spend): forever by default; Settings → Data lets you set 30 days to 2 years for each, and shows you what a sweep would remove before you press it.
  • Bridge tokens: until you disconnect the bridge.
  • Notes: until you delete them, or until Settings → Data deletes them on a schedule you set. The recording itself is never kept.
  • DevMode: a chat until you delete it; the file changes it made, and everything else kept from a machine, until you forget that machine - or sooner, if you set how long in Settings → Data, which then deletes chats untouched for that long, whole, and the file changes and Terminal commands older than it.
  • Circle - the people you mail and meet, and what passed between you - and the record of each agent run: forever by default; Settings → Data lets you set how long, and then forgets people not heard from in that time and removes finished runs older than it.
  • Server backups: a copy of the database is taken nightly and kept for 14 days, then deleted.

Your choices

  • Disconnect any bridge at any time on the Bridges page; its token is deleted at once. You can also revoke ClariSpace from your Google account permissions.
  • Turn a permission off without disconnecting - Settings → Permissions decides, per service, whether ClariSpace may read it and whether it may write.
  • Delete your history from Settings → Data, or delete a thread from its menu.
  • Delete a note from its page in Notes; it goes at once.
  • Delete a DevMode chat from its menu, or forget a machine in DevMode to delete everything kept from it.
  • Delete your account yourself, in Settings, Data & retention, Delete my account: a code is sent to your address first, then everything the account holds is deleted at once, ClariSpace's access to your Google account is cancelled, and it leaves the backups within 14 days. Or write to privacy@clarispace.in from the address on the account, and it is done within 7 days.
  • See what it did: Trail records every action ClariSpace took, and Spend every model call.

Security

Everything travels over HTTPS. Bridge tokens are encrypted at rest; DevMode's bridge token is kept only as a hash. Passwords are hashed. The server accepts connections only through its HTTPS front, sign-in and sign-up are rate-limited, and the page carries a Content-Security-Policy that allows no inline script. If you find a weakness, please write to security@clarispace.in before telling anyone else, and we will fix it first and thank you second.

Cookies

Two, both essential: a session cookie that keeps you signed in and a CSRF token that protects forms. Your display preferences are kept in your browser's local storage. There are no advertising or tracking cookies.

Children

ClariSpace is not directed at children under 13 and does not knowingly hold their data.

Changes

When this policy changes, the date at the top changes with it, and a change that matters to you will be announced inside the product before it takes effect.