Privacy Policy

Information the user chooses to provide or connect

Depending on the features and Android permissions the user enables, MyJarvisAi may process:

• Account information, such as a name, email address, provider account identifier, and connection status.
• Requests, conversations, and memory, such as spoken or typed requests, assistant responses, saved preferences, people, contact details, places or addresses, memories, and related context needed to answer or act.
• Phone messages, including SMS sender or recipient, message content, time, and delivery information, only after the user selects MyJarvisAi as the Android assistant, separately grants the applicable SMS permission, and asks to use the message feature.
• Notification context, including the source application, title or sender, category, and preview text from applications the user separately allows after granting Android notification access.
• Voice, image, and recognition information, including microphone audio during an active voice session, transcripts, user-selected images, face photographs, face-recognition templates, and an optional Voice ID profile. A separately distributed private owner build can also process camera captures when its operator enables that feature.
• Private owner device information, including nearby Wi-Fi choices, Bluetooth connection state, and device diagnostics, only in a separately distributed private owner build when its operator enables an owner-only native-device or glasses feature.
• Connected-home information, such as home and room names, device names and types, supported capabilities, current device state, automations, events, and supported controls the user grants.
• Optional Google service information, such as calendar events, Gmail messages and mailbox state, Drive file names or requested file content, and Google Contacts, only for a capability the user separately connects and authorizes.
• Other connected-service information only if a user separately enables that service and approves the permissions shown by its provider.

How Google Home information is used

MyJarvisAi uses user-authorized Google Home information only to provide connected-home features requested by the user, including:

• showing authorized homes, rooms, devices, automations, capabilities, and current state in the application;
• understanding which authorized home or device the user means in a request;
• answering the user's questions about their connected-home state; and
• performing supported device commands or automations the user requests or explicitly enables.

When an assistant request requires AI processing, MyJarvisAi may send the request and relevant connected context to the user's configured AI provider to produce the response or determine the supported action. The AI provider processes and may retain that information under its applicable terms, settings, and retention controls.

MyJarvisAi does not sell Google user data, use it for targeted advertising, or provide it to data brokers. MyJarvisAi's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Other optional Google services

Calendar, Gmail, Drive, and Google Contacts are separate optional connections. MyJarvisAi requests the applicable Google authorization only when the user enables a capability. Depending on what the user grants, MyJarvisAi can read calendar events, create or edit events, search and read mail, change supported mailbox state or send a user-confirmed message, search or read a requested Drive file, and read contacts for assistant requests. Content relevant to an assistant request may be included in the context sent to the configured AI provider and may appear in MyJarvisAi conversation history. Revoking Google access stops new access but does not delete copies already retained in conversation history or by the configured AI provider.

SMS and phone-message access

The public Android application requests SMS read, receive, and send permissions for its optional phone-message assistant feature. MyJarvisAi does not request Call Log permissions. Android requires the user to select MyJarvisAi as the current assistant before the application offers the separate SMS permission prompts. Removing the assistant role or a required SMS permission stops the corresponding message feature.

• Read: MyJarvisAi reads relevant SMS sender, time, and content only when the user asks it to find, read, summarize, or use a message. It does not bulk-import or index the SMS inbox.
• Receive: on an SMS arrival, MyJarvisAi retains a native Android message-row reference and an opaque, account-scoped selection token. Its arrival notification does not contain the sender or message body. The message content is read only after a later user request.
• Send: MyJarvisAi can prepare an exact recipient and message body, but sending requires the user's explicit confirmation of that exact draft through a short-lived, one-use authorization.

When the user asks the assistant to work with an SMS, the relevant sender, recipient, and content may be sent to the configured AI provider. MyJarvisAi does not create a separate archive of the SMS inbox; however, message content repeated in a request or response can be retained as part of the MyJarvisAi conversation history and by the configured AI provider under its terms.

Notification awareness

Android's notification-access screen is separate from permission to show MyJarvisAi's own notifications. If the user grants notification access, MyJarvisAi still requires the user to choose which source applications are allowed. For allowed applications, notification title or sender and preview text are held in memory for up to ten minutes, or removed sooner when the source notification is removed. Notification content is not written to disk by the notification-awareness component. The selected application package names and allowlist are retained locally so the preference continues to work.

If the user sends an assistant request while notification context is active, relevant allowed notification text may be included in the context sent to the configured AI provider. The provider may process and retain that context under its applicable terms. MyJarvisAi does not use notification content for advertising.

Microphone, voice, and images

When the user starts an active live-voice session, microphone audio is transmitted to the configured AI provider so it can transcribe the request and return a response. Android displays an ongoing foreground-service notification when a live-voice session continues while the application is not in the foreground. Conversation transcripts are saved to the user's MyJarvisAi account as described below.

The public Play build uses Android's system photo picker when the user chooses an image-assistant or recognition feature and does not request Android camera permission. A separately distributed private owner build can also use a phone or compatible-glasses camera when its operator enables a camera feature. An image attached to an assistant request is sent to the configured AI provider for that request. MyJarvisAi deletes its temporary attachment copy after the request or when the screen closes; this does not delete the original image selected by the user or a copy retained by the AI provider under its terms.

Face recognition and Voice ID

MyJarvisAi offers optional, user-directed face recognition. Enrolled face photographs remain in encrypted application storage on the phone and are not uploaded to the MyJarvisAi cloud. Measurements derived from those photographs, called face-recognition templates or embeddings, are stored under the user's Firebase account so recognition can work after sign-in on another phone. A user can remove an enrolled face through the in-app face controls. Face photographs and templates may be considered biometric identifiers under applicable law.

Optional Voice ID enrollment is performed on the phone. Enrollment audio is processed temporarily and is not retained by MyJarvisAi after the local model creates the profile. The resulting numerical voice templates remain only in the application's local data for that account until the user clears the Voice ID profile, erases application data, or uninstalls the application. Voice ID is separate from live-voice audio sent to the configured AI provider.

MyJarvisAi does not receive Android fingerprint or device-unlock biometric templates.

Private owner device connections

The public Play build does not request Android location, nearby Wi-Fi, Bluetooth, or camera permission. It does not read GPS position, determine the user's physical location, run geofences, or scan nearby Wi-Fi or Bluetooth devices.

A separately distributed private owner build can request nearby Wi-Fi and setup-time location access for owner-only native-device setup, Bluetooth access for compatible glasses, and camera access for owner-enabled camera features. That build may retain connection and device state needed for an enabled feature, but MyJarvisAi does not use nearby Wi-Fi or Bluetooth discovery to build a physical-location history. Locations, addresses, or coordinates that a user deliberately asks MyJarvisAi to remember are stored as user-provided memory rather than obtained from an Android location permission.

How other information is used

• to authenticate a user and maintain connections the user enables;
• to answer requests, provide context, and perform actions the user requests;
• to remember preferences or information the user asks MyJarvisAi to remember;
• to operate, secure, diagnose, and improve the reliability of MyJarvisAi; and
• to comply with law, enforce terms, and prevent misuse or harm.

Sharing and service providers

MyJarvisAi may disclose the information needed to providers that supply authentication, cloud infrastructure, AI processing, communications, diagnostics, or device connectivity. Assistant requests can include text, live microphone audio, attached images, requested SMS content, active allowed-notification context, saved memory, or connected-device context when that information is relevant to the feature the user invokes. Information may also be sent to a destination the user explicitly requests, such as when the user asks MyJarvisAi to control a connected device. Information may be disclosed when required by law or reasonably necessary to protect users, the service, or others.

MyJarvisAi does not sell personal information.

Storage, security, and retention

MyJarvisAi uses reasonable administrative and technical safeguards, including Android platform-provided protected storage for supported credentials and Android Keystore encryption for locally enrolled face files. No system can guarantee absolute security.

• Account cloud data: conversation history, saved memories, people, places, settings, connection records, and synced face-recognition templates can be stored under the user's Firebase account. Conversation history does not currently expire automatically. It remains until an applicable in-app deletion control removes it or the verified account-and-data deletion process is completed.
• Local application data: settings, credentials, browser sessions, Voice ID templates, enrolled face photographs, caches, and databases remain on the phone until the user removes them, erases the application sandbox, or uninstalls the application. Some local connection identifiers or authorization credentials remain while the related feature is enabled.
• Short-lived context: allowed notification content expires from memory after no more than ten minutes or when removed. Temporary image attachments are deleted by MyJarvisAi after use or when the screen closes. Message-selection and send-authorization tokens are short-lived.
• Connected providers: Google, the configured AI provider, websites, smart-home providers, and other independently controlled services apply their own retention policies. Disconnecting a service from MyJarvisAi prevents new access but does not by itself delete information retained by that provider.

After a verified deletion request, MyJarvisAi removes the covered Firebase sign-in account and associated MyJarvisAi data from active cloud systems. Limited records may be retained when reasonably necessary for security, fraud prevention, legal compliance, dispute resolution, or backup rotation.

User choices, revocation, and deletion

A user can control access in the following ways:

• disconnect a connected service or device from MyJarvisAi;
• revoke Google access from the user's Google Account connected-app settings;
• disable Android runtime permissions, remove the Android assistant role, or revoke Android notification access in the device's system settings;
• open the verified account and cloud-data deletion process from Settings > Account > Request account & data deletion;
• immediately erase the complete MyJarvisAi app-data sandbox on that phone from Settings > Account > Erase data from this phone; this local-only action does not delete the Firebase account or cloud data;
• delete saved memories or other user-managed information using available in-app controls; and
• request access to or deletion of MyJarvisAi account data by emailing harvesty.team@gmail.com.

Deletion requests should identify the email address used with MyJarvisAi and clearly state what should be deleted. We verify that the request comes from the account owner before deleting the Firebase sign-in account and associated MyJarvisAi account data from active cloud systems, including conversation history, saved memory, settings and connection records, and synced face-recognition templates. The cloud deletion request does not erase local data from a phone or source information that remains in the user's SMS application or independently controlled connected services. See Support and data requests for the complete request process.

Harvesty relationship

MyJarvisAi is a standalone Android application and a Harvesty product. A future optional connection between MyJarvisAi and Harvesty is planned, but it is not active today. Harvesty accounts and customer data are not connected to MyJarvisAi automatically. If that capability is introduced, the user or organization will be shown the connection and permission choices before data is shared.

Children

MyJarvisAi is not directed to children under 13, and we do not knowingly collect personal information from children under 13.

Changes and contact

We may update this policy as MyJarvisAi changes. The effective date at the top identifies the current version. Questions, privacy requests, and deletion requests can be sent to harvesty.team@gmail.com.