Privacy notice

This notice covers the Jeremiah AI information website and its separate, operator-managed Google integration pilot. It does not cover unrelated applications that use the same parent domain.

Who operates the application

Jeremiah AI is operated by Jeremiah Styles for an authorized, limited-user pilot. Contact sty06002@gmail.com with privacy, connection, or deletion questions.

Visiting this information site

These static pages contain no login flow, upload form, analytics scripts, advertising tags, or operational API calls. Cloudflare delivers and protects this site. It may process network and request information, including IP addresses, browser information, requested URLs, and security events. Cloudflare's processing and retention are described in its privacy policy. We have not added advertising, visitor-analytics, or cookie-setting application code. Provider security mechanisms may operate independently; this is not a promise that hosting generates no logs or cookies.

Google data the separate application may access

Only after an authorized user completes Google's consent process, the initial application may receive account-identification information, such as account ID, email address, and basic profile information; Google Drive file information, metadata, and content permitted by a read-only grant; and Google Sheets spreadsheet information and cell contents permitted by a read-only grant. Those grants can permit access to more than one file in the connected account. Actual operations must remain limited by the separately authorized workflow.

Read-only access does not authorize editing, deleting, sharing, or sending information. Any later write-capable test needs its own approved scope and resource boundary. This notice is not itself permission to expand access.

How information is used

Information is used to carry out a user's authorized retrieval or organization task, return its results, resolve technical failures, and maintain necessary security and execution records. Initial model tests use synthetic information rather than private Google account contents.

Google user data is not sold, used for advertising, or used to train generalized artificial-intelligence or machine-learning models in this pilot. Sending private Google account contents to external AI providers is not part of the currently authorized pilot. Any future AI-processing feature requires an updated, prominent disclosure, the user's informed consent, compatible provider terms and settings, and a separately approved workflow before activation. Google API data, including onward transfers, is subject to the Google API Services User Data Policy and its Limited Use requirements.

Storage and service providers

The operational application and its authorization credentials are separate from this public information site. Authorized working copies, task results, or execution records may be stored on administrator-controlled infrastructure. No credentials or Google account data are included in this static website package. Google provides the account authorization and source APIs. Cloudflare hosts these public pages, not the operational Google connection. The operator and authorized support personnel may access specific task data with the user's affirmative agreement, or as needed for security or applicable legal requirements. No unrelated third-party data sharing is authorized by this pilot. Credentials are kept separately with restricted filesystem access; authentication codes and tokens must not be posted to this website, support email, or shared logs.

Retention, revocation, and deletion

Connection credentials and protected configuration backups remain on operator-managed infrastructure until they are rotated or removed; synthetic test records remain until operator cleanup. These pages do not activate a recurring document archive. Before a workflow retains real document or spreadsheet copies, its purpose, retention period, and backup-deletion process must be specified to the affected user. There is no blanket claim of automatic deletion after a fixed number of days. Users may revoke the application through Google Account connections and request removal of application-held data and credentials by contacting the operator. Requests are handled after verifying the requester's authority; any legally required retention or backup limitations will be explained. Revocation prevents new authorized access but does not itself erase copies previously stored outside Google.

Changes and questions

Material changes to the application's access or data use will be disclosed in an updated notice before the affected capability is activated. New categories of access require the appropriate consent and workflow authorization. Do not send secrets or sensitive records to the support address.