https://vagle.ai/assets/LegalPage-CO5HFEn3.js

1import{j as e,C as p}from"./index-BxsKcnXk.js";import{L as t}from"./vendor-BPYN3F7l.js";import{b as h,S as g}from"./SEO-CTrNOA79.js";import{A as m}from"./LegalPage-5ZRfxVnG.js";import{S as i}from"./shield-check-DxPIBzVl.js";import{F as l}from"./file-text-CK85KyRB.js";import{L as y}from"./lock-keyhole-DTLt4UHe.js";import"./icons-tq9NNN10.js";const a="[email protected]",b="July 1, 2026",f=[{id:"what-we-collect",title:"1. What we collect",body:["Vagle AI collects the information needed to provide and operate the service. This can include account details, workspace details, company details, login activity, billing and usage records, assistant settings, phone number settings, provider configuration, support messages, and basic service logs.","When you use voice calling, campaigns, follow-up funnels, or call logs, we may process phone numbers, caller or lead names, email addresses where provided, lead fields, call time, call duration, call direction, call status, transcripts, summaries, recordings where enabled, detected intent, detected outcome, interest score, tool actions, and estimated usage cost.","When you use MCP, API access, ChatGPT, Codex, or another MCP-compatible client with Vagle AI, we may process token metadata, token scopes, workspace permissions, approval requests, audit logs, tool names, requested actions, idempotency keys, and safe input or output summaries. Raw MCP tokens are shown only when created and are stored hashed after that."]},{id:"connected-tools",title:"2. Connected tools and credentials",body:["If you connect Google Sheets, Airtable, Notion, Gmail, Google Calendar, webhooks, REST APIs, or another business tool, Vagle AI uses that connection only to perform the actions you configure. For example, the platform may update a lead row, create a note, send a configured email, create or update a calendar event, or call your webhook.","For Google tools, Vagle AI uses the connected Google account only for user-configured actions such as writing selected call fields to Sheets, creating or updating Calendar events, or sending configured Gmail messages. We do not use Google data for advertising, sell Google user data, or independently browse a user account outside the configured workflow.","Vagle AI’s use and transfer of information received from Google APIs follows the Google API Services User Data Policy, including the Limited Use requirements.","OAuth tokens, API keys, MCP tokens, provider keys, and connected tool credentials are treated as sensitive. We protect them with access controls and encryption where applicable, limit access based on workspace permissions, and avoid exposing secrets in normal UI, logs, and tool responses."]},{id:"how-we-use-data",title:"3. How we use data",body:["We use data to provide the service, place and receive calls, run AI voice agents, create transcripts and summaries, run follow-up funnels, update configured tools, calculate usage, troubleshoot errors, improve reliability, prevent abuse, protect accounts, and support customers.","We do not sell customer call data, lead data, transcripts, recordings, connected tool data, Google user data, or MCP/API token data."]},{id:"ai-and-telephony-providers",title:"4. AI, voice, and telephony providers",body:["Vagle AI may use third-party providers for telephony, speech-to-text, language models, text-to-speech, voice streaming, hosting, storage, payment, email delivery, and monitoring. The providers used for a call depend on the workspace configuration, provider keys, phone number setup, and selected assistant settings.","We send providers only the information needed for the configured workflow, such as call audio, text needed to generate a response, selected tool instructions, or usage information. Provider availability, pricing, latency, and behavior may change based on the provider and account configuration."]},{id:"recordings-transcripts",title:"5. Recordings and transcripts",body:["Call recording and transcription can contain personal or business information. Customers are responsible for giving required notices, obtaining required consent, and using recordings, transcripts, and automated calling in a lawful way.","Call logs, transcripts, summaries, recordings where enabled, detected outcomes, and tool actions are shown to workspace users based on their access level."]},{id:"data-sharing",title:"6. When data is shared",body:["We share data with service providers only when needed to operate the product, process configured workflows, deliver support, handle payments, protect the platform, or meet legal obligations.","Data is also shared with connected tools when a customer configures Vagle AI to send it there. For example, a call summary can be saved to a Sheet, an appointment can be sent to a calendar, or a webhook can receive lead fields selected by the customer."]},{id:"retention",title:"7. Retention",body:["We keep information for as long as needed to provide the service, maintain security, handle billing, resolve issues, support customers, and meet legal obligations. Some records may remain in backups, audit logs, security logs, or billing logs for a limited period.","Customers can ask us to delete or export data where applicable. Some deleti

1on requests may need to be handled by the business that collected the lead or caller data, because that business controls why the call happened."]},{id:"user-rights",title:"8. Access, correction, and deletion",body:["You can contact us to request access, correction, export, or deletion of personal information where applicable law gives you those rights. We may need to verify the request and may ask for information needed to locate the relevant account or workspace.","Callers who received a call from a Vagle AI customer should usually contact that business first. The business decides why the call was made, what lead data was used, and how long its business records should be kept."]},{id:"children",title:"9. Children and sensitive data",body:["Vagle AI is designed for business users. It is not intended for children under 13. Customers should not use Vagle AI to collect sensitive personal information unless they have a lawful basis, proper consent where required, and a clear business need for that data.","Customers should avoid collecting payment card numbers, passwords, government identifiers, health information, or other sensitive data through voice agents unless they have reviewed the legal and security requirements for that workflow."]},{id:"regional-rights",title:"10. Your regional privacy rights (GDPR, UK GDPR, CCPA/CPRA)",body:["Depending on where you live, you may have rights to access, correct, delete, port, or restrict the processing of your personal information, and to object to certain processing. To exercise any of these, contact us and we will respond within the timeframe required by applicable law.","For EU/UK users (GDPR): we process personal data on the legal bases of performing our contract with you, your consent where required, our legitimate interests in operating and securing the service, and compliance with legal obligations. Where Vagle AI processes data on behalf of a business customer, that customer is the data controller and Vagle AI acts as a data processor.","For California users (CCPA/CPRA): we do not sell or share personal information as those terms are defined under the CCPA/CPRA. You have the right to know, delete, correct, and to be free from discrimination for exercising your rights.","International transfers: where data is transferred across borders, we use appropriate safeguards (such as standard contractual clauses) where required by law."]},{id:"contact",title:"11. Contact",body:[`For privacy, data, or account questions, or to exercise your privacy rights, contact ${a}.`]}],w=[{id:"service-use",title:"1. Service use",body:["Vagle AI provides software for AI voice agents, inbound and outbound calling, follow-up funnels, call logs, transcripts, summaries, tool updates, campaigns, usage tracking, MCP access, and workflow automation.","You are responsible for how your team configures agents, what numbers you call, what leads you upload, what tools you connect, what instructions you give agents, and what actions you allow the platform to take."]},{id:"accounts",title:"2. Account responsibility",body:["You must keep login details, API keys, MCP tokens, provider keys, OAuth access, and connected tool credentials secure. Workspace owners and admins are responsible for choosing who can access assistants, call logs, recordings, transcripts, tools, billing, and settings.","You must tell us promptly if you believe an account, token, provider key, or connected tool has been accessed without permission."]},{id:"calling-consent",title:"3. Calling consent and compliance",body:["Customers are responsible for ensuring they have required consent and lawful basis to call their leads or customers.","You are also responsible for AI disclosure where required, call recording notices, opt-out handling, do-not-call rules, telemarketing rules, caller identity rules, local telecom rules, and industry rules that apply to your use case.","You must not use Vagle AI to bypass consent, hide the purpose of a call, impersonate another person or organization, or continue calling someone who has opted out where opt-out applies."]}

1,{id:"prohibited-use",title:"4. Prohibited use",body:["Do not use Vagle AI for spam, scams, harassment, deceptive calls, impersonation, unlawful surveillance, illegal data collection, malware, phishing, emergency services, or any use where a delayed, incomplete, or incorrect response could cause serious harm.","Do not try to bypass rate limits, attack the service, access another customer workspace, scrape protected systems, connect tools you are not allowed to use, or send secrets through fields that are visible to end users or AI models."]},{id:"billing",title:"5. Payment and usage billing",body:["Calling is usage based unless a separate written agreement says otherwise. Charges may depend on connected voice minutes, telephony, AI model usage, transcription, speech generation, recordings, provider configuration, platform settings, and workspace usage.","New accounts start with 0 calling credits unless credits are explicitly granted by Vagle AI in writing. Vagle AI does not provide free credits, bundled minutes, or a free trial by default. Calling and other usage consume your wallet balance or credits, and you are responsible for keeping a sufficient balance for the usage you enable.","Follow-up Funnels, Multi Agents, and Smart Assets are available through the All Access plan at the price shown in Billing. Unless we state otherwise in writing, paid fees are not refundable except where required by law.","You are responsible for reviewing usage, maintaining payment access, and setting limits or pauses where available."]},{id:"third-party-providers",title:"6. Third-party providers and connected tools",body:["The platform may depend on telephony, AI, transcription, speech, hosting, storage, payment, email, and connected tool providers. Their availability, pricing, limits, policies, and behavior may affect the service.","Supported providers depend on your selected plan, keys, geography, and configuration. You are responsible for complying with the terms of any third-party tools or provider accounts you connect."]},{id:"mcp-api",title:"7. MCP, API, and automated actions",body:["If you use MCP or API access, you are responsible for the tokens you create, the scopes you grant, the actions you approve, and the systems that call those endpoints.","External clients such as ChatGPT, Codex, or other MCP-compatible tools can act only within the scopes and safety mode of the token you create. Write actions such as creating drafts, publishing workflows, sending data to tools, or changing configuration should be reviewed carefully. Vagle AI may require approval steps, audit logs, idempotency keys, or scope checks for these actions."]},{id:"customer-data",title:"8. Customer data",body:["You keep ownership of your business data, lead data, prompts, files, call records, and connected tool content. You allow Vagle AI to process that data so we can provide the service.","You are responsible for making sure the data you upload, collect, or send through the platform is lawful, accurate, and appropriate for the configured workflow."]},{id:"testing-ai",title:"9. AI behavior and testing",body:["AI voice agents can misunderstand callers, produce incomplete answers, or take the wrong action if they are configured incorrectly. You should test agents before using them with real customers and review important workflows such as bookings, payments, escalations, tool updates, and compliance-sensitive calls.","Vagle AI does not provide legal, medical, financial, or emergency advice through the platform."]},{id:"liability",title:"10. Limitation of liability",body:["To the extent allowed by law, Vagle AI is not liable for indirect losses, lost profits, lost revenue, lost data, business interruption, third-party provider outages, customer configuration errors, unlawful calling, connected tool actions, or claims caused by use outside these terms."]},{id:"suspension",title:"11. Suspension and termination",body:["We may suspend or limit access if we believe an account is being used unlawfully, creates security risk, harms the platform, violates these terms, creates billing risk, or creates risk for callers, customers, providers, or connected tools."]},{id:"governing-law",title:"12. Governing law and disputes",body:["These terms are governed by the laws of India, without regard to conflict-of-law rules. The courts located in India shall have exclusive jurisdiction over any dispute arising from or relating to these terms or your use of Vagle AI, unless a separate written agreement states otherwise.","Before bringing a formal claim, you agree to first contact us so we can try to resolve the issue in good faith."]},{id:"changes",title:"13. Changes to these terms",body:['We may update these terms from time to time. When we make material changes, we will update the "last updated" date and, where appropriate, provide additional notice. Continued use of Vagle AI after changes take effect means you accept the updated terms.']},{id:"contact",title:"14. Contact",body:[`For questions about these terms, contact ${a}.`]}],v=[{id:"mission",title:"1. Mission",body:["Vagle AI is built to help small and growing businesses automate customer calls, lead follow-ups, appointment workflows, and business tool updates using AI voice agents."]},{id:"who-we-serve",title:"2. Who we serve",body:["The platform is designed for MSMEs, sales teams, clinics, real estate teams, service companies, support teams, agencies, and operators who need a practical way to handle calls and follow-ups."]},{id:"product-focus",title:"3. Product focus",body:["Vagle combines voice calling, follow-up funnels, call logs, and business tool automation in one practical platform. The goal is simple: fewer missed calls, clearer lead records, and less manual follow-up work.","Vagle AI is built for businesses that need calls, follow-ups, lead records, and tool updates to work together without manual automation setup."]},{id:"how-we-work",title:"4. How we work",body:["We keep claims conservative and practical. Provider availability, call quality, language support, and cost depend on the selected configuration, connected accounts, and real-world testing for each customer workflow."]},{id:"contact",title:"5. Contact",body:[`Business enquiries, grants, customer support, and sales: ${a}.`]}],A=[{id:"accounts",title:"1. Account protection",body:["Vagle AI uses user authentication, workspace access controls, admin permissions, and session protections to help protect business accounts and call data."]},{id:"tenant-separation",title:"2. Workspace and tenant separation",body:["Workspace data is separated by account, organization, and workspace context where applicable. Users should only see the data their workspace role allows them to access."]},{id:"credentials",title:"3. API keys, OAuth tokens, and MCP tokens",body:["Provider keys, OAuth tokens, connected tool credentials, and MCP/API tokens are treated as sensitive. We protect them with access controls and encryption where applicable, limit access based on workspace permissions, and avoid exposing raw secrets in normal responses.","MCP tokens are intended to be shown only at creation time. After that, stored token records should use hashed token values and display only safe metadata such as prefix, scopes, status, and timestamps."]},{id:"calls",title:"4. Call logs, transcripts, and recordings",body:["Call logs, transcripts, summaries, recordings where enabled, detected outcomes, and tool actions are available based on workspace access. Customers should assign access carefully because this data can contain personal or business information."]},{id:"tools-webhooks",title:"5. Tools, webhooks, and external actions",body:["Tool Workspace actions are designed to run only with configured credentials, selected fields, and scoped workspace permissions. Webhooks and HTTP tools should be configured with safe endpoints, limited payloads, and no secrets in visible fields.","Where available, tool execution logs should redact secrets such as Authorization headers, cookies, API keys, OAuth tokens, provider keys, and credential identifiers."]},{id:"audit-logging",title:"6. Audit logging and monitoring",body:["The platform uses practical controls such as audit logging, webhook validation, tool access checks, error monitoring, rate limiting where applicable, and scoped MCP/API permissions.","Audit logs are intended to help review important actions without exposing raw secrets. MCP/API tool responses are designed to return only the data needed for the requested action and to keep credentials, authorization headers, provider keys, and raw tokens out of normal responses."]},{id:"certifications",title:"7. Security certifications",body:["We are continuously improving security as the platform scales. We do not claim SOC 2, ISO, or similar certifications unless and until they are formally completed."]},{id:"contact",title:"8. Report a concern",body:[`To report a security concern, contact ${a}.`]}],k=[{id:"overview",title:"1. Overview",body:["This Acceptable Use Policy applies to everyone who uses Vagle AI. It exists to keep calls lawful, honest, and safe for the people who receive them. By using Vagle AI you agree to follow this policy in addition to the Terms and Conditions."]},{id:"prohibited",title:"2. Prohibited use",body:["You must not use Vagle AI for any of the following:"],bullets:["Spam, bulk unsolicited calling, or scams of any kind.","Harassment, threats, abusive calls, or repeated unwanted contact.","Deceptive calls, false claims, or hiding the real purpose of a call.","Impersonating another person, business, brand, or government body.","Bypassing consent, opt-out, or do-not-call requirements.","Unlawful surveillance, recording, or tracking of individuals.","Malware, phishing, credential theft, or social-engineering attacks.","Emergency, crisis, medical, or safety-of-life services or routing.","High-risk medical, legal, financial, or eligibility decisions without qualified human review.","Collecting sensitive data (payment card numbers, passwords, government IDs, health data) without a lawful basis and proper safeguards."]},{id:"consent",title:"3. Consent, opt-outs, and calling compliance",body:["You are responsible for having a lawful basis and any required consent to call your leads or customers, for AI disclosure where required, for call-recording notices, and for honoring opt-outs, do-not-call lists, and telemarketing and telecom rules that apply to your use case and region.","If a person opts out or asks not to be called, you must stop calling them where opt-out applies."]}

1,{id:"platform",title:"4. Protecting the platform",body:["Do not attempt to bypass rate limits, attack the service, access another customer workspace, scrape protected systems, connect tools you are not authorized to use, or send secrets through fields visible to end users or AI models."]},{id:"enforcement",title:"5. Enforcement",body:["We may investigate suspected violations and may suspend or limit access to protect callers, customers, providers, connected tools, or the platform. Serious or repeated violations can result in account termination."]},{id:"report",title:"6. Report abuse",body:[`To report abuse or a violation of this policy, contact ${a}.`]}],I=[{id:"overview",title:"1. Developer access overview",body:["Vagle AI offers workspace-scoped API access and MCP/API tooling so teams can build dashboards and integrations on top of their own call, lead, and outcome data. This page summarizes how access, tokens, scopes, and write actions are designed to work."]},{id:"api-keys",title:"2. Workspace API keys",body:["Workspace API keys are created per client workspace and are read-only and scope-limited by design. A key is shown in full only once at creation time. After that, only a non-secret prefix and safe metadata (scopes, status, timestamps) are displayed; the secret is stored hashed."]},{id:"scopes",title:"3. Scopes and read/write separation",body:["Access is limited by scopes such as calls, call detail, analytics, outcomes, and leads. Public read APIs are separated from write actions. Write or mutating actions (for example, connected-tool updates or configuration changes) are handled through authenticated, audited paths and may require approval or confirmation steps."]},{id:"isolation",title:"4. Workspace isolation",body:["API keys, MCP tokens, and requests are scoped to a single organization and workspace. A token cannot read or act on another workspace’s data. Tools and credentials configured in one workspace are not usable from another."]},{id:"tokens",title:"5. Token revocation and rotation",body:["Keys can be revoked or rotated at any time from the workspace. Revoking a key immediately stops further access using that secret. Rotating issues a new secret (shown once) and retires the old one."]},{id:"webhooks",title:"6. Webhooks and signatures",body:["Outbound webhooks are sent to URLs you configure and are signed with a per-endpoint signing secret so your server can verify authenticity before trusting an event. Webhook target URLs are validated to block private, internal, and metadata addresses, and the signing secret is shown only once."]},{id:"secrets",title:"7. Secrets and audit logs",body:["API responses, logs, and tool execution records are designed to exclude raw secrets — API keys, OAuth tokens, webhook secrets, and provider keys are not returned in normal responses. Important actions are recorded in audit logs that capture who did what, without exposing raw secret values."]},{id:"support",title:"8. Support and security contact",body:[`For developer questions, API access, or to report a security concern, contact ${a}.`]}],P=[{id:"overview",title:"1. GDPR readiness overview",body:["Vagle AI is designed to support European customers using AI voice agents, call logs, transcripts, recordings, follow-up funnels, and connected business tools. This page explains the platform controls available to help customers operate under the GDPR, UK GDPR, and related European privacy expectations.","This page is product and compliance information, not legal advice. Customers remain responsible for deciding their legal basis, notices, consent flows, and sector-specific obligations."]},{id:"roles",title:"2. Controller and processor roles",body:["For account, billing, authentication, security, abuse-prevention, and product analytics data, Vagle AI generally acts as a controller.","For caller, lead, campaign, transcript, recording, and connected-tool data processed on behalf of a customer, the customer generally acts as controller and Vagle AI acts as processor. Customers decide why calls are made, who is contacted, what data is uploaded, and how long customer business records should be kept."]},{id:"eu-mode",title:"3. EU Compliance Mode",body:["Vagle AI includes an EU Compliance Mode for account settings. When enabled, the platform enforces conservative defaults: AI disclosure required, recording consent required, outbound legal basis required, outbound calling blocked where consent/legal basis is missing, and shorter default retention windows for transcripts, recordings, and leads.","These controls help reduce accidental non-compliant usage, but they do not replace customer legal review for each campaign or jurisdiction."]},{id:"rights",title:"4. Data subject rights",body:["Users can export account-linked product data and submit privacy requests from account settings. Supported request types include export, deletion, rectification, and restriction of processing.","Callers or leads who were contacted by a Vagle AI customer should usually contact that customer first because the customer controls the purpose of the call and the lead source. Vagle AI helps customers respond to verified requests where Vagle AI is the processor."]},{id:"calling",title:"5. AI calling, notices, and opt-out",body:["Customers using AI voice agents in Europe should disclose that the person is speaking with an AI system where required, provide call-recording notices where recording or transcription is enabled, and honor opt-out and do-not-call requests.","Vagle AI supports opt-out/DNC handling and consent-gated follow-up funnels. Customers should enable those controls for European workflows."]},{id:"transfers",title:"6. International transfers",body:["Vagle AI may use providers located outside the EU/EEA for hosting, voice, transcription, language models, storage, payment, email, and support. Where required, cross-border transfers should be covered by appropriate safeguards such as adequacy decisions, standard contractual clauses, or equivalent contractual protections.","A current list of subprocessors is available on the Subprocessors page."]},{id:"security",title:"7. Security measures",body:["The platform uses authentication, access controls, workspace scoping, API and MCP token scopes, audit logging, credential protections, webhook signing, rate limits, and managed recording access controls to protect customer data.","Customers should assign workspace roles carefully and avoid collecting sensitive personal data through voice agents unless they have a lawful basis and appropriate safeguards."]},{id:"contact",title:"8. GDPR contact",body:[`For GDPR, DPA, subprocessor, or data-rights questions, contact ${a}.`]}],C=[{id:"scope",title:"1. Data Processing Addendum summary",body:["This DPA summary describes the intended processor terms for customers using Vagle AI to process caller, lead, campaign, transcript, recording, and connected-tool data. A signed customer agreement or negotiated DPA may include additional terms.","Vagle AI processes customer personal data only to provide the service, maintain security, support configured workflows, comply with law, and follow documented customer instructions."]},{id:"processing",title:"2. Processing details",body:["Subject matter: AI voice calling, inbound and outbound calls, follow-up automation, transcripts, summaries, recordings where enabled, lead records, connected tool updates, analytics, and support.","Data categories: names, phone numbers, email addresses, lead fields, call metadata, transcripts, summaries, recordings where enabled, tool-action metadata, workspace users, and support messages.","Data subjects: customer workspace users, callers, leads, prospects, customers, and contacts uploaded or connected by the customer."]},{id:"customer-instructions",title:"3. Customer instructions and legal basis",body:["Customers are responsible for lawful basis, notices, consent, opt-out handling, lead-source legality, do-not-call compliance, and industry-specific rules. Vagle AI provides controls to help customers configure compliant workflows.","Customers must not use Vagle AI for unlawful calling, deceptive calls, consent bypass, or sensitive-data collection without proper safeguards."]},{id:"subprocessors",title:"4. Subprocessors",body:["Vagle AI may use subprocessors for hosting, storage, speech-to-text, text-to-speech, voice agents, language models, telephony, payment, email, analytics, and support. Current subprocessors are listed on the Subprocessors page.","Vagle AI will use commercially reasonable efforts to ensure subprocessors are bound by data-protection terms appropriate to their processing role."]},{id:"security",title:"5. Security and confidentiality",body:["Vagle AI uses technical and organizational measures designed to protect customer personal data, including access control, role scoping, credential protection, transport security, logging, and limited access to production systems.","Personnel and service providers with access to customer data are expected to handle it confidentially and only for authorized purposes."]},{id:"assistance",title:"6. Assistance, deletion, and return",body:["Vagle AI will provide reasonable assistance for customer data-subject requests, security inquiries, data export, and deletion where Vagle AI acts as processor and the request is verified.","At customer request or account termination, customer data can be deleted or exported subject to legal, security, backup, audit, and billing retention obligations."]},{id:"breach",title:"7. Security incidents",body:["If Vagle AI becomes aware of a confirmed personal-data breach affecting customer personal data, Vagle AI will notify affected customers without undue delay and provide available information needed for customer assessment and notification duties."]},{id:"transfers",title:"8. International transfers",body:["Where customer personal data is transferred outside the EU/EEA or UK, Vagle AI and customers should rely on appropriate safeguards such as standard contractual clauses, adequacy decisions, or another lawful transfer mechanism."]}],x=[{id:"overview",title:"1. Subprocessor overview",body:["Vagle AI uses third-party providers to operate the product. The exact providers used for a customer workflow depend on configured phone numbers, AI providers, voice providers, storage, payment, email, and connected tools.","Customers can contact Vagle AI for the latest subprocessor list or to discu

1ss enterprise provider restrictions."]},{id:"list",title:"2. Current subprocessors",bullets:["AWS / EC2 / S3 - hosting, compute, deployment artifacts, storage, and infrastructure operations.","MongoDB Atlas - primary application database and operational data storage.","Cartesia - voice agents, speech generation, and real-time voice streaming where selected.","Deepgram - speech-to-text transcription where selected.","Groq, OpenAI, Gemini, Qwen, DeepInfra, Minimax, ElevenLabs, Rime, Fish, Smallest, Inworld - AI, language model, voice, or speech processing where selected/configured.","Twilio, Plivo, Vobiz, WhatsApp/Meta - telephony, messaging, phone number, or communication services where selected/configured.","Stripe and Razorpay - payment processing and billing operations.","Google APIs - Gmail, Calendar, Sheets, OAuth, or other configured Google actions.","Notion, Airtable, webhooks, and customer-connected APIs - connected tool destinations selected by the customer."]},{id:"data",title:"3. Data shared with subprocessors",body:["Only data needed for the configured workflow is sent to a subprocessor. This may include audio, text prompts, transcripts, summaries, phone numbers, lead fields, call metadata, tool-action payloads, billing identifiers, or workspace metadata.","Provider use can vary by customer configuration. Customers should review their own assistant, phone number, tool, and provider settings before running European campaigns."]},{id:"updates",title:"4. Updates and objections",body:[`For questions about subprocessors, provider restrictions, or enterprise terms, contact ${a}.`]}],c={privacy:{eyebrow:"Privacy Policy",title:"Privacy Policy",metaTitle:"Privacy Policy | Vagle AI",metaDescription:"Read how Vagle AI handles account data, call data, recordings, transcripts, lead data, connected tool data, MCP/API tokens, credentials, retention, and user rights.",path:"/privacy",subtitle:"How Vagle AI handles account data, call data, recordings, transcripts, lead data, connected tools, credentials, and support messages.",sections:f,summary:["We collect data needed to run the service.","Call data can include transcripts and recordings where enabled.","Connected tool data is used only for configured actions."]},terms:{eyebrow:"Terms and Conditions",title:"Terms and Conditions",metaTitle:"Terms and Conditions | Vagle AI",metaDescription:"Read the terms for using Vagle AI voice agents, calling, follow-up funnels, connected tools, MCP/API access, usage billing, providers, and call consent responsibilities.",path:"/terms",subtitle:"The basic rules for using Vagle AI for voice agents, calling, follow-ups, tool updates, billing, MCP/API access, and connected services.",sections:w,summary:["Customers are responsible for lawful calling.","Calling is usage based.","All Access unlocks follow-up automation and related premium workspaces."]},about:{eyebrow:"About",title:"About Vagle AI",metaTitle:"About Vagle AI | AI Voice Calling for Business Automation",metaDescription:"Learn about Vagle AI, a practical platform for AI voice calls, lead follow-ups, appointment workflows, and business tool updates.",path:"/about",subtitle:"Vagle AI helps businesses automate customer calls, lead follow-ups, appointment workflows, and business tool updates.",sections:v,summary:["Built for practical business calls.","Focused on MSMEs and growing teams.","Voice calling, follow-ups, and tools in one platform."]},security:{eyebrow:"Security",title:"Security",metaTitle:"Security | Vagle AI",metaDescription:"Review Vagle AI security practices for authentication, workspace access, sensitive credentials, MCP/API tokens, call logs, transcripts, recordings, webhooks, and audit logging.",path:"/security",subtitle:"A practical view of how Vagle AI protects accounts, credentials, MCP/API tokens, call logs, transcripts, recordings, and connected tools.",sections:A,summary:["Workspace access controls.","Sensitive credential protection.","Continuous security improvement."]},"acceptable-use":{eyebrow:"Acceptable Use",title:"Acceptable Use Policy",metaTitle:"Acceptable Use Policy | Vagle AI",metaDescription:"Vagle AI Acceptable Use Policy: no spam, scams, harassment, deceptive calls, impersonation, consent bypass, unlawful surveillance, emergency use, malware, or high-risk decisions without human review.",path:"/acceptable-use",subtitle:"The rules for lawful, honest, and safe use of Vagle AI voice agents and calling.",sections:k,summary:["No spam, scams, or deceptive calls.","Respect consent, opt-outs, and DNC rules.","No high-risk decisions without human review."]},developers:{eyebrow:"Developers & API",title:"Developers, API & MCP Security",metaTitle:"Developers, API & MCP Security | Vagle AI",metaDescription:"How Vagle AI workspace API keys, MCP/API access, scopes, read/write separation, token revocation, workspace isolation, audit logs, and webhook signatures work.",path:"/developers",subtitle:"Workspace API keys, MCP/API access, scopes, token revocation, workspace isolation, webhook signatures, and audit logging.",sections:I,summary:["Read-only, scope-limited workspace API keys.","Tokens shown once, stored hashed, revocable.","Signed webhooks and audited write actions."]},gdpr:{eyebrow:"GDPR",title:"GDPR Readiness",metaTitle:"GDPR Readiness | Vagle AI",metaDescription:"How Vagle AI supports European GDPR workflows with EU Compliance Mode, AI disclosure, consent controls, data rights, retention settings, DPA terms, and subprocessors.",path:"/gdpr",subt

1itle:"Product controls and operating commitments for European AI voice calling workflows.",sections:P,summary:["EU Compliance Mode.","Data export and privacy requests.","DPA and subprocessor transparency."]},dpa:{eyebrow:"DPA",title:"Data Processing Addendum",metaTitle:"Data Processing Addendum | Vagle AI",metaDescription:"Vagle AI DPA summary for customer-controlled caller, lead, campaign, transcript, recording, and connected-tool data.",path:"/dpa",subtitle:"Processor terms and customer responsibilities for Vagle AI customer data processing.",sections:C,summary:["Customer data processed on instructions.","Subprocessors disclosed.","Deletion/export assistance."]},subprocessors:{eyebrow:"Subprocessors",title:"Subprocessors",metaTitle:"Subprocessors | Vagle AI",metaDescription:"Current Vagle AI subprocessors for hosting, storage, AI, voice, transcription, telephony, payments, and connected-tool workflows.",path:"/subprocessors",subtitle:"Providers that may process customer data depending on selected Vagle AI configuration.",sections:x,summary:["Provider list by purpose.","Workflow-specific data sharing.","Enterprise provider restrictions available."]}},V={privacy:y,terms:l,about:l,security:i,gdpr:i,dpa:l,subprocessors:i};function G({type:r="privacy"}){const o=c[r]||c.privacy,d=V[r]||l,u=[h([{name:"Home",path:"/"},{name:o.eyebrow,path:o.path}])];return e.jsxs("div",{className:"legal-page",children:[e.jsx(g,{title:o.metaTitle,description:o.metaDescription,path:o.path,schema:u}),e.jsx("header",{className:"legal-header",children:e.jsxs("nav",{className:"legal-nav","aria-label":"Legal navigation",children:[e.jsxs(t,{to:"/",className:"legal-brand",children:["Vagle",e.jsx("span",{children:"AI"})]}),e.jsxs("div",{className:"legal-nav-links",children:[e.jsx(t,{to:"/about",className:r==="about"?"active":"",children:"About"}),e.jsx(t,{to:"/use-cases",children:"Use Cases"}),e.jsx(t,{to:"/blog",children:"Blog"}),e.jsx(t,{to:"/security",className:r==="security"?"active":"",children:"Security"}),e.jsx(t,{to:"/gdpr",className:r==="gdpr"?"active":"",children:"GDPR"}),e.jsx(t,{to:"/privacy",className:r==="privacy"?"active":"",children:"Privacy"}),e.jsx(t,{to:"/terms",className:r==="terms"?"active":"",children:"Terms"}),e.jsx(t,{to:"/contact",children:"Contact"})]}),e.jsxs(t,{to:"/",className:"legal-back",children:[e.jsx(m,{size:16})," Home"]})]})}),e.jsxs("main",{className:"legal-main",children:[e.jsxs("section",{className:"legal-hero",children:[e.jsxs("div",{className:"legal-hero-copy",children:[e.jsxs("div",{className:"legal-eyebrow",children:[e.jsx(d,{size:16})," ",o.eyebrow]}),e.jsx("h1",{children:o.title}),e.jsx("p",{children:o.subtitle}),e.jsxs("div",{className:"legal-meta",children:[e.jsxs("span",{children:["Last updated: ",b]}),e.jsxs("span",{children:["Contact: ",a]})]})]}),e.jsxs("aside",{className:"legal-summary-card","aria-label":"Page summary",children:[e.jsx(i,{size:22}),e.jsx("h2",{children:"At a glance"}),e.jsx("ul",{children:o.summary.map(s=>e.jsxs("li",{children:[e.jsx(p,{size:16})," ",s]},s))})]})]}),e.jsxs("section",{className:"legal-content-shell",children:[e.jsxs("aside",{className:"legal-toc","aria-label":"Table of contents",children:[e.jsx("strong",{children:"Contents"}),o.sections.map(s=>e.jsx("a",{href:`#${s.id}`,children:s.title.replace(/^\d+\.\s*/,"")},s.id))]}),e.jsx("div",{className:"legal-document",children:o.sections.map(s=>e.jsxs("section",{id:s.id,className:"legal-section",children:[e.jsx("h2",{children:s.title}),(s.body||[]).map(n=>e.jsx("p",{children:n},n)),Array.isArray(s.bullets)&&s.bullets.length>0&&e.jsx("ul",{className:"legal-bullets",children:s.bullets.map(n=>e.jsx("li",{children:n},n))})]},s.id))})]})]})]})}export{G as default};