Privacy Policy
This policy covers all Samvit AI Labs websites and apps. It explains what we collect, why, who helps us process it, how long we keep it, and what you can ask us to do. Part A applies to every product. Part B adds what is specific to each product.
On this page: Part A — All products · Part B — jaala · Part B — thoga
The short version
- Your work stays on your machine. Our apps store your work on your own device. We do not receive it.
- We collect what we need to run your account and licence, usage events that tell us whether the apps work, and whatever you choose to send us as feedback.
- We do not sell data, show ads, or send marketing email. We only email you about your account, billing and security.
- You can ask us to see, correct or delete your data at any time.
Part A — All products
1. Who we are
The data controller (in India, the data fiduciary) is SAMVIT AI LABS (OPC) PRIVATE LIMITED (One Person Company), CIN U62099TN2026OPC196958 (registered office details). Contact: support@samvitlabs.ai.
2. What we collect
Your account
When you sign in with Google or GitHub, we receive your email address, display name, profile picture link, and the sign-in provider's account identifier. We create a Samvit user ID for you. We never see your Google or GitHub password.
Your licence and devices
To give you a trial or a paid licence, we keep your licence status for each product (trial, active, expiry date) and a record of each device you use it on: a hardware identifier, the operating system, and the date it was registered. Each licence covers up to five devices.
To stop the free trial being restarted again and again, we keep a record that a trial was used on a given device (product + hardware identifier). This record is kept even if you delete your account. It does not contain your name or email.
How you use the apps (usage data)
The apps send us short usage events — for example app opened, import finished, search used — with counts and durations, the app version, your operating system, your country (worked out from your IP address; we do not store the IP address), and the time rounded to the hour.
- These events are stored under a random analytics code, not your name, email or user ID. The link between your account and that code is kept separately.
- They never include your work, file names, file contents or anything you type. The server rejects any event it does not recognise.
- Before you sign in for the first time, the app uses a random install ID for a few events (such as sign-in screen shown) so we can see where people get stuck.
- You can turn usage data off in the app's Settings. If you do, we cannot count your usage toward any usage-based pricing offer described in Part B.
Feedback you send us
When you use the Support button in an app, or the feedback link on our websites, we receive what you write, any screenshot or file you attach, your user ID, the app or page you sent it from, the app version and your operating system.
Screenshots and files may show your work. Only attach what you are happy for us to see. We never publish attachments. If you tick "OK to share publicly", we may post the text of your feedback on our public GitHub discussions, without your name and without attachments, after reviewing it.
Our websites
Our websites count page views, the page that referred you, your country and device type. They do not use tracking cookies. To count unique visitors without cookies, we use a code derived from your IP address and browser that changes every day; we do not store the IP address itself.
Signing in on a website (only needed to send feedback) uses the browser storage that the sign-in needs to work.
Payments
Payments are handled by Paddle.com, which acts as the merchant of record — Paddle is the seller of record for your purchase. Paddle collects your payment details under its own privacy policy. We receive your name, email, country, what you bought and your subscription status. We never see your card details.
Emails you send us
If you email us, we keep the message and your email address so we can reply and follow up.
Crash reports
If an app crashes, it may send a crash report with technical details — the error, the app version and your operating system. Crash reports do not include your work or file contents.
Update checks
The apps check our update server for new versions. Like any web server, it briefly sees your IP address to answer the request.
3. What we do not collect
- The work you create or store in our apps, or the files they read.
- Anything that passes between your machine and third-party services you connect, such as an AI provider. That traffic goes directly between you and them, under your agreement with them.
4. Why we use it
| Purpose | Data | Legal basis |
|---|---|---|
| Run your account, sign-in and licence | Account, licence and device data | Performing our contract with you |
| Prevent trial abuse and keep services secure | Device and trial records | Our legitimate interests |
| Understand whether the apps and sites work, and improve them | Usage and website data | Our legitimate interests — you can turn app usage data off |
| Decide eligibility for pricing offers | Usage data, feedback records | Performing our contract with you |
| Answer feedback and support requests | Feedback, emails | Performing our contract with you |
| Publish feedback text publicly | Feedback text | Your consent (the checkbox) |
| Billing and tax records | Payment and subscription data | Legal obligation |
5. Who processes it for us
We do not sell or rent personal data. We use these service providers, who process data on our instructions:
| Provider | What for |
|---|---|
| Google (Firebase, Google Cloud) | Sign-in, database, file storage, website hosting, usage analytics, crash reports |
| Google Workspace | Our email |
| GitHub | Public feedback discussions — only text you allowed us to publish |
| Paddle | Payments, as merchant of record |
We may also disclose data where the law requires it.
6. Where it is stored
Our database, files and analytics are stored in Google Cloud's Mumbai region (India). Sign-in is processed by Google in the United States. Where data leaves the European Economic Area or the UK, Google's standard contractual clauses protect it.
7. How long we keep it
| Data | Kept for |
|---|---|
| Account, licence and device records | While your account exists. Deleted within 30 days of your request |
| Trial-use record (product + hardware identifier) | While the product offers free trials. Contains no name or email |
| Usage data | Raw events up to 13 months, then only summaries. On account deletion, the link to you is removed and the remaining data no longer identifies you |
| Feedback and support emails | Up to 3 years, or until you ask us to delete them |
| Billing and tax records | 8 years, as Indian law requires |
| Backups | Deleted data disappears from backups within 7 days |
8. Your rights
You can ask us to:
- see the personal data we hold about you,
- correct it,
- delete it (and your account),
- withdraw consent to publishing your feedback,
- object to our use of it for analytics — or simply turn usage data off in Settings.
Write to support@samvitlabs.ai from the email address on your account, so we can verify it is you. We will respond within the time the law requires.
If you are unhappy with our answer, you can complain to the Data Protection Board of India, or, if you live in the EU or UK, to your local data protection authority.
9. Emails from us
We only email you about your account, billing, security, and changes to our terms or this policy. Billing emails include receipts and a reminder before each yearly renewal. We do not send newsletters or marketing email. Product news lives on each product's changelog.
10. Children
Our products are not intended for anyone under 18, and we do not knowingly collect their data.
11. Security
Data is encrypted in transit and at rest. Access to our systems is limited to the people who need it — today, that is the founder. Our database cannot be read or written directly by any app or browser; every change goes through checked server functions.
12. Changes to this policy
We may update this policy. We will post the new version on this page and tell you in the apps. The date at the top shows the latest version.
13. Grievance Officer
Ramki, Director
SAMVIT AI LABS (OPC) PRIVATE LIMITED
Registered office details
Email: support@samvitlabs.ai
Part B — jaala
B1. What stays on your machine
Your jaala graph, your AI coding sessions, your source code and your files are stored on your own device. jaala reads your Claude Code session history locally. We never receive any of it.
jaala encrypts all its data at rest on your device — your graph and the files you attach to it — with a key held in your operating system's keychain. We never have the key, so we cannot read or recover your data.
B2. AI features
jaala's AI features run through your own Claude Code installation and your own Anthropic account. That traffic goes directly between your machine and Anthropic under your agreement with them. It does not pass through us.
B3. Usage data in jaala
Examples of jaala's usage events: app opened, import finished, search used, canvas opened. We also use usage data and your Support feedback to decide eligibility for the beta price described in Part B of our Terms.
Part B — thoga
B1. What stays on your device
Your flows, their settings and the credentials you store are kept in a database on your own device, encrypted at rest with AES-256 (SQLCipher). The key is held in your operating system's keychain (macOS Keychain, Windows Credential Manager, or the Linux Secret Service). Files your flows read or write stay where they are on your device. We never receive any of it, and we never have the key, so we cannot read or recover your data.
B2. The credential vault
API keys, tokens and passwords you store in thoga's credential vault are each encrypted (AES-256-GCM) and then stored inside the encrypted database. On macOS, you can require Touch ID or your device passcode before thoga can unlock its key.
B3. Peer-to-peer (P2P)
When you use P2P, data goes directly between your devices and the peers you add, over encrypted connections (iroh). thoga refuses connections from peers you have not added. To find each other, and to connect when a direct connection is not possible, devices use public relay and discovery servers run by n0, the developer of iroh. Those servers may see your device's network address and its thoga device ID, but not the content, which stays encrypted. None of this passes through our servers.
B4. Third-party services and AI
Flows that use third-party services or AI providers talk to them directly from your device, under your own accounts and API keys and your agreements with those providers. That traffic does not pass through us. Local AI models, such as those run through Ollama, keep the data on your device.