JANTA AI

Privacy policy

Last updated 10 October 2026

Janta is an AI assistant for small businesses. It reads the apps a business connects, answers questions about them, and drafts work for a person to approve. This policy explains what Janta stores, who it shares it with and how long it keeps it.

Accounts and businesses

To sign in we store your name, email address and, if you sign in with Google, your profile picture. Each sign-in creates a session that records when it started, the IP address and the browser it came from. A business is an account that people belong to. Each member has a role (owner, admin, finance, sales, operations or marketing) that decides which screens, specialists and records they can open. When a business is set up we store its name and what you tell us about it: industry, description, a contact name and email, and the public links you list.

Website scanning

If you list your website or public social pages during setup, Janta fetches them through Firecrawl and asks an AI model for a short factual summary of the business (what it sells, to whom, where, and its tone). We keep that summary and whether each page could be read. We do not keep the pages’ text.

Connected apps

An owner or admin can connect apps such as QuickBooks, Google Workspace, Microsoft 365, HubSpot, Metricool, Notion, Calendly, Stripe, Airtable, ClickUp, Brevo, Odoo and Zoho. Some connections go through Nango, which holds the sign-in tokens for those apps on our behalf. Others connect directly to the app’s own MCP server: you sign in on the app’s page, or paste a key the app gave you. Those sign-in tokens and keys are stored encrypted (AES-256-GCM), only decrypted on our server, and never sent back to your browser. We store which apps are connected and whether each connection is working.

Janta reads these apps only when someone in the business asks a question or opens a screen that shows them, and only within the access the app granted. What a screen shows is cached for about five minutes. We do not copy your app records into our own database, except where they appear in a conversation, a draft or an approval. Disconnecting an app in Apps stops all further reads.

Google user data

When you connect Google Workspace, Janta asks Google for access to your Google Calendar (to read events and, once you approve, add or change them), the Google Docs and Sheets you paste a link to or ask Janta to create, the Google Drive files Janta creates or you choose to use with it, your email address, and permission to send email from your Gmail account when you approve a message. Janta cannot read your Gmail inbox or browse the rest of your Drive. It keeps the title and link of each Doc or Sheet you share so it can find it again by name, and forgets them when you disconnect Google.

Janta uses this data only to answer your questions, show it on your screens and carry out the actions you approve. It is sent to OpenAI’s API only as part of answering you, as described below. We do not sell Google user data, use it for advertising, or use it to develop, improve or train generalized AI or machine learning models, and people at Janta do not read it except with your permission, for security reasons, or to comply with the law.

Janta’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.

Conversations and AI processing

We store conversations with Janta and its specialists, along with which specialists answered, which apps they read, which model replied and how many tokens it used. To answer, Janta sends your question, the recent conversation, the business summary and the records its tools read to OpenAI’s API, which processes them to produce the reply.

Approvals and messages sent for you

By default Janta does not change a connected app or send a message on its own. Anything that would, such as adding a calendar event, updating a CRM record, sending an email or sending a WhatsApp message, is saved as a draft and waits until an owner or admin approves it, unless an owner set that kind of action to go ahead on its own. We keep each draft, who decided it, when, and what happened. Approved emails are sent from Janta’s sending address through our email provider, under your business’s name, with replies going to the person who approved them, or from the owner’s own Gmail or Outlook if the business chooses that in Settings. Where it has been set up, approved WhatsApp messages are sent through Meta’s WhatsApp Business Platform.

Your customers’ messages

If a business turns on Janta for customers, the messages people send to its linked WhatsApp number are passed to our AI model provider so Janta can reply. Janta answers them only from the business profile and what the business taught it, never from its connected apps or other customers’ records, and it hands the conversation to a person when it should. The business can switch this off at any time in Settings. Websites and files the business gives Janta for this are kept only as text, not as the original files; a website is read through Firecrawl, and a photo is read by our AI model provider. The business can remove any of them in Settings.

Usage records

To run and protect the service we record usage: each AI request’s tokens, cost, timing and outcome; each call to a connected app (which app, which endpoint, whether it worked and how long it took); which screens are opened; and changes to access such as invitations, role changes and removals. These records let us apply usage limits and investigate problems.

The people who operate Janta can see businesses, members and usage. To resolve a support issue they can open a business’s conversations or sign in as a user; each time they do, it is recorded.

Where data is stored

Janta’s database is PostgreSQL on a virtual private server rented from Hostinger. It is backed up daily, and backups are kept for 14 days unless we set a different period. Connection tokens are held by Nango. OpenAI, Firecrawl, our email provider and Meta receive only what they need for the task they perform.

Cookies

We use a cookie to keep you signed in, and your browser remembers whether you keep the side menu open. We do not use advertising or tracking cookies.

Keeping and deleting data

We keep account, business and conversation data while the account is in use. The member who started a conversation, or an owner or admin, can delete it, which removes its messages; usage records stay without the link to the conversation so monthly totals remain correct. An owner or admin can remove members and disconnect apps at any time, and can download everything the business holds from Settings. The owner can delete the whole business there too. Deleted data leaves our backups as they expire.

To see or correct what we hold about you, or to have your account or your business and its data deleted, email <[email protected]>.