Teamski
Privacy Policy
Last updated 2 October 2026
This policy explains what information Teamski ("we", "us") collects when you use Teamski at https://teamski.in (the "Service"), how it is used, and who it is shared with. By using the Service you agree to this policy. If you do not agree, please do not use the Service.
1. Information we collect
Account information. When you sign up or sign in, we receive your email address and, if you sign in with Google, Microsoft or GitHub, the basic profile information that provider shares, such as your name and profile picture. You may also add a display name and username.
Content you create. Messages in channels and direct messages, files you upload, files agents create, tasks you give agents, instructions you write for agents, and edits to any of these.
What agents remember. The Service may keep short notes and summaries drawn from conversations so agents can refer back to them. You can turn this off in Settings. Deleting or editing a message removes notes that were recorded against it.
Connected accounts and keys. If you connect another service (for example Google Sheets, GitHub, Notion or another app), we store the access tokens that service gives us so agents can act on your behalf. If you add an API key for an AI provider, we store that key. These are used only to carry out the actions you or your team ask for.
Usage information. Which AI model answered, how many tokens a request used, how long it took, and whose key paid for it. This is used to show usage, apply plan limits and estimate costs.
Technical information. Like most websites, our servers and hosting providers may record your IP address, browser type and request logs.
Payment information. If you buy a paid plan, payment is handled by a third-party payment processor. We receive confirmation of payment and your plan details, not your full card number.
2. How we use information
- To provide, operate and maintain the Service.
- To send your messages, files and instructions to the AI model chosen for your workspace so it can respond, and to carry out actions you approve in connected services.
- To show usage, apply plan limits and process payments.
- To respond to support requests and send service notices.
- To investigate misuse and to comply with legal obligations.
We do not sell your personal information, and we do not use your content to show advertising.
3. AI models and third parties
To answer a request, the content of that request (including relevant earlier messages, attached files and notes) is sent to an AI model. Which model depends on the choices made in your workspace:
- Built-in models run on servers we operate or rent.
- Models on your own or your team's key (for example Anthropic, OpenAI, Google, NVIDIA, xAI, Groq, DeepSeek, Mistral, OpenRouter or Together) receive that content directly and handle it under their own terms and privacy policies.
We also rely on other providers to run the Service, including:
- Supabase, for our database, file storage and sign-in.
- Our server hosting provider.
- Google, Microsoft and GitHub, if you choose to sign in with them.
- Web search providers (such as Brave Search or DuckDuckGo), which receive search queries when an agent searches the web.
- Apps you connect, such as Google Sheets, GitHub, Notion, Linear, Atlassian, Asana, Sentry, Stripe, Canva or Hugging Face, which receive the requests an agent makes on your behalf.
- An email provider (Resend), which sends invitations to the addresses people enter, and account emails such as reminders about your plan or your account.
- Meta (Facebook and Instagram), which measures visits and signups that come from our ads. See section 6.
- Google Sheets, where we keep the details you send if you contact us about an Enterprise plan, so we can follow up.
- A payment processor, once paid plans are available.
Each of these handles information under its own terms. We are not responsible for their practices.
4. Google user data
If you connect a Google account, the Service requests access to Google Sheets only. It reads a spreadsheet when you give an agent its link, and adds rows to a spreadsheet only when you approve that action. This data is used only to carry out those requests and is not used for advertising.
Teamski's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
5. Who can see your content
Content in a project is visible to the members of that project. Direct messages are visible to the people in that conversation. On plans that include it, members of a project can see who used the project's shared key and an estimate of what they spent. Background agents act using the connected accounts of the person who started them.
6. Cookies and local storage
We use cookies that are needed to keep you signed in and to protect sign-in flows. Your browser also stores some of your settings locally.
We also use the Meta Pixel, an advertising tool from Meta, to learn whether our ads on Facebook and Instagram bring people to Teamski. It sets a cookie and tells Meta which pages of our site you visit, along with your browser, device and IP address, and when you sign up or send us an Enterprise enquiry. It does not receive your messages, files, projects or anything else inside your workspace, and it is never loaded on password-reset or sign-in links. Meta handles this information under its own privacy policy.
When you sign up, or send us an Enterprise enquiry, our server also tells Meta about it directly, through Meta's Conversions API. That message includes a hashed (one-way scrambled) copy of your email address and account ID, which Meta uses to match the signup to an ad, along with your IP address and browser. It is sent once per signup or enquiry, and it is sent even if your browser blocks the pixel.
You can limit how Meta uses this through your Meta ad preferences. Blocking third-party cookies or using an ad blocker stops the pixel in your browser - Teamski works the same either way.
7. Keeping and deleting information
We keep information for as long as your account is active or as needed to provide the Service. You can delete messages, connections and keys in the app, and delete your whole account in Settings → Account. Projects other people are in are handed to another member rather than deleted. Some information may remain in backups or logs for a period, or where we are required to keep it by law.
8. Security
We take reasonable steps to protect information, but no method of storing or sending data over the internet is completely secure. We cannot guarantee the security of any information, and you use the Service at your own risk.
9. Your choices and rights
Depending on where you live, including under India's Digital Personal Data Protection Act, 2023, you may have the right to access, correct or delete your personal information, or to withdraw consent. To make a request, email us. We may need to confirm your identity first.
10. Children
The Service is not intended for anyone under 18. If you believe a child has given us personal information, contact us and we will take steps to delete it.
11. Transfers
Our providers may process information in countries other than yours, including outside India.
12. Changes
We may update this policy. When we do, we will change the date at the top. Continuing to use the Service after a change means you accept the updated policy.
13. Contact
Questions or requests about your data, including access, correction or deletion: use our . You can also delete your account yourself in Settings → Account.