Hi, co-founder here!

Thanks for the feedback, really appreciated!

Would you consider automatically sending the export as an anti-feature, and if so why? For context, we added this to help with disagreements were one party kick out another party in a dispute. So afterwords they can reach agreement with a common basis.

I'd guess that if your dispute has reached the level of kicking each other collaboration tools, then I would not be the target market either, in the sense that this isn't a common enough use case for me, that it would warrant optimizing for it. A workplace like that is just not very healthy.

Sure, conflicts happen all the time, and I guess it is good to be able to handle that, too. But it feels a bit odd to include this in the marketing material as a common case.

If I was marketing I would try to find a way to draw attention to this feature in a more subtle way.

The thing that you are trying to sell is that "all parties have access to verified decisions at all times", right? Maybe there is a way to word it that does not end up associating "loqbooq" with "disputes and projects falling apart".

While I am at it: I think I understand the technical background of Points 1,2,3,4,5 of "In Case of Dispute", but it's worded very technically. Maybe there is a way of describing the benefits of a (semi-)distributed verified log more high-level and then add an additional section "How it works under the hood".

And of course congratulations on the launch!

Thanks so much! You got some good points, really appreciated! We definitely don't want Loqbooq associated that way and will re-work the content there.

Did you mean to say

"We will let you export your full history and data anytime" (as a company's data)

OR did you mean

"If you are fired from your employer, you get a copy of your data"? yeah that seems weird.

i was thinking about scenario where all parties involved in decision are employees or contractors working on some internal project for a single enterprise company, and decision log is being used to record project decisions.

in that case, enterprise company is the one paying the bill for loqbooq subscription, so enterprise would want to set the policy for accessing data / onboarding / offboarding. they'd want SSO integration for access control, and if SSO integration said "this user no longer has an account; access denied" then the enterprise would want loqbooq to deny access and not email out a copy of internal enterprise data.

basically: if there's a disagreement between one or more parties involved in a project where loqbooq is being used, but only one of the parties is the customer paying loqbooq the monthly subscription, so wouldn't that paying customer want loqbooq do do the thing that is most in their interest?

Enterprise might think through scenarios like:

* "what if one of our contractors or employees foolishly/accidentally dumps customer PII into external loqbooq.app SaaS outside of our datacentres? how do we limit & do damage control over data breach?"

* what if we believe that some of our employees are trying to start up a new business in competition with us, and might try to use our proprietary information to do so? (product roadmaps ; architecture docs ; lists of customers & suppliers ; ...)

In both scenarios they may want a mechanism that gives company administrators a quick and reliable way to terminate user access to loqbooq and limit risk of further information leaks.

Awesome feedback, thank you so much.