Privacy Policy — SACA MCP

Scope and confirmation status

This policy concerns the read-only SACA MCP service at https://sacacreations.in/mcp. It describes the verified application behavior, not a claim that no data is collected.

Confirmation before publication: SACA must confirm the deployed hosting and analytics settings, operational log access, retention and deletion periods, and third-party processing arrangements. Those details are not established by the application code and are marked below. SACA should approve this policy before presenting it as final.

Information accessed and returned

The tools return public school information, Bharatanatyam class options, production and performance descriptions, and Library article titles and text. They read content bundled with the website, not private contact submissions or student records.

The service processes MCP requests, including the requested tool and an article identifier when supplied. Its tools do not ask for your name, email, phone number, or account details, and do not save tool requests in an application database. Please avoid including personal or sensitive information in queries.

Operational logs and analytics

The server includes error logging. The MCP library also supports operational records such as tool name, request method, protocol version, outcome, processing time, and request or response sizes. Local diagnostic messages can include error details.

The library’s default configuration can send usage metrics to Lovable when its required server credential is configured; without that credential, metric transmission disables itself. The metric payload is operational metadata rather than article-request text or full tool responses. Whether metric transmission is enabled on the deployed Vercel service requires confirmation.

Hosting and network providers process connection information to deliver requests and may retain access logs, including IP addresses, timestamps, request paths, and technical headers. Exact log fields, access, analytics settings, and retention periods require confirmation from SACA’s deployed service settings. No separate website analytics integration was identified in the reviewed application source; that does not exclude hosting-level analytics.

Cookies and browser storage

The MCP tool handlers do not explicitly set cookies or use browser storage and do not require a SACA login. That does not establish the behavior of hosting infrastructure or your AI app, which must be assessed separately.

These support and policy pages use the website’s shared styles and branding. The website requests fonts from Google Fonts. Other website functionality includes browser authentication support; its settings should not be interpreted as MCP data collection. Cookies and storage added by deployed services require confirmation.

Third-party processing

Vercel hosts the deployed service. Lovable may receive the operational metrics described above if enabled. Your chosen AI app receives the tool results and handles your conversations under its own privacy policy; connecting SACA MCP does not replace that policy.

The separate website enquiry form processes contact details through Google Sheets and Lovable Cloud for enquiry handling and submission limits. MCP tools do not access those submissions. This MCP-specific policy does not set a retention period for that separate form.

Retention and privacy requests

The MCP tools have no application-level request archive. Retention periods for server logs, usage metrics, infrastructure records, and correspondence have not been verified; no specific deletion deadline or retention period is promised here. SACA must confirm those periods before publication.

For privacy questions or requests relating to information SACA controls, email sacacreations@gmail.com. Describe your request without sending passwords or unnecessary sensitive information. If it concerns a conversation stored by your AI app, contact that provider as well.