Legal policies for Jexi.

Roles

For most customer workspaces, the customer is the controller or business for end-user personal information and Jexi acts as a processor or service provider. Jexi may act as a controller for account administration, billing, security, product analytics, direct business communications, and legal compliance.

Processing scope

• Support tickets, chat logs, email threads, translations, drafts, reply history, and agent notes.
• Knowledge-base content, macros, brand voice examples, internal instructions, and workflow settings.
• Domain, hosting, billing, CRM, account, or operational records made available through customer-selected integrations.
• Audit logs, approval records, workflow status, action results, usage events, diagnostics, and security logs.

Customer instructions

Jexi processes customer content according to documented customer instructions, including product configuration, connected permissions, support requests, order forms, data processing agreements, and applicable workflow settings.

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

Subprocessors

Jexi uses infrastructure, security, observability, communication, support, analytics, and AI vendors to operate the service. We require subprocessors to process customer data only for authorized purposes and under confidentiality, security, and data-processing commitments.

Customers with signed agreements may request current subprocessor information and may receive notices or objection rights as stated in their agreement.

Security and access

• Use least-privilege access for customer workspaces and internal administration.
• Restrict production access to personnel with a business need for operations, support, security, or contractual obligations.
• Use encrypted transport for service traffic and reasonable administrative, technical, and organizational safeguards.
• Maintain audit trails for important workflow actions, approvals, and security-relevant events where supported by the product.

Return, deletion, and backups

Upon request or termination, Jexi will delete or return customer content according to the applicable agreement, product capabilities, and legal requirements. Backup, audit, and security copies may remain for a limited period and are protected from active production use except for recovery, security, compliance, or legal purposes.

Incident notice

If Jexi confirms a security incident involving customer content, we will notify affected customers without undue delay and provide information reasonably available to help customers meet their own legal obligations.

Customer responsibilities

• Provide required notices and obtain required permissions before submitting data to Jexi.
• Limit connected permissions to what each workflow needs.
• Configure approval rules for sensitive, regulated, or irreversible actions.
• Do not submit special category, children's, health, payment card, government ID, or similarly sensitive data unless the agreement and setup expressly support it.