Privacy & Data Handling
A plain-language summary of what information Clergy Connect stores and how it's used.
What we collect
Name, email address, and optional phone number for each clergy account; which parishes someone serves and how far they're willing to travel; recurring Mass/confession times and one-off events (funerals, weddings); and the coverage requests submitted, approved, claimed, or denied over time.
Why we collect it
Solely to coordinate coverage — matching an open Mass or confession slot with nearby clergy who are willing and able to cover it, and keeping the diocese's shared calendar accurate.
Who can see what
Diocesan admins can see every parish, clergy member, and request. A pastor or deacon can see their own information in full, and sees other clergy members' names and schedules only as needed to coordinate coverage — never anyone's login credentials, which no one at the diocese can view; passwords are never stored in readable form.
Where it's stored
Data lives in a Postgres database hosted by Supabase, in the United States. The website itself is hosted by Vercel, and coverage-request emails are sent through Resend. We don't sell, rent, or share this data with any other third party, and there's no advertising or tracking of any kind — the only cookie set is the one that keeps you signed in.
Removing your data
A diocesan admin can remove any account at any time, which deletes that person's login and clergy record. To request removal of your own data, contact your diocese office directly.
This page is a plain-language summary, not a substitute for a legal privacy policy or data processing agreement. If your diocese requires a formal reviewed policy, please contact us before onboarding.