NOD Executive Intelligence Private Limited
Privacy Policy
This policy explains how NOD Executive Intelligence Private Limited ("NOD", "we", "us" or "our") processes personal data when you visit our website, create an individual account or workspace, or use our dashboard, companion applications, integrations and support services (the "Services").
Features and integrations depend on availability, your plan, your permissions and your workspace settings. A description of an optional feature does not mean that it is enabled for every account.
1. Who we are and how to contact us
The Services are operated by NOD Executive Intelligence Private Limited, a company registered in India. CIN: U62091GA2026PTC018412.
Registered office:C/O MR. SUNIL VITHOBA NAIK, H.NO. 66/1 (B-TF3),
BUILDING-B, DICARPALI NAGESH RESIDENCY,
SOUTH GOA, GOA – 403707, INDIA
Website: nod-ei.site
Privacy and grievance contact: Cosam Crasto, CTO / Co-founder
Email: supportnod@gmail.com
Use this contact for privacy questions, complaints, requests to exercise your rights, or concerns about data received through a connected service. Please do not send passwords, authentication codes or unnecessary identity documents.
2. Individual accounts and workspaces
For website visits, account administration, billing, security and our own support activities, NOD determines how and why personal data is processed. Where applicable law uses these terms, we act as a data controller or Data Fiduciary for those activities.
When a customer connects communications, files or other content for its workspace, NOD processes that content to provide the Services on the customer's instructions. Depending on the activity and applicable law, the customer acts as controller and NOD acts as processor. Applicable customer agreements and data processing agreements also govern that processing.
Workspace owners and administrators manage membership, roles, connected sources and sharing. They may be able to view shared workspace content, activity and records, including information about employees, contractors and clients. Do not assume that content posted to a shared workspace is private from its administrators or other authorised members. Personal features and client portals have their own access boundaries.
If your account is managed by an organisation, ask its administrator about its policies, monitoring and retention choices. You may also contact us; where your request concerns content controlled by that organisation, we will coordinate with it as appropriate.
3. Personal data we collect
We receive data directly from you, from people who invite or communicate with you, from authorised workspace administrators, from services you connect, and from your use of the Services.
- Account and workspace information
- Your name, email address, authentication information, phone number and verification status, workspace name and abbreviation, membership and role, preferences, and optional job title or team size. Account and phone identifiers associate commands and activity with the right user and subscription seat.
- Age-screening information
- A date of birth entered for screening is used to calculate eligibility. The screening process retains the result, screening time and policy version rather than the full birth date. This is a self-declaration, not identity verification or verified parental consent.
- Connected communications and work content
- Messages, sender and participant identifiers, channel or group details, timestamps, attachments, documents, tasks, reminders, project instructions, client updates, approvals and other material submitted or made available through an enabled integration. This can include data about people who do not have a NOD account.
- Audio, transcripts and AI interactions
- Voice notes or audio submitted for processing, transcripts, questions and relevant context sent to AI features, generated answers, summaries, classifications and related work records.
- Development and infrastructure information
- Where enabled, repository, branch, commit, issue and review information; submitted code comments or snapshots; and resource identifiers, utilisation measurements, operational events and cost-related information from connected monitoring tools.
- Billing and transaction information
- Your plan, seat count, billing country and currency, subscription status, transaction and invoice references, and records of accepted terms. Payment details are handled through the payment provider's checkout; NOD processes the billing information and payment status returned to it.
- Device, usage and security information
- IP addresses, browser or device information, session and sign-in records, request and event identifiers, integration status, errors, notification tokens and, where enabled with the relevant choice, product analytics. Operational records may include content associated with a request or transcription when it is processed or logged.
- Support information
- Your contact details, correspondence, bug reports and screenshots, files or other information you choose to provide when contacting support, including before registration.
Please provide only information needed for your use of NOD. Avoid submitting highly sensitive personal information, payment credentials, passwords or secret keys unless a specific feature requires and supports that information.
4. How and why we use data
We use personal data to:
- Create and authenticate accounts, verify contact details, manage workspaces and apply access permissions.
- Provide enabled features, including task extraction, reminders, search, transcription, AI responses, reports and authorised actions in connected applications.
- Maintain subscriptions, allocate seats, process billing and keep transaction and acceptance records.
- Deliver service messages, configured reminders, alerts and notifications, and respond to support requests.
- Diagnose failures, maintain and improve service reliability, and understand product usage through configured analytics and your choices.
- Protect accounts, investigate suspicious activity, enforce service rules and prevent misuse, including unauthorised credential sharing.
- Meet applicable legal obligations, handle complaints and disputes, and establish or defend legal claims.
Where EU or UK data protection law applies and NOD acts as controller, the legal basis depends on the activity: performing a contract with you; our legitimate interests in operating, securing and supporting the Services, balanced against your rights; complying with legal obligations; or your consent for processing that requires it, such as optional analytics. Where we rely on consent, you can withdraw it without affecting the lawfulness of earlier processing. The legal basis for customer-controlled workspace content is determined by the customer.
For processing subject to Indian law, we rely on consent or another permitted basis where applicable. A privacy notice does not replace a consent or authorisation that the law requires.
AI classifications and summaries can be inaccurate. Review results before using them for important decisions. This policy does not authorise employers or customers to make decisions about people that would otherwise be unlawful.
5. Connected services and permissions
Connecting an account or source allows NOD to receive and use the information made available through that connection. The scope depends on the permissions granted, selected sources and enabled features. Incoming events may need to be received and inspected before NOD can determine whether they should create a task or another record.
WhatsApp linked devices
NOD uses a Baileys-based linked-device connection for its WhatsApp integration. This is a linked-device integration, not a representation that NOD's connection is the official WhatsApp Cloud API. Processing can include linked chat or group messages, participant identifiers, attachments, voice notes and connection/session credentials needed to operate the integration. Connect only accounts and conversations you are authorised to make available to NOD, and inform other participants where required.
Google services
Google sign-in provides identity information used for account access. Separate permissions for Gmail, Google Calendar or Google Drive enable corresponding features, such as processing selected email folders, calendar information or files. These connections are optional where the related feature is optional. Relevant content may be processed by NOD's configured AI or other service providers to provide the feature you enable.
NOD does not use Google user data for advertising or to train AI models. NOD's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements. Human access to Google user data is limited to circumstances that policy permits, such as your affirmative agreement to access specified data, necessary security investigation, or legal requirements.
Other work tools and automation
Enabled connections can include Slack channels, Jira issues, GitHub development activity, CRM tools such as HubSpot, and Zapier automation. NOD receives relevant content, webhook events and metadata and may send instructions or content to a connected application when you use or configure an action. Assistant and companion tools, including the Android assistant and VS Code CodeFlow extension where available, can submit commands, device identifiers, development context and authentication information needed for their functions.
Each external service also processes information under its own policies and your relationship with that service. Review permissions before connecting a source, and do not grant access to data you are not entitled to share.
6. AI, transcription and model training
AI features process relevant customer content and context to generate extracted tasks, classifications, summaries and responses. Text processing can use NVIDIA AI endpoints, and audio transcription can use Deepgram, depending on the configured feature and deployment. Processing may include prompts, source excerpts, voice recordings, transcripts and generated output.
NOD does not use customer messages, files, audio, transcripts or AI conversations to train, fine-tune or improve AI models. Using a model to produce a requested result is different from using content to train that model.
This statement describes NOD's own use of customer content. Providers' retention, abuse monitoring, human review and model-training terms depend on the service, account configuration and applicable agreement. This policy does not promise universal zero retention or a provider-wide no-training setting. Contact our privacy contact for information about the provider arrangements applicable to a feature before submitting content that requires particular restrictions.
Where available, local-only modes or workspace AI restrictions can limit processing. Do not assume that all AI runs on your device: cloud AI features send relevant content to the configured provider.
7. Who receives personal data
We do not sell or share personal data for advertising. Providing the Services does require disclosures in the following circumstances:
- Workspace participants and chosen recipients: information is available to members, administrators, clients and external recipients according to workspace permissions and the sharing or automation you configure.
- Service providers: providers support hosting, databases, authentication, storage, search, AI, transcription, payments, email, notifications, security and diagnostics. Depending on the enabled feature and deployment, these include Supabase, Render, Vercel or Cloudflare, NVIDIA, Deepgram, Razorpay, Resend, Firebase Cloud Messaging, Sentry, PostHog and externally hosted Qdrant.
- Connected platforms: information and instructions are exchanged with services you connect, such as WhatsApp, Google, Slack, Jira, GitHub, HubSpot and Zapier, as needed for the relevant functions.
- People supporting NOD: customer information may be accessed in connection with support, troubleshooting, security, administration or legal matters. Contact us about access arrangements for a particular request; additional restrictions apply to Google user data as described above.
- Legal and protective disclosures: we may disclose information where required by law or valid legal process, or where necessary and legally permitted to investigate abuse, protect people, enforce agreements or defend legal claims.
- Business changes: information may be disclosed as part of a proposed or completed restructuring, financing, merger, acquisition or transfer of the business, subject to applicable law and any additional consent requirements.
Some providers, including payment services and connected platforms, may also act for their own purposes under their own privacy notices. Contact us for information about the providers applicable to your workspace.
8. Cookies, analytics and notifications
We use essential cookies and browser/device storage for sign-in, security, age-screening results and saved preferences. Optional product analytics, where configured, starts only after you allow analytics through NOD's cookie controls. The product analytics implementation disables session recording and automatic content capture. Global Privacy Control and Do Not Track are treated as a refusal of optional analytics.
You can revisit Cookie settings in the website footer and change your choice. Some changes apply on the next page load. You may also control storage through your browser, although blocking essential storage can affect sign-in. See our Cookie Notice for storage details.
Configured reminders, operational alerts and optional engagement prompts may use email, WhatsApp or device notifications. Available preferences let you control optional alerts; you can also disable device notifications in your operating system. Security, account and billing notices may still be sent when necessary to operate your account. We do not use this policy as consent to unrelated marketing.
9. Local messaging and client sharing
Where local messaging is available and selected, supported message content can travel directly between participating devices using local networking or peer-to-peer connections. Authentication, connection signalling, membership and other operational metadata may still involve NOD's infrastructure. Local mode does not mean that every piece of related data stays off cloud services.
Cloud messaging and a cloud fallback, where available and selected, process message content in cloud infrastructure. Device-local records, copies received by other participants, exports and third-party copies may remain outside NOD's central storage controls.
Internal and client-facing workspaces have separate permissions. Publishing an internal update to a client portal discloses the selected content to the authorised client audience. Review the destination and preview before approving a transfer, including an update prepared from local information.
10. Retention, disconnection and deletion
We retain personal data according to its purpose, applicable customer or workspace settings, operational needs, and legal obligations. Data is not kept permanently merely because it is classified as a useful work record.
- Accounts and workspace records: retained while needed to provide and administer the account or workspace, then subject to deletion or anonymisation, applicable customer instructions and legal exceptions.
- Temporary chat content: where enabled, workspace retention settings can expire selected temporary messages. Supported settings include 24, 48, 72 or 168 hours. Holds, replies, attachments and protected work records may affect eligibility. Expiry can remove message content while leaving limited record information; it does not guarantee that every copy or backup disappears at that moment.
- Tasks, reports, documents and other work records: retained for their ongoing workspace purpose and applicable settings rather than the temporary-message schedule.
- Credentials and integration records: retained as needed for the connection and account security. Disconnecting stops future access through that connection; it does not automatically erase previously imported messages, transcripts, tasks, reports or recipient copies. You can also revoke access in the external provider's settings.
- Support, diagnostics and security records: retained as needed to resolve issues, operate and protect the Services, investigate incidents and address disputes.
- Billing and legal records: retained for applicable accounting, tax, recordkeeping and legal requirements, including after account deletion.
- Backups and provider copies: deletion from active systems may precede removal through backup rotation or a provider's deletion cycle. A request cannot erase copies that another recipient independently controls.
You can submit an account deletion request through available account controls or contact supportnod@gmail.com. The in-app process records a request for completion; it is not an instant purge of every system. We verify requests and handle them within the time required by applicable law, explaining any permitted extension or exception.
Deleting your personal account and deleting an organisation's shared workspace are different requests. If you own a workspace used by others, the in-app flow may require a handover or membership changes. This does not prevent you from contacting us to exercise your statutory rights. We assess shared content, other people's rights and retention obligations separately.
11. Security
Security measures used by the Services include authentication, role-based access controls, protected sessions, encrypted transport, safeguards for stored integration credentials, and filtering of recognised secrets in supported processing paths. No transmission, storage system or automated filter is completely secure, and secret detection may miss information.
Protect your devices and account credentials, review membership and integration permissions, and tell us promptly if you suspect unauthorised access. These responsibilities do not replace NOD's own obligations. If a personal data breach occurs, we will make notifications required by applicable law.
12. International processing
NOD is based in India and serves users internationally. Depending on the feature, deployment, provider and support arrangements, personal data may be processed outside your country, including in India and in countries where relevant providers operate. International availability does not mean that data is stored only in your country or region.
Cross-border processing is subject to applicable data protection requirements. Where a transfer requires a particular safeguard, that requirement must be addressed in the arrangements for the transfer; accepting this policy does not by itself replace that safeguard. Contact us for information about processing locations and transfer arrangements applicable to your workspace or proposed deployment.
13. Your choices and privacy rights
Depending on your location, our role and the law that applies, you may have rights to:
- Receive information about, and obtain access to or a copy of, your personal data.
- Correct inaccurate or incomplete information and request deletion, subject to legal exceptions.
- Receive certain data in a portable format, restrict processing or object to processing, including processing based on legitimate interests.
- Withdraw consent where processing relies on consent, and control optional analytics and notifications.
- Exercise applicable rights concerning significant automated decisions, sensitive personal information, advertising-related sale or sharing, and appeals against a request decision.
- Raise a grievance or complain to the competent data protection regulator.
Available account controls let you correct profile details, export your own records, manage notifications, disconnect integrations and request deletion. An individual export may not include every shared workspace record; contact us or the workspace administrator for help with a broader request.
Send requests to supportnod@gmail.com, identifying the account or workspace and the right you wish to exercise. We may need proportionate information to verify your identity or an authorised agent's authority. We will respond within the applicable legal deadline and explain any permitted limitation, extension or fee. We will not unlawfully discriminate against you for exercising your rights. If you disagree with our response, reply to the privacy contact to request review.
EU / EEA and UK
Where the GDPR or UK GDPR applies, rights include access, correction, erasure, restriction, portability, objection and withdrawal of consent where applicable. You may complain to a supervisory authority, including the authority in the country where you live or work or where an alleged infringement occurred. UK users can contact the Information Commissioner's Office.
India
You may contact our grievance contact about your personal data. Rights under India's Digital Personal Data Protection framework apply as relevant provisions come into force and subject to their conditions, including rights concerning information, correction, erasure, grievance redressal and nomination. We do not describe provisions with a future commencement date as already in force.
United States
US state privacy rights depend on your state and whether the relevant law applies to NOD. Where applicable, these may include access, correction, deletion, portability, opt-outs, authorised-agent requests and an appeal. California residents may have rights to know the categories, sources, purposes and recipients of personal information, as described in this policy. We do not sell or share personal data for advertising. Request information or exercise applicable rights through the contact above.
14. Age eligibility and young users
NOD's intended audience includes people aged 13 and above, subject to local legal requirements. Current self-service registration is restricted to users aged 18 or older. Access for users aged 13–17 is not currently available through that registration flow, and we do not currently offer a verified parental-consent process. A stated minimum age of 13 does not remove higher local requirements or establish a minor's capacity to enter a subscription contract.
Before introducing access for younger users, relevant eligibility, parental or guardian authorisation, privacy safeguards and subscription arrangements must be addressed. We will update this policy and applicable notices when those arrangements change. The Services are not intended for children under 13. If you believe a child has provided personal data without required authorisation, contact us so we can investigate and take appropriate action.
15. Changes to this policy
We may update this policy to reflect changes to the Services, our practices or applicable requirements. The effective date and version appear at the top. For material changes, we will provide appropriate notice through the Services or another suitable channel and obtain fresh consent where required before beginning relevant new processing.
Questions or concerns? Contact Cosam Crasto at supportnod@gmail.com.