Privacy Policy

Last updated 7 October 2026

This policy explains what personal data Sochen collects, why, who it goes to, and the choices you have. In short: we collect what we need to run your agent. We never sell your data, we don’t show ads in Sochen, and we do not use your content to train AI models. Advertising comes in one way only: to see which of our own ads on X work, X’s pixel can run on Sochen’s pages, and Sochen can tell X when someone signs up, starts a trial or pays. Where you are decides whether we ask you first or tell you and let you switch it off; see Ad measurement.

Who runs Sochen

Sochen decides how your data is used (the “controller”). Write to us at ndivij2004@gmail.com.

What we collect

  • Account details: your email address, the name you give, and your password, which is stored only as a secure hash. If you sign in with Google instead, Google tells us your name, email address and profile picture, and that it has confirmed the address; we keep the sign-in tokens it issues, which can only read those details. We never see your Google password or anything else in your Google account.
  • What you give Sochen: your messages, files you attach, requests you make by voice, and the results of the jobs Sochen runs for you. We do not store voice recordings.
  • Memory: facts and preferences Sochen saves to help you in later chats, and short notes it keeps about recent conversations. You can see and change all of it on your Memory page. Your pets’ diaries (and Eli’s, from your chats without a pet) are written the same way, by an AI model from each day’s chats, and emailed to you each morning unless you turn that off; a line you correct is saved to memory in your words. If you share a day, anyone with its link sees what the pets wrote that day, without the lines that quote you or links to your chats, until you stop sharing it.
  • Connections: the addresses of the apps and MCP servers you connect, and the access tokens or keys you provide for them. These are encrypted before they are stored.
  • Phone: if you add your number for calls, the number and a PIN, which is stored only as a hash. For a call Sochen makes to a business for you, what you asked it to find out or say, and the call’s transcript and summary, encrypted.
  • Dictation: your dictation settings and word list, and for each dictation how long it was and how many words it had. Not the audio, and not the words themselves.
  • How you found Sochen: the campaign tags on the link you first opened, or the site you came from, and the page you landed on (see Cookies below). With ad measurement on, also the ad click id, your choice about ad measurement, and a log of what was sent (see Ad measurement).
  • Feedback: what you send us from the Feedback page or ask Sochen to pass on, which chat it came from, and our answers. We read it to fix and improve Sochen, and email you when we answer it.
  • Usage and billing: the model, tokens, tools and credits each turn used, your plan, and your payment history. Dodo Payments handles your card and bank details; we never see or store them.
  • Withdrawals and cancellations: if you buy from the EU or the UK, your request to start straight away (the exact words you confirmed, and when), and any withdrawal or cancellation you send from Billing, with when it arrived and what was refunded.
  • Technical data: your IP address and approximate country, which we use to show prices in your currency and to keep Sochen secure; your time zone, so dates and reminders are right for you; your browser’s name and version, kept with each signed-in session; when each chat was last open on your screen, so we don’t email you about a job you’re watching; standard server logs kept by our hosting provider; and cookie-free page-view counts (see Vercel below).

How we use it

  • to run Sochen: answer your requests, carry out jobs, and remember what you want remembered;
  • to count credits, take payments and show you your usage;
  • to keep Sochen secure and prevent abuse;
  • to reply when you contact us;
  • to see which of our posts and ads bring people, as Ad measurement describes; and
  • to fix problems and improve Sochen.

We do not read your conversations unless you ask us to help with a problem, or we must in order to investigate abuse or comply with the law. We do not sell your personal data, we do not show ads in Sochen, we do not use your content to train AI models, and none of it ever goes to an ad platform.

Who we share it with

We share data only with the providers that run Sochen, and only what each one needs:

  • Vercel hosts Sochen, routes requests to AI models through its AI Gateway, runs the private sandbox where Sochen works on your files (with no internet access), keeps the files Sochen makes for you in private storage, and counts page views with Vercel Web Analytics: the page (without chat ids or anything after a “?”), the site you came from, and your country, browser and device type, with no cookies; and a few steps by name, such as “wrote a free cold email” or “started signing up”, with nothing you typed.
  • AI model providers (Google, Anthropic, OpenAI, Alibaba, Moonshot AI and DeepSeek) receive your messages and the context needed to answer them, and process them under their API terms. Every call asks AI Gateway for a provider that doesn’t train on your content and keeps no copy of it; Google’s Gemini models run under Google’s paid API terms, which rule out training but keep prompts for a short time to check for abuse. The model you choose answers you. DeepSeek V4.1 Flash runs on companies that host open models (DeepInfra, Relace, Fireworks AI and Together AI), not on DeepSeek’s own servers. Sochen’s background memory work, such as saving notes about a chat, uses Google’s Gemini Flash. When Sochen gathers your memories to answer a question, DeepSeek V4.1 Flash reads them on DeepInfra, Fireworks AI or Together AI, which don’t keep the data or train on it; if they’re unavailable, Gemini Flash reads them. Voice conversations go to OpenAI.
  • Dictation: the audio of a dictation goes to the service that turns it into text: either Soniox, which your browser or the desktop app streams it to directly under a key that lasts a minute, or, through AI Gateway and on terms that rule out training on it, xAI’s Grok STT or a transcription model from OpenAI or Google (or Google’s Gemini API directly). Google’s Gemini then writes the words up. Sochen keeps neither the audio nor the text.
  • Twilio carries phone calls between Sochen and you, or a business you ask Sochen to call, and sends the code that checks your number. It receives the phone numbers and the call’s audio. OpenAI’s voice model, which does the talking, receives the audio too.
  • Resend sends our emails to you, such as confirming your address, resetting your password, answering your feedback, and telling you when a long job finishes or needs you (you can turn those off in Settings).
  • AgentMail runs Sochen’s own inbox: emails you send to Sochen, their attachments, and Sochen’s replies pass through it and are kept in that inbox.
  • context.dev tells Outreach what a company says about itself on its own website, so each email can mention something true: it receives only the company’s domain (from a work address), never who you are or who you’re writing to.
  • Monid runs the skills your pets learn with your OK (home listings, reviews, prices, SEO numbers and other data): what a skill is asked to look up goes to Monid and to the data provider behind that skill, and what they find comes back to your chat. Nothing else about you is sent.
  • Linq runs Sochen’s iMessage number: texts you send to Sochen, their photos and files, and Sochen’s replies pass through it and are stored there.
  • Neon hosts our database.
  • Voyage AI turns memory text into search vectors so Sochen can find relevant memories, and ranks the memories it finds for a question, without training on it.
  • Firecrawl and context.dev receive search queries and web addresses when Sochen searches or reads the web.
  • Google Maps Platform receives place searches, areas and addresses when you ask Sochen about places, travel times or a neighbourhood. Maps shown in Sochen load from Google, which sees your IP address.
  • Browser Use runs the cloud browser for browser jobs and receives the task and the pages it visits.
  • Agent37 runs your cloud computer when Sochen uses one for you, on its servers in Virginia, United States, with its disk encrypted. The computer is yours alone: it’s kept between your jobs and switched off while unused, and when each job ends everything it left in the browser (history, cookies, open pages, downloads) is wiped. It’s deleted with your account; Agent37 keeps a recovery copy of a deleted computer for 7 days, then purges it. Screenshots of it go to the AI model that drives it, like the rest of the chat. If you turn on “Remember my sign-ins”, the computer’s browser profile (the sign-ins sites keep, never passwords or card numbers) is encrypted on the computer under a key only Sochen can derive, then kept in private Amazon Web Services storage in Mumbai until you turn it off, forget it, Freeze your account, or go 30 days without using the computer.
  • Shopify stores you shop at through Sochen receive your search, the products you pick and, if you give it, your delivery pincode. Your cart and checkout are on the store’s own site, under its privacy policy, and you pay the store directly.
  • Dodo Payments processes payments as our merchant of record.
  • Composio runs the sign-in and holds the access for the everyday apps you connect through it (Gmail, Google Calendar, Drive and Sheets, Outlook, Slack, Google Ads, Google Analytics, Search Console, Razorpay, Instagram and Facebook Pages). When Sochen reads or acts in one of those apps for you, the request and the app’s answer pass through Composio. Disconnecting the app in Sochen, or deleting your account, revokes that access. For Insights, Sochen keeps each day’s totals from your business apps (money in, payments, ad spend, reach, visitors), never single payments or customers, and deletes them with your account.
  • Orthogonal, and through it Apollo and Tomba, when you use Outreach to find people: Sochen sends who you’re looking for (roles, places, companies) or the names you give, and gets back people’s work details and whether an address takes mail.
  • TypeSafe (Jev) or OpenAI, whichever you pick, for Outreach’s quick decisions: whether a person fits what you described (their name, role and company), and what a reply means (the reply’s text). Neither may train on it.
  • Sarvam AI or Google, if you give a pet a voice with your own key from either: the text of the pet’s spoken replies goes to that provider, under your account with them.
  • Your browser’s push service (Google’s, Mozilla’s, Apple’s or Microsoft’s, by browser) delivers the notifications you turn on. They say only that something is ready or needs you, never what.
  • X (X Corp., which runs x.com) receives ad measurement events, and its pixel sees the Sochen pages you open where ad measurement is on, and nothing else, as Ad measurement describes.
  • The apps you connect receive what Sochen sends them when it works with them for you.

We may also disclose data when the law requires it, to protect someone’s safety, or as part of a sale or merger of Sochen, in which case this policy continues to apply to your data.

Ad measurement

To see which of our ads on X work, and so X can show them to people likely to find Sochen useful, Sochen tells X when you sign up, when you start a trial, and each time you pay, renewals and top-ups included. These events go from our server to X’s Conversion API. Each one carries:

  • which event it is, when it happened, the Sochen page it happened on, and a code that stops it being counted twice;
  • your email address as a one-way code (a SHA-256 hash), which X can match to an X account with the same email but can’t turn back into the address;
  • the ad click id, if you came from an X ad and allowed us to keep it;
  • at sign-up only, your IP address and your browser’s name and version;
  • for a payment, the trial included, the amount and currency; for an Outreach add-on trial, zero.

Never your name, chats, files or memory, what you ask Sochen to do, or anything else about how you use it.

Where ad measurement is on, X’s pixel also runs on Sochen’s pages. It loads from X, so X sees your IP address, your browser and the page you’re on; it records a page view and can set and read X’s own cookies, so X can tell when someone who saw or clicked our ads came to Sochen. It doesn’t report sign-ups, trials or payments: only our server does, as above, so none is counted twice.

X uses all this to count and report what our ads brought in and to choose who sees them, under its own terms; X’s Privacy Policy covers what it does with it.

Whether we ask first depends on where you are:

  • The EEA, the UK and Switzerland: off unless you say yes. Until then Sochen keeps nothing in your browser about how you found it, not even the first-touch cookie below, saves nothing with your account, sends nothing and doesn’t load X’s pixel. If you arrive from a link, another site or an ad, a small card asks; sign-up asks again.
  • India: off unless you tick yes at sign-up.
  • Everywhere else: on, and the sign-up form says so; untick it there or switch it off later in Settings. If your browser sends Global Privacy Control, X’s pixel doesn’t load and your account starts with it off.

Switching it off in Settings stops anything more being sent, stops X’s pixel loading in that browser, and deletes the ad click ids kept with your account (in the EEA, the UK and Switzerland, everything kept about how you found Sochen). Events already sent stay with X under its terms. We keep your choice as long as your account, and a log of what was sent (which event, when, and whether it went, never its contents) for 90 days.

With ad measurement on, we also keep a Meta or Google ad click id (fbclid, gclid, gbraid or wbraid) with your account if the link you came from carried one, to tell which links bring people. Nothing is sent to Meta or Google.

Legal basis: in the EEA, the UK, Switzerland and India, your consent, which you can withdraw at any time in Settings. Elsewhere, our legitimate interest in knowing which of our own ads bring people to Sochen, which you can object to at any time by switching it off.

Signing in with Google

If you choose “Continue with Google”, Sochen asks Google only for your name, email address and profile picture, and whether Google has confirmed the address (the “openid”, “email” and “profile” permissions). It asks for nothing else: not your Gmail, Drive, contacts or calendar.

  • How we use it: to create your Sochen account, sign you in, and show your name and picture in Sochen. If you allow ad measurement, your sign-up is reported to X like any other sign-up, with your email only as a one-way code (see Ad measurement). We don’t sell it, and we don’t use it to train AI models.
  • How we store it: with your account, where the rest of your data is kept (see Where your data is stored). The sign-in tokens Google issues are stored encrypted, and they can only read those same details.
  • Who we share it with: no one beyond the providers that host Sochen’s data for us (listed above), and the one-way code X receives if you allow ad measurement.
  • Removing it: deleting your Sochen account removes it. You can also remove Sochen’s access at any time in your Google Account, under Security, “Third-party apps with account access”.

Sochen’s use of information received from Google APIs follows the Google API Services User Data Policy. Connecting Gmail, Calendar, Drive or other Google apps is separate: that runs through Composio, as described under Who we share it with.

Outreach

Outreach sends emails you approve from your own Gmail, to people you chose or Sochen found. Sochen keeps each campaign’s settings, the people’s names, work addresses, roles and companies, and the emails, all encrypted, and deletes them with the campaign or your account. A work address Sochen found, or a check of one, is kept encrypted for up to 60 days so the next lookup of the same person isn’t paid for again. Replies stay in your Gmail: Sochen reads a reply to tell whether it’s a yes, a question, a no or an out-of-office, and reads the new text of the conversation to draft your answer, which waits for you to send or set aside. It keeps that word and the answer it drafted (encrypted), not the reply. If someone asks not to be emailed or an address bounces, Sochen keeps a one-way fingerprint of the address so you never email it again by mistake, even after you delete the campaign. Business emails carry your postal address and a way to opt out. You’re responsible for using Outreach lawfully, including anti-spam rules where your recipients are.

Local mode

In local mode, the AI model is downloaded to your device from Hugging Face, and the engine that runs it from jsDelivr, and it runs there. Your local chats are kept in your browser, not on our servers. Tools the local model uses, such as web search, still run on our servers and use the providers above.

Files kept on your device, and the free tools

When you switch on “On this device” in a chat, or use the free tools at sochen.dev/tools, your files are processed in your browser and are not uploaded to our servers. Your browser downloads the engines and models it needs, such as the PDF engine and the text reader’s language models, from sochen.dev. In a chat, Sochen’s AI receives only each file’s name, type and size, and for pictures and PDFs their size in pixels or their page count. If Sochen asks to read a file’s text and you agree, your browser reads it and sends only the text, which becomes part of that chat; the file itself stays on your device. A password you give Sochen to open a file, such as an e-Aadhaar’s, becomes part of that chat too. Files kept on your device stay in your browser until you remove them in Settings or clear your browser’s data.

The free cold email on the client-outreach page needs no account. What you type there and the website you name go to our web reader (Firecrawl), which fetches that site, and to our AI provider (OpenAI, through Vercel’s AI Gateway, which keeps no copy and doesn’t train on it) to write the email. We don’t keep what you typed or the email; we count requests from your network address for a day to limit how many each person makes. If you ask us to email it to you, we keep your address and that email to send it, and, if you also asked for the two tips, until they’ve gone over the next three days; after that only your address and whether you stopped them. Every tip has a one-click stop, and they stop by themselves if you sign up.

Using Sochen in ChatGPT

You can use Sochen’s invoice, rent receipt, bill-split and form-photo tools in ChatGPT without a Sochen account. When you do, Sochen receives what you give for that job: for an invoice, the seller and buyer names, addresses, states and GSTINs, the items, and an optional UPI ID; for rent receipts, the tenant’s and landlord’s names, the address and the rent; for a bill split, the names of the people, the amounts and the payer’s UPI ID; for a photo, the image you attach. Sochen also receives an anonymous ID that ChatGPT assigns; it uses that ID only to apply a daily limit, and stores it only as a one-way hash. Sochen makes the file and keeps it in private storage for 24 hours behind a link only you receive, then deletes it. It does not keep the invoice details or your original image apart from that file, and none of it is used to train AI models.

Where your data is stored

Our servers and database are in the United States. The cloud computer runs on Agent37’s servers in Virginia, United States; the sign-ins it keeps if you ask are stored on Amazon Web Services in Mumbai, India. Live dictation goes to Soniox in the United States. AI model providers and the other services above process data where they operate, mostly in the United States. We rely on their contractual and security commitments to protect it wherever it is processed.

How long we keep it

  • Your account, chats, memory and your pets’ diaries: until you close your account. Removing a chat takes it off your list; deleting a memory stops Sochen using it, and its earlier versions are kept for 90 days so the change can be undone, then deleted.
  • Connections: until you remove them, which deletes their stored credentials.
  • Changes Sochen makes in your connected apps (what it sent, and the before-and-after shown on the approval card, stored encrypted): 30 days, so you can undo them, then deleted automatically.
  • Feedback and our answers: until you close your account.
  • Public web pages and searches Sochen reads for you: kept in a shared cache for up to a day (company profiles, a month), so the same public page isn’t fetched twice. It holds only public web content, never your files, messages or accounts.
  • Short conversation notes used for memory: deleted automatically after 90 days. Notes from a chat you archive are no longer used.
  • Files Sochen makes for you (signed, filled, converted or edited copies): deleted automatically after 30 days. Page previews shown in chat: after 7 days. Files you attach stay in that chat’s private workspace so Sochen can keep working on them.
  • Videos you upload for Sochen to watch: deleted automatically after 7 days. To watch one, Sochen sends it to Google’s Gemini model; a video over 45 MB is stored in Google’s Gemini file store for up to 48 hours first, then deleted by Google.
  • Billing records: as long as tax and accounting law requires.
  • Requests to start straight away, and the withdrawals and cancellations you send: as long as your account.
  • How you found Sochen, and your ad measurement choice: as long as your account. The log of ad measurement events: 90 days.
  • You can delete your account yourself in Settings: your chats, memory, files, groups, schedules and settings are deleted right away, and copies in backups and our hosting provider’s logs within 30 days, apart from billing records we must keep. Copies in backups are removed as those backups expire.

Your choices and rights

  • See, edit, delete and export your memory from the Memory page.
  • Remove a connection from the Connections page, which deletes its stored credentials.
  • Cancel your plan from Billing.
  • Switch ad measurement on or off in Settings.
  • Delete your account and your data from Settings.
  • Ask for a copy of your data or ask us to correct it by emailing ndivij2004@gmail.com from your account’s email address. We reply within 30 days.

Depending on where you live, including under India’s Digital Personal Data Protection Act, 2023, you may have further rights, such as withdrawing consent or nominating someone to exercise your rights. Email us to use them. If you are not satisfied with our answer, you can complain to your data protection authority.

Security

Passwords are hashed, connection credentials are encrypted, all traffic uses HTTPS, and only you can open your chats. No system is perfectly secure. If a breach affects your data, we will tell you and the relevant authorities as the law requires.

Cookies and browser storage

We use a cookie to keep you signed in, and your browser’s storage for things like local chats, downloaded local models and files you keep on this device.

A first-party cookie also remembers, for 90 days, how you first found Sochen: the campaign tags on the link you opened, or the site you came from, and the page you landed on. If you came from an ad, it keeps the latest ad click id too (X’s twclid, or Meta’s fbclid or Google’s gclid, gbraid or wbraid). If you sign up, how you found Sochen is saved with your account so we know which posts and ads bring people; it goes to no one else. The ad click ids are saved with it only if you allow ad measurement: X’s then goes to X with the events described there, and the others to no one. In the EEA, the UK and Switzerland this cookie is set only after you say yes. A second cookie remembers your answer for a year.

Where ad measurement is on, X’s pixel can set and read X’s own cookies, as Ad measurement describes. We use no other third-party advertising or analytics cookies, and page views are counted without cookies.

Children

Sochen is not for anyone under 18, and we do not knowingly collect data from children. If you think a child has given us data, email us and we will delete it.

Changes

We will post changes here and update the date above. For significant changes, we will tell you by email or in Sochen first.

Contact and grievances

For privacy questions, requests or complaints, email ndivij2004@gmail.com.