Privacy at ELI Personal.

What ELI keeps

Conversation history, correctable personal understanding, goals, research needs, qualified Findings, plans, action previews and result receipts may be stored on ELI's private host so the relationship can continue across sessions.

Basic Google account identity is used to restrict sign-in to the single authorised owner. Operational records may include timestamps, bounded provider metadata and cost or failure receipts needed to prevent unsafe retries. Credentials, private source paths and raw personal files are not added to public pages.

OpenAI processing

Selected requests are processed by OpenAI for conversation, planning, structured judgement, public research or voice transcription. ELI sends recent conversation and only the bounded context needed for that request rather than the entire private store.

ELI requests provider-side storage to be disabled where the API supports it. That request is not a promise about every form of provider retention; OpenAI's own terms and privacy practices also apply.

Google data

ELI uses Google user data only to provide the connected features described here. It is not sold or used for advertising, credit decisions or audience profiling.

Sign-in

Google sign-in verifies the configured owner. The application requests basic identity information for that purpose.

Google Calendar

When connected, ELI reads selected owned calendar information to understand commitments. Relevant Calendar details may be included in a selected OpenAI request when they are needed to prepare or discuss a plan. Calendar writes are limited to the separate calendar created for ELI and remain behind the application's permission and confirmation rules.

Gmail

ELI uses Gmail to send the exact recipient, subject and body that the owner explicitly confirms. If a send result is uncertain, a separate current permission may be used to check only the matching sent message; it is not used to browse or summarise the inbox.

Voice

Voice starts only after the owner activates the microphone. Raw audio is not persisted after the transcription request. A correctable transcript and a bounded receipt may be retained so the owner can review what ELI heard before sending it as conversation.

Owner controls

• Sign out to revoke the current ELI session and clear private browser storage supported by the application.
• Correct or remove supported personal understanding and withdraw or pause supported research needs and Findings.
• Revoke Google access from the Google Account permissions page or disconnect a configured integration.
• Review a proposed external action before confirming it and inspect the retained result afterwards.

Retention and requests

Different records have different correction, revocation and recovery requirements. ELI currently makes no universal deletion window or blanket deletion guarantee.

For access, correction, revocation or deletion questions, contact the support email shown on the Google consent screen. A request is reviewed against the records and safety receipts the private application actually holds.