Privacy Policy
Effective date: [Effective date]
1. What we collect
- Account data — your email address and profile, collected and managed through Clerk, our authentication provider. JouleCloud does not store passwords.
- Organization metadata — organization name, membership, budget and rate-limit settings, and billing state.
- API usage metadata — per-request token counts, model id, timestamps, latency, and accrued spend. This is what the console usage views and billing are built on.
2. Prompts and completions
Request and response bodies transit our gateway in order to produce the response and meter usage — that is inherent to operating an inference API. Request logs are retained for [Retention period for request logs] for debugging and abuse prevention, then deleted. We do not use your prompts or completions to train models, and we do not sell them.
3. Operational metadata and derived data
Separately from request content, operating the network generates operational metadata: request volumes and timing, model and hardware utilization, routing decisions, node telemetry, and energy-price and capacity signals observed by the network. We aggregate and de-identify this metadata and may use the result (“Derived Data”) for any lawful business purpose — including the market activities expressly disclosed in section 7 of the Terms of Service. Derived Data never includes, and those activities are never informed by, the content of your prompts or completions.
4. What we do not do
- We do not sell personal data.
- We do not use customer request content for advertising.
- We do not claim certifications we do not hold — see Security for our real posture.
5. Subprocessors
We use a small set of service providers to run JouleCloud, listed by function: Clerk (authentication), Vercel (application hosting), Stripe (billing). [Confirm subprocessor list before publishing.]
6. Your rights
You may request access to, correction of, or deletion of your personal data by emailing [Privacy contact email — default hello@jouledns.com]. Deleting your organization removes its keys and settings; usage records needed for billing integrity may be retained as required.
7. Changes
We will post any changes to this policy on this page with a new effective date.