Legal policies for Jexi.

Last updated: September 15, 2026

This Privacy Policy explains how Jexi, operated by NicNames, Inc. (“Jexi,” “we,” “us,” or “our”), collects, uses, stores, shares, protects, and deletes personal information, customer workspace content, Google user data, and connected-system data.

This Privacy Policy applies to the Jexi website, pilot forms, communications, onboarding, support, and the Jexi service, including AI-assisted customer support, multilingual replies, customer memory, workflow automation, connected integrations, and operational support tools.

If a signed customer agreement, order form, or data processing agreement applies, that agreement may provide additional terms. However, the section titled “Google Workspace and Google API Data” controls Jexi’s use of information received from Google APIs if there is any conflict.

For privacy questions, rights requests, deletion requests, vendor review, or security/legal inquiries, contact [email protected].

---

1. Who this policy covers

Jexi is a business service for AI-assisted customer support, multilingual customer operations, customer memory, workflow automation, and connected business tools. Customers may use Jexi with their employees, agents, contractors, administrators, support teams, and end users.

For business contact data, website data, billing data, support communications, security logs, product administration, and legal/compliance records, Jexi generally acts as an independent controller.

For customer workspace content, end-user communications, connected-system data, and operational data that a customer submits to or connects with Jexi, Jexi generally acts as a processor or service provider on behalf of that customer.

Customers are responsible for providing required notices, obtaining required permissions, configuring connected integrations, limiting access permissions, and ensuring that their use of Jexi complies with applicable laws, platform rules, and customer contracts.

---

2. Information we collect

Jexi may collect or process the following categories of information.

Account and business contact information

This may include name, work email, company name, role, login details, administrator details, pilot request details, demo request details, procurement information, vendor review materials, and support communications.

Customer workspace content

This may include support tickets, chat messages, email threads, email drafts, translations, summaries, reply history, knowledge-base materials, policies, templates, macros, customer context, customer memory, brand voice examples, workflow instructions, approval records, audit logs, and other content submitted to or generated inside a customer workspace.

Connected integration data

Customers may choose to connect third-party systems to Jexi. Depending on the integrations enabled by the customer, Jexi may process data from systems such as Gmail, helpdesk tools, CRM systems, billing systems, registrar systems, hosting systems, domain-management systems, internal databases, or other business tools needed for configured workflows.

Usage, technical, and security data

This may include IP address, browser type, device details, operating system, pages viewed, product events, timestamps, diagnostics, error logs, security signals, session data, authentication events, integration status, workflow status, and audit records.

Commercial and administrative information

This may include plan details, invoices, payment status, contract records, procurement records, legal notices, customer communications, vendor-review materials, and account-administration records.

Cookies and similar technologies

Jexi may use cookies, local storage, pixels, and similar technologies to operate the website and service, secure sessions, remember preferences, understand aggregate usage, measure performance, and support onboarding and communications. More details may be provided in Jexi’s Cookie Notice.

Optional website analytics

On the public jexi.com website, we use Google Analytics only after you choose Allow analytics. Consent is optional: rejecting it does not prevent you from creating an account, contacting us, or using Jexi. Before consent, this integration does not load Google's Analytics script or send Analytics requests.

Analytics helps us understand public page visits, campaign sources, signup/contact clicks and successful setup requests. Google processes browser and device information and cookie identifiers to produce reports. We send only predefined page and event categories and reviewed campaign labels. We do not send form contents, names, email addresses, company names, customer domains, account tokens, ticket text or support conversations. This website integration does not track authenticated app content. Google Signals, advertising personalization, advertising storage and user-provided-data collection are not enabled by this integration.

The Analytics cookies _ga and _ga_5FRQ8K64NP last up to 90 days, without their lifetime being extended on each visit. We retain Analytics user and event data for two months; aggregated reports may remain longer. We remember your analytics choice in browser local storage for 180 days and ask again when it expires. If browser storage is unavailable, your choice applies only in the current tab.

You can change or withdraw consent using Cookie settings in the website footer. Withdrawal stops collection, removes this website's Analytics cookies, and reloads the page to unload the Google tag. It does not undo processing before withdrawal. For access or deletion requests, contact [email protected]; Jexi handles requests concerning its Analytics property. See our Cookie Notice and how Google uses information from sites that use its services.

---

3. Google Workspace and Google API Data

This section applies to all information Jexi receives from Google APIs, including Google Workspace APIs and Gmail APIs. For purposes of this Privacy Policy, this information is called “Google user data.”

Jexi’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Google data Jexi may access

Jexi accesses Google user data only when a customer, administrator, or authorized user connects a Google account, authorizes OAuth scopes, enables a Google Workspace integration, or configures a Jexi workflow that requires Google access.

Depending on the integration and OAuth scopes authorized, Jexi may access the following Google user data:

Jexi does not access Google Drive, Google Calendar, Google Chat, or other Google Workspace data unless a customer or authorized user separately enables the applicable integration, grants the required permissions, and Jexi updates its disclosures where required before using that data for a new purpose.

Jexi does not request Google permissions to “future proof” the service. Google permissions are requested only where reasonably necessary for enabled, user-facing Jexi features.

How Jexi uses Google user data

Jexi uses Google user data only to provide, maintain, secure, or improve customer-authorized, user-facing Jexi features. These uses may include:

• Connecting a customer’s Gmail or Google Workspace account to Jexi.
• Reading authorized email threads so Jexi can help classify, route, summarize, translate, or respond to customer support requests.
• Drafting suggested replies for customer review.
• Sending replies or performing Gmail actions only where the customer or authorized user has enabled that workflow and granted the required permission.
• Translating messages and replies.
• Summarizing conversations and extracting customer-specific operational context.
• Creating support records, workflow history, customer-specific memory, and audit records inside the customer’s Jexi workspace.
• Troubleshooting integration errors and maintaining reliable service operation.
• Detecting abuse, preventing unauthorized access, investigating security events, and protecting users, customers, and Jexi.
• Complying with applicable law, legal process, or enforceable government requests.

Jexi does not use Google user data for unrelated analytics, advertising, retargeting, personalized advertising, interest-based advertising, data brokerage, credit-worthiness, lending, surveillance, or resale.

Google user data and AI processing

Jexi may use AI systems to provide user-facing features selected by the customer, such as drafting support replies, translating messages, summarizing email threads, classifying requests, identifying context, recommending next actions, and helping customer teams operate support workflows.

Google user data may be processed by AI model providers or AI infrastructure vendors only as necessary to provide, maintain, secure, or improve the customer-authorized Jexi features visible in the service.

Jexi does not use Google user data obtained from Google APIs to create, train, or improve generalized artificial intelligence or machine learning models. Jexi also does not permit its AI model providers, subprocessors, or vendors to use Google user data to train or improve their generalized AI or machine learning models.

Customer-specific summaries, draft replies, translations, workflow notes, and context records generated from Google user data remain limited to the customer’s authorized workspace and are used only to provide the Jexi features requested by that customer or user.

Sharing Google user data

Jexi does not sell Google user data.

Jexi does not transfer Google user data to advertising platforms, data brokers, information resellers, credit-worthiness providers, lending providers, surveillance providers, or parties that use the data for advertising, retargeting, personalized advertising, interest-based advertising, unrelated analytics, or resale.

Jexi may share Google user data only in the following limited circumstances:

• With infrastructure, hosting, security, observability, support, communication, and AI subprocessors that are necessary to provide, maintain, secure, monitor, or support the user-facing Jexi features authorized by the customer or user.
• With customer-selected integrations or third-party systems only when necessary to perform a customer-configured workflow or action.
• For security purposes, including detecting abuse, investigating unauthorized access, preventing fraud, or responding to security incidents.
• To comply with applicable law, regulation, legal process, or enforceable government request.
• In connection with a merger, acquisition, reorganization, financing, or sale of assets only where permitted by Google policy and applicable law, including any required prior user consent.

Jexi requires subprocessors that process Google user data to process that data only for authorized purposes and under confidentiality, security, and data-processing commitments.

Human access to Google user data

Jexi personnel do not read Google user data except in limited circumstances:

• The customer or authorized user has given documented consent for Jexi to access specific data for support, troubleshooting, or account recovery.
• Access is necessary for security, abuse prevention, fraud prevention, or incident investigation.
• Access is required to comply with applicable law, regulation, legal process, or enforceable government request.
• The data has been aggregated and anonymized and is used for internal operations in accordance with applicable law and Google policy.

Jexi uses least-privilege access controls and limits production access to personnel with a legitimate business need.

Security of Google user data

Jexi protects Google user data using administrative, technical, and organizational safeguards designed to prevent unauthorized access, use, loss, alteration, disclosure, or destruction.

These safeguards include:

• Secure transmission using modern protocols such as HTTPS/TLS.
• Encryption of Google user data at rest where stored by Jexi.
• Encryption of OAuth access tokens, refresh tokens, service credentials, and related credentials at rest.
• Access controls based on least privilege.
• Workspace boundaries and role-based access where supported by the product.
• Audit logs for important workflow actions, approvals, security-relevant events, and integration activity where supported by the product.
• Monitoring for errors, abuse, unusual activity, and security events.
• Operational processes for credential rotation, revocation, and incident response.
• Key-management practices designed to protect encryption keys and credential material.

No internet service can guarantee perfect security, but Jexi works to protect Google user data and customer content using reasonable safeguards appropriate to the nature of the service and the data processed.

Retention and deletion of Google user data

Jexi retains Google user data only for as long as necessary to provide the customer-authorized Jexi features, comply with legal obligations, resolve disputes, maintain security, prevent abuse, enforce agreements, and maintain required audit records.

A customer administrator or authorized user may disconnect a Google integration through available product settings, revoke OAuth access through their Google account or Google Workspace administrator settings, or request deletion of Google user data by contacting [email protected].

When a Google integration is disconnected, Jexi stops accessing new Google user data from that integration and disables or deletes associated OAuth tokens according to product capabilities, security requirements, and applicable legal obligations.

Upon request or termination, Jexi will delete or return Google user data according to the applicable customer agreement, product capabilities, and legal requirements. Residual copies may remain for a limited period in backups, security logs, audit records, or legally required records. These residual copies are protected from active production use except for recovery, security, compliance, or legal purposes.

If Jexi materially changes how it accesses, uses, stores, shares, or deletes Google user data, Jexi will update this Privacy Policy and, where required, provide notice or obtain consent before using Google user data in a new way.

---

4. How we use information

Jexi may use information described in this Privacy Policy for the following purposes:

• To provide, operate, secure, maintain, and support Jexi.
• To create and manage customer accounts and workspaces.
• To process support messages, email threads, chats, tickets, and customer requests.
• To draft replies, translate content, summarize conversations, classify requests, identify context, and recommend next actions.
• To maintain customer-specific memory, workflow history, approval records, audit trails, and operational context.
• To connect and operate customer-selected integrations according to permissions, OAuth scopes, customer instructions, and workflow settings.
• To perform customer-approved workflows, such as support routing, reply drafting, account checks, domain or hosting support workflows, billing-support workflows, and other configured operational actions.
• To prevent abuse, investigate security events, debug errors, enforce agreements, and protect customers, users, end users, and Jexi.
• To communicate about onboarding, demos, pilots, support, administrative matters, security notices, service notices, legal notices, and product updates.
• To improve reliability, usability, safety, workflow quality, and product performance using telemetry, feedback, and aggregated or de-identified signals where appropriate.
• To comply with law, legal process, tax obligations, accounting obligations, sanctions, export controls, security obligations, and enforceable government requests.

Jexi does not sell customer workspace content or Google user data.

---

5. AI processing

Jexi uses AI systems to help teams automate and improve customer operations. AI features may include drafting replies, translating messages, summarizing conversations, classifying requests, identifying relevant context, recommending actions, creating customer-specific workflow notes, and helping support teams operate more consistently.

AI output may be incomplete, inaccurate, outdated, or inappropriate for a particular situation. Customers are responsible for reviewing AI-generated output where accuracy, tone, compliance, security, safety, customer impact, refunds, account changes, legal issues, or sensitive workflows matter.

Customer content may be sent to AI model providers, infrastructure vendors, and subprocessors only as needed to provide the service, operate integrations, secure the product, comply with customer instructions, or satisfy applicable agreements.

Jexi does not use customer workspace content to train generalized AI or machine learning models. Jexi does not use Google user data obtained from Google APIs to create, train, or improve generalized AI or machine learning models.

Customers should not submit data to Jexi that they are not authorized to use, process, disclose, or connect to the service.

---

6. Legal bases and customer instructions

Where privacy laws require a legal basis, Jexi relies on the basis appropriate to the processing, such as providing a contracted service, taking steps before entering into a contract, legitimate business interests, consent, compliance with law, or protection of rights and security.

When Jexi processes customer workspace content as a processor or service provider, Jexi processes that content according to the customer’s documented instructions. These instructions may include product configuration, connected permissions, OAuth scopes, order forms, customer agreements, data processing agreements, support requests, approval settings, and workflow configuration.

If Jexi believes an instruction violates applicable law or platform policy, Jexi may notify the customer where legally permitted and may pause the affected processing until the instruction is clarified.

---

7. Sharing information

Jexi may share personal information and customer content as described below.

Subprocessors and service providers

Jexi may share information with vendors that host, secure, monitor, support, analyze, communicate, or power Jexi. These vendors may include infrastructure providers, cloud hosting providers, database providers, security vendors, observability tools, communication providers, support tools, analytics providers, and AI model or AI infrastructure providers.

Jexi requires subprocessors and service providers to process data only for authorized purposes and under confidentiality, security, and data-processing commitments.

Customer-selected integrations

Jexi may share information with customer-selected third-party systems when needed to perform a customer-configured workflow or action. Examples may include helpdesk systems, CRM systems, Gmail or Google Workspace integrations, billing systems, registrar systems, hosting systems, domain-management tools, or internal systems selected by the customer.

Professional advisers and business operations

Jexi may share limited information with professional advisers, auditors, insurers, financial providers, and business operations vendors under appropriate confidentiality obligations. Google user data and customer message content are not shared with these parties unless legally required, necessary for security or compliance, or otherwise permitted under this Privacy Policy and applicable law.

Legal, safety, and compliance

Jexi may disclose information to authorities, courts, regulators, law enforcement, or third parties when required by law, legal process, safety needs, security obligations, or to protect rights, users, customers, end users, or Jexi.

Business transactions

Jexi may disclose information to successor entities or transaction participants in connection with a financing, merger, acquisition, reorganization, sale of assets, or similar business transaction. For Google user data, Jexi will do so only where permitted by Google policy and applicable law, including any required prior user consent.

No sale of Google user data or customer workspace content

Jexi does not sell Google user data or customer workspace content. Jexi does not share Google user data or customer workspace content for advertising, retargeting, personalized advertising, interest-based advertising, data brokerage, information resale, credit-worthiness, lending, or surveillance.

---

8. Security

Jexi uses administrative, technical, and organizational safeguards appropriate to the nature of the service and the data processed. These safeguards are designed to protect information against unauthorized access, use, loss, alteration, disclosure, and destruction.

Jexi’s security practices may include:

• Encrypted transport for service traffic.
• Encryption at rest for customer content and Google user data where stored by Jexi.
• Encryption at rest for OAuth access tokens, refresh tokens, API credentials, and related credential material.
• Least-privilege access controls.
• Workspace separation and role-based access where supported.
• Monitoring for errors, abuse, unusual activity, and security events.
• Audit trails for important workflow actions, approvals, integration activity, and security-relevant events where supported.
• Operational recovery processes for critical systems.
• Credential rotation, revocation, and incident-response processes.
• Ongoing review and improvement of controls as the product and customer requirements mature.

Customer administrators are responsible for inviting appropriate users, removing users who no longer need access, configuring least-privilege roles, limiting integration scopes, protecting connected accounts, and enabling approval rules for sensitive workflows.

If Jexi confirms a security incident involving customer content or Google user data, Jexi will notify affected customers without undue delay and provide information reasonably available to help customers meet their own legal obligations. Where required by law, contract, or platform policy, Jexi will also notify affected users, regulators, or platform providers.

No internet service is perfectly secure. Jexi works to protect the service with reasonable safeguards, but customers remain responsible for their own users, endpoints, policies, connected accounts, and workflow configuration.

---

9. Retention, export, and deletion

Jexi keeps information for as long as needed to provide the service, comply with legal obligations, resolve disputes, maintain security, maintain audit trails, enforce agreements, prevent abuse, and protect customers, users, end users, and Jexi.

Customer workspace retention, export, and deletion are handled according to product capabilities, customer instructions, applicable customer agreements, and legal requirements.

Customers may request export, return, or deletion of customer workspace content by using available product controls or contacting [email protected].

Some residual copies may remain for a limited period in backups, security logs, audit records, or legally required records. These residual copies are protected from active production use except for recovery, security, compliance, or legal purposes.

Google user data retention and deletion are described in the section titled “Google Workspace and Google API Data.”

---

10. Privacy rights

Depending on where a person lives, they may have rights to access, correct, delete, export, restrict, object to, or appeal certain processing of personal information. They may also have a right to complain to a privacy regulator.

Privacy requests can be sent to [email protected].

Jexi may need to verify the request before responding. If a request concerns information inside a customer workspace, Jexi may refer the request to the customer because the customer controls that workspace data.

Customers are responsible for responding to end-user privacy requests where the customer acts as the controller, business, or equivalent legal role for the relevant workspace data.

---

11. International transfers

Jexi and its subprocessors may process information in countries other than where it was collected. Where required, Jexi uses appropriate transfer mechanisms and contractual safeguards, such as data processing terms, standard contractual clauses, or other lawful transfer bases.

---

12. Children and sensitive data

Jexi is designed for business use and is not directed to children.

Customers should not submit children’s data, special category data, health data, payment card data, government identifiers, biometric data, financial account credentials, or similarly sensitive data unless their agreement and configuration expressly support that processing and all required legal notices and consents have been provided.

Customers should configure approval rules for sensitive, regulated, high-impact, irreversible, or security-relevant workflows.

---

13. Changes to this Privacy Policy

Jexi may update this Privacy Policy from time to time. The “Last updated” date above shows when this Privacy Policy was last revised.

If Jexi materially changes how it uses personal information, customer workspace content, or Google user data, Jexi will provide notice where required by law, contract, or platform policy. If Jexi changes how it accesses, uses, stores, shares, or deletes Google user data in a way that requires new consent, Jexi will update its disclosures and obtain consent where required before using Google user data for the new purpose.

---

14. Contact

For privacy questions, rights requests, deletion requests, Google data requests, security/legal inquiries, or vendor review, contact:

Jexi
Operated by NicNames, Inc.
Email: [email protected]