> ## Documentation Index
> Fetch the complete documentation index at: https://developer.timekettle.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Timekettle Developer

> Build with Timekettle translation services, review platform policies, and prepare integrations for production.

# Build language experiences with Timekettle

Timekettle Developer is the home for integration guidance, platform policies, and legal documentation for teams building with Timekettle translation services, SDKs, and AI-enabled language workflows.

<Callout icon="shield-check" color="#FF6A00">
  These docs are structured for maintainability: concise pages, root-relative links, shallow navigation, and legal content that can be reviewed independently before launch.
</Callout>

## Quick links

<CardGroup cols={2}>
  <Card title="Getting started" icon="rocket" href="/getting-started/overview" cta="Open guide">
    Understand the developer site structure, integration assumptions, and production readiness checklist.
  </Card>

  <Card title="Privacy Policy" icon="shield" href="/legal/privacy-policy" cta="Review policy">
    Review how Timekettle Developer and SDK services may collect, process, retain, and protect data.
  </Card>

  <Card title="Terms of Service" icon="file-text" href="/legal/terms-of-service" cta="Review terms">
    Understand service access, user responsibilities, API usage rules, availability, and termination.
  </Card>

  <Card title="Cookie Policy" icon="cookie" href="/legal/cookie-policy" cta="Review cookies">
    Learn how necessary, analytics, and functional cookies support the developer documentation site.
  </Card>
</CardGroup>

## What you can do here

<Tabs>
  <Tab title="Evaluate" icon="search">
    Review the high-level developer documentation and legal terms before starting a Timekettle integration.
  </Tab>

  <Tab title="Integrate" icon="code">
    Use the getting started guide as the landing point for SDK, API, authentication, and rollout documentation as the platform expands.
  </Tab>

  <Tab title="Prepare for launch" icon="clipboard-check">
    Use the policies and checklists to align privacy disclosures, user consent flows, diagnostics, retention, and support processes.
  </Tab>
</Tabs>

## Recommended reading order

<AccordionGroup>
  <Accordion title="For engineering teams" icon="code-2">
    Start with [Getting started](/getting-started/overview), then review [API usage terms](/legal/terms-of-service#api-usage) before exposing production traffic.
  </Accordion>

  <Accordion title="For legal and privacy reviewers" icon="scale">
    Start with [Privacy Policy](/legal/privacy-policy), then review [Cookie Policy](/legal/cookie-policy) and [Terms of Service](/legal/terms-of-service).
  </Accordion>

  <Accordion title="For documentation maintainers" icon="book-open">
    Keep new pages in MDX, add them to `docs.json`, use root-relative links, and run `mint validate` plus `mint broken-links` before deployment.
  </Accordion>
</AccordionGroup>