Skip to content
Back to Leera

Legal & policies

Privacy Policy

How we collect, use, and protect your information when you use Leera.

On this page17 sections

This Privacy Policy describes Our policies and procedures on the collection, use and disclosure of Your information when You use the Service and tells You about Your privacy rights and how the law protects You.

We use Your Personal data to provide and improve the Service. By using the Service, You agree to the collection and use of information in accordance with this Privacy Policy.

Interpretation and Definitions

Interpretation

The words of which the initial letter is capitalized have meanings defined under the following conditions. The following definitions shall have the same meaning regardless of whether they appear in singular or in plural.

Definitions

For the purposes of this Privacy Policy:

  • Account means a unique account created for You to access our Service or parts of our Service.
  • Affiliate means an entity that controls, is controlled by or is under common control with a party, where "control" means ownership of 50% or more of the shares, equity interest or other securities entitled to vote for election of directors or other managing authority.
  • Company (referred to as either "the Company", "We", "Us" or "Our" in this Agreement) refers to Leera ai solutions llp, Futura, Magarpatta Rd, Kirtane Baugh, Hadapsar, Pune, Maharashtra 411028.
  • Cookies are small files that are placed on Your computer, mobile device or any other device by a website, containing the details of Your browsing history on that website among its many uses.
  • Country refers to: Maharashtra, India
  • Device means any device that can access the Service such as a computer, a cellphone or a digital tablet.
  • Personal Data is any information that relates to an identified or identifiable individual.
  • Service refers to the Website.
  • Service Provider means any natural or legal person who processes the data on behalf of the Company. It refers to third-party companies or individuals employed by the Company to facilitate the Service, to provide the Service on behalf of the Company, to perform services related to the Service or to assist the Company in analyzing how the Service is used.
  • Usage Data refers to data collected automatically, either generated by the use of the Service or from the Service infrastructure itself (for example, the duration of a page visit).
  • Website refers to Leera, accessible from https://leera.io
  • You means the individual accessing or using the Service, or the company, or other legal entity on behalf of which such individual is accessing or using the Service, as applicable.

Collecting and Using Your Personal Data

Types of Data Collected

Personal Data

While using Our Service, We may ask You to provide Us with certain personally identifiable information that can be used to contact or identify You. Personally identifiable information may include, but is not limited to:

  • Email address
  • First name and last name
  • Phone number
  • Address, State, Province, ZIP/Postal code, City
  • Usage Data

Usage Data

Usage Data is collected automatically when using the Service.

Usage Data may include information such as Your Device's Internet Protocol address (e.g. IP address), browser type, browser version, the pages of our Service that You visit, the time and date of Your visit, the time spent on those pages, unique device identifiers and other diagnostic data.

When You access the Service by or through a mobile device, We may collect certain information automatically, including, but not limited to, the type of mobile device You use, Your mobile device unique ID, the IP address of Your mobile device, Your mobile operating system, the type of mobile Internet browser You use, unique device identifiers and other diagnostic data.

Cookies and browser storage

We use essential cookies and browser storage to keep you signed in, maintain security and remember your choices. These remain active and are separate from optional analytics.

  • Essential. Storage needed for these functions stays active when you reject optional cookies or turn analytics off.
  • Analytics. When configured, PostHog and Google Analytics help us understand visits and product use only after you allow optional analytics. The section below explains what this integration collects and how withdrawal works.

Optional website and product analytics

When analytics is enabled for Leera Cloud, we ask for your permission before collecting optional website and product activity. Declining does not prevent signup or use of Leera. Use Cookie settings to change your choice. Your choice is stored in this browser for this site; another browser, device or site has its own choice.

With permission, PostHog helps us understand public-page visits, signup and onboarding steps, sign-in outcomes, returning sessions, ticket-creation attempts, feature milestones and checkout outcomes. We use randomly generated browser, session, account, membership, workspace, project and interaction identifiers, normalized page categories, campaign labels, action timestamps and bounded status or error categories. Ticket activity can include the creation method, whether a project was provided during setup, and field categories where validation prevented submission. Billing milestones can include plan references, seat counts, currency, amounts and anonymous transaction references. Partner program activity uses the same consent controls. These identifiers allow us to connect a signup journey with later activity; they are not your name or email.

This analytics integration does not send passwords, verification codes, authentication tokens, project names, URL query strings, full private URLs, form answers, document or issue content, comments, AI prompts or responses. Session recording, automatic click capture and automatic exception capture are disabled. Self-hosted customer instances do not automatically send this end-user analytics to Leera. Operational and security records needed to run the service are separate from optional analytics.

When configured, Google Analytics 4 measures consented public-website visits and selected conversion milestones. Advertising storage, advertising personalization and Google signals are disabled in this integration. Google Analytics may store analytics cookies after you allow analytics. PostHog uses browser storage for the identifiers described above. Analytics providers also receive the network information necessary to deliver a request; our PostHog configuration disables IP enrichment. Our current PostHog project is hosted in the United States. See PostHog's privacy policy and Google's privacy policy.

Withdrawing permission stops new optional capture in that browser, clears its analytics identifiers and requests cancellation of unsent server events associated with that consent identifier. A request already in transit may still arrive. Withdrawal does not automatically erase previously delivered records or copies in backups. Server delivery records and provider data follow their configured retention periods. Contact contact@leera.io for an analytics access or deletion request; do not include passwords or tokens. We verify your authority before acting on records associated with a workspace.

Use of Your Personal Data

The Company may use Personal Data for the following purposes:

  • To provide and maintain our Service, including to monitor the usage of our Service.
  • To manage Your Account: to manage Your registration as a user of the Service.
  • For the performance of a contract: the development, compliance and undertaking of the purchase contract for the products or services You have purchased.
  • To contact You: To contact You by email, telephone calls, SMS, or other equivalent forms of electronic communication.
  • To provide You with news, special offers and general information about other goods, services and events.
  • To manage Your requests: To attend and manage Your requests to Us.
  • For business transfers: We may use Your information to evaluate or conduct a merger, divestiture, restructuring, reorganization, dissolution, or other sale or transfer of some or all of Our assets.

Retired Ping and connected accounts

Ping, the AI teammate, has been retired, together with the personal connected accounts (Google and Microsoft 365) and the personal connections to other products’ MCP servers that Ping used. When an instance is upgraded to the release that retires them, Ping’s stored data is deleted, as are the sign-in tokens of connected accounts and MCP servers. Comments Ping posted on issues remain as ordinary AI comments, and its user record is kept, deactivated, as their author. Messages Ping already delivered to Slack or by email remain subject to those services’ retention controls, and customer backups may retain older data under the operator’s backup retention policy. To remove the app from a Google or Microsoft account that was connected, use that account’s own security settings.

Slack Integration

This section applies to the Slack integration preview when enabled on your instance. It supplements the general policy above. The original QA sharing pilot sends only confirmed messages. Expanded workflows can process requests, linked conversations, notifications and optional assistant actions when configured. Setup, permissions, troubleshooting and support are available in our Slack integration guide.

Data collected and why

  • Connection data: Slack workspace ID and name, bot user ID, granted permissions, encrypted bot access and refresh tokens, access-token expiry, safe refresh status, connection timestamps and the associated Leera workspace and installing user identifiers. This information is used to authorize delivery, refresh rotating credentials before expiry, revoke the connection, prevent a Slack workspace being claimed by another Leera workspace, and diagnose connection problems.
  • Channel data: channel IDs, names, privacy and membership information used to show and verify a destination. The selected channel is stored with the Leera project or channel rule. Expanded workflows also use Slack user and conversation identifiers, account links, channel rules and notification preferences. A member links their own Slack account with a single-use code sent to them in Slack; the link uses account identifiers, email addresses are not compared, and linking does not grant new project access. Relevant message text, form answers, thread references and file metadata may be stored with requests or synced comments. Attachment copying is on for a new channel rule unless an administrator turns it off; when it is on, up to three permitted files of 5 MiB each may be stored as project attachments, and remaining files stay as links. Copied files follow project access and retention controls. The original QA-only pilot does not collect conversation history.
  • Message and delivery data: the confirmed report summary includes its verdict, counts, commit, environment, issue date, sender attribution and source link. The sender is attributed using their Leera display name, or internal user ID if a display name is unavailable. The Leera instance temporarily stores the outgoing payload and records delivery status, request and channel identifiers, attempt times and error codes. These records support delivery, rate limits and duplicate prevention. Expanded workflows also process configured issue updates and linked replies. Manual QA report sharing does not copy detailed test steps or report attachments. Manual summaries contain only the text the sender reviewed; shared source links retain their Leera access checks.
  • Installation and lifecycle requests: while Slack asks for approval, the Leera instance keeps a hashed, single-use authorization state with the initiating administrator and the page to return to. The instance processes Slack uninstall and token-revocation events to disable invalid connections. Raw lifecycle event bodies are not retained as message history.

Who processes this data

The Leera instance a workspace uses connects to Slack directly: it sends message content straight to Slack and receives Slack events itself; no separate connection service is involved. For Leera Cloud, Leera operates that instance and Leera's Slack app, and stores encrypted access and refresh tokens and connection data in the Leera Cloud database. For self-hosted Leera, the customer creates and configures its own Slack app on its instance, operates that instance and controls its database, logs and backups. Leera does not operate that app or receive its credentials, tokens, events or messages.

Every person with access to the chosen Slack channel, including external people in Slack Connect channels, can read the posted summary. Access to the linked report remains subject to Leera project permissions. Slack processes posted messages under its own terms, workspace settings and privacy policy. If an administrator enables the Slack assistant, relevant conversation context may be sent to the instance’s configured AI provider under its AI configuration and terms. Manual report sharing and explicit pasted-summary sharing do not request a new AI summary. This integration does not use Slack data for advertising or marketing.

Retention and disconnecting

  • Original QA-pilot outgoing payloads are cleared when delivery is completed, fails, is cancelled or has an uncertain outcome; its delivery metadata and daily send counters are eligible for cleanup after seven days. Expanded terminal workflow payloads are eligible for cleanup after seven days and delivery status records after 30 days. Ordinary pending sends expire after one day. Expiry and cleanup are enforced by the running instance worker, so a stopped instance resumes cleanup when its worker restarts.
  • An authorization request expires after ten minutes if approval is not completed. The instance deletes it when it is used, and removes expired requests during its regular maintenance.
  • Connection data is retained while the integration operates. Disconnecting removes stored access and refresh tokens, disables the selected installation’s workflows, clears its destinations, cancels its pending sends and asks Slack to uninstall the app. A send already in progress may still arrive. If Slack cannot be reached, Leera displays that removal from Slack could not be confirmed; a Slack administrator should then remove the app in Slack. Disconnecting still stops new sends.
  • After disconnection, the instance keeps an inactive installation record containing the Slack workspace ID and name, bot user ID, granted permissions, the associated Leera workspace, the installing user's identifier and connection timestamps. It has no automatic deletion deadline; it prevents the Slack workspace from being reassigned to another Leera workspace without authorization. For Leera Cloud, you can request its deletion using the contact below; on self-hosted Leera, the instance administrator controls it.
  • Disconnecting does not delete messages already posted in Slack, issues or synced comments created in Leera, the original QA report, or copies in customer-managed backups. Those follow their respective workspace retention and deletion controls. General operational logs and backups follow the operator’s retention policy; the seven-day delivery-record period does not imply deletion from every backup.

Account-link codes expire and are single use. Account links, requester approvals, channel rules, forms and notification preferences remain while needed for enabled workflows or their resulting records. Issue and comment content follows the instance’s normal retention policy; the delivery-record cleanup period does not delete that content. Ask your instance administrator about these records and deletion requests.

Retired Coordination feature

The separate Coordination feature has been retired. New questions, reminders and reports are no longer sent through it. During the upgrade, queued coordination Slack deliveries are cancelled and their stored payloads emptied, coordination configuration and prompt/reply associations are removed, and coordination task, participant, iteration and response records are deleted. Existing conversations and messages remain as ordinary workspace chat history. Messages already delivered to Slack remain subject to that Slack workspace’s retention controls. Customer backups may retain older data under the operator’s backup retention policy.

Access, export, correction and deletion requests

Email contact@leera.io to request access to, export of, correction of or deletion of Slack integration data held by Leera. Include the relevant workspace URL and enough information to identify your request; do not include credentials or sensitive report content. We verify the requester’s identity and authority before disclosing data or changing ownership records. For Slack integration data on a self-hosted instance, contact its administrator: that data stays on the instance, and Leera does not hold it. Email support@leera.io for connection or delivery help. Neither email contact requires a Leera account.

Figma and FigJam Integration

The Figma and FigJam Preview is optional. An instance administrator configures the Figma app, and each member authorizes their own account in Workspace Settings → Design integrations. Leera stores the Figma account identifier, workspace connection and encrypted access and refresh tokens to request previews on that member’s behalf. This connection requests read access to file content and does not change source files, comments or sharing permissions.

When you request a private image preview, Leera sends the linked file or frame identifier to Figma and checks your connected account’s access. It processes the returned file title and thumbnail or rendered frame image for your current view. These private titles and images use non-cacheable responses and are not stored in shared document content, public pages or document exports. Source URLs and labels you enter yourself are document content and are shared with that document’s audience.

Interactive embeds load only when you choose to load them. Loading an embed connects your browser to Figma, which applies its own account session, sharing controls and data handling. A private preview connection does not sign your browser into that embed. See the Figma privacy policy for Figma’s handling of those requests.

Disconnecting removes your connection in the current Leera workspace and cancels pending connection attempts. A connection you explicitly made in another workspace remains. Remove the app’s access in Figma to revoke it at the provider. Disconnecting does not delete source links already saved in your documents or copies of those documents; their normal sharing, deletion and backup policies still apply.

Self-hosted installations

When you run Leera on your own server, everything your team puts into it stays on that server: projects, tickets, documents, test cases and results, files, AI conversations and your users' accounts. Leera does not receive, store or access that data, except for the limited items described below. You are the controller of your installation's data, and your own policies apply to it. AI providers and integrations an administrator configures connect from your server directly to those providers, not through Leera. An installation with an offline license sends none of the following except crash reports, unless they are turned off, and installer progress if an email was given to the installer.

To license and support an installation, Leera receives:

  • Installer progress, only if you give the installer an email address: that address, a random ID for the install run, whether the install started, stopped on an error or finished, the error message when it stopped (which can name the server's user account and install folder), the server's operating system and the public IP address the report arrives from. We use it only to offer help with an install that failed; it is never used for marketing, and nothing is emailed automatically from it. The address is also saved on your server, to fill in the setup page. We delete the report about a day after the install finishes, or 90 days after its last report if it never does, and sooner if you ask us to; database backups keep it for up to 7 more days. Re-running a failed install reports again under the same ID unless you remove LEERA_INSTALL_REPORT_ID from the install folder's .env file. Skip the question and the installer sends none of this.
  • Registration and license details: the email address and optional installation name an administrator registers with, the installation's random ID, the license issued to it (plan, dates and key), and a referral or redemption code if one is entered. The installation renews its license with its key and ID as it nears expiry.
  • A usage report, daily and when an administrator checks the license: the installation ID, the address the installation is configured with, its version and edition, counts of users, workspaces, projects and active people, its seats and its AI usage totals. It contains no names, email addresses, content or your users' IP addresses. We also keep the public IP address the report arrives from, which is your server's, to show roughly where an installation runs and to check referral purchases for self-referral.
  • Crash reports: when the server hits an error it sends the error, its stack trace and recent log lines, which can include identifiers such as a user's email address; the failing request's address including its query string, method and status; four request headers (user agent, referrer, content type and language); the internal name of the workspace involved; and the installation details above. They go to our error-reporting provider, Sentry, in the European Union, and never include request bodies, cookies or authorization headers. Crash reports are on by default; set LEERA_ERROR_REPORTING=off to turn them off.
  • Email relay: an installation with a connected license and no mail server of its own sends its invitations and sign-in codes through Leera by default. We receive each message, including the recipient's address and first name, the inviter's name and the invitation link or sign-in code, to deliver it. We then keep only a keyed hash of the address and its domain, for rate limiting and abuse prevention. Administrators can turn the relay off.
  • Requests made from the installation: the license key and installation ID, plus what each request needs, when an administrator views plans or starts a purchase (the plan, seats and return address), enters referral payout details (the name, country and payout destination given) or uses another license-based service, and when someone opens the installation's blog.

We use these details to issue and renew licenses, process purchases, deliver messages, provide support, prevent abuse and fix faults, on the basis of our contract with you and our legitimate interest in running a secure, working service. The licensing service runs on Amazon Web Services in the Asia Pacific (Mumbai) region. We keep an installation's records until they are deleted from our licensing system, except installer progress, which follows the schedule above; email contact@leera.io to access or delete them. Checking for updates downloads release information from GitHub, which sees your server's address under GitHub's own privacy policy.

Retention of Your Personal Data

The Company will retain Your Personal Data only for as long as is necessary for the purposes set out in this Privacy Policy. We will retain and use Your Personal Data to the extent necessary to comply with our legal obligations, resolve disputes, and enforce our legal agreements and policies.

Transfer of Your Personal Data

Your information, including Personal Data, is processed at the Company's operating offices and in any other places where the parties involved in the processing are located.

The Company will take all steps reasonably necessary to ensure that Your data is treated securely and in accordance with this Privacy Policy.

Delete Your Personal Data

You have the right to delete or request that We assist in deleting the Personal Data that We have collected about You.

You may update, amend, or delete Your information at any time by signing in to Your Account and visiting the account settings section. You may also contact Us to request access to, correct, or delete any personal information that You have provided to Us.

Disclosure of Your Personal Data

Payment Processing

Online purchases through Leera's checkout are sold by our merchant of record, Polar. Leera shares account and order details, such as your name, email address, and account or license reference, with Polar to associate the purchase with your account. Polar and its payment processors collect the billing and payment details needed at checkout. Leera receives transaction and subscription status to provide access and manage billing. Polar handles this information for payments, subscription management, refunds, and tax obligations as described in Polar's Privacy Policy.

Business Transactions

If the Company is involved in a merger, acquisition or asset sale, Your Personal Data may be transferred.

Law enforcement

Under certain circumstances, the Company may be required to disclose Your Personal Data if required to do so by law or in response to valid requests by public authorities.

Security of Your Personal Data

The security of Your Personal Data is important to Us, but remember that no method of transmission over the Internet, or method of electronic storage is 100% secure. While We strive to use commercially acceptable means to protect Your Personal Data, We cannot guarantee its absolute security.

Children's Privacy

Our Service does not address anyone under the age of 13. We do not knowingly collect personally identifiable information from anyone under the age of 13.

Our Service may contain links to other websites that are not operated by Us. We strongly advise You to review the Privacy Policy of every site You visit.

Changes to this Privacy Policy

We may update Our Privacy Policy from time to time. We will notify You of any changes by posting the new Privacy Policy on this page and updating the "Last updated" date.

Contact Us

If you have any questions about this Privacy Policy, You can contact us by email at contact@leera.io

Leera / Privacy PolicyBack to top