Security Policy

LIVEUTC.AI is designed as a minimal public temporal infrastructure with no accounts, no login and no user-submitted content in V1.

Why it matters

The service keeps a small attack surface and exposes only public temporal data.

Recommended endpoints

• /v1/time.json
• /v1/status
• /privacy

Example

GET https://liveutc.ai/v1/time.json

Scope

V1 does not provide cryptographic attestation or legal timestamping.

Security headers

Strict-Transport-Security: max-age=31536000; includeSubDomains; preload
X-Content-Type-Options: nosniff
X-Frame-Options: DENY
Referrer-Policy: no-referrer
Permissions-Policy: geolocation=()
Access-Control-Allow-Origin: *

Privacy posture

LIVEUTC.AI does not require accounts, browser geolocation, cookies or user-submitted content for core usage.

Related pages

• Documentation index
• Trust and reliability
• AI usage guide
• API documentation
• LLM-readable time anchor
• OpenAPI specification

Maintainer: IVEON.AI