How privileged data is actually handled here.

When a firm uses Ayansar to manage matters, we hold the operational information required to keep the product working - matter metadata (parties, jurisdiction, filing dates, controlling limitation windows), documents assembled or uploaded through the product, captured time entries, invoices, and communications sent through the client portal.

We do not solicit personal information beyond what is necessary to operate the product. Where a matter naturally involves personal data of clients or counterparties, that data lives inside the matter and is scoped to it.

The information a firm brings into Ayansar is used only to operate that firm's account - to render the matter engine, run the deadline lens, generate documents from templates, capture time and produce invoices.

Firm data is not aggregated across customer accounts, is not fed into training corpora for shared models, and is not sold. Product analytics that measure product health are collected in a manner that does not attach to identifiable matter content.

Because matter files routinely include material subject to attorney-client privilege, Ayansar is designed so that access to a matter is scoped by role. A client viewing a matter portal never sees internal notes; a paralegal working one matter cannot browse into an unrelated one. All access is logged.

When support access is required to resolve an issue, it is granted case-by-case, in-product, and revoked as soon as the issue is closed.

The primary data path for a matter - opening it, tracking its timeline, assembling documents, capturing time - does not depend on hidden third-party services. Where a supporting service is used (for example, email delivery for client notifications, or storage infrastructure for uploaded documents), it is engaged under written data-processing terms and disclosed on procurement request.

A firm can request the current list of sub-processors during a procurement review.

Data is retained for as long as the firm's account is active. On account closure, the firm can elect to export its data, or have it deleted; either election is executed within the operational window set out in the terms of service.

For matters that have been closed but where the firm retains an obligation of custody, retention follows the firm's configured period rather than a platform default.

Requests to review, correct, export or delete personal data held within a firm's Ayansar account are directed first through the firm as data controller. Individuals seeking direct contact regarding data-handling questions can reach us through the Contact page.