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
- Your profile. The details you give us: name, email, phone, home and shipping address, birthday, emergency contact, shirt size, photo, and documents you sign in the Portal.
- What you gave us when you applied. If you were hired through the Portal, your application answers and interview record stay with your file. If your application asks for an audition, the video or audio recording you make or upload is kept with your file too. On the background check authorization you sign before your offer, we ask for your full legal name, date of birth and home address. They are used to run that check and to start your Form I-9, so you are not asked for them twice. After your offer we run a basic screening. If we then order a full background check, the screening company emails you its own form and collects your details directly. Its report, and the form you signed with it, are kept with your file. If we have no mobile number for you, your application page asks for one and texts it a code to confirm it is yours, or you can choose email only. If the number you confirm is already on an earlier application of yours under the same name, the two applications are joined into one.
- If you applied to be a director. The director application asks for your name, email, mobile, the market you would lead and where you live, whether you agree with our statement of faith, your background and experience, and when you could start; later steps ask for a résumé or a LinkedIn link if you add one. Your name, email, mobile and home address are kept from the moment you press Continue on the first question, with the area you then pick, even if you do not finish the application, so we can reach you if a place opens up. When you sign the confidentiality agreement, the background check authorization and the offer letter, we keep a record of each signature: the exact version of the document, the name you typed, when you signed, and the network address and browser you signed from. We also keep which parts of the second-round overview you acknowledged, and the time of each code you confirm before you sign. These stay with your application. Your application, including your answer about our statement of faith, is seen only by the recruiting team and the administrators, not by directors.
- Your work records. Schedules, shifts, hours, pay, mileage (recorded by the mileage log, or the miles and the places you drove between that you or payroll enter by hand), deposits, the expenses you claim with the receipt photos you add (you see them, and so do the people who process your payroll: director payroll for a director’s check, and for executive and misc checks, the board; managers who can see a director’s pay also see the amounts and descriptions; a receipt photo is redrawn on your device before it is uploaded, so any location your camera stored in it is not kept), if you work in California, the paid sick leave your director records for you (the day and hours, never the reason: seen on your check, and by your director and the people who can see your pay), and the event and course records, photos and notes your work creates. A drive in the mileage log starts and ends at the home address on your profile: its miles are the road route from your home, through the courses you check in at during the drive, and back home. To measure it, a mapping service turns your home address into a point on the map; we keep that point with your account, only the system that measures the miles reads it, and we work it out again when you change your address. Your phone's location is not recorded when you start or stop a drive. A course visit records when you check in on arriving and when you tap that you are leaving, so it shows how long you were at the course; leaving records the time only, not your location. A visit to a store or business for donor networking records the same arriving and leaving times, on that business's donor record. A visit you forgot to check in at can be added afterwards from the end of a drive, on your word: it keeps the arriving and leaving times you give, is marked as added on your word, records no location, and its stop on the drive is the course's own map point. A Training visit records which specialist you were training.
- Gifts for a staff member's ministry. When someone gives to Guardian with a preference for a staff member's ministry, the board records the giver's name, the date, the amount, how it came in (and a check number), and the giver's email address only if they give one, which is used to email them Guardian's receipt. The gifts and what is paid out of them on each of the staff member's checks are seen by the board and by that staff member, who sees the givers' names and amounts but never their email addresses.
- Receipts for donors at events. When someone who gives at a golf event asks for a receipt, the Tracker records the email address or mobile number they give, with the amount, whether it was cash or card, the event and who took it, and uses it only to send them Guardian's receipt by email or text (a text links to the receipt on its own page, which shows no name or address). The staff on that day see that a receipt was sent, with the address partly hidden; the full address is kept with the receipt for our records.
- Your training. Which lessons you have finished and when, and your quiz results.
- Messages. What you post in the Guardian Hub: team chat, direct messages, announcements, kudos, and the tickets and feedback you file. If you tell us you can't use the Portal app, what you write, the kind of phone you have (iPhone or Android, from your browser) and the app and page you sent it from are kept with your account and emailed to our support team. In an interview room, the chat — including links and files you share there — is kept with that interview's record. When you ask the @Guardian assistant a question, what you ask is sent to it along with which app and kind of screen you were on (never which record), so that it can answer from where you are. If you use the microphone button in a Hub message box, your browser turns what you say into text with its own speech service and puts the words in the box for you to check; we receive only the text, and only if you send it. If you record an audio message in the Hub (+ beside the message box, then Audio message), the microphone records only from that tap until you stop, delete or send it (at most 5 minutes), and nothing leaves your device unless you send it. A voice message you send is stored with your messages and kept like the pictures you post there; the people in that conversation can play it, and so can the Hub's moderators if it is reported to them. We also note which voice messages you have played, so one you haven't played is marked on all your devices; that note is seen only by you and is deleted with the message or your account. While a voice message plays in the Android app, your phone shows a notification and lock-screen media controls with "Audio message" and the sender's name, until it ends, is closed, or stays paused for 10 minutes. In a Hub call or an interview room, your camera and microphone are used only while you have them turned on, to send your picture and voice live to the others in the call; calls are not recorded. In an interview room you can also choose to use your phone for the sound: we call the mobile number on your Guardian file from our phone line (the interviewer can ask us to call yours), and nothing is connected until you press 1, so a voicemail never hears the interview; or you call our line and enter the code shown on your screen. That call's sound reaches the room through our phone and video-call service providers, like the rest of the call, and we keep only when the phone call was placed, answered and ended, never the sound and never the number you called from. If someone enters a wrong code, we keep a scrambled stand-in for the calling number for one hour, only to stop codes being guessed. While you are muted, your device checks on its own whether you are talking, only to remind you that you are muted; that sound never leaves your device. When you call someone one-on-one in the Hub, or someone calls you, we keep a record of the call with both your accounts: who called whom, whether it was a voice or a video call, when it rang, whether it was answered, declined, missed or cancelled, and when it ended (so how long it lasted) — never the sound or the picture. A call that could not ring is recorded the same way: when the person was already in a call, had calls turned off, or was off work by their schedule. The record also notes which open Portal page answered, when each of you was last seen in the call (so a call nobody is in any more is ended), and which of your phones rang. It is kept like your messages (see How long we keep it below) and is deleted with either person's account. Each call also leaves one line in your direct messages with that person (for example "Voice call · 2:14" or "Missed voice call"), kept like your other messages; a call to someone who has calls turned off leaves none. A call to you rings on the Portal pages you have open and, if you have the Portal app, on your phone as a notification (the Android app rings like a phone call and shows the caller's name and profile photo, also on a locked screen; the photo comes as a link that stops working after 15 minutes); a call you miss also sends you a notification, like a direct message. On a computer, if you turn on "Notify me when no Portal tab is open" there (it is off until you turn it on, and is set separately in each web browser), we keep a push address for that computer's web browser, so the browser can show your Hub messages (who wrote, and the message) and call alerts (who is calling, with their photo) even when no Portal tab is open; each goes through your browser's push service, encrypted so that only your browser can read it. It is never used in a phone's web browser: on a phone, notifications come from the Portal app. The address is used only while you are signed in on that computer: it is deleted when you sign out there or turn the setting off, and once that sign-in ends any other way (signing out of another Guardian app, or the sign-in running out) it is no longer used and is deleted the next time a message or call would have reached it. We keep at most ten such addresses for you, and drop one that no Portal page on that computer has confirmed in 30 days. If you have blocked someone, their calls never reach you and leave nothing in your messages. You can turn "Voice and video calls" off on your Notifications page; then nobody can call you, and a caller is told you have calls turned off.
- Photos and videos you share at an event. Photos and short videos (with sound, up to 3 minutes) that you choose to share in an event's area, such as the directors' retreat page, with an optional caption, and the comments and emoji reactions people add to them. They are stored privately, and only that event's attendees and our administrators can see them. The person who shared a photo or video, or an administrator, can delete it. Location information stored in a photo or video is removed before it is uploaded.
- Notifications and work schedules. If you allow notifications, a token that identifies your device so we can deliver them, and the notification preferences you set. On an iPhone, the Portal app also gives us a second token that is used only for calls to you; it is kept with the first and deleted when you sign out there. The work schedules you make on your Notifications page: each one's name, days and hours, and where it is used. If your phone notifications follow one, a notification that comes in outside it is not sent, except the events you choose to let through and a test notification you send yourself; when it next starts you get one notification that says how many came in. Calls to you follow that same work schedule: outside it a call does not ring, the caller is told you are off work, and you find a missed call in your messages. A work schedule is kept until you delete it. If you turn on Away auto-reply in Hub settings, someone who messages you, replies to you or @mentions you in the Hub while you are outside the work schedule you picked is told that you are off, when you are back, and that time on your own clock; their Hub is also sent your time zone, to work that time out. Each person is told once per time off. Your schedule's days and hours are not shown. If the Android app shows you the tip about messages on your lock screen, we keep, with your account, when it first appeared and when you put it away. If you answer whether a test notification showed on your lock screen (Account → Notifications → "Can you see text messages on your locked screen?", on any device), we keep your answer and when you gave it. To pick the steps for your phone, that page reads your phone's maker and Android version from what your app or browser sends each time you open it, and keeps neither. On Android, a Hub message's notification shows who sent it, with their name and profile photo: the notification carries a link to that photo that stops working after 15 minutes, and your phone keeps a shortcut to each conversation, with the sender's name and photo, after the notification is gone, until you sign out of the app. Your recent conversations also show, with those names and photos, when you press and hold the app's icon; if you drag one to your home screen, signing out renames it "Portal" and turns it off.
- Using the Portal app. When you use the Portal app on your phone, whether or not you allow notifications, we note that you did, at most once a day: whether it is the iPhone or the Android app, its version, and when you first and last used it. It is kept while you have an account. We use it only to know whether to offer you the app when you use the Portal in your phone's web browser; if you tell us there that the app does not work for you, we treat you as not having it until you next use it.
- Your Action Center. Which items in your Action Center you have marked as read, and which you have said do not apply to you, with the reason you picked and any line you added. You can see these and so can the administrators who manage accounts. If a colleague assigned the task to you, they are told that you said it does not apply, and why. You can put an item back at any time. If you take an item your role shares (“I'll take it”), the others it was sent to see your first name as its owner.
- Your time zone. Whether or not you allow notifications, the Portal keeps the time zone the Portal app on your phone is set to, and the time zone a web browser last reported (on a phone or a computer), each read when you open the Portal or come back to it, with when it was reported; only the most recent report of each is kept. Your work schedules follow your phone app's time zone first, then the web browser's, so they stay right when you travel. Until either has reported one, a time zone you choose on your Notifications page stands in; you can also turn Automatic off there and set one time zone yourself, which is then used whatever is reported. A chosen time zone is kept with who chose it and when. We never work out your time zone from your network address.
- If you are a moderator on call, the other moderators can see your work schedules, choose which of them your moderator texts follow (or none), and see the time zone they are read in and whether you are inside them now. They cannot make or change your schedules.
- Precise location — only while you are using the app for work. Your precise, GPS-level location is recorded when you clock in or out; when you start an event and then, while that event is running and you are using the app, at most once a minute; and when you check in at a course, together with your distance from it (during a drive, that check-in is also a stop on the drive). During a drive, checking in at a business on a donor visit records your location only as a stop on the drive, and only when you are within 25 miles of the business; it is not kept on the visit. The app asks for location only while you are using it — never the “always” permission — and your phone's own permission prompt is what grants it. We never record location continuously, on a timer, in the background, or with the app closed. You consent to this when you agree to the Portal's Terms of Use, and you can turn location off for the app in your phone settings at any time.
- Maps you look at. A few screens ask your device for your position purely to draw a map around you — for example a course map. Your phone may show its location indicator while that happens. Nothing from those screens is stored: we keep only the records described above.
- A course's own location. When you add a course, or add an address to one, you search for it by name or address and pick the right place from a mapping service's suggestions. That place's address and map pin are saved on the course's record (which shows who added the course), or you can type the address instead. Your own position is not used for this.
- The organization's own bank and card records. The finance team connects Guardian's own bank and credit-card accounts so their transactions arrive in the Portal for bookkeeping: the date, the amount, the bank's description of each line (which can name the person or business paid) and the merchant's name. These are the organization's accounts only; the Portal never connects an individual's personal bank or card account. When a Zelle payment to the organization names a staff member, as its sender or in its memo, the Portal matches it to that person's event-cash deposits: a deposit they filed for the same amount is marked as received, and a Zelle for exactly what they owe is recorded as their deposit. The people who manage cash deposits see each Zelle's date, amount, sender and memo; your own deposit record shows only that it came from the bank.
- Technical records. Sign-in events, the type of device and browser you use, network address, and error reports when something breaks. During a video call, how much data your device received, how many cameras it was showing and at what picture size, kept in our technical logs so we can see what calls use. During a call we also note whether your microphone was on, muted or off, how much sound your device sent and how much it received from each person on the call (never the sound itself), the call's volume settings on your device, whether your browser was holding the call's sound back, and any error your device gave when the call tried to use its camera or microphone. We also note how well your connection was carrying the call: its delay, how much of what you sent or received was lost or arrived unevenly, how fast your device could send, the kind of route the call took (never your network address), the size and frame rate your camera was sending, and the connection grade the call service gave you and each person on the call. During a call we also note whether your device kept its screen on for the call, and when the call's page was hidden, shown, or paused by your device. On the recruiting team's Messages page, the last time you had it open, so you aren't texted about a question you are already looking at. Only that one latest time is kept.
- Reports about workplace issues. If you file a report about a workplace issue, what you wrote, when you say it happened, who you named, any files you attach to it as evidence, and whether you asked for your name to be kept off it. If someone files a report that names you, that report, its files and the notes kept on it.
- Notes on your file. The recruiting team and your director can keep short working notes on your file, for example a follow-up on your paperwork or your schedule. A note records who wrote it, when, and who it was handed to.
- HR records on your file. The people who handle HR can keep confidential notes and documents on your file, for example about a workplace accommodation or a disciplinary matter. These can include audio and video files.
- Your interview's opening video. If your interview begins with a video, we record when you started it, how much of it you have watched, and when you finished, so that your interviewer knows when you are ready to come in.
- The interviews a director hosts. If you are a director who hosts interviews, we record the two weekly times you pick and the clock they are on. If you say you can't host one, we record the reason you choose, any note you add, who you asked to take it and what they answered. If an interview you were due to host starts with people waiting and nobody hosting, that is recorded too.
- When you leave. If you stop working with us, we record your final day, the reason you left, and who recorded it. Your account is switched off at the end of your final day, and so is your place on our card payment team if you have one.
- Kits and supplies. We record whether you have been issued a Guardian kit and when, and any report that your kit or a piece of it was lost or damaged, with what happened. Your director marks that you have a kit; a kit deposit on your pay record also counts as having one. Your director lists what your kit holds, item by item, and you record what you actually have, in a pop-up in the Portal or on Account → My kit: we keep the counts and any note you give, and every change, with who made it and when. We also keep a record of the supplies our office ordered and shipped to you or to your director for you (what, how many and when, from our suppliers’ order history), and whether you may carry merchandise yet, which follows from the first event you run on your own, or a director’s or the recruiting team’s decision with the reason they give. Your director and the recruiting team see all of this; only the recruiting team sees what the supplies cost. When you leave, you sign for handing your kit back on a page we email you: we keep what you ticked as handed back, the day, the name you typed and a scrambled form of the network address you signed from. If your director asks for a replacement to be shipped to you, it goes to the address on your profile. If you lead a team, we also keep the supply requests you make, a shipping address if you give a different one for a request, and your own count of the supplies you hold.
- Your first Guardian Day. We ask which week you can start. Once you have passed the course, we ask you to confirm which days of your first weekend you can train, and later whether your director has been in touch. Your director, the people they report to and the recruiting team see your answers. If a weekend you could train passes without a first event, your director records why, and we keep that reason with the weather we had on record for those days.
- Partnership development. If you work on grants, donors or partnerships, the Portal keeps the work you record there: the records you own or help with, your tasks, the notes you log, and the emails you send from it, which go out from your own Guardian mailbox and are kept on the record with who they went to. It also keeps details of people outside Guardian at the foundations, companies and other organizations we work with: their names, roles or how we know them, email addresses and phone numbers, notes of our conversations with them and any note the team keeps about them (such as the best time to reach them), the meetings we set with them, and whether a contact has agreed to receive texts from us, with the day and who recorded it.
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
- Notifications — you can tune what the app notifies you about, and whether it makes a sound, under Account → Notifications, and your phone settings control whether the app may notify you at all. On the same page you can make and delete your work schedules, choose one for your phone notifications to follow, and set your time zone yourself. Messages about your pay, schedule and deposits still reach you by other means while you work with Guardian.
- Location — you can turn it off for the app in your phone settings. If you do, no location is recorded for you and the app tells you; your director may need to confirm your hours or presence another way, and mileage cannot be calculated.
- Your profile — you can update it under Account at any time.
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