TideCloak 0.11.9
A minor maintenance release aimed at fixing urgent Stripe billing issues.
Highlights:
- Billing keep-alive
- Subscription cancellation and revival
- Subscription freeze on fault
Cybersecurity Fabric 0.11.9 changes
Billing keep-alive
A new subscription keep-alive mechanism was introduced to guarantee no unnecessary charging occur when subscriber seized to operate. The existing VRK monthly renewal process now acts as a monthly keep-alive test for active TideCloak instances, and is now coupled with Stripe monthly subscription invoicing and billing. Stripe will continue to maintain it's subscription payment as long as the TideCloak service has renewed its VRK beforehand. Note that TideCloak maintains $0 paid subscriptions for its free tier (pseudo-payment). If a TideCloak instance stopped renewing its VRK, Stripe will suspend its subscription for up to 3 months, where the customer can renew at any time. After 3 months, account will go into a cancelled state, requiring the customer to request reactivation of old account. After additional 9 months (12 months from subscription suspension), account will enter its archived state, with all associated keys and information to be taken offline and archived.
Subscription repayment after suspension
Should a suspended TideCloak resumes operations and renew its VRK, Stripe will invoice and collect for all missing months' payments.
Subscription cancellation and revival
After a full year of inactivity (no keep-alive received), the customer's subscription is cancelled with all information is archived offline (by each and every hosting ORK). Should the customer (or anyone like law enforcement) want to revive that account after, a request is to be made to Tide (via info@tide.org) to organize a revival through the offline archived data. That revival will be charged at a premium.
Subscription suspension on fault
Should an automated renewal of license result in errors, related to the VRK or others, the service will be immediately suspended until resolved.