Privacy

Career material deserves careful handling.

Battlecat works with career material, so privacy matters. The product is designed around data minimisation: ask for the least useful amount of information needed to read the signal, generate the repair and let you return to your pack.

01

What you submit

The Free Role Lane Check asks for a short career sample only. It does not need your full résumé, home address, phone number, referees or other private details.

The paid Role Lane + Action Pack can use fuller career material so the report can be more useful. This may include your current headline, profile copy, résumé summary, role direction, project evidence, proof points, work wanted or avoided, misunderstood positioning, and any optional job or recruiter context you choose to provide.

Do not paste private, sensitive or unnecessary personal information unless it is genuinely needed for the report.

02

What Battlecat stores

For paid Role Lane + Action Pack users, Battlecat may store your email address, paid access record, pack entitlement, report-build count, latest submitted intake, latest generated report and basic timestamps needed for access, support, abuse prevention and product operation.

The free check is designed to avoid collecting more than a short sample. Free-check samples are not intended to become long-term career records.

03

Where data is stored

Battlecat product, access and report data is stored in Supabase. Payments are handled by Stripe. Battlecat does not store full card details.

Report generation is processed through a third-party model or API provider. Your submitted material is sent to that provider so the report can be created.

04

How report generation uses your material

When you build a Role Lane + Action Pack report, Battlecat sends the relevant intake material to the report-generation provider. This may include your role direction, career summary, project evidence, proof points, work preferences and any optional job or recruiter context you provide.

The provider processes that material to return the report. Battlecat does not claim that submitted material never leaves Battlecat.

Battlecat is configured to minimise retention and avoid training on submitted material where supported by the report-generation provider and routing layer. Provider policies can vary, so only submit information you are comfortable having analysed for this purpose.

05

OpenRouter and model providers

Battlecat uses OpenRouter as part of its report-generation system. Submitted material is sent to the report-generation provider so Battlecat can create the report.

Battlecat’s OpenRouter account is configured with Zero Data Retention routing enabled across the available model groups, including non-frontier, Anthropic, OpenAI and Google routes. Provider routes that do not meet the Zero Data Retention requirement are blocked by that setting.

Battlecat’s OpenRouter privacy settings also block paid and free endpoints that may train on request data, block free endpoints that may publish prompts, and do not allow the optional data-discount setting that permits input/output use for product improvement.

Prompt and completion logging is not intentionally enabled for ordinary Battlecat report generation.

OpenRouter and downstream model providers still process submitted material in order to generate the report. OpenRouter may retain request metadata such as token counts, latency, model/provider routing information and cost reporting, but this metadata does not include the content of prompts or responses according to OpenRouter’s documentation.

Battlecat also enforces provider privacy controls in the report-generation request where supported, including Zero Data Retention routing and denial of provider data collection.

06

How long data is kept

For paid Role Lane + Action Pack users, Battlecat keeps the latest intake/report and pack access data while the pack is active and for a limited support or recovery period after last activity.

Battlecat automatically removes stored paid intake/report content after 90 days from last activity, unless it has already been deleted earlier at the user’s request.

Some limited records may need to be kept for longer where required for payment, tax, fraud prevention, dispute handling, security, abuse prevention or legal reasons. These records should not include the full submitted career material unless it is specifically required for one of those purposes.

Free-check samples are not intended to be kept as long-term records. Free-check material should not be stored as a permanent career record. If free-check material appears in operational logs or debugging tools, it should only be kept as long as needed for operation, support, abuse prevention or debugging.

07

What Battlecat does not do

Battlecat does not sell your career material.

Battlecat does not publish your submissions.

Battlecat does not use your material to train its own model.

Battlecat does not invent achievements, metrics or experience from your material.

Battlecat does not require private details such as home address, phone number, ID numbers, referees or full identity documents.

08

Your choices

You control what you submit. Remove private details before using the tool. Use examples, summaries and project evidence rather than unnecessary personal information.

You can contact us to ask what information is associated with your email, request correction, or request deletion where we are able to do so.

09

Contact

For privacy questions or deletion requests, contact hello@battlecat.co.

This page is clear product guidance, not legal advice. It should be reviewed before a major public launch.