Account Audit Required: Billing Discrepancy, Post-Expiry Trade Initials, Deficient Data Deletion Policy, and Script Export Flaws

Hello Gainium Support,

I am writing to address several technical and billing issues regarding my account and the platform’s performance that require direct clarification and resolution from your team.

1. Subscription Billing and Unrequested Plan Expiry I signed up for the Mini plan using my credit card with the expectation that the subscription would automatically renew each month. However, the plan simply stopped and expired on June 4. While it is possible my account funds were temporarily low at the exact moment of the charge, I received no failed payment notifications or retry attempts.

  • Under normal operating procedures, does your system automatically rebill credit cards monthly, or do subscriptions require manual renewal each period?

  • If a payment fails, what is your automated system protocol regarding retries and user notifications before a plan is cancelled?

2. Multi-Pair / Binance Paper Trading Initiated Post-Subscription Expiry Further complicating the expiration timeline, entirely new multi-pair paper trading deals on Binance were actively initiated on my account on June 14 and June 21—well past the June 4 expiration date.

  • Is there an unmapped grace period built into expired subscriptions that allows the creation of new, restricted deals?

  • If so, what is the exact duration of this window before the system forces a hard downgrade to Free tier restrictions?

3. Unannounced Deletion of 350+ Backtest Histories A few days ago, nearly my entire historical record of backtests disappeared. Out of roughly 400 backtests representing months of development iterations, I am left with only 35, going back no further than June 14.

I use this account frequently and have never left it idle for more than two weeks. Discovering that months of strategy development and data trails have been wiped out without warning is completely unacceptable. If your platform scrubs historical backtests for server maintenance or data management, this policy should be explicitly and clearly marked as a warning on the backtest page as a baseline courtesy to your users.

  • Why were these backtests deleted from your servers despite active account usage?

  • Can your database engineering team restore these historical logs to my account immediately?

4. Inverted Notation in Script Code Exports (API Discrepancy) When exporting bot configurations to a script file, the generated code frequently exports settings with completely inverted notations compared to the UI and the actual execution logic. When I raised this previously, I was told it was a carried-forward legacy issue because previous exports were already generated that way.

This approach is highly counterintuitive and actively breaks integrations with general AI agents/LLMs trying to interface with your API, as they interpret the exported script logic literally.

  • Are there immediate plans to fix this script-export schema so it accurately reflects true execution parameters?

  • If not, can you provide the documentation or mapping rules for these inverted parameters so I can programmatically compensate for this error?

I look forward to your direct, technical response on these matters—particularly regarding the billing structure and the recovery of my backtest logs.

Regards,
Ronnie

Hi Ronnie,

  1. We introduced recurring billing 3 weeks ago through Paypal. When you bought the mini plan, we only had one time payments, which required manual extension or having enough funds in the Gainium wallet + Auto renew enabled. Now you can subscribe with Paypal and they handle the recurring payment, but as I said this is a recent addition. You should have received several emails about the subscription expiring.

  1. Yes there is a grace period, 7 days if I am not mistaken. And when the plan expires and the account switch to free all bots except the most recent ones that fit within the free plan are disabled. So your last 5 DCA bots could have survived the plan expiry.

  2. This is how backtest have worked ever since they were released, they will be auto-deleted after 30 days unless you mark them “Save permanently”. A backtest contains a lot of data, and users can produce thousands per day. Considering most backtests are just testing with limited value, we can’t afford to save everything in the database for everyone, that’s why the checkbox makes it a deliberate choice. I am afraid those cannot be recovered as we only keep a limited amount of backups, anything deleted more than a few days ago cannot be recovered.

  1. I don’t think “frequently” is the reality, there is one documented case concerning MA crossovers where the export is truly inverted, and as far as I know that’s the only case. The details were explained by Maksym in the relevant post. I will look into it. Let me know if you are referring to something else or there are other cases I don’t know about.