Yeksu Privacy Policy

Yeksu is a workspace platform for business knowledge, missions, automation flows, service connections, AI-assisted outputs, and operational tools.

This policy applies to the web app, public pages, admin console, APIs, OAuth connections, and services offered under the Yeksu name.

This policy covers data processed when you sign up, sign in, invite members, create a workspace, connect services, run automations, create missions, use Graphist, Smart Template, Think Room, and payments.

Third-party websites, social platforms, payment gateways, AI providers, and connected services have their own privacy policies.

We may store your email, name, profile image, email verification status, social sign-in identifiers, roles, active sessions, language choices, and interface preferences.

Passwords are not stored in plain text. Session tokens and verification codes are processed with time and purpose limits.

Workspace data may include business name, members, invitations, roles, permissions, UI settings, business profile, logo, brand color, website, social links, and business descriptions.

Workspace admins may view or manage certain member data and activity according to their role and permission level.

We may process text you enter, files, messages, requests, outputs, drafts, versions, comments, prompts, tables, records, tasks, mind maps, and knowledge data to provide the product.

You are responsible for entering confidential information or data about other people only when you are allowed to use it in the workspace.

Yeksu may store flow definitions, inputs, schedules, operations, conditions, outputs, run status, logs, errors, drafts, approval requests, and version history for missions and automations.

Some unfinished builder drafts may be stored only in your browser so the wizard can recover them when you return.

When you connect services such as Telegram, Instagram, Buffer, WhatsApp, WordPress, Bale, or other providers, Yeksu stores connection identifiers, status, usable resources, permission scope, last check time, errors, and the data required to perform the selected operation.

For OAuth connections, Yeksu requests only the access needed for the selected feature. Persistent provider tokens and credentials, when stored, are kept in a controlled credential store with access controls and encryption.

If sending or receiving messages is enabled, Yeksu may process destination identifiers, resource names, handles, webhook status, inbound events, delivery status, and send errors for the relevant mission or automation.

The Buffer connection can be used to publish Instagram posts or stories through channels you authorize in Buffer. Telegram, Bale, and messaging services are processed only within connected resources.

Features such as Think Room, Smart Template, Graphist, flow suggestions, and Agent may process your text, files, business context, prompts, outputs, and feedback to generate a response or output.

To generate or analyze content, the necessary data may be sent to AI providers or workspace-configured models. Yeksu aims to send only the data needed to complete the request.

For knowledge features, files and text may be split into searchable chunks so responses, missions, or automations can retrieve relevant context.

Workspace admins can configure or review storage policies, limits, and some workspace knowledge restrictions.

To manage payments and usage, Yeksu may store plan, subscription, wallet, transactions, usage credits, orders, payment reference IDs, payment status, budget limits, and alert events.

Sensitive card details are processed by the payment gateway. Yeksu stores only the data needed for reconciliation, support, reporting, and billing, such as status, amount, reference, and masked card number when provided by the gateway.

For security, reliability, and debugging, we may log IP address, browser type, request path, session identifier, event time, API errors, worker status, run identifiers, and operational logs.

This data is used to detect abuse, fix errors, improve performance, review billing, and provide technical support.

Yeksu uses session cookies and refresh-token cookies with path, time, and security limits for secure sign-in. Locale, theme, UI settings, and some local drafts may also be stored in your browser.

Clearing cookies or local storage may sign you out, remove local drafts, or reset interface preferences.

We may contact you for sign-in or registration codes, security notices, product messages, support responses, or important account and workspace updates.

Necessary security or transactional messages may be sent even if marketing messages are disabled.

We use data to provide the service, authenticate users, manage workspaces, run connections, generate outputs, maintain missions, protect security, debug issues, calculate usage, support customers, and improve user experience.

Where required by law or contract, data may be processed to respond to valid requests, resolve disputes, prevent abuse, or enforce service terms.

Some processing is based on choices you make, such as connecting a service, enabling message intake, choosing an output destination, running a flow manually, or activating an automation.

If you revoke a connection in Yeksu or in the third-party service, operations that depend on that connection may stop working.

Yeksu does not sell your data. Data is processed with necessary service providers for hosting, storage, transactional email, payments, AI processing, external connections, security, support, and fulfilling your requests.

When you send an output to an external destination, the content and delivery data needed for that destination are sent to the relevant service.

Connections to third-party services such as Buffer, Instagram, Telegram, Bale, WhatsApp, WordPress, or payment gateways are also governed by those services and their settings.

Disconnecting a service in Yeksu may stop Yeksu access, but you may also need to revoke app access from the third-party account.

Infrastructure, AI providers, payment services, email providers, or third-party connections may operate in different countries or regions.

In those cases, data is processed only as needed to provide the service and with contractual, technical, and access controls.

Data is retained for as long as needed to provide the service, maintain accounts, run missions, support users, protect security, handle accounting, report usage, or meet legal requirements.

Logs, drafts, outputs, files, messages, and payment records may have different retention periods. Deleting an account or workspace may not immediately remove backups or records that must be kept.

Yeksu uses technical and organizational controls such as roles, access limits, password hashing, secure cookies, sensitive event logging, encryption for persistent credentials, and connection health checks.

No system is risk-free. If you believe your account or connection is at risk, revoke access and report it through the privacy contact or support channel.

If you belong to a workspace, its admins may access content, connections, outputs, missions, members, settings, and activity records related to that workspace.

Requests about data inside a workspace should usually be reviewed first through the workspace admin.

You may request access, correction, export, or deletion of data related to you. The response depends on your role, workspace ownership, security requirements, and records that must be retained.

We may need to verify your identity or workspace authority before completing a request.

Yeksu is designed for business and organizational use and is not intended to knowingly collect data from children or people who cannot legally use the service.

If you believe child data has been entered without permission, contact us through the privacy contact.

We may update this policy as the product, laws, service providers, or operational practices change. The updated version will be posted on this page with a new update date.

For privacy questions or requests, use the privacy email shown on this page. We may need to verify your identity or workspace authority before completing a request.