Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Text edit to section "Why do we include the privacy notice" on preview comment page #1866

Open
katska opened this issue Jul 26, 2024 · 2 comments
Labels

Comments

@katska
Copy link

katska commented Jul 26, 2024

On a page such as https://www.planningalerts.org.au/comments/166670/preview

Screenshot 2024-07-26 at 3 35 34 PM

Using "force" twice in close proximity seems a little clunky when I scanned it today, could the second use of the word "force" be replaced with "make"? Or if there's a desire to emphasise we're forcing them, then please say so, it's a different strategy and I'm happy to think of changes to make that really sing! Noting I like the words "assert" and "affirm" relating to standing up for / advocating the commenter's right for their personal information to be kept safe. (in case I come back to this and we like sending the language that way).

Why do we include the privacy notice?

Different planning authorities handle your private information (email address and street address) in all kinds of different ways.

This privacy notice is our attempt to force planning authorities to give you the same privacy protection as provided by Planning Alerts and force them to ask for your active consent if they want to publish or pass on your private information.

@JoannaHill
Copy link

Screen Shot 2024-07-29 at 4 53 19 pm Updating to correct screengrab

@JoannaHill JoannaHill changed the title a bit of refinement please for section "Why do we include the privacy notice" Text edit to section "Why do we include the privacy notice" on preview comment page Jul 29, 2024
@JoannaHill
Copy link

I agree the use of the word 'force' twice in the same sentence may be a little strong. @katska be cool if you make a replacement sentence suggestion here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Post Launch clean up
Development

No branches or pull requests

2 participants