Privacy

When you run the free audit, the CSV or TSV you upload or paste is parsed and analysed entirely in your own browser. The raw invoice text — line descriptions, pod names, workload names — is never transmitted to us and never stored anywhere.

If you request an optional email summary, we ask for your name, work email, optionally your company, and an optional spend band. That's it. We store those so we can send you the report and, if you tick the box, tell you when the benchmark and new tools ship. You can unsubscribe at any time, and you can ask us to delete your record by emailing support@creatorcoreforge.com.

We also record your browser's user-agent string and the page that referred you, for basic analytics and abuse prevention. We do not use third-party advertising trackers.

Cost Control is optional. Your RunPod API key is sent securely to our server, encrypted in Supabase Vault, and used only to read resource and billing information. We do not store resource environment variables, start or stop pods, or delete RunPod data.

We store selected pod details and billing summaries for up to 90 days, plus the job records you choose to enter. Disconnecting deletes the stored key and imported scan history; job records can be deleted individually. Account access is restricted to you.

Budget and weekly emails are off by default. If enabled, summaries are sent to your verified sign-in email through our email delivery provider.

When you request an optional email summary, the figures from your audit — totals billed, compute and storage split, GPU-hours, estimated overspend, and the mix of GPU classes you ran (for example "H100 SXM") — contribute to the CoreForge GPU Spend Benchmark, the annual public report on what AI teams actually pay.

These figures are stored in a separate table that holds no link back to you: no name, no email, no company, no foreign key, and no invoice text or workload names. Nothing identifying you, your company or your work ever appears in the benchmark, and the contribution cannot be traced back to your lead record. That separation is deliberate and structural, not a promise we ask you to take on faith.

• Store your raw invoice text or workload names.
• Sell your name, email or company to anyone.
• Join your benchmark figures back to your identity.
• Fake a delay or a block to manufacture perceived value.

If you create an account and save reports, those saved reports are stored against your user ID. On Solo they are visible only to you, enforced at the database level. On a Team plan, saved reports are shared with the team owner and the other members of that team, so everyone can see the team's spend history.

We keep your account data while your account is open. To delete your account and the reports and job records stored with it, email us and we will confirm once it's done. Payment records held by Stripe are kept as tax and accounting law requires.

We share data with these providers only so they can run parts of the service:

• Stripe — payments and subscription billing. Card details go to Stripe directly; we never see or store them.
• Google Firebase — sign-in.
• Supabase — database, account data, saved reports and the encrypted RunPod key.
• Resend — sending the report and alert emails you ask for.
• Lovable and Cloudflare — hosting the website.
• Plausible — cookieless, aggregate page analytics, when enabled. It does not track you across sites.

Some of these providers process data in the United States. We do not sell personal data.

Questions, corrections or a deletion request: support@creatorcoreforge.com. See also the terms.