How we look after your data

• Our application database runs on DigitalOcean servers in Bengaluru, India. Your account, workspaces, projects, team members, agents, tasks, leads and sign-in records are stored there.
• Photos and PDFs sent in chats are stored in DigitalOcean Spaces in New York, United States. They are private, are only served through our engine after it checks who is asking, and are deleted after 90 days.
• The website and app are served by Vercel. The app's server code runs in Vercel's Mumbai region and passes your requests on to our engine in Bengaluru.
• A few services process data outside India: email delivery, Google sign-in if you use it, AI models when agents run tasks, and connected apps if your workspace uses them. They are listed under service providers below.

Email codes

• A sign-in code has 6 digits, works once and expires after 10 minutes.
• Asking for a new code cancels any unused earlier code. After 5 wrong tries, a code stops working.
• We store only a keyed hash (HMAC-SHA256) of each code, never the code itself.
• Code requests are limited to 5 an hour for each email address and 30 an hour from each network. Network addresses are stored only as hashes.
• The sign-in form gives the same response whether or not an account exists for an email address.

Sign in with Google

• We use Google's standard sign-in flow with PKCE and ask only for your name, email address and profile picture.
• We accept a Google sign-in only when Google confirms the email address is verified.
• Each attempt uses a one-time value that expires after 10 minutes, and after sign-in we only send you to pages inside our app.

Sessions

• After you sign in, your browser keeps a random session token in a cookie marked HttpOnly, so page scripts cannot read it, and Secure, so it is only sent over HTTPS. Our production engine will not start if secure cookies are switched off.
• We store only a SHA-256 hash of the token. A session lasts up to 30 days, and signing out ends it on our servers straight away.

Cross-site request protection

• The session cookie is sent with SameSite=Lax, and our engine refuses any request that changes data when it comes from a website other than our app.
• Our engine only answers app requests that come through our own app server with a shared secret key. Anything else gets a “not found” reply. The exceptions are a health check and incoming payment webhooks, which must carry the sender's signature.
• Our production engine will not start with development secrets or without HTTPS for the app.

Everyone in a workspace has one of four roles. Each request is checked against your role before anything happens.

• Invitations are sent to an email address and are accepted only when someone signs in with that verified address.
• Members and pending invitations both count toward your plan's seats. The free plan has 2.
• Workspaces are isolated. If you are not a member of a workspace, it answers “not found”, exactly as if it did not exist. Projects from another workspace are refused the same way. Automated tests check this.
• An agent can use only the tools and app actions switched on for it, and each tool's approval setting is checked before it runs.
• Sign-ins, sign-outs, invitations, membership changes, workspace and project changes, agent changes, approval decisions and app connections are recorded in an audit log.

• The website and app are served over HTTPS, and our app talks to our engine over HTTPS.
• Our pages cannot be shown inside frames on other websites, which guards against clickjacking.

• LiveWe do not use your content to train AI models, and we do not sell it.
• LiveWhen an agent runs a task, we send the AI model provider only the content that task needs, to get a result back.
• LiveEach step of a task records which model ran, the tokens it used and what it cost, so you can see it on the task.
• LiveTest chats send nothing to anyone. Actions in connected apps that only read data run for real in a test; anything that would change data is simulated.
• LiveEach task has a spending cap, and a daily AI spending cap across the platform pauses customer-facing AI work if it is reached.
• NextSpending limits and alerts that you set for your own workspace.

Under India's Digital Personal Data Protection Act, 2023, you can ask us to give you information about your personal data, correct, complete, update or erase it, and you can withdraw consent, nominate someone to act for you and have your grievances addressed.

Write to outreach@prodigalai.com from your registered email address. The privacy policy explains each right, how long we keep data and how we handle data inside a customer's workspace.

These services process personal data for us, each only for the purpose shown. When we add channels such as WhatsApp, we will add them here.

• DigitalOcean

  What it does:

  Servers and databases

  Where:

  Bengaluru, India

  When:

  Always

• DigitalOcean Spaces

  What it does:

  File storage for photos and PDFs sent in chats

  Where:

  New York, United States

  When:

  When photos or PDFs are sent in chats

• Vercel

  What it does:

  Website and app hosting

  Where:

  App server code runs in Mumbai, India; pages are delivered through a global network

  When:

  Always

• Cloudflare

  What it does:

  DNS

  Where:

  Global network

  When:

  Always

• Postmark

  What it does:

  Email, such as sign-in codes and invitations

  Where:

  Outside India

  When:

  When we email you

• Google

  What it does:

  Optional sign-in

  Where:

  Outside India

  When:

  Only if you choose Sign in with Google

• Razorpay

  What it does:

  Payments

  Where:

  India

  When:

  When you buy credits

• AI model providers, such as Anthropic

  What it does:

  Processing the content a task needs to return a result

  Where:

  Outside India

  When:

  When an agent runs a task

• Brave

  What it does:

  Web search: only the search words, kept up to 90 days for billing and not linked to a person

  Where:

  Outside India

  When:

  Only for agents a workspace lets search the web

• Voyage AI

  What it does:

  Finding knowledge by meaning

  Where:

  Outside India

  When:

  When agents search knowledge. Voyage keeps nothing and trains on nothing we send

• fal.ai

  What it does:

  Making images: the image description and the image

  Where:

  Outside India

  When:

  Only for agents a workspace lets create images. fal keeps no copy

• Recall.ai

  What it does:

  The meeting notetaker: the meeting link, its recording and transcript

  Where:

  United States

  When:

  Only when a workspace's team sends a notetaker. Recording deleted once transcribed

• Google, Slack and HubSpot

  What it does:

  Apps a workspace connects directly: its calendar and Gmail, its Slack, its HubSpot

  Where:

  Outside India

  When:

  Only if the workspace connects them

• Pipedream

  What it does:

  Connected apps: signing in to your apps and running the app actions you add to agents

  Where:

  Outside India

  When:

  Only if your workspace connects an app (pilot)

What is in place today, what is partly done and what is still planned. A date is when it reached customers; we don't give dates for work that hasn't started.

If a security breach affects personal data we hold, we will tell the people affected and the Data Protection Board of India without delay, saying what happened, what it means for them and what we are doing about it. We will send the Board a full report within 72 hours of finding out, as India's data protection rules require, and post an update on our company page.

We do not hold any security certification yet, and we will not claim one until an independent audit is complete. Here is what we plan to work on next.

• PlannedSOC 2 readiness. Preparing our controls and evidence for a SOC 2 audit.
• PlannedSingle sign-on and SCIM. Sign in through your company's identity provider, and manage users from it.

If you think you have found a security problem in Dhanur AI, email outreach@prodigalai.com with “Security report” in the subject. Please include what you found, the steps to reproduce it, the pages or requests involved, and how we can reach you.

While you look

• Test only against your own account and workspace.
• Do not access, change or delete other people's data. If you reach it by accident, stop and tell us.
• Do not run denial-of-service tests, send spam or try to trick our team.
• Give us a reasonable time to fix the issue before you share it publicly.

We read every report and will keep you updated while we work on a fix. We do not run a paid bug bounty at the moment.