PS -- If that particular question remains a concern for your group, kids names are not required at all and/or your group could easily use just first initials or the like to ID kids. The system is by-and-large for managing parent information, so limiting kid information in that way won't affect your functionality.
Thanks, Tim,
I think the same way you replied. I just wanted an "official" answer I could bring to the board. Thanks so much for this idea! I'll pass it on!
Holly
The site is not https, because there is no generally-recognized-as-problematic data on there. That would be things like social security numbers or credit card numbers or the like, things that lend to identity theft.
That said, it's still very secure. No one can see a thing without a user name and password. And even those users can have their access controlled by you and your coordinators (leaders can see all, average parent can just use own record, etc.). Our servers are behind multiple levels of firewalls at a secure, off-site location that specializes in this type of application.
When computers are involved, I suppose nothing is 100% foolproof. All the data on kids classes and the like are on servers at your school district, too. And the security on the PTO Manager data is better or equivalent to the vast majority of school district's security. It's also exactly the same kind of information that is regularly printed (and then distributed widely) in school directories.
As for the hospital scenario? Can I guarantee you that it couldn't happen? No. But no one could. I'd hope your district has kids-release policies that would defeat your scenario (most do).
Glad to answer more questions, and -- as the father of 4 little ones -- I share your concern about kids' safety. But I don't think the data stored here -- especially with the built-in security the site does have -- leads to that type of problem.
Best,
Tim
PS -- If that particular question remains a concern for your group, kids names are not required at all and/or your group could easily use just first initials or the like to ID kids. The system is by-and-large for managing parent information, so limiting kid information in that way won't affect your functionality.
What about the PTO Manager part? The other board members in our group are concerned that any hacker can get in & find out info about their children. We have entered in children's name & room #s and the argument is that someone can see my name as a parent & then my kids' teachers names & room numbers. Now, they can go to the school & tell the secretary that I am in the hospital & they are here to pick up so & so in mrs. xx room #111. THat made them all very nervous when someone brought that up. In this day & age you can't be too careful, but are we going overboard? I understand we could NOT put in room #s, etc. but that just defeats a HUGE part of using the software. Any ideas?? :confused:
Thanks!
Holly
I'm glad the instructions will be more clear. When I was first previewing the program this threw up a red flag for me because my husband had just been the victim of a phishing scheme. It taught me to be much more cautious, but like Chad said, some people just don't know.
That's a good point. We'll make those instructons more clear. The good news is that -- as Mike said above -- there are no transactions processed anywhere on the site. No credit card transactions or numbers. No transfers. It's not a banking site.
If credit card numbers were stored -- that would be a different story. Those can be used by someone (anyone) to purchase or do harm.
No security encryption and you have the ability to store your account numbers on the site?? Most groups may only put in the last 4 digits but what about the ones that dont?
