Effective September 10, 2026

Privacy policy

This policy covers InMyEar, including the InMyEar Legacy Gmail connection. Steve Springer operates the assistant for his own authorized accounts. This information site does not offer public enrollment.

Data accessed

Provider authorization supplies account identity, granted permissions, and credentials used to maintain the connection. Mail features access message identifiers, sender and recipient information, subjects, dates, and bounded message previews. Requested voice interactions also process speech, transcripts, instructions, and tool results. Separate calendar features access the connected identity, calendar metadata, and event information needed for the requested function.

Purposes and permissions

InMyEar uses this information to identify the correct account, display or summarize requested messages, provide recent-mail monitoring when enabled, and retain observations the owner chooses to review. Legacy Gmail is read-only. Send-enabled accounts and calendar creation require separate authorization and exact, current-session spoken confirmation before an external write.

AI processing and other recipients

When the owner uses voice or cloud AI assistance, selected message information, transcripts, instructions, and tool results may be sent to OpenAI to provide that interaction. The owner may also select local AI processing where configured. Google and Microsoft process API and authorization requests for their respective connected services. Background mail monitoring makes provider requests but does not invoke AI models.

InMyEar does not sell Google user data, use it for advertising, or use it to train or improve generalized AI models. Its use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Information is accessed by the owner and by service providers as needed to provide the selected functionality; authorized administrative access may be needed for maintenance or security.

Storage and protection

Connected-account credentials and application state are held in restricted storage on the owner’s infrastructure. Credentials are separated by enrollment and are not published on this website. Private recovery backups may include credentials and application state. Exported context packets are separate copies under the owner’s control.

Retention and deletion

When enabled, recent-mail monitoring retains up to 300 bounded samples. Samples expire seven days after observation; visible reads filter expired samples and scheduled maintenance removes them. Reviewed observations and their bounded source excerpts persist until the owner dismisses or forgets them. A digest may remain to prevent the same forgotten observation from being proposed again. Commitments and execution receipts can persist for continuity and to prevent duplicate actions.

Disconnecting an account or revoking its grant stops future authorized access but does not automatically erase previously retained observations, exports, provider records, or recovery backups. The operator can remove stored connections and application records; backup copies remain until the applicable recovery copies are replaced or removed. Provider-side processing and retention are also governed by the relevant provider’s policies.

Your controls

Google access can be revoked through Google Account connections. The owner can disable monitoring, remove an enrollment, forget reviewed observations, and request deletion of retained records. No email send or calendar insertion is performed as an automatic enrollment test.

This public website

These pages use no analytics scripts, advertising, tracking cookies, or sign-in. The hosting infrastructure processes ordinary connection information to serve the pages.

Contact and changes

Contact cpsrents@gmail.com for questions or deletion requests. Changes to this policy will be reflected on this page with an updated effective date.