This policy explains, in plain language, what happens when you use Sign in with Google on Medicare Exit Guide. It applies only to this website and to the demo backend it hosts. Websites that integrate our reusable module publish and operate their own policies.
openid, email and
profile. We access, use and temporarily hold only the basic profile fields contained in the
Google ID token, solely to verify your identity and maintain a session on this site. We do not access
Gmail, Drive, Contacts, Calendar or any other Google service, and we do not transfer Google user data
to anyone except Google (the identity provider) and Cloudflare (the hosting provider).
01 / SCOPE
Who we are
Medicare Exit Guide (“the Site”) is a demonstration and distribution site for a reusable, zero-dependency Google Sign-In module. It is operated by the operator of Medicare Exit Guide.
The Site is not affiliated with, endorsed by, or operated by Google LLC. Google accounts and the Google sign-in experience are provided by Google under its own terms. Questions about this policy can be sent to privacy@medicareexitguide.com.
02 / WHAT IT DOES
What the Site does
The Site loads Google Identity Services (GIS), displays Google’s official sign-in button, and
receives a signed ID token (JWT) after you choose an account. The raw token is sent
once to this Site’s backend endpoint POST /api/auth/google, where its signature,
audience, issuer and expiry are verified against Google’s public keys.
After verification the backend issues its own short-lived HttpOnly session cookie. There is no registration form, no password, no payment and no user database on this Site.
03 / DATA RECEIVED
Information we receive
When you sign in, Google includes the following fields in the ID token:
sub— a stable, site-specific Google account identifier;emailandemail_verified— your email address and its verification status;nameandpicture— your basic profile display name and avatar;iss,aud,iat,exp— token metadata used only for validation.
We never receive your Google password, and we do not request sensitive or restricted scopes. Cloudflare, which hosts the Site, may record standard request metadata (IP address, user agent, timestamp, request path) for security and operations.
04 / PURPOSE
How we use it
The profile fields are used to (a) verify that the sign-in response genuinely came from Google, (b) display your name, email and avatar in the demo interface, (c) maintain the session while the page is open, and (d) detect and prevent abuse of the demo endpoint.
We do not use this information for advertising, profiling, automated decision-making, model training, or sale to data brokers.
05 / LIMITS
What we do not collect
We do not collect passwords, precise location, payment details, contact lists, health information, or the contents of any Google service. We do not set advertising or cross-site tracking cookies. The demonstration backend does not persist your profile into a database; the session is a self-contained signed token held in your browser cookie.
The module’s default configuration is persistence: 'none', so credentials are not
written to localStorage or sessionStorage. A website that integrates the
module may choose different settings — read that website’s own privacy policy.
06 / RETENTION & SECURITY
Storage, retention and security
The ID token is held in server memory only for the duration of verification and is not written
to durable storage. The resulting ga_session cookie is
HttpOnly; Secure; SameSite=Lax; Path=/ and expires after 7 days;
signing out clears it immediately.
All traffic is served over HTTPS. The Site sends a restrictive Content-Security-Policy,
Cross-Origin-Opener-Policy: same-origin-allow-popups and other security headers.
Session tokens are signed with HMAC-SHA256 using a server-side secret that is never shipped to
the browser. Infrastructure logs are retained by Cloudflare under its own policy.
07 / COOKIES & THIRD PARTIES
Cookies and third parties
- This Site:
ga_session— strictly necessary to keep you signed in. - Google: cookies on
accounts.google.comare controlled by Google and are required for the Google account chooser. See the Google Privacy Policy. - Cloudflare: hosting, CDN and optional aggregate traffic analytics; security cookies may be set to detect bots. See the Cloudflare Privacy Policy.
No Google user data is shared with advertisers or other third parties.
08 / YOUR CHOICES
Your choices and rights
- You can browse this Site without signing in; the legal pages and documentation never require an account.
- You can sign out at any time using the button on the home page or
DELETE /api/auth/google, and clear cookies in your browser settings. - You can revoke this application’s access from your Google Account at myaccount.google.com/permissions.
- You may request access to, correction of, or deletion of personal data by writing to privacy@medicareexitguide.com. Because this demo keeps no user database, there is ordinarily no stored record to delete.
Where applicable law (for example the GDPR or the CCPA/CPRA) grants additional rights, we will honour them. We do not sell personal information or share it for cross-context behavioural advertising.
09 / CHILDREN
Children
The Site is a developer demonstration and is not directed at children under 13 (or the minimum age in your jurisdiction). We do not knowingly collect personal information from children. If you believe a child has signed in, contact us and we will remove the associated session data.
10 / CHANGES
Changes and contact
We may update this policy when the Site changes. The “Last updated” date at the top of this page always reflects the current version, and material changes will be noted on the home page. This policy is effective as of 10 November 2026.
Operator: the operator of Medicare Exit Guide · Contact: privacy@medicareexitguide.com · Related document: Terms of Service.