Privacy Policy

1. Introduction and Scope

1.1. Overview

Welcome to Squirrel. Squirrel is an artificial intelligence (“AI”) executive companion application designed to join, analyze, transcribe, summarize, and execute autonomous workflows across enterprise application ecosystems based on workplace communications (the “Services”). The Services are operated, provided, and controlled by the founders Sujal Krishna, Sounak Roy, and Sarthak Mondal, operating under the brand name Squirrel (collectively referred to as “Squirrel Tech Services,” “we,” “us,” or “our”). As of the Last Updated date, Squirrel Tech Services is an unincorporated business entity with its primary operations and administrative address at KP 5, Prashanti Vihar Road, KIIT University, Bhubaneswar, Odisha 751024, India.

This Privacy Policy (“Policy”) forms a legally binding agreement between you—whether an individual end-user, an administrator managing an organizational account, a corporate subscriber, or a meeting participant (collectively, “you,” “your,” or “User”) — and us. This Policy comprehensively details our absolute commitment to the protection of personal data, the precise mechanisms through which we collect, store, process, transmit, and delete information, and the robust technical and organizational guardrails we enforce to maintain enterprise-grade confidentiality.

1.2. Scope of Application

This Policy applies strictly to all processing operations executed by us or on our behalf via:

• The website located at https://meetsquirrel.com (the “Website”).
• The Squirrel AI executive software platform, application programming interfaces (“APIs”), and software extensions.
• Any interactions, communications, or support tickets initiated between you and our teams.

This Policy does not govern the processing of data by third-party platforms that you independently connect to our system, nor does it control the internal data handling policies of corporate entities who license our Services for their workforces (who act as Data Controllers under applicable laws).

1.3. Regulatory Compliance Framework

Recognizing the cross-border nature of digital communication and enterprise workflows, this Policy is engineered to satisfy the rigorous and distinct compliance bars established under multiple globally significant data protection regimes, including but not limited to:

• The Indian Digital Personal Data Protection Act, 2023 (“DPDP Act”), given our jurisdictional anchor in Odisha, India.
• The European Union General Data Protection Regulation (“EU GDPR”) and the United Kingdom General Data Protection Regulation (“UK GDPR”) (collectively, “GDPR”), governing processing activities involving data subjects located within the European Economic Area (“EEA”) and the United Kingdom.
• Other regional, national, and state-level data privacy enactments globally, insofar as they mandate specific baseline protections for corporate and individual digital identities.

1.4. Acknowledgement and Minimum Age Structure

By creating an account, authenticating our browser automation utilities, permitting our AI companion to enter a communication channel, or interacting with our Services, you explicitly acknowledge that you have read, understood, and agreed to the practices described herein.

The Services are engineered strictly for professional, commercial, and enterprise utilization. You are strictly prohibited from registering an account, manipulating our systems, or otherwise provisioning personal data to us if you are under the age of 16 years. We do not knowingly collect, solicit, or process information from individuals under this age threshold. If we discover that personal data of a person under 16 has been processed without verifiable parental or guardian consent, we will permanently eliminate such records from our production environments within our standard data lifecycle.

2. Definitions

To ensure absolute transparency and lexical alignment for corporate legal reviews, internal compliance audits, and regulatory inquiries, the following terms shall carry the definitions specified below:

• “AI Processing” means the computational execution of machine learning, natural language processing (“NLP”), deep learning architectures, automatic speech recognition (“ASR”), and semantic analysis algorithms to transform unstructured raw audio or text files into structured actionable datasets, meeting intelligence outputs, and cross-application API calls.
• “Autonomous Task Execution” refers to the execution of digital actions—such as dispatching emails, provisioning records inside a CRM, modifying tables in a project management interface, or orchestrating database updates—across a User’s third-party software stack without explicit, prompt-by-prompt human confirmation, driven by parameters defined via user-granted authentication permissions.
• “Browser Automation” means the algorithmic simulation of human user interaction via headless or headed virtualized web browser sessions, utilized by our systems to securely enter, observe, capture, and exit digital web-conferencing software spaces as an invited participant.
• “Customer Data” means the electronic data, text, messages, graphics, documents, code, or other materials submitted, stored, or processed by a User or on a User’s behalf via the Services, excluding Meeting Data.
• “Data Controller” or “Principal” means the natural or legal person, public authority, agency, or other body which, alone or jointly with others, determines the purposes and means of the processing of personal data. Under this Policy, enterprise customers utilizing Squirrel for their workforces typically operate as Data Controllers, whereas individual independent users may share direct consumer-to-business processing dynamics.
• “Data Processor” or “Data Fiduciary” or “Data Importer” refers to the entities executing processing tasks on behalf of a primary data authority or managing data processing frameworks within specific legislative terminology (e.g., Data Fiduciary under the DPDP Act).
• “Meeting Data” means all informational artifacts captured, calculated, derived, or generated during a synchronized digital communication event serviced by Squirrel, including raw audio streams, speaker identification arrays, automatic transcripts, parsed action items, calculated timeline benchmarks, strategic decision matrix maps, and subsequent AI-generated text documents.
• “Personal Data” or “Digital Personal Data” means any information relating to an identified or identifiable natural person; an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier, or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural, or social identity of that natural person.
• “Subprocessor” means any third-party infrastructure host, technical utility, AI application infrastructure provider, or specialized software vendor engaged by us to process Personal Data or Meeting Data under a strict, execution-specific written contract.

3. Information Collected

We collect several categories of information to provide an enterprise-grade AI companion experience. This collection occurs directly from your inputs, automatically via system use, and through third-party platform authentications.

3.1. Account and Profile Information

When you create a Squirrel account, initiate a subscription plan, or interact with our administrative onboarding portals, we collect:

• Identity Data: Full legal name, corporate title, professional affiliation, and internal organizational hierarchy parameters.
• Contact Data: Direct professional email address, telephone numbers, and designated corporate correspondence channels.
• Authentication Credentials: OAuth 2.0 security tokens derived via secure Single Sign-On (“SSO”) utilities (e.g., Google Workspace Authentication, Microsoft Azure AD, Zoom OAuth). We do not record or view plaintext primary user account passwords for these external networks.
• Transactional and Billing Data: Detailed transaction histories, active subscription status flags (Basic, Pro, or Max plans), billing addresses, and operational tax identifiers (e.g., GSTIN numbers where applicable under Indian financial regulations). All structural financial transactions are executed exclusively via our secure payment gateway partner, Razorpay. We do not harvest, read, or cache credit card account strings, bank verification digits, or primary security PINs within our servers.

3.2. Technical and Core Operational Data

To maintain the security, latency optimization, and reliability of our platform, our system architecture automatically records technical telemetry, including:

• Device and Environment Characteristics: Internet Protocol (“IP”) addresses, browser type, hardware architecture, operating system variations, language selections, and screen resolution matrices.
• Network Logs: Absolute timestamps of server connections, API routing paths, volume of data transmitted, system latency maps, and application crash diagnostics.
• Essential Session Cookies: Minimal stateful identifiers required purely to keep you securely authenticated during active browser sessions and preserve essential UI configurations.

4. Meeting Data and Audio Processing

The core value proposition of Squirrel lies in its advanced ability to transform messy, unparsed multi-party speech into strategic business execution layers. This section outlines the precise lifecycle of your live conversational content.

4.1. Capture and Browser Automation Framework

Squirrel does not possess offline recording functionality, physical environment wiretap features, or ambient background monitoring code. It only captures audio and metadata when explicitly invited to join an active digital conferencing space.

• Execution via Browser Automation: Squirrel enters digital meetings using browser automation architectures. When a meeting is scheduled and verified by a User, a dedicated, isolated virtual instance launches a secure browser session. This virtual browser connects to the target video conferencing provider—specifically Google Meet, Microsoft Teams, Zoom, or Cisco Webex—acting exactly like a human attendee arriving via a standard web link.
• In-Meeting Presentation: To ensure absolute clarity, the virtual instance identifies itself transparently in the meeting participant directory, displaying a clear structural label (e.g., "Squirrel AI Companion [Host: User Name]").
• Data Streams Captured: The virtual browser session processes the digital audio stream outputted by the conferencing bridge, alongside raw participant roster shifts, chat logs (where permitted by system rules), and platform-native speaker identity tags. Squirrel does not capture, render, or cache the video feeds or screen-sharing video frames of attendees, minimizing unnecessary data footprint.

4.2. Ingestion Matrix: The Structural Components of Meeting Data

The moment our virtual browser connects to a meeting space, the stream is organized into the following structured data array:

4.3. Absolute Model Training Restrictions

Zero Model Training Directive

Squirrel Tech Services enforces an absolute, legally binding boundary regarding customer data privacy: Your raw audio streams, speaker tags, meeting transcripts, structural summaries, action items, and cross-application generated documents are NEVER used to train, tune, or validate proprietary large language models (LLMs), speech-to-text foundational architectures, or machine learning algorithms owned by us or any third-party subprocessor.

All processing operations are strictly transactional. Your data is processed solely to fulfill your specific workflow requests, generate your explicit summaries, and execute your authorized application automations.

5. AI Processing and Third-Party AI Providers

To achieve high-accuracy speech transcription and cross-application cognitive automation, Squirrel routes data through specialized AI processing pipelines.

5.1. Primary Speech-to-Text Provider

For the conversion of raw audio data into text format, Squirrel uses the high-performance ASR platform AssemblyAI (operated by AssemblyAI, Inc.).

• Data Transmission: Once our browser automation system ingests meeting audio, the encrypted digital audio file is transmitted securely to AssemblyAI via transport layer security.
• Functional Boundary: AssemblyAI processes the audio solely to output an accurate text transcript and speaker label breakdown. Under our binding data processing arrangements, AssemblyAI does not retain your audio or text records to train their foundational voice engines, and your data is deleted following the completion of the transcription task according to strict retention schedules.

5.2. Next-Generation Language Models and Subprocessor Flexibility

To extract complex insights, summarize multi-hour corporate strategy arguments, construct task definitions, and format cross-application workflow blocks, we use enterprise-grade large language models (LLMs).

To ensure the system remains robust against downtime and benefits from ongoing AI performance improvements, our technical framework allows us to add or rotate verified third-party AI subprocessors (such as Anthropic PBC, OpenAI OPCO LLC, or cloud-hosted enterprise AI models running within Amazon Web Services or Google Cloud Platform clusters).

Any third-party AI subprocessor we onboard is bound by strict contractual data processing addendums (DPAs) that enforce these core requirements:

1. Zero storage of customer inputs or text outputs for foundational model training or optimization.
2. Complete encryption of all datasets in transit and at rest using modern encryption standards.
3. Strict isolation of data processing environments, preventing the mixing of Squirrel customer data streams with general consumer usage queries.

6. Automation and Third-Party Integrations

Unlike basic summarization tools, Squirrel is engineered to function as an autonomous AI agent capable of executing complex workflows across your enterprise application stack. This section explains the governance and consent structures that keep you in control of this automation.

6.1. User Permissions and Consent-Driven Actions

Squirrel cannot browse your apps, download database schemas, or execute workflows without explicit setup. All autonomous tasks are governed by OAuth 2.0 authentication protocols and precise scope limitations.

• Granular OAuth Scopes: When you activate an integration (e.g., Salesforce, Jira, or Notion), you are redirected to the native authentication interface of that platform. You view the exact permissions Squirrel requests (e.g., "Write access to Jira issues", "Read/Write access to Google Calendar"). By completing that authentication flow, you grant Squirrel the cryptographic authority to execute actions within those boundaries.
• Autonomous Task Execution: Once you grant these permissions, Squirrel can autonomously execute actions without asking for real-time confirmation for every individual event, provided the action matches parameters you configured. For example, if the system analyzes a meeting transcript, detects a clear assignment (“Sujal will update the Q3 marketing timeline in Notion”), and you have enabled the Notion execution rule, Squirrel will automatically make the API call to modify that Notion page.

6.2. Detailed Supported Integrations Catalog

Our platform contains built-in API connectivity modules to support automated tasks across a wide variety of enterprise software tools. These integrations include:

• Calendar and Scheduling Ecosystems: Google Calendar, Microsoft Outlook Calendar.
• Video Conferencing Infrastructure: Google Meet, Zoom, Microsoft Teams, Cisco Webex.
• Customer Relationship Management (CRM) Systems: Salesforce, HubSpot, Pipedrive, Zoho CRM, Attio, Close, Copper CRM, Freshsales, Microsoft Dynamics CRM.
• Knowledge Bases and Documentation Centers: Notion, Confluence, Google Drive, Google Docs, Dropbox, OneDrive, SharePoint, OneNote.
• Project Management and Team Collaboration Engines: Asana, Jira, Trello, ClickUp, Monday.com, Airtable, Wrike, Linear, Basecamp, MeisterTask, Smartsheet.
• Communications Channels: Slack.
• Task Management and Productivity Utilities: Todoist, Clockify, Everhour.
• Orchestration middleware and Enterprise APIs: Zapier, n8n, FlowMattic, alongside secure outbound Webhooks and Custom API configurations.

6.3. API Data Governance

When interacting with these integrations, Squirrel reads and processes only the information necessary to successfully execute the requested task (such as looking up a project ID in Jira or finding a contact record in HubSpot). We do not scrape your entire corporate database or download your unrelated business documents. Any information fetched during an active API task is handled with the same security protections as our primary internal data stores.

7. Legal Basis for Processing (GDPR / DPDP Act alignment)

For individuals residing within the European Economic Area (EEA), the United Kingdom, or India, our processing of your Digital Personal Data relies on specific, well-defined legal grounds.

7.1. The GDPR Framework Reference Matrix

Under Article 6 of the EU/UK GDPR, we organize our processing activities under these legal frameworks:

• Performance of a Contract: When you sign up for an account, subscribe to our Basic, Pro, or Max plans, or request technical support, processing is necessary to deliver the core software functionalities you contracted to receive.
• Legitimate Interests: We process technical telemetry, system interaction logs, and analytical tracking to maintain platform security, prevent fraud, improve performance, and optimize our infrastructure. We ensure our operational interests do not override your fundamental privacy rights.
• Compliance with Legal Obligations: We process data to comply with financial accounting requirements, cooperate with tax authorities, or respond to valid legal requests from law enforcement or judicial bodies.
• Explicit Consent: In situations like processing live conversational audio during a meeting where you are a participant, our processing relies on the consent granted by the meeting organizer and individual attendees through our notice systems.

7.2. The Indian DPDP Act Framework Alignment

In compliance with the Digital Personal Data Protection Act, 2023 of India, Squirrel acts as a Data Fiduciary regarding your account registration details and a Data Processor when managing enterprise data on behalf of corporate subscribers.

• Notice and Consent: All personal data collection is introduced by clear, granular explanations of what is collected and why. By clicking our authentication buttons, registering an account, or opting into our meeting captures, you give your free, specific, informed, unconditional, and unambiguous consent for the processing of your data for those stated purposes.
• Legitimate Uses: Where permitted under Section 7 of the DPDP Act, certain data processing operations may proceed for “legitimate uses,” such as responding to medical emergencies, maintaining public safety, or fulfilling specific legal mandates.

8. Meeting Recording Consent and Compliance Rules

Because Squirrel joins digital meetings and captures multi-party audio, its presence involves multiple individuals who may not be direct customers of our platform. Maintaining compliance with recording laws is a shared responsibility between Squirrel and the User hosting the meeting.

8.1. Multi-Jurisdictional Legal Realities

Wiretapping and recording regulations vary significantly across national boundaries, states, and legal territories:

• Two-Party / All-Party Consent Jurisdictions: Locations like California, Massachusetts, Germany, and various European states require every single participant in a conversation to explicitly or implicitly consent to a recording before it can legally occur.
• One-Party Consent Jurisdictions: Other regions require only one participant (the meeting host or organizer) to authorize the recording.

8.2. Mandated Platform Guardrails

To protect all parties involved, Squirrel deploys several automated features to ensure transparency and notice:

1. Clear Visual Identification: Our browser automation bot always enters meeting spaces with a distinct, unambiguous display name indicating its role as an AI recording utility (e.g., Squirrel AI Companion).
2. Automated Notification In-Chat: Upon entering a meeting space, the bot can be configured to automatically post a standardized message into the text chat room, stating: “I am the Squirrel AI Companion, invited by [Host Name] to transcribe and automate workflow tasks for this session. By continuing, you consent to this processing. For more details, visit https://meetsquirrel.com.”
3. Proactive Host Assurances: If you use Squirrel to record meetings, you represent and warrant to us that you have provided all required legal notices and obtained all necessary consents from every participant before allowing our bot to enter the session. If any participant objects to being recorded, you must immediately remove the Squirrel bot from the meeting interface or use platform tools to mute the bot’s audio ingestion pipeline.

9. International Transfers and Data Architecture

Squirrel uses a highly resilient, cloud-native storage infrastructure to provide fast, reliable, and secure data access worldwide.

9.1. Centralized United States Cloud Hosting

While Squirrel Tech Services is managed by founders located in India, all primary databases, application state engines, and long-term data repositories are hosted in the United States using NeonDB (a serverless PostgreSQL platform running on top of isolated cloud physical infrastructure).

• Technological Implication: If you reside in India, the European Union, the United Kingdom, Australia, or any other global territory outside the United States, your use of our Services means that your account information, integration configurations, and Meeting Data will be transferred across international borders and stored within the United States.

9.2. Transfer Safeguards Matrix

To protect data during these cross-border transfers, we implement robust legal and operational safeguards:

• Standard Contractual Clauses (SCCs): For users in the EEA and UK, we use the European Commission’s Standard Contractual Clauses embedded within our data agreements to ensure that data transfers to the United States maintain a level of protection equivalent to GDPR standards.
• Indian DPDP Cross-Border Alignment: We track and comply with all central government updates under the DPDP Act regarding permitted cross-border data transfer countries and restricted territories.
• Advanced Technical Safeguards: All data moving between our systems, third-party AI processors, and NeonDB databases is continuously encrypted using TLS 1.3 in transit and AES-256 at rest, shielding your information from unauthorized access during transit.

10. Retention, Deletion, and Account Lifecycle

We hold your data only for as long as necessary to provide our Services and maintain proper business records.

10.1. Account Deletion and the 30-Day Recovery Buffer

If you decide to close your Squirrel account, your profile enters our structured account lifecycle:

• The Grace Period: Your account is placed into a “Soft-Deleted” status for exactly 30 days. During this period, all live automations stop, API integrations are paused, and your access is locked. However, your data remains securely cached in our primary tables. This buffer exists to prevent catastrophic loss if an account is closed accidentally or by an unauthorized user.
• Permanent Removal: Once this 30-day grace period expires, our automated system runs a permanent deletion routine. Your account information, encryption keys, integration configurations, and historical Meeting Data are completely erased from our live NeonDB production servers.

10.2. Data Component Retention Table

To give you clear insight into our data retention practices, here is how different data components are handled during an active subscription:

10.3. Technical Backup Lifecycle

Residual data may remain in our encrypted system backups for up to 60 additional days after permanent removal from our active production systems. These backups are encrypted, isolated from live application access, and are continuously overwritten through our standard rolling backup schedule.

11. Security Architecture and Technical Controls

We deploy rigorous, enterprise-grade technical controls to keep your data safe and secure.

11.1. Encryption Standard Practices

• Data in Transit: Every data transmission—including web requests, API calls to integrated software, and audio streaming to AI engines—is encrypted using Transport Layer Security (TLS 1.3) protocols.
• Data at Rest: All tables, transcripts, indexes, and account details stored in our NeonDB databases are secured using Advanced Encryption Standard (AES-256) cryptographic keys managed under strict access controls.

11.2. Internal Security Access Controls

• Role-Based Access Control (RBAC): We implement strict internal access rules. Our team members cannot view your transcripts, summaries, or integration configurations unless you submit a specific customer support request that requires data inspection, or a severe infrastructure failure demands technical intervention.
• Secure Authentication Frameworks: User access to our application is protected by secure Single Sign-On (SSO) systems and OAuth 2.0 frameworks. This design ensures your primary third-party account passwords are never visible to or stored on our servers.
• Continuous Monitoring and Incident Response: We run automated security scanning tools to monitor for anomalies, unauthorized API attempts, and system vulnerabilities. If a data security incident occurs, our team follows a structured incident response plan to isolate the issue, secure our infrastructure, and notify impacted users and relevant regulatory bodies within mandated timelines (such as the 72-hour GDPR notification window).

12. Data Export and User Control Rights

We believe your data belongs to you. We provide clear tools and respect your legal rights regarding how your information is handled.

12.1. Native Export Capabilities

You can download your data at any time directly through the Squirrel user interface. You do not need to submit a legal request to access your information. You can easily export:

• Full text transcripts of meetings.
• AI-generated summaries and decision outlines.
• Extracted action items and task lists.
• Custom structured text documents generated by our models.

These files can be exported in standard formats like Markdown, clear JSON structures, or plain text (.txt) files, making it simple to transfer your data to other software systems.

12.2. Global Rights Framework (GDPR / DPDP Act)

Depending on where you live, you have comprehensive legal rights regarding your personal data. We respect and fulfill these rights globally:

• Right to Information and Review: You have the right to receive clear details about what personal data we process, where it is stored, and which subprocessors handle it.
• Right to Correction and Rectification: You can update or correct inaccurate or incomplete profile data directly within your account settings interface or by emailing our support team.
• Right to Erasure (The Right to be Forgotten): You can request that we delete all your historical personal data from our systems, subject to necessary legal exceptions like tax auditing rules.
• Right to Restrict or Object to Processing: You can choose to withdraw your consent for specific data uses, such as disabling a third-party integration or turning off automated email scheduling workflows.
• Right to Lodge a Complaint: You have the right to contact a relevant data protection authority if you believe our data processing practices violate local privacy laws.
• For users in India, complaints can be addressed to the Data Protection Board of India.
• For users in the UK or EEA, you can contact your local Data Protection Authority or Supervisory Official.

To exercise any of these privacy rights, please contact our privacy team at privacy@meetsquirrel.com. We review and respond to all verified requests within our standard operational timelines and always within legally mandated periods.

13. Cookies and Analytics Policy

We maintain a minimal cookie policy focused strictly on core system performance.

• No Intrusive Analytics Tracking: Squirrel does not use intrusive tracking tools, third-party analytics suites, or retargeting pixels. We do not run Google Analytics, Mixpanel, PostHog, Meta Pixel, Microsoft Clarity, or Segment tracking codes on our platform.
• Strictly Essential Cookies Only: We use only essential cookies required to run the core application session. These cookies securely store your login state, track your OAuth session parameters during integration setups, and remember your basic user interface choices.
• No Third-Party Ad Networks: Because we do not run third-party advertising networks, your use of Squirrel is never shared with advertisers or tracked across unrelated websites.

14. Subscriptions, Billing, and Refund Rules

Your use of our paid features is governed by clear, predictable financial rules.

• Subscription Options: Squirrel offers distinct service tiers (Basic, Pro, and Max) available on either Monthly or Annual billing cycles.
• Payment Processing: All payments are processed through our secure integration partner, Razorpay. By signing up for a paid tier, you authorize Razorpay to charge your selected payment method for the recurring subscription fees, applicable local taxes, and processing costs.
• Strict No-Refunds Policy: All financial transactions are final. Squirrel Tech Services enforces a strict no-refunds policy for all subscription charges. We do not provide partial refunds, prorated credits, or cash returns if you cancel a subscription before the end of your billing cycle.
• Access Post-Cancellation: If you cancel a subscription, your active tier benefits remain fully available until the current paid billing cycle ends. At that point, your account transitions to our free baseline tier, or access is paused according to your choice.

15. Communications and Marketing Governance

• Transactional Emails: We send essential system updates, billing notifications, security alerts, and integration reports to your registered email address. These emails are necessary to manage your account security and platform operations, so you cannot opt out of them while your account is active.
• Product Update and Marketing Emails: We may occasionally send emails about new features, product updates, technical tips, or promotional opportunities. You can opt out of these updates at any time by clicking the "Unsubscribe" link at the bottom of the email or by adjusting your preferences in your account dashboard. Opting out of marketing updates will not impact your transactional system alerts.

16. Changes to This Privacy Policy

As our platform grows and global data privacy regulations evolve, we may occasionally update this Privacy Policy.

• Notice of Updates: If we make meaningful updates to this Policy, we will notify you by posting a prominent alert on our primary website dashboard, sending an email notice to your registered address, or updating the “Last Updated” date at the very top of this document.
• Reviewing Updates: We encourage you to review this Policy periodically to stay informed about how we protect your information. Your continued use of the Squirrel platform after an update becomes effective indicates your acknowledgment and agreement to the revised Privacy Policy.

17. Contact Information and Jurisdictional Roots

If you have questions, concerns, or requests regarding this Privacy Policy, please contact our team:

• Primary Email Contact: privacy@meetsquirrel.com
• Administrative Operations Address:
  Squirrel Tech Services
  Attn: Sujal Krishna, Sounak Roy & Sarthak Mondal
  KP 5, Prashanti Vihar Road, KIIT University,
  Bhubaneswar, Odisha 751024, India.

Governing Law and Dispute Resolution

This Privacy Policy, our internal data management practices, and all related interactions are governed by the laws of India, without regard to conflict of law principles.

Any legal disputes, regulatory actions, or lawsuits arising from or relating to this Policy must be filed and resolved exclusively in the courts located in Bhubaneswar, Odisha, India. By using our Services, you consent to the personal jurisdiction and venue of these courts.