import type { Metadata } from "next";
import { LegalPage } from "@/components/marketing/legal";

export const metadata: Metadata = {
  title: "Privacy Policy",
  description: "How PolyLLM handles your account, API keys, conversations and usage data. Short, honest and written for humans.",
  alternates: { canonical: "/privacy" },
};

export default function PrivacyPage() {
  return (
    <LegalPage
      eyebrow="Legal"
      title="Privacy Policy"
      updated="September 8, 2026"
      intro={
        <p>
          PolyLLM is a bring-your-own-keys workspace. That shapes everything about privacy here: we run the interface, you own the keys and the relationship with each AI provider. This policy explains, in plain terms, what we store, why, where it goes and how you get rid of it.
        </p>
      }
      sections={[
        {
          id: "what-we-collect",
          title: "What we collect",
          body: (
            <>
              <ul>
                <li>
                  <strong>Account:</strong> your name, email address and an Argon2id hash of your password. We never store the password itself.
                </li>
                <li>
                  <strong>Provider API keys:</strong> the keys you choose to connect, encrypted at rest with AES-256-GCM. Only a short hint (for example <code>sk-••••••••9A2K</code>) is ever displayed.
                </li>
                <li>
                  <strong>Conversations:</strong> the prompts you send, the responses you receive, attachments you upload, folders, presets and settings.
                </li>
                <li>
                  <strong>Usage metadata:</strong> per request, the model, token counts, latency, an estimated cost and an error code if one occurred. Never the prompt text itself in this table.
                </li>
                <li>
                  <strong>Audit and security logs:</strong> sign-ins, key changes, exports and deletions, with the IP address and browser user agent at the time, kept to protect your account.
                </li>
              </ul>
              <p>We do not use analytics trackers, advertising pixels or fingerprinting scripts.</p>
            </>
          ),
        },
        {
          id: "api-keys",
          title: "How your API keys are handled",
          body: (
            <>
              <p>
                Keys are encrypted before they are written to the database using AES-256-GCM with a server-held master key. They are decrypted in server memory only for the duration of a request to the provider you selected, and they are never sent to your browser, written to logs or shared with anyone.
              </p>
              <p>You can replace or remove a key at any time from Settings. Removing a key deletes the encrypted record immediately. You can also revoke a key from the provider&apos;s own console, which makes the stored copy useless.</p>
            </>
          ),
        },
        {
          id: "where-data-goes",
          title: "Where your data goes",
          body: (
            <>
              <p>
                When you send a message, its content (and any attachments the model supports) is transmitted from PolyLLM&apos;s server to <strong>the provider behind the model you picked</strong> and nowhere else: OpenAI, Anthropic, Google or xAI. Each provider processes that data under its own terms and privacy policy, using your account with them.
              </p>
              <p>We do not route requests through third-party inference brokers, and we do not use your prompts or responses to train anything.</p>
              <p>
                Transactional email (verification, password reset, security notices) is delivered through <strong>Resend</strong>, which receives your email address and the message content for that purpose only.
              </p>
            </>
          ),
        },
        {
          id: "storage",
          title: "Where your data is stored",
          body: (
            <p>
              Conversations, settings, usage records and encrypted keys are stored in PolyLLM&apos;s own PostgreSQL database. Backups are encrypted and retained for a limited period to recover from failures. Access is restricted to the operators of the service for maintenance and abuse prevention.
            </p>
          ),
        },
        {
          id: "your-controls",
          title: "Export and deletion",
          body: (
            <ul>
              <li>
                <strong>Export:</strong> download a complete JSON export of your conversations, settings and usage from Settings at any time.
              </li>
              <li>
                <strong>Delete a conversation or folder:</strong> removed immediately, including attachments and any public share link.
              </li>
              <li>
                <strong>Delete your account:</strong> after an email confirmation, every row associated with you is deleted, including encrypted keys, sessions and audit entries. Backups expire on their normal schedule.
              </li>
            </ul>
          ),
        },
        {
          id: "sharing",
          title: "Public share links",
          body: (
            <p>
              If you create a share link for a conversation, a frozen snapshot of its messages becomes readable by anyone with the link, without an account. Share pages are excluded from search engines. Revoking the link disables the page immediately.
            </p>
          ),
        },
        {
          id: "cookies",
          title: "Cookies",
          body: (
            <p>
              PolyLLM sets a small number of first-party cookies to keep you signed in and to protect against cross-site request forgery. They are HttpOnly and Secure. A preference cookie remembers your light or dark theme. There are no third-party or advertising cookies.
            </p>
          ),
        },
        {
          id: "changes",
          title: "Changes to this policy",
          body: <p>If we change how we handle your data in a meaningful way, we will update this page and notify you by email before the change takes effect.</p>,
        },
      ]}
    />
  );
}