Privacy Policy

ThinkNCollab ("we", "us", or "our") is dedicated to safeguarding the privacy, confidentiality, and security of developers, engineering teams, and organizations accessing our platform via thinkncollab.com, the thinkncollab-shell CLI, WebRTC rooms, and programmatic APIs.

This Privacy Policy explains our practices regarding the collection, processing, transmission, storage, and erasure of personal data under the Digital Personal Data Protection Act, 2023 (DPDP Act, India), the General Data Protection Regulation (GDPR, EU), and applicable international privacy standards. For the purposes of DPDP, ThinkNCollab acts as the Data Fiduciary, and you act as the Data Principal.

• Registration Details: Name, verified email address, optional contact phone number, and bcrypt-salted passwords.
• Profile Information: Developer handle, avatar image (hosted via Cloudinary), job title, and bio information.
• Payment & Billing Data: Payment methods and invoices processed securely through our PCI-DSS Level 1 compliant gateway (Razorpay). ThinkNCollab never stores raw credit card numbers or banking secrets.
• Workspace & Board Records: Room names, Kanban cards, task assignments, due dates, tags, and team chat messages.
• Network Logs: IP address, browser user-agent, operating system, and endpoint access timestamps (retained for security audits and DDoS protection).
• Socket Connection States: Active room presence and connection heartbeats to display real-time member presence.

When you execute thinknsh share start in the ThinkNCollab CLI, an in-memory socket channel is established on the /thinknsh namespace. Terminal output chunks are relayed dynamically to authenticated room viewers. Terminal streams are entirely ephemeral — they are not recorded, transcribed, or stored on our servers unless the room owner explicitly activates session recording.

The CLI creates local configuration files in your home directory that remain strictly on your local machine:

• ~/.thinknsh_history — Your local shell command history (never leaves your computer).
• ~/.thinkncollab/config.json — Local aliases and prompt settings.
• ~/.tncrc — Encrypted local authentication token required for automated CLI operations.

We process your personal information strictly for legitimate operational purposes and service delivery:

• To authenticate your identity across our web workspace and CLI applications.
• To render real-time collaborative Kanban boards, active user presence, and notification alerts.
• To relay audio/video signals and screen-sharing packets during live developer meetings.
• To calculate automated task priority recommendations via the TaskScoreCalculator algorithm.
• To synchronize authorized GitHub commits, pull requests, and Google Calendar milestones.
• To process subscription payments and prevent platform fraud, abuse, or DDoS vectors.

ThinkNCollab maintains a strict policy: We do not sell, rent, or trade your personal data. Information is shared only under strict boundaries:

• With Room Collaborators: Your name, avatar, online status, and room contributions are visible to authorized members within your workspace.
• Authorized Subprocessors: Infrastructure and service partners (MongoDB Atlas, Cloudinary, Razorpay, Google, Hostinger email, Anthropic for opted-in AI chat, Slack for rooms that connect it, and browser push services) bound by confidentiality and data protection agreements. See Subprocessors below.
• Legal Compliance: When strictly required by law enforcement, court subpoenas, or regulatory authorities pursuant to valid legal processes.

• Client-Side End-to-End Encryption (E2EE): Meeting audio/video media is encrypted inside isolated Web Workers using ECDH-P256 key exchanges and AES-256-GCM. Session keys are derived peer-to-peer in your browser and are never revealed to our signaling servers.
• Zero-Cloud Recording Policy: Video meetings recorded via our built-in canvas recorder render locally on your machine's hardware and download directly to your disk. We do not store, stream, or buffer video meeting files on our cloud servers.
• TLS 1.3 in Transit: All web traffic, CLI interactions, and WebSocket relays require TLS 1.3 / HTTPS encryption.
• Data at Rest: Database records are encrypted at rest using AES-256 in MongoDB Atlas managed clusters.

ThinkNCollab provides intelligent assistance via internal AI engines and external AI connectors such as Anthropic Claude via the Model Context Protocol (MCP).

• Zero Foundation Model Training: We NEVER use your proprietary source code, private Git repositories, terminal stream outputs, task descriptions, or confidential workspace conversations to train public artificial intelligence models.
• Granular OAuth 2.1 Consent & Scoping: When connecting Claude or any MCP client, users explicitly select which workspaces/rooms to share and grant specific granular scopes (tnc.read, tnc.write, tnc.chat). Claude cannot access unshared rooms or resources outside granted permissions.
• End-to-End Encrypted (E2EE) Protection: Credentials and private terminal keystrokes are never passed to AI connectors. End-to-end encrypted room chat is readable by Claude only in rooms where the owner turns on Claude access, and only for messages sent after that (see Claude in Team Chat below).
• Ephemeral Inference & Real-Time Execution: Tool requests executed by Claude are performed in real-time under your authenticated session and are discarded once executed.
• Instant User Revocation: Users retain complete control over connected AI applications. You can inspect or immediately revoke access at any time from ThinkNCollab Settings under Connected AI Apps or via our OAuth revocation endpoint (/connect/revoke).
• Zero Data Brokerage: We do not license, sell, or disclose your codebase metadata to third-party AI vendors.

ThinkNCollab offers two optional ways to work with Anthropic's Claude. Both are off until someone with the right role turns them on, and both act only with the permissions of the person using them.

• AI connectors (MCP): When you connect Claude or another MCP client to ThinkNCollab, you choose which rooms to share and which scopes to grant (tnc.read, tnc.write, tnc.chat). The client can only reach those rooms, with your role in each. You can review or revoke a connected AI app at any time from Settings → Connected AI apps.
• @Claude in team chat: Only if a room owner turns on Claude access for that room. When a member writes "@Claude …", that message and the room data Claude looks up to answer (with that member's permissions) are sent to Anthropic's API, and the reply is posted in the same channel. Claude only reads; any change it suggests must be confirmed by the person who asked.
• End-to-end encrypted chat: When a room owner turns on Claude access, the room's AI device is added as a recipient for new encrypted messages from then on, so Claude can read the conversations it is asked about. Messages sent before that stay unreadable to it, and turning Claude access off stops it receiving new ones.
• Anthropic processes this data to produce the answer under its commercial terms, which do not allow it to be used to train Anthropic's models. ThinkNCollab never uses your code, tasks or conversations to train AI models.

Room owners and managers can optionally link a room to one Slack channel through the ThinkNCollab Slack app, so task updates appear in Slack and members can use /tnc commands and task buttons.

• What we receive from Slack: your Slack workspace ID and name, the ID and name of the channel you choose, and the bot token Slack issues for the app. The bot token is encrypted at rest (AES-256-GCM) and is never sent to your browser.
• Matching people: When someone uses /tnc or a task button, we look up that Slack user's email through the Slack API only to match them to their ThinkNCollab account, and then apply that account's role in the room. The lookup is kept in memory for up to 10 minutes and is not stored in our database.
• What we send to Slack: for tasks in the linked room only — task title, key, status, priority, due date, assignee names and a link back to ThinkNCollab — when tasks are created, assigned or finished (each can be turned off), when someone runs /tnc, and when a task link is pasted in a workspace that is linked to that task's room.
• We do not read or store your Slack conversations. The text after /tnc create is used only as the new task's title.
• Permissions requested from Slack: commands, chat:write, incoming-webhook, links:read, links:write, users:read and users:read.email. Every request from Slack is verified with Slack's signing secret before we act on it.
• Disconnecting: A room owner or manager can disconnect from the room's Integrations tab. We then revoke the bot token with Slack and delete the stored connection. A Slack workspace admin can also remove the app from Slack at any time.

• Imports from Jira, Trello and Slack exports: Files and API credentials you provide for an import are used only to run that import. Jira API tokens are not stored.
• Marketplace partner apps: When a room owner or manager installs a partner app, that app receives the room events and data it is approved for (for example task changes) and can use the Partner API only within the scopes granted. Uninstalling the app stops this immediately.
• Figma: Figma files you embed are loaded by your browser directly from Figma; we store only the link.
• Push notifications: If you allow browser notifications, short notification text (such as a title and a one-line message) is delivered through your browser vendor's push service (for example Google, Mozilla or Apple). You can turn notifications off in your browser or in Settings.
• Email: Account, invitation, reminder and billing emails are sent through our email delivery provider. Some emails contain a tracking pixel so we can tell whether they were delivered and opened.

Under the Digital Personal Data Protection Act, 2023 (DPDP) and GDPR, you possess comprehensive rights as a Data Principal:

• Right to Access & Summary: Request a summary of personal data processed by ThinkNCollab and the identities of any data fiduciaries with whom it was shared.
• Right to Correction & Erasure: Update inaccurate personal details or request the permanent erasure of your account and personal identifiers within 30 days.
• Right to Withdraw Consent: Revoke consent at any time for notifications, third-party integrations, or marketing emails.
• Right to Nominate: Under the DPDP Act, nominate another individual to exercise your rights in the event of death or incapacity.
• Right of Grievance Redressal: Direct complaints to our appointed Grievance Redressal Officer with guaranteed review within 30 days.

We use essential cookies strictly required to maintain secure user login sessions, remember workspace theme preferences, and prevent Cross-Site Request Forgery (CSRF). We do not use invasive third-party cross-site advertising trackers.

ThinkNCollab is directed at software engineers, teams, and professionals. We do not knowingly collect personal information from children under the age of 13. If you become aware that a child has provided us with personal data, please notify us immediately at privacy@thinkncollab.com for expedited removal.

ThinkNCollab enables optional integration with Google Calendar to synchronize team meeting schedules and task due dates.

• Minimal Access Scopes: We request only the calendar.events scope necessary to read upcoming room events and create task milestone reminders.
• No Ancillary Scopes: We never request access to Gmail, Google Drive, Google Contacts, or private files.
• Limited Use Compliance: ThinkNCollab's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
• Revocation: You can disconnect Google Calendar anytime via room settings or your Google Account Permissions page.

When connecting GitHub via our official GitHub App, OAuth, or Webhooks:

• Read-Only Metadata: We process commit titles, branch names, pull request numbers, and author handles to update Kanban cards on your board.
• No Proprietary Code Storage: We do not copy, index, or store your private codebase files, proprietary algorithms, or repository source code.
• Immediate Revocation: You can uninstall the ThinkNCollab GitHub App at any time from your GitHub Installation Settings to immediately sever webhook feeds.

We engage vetted infrastructure subprocessors to provide database hosting, media delivery, and payment gateways:

We may update this Privacy Policy to reflect technical advancements or legal revisions. When updates are published, the "Effective Date" at the top of this document will be updated. In cases of material changes, we will provide at least 30 days' advance notice via email or prominent in-app notification.

In accordance with the Information Technology Act, 2000 and the Digital Personal Data Protection Act, 2023, ThinkNCollab has appointed a designated Grievance Redressal Officer:

Office

Data Protection & Grievance Redressal Cell, ThinkNCollab

Email

support@thinkncollab.com

Postal address

Sushant AquaPolis, Crossing Republik, 201016, U.P., India

Support line

+91 96484 70308