{"name":"The Leo King Business Intelligence API Data Processing","version":"v1","status":"public-contract","contractVersion":"2026-07-07.enterprise-trust-console-audit-webhook-versioning-limits-examples-support-procurement-conformance-data-processing-launch-readiness-access-control-compliance-map-ai-governance-v1","lastReviewedAt":"2026-07-07","policy":{"status":"live","publicContact":"mailto:partners@theleokingai.com","scope":"Public data-processing review metadata for API buyers. It describes current API handling boundaries and does not replace signed customer-specific DPA terms.","dpaBoundary":"A signed DPA or data-processing addendum is required before custom retention, regional residency, regulated-data commitments, private endpoint scopes, or customer-specific processor terms are promised.","dataMinimization":["Send stable partner-side subject or customer ids instead of names whenever possible.","Send only birth date, time, place, latitude, longitude, campaign context, or prompt fields required by the selected endpoint.","Do not send payment instruments, government ids, health records, unrelated profile data, or raw secrets.","Use sanitized payload shape, request_id, endpoint, UTC timestamp, and key prefix only for support."],"restrictedData":["raw API keys, bearer tokens, webhook secrets, provider credentials","payment card or bank account data","government identifiers","health records or protected medical data","children's data without a signed, reviewed use case","regulated or high-risk data categories not approved in signed terms"],"regionalBoundary":"Public API metadata does not claim data residency or regional processing commitments. Region-specific commitments require signed enterprise terms and provider review.","deletionBoundary":"Deletion/export requests should start from the partner system of record. Platform-side deletion/export assistance requires request_id, partner subject id, organization id, and signed support process when private payloads are involved.","exportBoundary":"Self-serve public metadata is exportable. Customer-specific raw payload exports, long-range audit exports, and private logs require signed enterprise terms and security review."},"purposes":[{"category":"Core Astrology Compute","status":"beta","purpose":"Calculate deterministic chart, transit, compatibility, lunar, and helio background data for partner products.","dataCategories":["partner subject id","birth date","birth time when supplied","birth place or coordinates","event datetime/location"],"lawfulBasisBoundary":"Partner is responsible for end-user notice, consent, and lawful basis for collecting and sending birth or event data.","retentionSource":"API Request Metadata and Birth Data Payloads entries in the public retention policy.","partnerResponsibility":"Store only the deterministic output needed for the product and avoid sending unrelated identity fields."},{"category":"AI Intelligence And Experiences","status":"beta","purpose":"Generate audience intelligence, premium spiritual experiences, oracle/tarot interpretation, and world-signal analysis.","dataCategories":["partner customer id","campaign context","route-specific prompt/context","generated output","model/provider metadata"],"lawfulBasisBoundary":"Partner controls prompts and user-facing context; platform quality gates prevent fallback-shaped output from being treated as success.","retentionSource":"Generated AI Outputs and Support Evidence entries in the public retention policy.","partnerResponsibility":"Do not send private prompts, sensitive personal data, or regulated data unless the signed use case permits it."},{"category":"Billing And Entitlement","status":"beta","purpose":"Meter credits, plan state, scoped key access, request rate, subscription state, and usage reconciliation.","dataCategories":["organization id","API key hash/prefix","endpoint","credits","billing lane","subscription state","request_id"],"lawfulBasisBoundary":"Billing provider handles payment instruments; this API surface tracks entitlement and usage state for subscribed API access.","retentionSource":"Billing And Entitlement Records and API Request Metadata entries in the public retention policy.","partnerResponsibility":"Never send payment card or bank account data to API routes or support channels."},{"category":"Support, Incident, And Conformance Evidence","status":"live","purpose":"Triage integration issues, incidents, output-quality regressions, conformance evidence, and procurement review.","dataCategories":["request_id","endpoint","UTC timestamp","key prefix only","idempotency key hash","sanitized payload shape","deployment metadata"],"lawfulBasisBoundary":"Support evidence should be operational metadata. Raw secrets and complete private payloads are not needed for normal support.","retentionSource":"Support Evidence entry in the public retention policy and conformance evidence retention policy.","partnerResponsibility":"Redact raw payloads, secrets, payment details, and complete birth data unless a signed support process requires them."}],"dataSubjectRequests":{"status":"enterprise","requestTypes":["access/export","deletion","correction","processing restriction","support evidence review"],"partnerResponsibilities":["Authenticate the end user or customer inside the partner system of record.","Map the request to partner subject id, organization id, request_id, endpoint, and UTC timeframe.","Remove or suppress partner-stored outputs according to the partner's own privacy obligations.","Do not send raw API keys, complete private payloads, or payment details in request tickets."],"platformResponsibilities":["Confirm whether request metadata, usage ledger rows, support evidence, or generated outputs are in platform-controlled stores.","Coordinate deletion/export assistance under signed terms when private payloads or customer-specific audit logs are involved.","Keep operational billing, security, and fraud-prevention records where retention is required by signed terms or platform obligations."],"supportPacket":["organization id","partner subject id","request_id list when available","endpoint list","UTC date range","requested action","signed support/DPA reference when private data is involved"],"exclusions":["Public metadata routes do not contain customer payloads.","Payment instruments are handled by Clerk/Stripe and are not exported from API support routes.","Raw provider secrets and internal security logs are not customer export artifacts."]},"retention":[{"category":"API Request Metadata","status":"beta","retention":"Usage ledger retains request_id, endpoint, lane, credits, billable units, model metadata, and timestamps for billing/support reconciliation.","handling":"Do not include full secrets or raw payloads in support tickets; provide request_id and sanitized payload shape."},{"category":"Birth Data Payloads","status":"live","retention":"Processed for deterministic chart calculation and model context; persistent storage is limited to endpoint-specific product records when required.","handling":"Use customer ids and only the birth fields needed for the route. Avoid names and unrelated personal profile data."},{"category":"Generated AI Outputs","status":"beta","retention":"Outputs may be retained where needed for async jobs, quality review, support, or partner-visible history.","handling":"AI output must meet the same product contract after retries; fallback-shaped output should be escalated as a quality incident."},{"category":"Billing And Entitlement Records","status":"beta","retention":"Plan state, credit balances, subscription state, and usage counters are retained for billing operations.","handling":"Payment instruments are handled by Clerk/Stripe rather than stored directly in this API surface."},{"category":"Support Evidence","status":"live","retention":"Support packets should include request_id, endpoint, UTC timestamp, key prefix only, and sanitized payload shape.","handling":"Never send raw API keys, bearer tokens, payment details, or complete private payloads in email or chat."},{"category":"Raw Secrets","status":"live","retention":"Raw API keys and provider secrets must not be logged, committed, or returned by public routes.","handling":"Rotate any exposed secret immediately and replace it with a managed environment variable."}],"subprocessors":[{"name":"Vercel","purpose":"Next.js hosting, edge routing, logs, and deployment rollback.","dataScope":"Request metadata, route execution, environment variable names, and runtime logs.","status":"live"},{"name":"Convex","purpose":"API key validation, usage ledger, entitlement state, and billing/event records.","dataScope":"Organization ids, key hashes/prefixes, usage events, billing state, and support metadata.","status":"beta"},{"name":"Clerk","purpose":"Customer console authentication, organizations, billing state, and checkout integration.","dataScope":"Authenticated user/org profile metadata, plan state, and billing webhook events.","status":"beta"},{"name":"Stripe","purpose":"Payment processing through Clerk Billing and Stripe-connected checkout.","dataScope":"Payment and subscription data handled by the billing provider, not by raw API route storage.","status":"beta"},{"name":"OpenAI Or RunPod","purpose":"Model-backed generation for AI Intelligence routes when enabled by production config.","dataScope":"Sanitized prompts, schema instructions, and route-specific context required to produce the requested output.","status":"beta"},{"name":"Render","purpose":"Kerykeion sidecar hosting for deterministic astrology calculation.","dataScope":"Birth data and calculation inputs needed for chart, transit, synastry, compatibility, and lunar computations.","status":"beta"},{"name":"Upstash","purpose":"Distributed rate limit state and abuse protection.","dataScope":"Request counters, endpoint/key identifiers, and rate-limit windows.","status":"beta"},{"name":"Sentry","purpose":"Error monitoring, release visibility, and source-map assisted debugging.","dataScope":"Error events, stack traces, route context, release id, and redacted runtime diagnostics.","status":"beta"}],"links":{"docs":"/api-docs","security":"/api/v1/security","securityTxt":"/.well-known/security.txt","accessControl":"/api/v1/access-control","procurement":"/api/v1/procurement","conformance":"/api/v1/conformance","compliance":"/api/v1/compliance","support":"/api/v1/support","incidents":"/api/v1/incidents","openapi":"/api/v1/openapi"}}