Project Go Hub stores your members’ contact details and giving records. Here is how we protect them.
Everything sent between your device and Project Go is encrypted with HTTPS. Our database runs on DigitalOcean’s managed database service, which also encrypts the stored data and its backups.
Card and bank details never reach our servers. Givers type them into a payment form run by Stripe, which processes the gift.
Each church’s records are kept separate, so no one in another church can see your members. Inside your church, roles decide who can see and change each area, and your admins set what each role can do.
A person who signs up sees nothing until one of your admins approves them. Approve only people you know. If you would rather add every member yourself, you can turn sign-ups off.
Passwords are stored in a form that cannot be turned back into the password, so no one can read them, including us. Repeated wrong passwords lock the account, and resetting a password signs out every device.
Two-step sign-in adds a code from an authenticator app to the password. Any member can turn it on, and your church can require it for everyone who can edit the directory, finances, roles or church settings.
Only the Project Go staff who run Hub can reach the production database. Every connection to it is encrypted and needs the database’s own password.
When something breaks, the app sends us an error report so we can fix it. Names, email addresses, phone numbers, cookies and form contents are removed before the report is sent.
The database is backed up every day, and each backup is kept for seven days. If something goes wrong, we can restore it to any point in those seven days.
Every change runs automated tests before release, and our team checks each release before it goes live.
If you have a security question or think something is wrong, email [email protected].