<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: 10 Tips for Using Facebook in Ministry</title>
	<atom:link href="http://ministrycom.org/2009/02/10-tips-for-using-facebook-in-ministry/feed/" rel="self" type="application/rss+xml" />
	<link>http://ministrycom.org/2009/02/10-tips-for-using-facebook-in-ministry/</link>
	<description>National organization to support ministry communications professionals</description>
	<lastBuildDate>Thu, 14 Jan 2010 14:45:02 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Carla</title>
		<link>http://ministrycom.org/2009/02/10-tips-for-using-facebook-in-ministry/comment-page-1/#comment-310</link>
		<dc:creator>Carla</dc:creator>
		<pubDate>Tue, 17 Feb 2009 18:39:06 +0000</pubDate>
		<guid isPermaLink="false">http://ministrycom.org/?p=224#comment-310</guid>
		<description>We had a big wake-up call when we realized how much information could be obtained. 

Scenario:
You have a youth page (run by the Church) and a lot of the youth in your area sign up as friends.
You have your events posted.
A child posts that they are looking for a ride to the next event and they live in such and such an area.

People reading this group now have 
1. approximate age and grade of the child
2. child&#039;s first and last name
3. where they are going to be at what time
4. approximate area they live

That is without them posting any further information on their profile. If their profile is public then all bets are off. 

I have often wondered how much liability that organizations such as churches hold in situations such as this. Our answer here has been to lock down the interaction portions, as we really can&#039;t control what the kids say or how they restrict access to their profiles. Of course, unscrupulous people can always pose as a child and gain access that way, but we can say we have taken reasonable precautions.

I would be interested to know if anyone else has had a legal/liability opinion on any of this type of online stuff.</description>
		<content:encoded><![CDATA[<p>We had a big wake-up call when we realized how much information could be obtained. </p>
<p>Scenario:<br />
You have a youth page (run by the Church) and a lot of the youth in your area sign up as friends.<br />
You have your events posted.<br />
A child posts that they are looking for a ride to the next event and they live in such and such an area.</p>
<p>People reading this group now have<br />
1. approximate age and grade of the child<br />
2. child&#8217;s first and last name<br />
3. where they are going to be at what time<br />
4. approximate area they live</p>
<p>That is without them posting any further information on their profile. If their profile is public then all bets are off. </p>
<p>I have often wondered how much liability that organizations such as churches hold in situations such as this. Our answer here has been to lock down the interaction portions, as we really can&#8217;t control what the kids say or how they restrict access to their profiles. Of course, unscrupulous people can always pose as a child and gain access that way, but we can say we have taken reasonable precautions.</p>
<p>I would be interested to know if anyone else has had a legal/liability opinion on any of this type of online stuff.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: tsanders</title>
		<link>http://ministrycom.org/2009/02/10-tips-for-using-facebook-in-ministry/comment-page-1/#comment-309</link>
		<dc:creator>tsanders</dc:creator>
		<pubDate>Tue, 17 Feb 2009 16:14:48 +0000</pubDate>
		<guid isPermaLink="false">http://ministrycom.org/?p=224#comment-309</guid>
		<description>Good comments. The idea is that &quot;staff&quot; should have public profiles, not students. Granted that can cause some bleed-over of data from the student posts.</description>
		<content:encoded><![CDATA[<p>Good comments. The idea is that &#8220;staff&#8221; should have public profiles, not students. Granted that can cause some bleed-over of data from the student posts.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carla</title>
		<link>http://ministrycom.org/2009/02/10-tips-for-using-facebook-in-ministry/comment-page-1/#comment-308</link>
		<dc:creator>Carla</dc:creator>
		<pubDate>Tue, 17 Feb 2009 16:05:06 +0000</pubDate>
		<guid isPermaLink="false">http://ministrycom.org/?p=224#comment-308</guid>
		<description>Just a thought on tip #1 - make your profile public.  I would caution churches on how much information they make public when it comes to youth group profiles. Kids posting and saying that yes, they will be at such and such an event at such and such a time etc. is leaving them vulnerable if the profile is open to anyone.  We keep certain elements public so that people can get a sense or a feel for what is going on, but then they must become friends to see the exchanges among the kids.</description>
		<content:encoded><![CDATA[<p>Just a thought on tip #1 &#8211; make your profile public.  I would caution churches on how much information they make public when it comes to youth group profiles. Kids posting and saying that yes, they will be at such and such an event at such and such a time etc. is leaving them vulnerable if the profile is open to anyone.  We keep certain elements public so that people can get a sense or a feel for what is going on, but then they must become friends to see the exchanges among the kids.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
