Who handles your information
Charging Bull Software handles owner account, billing, service-operation and support information. An owner is the game developer; their customers are players. Owners decide what information their games collect from players and are responsible for their own notices and lawful instructions. We process the builds, saves and game traffic needed to host those games. Contact the game owner about information collected within a game; contact us about your NetCraftGames account or information we handle ourselves.
Email support@netcraftgames.com. For the waitlist or anything general, info@netcraftgames.com also works; both reach the same mailbox.
Information we process and why
| Information | Purpose |
|---|---|
| Account name, email, verification status, password verifier, authentication and optional MFA records, settings and access-key metadata | Create and protect accounts, authenticate requests and operate owner controls. |
| Server builds, manifests, dependency/configuration information, protected server secrets, credential metadata and verified saves | Check compatibility, configure accepted releases, run game servers and provide available recovery downloads. Code-reading reports can retain redacted excerpts of up to 160 characters while the build is retained. |
| Runtime history, player/connection counts, traffic totals, usage ledger, chart history, activity and security/API audit events | Allocate prepaid capacity, show service use, diagnose faults, prevent abuse and reconcile actions and payments. |
| Player reports, incident descriptions and diagnostic facts | Investigate reported game or service problems. Information players or owners put in reports may identify them. |
| Stripe customer, checkout, subscription, invoice/payment/refund/dispute identifiers, billing and tax information, terms version and acceptance record, status, amount and signed payment-event records | Process and reconcile purchases, entitlements, cancellations, refunds, taxes, agreement to terms and replay protection. Stripe receives payment details directly; we do not receive full card numbers. |
| Email addresses, message content, delivery metadata and support investigation/response records | Reply to enquiries, operate the waitlist, send service notices, investigate privileged requests and track response targets. |
| Network/request information such as IP address, time, requested path and security/rate-limit events | Deliver the website and application and protect them from misuse. Cloud and email providers also process delivery/security metadata. |
Do not include passwords, private keys, payment-card numbers or unrelated sensitive personal information in reports or email. Redaction can miss information. We do not perform customer age verification or country-of-origin checks.
Website storage and tracking
The marketing website sets no cookies and uses no analytics or advertising trackers or third-party fonts. Some compatibility tools run local browser scripts; the site does not upload the project files you check with those tools. AWS serves the website and handles ordinary request data. We have not configured website access-log delivery to ourselves.
The application uses a session cookie for sign-in and stores authentication and security state needed to operate your account. A public game status/share page is visible when its owner enables it. Your game's own client, scripts and tracking remain the owner's responsibility.
Providers and support AI
| Provider or system | Information and purpose |
|---|---|
| Amazon Web Services (AWS) | Website delivery and DNS; application and game compute; database/storage, builds, saves, backups and infrastructure security/operation. The initial game region is us-east-1 in the United States; global content delivery and provider operations can process request metadata elsewhere. |
| Stripe | Payment collection, billing portal, subscriptions, refunds, disputes and payment-event delivery. Stripe also processes information for its own legal, fraud-prevention and payment obligations. |
| Posthouse, operated by Charging Bull Software | Inbound and outbound email, message storage and delivery records. Email also passes through the sender's and recipient's mail providers. |
| Anthropic, through the installed Claude support selector | A bounded, best-effort redacted excerpt of an eligible public-information support enquiry, to select a reviewed reply. The selector cannot write an arbitrary reply or perform account, billing or security actions. |
| Charging Bull Software's Manager support investigations | Restricted case references, triage reasons, deadlines and follow-through records for requests requiring operator review. |
AI-operated support is separate from optional AI analysis of game incidents or source code. Optional game AI remains off by default and requires separate enablement, consent and provider disclosures before a request. Support messages about accounts, billing, security, privacy or uncertain matters require investigation. Avoid sending private game files to support. Support runs during the hours and targets in the terms.
The support selector uses a Claude Max account with model improvement turned off. Anthropic's Claude Code data policy states a standard 30-day retention period for consumer users who decline model improvement. Its privacy controls exclude new sessions from future general model training under that setting, but allow safety-flagged content to be used for trust and safety work. Longer retention exceptions include policy violations, legal requirements and disputes. This is a consumer-plan service, without an enterprise or API zero-data-retention arrangement.
Our service operates from the United States. Providers and email delivery can process information in other countries. Anthropic's privacy policy, Stripe's privacy policy and the AWS privacy notice describe their international processing and privacy practices. Stripe can retain payment information after our relationship ends for legal, fraud-prevention and financial-record obligations. Our account deletion process does not control these separate provider records. We do not promise immediate provider deletion or processing confined to one country.
We use information to supply and secure the service, respond to you, fulfil the hosting contract and meet applicable legal obligations. We do not sell personal information or use it for targeted advertising. We disclose information to the providers needed for those purposes, to a recipient you authorize, or when law requires it. We may preserve and disclose relevant records to investigate abuse or protect legal rights where permitted by law.
Retention, recovery and deletion
Automatic usage compaction and cancelled-account erasure are off. A 30-day recovery date does not itself erase anything. We assess deletion requests manually, including the information to remove, copies held in other systems and any records we must retain. Contact us to make a request. Until removal is completed, data can remain beyond the recovery window. We will explain relevant exceptions when responding to your request.
| Record class | Current rule and limits |
|---|---|
| Active account, builds, saves and related service records | Kept to provide hosting and recovery. Cancellation takes effect at paid-period end, followed by a 30-day export/recovery window. A release archive keeps its files. Eligible account erasure requires the window to end, no legal/mandatory/payment hold, no active purchase, runtime, queued job or held reservation, and exact stored save versions. |
| Raw billed usage | Eligible for compaction after 90 complete UTC days following the source month's close. The implemented process archives exact detailed rows to private, versioned AWS S3 storage before replacing them with monthly totals and retaining replay controls. Automatic compaction is off, so this eligibility date is not a deletion deadline. Usage archives have no automatic expiry job. |
| Account erasure | The erasure tool removes eligible builds/saves from managed object storage before deleting related application records and anonymizing the account. It preserves financial, credit, subscription/payment, usage-summary/replay, hold, security/API audit and erasure-receipt records. Backups, object versions, email and support investigations are separate copies. Automatic account erasure is off. |
| Financial and tax records | Our normal policy is one year where lawful. Removal requires manual review; there is no automatic financial pruning. Required tax records, disputes, legal holds and necessary payment-replay records can require longer retention. Applicable Maryland sales/use-tax records generally require four years; federal tax-supporting records generally require three years with longer exceptions. |
| Authentication | Expired sessions and login challenges are cleaned up; verification/reset challenges are removed one day after expiry. Sealed verification/reset email payloads older than one hour are removed from the application's outbox. A mailbox copy is separate. |
| Optional game-AI analysis | The implemented purge removes cached analysis content after 30 days and cost-attempt/job audit records after 90 days. The separate provider's copies follow its disclosed terms. The feature remains off by default. |
| Backups and object versions | The infrastructure templates set database-backup expiry at 35 days, noncurrent backup versions at one further day, and retention of the three newest local backup files. Noncurrent build/save object versions have a 90-day lifecycle. These configured periods are not a verified maximum for every existing copy or a promise of immediate deletion. |
| Support email, support claims, waitlist, security/API audit and other retained operational records | There is no complete automatic expiry schedule for these classes. We assess them manually for service, security, investigation and legal needs, including when you request deletion. Posthouse and external provider copies are separate from application erasure. |
The Maryland record rule and IRS guidance explain why the one-year preference is not a blanket deletion deadline. Holds block the affected retention jobs until an authorized review releases them. Releasing a hold does not erase its audit trail. Restoring a backup can restore old records; applicable erasure and hold decisions must be reconciled before those records return to ordinary use.
Export and your choices
While signed in, you can request an account export containing account/game/release records, build metadata, runtime history, reports, incidents, activity, intake records, cancellation-recovery dates, the usage ledger and available monthly usage summaries. Chart history is limited to the newest 20,000 rows. The build/save inventory shows up to 500 builds and 100 verified saves. These responses identify their limits and whether more records exist; contact support if a result is incomplete.
Build binaries and available verified saves use separate authorized download actions with links valid for 15 minutes. The JSON export excludes password/MFA material, secret values, admin credentials, sessions, provider keys and internal worker-bootstrap information. It includes secret names and permitted credential metadata. It is not an export of every backup, security record, email or external provider record.
You can ask to access, correct or delete personal information, stop waitlist messages, or raise a privacy concern through the contact address above. We may need to verify that you control the account or are authorized to act. We assess requests under applicable law, explain relevant retention exceptions and provide any response, appeal or complaint rights the law requires. Players should also contact the owner of the game that collected their information. No request requires emailing a password or private key.
Security and notices
We restrict access by account and operational role and use authentication, protected secrets and encrypted transport/storage controls. These controls reduce risk; they do not guarantee that an incident cannot occur. Report suspected unauthorized access through contact. We investigate and provide required notices to affected owners, individuals and authorities under applicable law. Owners remain responsible for their game's security and notices to players.
We will date material policy changes and provide any required notice before applying them.