The only way to avoid Grammarly using your data for AI is to pay for 500 accounts - eviltoast

Source: https://front-end.social/@fox/110846484782705013

Text in the screenshot from Grammarly says:

We develop data sets to train our algorithms so that we can improve the services we provide to customers like you. We have devoted significant time and resources to developing methods to ensure that these data sets are anonymized and de-identified.

To develop these data sets, we sample snippets of text at random, disassociate them from a user’s account, and then use a variety of different methods to strip the text of identifying information (such as identifiers, contact details, addresses, etc.). Only then do we use the snippets to train our algorithms-and the original text is deleted. In other words, we don’t store any text in a manner that can be associated with your account or used to identify you or anyone else.

We currently offer a feature that permits customers to opt out of this use for Grammarly Business teams of 500 users or more. Please let me know if you might be interested in a license of this size, and I’II forward your request to the corresponding team.

  • sugar_in_your_tea@sh.itjust.works
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    1 year ago

    Yup, and that’s a large part of why I don’t use larger SM. Yeah, Meta, Twitter/X, Microsoft, Google, etc can scrape lemmy, but that’s unlikely to be a huge source of info. But if they scrape, they scrape, and I guess I’m okay with that.

    My larger concern is with privacy. I try to mitigate the privacy concerns by recreating my SM accounts every year or two, so that way at least I won’t likely be doxxed.

    So on the side, I’m looking into ways of building more robust SM. I’m interested in fully decentralized systems, which can optionally be encrypted and limited to a few. ActivityPub gets close, but it still relies on public servers to store content, and many services aren’t encrypted. I’m more interested in p2p systems like IPFS, and I think a reasonably intuitive system can be built in that way. In fact, I’m planning on building a lemmy-compatible instance that uses Iroh as the backend storage and connection mechanism once Iroh gets to a usable state.

    But I’m not exactly a zealot here. I didn’t switch to lemmy until Reddit announced its third party API pricing change (I switched before my app of choice shut down), because I value convenience. Lemmy is now big enough for me, so I’m looking into the next step.