Privacy

Privacy policy

The Atlas uses sign-in information to identify approved collaborators and protect the private reader.

Effective November 15, 2026

Who operates the Atlas

SATB2 Atlas is maintained by Jonathan Revah. This policy covers the public Atlas information pages and access to the reader at satb2atlas.org, including its staging site at staging.satb2atlas.org. For questions or requests, email support@satb2atlas.org.

Information used for sign-in

Email one-time PIN uses the email address you enter and verification of the code sent to you. Google sign-in is being prepared as an additional option. When you choose it, Google and Cloudflare Access process your Google account identifier, email address, and basic profile information, which can include your name and profile picture, to authenticate you.

The Google permissions are limited to openid, email, and profile. They do not grant access to your Gmail messages, Drive files, calendars, or contacts. The Atlas does not receive your Google password.

Cloudflare Access issues a signed authentication session. The reader checks the session and its email address against the approved collaborator addresses or domains before serving protected content. Google sign-in alone does not grant access.

Access records and technical information

Cloudflare processes request and security information needed to deliver and protect the site, such as IP addresses, browser information, requested URLs, timestamps, and authentication outcomes. Access administrators can review authentication records. If you email us, we also receive the information in your message.

The public information pages do not require an account. They include no advertising scripts, analytics scripts, embedded trackers, or forms. Hosting and security providers can still process technical request information.

How information is used and shared

Sign-in information is used to authenticate users, apply collaborator access rules, maintain sessions, investigate access problems, and protect the service. Contact information is also used to respond to requests you send us.

Google handles Google account authentication. Cloudflare provides the website hosting and access-control services. Authorized Atlas administrators can manage collaborator access and investigate sign-in problems. Information may also be disclosed when required by law.

We use Google sign-in data only for these access and security purposes. We do not sell it, use it for advertising, place it in public research records, or use it to train AI models. These commitments apply to information obtained through sign-in; research records have their own source and access restrictions.

Cookies and browser storage

Cloudflare Access uses authentication cookies to maintain a signed-in session for the protected reader. Google may use its own cookies when you visit its sign-in pages. Blocking authentication cookies can prevent sign-in from working. The public information pages do not set application cookies or use local storage.

Retention and removal

We keep collaborator approval information while it is needed to administer access. Authentication and security records follow the retention settings of the services that hold them. Support correspondence may be kept while needed to respond to a request or resolve an access issue.

You can ask us to remove your collaborator access and delete personal information under our control that is no longer needed. Some records may need to be retained for security, legal requirements, or resolving an outstanding issue. Contact us for information about a particular record or retention period.

Your choices

You can choose not to sign in or stop using the reader. Once Google sign-in is enabled, you can review or remove its connection in your Google account connections. Removing the Google connection does not necessarily end an already-issued Cloudflare session immediately; contact us if you need access revoked promptly.

Email support@satb2atlas.org to ask about access, correction, deletion, or privacy. Please do not send passwords, sign-in codes, or sensitive medical records. We may ask for information needed to verify a request.

Other services and policy updates

Google and Cloudflare also process information under their own policies: Google Privacy Policy and Cloudflare Privacy Policy. We will update this page when the Atlas changes how it handles information. A material new use of Google user data will be disclosed before that use begins, with consent requested where required.