Guardian Portal

Privacy policy

Last updated November 17, 2026

Guardian Portal is the staff app of Guardian Community (Guardian Outreach Ministries Inc.). It is for our employees and contractors, who sign in with an account the organization issues. This policy explains what the Portal collects, why, who can see it, and the choices you have. It covers the Portal on the web and in the iPhone and Android apps. Our public website has its own policy. Everything here is processed for employment purposes: you are staff, and these are your work records.

What we collect

How we use it

To run the organization: scheduling and staffing, paying you and reimbursing mileage and expenses, confirming attendance at courses and events, shipping you kits and gear, reaching you or your emergency contact, team communication, training, and resolving disputes about any of these. We do not sell your information, and we do not use it for advertising.

Who can see it

Colleagues see your name, photo and role, and the messages you post where they can read them. On the Tracker's leaderboards, other staff see the results of your Guardian Days (the money raised, golfers, groups and time live), the course and start time of a day you work in their area that day, your badges and points, and the day battles you take part in (who against, what counted, the scores and the result, and your record against that person). When a battle you are in starts or ends, the people working near you that day get a notification. If you are a director or a specialist, your photo, first name and market can also appear on our public careers pages, where people applying to join us see who leads and works in an area. Your ID badge and business card, which are made from your photo, name, role and league, can be seen and downloaded by you, by your director and by the administrators who manage accounts. An administrator can replace your badge, or upload a different photo of you for your badge and business card to be made from, and you are told when that happens. Your own profile photo is not changed by that. An administrator can also set the work email address your business card prints. The administrators who manage accounts can also see whether you use the Portal app, the kind of phone you have used the Portal on in the last 90 days and the last day you did (iPhone or Android, worked out from the type of device your sign-ins and your agreements to the Terms of Use report), each phone or tablet's app version and the date it started using the app, and how many notifications of which kinds were sent to you in the last week or are waiting to be sent, never what they said. Your birthday (the month and day, never the year or your age) is shown in the Hub to your director and those above them, and to the administrators who manage accounts; an administrator also sees your full date of birth on your account record. Colleagues on your own level do not see it. Your director or manager sees your schedule, hours, location stamps and work records in the normal course of scheduling and approvals. In Command Center's weekly director report, your director, the person they report to and leadership also see the post event gross of the events you worked in the last four weeks (what they raised after contest payouts, crew pay and merch at cost), a figure your pay is part of. If you are a director, your own weekly report there, with its post event gross and grade, is seen by you, the person you report to and leadership. The people who process payroll and reimbursements see what they need for that. Access is limited by role, and pay and HR records are sealed to the few people who handle them. While you are being hired and onboarded, the recruiting team and your director see how far along you are, including your training progress and your score on any quiz you have not passed yet. The date of birth and street address you give on the background check authorization are seen only by the central recruiting team and senior leadership, not by your director. A background check report is seen only by that same group. Your director sees whether the check is pending, cleared or not cleared, and nothing from the report. On the map used to plan hiring, the central recruiting team and senior leadership can see the area you live in, and so can your director and those above them, for the people in their own leagues only: it is placed at the middle of your home ZIP code, never at your street address. The map point of your home address that measures your mileage is seen by no one: the full route of a drive, which starts and ends there, is shown only to you, and what your director, payroll and leadership see of a drive is its miles and the stretch between its first and last course. If you are a director, leadership and the person you report to also see your working day as it happens, on Command Center's Field tab and on your person file there: whether you are checked in at a course and which one, the Guardian Day or interview session you are running, the course stops of a drive in progress (never where it started or ended), your planned stops, and where your latest course check-in or Guardian Day was. Your person file there also adds up your course check-ins, their outcomes and your drives' miles over time and compares them with the average director (never a drive's route or where it started or ended). Nothing new is recorded for this; it shows what your check-ins, drives and events already record. A visit added on your word is shown as added on your word to the people who can see that course or donor, and to leadership in Command Center's Field area. Who a Training visit was training is seen by the people who can see that course.

Partnership development records, and the outside contacts kept with them, are seen only by the people given access to that area and by the board.

A report about a workplace issue is seen only by the people who handle HR and by the board. A report that names someone who handles HR goes to the board only. Your director, your colleagues and the person named do not see it. If you ask for your name to be kept off a report, the people who read it are not shown who filed it; your name stays attached only so that you can check that report's status yourself. You can see your own reports and their status, not the notes kept on them. Files attached to a report are kept with it and can be opened only by the same people who can read the report; each time one is opened is recorded.

If someone reports a message or a person in the Guardian Hub, the reported messages and what the reporter wrote are reviewed first by an automated system and, when it cannot decide, by the Hub's moderators. The moderators see who sent the report; the person reported does not. A message removed for breaking the rules is kept with the report so that a moderator can restore it. If you block someone, they are not told, and their messages still reach you, hidden.

Notes on your file are read by the central recruiting team, by your director and the managers above your director, and, while you are an applicant, by the staff who run your interview. They are working notes for the people who manage you, and the Portal does not show them to you. Confidential HR matters are not kept in these notes.

Confidential HR notes and documents on your file are seen only by the people who handle HR and by the board, never by your director or your colleagues, and the Portal does not show them to you. Each time that HR file or one of its documents is opened is recorded.

How far you are through an interview's opening video is seen by the people running that interview and by the central recruiting team. It is used to let you into the interview when the video ends, and for nothing else.

A director's interview times are seen by the applicants who can book them and by the central recruiting team. The reason a director gives for not hosting an interview is seen by the central recruiting team and by the director they ask to take it. An interview that nobody hosted is seen by the central recruiting team, and the vice presidents and that director's senior regional director are told about it.

The record of your leaving is seen by the central recruiting team. Your director can start it, with your final day and the reason, and is told your final day, so that the events you were booked on can be covered. The people who run payroll see your final day beside your last pay, so that it can be paid on time; they do not see the reason you left.

If you ask us to confirm your employment, for example to a landlord or a lender, we can make a verification form with your name, address, hire date, your last day if you have left, a final day already on your file, your rate of pay and your average hours (or coaching sessions) a week, for you or the person handling it to send to whoever you name. It is made only when your request comes with your signed authorization, it never says why someone left, and each one is recorded on your file with who made it and who it was for. For specialists and coaches it is made by the person who handles HR or by the board; for everyone else, only by two members of senior leadership.

The record of the events you worked is also used to estimate how long people stay and how likely it is that a person stops working in the next 30 days. The estimate is made from four things: how long you have been here, how many days you worked in the last 30, how long since you last worked, and whether you are a director. It is seen by the central recruiting team and the Portal's administrators, and is used to plan how many people to hire. Your director and your colleagues do not see it, the Portal does not show it to you, and nothing about your pay goes into it or comes out of it. Directors see only totals for their own leagues, such as how many people are working, how many could leave and how long people stay, never a named person's estimate.

Service providers

The Portal runs on service providers that store or carry data on our behalf and are bound to use it only for that: hosting and database services, the notification services of your phone's platform and of your web browser, text-message and email delivery, voice and video calling, sign-in, payroll and accounting, card payment processing (staff who take card payments at events are added to our team there by name, email and phone number), background screening, bank data aggregation (which carries the organization's own bank and card transactions to the Portal), an artificial-intelligence service (the @Guardian assistant, and the automated review of messages reported in the Hub), maps and address lookup (which receive a location or an address in order to return a map, an address or a driving distance), and operational logging. We also share information when the law requires it.

Once a day the Portal checks our payroll system's staff list to see whether you have been set up there, and whether you have been closed out after you leave. From that check it keeps only that system's record number for you and the dates. It changes nothing in the payroll system.

Location is never sold, and never shared with advertisers, analytics providers or data brokers. It reaches only the providers that store it for us, as part of the work record it belongs to, and the mapping service that turns it into an address or a driving distance.

Your choices

How long we keep it

A location stamp is kept with the payroll or event record it supports, for as long as we must keep that record, and it is deleted when that record is deleted. Location is never kept as a separate trail of its own. Hours, pay, mileage, deposits and expense receipts follow the same rule. The map point of your home address is replaced when you change your address and deleted when your account is deleted. Profile details and messages are kept while you work with Guardian and as long afterwards as the law requires, then deleted or anonymized.

Asking for your data, or its deletion. You can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete it, by writing to admin@guardiancommunity.org. We will tell you what we can and cannot delete — some employment records we are required to keep.

Security

Data travels encrypted, access is controlled by role and every access to sensitive records is logged. Sign-in supports passkeys and a Guardian Google account. No system is perfectly secure; tell us at once if you believe your account has been used by someone else.

Children

The Portal is for Guardian Community staff. It is not directed at children.

California

If you work for Guardian in California, the California notice in your Terms of Use applies to the information described here.

Changes and questions

When this policy changes we update the date above and tell you in the Portal. Questions: admin@guardiancommunity.org.

Sign in · Guardian Community, guardiancommunity.org