Privacy Policy

Milago Technologies Private Limited ("Milago", "Milago AI", "we", "us", or "our") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, share, store, and safeguard personal data when you use our website, web application, dashboard, browser extension, meeting bot, integrations, and related services (collectively, the "Service").

Milago AI is an AI-powered meeting intelligence platform designed for business and professional users. The Service helps users capture meetings, generate transcripts, and produce AI-assisted summaries, action items, decisions, insights, knowledge items, and other structured outputs. Because the Service involves meeting recordings, transcription, artificial intelligence, workspace collaboration, and third-party technology providers, this Privacy Policy is drafted to explain our practices in a practical and transparent way.

We aim to handle personal data in line with India's Digital Personal Data Protection Act, 2023 and applicable rules, together with broadly recognised global privacy principles such as transparency, purpose limitation, data minimisation, security, user control, and accountability.

Our registered office is located at 9th Floor, Brigade IRV, Nallurhalli Road, Whitefield, Bangalore 560066, Karnataka, India.

1. Information We Collect

We collect only the information that is reasonably necessary to provide, secure, operate, support, and improve the Service. The type of information we collect depends on how you interact with Milago AI and which features you choose to use.

We collect different categories of data depending on how the Services are used. The categories below describe the main types of information processed by Milago AI.

1.1 Account and Identity Data

When a user creates or manages a Milago AI account, we may collect information such as name, email address, profile image, account role, workspace membership, plan tier, billing status, account status, and related identifiers. If a user signs in through an OAuth or single sign-on provider, we may receive basic account information from that provider, such as name, email address, profile image, and authentication identifiers.

Passwords, where used, are stored only in hashed form. We do not store passwords in plain text.

1.2 Authentication and Session Data

We process authentication and access-related data to keep accounts secure and to provide the Services. This may include OAuth account linkages, access sessions, browser session identifiers, login metadata, and technical records required to authenticate users and maintain secure access.

Where users connect third-party accounts, such as calendar or identity providers, we may store tokens or credentials necessary to enable that integration. These are used to provide the connected functionality requested by the user, such as calendar-based meeting scheduling or third-party sign-in.

1.3 Meeting and Recording Data

Milago AI may process meeting-related data when users capture meetings through the meeting bot or browser extension. This may include meeting title, date, time, meeting URL, platform information, attendee details, participant names, recording source, processing status, audio recordings, video recordings where enabled, screen-share content where captured, and related meeting metadata.

Audio is generally captured when a meeting is recorded through Milago AI. Video capture is configurable and may include meeting video or screen-share content if the user enables that setting or uses a recording mode that supports it.

1.4 Transcript and Speaker Data

After audio is captured, it may be transcribed using third-party speech-to-text technology. Transcript data may include spoken words, speaker labels, timestamps, diarisation data, per-utterance segments, and related processing metadata.

Speaker labels may be based on the information available in the meeting or generated by the transcription provider. While the Services are designed to provide useful transcription and speaker attribution, diarisation and transcription may not always be complete or fully accurate.

1.5 AI-Generated Outputs

Milago AI uses artificial intelligence to generate structured outputs from meeting transcripts and related metadata. These outputs may include meeting summaries, action items, owners, decisions, key insights, knowledge items, feedback items, meeting category classifications, and responses generated through chat-with-transcript functionality.

AI outputs are generated from the meeting content made available through the Services. They should be reviewed by users for accuracy, completeness, and context before being relied upon.

1.6 Calendar and Integration Data

If users connect their calendars or other integrations, we may process calendar event titles, meeting times, attendee lists, meeting links, scheduling preferences, bot preferences, and related metadata necessary to schedule, join, or process meetings through the Services.

The scope of information available to us depends on the permissions granted by the user through the relevant third-party integration.

1.7 Workspace and Collaboration Data

For individual and organisation workspaces, we process workspace-related information such as organisation name, workspace members, user roles, shared meetings, boards, tasks, knowledge items, feedback items, shared links, access permissions, and collaboration activity.

Where a user generates a shared link to a meeting, transcript, board, or other content, that link may allow read-only access to the relevant content depending on the sharing settings selected by the user.

1.8 Billing and Subscription Data

We process subscription and billing-related information such as plan identifiers, billing cycle, invoice records, subscription status, payment gateway references, and transaction-related webhook information. Payments are processed through third-party payment gateways. Cardholder data is handled by the payment gateway and does not pass through or remain stored on Milago's own systems.

1.9 Usage, Analytics, and Technical Data

When users visit our website or use the Services, we may collect technical and usage information such as page views, in-app events, anonymous session identifiers, user ID where applicable, IP address, URL, referrer, user-agent, browser type, device information, operating system, event timestamps, and related analytics data.

We use this information to understand product usage, improve performance, support reliability, identify errors, prevent abuse, and maintain security.

1.10 Support, Communications, and Administrative Records

If users contact us for support, billing, sales, or legal inquiries, we may process the information included in those communications. We may also maintain records of transactional emails, account notifications, support activity, administrative actions, data export requests, deletion requests, and other operational records.

Internal administrative actions taken on user accounts may be recorded in audit logs for accountability, security, and compliance purposes.

1.11 Sensitive or Confidential Information:

Milago AI is not designed to intentionally collect highly sensitive personal data such as government identifiers, health data, biometric data, children's data, or financial account credentials. However, because users may record business meetings, meeting content may sometimes include confidential, personal, privileged, employment-related, financial, or otherwise sensitive information. Users are responsible for deciding whether a meeting is appropriate to record and process through the Service.

Sources of Data: In summary, the personal data we process may come directly from you, from your use of the Service, from meetings you choose to capture, from your organisation or workspace administrator, from connected third-party integrations, or from technical systems that automatically generate logs and analytics data.

2. How We Collect Your Information

We collect personal data in several ways.

Some data is provided directly by users, such as when they create an account, update their profile, connect integrations, configure a workspace, contact support, subscribe to a plan, or upload information into the Services.

Some data is collected through the product's meeting capture features. A user may choose to capture a meeting through a server-side meeting bot that joins the meeting as a visible participant, or through a browser extension that records from the user's browser session after the user initiates recording. The selected capture method determines how meeting media is collected and processed.

Some data is received from third-party services integrated with Milago AI, including calendar services, OAuth identity providers, meeting platforms, payment gateways, email providers, transcription providers, AI model providers, and infrastructure providers.

We also collect certain technical, analytics, and security data automatically when users access or interact with our website, application, extension, or backend services.

3. How We Use Your Information

We use personal data only for legitimate, necessary, and product-related purposes. These purposes include operating the Service, enabling meeting intelligence features, supporting customers, maintaining security, and complying with applicable obligations.

• Providing and Maintaining the Service: We use your information to create and manage accounts, authenticate users, maintain sessions, provide access to dashboards, enable workspace collaboration, apply role-based permissions, and operate the features available under your plan.
• Meeting Capture, Transcription, and Processing: We use meeting data to capture meetings through the meeting bot or browser extension, store recordings, generate transcripts, attribute speaker segments, process meeting metadata, and make meeting records available through the dashboard.
• AI-Powered Meeting Intelligence: We use transcripts, meeting metadata, and user prompts to generate AI-assisted summaries, action items, decisions, insights, knowledge items, feedback items, classifications, and chat-with-transcript responses. These features are intended to help users organise and understand meeting content more efficiently.
• Calendar and Integration Functionality: If you connect a calendar or identity provider, we use the authorised data to support features such as third-party sign-in, calendar-based scheduling, meeting detection, bot scheduling, and meeting organisation. We access only the data necessary to provide the connected functionality you choose to enable.
• Workspace Sharing and Collaboration: We use workspace and collaboration data to allow users to share meetings, boards, transcripts, tasks, and knowledge items with authorised workspace members or recipients of shared links, based on the relevant access settings.
• Customer Support and Service Communications: We use contact and account information to respond to support requests, send verification emails, password reset emails, billing notices, service alerts, product updates relevant to your account, security notices, and other transactional communications.
• Payment Processing and Account Management: We use billing and transaction data to verify payment status, activate subscriptions, manage plan limits, send invoices or receipts, handle refunds or billing issues, maintain records, and comply with tax, accounting, and financial obligations.
• Analytics and Product Improvement: We may use usage and technical data to understand how the Service is used, troubleshoot issues, identify product friction, monitor performance, improve features, and develop new functionality. Where possible, we use aggregated or de-identified information for product analytics and improvement.
• Security, Abuse Prevention, and Legal Compliance: We use account, technical, administrative, and usage data to protect the Service, detect suspicious activity, investigate misuse, prevent unauthorised access, enforce our Terms, comply with legal obligations, respond to lawful requests, and protect the rights, safety, and security of Milago, our users, and third parties.

No Advertising Sale: We do not sell your personal data. We do not use meeting recordings, transcripts, or Customer Content for third-party advertising, behavioural advertising, or unrelated marketing by third parties.

Legal Grounds: Where applicable law requires a legal basis, we may process personal data on grounds such as performance of a contract, consent, legitimate interests, compliance with legal obligations, or other recognised grounds under applicable privacy laws. For meeting recordings and similar activities where consent or notice is required, the user or customer initiating the recording is responsible for obtaining the required participant permissions.

4. Meeting Recording, Participant Notice, and User Responsibility

Milago AI allows users to record, transcribe, and analyse meetings. This is a powerful feature, but it also requires care. Recording a meeting may trigger privacy, confidentiality, employment, communications, sector-specific, platform-specific, or consent-related obligations depending on where participants are located and what is discussed.

Milago AI supports meeting capture in two main ways. First, a server-side meeting bot may join a supported meeting as a visible participant. The default bot name may appear as "Milago Notetaker" or a similar configured name. Second, a user may use the browser extension to record a meeting from the user's browser session after initiating the recording.

The meeting bot is designed to be visible in the meeting participant list. It is not intended to operate as a hidden or covert recording tool. However, the mere presence of a bot in a participant list may not be sufficient in every situation or jurisdiction. Users should clearly inform meeting participants before or at the start of a meeting that the meeting may be recorded, transcribed, and analysed using Milago AI.

By using Milago AI to record, transcribe, or analyse a meeting, you confirm that you have the authority to do so and that you have provided all required notices and obtained all legally required consents, permissions, or approvals from meeting participants. This includes compliance with applicable laws, workplace policies, confidentiality obligations, customer requirements, and rules of the relevant meeting platform.

Milago does not independently verify whether every meeting participant has been informed or has consented to recording. You should not use the Service to record meetings secretly, unlawfully, or in a manner that violates a participant's reasonable expectation of privacy.

If you are an organisation using Milago AI for your team, you should adopt internal policies and participant notice practices that explain when and how meetings may be recorded, who can access the recordings and transcripts, how long they may be retained, and how participants can raise concerns.

5. Cookies and Tracking Technologies

We use cookies and similar technologies to operate, secure, and improve the Service.

At a minimum, the Service may use essential cookies or similar technologies to maintain login sessions, authenticate users, secure accounts, remember basic settings, and support core application functionality. These cookies are necessary for the Service to work properly.

Where analytics is enabled, we may use analytics cookies, session storage, or similar technologies to collect standard usage information such as page views, sessions, device information, browser information, referrers, URLs, and in-app events. We use this information to understand product usage, troubleshoot issues, and improve performance.

We do not currently use marketing cookies, third-party advertising cookies, social media pixels, or session-replay tools in the web application. If this changes in the future, we will update this Privacy Policy and, where required by law, provide an appropriate consent or preference mechanism.

You may control cookies through your browser settings. However, disabling essential cookies may affect important functionality, including login, session continuity, and account security.

Additional cookie information may be made available on request or through future product updates.

6. How We Share Your Information

We share personal data only where necessary to provide the Service, operate our business, comply with legal obligations, or protect legitimate interests. We do not share meeting content with advertisers or unrelated third parties.

• Meeting Bot and Meeting Infrastructure Providers: When you use the meeting bot, certain information such as meeting URLs, bot display settings, meeting metadata, and captured audio or video may be processed by the infrastructure provider that helps the bot join and capture meetings.
• Speech-to-Text Providers: We share meeting audio streams or audio files with transcription providers so that they can generate transcripts and speaker diarisation. These providers return transcript text, speaker labels, timestamps, and related transcription data to us.
• AI Model Providers: We may share meeting transcripts, meeting metadata, participant names where available, and system prompts with AI providers to generate summaries, action items, decisions, insights, classifications, and chat responses. Raw audio and video are not intended to be sent to large language model providers for generation of AI meeting outputs.
• Cloud, Database, and Storage Providers: We use cloud infrastructure, object storage, databases, and backend services to host the Service, store recordings, maintain transcripts, process workspace data, and operate the platform securely and reliably.
• Payment Gateways: Payment information is processed through third-party payment gateways. These providers may receive billing identifiers, transaction amounts, payment status, invoice information, and related payment data. Full card details are handled by the payment gateway and not stored on Milago's own systems.
• Identity, Calendar, and Integration Providers: If you connect third-party accounts, such as identity providers or calendars, data may flow between Milago and those providers to support sign-in, calendar access, meeting scheduling, and related integration functionality.
• Email, Support, Analytics, and Telemetry Tools: We may use service providers for transactional emails, customer support, application telemetry, error monitoring, and analytics. These providers receive only the information needed to perform their services for us.
• Workspace Members and Shared Link Recipients: Content may be shared with members of your workspace or with people who receive a shared link, depending on the access settings selected by you, your organisation, or your workspace administrator. Users should treat shared links carefully and share them only with authorised recipients.
• Legal Requirements and Protection: We may disclose personal data if required by law, regulation, court order, government request, legal process, or where necessary to enforce our Terms, protect rights, investigate misuse, prevent fraud, or address security incidents.
• Business Transfers: If Milago is involved in a merger, acquisition, investment, financing, restructuring, sale of assets, or similar transaction, personal data may be transferred or disclosed as part of that transaction. In such cases, we will seek to ensure that the recipient continues to protect personal data in a manner consistent with this Privacy Policy.
• With Your Consent: If we need to share personal data for a purpose not described in this Privacy Policy, we will seek consent where required by applicable law.

A list of key third-party service providers used for hosting, transcription, AI processing, payments, communications, analytics, and related services is available to enterprise customers on request.

7. Data Retention

We retain personal data only for as long as reasonably necessary for the purposes described in this Privacy Policy, unless a longer period is required or permitted by law.

• Account Information: We retain account information while your account remains active or as needed to provide the Service. If you delete your account or request deletion, we will delete or anonymise account data from active systems within 90 days of the deletion request, subject to the limited retention categories described below.
• Meeting Recordings, Transcripts, and AI Outputs: Meeting recordings, transcripts, summaries, action items, decisions, insights, tasks, boards, and related Customer Content are generally retained for as long as the relevant meeting, workspace, or account remains active, unless you delete the content earlier through available product controls. Upon account deletion or subscription termination, Customer Content will be deleted from our active systems within 90 days of the effective date of termination ("Deletion Window"). During the Deletion Window, the content will not be accessible through the platform. We will endeavour to complete active-system deletion before the end of the Deletion Window.
• Backup and Archival Systems: Data remaining in backups at the time of deletion from active systems is retained only for backup and disaster recovery purposes and is ordinarily overwritten within 30 days in the normal course of rotation. Audio and video recordings are maintained as live files and are not stored in a separate backup system; accordingly, deletion of such media from active systems is generally final, subject to any legal or compliance retention requirements.
• Calendar and Integration Data: Calendar and integration data is retained for as long as the relevant integration remains connected or as otherwise needed to provide the requested functionality. If you disconnect an integration, revoke access, or delete your account, we will stop collecting new data from that integration and will delete or anonymise related data within 90 days, subject to the limited retention categories below.
• Payment and Transaction Records: Billing, subscription, invoice, and transaction records are retained for the period required by applicable tax, accounting, and financial laws. Under current Indian law, this is ordinarily seven years from the date of the transaction.
• Security Logs and Audit Records: Infrastructure logs and telemetry are retained for operational and security purposes and are ordinarily maintained for up to 90 days, subject to provider practices. Administrative audit logs are retained for the duration of the account and are deleted or anonymised upon account deletion, except where retention is required for security, legal, or compliance purposes.
• Support and Administrative Records: Support communications, privacy requests, audit logs, and administrative records are retained for as long as necessary to respond to requests, maintain business records, demonstrate compliance, resolve disputes, or protect the Service.
• Legal Hold and Dispute-Related Retention: Where data is subject to a legal hold, court order, regulatory preservation requirement, dispute, complaint, or enforcement proceeding, we will retain the relevant data until final resolution of that matter, notwithstanding any shorter period that would otherwise apply.
• Anonymised Data: Anonymised or aggregated data that cannot reasonably identify you or your organisation may be retained indefinitely for product analytics, improvement, benchmarking, and research purposes.
• Retention Controls: Milago may introduce additional retention controls, automated deletion settings, or enterprise-level retention configurations in the future. If we do so, this Privacy Policy or related product documentation will be updated accordingly.

Where we no longer have a legitimate need to retain personal data, we will delete, anonymise, or restrict it in accordance with applicable law and our internal practices.

8. Your Rights and Choices

Depending on where you are located and how your personal data is processed, you may have certain rights under applicable privacy laws. For users in India, these rights are framed with reference to India's Digital Personal Data Protection Act, 2023 and applicable rules. We also aim to follow broadly recognised global privacy norms for access, correction, deletion, transparency, and grievance handling.

• Right to Access Information: You may request information about the personal data we hold about you and how we process it. Where available, you may also use product features to view account details, meeting records, transcripts, and related content available in your account or workspace.
• Right to Correction: You may request correction or updating of inaccurate or incomplete personal data. Certain profile information may be corrected directly through account settings.
• Right to Deletion or Erasure: You may request deletion of personal data, subject to legal, contractual, technical, security, billing, audit, and compliance limitations. You may delete individual meetings and, where available, delete your account through self-service controls.
• Right to Data Export or Portability: Where available through the product, you may request an export of your account data and related content. Exports may include profile information, meetings, transcripts, tasks, knowledge items, feedback items, bot preferences, calendar connection information, scheduled bot information, and other data associated with your account.
• Right to Withdraw Consent or Disconnect Integrations: Where processing is based on consent, you may withdraw consent where permitted by law. In practical terms, you may disconnect calendar or identity integrations, revoke third-party permissions, stop using the browser extension, or stop initiating meeting recordings. Withdrawing consent may affect your ability to use certain features.
• Right to Grievance Redressal: If you have concerns about how we handle your personal data, you may contact us or our Grievance Officer using the details in the Contact section. We will review and respond to grievances in accordance with applicable law.
• Right to Nominate: Where applicable under Indian law, you may have the right to nominate another individual to exercise your rights in the event of death or incapacity.
• Right to Object or Restrict Processing: In some jurisdictions, you may have the right to object to or request restriction of certain processing activities. We will evaluate such requests in accordance with applicable law.

If Milago processes Customer Content on behalf of an organisation, workspace, or customer, we may refer certain requests to the relevant organisation or workspace owner. For example, if you were a participant in a meeting recorded by a Milago customer, the customer may be the appropriate party to decide whether a recording or transcript should be accessed, corrected, shared, or deleted.

To exercise your rights, contact us using the details provided below. We may need to verify your identity and authority before responding. We will not discriminate against you for exercising your privacy rights, although some requests may limit your ability to use features that depend on the data requested to be deleted or restricted.

9. Children's Privacy

The Service is intended for business and professional users and is not directed to children or minors. We do not knowingly invite children to create accounts or use the Service.

Users should not use Milago AI to knowingly collect or process personal data of children unless they have all legal authority, notices, consents, and safeguards required under applicable law. If we become aware that a child has created an account or that children's personal data has been processed in a way that is not permitted, we may take steps to delete the relevant information, restrict processing, or contact the responsible customer or user.

If you believe that personal data of a child has been provided to Milago AI improperly, please contact us immediately.

10. Data Security Measures

We take the security of personal data seriously and use technical and organisational measures designed to protect information against unauthorised access, loss, misuse, alteration, disclosure, or destruction.

• Encryption in Transit: Data exchanged between users and the Service is transmitted over HTTPS/TLS. Communications with third-party providers are made through secure endpoints where supported.
• Password Protection: Passwords are stored in hashed form. We do not store user passwords in plain text.
• Infrastructure Security: We use managed cloud infrastructure, object storage, databases, and backend services that provide standard security and encryption controls. Data at rest relies on the encryption and security measures provided by our infrastructure and storage providers.
• Access Controls: Access to user and workspace data is controlled through application-level access controls, authenticated sessions, and role-based permissions. Organisation workspaces may include roles such as owner, admin, member, billing, support, or read-only access depending on product configuration.
• Administrative Logging: Certain internal administrative actions may be recorded in audit logs to support accountability, troubleshooting, security, and compliance.
• Monitoring and Incident Response: We use monitoring, telemetry, and operational tools to detect errors, investigate suspicious activity, maintain reliability, and respond to potential incidents.
• Data Minimisation: We aim to collect and process only the information needed to provide and improve the Service, support integrations, maintain security, and meet legal or business requirements.

No system is completely secure. Milago does not currently provide end-to-end encryption for meeting content, and application-layer field-level encryption may not apply to all stored data. Formal certifications such as SOC 2 Type II or ISO 27001 should not be assumed unless expressly confirmed by Milago in writing.

You also play an important role in protecting your data. You should use strong credentials, protect your account, manage workspace permissions carefully, limit shared links to authorised recipients, and promptly notify us if you suspect unauthorised access or misuse.

11. International Data Transfers

Milago is based in India and initially focuses on users and customers in India, while also supporting business use across other jurisdictions. Because the Service relies on global cloud infrastructure and specialised third-party providers, personal data may be stored, accessed, transferred, or processed in India, the United States, or other countries where Milago or its service providers operate.

International transfers may occur when we use cloud hosting, object storage, databases, transcription services, AI model providers, email services, analytics tools, payment gateways, support tools, or other service providers located outside India. Transfers may also occur when users, workspace members, meeting participants, or administrators access the Service from different countries.

At present, Milago does not make a general commitment that all personal data will remain within a specific country or region. Where required by applicable law, we take steps intended to protect transferred data through contractual, technical, organisational, or legal safeguards appropriate to the nature of the transfer.

Customers with strict data residency, localisation, regulated-sector, or cross-border transfer requirements should contact Milago before using the Service for highly sensitive or regulated workloads.

12. AI Processing, Outputs, and Limitations

Artificial intelligence is a core part of Milago AI. We use AI technologies to help users understand and organise meeting content more efficiently. This includes generating summaries, action items, decisions, insights, classifications, knowledge items, and responses to user questions about a transcript.

• Data Used for AI Processing: AI processing generally uses meeting transcripts, meeting metadata, participant names where available, meeting titles, user prompts, and system prompts. Audio and video recordings are not intended to be sent directly to large language model providers for generating meeting summaries and insights. The AI processing layer operates primarily on text and related metadata.
• Use of Third-Party AI Providers: We may use one or more third-party large language model providers, including fallback providers for reliability and redundancy. These providers process the data sent to them for the purpose of generating the requested outputs.
• Model Training: We do not separately enable voluntary training of general or public AI models using Customer Content. Our use of AI providers is intended to be under commercial or API terms that restrict use of customer inputs for general model training, subject to the specific terms of the relevant provider.
• AI Outputs Are Not Guaranteed: AI systems can produce incomplete, incorrect, misleading, or contextually inappropriate results. This may happen because of poor audio quality, incomplete transcription, incorrect speaker attribution, ambiguous discussion, missing context, or model limitations. Milago does not guarantee that AI-generated summaries, action items, decisions, or insights will be accurate, complete, or suitable for every purpose.
• User Review Required: AI outputs are designed to assist users, not replace human judgment. Users should review AI-generated content before relying on it, sharing it, assigning tasks, making business decisions, treating it as an official record, or using it in legal, employment, financial, compliance, or other sensitive contexts.
• Responsibility for Use: You remain responsible for how you use, edit, share, publish, rely on, or act upon AI-generated outputs. If a meeting involves confidential, regulated, privileged, or sensitive information, you should assess whether it is appropriate to process that meeting through AI features.

In short, Milago AI is intended to make meeting follow-up faster and more structured, but it should be used with professional judgment. The output should be treated as an assistive layer, not as a final authority.

13. Confidential Information and Meeting Content

Meetings can contain sensitive business discussions, trade secrets, personal data, employment matters, client information, legal discussions, financial information, or other confidential content. Milago does not decide what should or should not be recorded. That responsibility sits with the user or organisation initiating the recording.

Before using Milago AI for a meeting, users should consider whether the meeting is appropriate for recording, transcription, AI analysis, and workspace sharing. Users should also consider whether they need additional approvals, confidentiality notices, internal policies, client consent, or contractual permissions before capturing the meeting.

Milago does not review meeting content for legal compliance before processing it. If you upload, record, process, share, or analyse meeting content through the Service, you are responsible for ensuring that your use of the Service is lawful and appropriate for the context.

14. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our Service, technology, data practices, legal requirements, or business operations. When we update the Policy, we will revise the "Last Updated" date at the top of this document.

If we make material changes that significantly affect your rights or how we process personal data, we may provide additional notice through the Service, website, email, or another appropriate channel.

We encourage you to review this Privacy Policy periodically. Your continued use of the Service after an updated Policy becomes effective means that the updated Policy applies to your use of the Service from that point forward.

15. Contact Us

If you have questions, concerns, requests, or complaints about this Privacy Policy or our data practices, you may contact us at:

Milago Technologies Private Limited
9th Floor, Brigade IRV, Nallurhalli Road, Whitefield, Bangalore 560066, Karnataka, India

General Privacy & Support Contact: support@milago.ai

Grievance Officer (India):
Name: Pradyumna Acharya
Email: pradyumna@milago.ai
Address: 9th Floor, Brigade IRV, Nallurhalli Road, Whitefield, Bangalore 560066, Karnataka, India

Please include sufficient information for us to understand and respond to your request. If you are contacting us on behalf of an organisation, please include the organisation name, your role, and your authority to make the request.