Suggested in #664964-19: Add privacy policy link to forms protected via textual analysis by @Diego Herranz:

When a user reads:
"By submitting this form, you accept the Mollom privacy policy."
He might get worried because he doesn't know what Mollow is at all.

Maybe:
"By submitting this form, you accept the Mollom privacy policy (anti-spam and quality monitoring)"

And so, the user gets the idea of the anti-spam service, and doesn't worry that much.

Files: 
CommentFileSizeAuthor
#6 mollom.privacy.png17.2 KBsun
#6 mollom.privacy.patch1.58 KBsun
FAILED: [[SimpleTest]]: [MySQL] 6,893 pass(es), 2 fail(s), and 0 exception(s).
[ View ]

Comments

Issue tags:+user experience

I agree, this needs to be better worded otherwise people may hack the module to remove the link altogether, which would not be good if Mollom needs to display this for legal purposes.

I would suggest mentioning the spam policy first and put Mollom in parentheses with the link being just "privacy policy". Like this:
"By submitting this form, you accept the anti-spam and quality monitoring (Mollom) privacy policy."

Also, would it be possible to legally say "our" vs "the"?

Update: I see that we can disable the policy link in the settings, but it states you are required to inform users another way via the terms of service so I guess the above is still valid. I guess knowing this, it would be nice if there was also a setting to customize the text displayed on the mollom settings page.

Came across this issue as well, as for endusers it's unclear what mollom is.

Workaround : if your site is not in english, you can change the translation of this text, or provide custom text for english as well (cfr. http://drupal.org/node/24593). Didn't test the last option since the sites I'm administering are not in english for endusers.

If you are not using the Locale module it might be simpler to use string overrides in settings.php. I believe there is a comment explaining it in the default.settings.php.

Status:Active» Needs review

Thanks a lot for having this discussion — I think it's badly required to revisit the messaging.

In fact, it was brought to my attention that the Mollom Support staff gets a lot of misdirected support tickets from end-users that mistakenly ended up on mollom.com.

I've the impression that most of you customized that string? Could you share what you ended up with?

Let me try to wordsmith and brainstorm some iterations, starting from #0 and #1:

  1. By submitting this form, you accept the Mollom privacy policy.

    Not clear what "Mollom" is.

  2. By submitting this form, you accept the Mollom privacy policy (anti-spam and quality monitoring).

    Clarification after the fact — parenthesis should (always) be avoided.

  3. By submitting this form, you accept the anti-spam and quality monitoring (Mollom) privacy policy.

    Not sure why Mollom appears in parenthesis — this reads "dubious" and will likely cause even more confusion...?

  4. By submitting this form, you accept the privacy policy of the Mollom spam filter and content moderation service.

    More appropriate, but (way) too long. Also, privacy policy link is too detached from Mollom.

  5. Your form submission will be processed by the Mollom spam filter and content moderation service.

    Do we actually need to state "privacy policy" at all?

  6. By submitting this form, your post will be processed by a content moderation service. The Mollom privacy policy applies.

    Oy — much more accurate + clear?

  7. Your data will be processed by a moderation service; the Mollom privacy policy applies.

    Better? Semicolon--

  8. Your data will be processed by a third-party moderation service. Consult the Mollom privacy policy for details.

    Why not?

What do you think? :)

Issue summary:View changes
StatusFileSize
new1.58 KB
FAILED: [[SimpleTest]]: [MySQL] 6,893 pass(es), 2 fail(s), and 0 exception(s).
[ View ]
new17.2 KB

To continue progress, here's a more concrete patch and screenshot -- what do you think?

Status:Needs review» Needs work

The last submitted patch, 6: mollom.privacy.patch, failed testing.