Apple And Google Authentication
Effective date: May 31, 2026
MEAL-4DAT uses authentication to protect user accounts, connect reservations to the right person, prevent duplicate or fraudulent activity, and allow event organizers to manage meal planning accurately.
Sign In With Apple
When a user chooses Sign in with Apple, Apple asks the user to approve sharing account information with MEAL-4DAT. Depending on the user's Apple settings, MEAL-4DAT may receive an Apple user identifier, email address, relay email address, display name, identity token, and authorization code. MEAL-4DAT sends the Apple credential to the backend for verification before creating or updating the user's 4DAT account.
Google Sign-In
When a user chooses Google Sign-In, Google asks the user to approve sharing account information with MEAL-4DAT. MEAL-4DAT may receive a Google user identifier, email address, display name, profile information permitted by the user, and identity token. MEAL-4DAT sends the Google credential to the backend for verification before creating or updating the user's 4DAT account.
4DAT Account Identifier
MEAL-4DAT may create a 4DAT account identifier from provider, device, timestamp, and entropy inputs. This helps avoid exposing raw Apple or Google identifiers directly in normal app records.
Session Storage
After successful login, MEAL-4DAT stores session tokens in protected device storage such as the iOS Keychain. These tokens allow the app to keep the user signed in and refresh the session when permitted.
Logout
When a user signs out, MEAL-4DAT clears the local session and may notify the backend to end or revoke the session. Apple or Google account access remains controlled through the user's Apple ID or Google Account settings.
Authentication URLs
This website provides public URLs that can be used for provider setup, app review, support, and disclosure requirements. OAuth redirect URLs should be configured in the provider console and app backend to match the production domain and app scheme used by MEAL-4DAT.