Skip to main content

Sign-in and privacy on social feed pages

Your attendees identify themselves before they can post, and what that means for their data.

Written by Cyril Fluck

This applies to Social Feed, Announcements and Crowd Pics pages — the same page type with different settings.

Your attendees sign in before they post

Anyone can read a social feed page without signing in. The first time somebody tries to post, comment or like, they are asked to sign up or sign in with their email address.

This is not something you configure. It applies to every social feed page.

Why it works that way

It means posts have a real author, so people can see who wrote what. It also lets Yapp notify somebody when their post gets a reply, and lets them go back and edit or delete their own posts later.

What happens to their email address

Yapp does not email your attendees marketing, and does not share their contact details with anyone — including you. The address identifies the author of a post and nothing else.

This is worth knowing if an attendee asks you about it, or if your organisation has to answer data questions before running an event. The detail is in the Privacy Policy and the Data Processing Agreement.

What your attendees see

Their side of this is explained in signing in to post, which you are welcome to send them.

Removing somebody from your app

If a person is causing problems, you can revoke their access. See Social Feed moderation.

Did this answer your question?