djMot

Renew?

Renew?

Object Desktop was alerting me to some updates to the apps I have installed.  When I opened OD, the updates were noted, but also Object Desktop itself said, "Renew".  So I clicked that button at got to a 404 on the Stardock site saying:

Product Not Found
We're sorry, the product you requested is no longer unavailable.

 

Hmm.  Double negative notwithstanding, what's up with this?

187,878 views 54 replies
Reply #51 Top

Quoting Jafo, reply 50


Quoting RedneckDude,

Interesting, possibly changing my mind. So in other words, one can renew, then turn off auto renewal?



Yes, all Subscription services must have an opt-out system.  Consumer Law demands no less.

The "auto renew" process is simply the easy way for most customers who actually do renew annually...;)

You're my hero!  That is as clear as one could expect!   

+1 Loading…
Reply #52 Top

Quoting RedneckDude, reply 49

Interesting, possibly changing my mind. So in other words, one can renew, then turn off auto renewal?

Quoting Jafo, reply 50

Yes, all Subscription services must have an opt-out system.  Consumer Law demands no less.

The "auto renew" process is simply the easy way for most customers who actually do renew annually...

Yes, how is detailed here:

https://support.stardock.com/space/SHC/1544388616/Stardock+Software+Subscriptions#How-to-cancel-\-pause-a-subscription-auto-payment

 

Sean Drohan
Stardock Product Lifecycle Manager

Reply #53 Top

Quoting sdRohan, reply 39

As noted, its not a 'big' difference, its the only difference

Which makes it a big difference.  The two aren't mutually exclusive. B)

But I get your point, Sean.  Just trying to add a bit of levity.

Quoting Neil, reply 48

I think whilst object desktop would go to auto renew, you are able to set it to do not renew again after renewing it if you wish.

Quoting RedneckDude, reply 49
Interesting, possibly changing my mind. So in other words, one can renew, then turn off auto renewal?

Quoting Jafo, reply 50

Yes, all Subscription services must have an opt-out system.  Consumer Law demands no less.

The "auto renew" process is simply the easy way for most customers who actually do renew annually...;)

As Jafo correctly states, it is required by law.

What isn't required by any law or policy is:

Would the original Classic Desktop subscription still qualify as a Classic Desktop subscription after an opt-in to the auto-renewal, a cancellation of the auto-renewal, and then opting back into a renewal at a later time after the lapse?

To which Sean has answered:

Quoting sdRohan, reply 39

There is no situation that can be posited where a Classic Subscription loses its designation or well-established attributes. 

I tried setting this all out in a real world example earlier in the thread, which is better summarized by this post:

Quoting mclab, reply 23

And it does not directly answer the question by @Narusegawa Naru or the follow-up example I posted, which can essentially be boiled down to the following: 

Will a Classic Subscription always be considered a Classic Subscription, even if it lapses multiple times?  And will the Renew option always been present, even if (again) there are multiple lapse periods during its lifetime of said Classic Subscription?

But a lot of it got lost in the minutae and my wording, so it's nice to see things a bit more simply stated as has been done in this thread and by Sean's post above.

Again, huge shoutout to @sdRohan, @Jafo, @basj0, and @BradSams for all their clarifications in this thread and others.

Reply #54 Top

This URL is now incorrect.  Or rather, it does not have the proper anchor, since the documentation has been changed since it was originally posted.  Clicking this link does not lead to the correct portion of that documentation.

The correct URL is:

https://support.stardock.com/space/SHC/1544388616#How-to-cancel-\-pause-a-subscription-auto-payment

On a different but related note, I think some of the issue or issues have been that the support documentation - especially the "What is an Object Desktop Subscription" document - is attempting to do a lot of clarification in essentially a single thread, which might be where people are getting lost.

Maybe having support documentation JUST for Object Desktop Classic as an entirely separate document, with all the terms and policies spelled out just for Object Desktop Classic, might be a better approach?  Then an entirely separate document for all new purchases starting June 1 with whatever label Stardock wants to call that product, and all the terms and policies spelled out for that in single document as well.  Linking to one document that has explanations for both products might be the confusing part for some.

+1 Loading…