Locksmith

Hey there! There’s no need to subscribe to Locksmith to unlock your content. Locksmith can be disabled from the settings page in the app, using the “Disable Locksmith” button.

I can definitely appreciate why finding that your products are still locked when you didn’t expect them to be would be an unpleasant surprise! For this reason we mention specifically in the emails that are automatically sent out, that a subscription doesn’t need to be started, and that customer access to your locked content will be disabled when a trial lapses. We do not hold stores hostage.

​I understand why you might expect Locksmith to automatically disable your locks. The reason we've chosen not to automatically disable all of a store's locks is because some shops may let their trials lapse before subscribing, or they may simply need to update their billing information with Shopify, causing the payment to not be processed.
​
​If that happens, we want to make sure the locks are still in place, since shops rely heavily on us to protect content. We're first and foremost an access control application, and so disabling locks could open up shops to showing content or selling products to folks who shouldn't have access.

Thank you for your feedback. These are important points that we want merchants to be informed about. Again, I know that situation wasn't ideal, to say the least, and I'm sorry for the confusion and issue.

We are now looking into how we can improve messaging in the app to make it clearer that a subscription isn’t needed to disable or uninstall Locksmith, and that a subscription is only required to keep using Locksmith.

All the best!

- Tristan

Hey there! Looking at followup emails, it does sound like you were able to create the Locksmith setup you needed – locking storefronts *is* something Locksmith does well, and it looks like you're all squared away.

To the rest of your note: thanks for letting this know how this went for you. All of our support *is* offered via email, with a turnaround time up to 24 hours, and often much less. (A note to this effect is included in the auto-response we send to all new support messages.)

This works well in most circumstances – but not all, and that's absolutely legitimate, and those stories are important too. It's our intent to be as straightforward as possible about what we do and do not offer, so that you can choose the tool that works best for what you need – whether that's Locksmith, or another tool with a different support structure.

If you do choose to keep using Locksmith, you know where to find us. :) We'll always do our best to help.

Cheers,

-Isaac

❤️ ❤️ Our pricing is Pay What Feels Good – see lightward.com/pricing for details. It sounds like the suggested price you saw *didn't* feel good to you, which is great – per the policy, it just means that this is the part where we talk about what price *does* feel good to you instead. :) If you want to keep using Locksmith, drop us a line at team@uselocksmith.com to talk pricing. That conversation is always open, to everyone, at all times. We work hard to make sure that every dollar that moves here is moved in good faith, and good feeling.

About the uninstall issue you mentioned: Locksmith only ever auto-adds code that it is capable of auto-removing. That's a hard constraint built into the system itself, but it *does* mean that removal needs to happen through the app. (Shopify removes Locksmith's ability to clean up after itself the moment that Locksmith is removed from the apps list.) Locksmith *does* auto-remove its own code if you disable or delete all your locks, or if you disable Locksmith entirely from within the app. But, with the app removed from the apps list, it sounds like you were left in a bit of a bind – to get out of that, start here: https://docs.uselocksmith.com/article/221-removing-locksmith

And, as always, if there are ever issue *during* the trial period, we're an email away. ❤️

I hope this note gets to you; we'll also drop you a line via direct email to make sure you've got what you need. We'll always do our best to help. :)

All the best,

-Isaac

❤️ I feel you; this kind of thing can be unpleasantly surprising. Because Shopify doesn't allow recently-removed apps to go back and clean up their theme code, it's really important to disable Locksmith within the app (or simply delete all of your locks) *before* removing Locksmith from your apps list.

If this is still affecting you, here's the place to start: https://docs.uselocksmith.com/article/221-removing-locksmith

Or, send us an email at team@uselocksmith.com. We're here. :)

For those looking in on this review, it's worth mentioning that we work *hard* to communicate the uninstallation process:

* We send an automatic email to the store owner immediately upon app removal, if we detect that Locksmith's code is still in your theme.
* We include the uninstall requirements in our required user agreement, on the first screen of the app.
* There's a link to our uninstall process at the end of every page within the Locksmith app, and in our immediate auto-response to new inquiries to team@uselocksmith.com.

We're here to help, always, always. :) To the reviewer: thanks for letting us know how this affected you. We haven't heard from you via email, so I'm hopeful that you've been able to get this sorted. Please reach out if there's anything we can do to help you further.

All the best,

-Isaac

❤️ There are two important pieces here, from our end.

First: our pricing policy is "pay what feels good". We work really hard, in many places, to communicate this. The wires were crossed, and that message never came through. If someone's paying for Locksmith, the intent is for it to always be a number that all parties genuinely feel good about. The $99/mo figure, as documented in the "Pricing" section of our app store listing, is a suggestion based on the store's Shopify plan. But it is a suggestion only, and per the policy (lightward.com/pricing), we're always here for that what-price-feels-good conversation.

Second: this situation revealed a bug, in which some suspended Locksmith accounts had their entire storefront frozen instead of *just* the content that had been locked. We send out multiple heads-up-your-trial-is-ending emails, and automatically give a 5-day grace period before suspending accounts – but when accounts *are* suspended, the intent is to *only* suspend access to the content that was locked. We absolutely never intended to lock your entire storefront. That's a huge error, for which I just pushed out a fix. It won't happen again.

To the reviewer, personally: I absolutely understand the frustration of having a service yanked out from under you, and of having to pay an unexpectedly high amount just to restore that service. That kind of situation is absurd; I get it. Please know that this experience is the actual opposite of what we've worked hard to create. ❤️ Thank you for letting us know how this went for you; your experience here matters a ton to me. If you want to keep using Locksmith, we're here, to establish a new price that *does* feel good to you, and also to make sure that the erroneous locking of your storefront *cannot* happen again.

All the very best,

-Isaac

I’m sorry you had to experience this. The issue coming from Locksmith in this case was that the add to cart button, in the featured products area of your home page, was showing as “sold out” until the customer interacted with the variant selector. Your developer removed the Locksmith code from that template, which fixed the problem, but Locksmith automatically added its code again shortly after, and the issue resurfaced.



I totally understand your frustration, and while we did mention that Locksmith auto-installs, we should have brought up the ignore list functionality to prevent that from showing up again. Locksmith has an ignore list on the Settings page, which allows you to specify theme files that Locksmith should leave alone during its install process.



We did see that your slider navigation was not functioning, but it seems that was a side effect of the product object being “nil” in the featured product area, or perhaps something else in that template. Those are generally unrelated, and we're not sure why that happened, since the app is only working with your products and variants.

We’ve been able to duplicate the add to cart button issue on other themes, but not the unresponsive menu. That’s something specific to the theme you’re using, and fixing the add to cart also stopped the navigation menu issue.

I’m glad we were able to get this fixed for you, and that everything is working.

Again, I’m sorry for the frustrating situation. We’re here to help if anything else comes up. 



Best,


Ken