Legal

Privacy Policy

What we hold, why we hold it, where it lives, and what you can ask us to do with it.

Last updated 27 September 2026

1. Who this is from

Talking Bird is operated by Akshat Gupta, in India. Our postal address is available on request from privacy@talkingbird.in. Where this policy says “we”, it means Talking Bird.

2. Our role, and yours

Talking Bird answers questions about documents and spreadsheets that a customer connects to it. Almost everything it holds is content the customer put there, and that content frequently contains information about other people — staff, applicants, vendors, grantees.

Under India’s Digital Personal Data Protection Act, the customer is the Data Fiduciary for that content and Talking Bird is a Data Processor acting on their instructions. We do not decide what goes into a workspace and we do not use it for our own purposes. If you are an employee of one of our customers and want to know what is held about you, your employer is the right first stop; we will help them answer.

We are the Data Fiduciary for one narrow category: the account details of the people who sign in, and the enquiries sent to us through this website.

3. What we hold

WhatWhere it is storedWhy
Files you connect or uploadObject storage, one folder per workspaceThe source of every answer
Extracted text, in fragmentsPostgres, one row per fragmentWhat makes a document searchable
Numeric representations of those fragmentsPostgresHow the relevant passage is found
Spreadsheet contentsHeld in memory while a question is being answered; the file itself stays in object storageSo totals are calculated rather than estimated
Questions asked, and the answers givenPostgresConversation history you can read and delete
Account details: name, work email, rolePostgresSign-in and permissions
Your name and email address from Google or Microsoft, if you sign in with themPostgresSigning you in - nothing else is requested from that account
Credentials for systems you connectPostgres, encryptedRe-reading a source without asking you again
Mailbox tokens, if you connect emailPostgres, encryptedDrafting replies you send yourself

4. What we do not hold

  • No payment card details. There is no checkout on this site. Plans are agreed with a person and invoiced by hand, so card and bank details never reach the product.
  • No government identifiers collected by us, and no special-category personal data — unless a customer chooses to upload documents containing it, which is their decision to make.
  • No advertising or profiling data. We do not build profiles, and we do not sell or share anything with data brokers.

5. Cookies and tracking

This site sets no cookies and runs no third-party analytics. There is no Google Analytics, no advertising pixel and no session recorder anywhere in it — which is why you have not been asked to accept a cookie banner.

The application stores a few values in your browser’s local storage, which stays on your device and is never transmitted to a third party: your sign-in token, your light or dark theme preference, whether you have completed the product tour, and your own dashboard layout. Clearing your browser data removes all of them and signs you out.

6. Where it lives

  • Subscription. Amazon Web Services, in the US East (N. Virginia) region, USA. Storage, the database and the language model all run there, so data does not leave that region in normal operation.
  • Self-hosted licence. Entirely inside your own infrastructure. Nothing reaches us: no telemetry, no phone-home, no shared database. This policy then describes only what your own systems do.

7. Answering a question sends text to a model

To answer, the product sends the passages it judged relevant — not your whole corpus — to a language model. On the subscription service that model is Amazon Bedrock, called inside AWS. Under Bedrock’s terms those prompts and responses are not used to train models and are not retained by the model provider.

On a paid plan you may supply your own key for another provider instead. If you do, those passages go to that provider under your agreement with them rather than ours, and their privacy terms govern what happens next.

8. Data from Google and Microsoft accounts

Signing in. “Continue with Google” and “Continue with Microsoft” share only your name and email address with us. We use them to create your account and sign you in, and for nothing else.

Two features connect to a Google account, and only when someone in a workspace chooses to switch them on. Nothing is read from a Google account before that person has signed in to Google and approved the access on Google’s own consent screen.

FeatureWhat we accessWhat we do with it
Connect a Gmail mailboxMessages in that mailbox, the ability to mark them read, create drafts and send, and the mailbox's email addressRead new messages to find questions sent to your team; write a draft reply from your own data; mark the message as handled; send the reply once a person approves it, or automatically only if your workspace administrator has switched automatic sending on
Connect Google DriveRead-only access to files, and the account's email addressRead and copy the files in the folders you choose, so they can be searched and cited. We never change, move or delete anything in your Drive
  • Used only to provide these features to the workspace that connected them. Google user data is never used for advertising, never sold, never used to build profiles, and never used to train artificial intelligence models — ours or anyone else’s.
  • Not read by people. No one at Talking Bird reads your Google data unless you ask us to for support, it is needed to investigate abuse or a security incident, or the law requires it.
  • Not shared, except with the service providers in section 9 that we need to run the product (hosting, storage and the language model), under contracts that allow nothing else.
  • Stored securely. Access tokens are encrypted before they are saved. Copied Drive files, their extracted text, and email messages with their drafted replies are stored in your workspace’s own storage.
  • Removed when you disconnect. Disconnecting Gmail (on the inbox agent) or Drive (under Data) revokes our access and deletes the stored token immediately. You can also revoke it at any time from your Google account’s permissions page. Files and drafts already copied stay until you delete them, and deleting the workspace deletes all of it.

Talking Bird’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.

Connecting an Outlook mailbox through Microsoft works the same way, with the same limits: we read new messages, draft replies, mark messages as handled and send approved replies, and disconnecting deletes our access.

9. Who else is involved

We use a small number of sub-processors to run the service: Amazon Web Services (hosting, storage, and the language model through Amazon Bedrock), Vercel (serving this website), and Google (sending verification codes, invitations and password resets). We will give notice before adding a new one.

We do not otherwise disclose customer content. If we were ever compelled to by law, we would tell the affected customer unless we were legally prohibited from doing so.

10. How long it is kept

  • Content stays until you delete it. Deleting a file removes its searchable fragments with it, and deleting a workspace removes everything belonging to it — the database cascades the deletion from the workspace record through every dependent row.
  • Deleted data can survive in encrypted backups for up to 7 days before those backups age out.
  • Enquiries sent through this website are kept for 24 months, then deleted.

11. Your rights

Under the DPDP Act you may ask for access to your personal data, its correction, or its erasure, and you may withdraw consent. Where the data sits inside a customer’s workspace, that customer answers the request and the product gives them the tools to act on it directly. For the account details we hold ourselves, write to us and we will act.

Our grievance officer is Akshat Gupta, at privacy@talkingbird.in. We acknowledge a grievance within 3 business days and respond in full within 30 days. If you are not satisfied with our response you may complain to the Data Protection Board of India.

12. Security

Credentials and mailbox tokens are encrypted at the application layer with a key held outside the database, and the product refuses to store one at all if that key is missing rather than falling back to plain text. Workspaces are separated by checks that run on every read, and those checks are covered by tests that deliberately try to cross them. The full detail, including what is not yet in place, is on the security page.

13. Changes

When this policy changes we will update the date at the top, and for any change that materially affects customers we will tell workspace administrators directly rather than relying on you to re-read the page.

Questions about this page: privacy@talkingbird.in. Back to talkingbird.in.