6.1 With Your Chapter
Chapter officers and members can see your profile information, directory listing, payment status, event attendance, and announcement read status as part of normal operations. Your academic information (major, minor, graduation year, class year) is visible to any authenticated user viewing your profile, including users outside your organization. Your GPA, email, phone number, hometown address, and high school are only visible to members of your own organization.
Cross-chapter features: The Platform supports cross-chapter friend connections, shared events, and shared announcements. When your chapter participates in a cross-chapter feature, your profile information (name, profile photo, and academic info) may be visible to members of other participating chapters. Cross-chapter friend connections also allow users in different organizations to view each other's profiles. Your chapter officers control whether your chapter participates in cross-chapter features.
Saving to contacts: People who can see your contact information in the app can save your name, profile photo, phone number, email, chapter, Instagram, TikTok, X and Snapchat handles, and LinkedIn profile link to their phone's contacts. Once saved, that contact lives on their phone and Greek Life cannot remove it. Turn off "Include me when my chapter saves contacts" in Settings to be left out when a member saves the whole chapter at once. When a member uses Save all, the app checks their existing contacts only on their own phone so no duplicates are made; Greek Life never uploads or stores anyone's contacts.
Class schedule: If you add a class schedule, members of your chapter can see the name, days, and times of each block you save. If you choose Import From Your Calendar, the app reads the calendars on your phone, only on your phone, to find events that repeat every week and show them to you. Only the events you pick are saved to your schedule, as their name, days, times, and start and end dates. Greek Life never uploads or stores the rest of your calendar.
6.2 With Stripe (Payment Processing)
Your name, email, phone number, and payment identifiers are shared with Stripe to process payments. Each chapter operates as an independent merchant of record through Stripe Connect. Stripe's handling of your data is governed by Stripe's Privacy Policy.
6.3 With Amazon Web Services
We use AWS for email delivery, SMS messaging, file storage, and the call servers that connect voice and video calls. Chat media files are encrypted end-to-end when the conversation has E2E encryption enabled. Other uploads are protected by server-side access controls and encryption in transit. SMS message content is retained for up to 4 years for TCPA compliance.
6.4 With Expo, Apple, and Google (Push Notifications)
Except for incoming call alerts (below), push notifications are delivered through Expo's notification service, which routes each notification to your device via Apple Push Notification Service (APNs) on iOS or Firebase Cloud Messaging (FCM, a Google service) on Android. These services receive the push notification token associated with your device and the non-content notification envelope so they can deliver it. Chat message content is never included in push notifications. Apple's handling of APNs data is governed by Apple's Privacy Policy; Google's handling of FCM data is governed by Google's Privacy Policy.
Incoming calls: If your chapter has calls turned on, we send the alert that rings your device for an incoming call directly to Apple (as an APNs VoIP push) on iPhone and directly to Firebase Cloud Messaging on Android, not through Expo. A ring alert carries the caller's name and account ID, the IDs of the chat and of the call, the address of the call server, whether it is a video call, when it was sent and when it stops ringing, and a one-time code, with the address to send it to, that lets your device decline the call. It never carries the audio or video of a call. On Android, we also send a short alert that tells a ringing device to stop once the call is answered or over. A missed call notification is delivered through Expo like other notifications.
6.5 With Mapbox (Geocoding)
Address search queries for event location setup are sent to Mapbox. No identity or account information is shared.
6.6 With Giphy (GIF Search)
GIF search queries are sent directly from your device to Giphy. Device-level information (such as IP address) may be transmitted as part of these requests. Giphy's handling of this data is governed by Giphy's Privacy Policy.
6.7 With Google (Maps)
The mobile app uses Google Maps to display event locations. Device-level information may be transmitted to Google when you interact with maps. No account identifiers are shared. Google's handling of this data is governed by Google's Privacy Policy.
6.8 Third-Party Services Disclaimer
Greek Life does not control and is not responsible for the data practices, security measures, or privacy policies of any third-party service provider, including but not limited to Stripe, Amazon Web Services, Expo, Mapbox, Giphy, OpenFreeMap, Apple, and Google. Once your information is shared with or collected directly by a third-party service, it is governed by that provider's own privacy policy and terms of service. Greek Life disclaims all liability for any loss, unauthorized access, or misuse of your information by any third-party service provider.
6.9 Legal and Safety Disclosures
We may disclose your information if required by law, subpoena, court order, or government request; to protect the safety of any person; to investigate or prevent fraud, security threats, or violations of our Terms of Service; or to protect our legal rights. For end-to-end encrypted messages, we can only provide the encrypted ciphertext, as we do not possess decryption keys. Voice and video calls are not end-to-end encrypted, but we never record them, so we hold no audio or video of any call; the call records described in Section 8 can be disclosed like our other records.
6.10 Sale and Sharing Disclosure
We do not sell your personal information as defined under the CCPA/CPRA. We do not share your personal information for cross-context behavioral advertising.
6.11 Mobile and Text Messaging Opt-In Data
No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. All sharing described in this section excludes text messaging originator opt-in data and consent: your mobile phone number and SMS consent records will not be shared with, sold to, or exchanged with any third party for any purpose other than transmitting the messages you consented to receive through our SMS delivery provider, or as required by law.
6.12 With Google (Google Calendar)
Google Calendar is optional, and we send nothing to it unless you add it. This section is about adding it by signing in to Google: you let Greek Life create one calendar, named after your chapter, in the Google account you pick, and keep it updated with the events in your Events list in the app (from the past year through the next year, leaving out cancelled events). If you instead paste your private calendar link into Google Calendar, Google copies your events from that link, and we get nothing from your Google account.
What we ask Google for: Only permission to create calendars and to manage the calendars Greek Life creates, including seeing, adding, changing, and deleting their events. This does not let us see or change your other calendars or their events, and we do not ask for access to Gmail, your contacts, or any other Google service. Section 6.13 describes a separate, optional feature that lets a chapter officer show one chapter calendar in Greek Life.
What we keep: An encrypted authorization from Google that lets us create calendars and manage the ones Greek Life creates, the ID of the Greek Life calendar in your account, the email address of the Google account it is in (shown in the app so you can see which account is connected), and a list of the events we have added to it so we can keep them up to date.
What we send to Google: For each event we add, its title, date and time, time zone, location, and description, as they appear in the app, plus a reference number so we can update it later. We also set the calendar's name, description, and time zone. When you start signing in, if the email on your Greek Life account is a Gmail address, we pass it to Google's sign-in page so Google can suggest that account. Apart from that, we never send attendee lists, RSVPs, or the email addresses or phone numbers in anyone's Greek Life profile. We add no guests to these events, so Google sends no invitations.
How we use Google data: Only to keep that calendar up to date with your events, as described above, and to keep the connection working and secure. We do not sell it, use it for advertising, or share it with anyone except the service providers that run Greek Life for us (such as Amazon Web Services) or when the law requires. We do not use information received from Google Workspace APIs, including Google Calendar, to develop, improve, or train any artificial intelligence or machine learning model, including generalized or non-personalized models. Apart from totals (such as how many members are connected), Greek Life staff do not look at it unless you ask us to (for example, for support), when it is needed to investigate a bug or abuse, or when the law requires.
In your Google account: Once events are in your Google account, Google's Privacy Policy also covers them. Anyone you share that calendar with can see them, and if you pick a school or work account, your school or employer manages that account. Changes you make to these events in Google Calendar may be replaced the next time we update the calendar.
Removing it: Tap Remove in the app and we delete that calendar from your Google account and cancel Greek Life's access, usually within a few minutes. If Google cannot be reached, or we have paused Google Calendar because of a technical problem, we keep trying, and within about 3 days we delete the stored authorization even if the calendar or our access could not be removed. If the same Google account is, or may be, still connected to Greek Life through another connection (for example, another member uses the same Google account, or you added Google Calendar again), cancelling access would disconnect that connection too, so we delete only our stored copy of the authorization. If you start signing in to Google but do not finish (you close the page, it times out, or the connection cannot be completed), we delete what Google sent us within minutes. In each of these cases Greek Life may still be listed in your Google Account, and a calendar we could not delete stays in Google Calendar. You can delete the calendar in Google Calendar and remove Greek Life on your Google Account's linked apps page at myaccount.google.com/linkedapps (if another connection uses the same Google account, this disconnects it too).
Other ways it ends: The same steps run if you leave or are removed from your chapter (and are not moved straight into another one), change or reset your password, or delete your Greek Life account. If you move to another chapter, the calendar switches to your new chapter's events (when that chapter has calendar sync on). If you delete the calendar in Google Calendar, we stop updating it and end the connection. If you remove Greek Life's access in your Google Account first, we can no longer delete the calendar, so delete it in Google Calendar. The connection then needs to be reconnected (the app asks you to when you can still add Google Calendar), and if it is not reconnected within 90 days, the connection ends.
When it pauses: If you can no longer see chapter events in a calendar (for example, you become an alum, your account is locked out for unpaid dues, or your chapter turns off calendar sync), we take the events out of the calendar but keep the connection, so they come back if that changes. If it has not changed after 90 days, we end the connection as described above.
Calendars we cannot reach: Rarely, a Greek Life calendar can be left in a Google account where we can no longer reach it, for example after a network failure while we create it, or after you reconnect with a different Google account. We cannot see or delete such a calendar, but you can delete it in Google Calendar.
Greek Life's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
6.13 With Google (Linking a Chapter's Google Calendar)
This is a separate, optional feature from Section 6.12. A chapter officer who can manage events can link one Google Calendar to the chapter, so its events appear in the chapter's Events list in Greek Life and stay up to date. The officer either signs in to Google and picks the calendar, or pastes the calendar's private address in iCal format. Either way, Greek Life only reads that calendar: we never add, change, or delete anything in Google Calendar.
What we ask Google for: When an officer links by signing in, we ask Google for read-only permission to see the calendars that Google account can access (Google's calendar.readonly permission). We use it for two things only: once, while the officer is linking, to show them the list of their calendars so they can pick the chapter's calendar; and then, about every 15 minutes, to read the events of the one calendar they picked. We do not read the events of any other calendar, and we do not ask for access to Gmail, contacts, or any other Google service.
What we read: From the list of calendars: each calendar's name, color, whether it is the account's main calendar, and the officer's access level, only to show the list. Another person's main calendar shared with the officer is never listed. From the calendar that was picked: its name and time zone, and for each event its title, description (including a Google Meet link, if any), location, start and end time, whether it repeats, whether it is marked private, whether it was cancelled, and its type (we ask only for regular events, never birthdays or out-of-office entries). Only when the picked calendar is the signed-in person's own main calendar do we also receive who organized each event and whether that person declined it, only to leave out invitations from other people and declined events, and we do not keep that information. We never request the guest list of any event.
What we keep: An encrypted authorization from Google (or, if the calendar was linked by pasting, its encrypted private address), the ID and name of the linked calendar, a shortened form of the Google account's email address (for example, jo***@gmail.com) so officers can see which account is linked, and a one-way fingerprint of that email so we can tell whether another chapter's link uses the same Google account. Each event we bring in becomes an event in the chapter's Events list, with a reference to the Google event so we can keep it up to date. The list of calendars is kept only while the officer is picking.
Who sees it: Imported events are shown to the members of the chapter that the officer chose (for example, the board and active members), like any other chapter event, and members get no notification for each one. Events marked private in Google are shown to the chapter's board only; when the linked Google account can only view the calendar, new private events are not brought in and ones already brought in stay as they are. On a person's own main calendar, private events, invitations from other people, and declined events are left out.
How we use Google data: Only to show the chapter's events in Greek Life and keep them up to date, and to keep the link working and secure. We do not sell it, use it for advertising, or share it with anyone except the chapter members described above, the service providers that run Greek Life for us (such as Amazon Web Services), or when the law requires. We do not use information received from Google Workspace APIs, including Google Calendar, to develop, improve, or train any artificial intelligence or machine learning model, including generalized or non-personalized models. Apart from totals (such as how many chapters have a linked calendar), Greek Life staff do not look at it unless the person who linked the calendar, or the owner of that Google account, asks us to for a specific support request (we keep a record of that request), when it is needed to investigate a bug or abuse, or when the law requires.
Removing it: An officer can unlink the calendar in the app at any time, and chooses whether to keep the events already brought in (they become the chapter's own events and stop updating) or to remove the upcoming ones nobody has answered. When a calendar linked by signing in is unlinked, we always delete the stored authorization within about 3 days (usually within a few minutes), and we also ask Google to cancel Greek Life's access to that Google account when Google can be reached and no other link uses that account. If the same Google account is still linked to another chapter, or is in the middle of linking one, cancelling access would break that link too, so we delete only our stored copy. A pasted private address is deleted as soon as the calendar is unlinked. If someone starts signing in but does not finish, we delete what Google sent us within a few hours. If the officer whose Google account is linked deletes their Greek Life account, or leaves or is removed from the chapter, we delete that authorization and ask the chapter's other officers to sign in again. In these cases, and whenever we could not cancel access, Greek Life may still be listed in that Google Account. You can also remove Greek Life's access at any time on your Google Account's linked apps page at myaccount.google.com/linkedapps; the chapter's events then stop updating until an officer signs in again.
Greek Life's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
6.14 Chapter Ratings and Reviews
This Section 6.14, and the parts of this Privacy Policy about chapter ratings, take effect on November 8, 2026.
If you rate a chapter, the public sees your stars, your written review once it is published (after it passes our automatic checks, or after a person at Greek Life clears a review the checks flag), the label of the group your rating is in ("Member of this chapter," or "Verified at" followed by the school's name), the month you rated, and, for a rating made during a giveaway, the label "Rated during a giveaway." The public never sees your name or your email. Your stars also count in the averages shown for your group.
Except under valid legal process or in an emergency, as described below, we never share who wrote a rating, a review, or a report with the chapter or its officers, a council, a campus office, a national organization, or any other user, and none of them can look it up in Greek Life. Inside Greek Life, only a super administrator can see who wrote a rating, and only to answer a legal request, an emergency, an abuse investigation, a report that a rater is under 18, or your own request for your data. Each time it happens, it is recorded.
We disclose who wrote a rating to anyone outside Greek Life only under valid legal process or in an emergency, as our Legal Requests page explains. Unless the law forbids it or it is an emergency, we email you at least 14 days before we disclose anything about you, at the address we still hold for you if we hold one. For who wrote a rating, a review, or a report, this paragraph replaces the broader grounds in Section 6.9.
If you verify with a school Google or Microsoft account, that company, and your school, which manages the account, may see that you signed in to Greek Life, under their own policies. We send them nothing about your rating.
If you tap "I'm interested" on a chapter that is not on Greek Life, after verifying your school email, we keep only keyed fingerprints of your verified email and of your device for that one chapter, so each person counts once. Nothing links your taps on different chapters, and we never tell the chapter or anyone else who tapped. A chapter can learn only a rounded count (5 or more, 10 or more, or 25 or more) in a message a person at Greek Life sends it.
When a chapter officer replies to a review, the reply shows as a response from the chapter, never with the officer's name. To reply, the officer signs in through a one-time link we email to the address on their Greek Life account (an officer who uses two-step sign-in gets a notice to sign in another way instead, because an email link alone never replaces a second step).
6.15 With OpenFreeMap (Web Maps)
On the web version of Greek Life, maps are drawn from map images that your browser loads directly from OpenFreeMap (tiles.openfreemap.org). Like any website your browser contacts, OpenFreeMap receives your IP address and browser information with these requests. No account identifiers or chapter information are shared. OpenFreeMap's handling of this data is governed by OpenFreeMap's Privacy Policy.