alymo.ai

Privacy policy

Jingxin software Inc. · Effective October 4, 2026

Alymo is operated by Jingxin software Inc., Richmond, BC, Canada. This policy explains how we handle information through Alymo’s website, apps, agents and connected services. Contact [email protected] about privacy, access, correction or deletion.

For email registration we process your email address, verification code, password and optional display name. Passwords are stored as hashes. Google Workspace delivers registration messages from [email protected]. We use account information to verify registration, authenticate you and protect access to your account.

When you choose social sign-in, your provider authenticates you. Alymo exchanges temporary authorization codes and tokens, verifies the response and creates its own session. The sign-in flow does not store provider access or refresh tokens for later access to that provider’s services.

  • Google: we request OpenID, email and profile permissions and use your provider identifier and verified email, when supplied, to establish your account. These sign-in permissions do not give Alymo access to your Gmail messages, contacts or Drive files.
  • Apple: we request name and email and use your provider identifier and verified email, which may be an Apple private relay address. Apple may supply your name only on first authorization. We do not rely on a browser-submitted name to verify identity.
  • Facebook: we request public_profile. Our current sign-in implementation retrieves your app-specific Facebook identifier to establish your account. It does not request your Facebook email, friends or posts.
  • Connections you choose to add separately have their own permissions. Social sign-in alone does not authorize an agent to access those connected accounts.

Connecting Gmail is separate from Google sign-in. After you agree to the Gmail data-use notice and Google's consent screen, Alymo requests gmail.readonly to search and read message headers, snippets and bodies, and gmail.compose to create drafts and send messages. Manual sending requires your approval. You may separately enable Auto-draft or Auto-reply for a contact: Auto-draft saves replies for review; Auto-reply sends replies without asking each time. These modes apply to new received messages and require background email processing, saved Privacy permission and a connected selected mailbox. You can turn a contact’s mode off in Contacts or stop background processing in Email skill settings. Google bundles drafts and sending in gmail.compose. Draft editing and deletion are not currently supported by Alymo.

We store your mailbox address, granted permissions, consent version and encrypted access and refresh tokens. Email results and derived summaries, memory and task records can remain in your conversations and saved records on Alymo's servers. Relevant Gmail-derived context may be sent to your selected model provider and configured endpoint to provide your requested email assistance. Mailbox access remains scoped by Privacy permissions to the requesting agent and service. Review the selected provider’s terms and data practices before processing private email. Private-content text runs suppress content diagnostics and third-party decision optimization. Review your agent and Privacy permissions before authorizing access.

Alymo's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy and Google Workspace user data and developer policy, including the Limited Use requirements. We do not sell Google-derived data, use it for advertising or creditworthiness decisions, or use or transfer it to train general AI models. Human access is limited to your explicit consent for specific data, security investigations, applicable legal obligations, or aggregated anonymized internal operations permitted by Google's policy.

Gmail-derived content is retained to provide the conversations and records you request, subject to the retention and deletion process below. Private-content text runs suppress content diagnostics; operational metadata may still be logged. Historical logs and backups may retain earlier content until handled by the deletion process. This is not a promise of zero retention by Alymo or a provider.

Disconnect removes Alymo's stored mailbox credentials. It does not revoke authorization at Google or erase earlier conversations, derived records, logs or backups. You can revoke Alymo in your Google Account's third-party connections settings and request deletion of Gmail-derived data by emailing [email protected]. Connecting or disconnecting Gmail does not impose account-wide model or voice restrictions on unrelated agents.

Google Workspace user data and developer policy

Google API Services User Data Policy

Conversations, agents and content

We process the content you provide and the results generated for you, including messages, attachments, voice or image inputs, agent and skill settings, saved records and tool results. This can include sensitive information if you choose to supply it. Only provide information you are entitled to use.

Cloud conversations and related records are stored on Alymo’s servers. To answer your request, relevant conversation context, instructions, attachments and tool results are sent to the selected model or media service. Available providers depend on your model and feature choices and can include OpenAI, Anthropic, Google and xAI. Other endpoints may be used when you configure them or connect a service. Those providers’ own terms and data practices also apply; an on-device model and a cloud model have different data flows.

Agents can save memory and task records for later use. Where your Privacy Agent permissions allow it, supported cloud conversations can be processed to extract and store personal information. Review your agent’s permissions and saved records when deciding what to share.

Supported on-device chat keeps its conversation history and model diagnostics on your device. Tools, Connections and cloud features can still send the information needed for their operation to Alymo or external services. Local diagnostic logs can contain conversation and tool content. Device storage and backups are controlled partly by your device and operating system.

When you add a Connection, we store its configuration and encrypted credentials so authorized tools can use the service. The connected service receives requests and information needed for the actions you authorize. Removing a Connection does not delete records already held by the external service.

Information you publish, share or send can be visible to the selected recipients or the public, depending on the feature and its access settings. This can include published agent or skill descriptions, shared records and direct messages. Review sharing settings before including private or customer information. Sharing an agent does not automatically copy its Connection credentials.

We process account identifiers, usage and credit records, service requests, error information and support correspondence to operate features, calculate usage, diagnose problems, prevent misuse and respond to you. Infrastructure services process connection information such as IP addresses and request metadata. Diagnostic records may contain content associated with a failed operation.

Google Cloud hosts Alymo’s production service in the United States, Google Workspace handles registration email and business correspondence, and Cloudflare handles delivery and security for the public website. Model providers, authorized Connections and other services involved in a feature process the information needed to provide that feature. Authorized personnel may access information when necessary for support, security or service administration.

We may disclose information when required by law or when reasonably necessary to protect rights, safety and service security. Information may be processed outside your province or country, where local laws may differ.

The web app uses a session cookie to keep you signed in and browser storage to remember account-related preferences. The current web session cookie expires within seven days. Native apps store settings and supported local conversation data on your device. Clearing browser or app storage can remove local data and sign you out, but does not by itself delete your server account.

Account information and saved content remain available while needed to provide your account and requested features. We retain operational, security and transaction information as needed for those purposes and applicable obligations. Retention depends on the record and purpose; the expiry of a login code is not the retention period for your account or conversations.

Email verification codes and pending social sign-in flows expire after ten minutes. Social sign-in completion tickets expire after one minute. Expired authentication state is rejected and cleaned up as new flows are created.

You can request deletion of your Alymo account, particular information or Facebook sign-in data by emailing [email protected]. We verify account ownership, clarify the request when needed, and delete or de-identify information that we no longer need to retain. We explain any necessary retention, restrictions or further steps in our response. Backup copies may remain until replaced or expired and must not be used to restore deleted information to active use. Local device copies and information retained independently by recipients or external services may need to be removed separately.

You can choose email registration instead of a social sign-in provider, review agent permissions, manage Connections and use available controls to edit your profile or saved content. You can also revoke Alymo’s authorization in your sign-in provider’s account settings. Revoking provider access stops that authorization; it does not automatically delete your Alymo account or previously stored data.

Contact [email protected] to request access, correction, a copy of your information, deletion or withdrawal of consent, or to raise a privacy concern. We may need information to verify ownership and understand the request. Do not send passwords, verification codes, access tokens or identity documents in an initial email. We respond in accordance with applicable law and explain any limitations. Withdrawing information or permissions needed for a feature can prevent that feature from working.

If you believe a child has supplied personal information without appropriate authorization, contact us so we can investigate and address it.

We use safeguards including encrypted network connections, hashed passwords, encrypted Connection credentials and access controls. No service or device can guarantee absolute security. Protect your account and device and report suspected unauthorized access to [email protected].

We may update this policy as our service and practices change. We will publish the revised text and effective date here and provide additional notice or seek consent when required.