Privacy Policy

Who we are

AnoLawg is operated by AnoLawg LLC (“AnoLawg”, “we”, or “us”), an Ohio limited liability company. For CRM firm data — matters, contacts, bills, messages entered by a firm or its clients — the firm is the data controller and AnoLawg is the processor. For your AnoLawg account credentials, billing records on our side, public profiles, and service telemetry, AnoLawg is the controller.

How we use your data

We process personal data only for purposes you would reasonably expect, each with a lawful basis under GDPR / UK GDPR and documented under US state privacy laws.

• Provide and secure the service

  Authenticate you, route requests, prevent abuse, deliver the features you or your firm subscribe to.

  Legal basis: Contract performance · Legitimate interest in security.

• Process firm and client data on behalf of firms

  Store and operate on matters, contacts, bills, documents, and messages so firms can run their practice and clients can pay bills and communicate.

  Legal basis: Processor acting on controller (firm) instructions.

• Billing and fraud prevention

  Charge subscription fees, collect bill payments via Stripe Connect, reconcile invoices, prevent payment fraud and chargebacks.

  Legal basis: Contract performance · Legal obligation.

• Safety, legal, and incident response

  Investigate abuse reports, comply with lawful requests, notify affected parties of security incidents within statutory timelines.

  Legal basis: Legal obligation · Legitimate interest.

• Transactional communications

  Account verification, password resets, billing receipts, referral notifications, system status. These are not marketing.

  Legal basis: Contract performance.

• Third-party integration on your behalf

  When you link your Microsoft or Google account, we call Microsoft Graph or Google APIs as you — using the OAuth tokens you explicitly granted — to send email from your mailbox, browse firm storage locations during setup, create matter folders in your drive, attach files to matters, or sync calendar events. We never access these providers without an active user-granted token, and the scope of access is limited to what you approved at consent.

  Legal basis: Contract performance · Explicit consent (OAuth grant).

• Measure and improve AnoLawg

  Understand page performance, product usage, referral flows, billing-flow outcomes, and feature-test results so we can diagnose issues and improve user-facing features. Browser analytics, UTM attribution cookies, Vercel Analytics / Speed Insights, and PostHog browser or server analytics events are tied to analytics consent where that consent applies.

  Legal basis: Legitimate interest · Consent where required by law.

We do not sell your data. We do not share personal data with third-party advertisers, brokers, or for cross-context behavioral advertising. We do not use firm or client data to train public AI models.

Third parties & subprocessors

We use vetted service providers to deliver AnoLawg. Each is bound by a written agreement limiting use of your data to the purposes below. We will update this list and notify firms in advance of any material additions.

Documents: AnoLawg is a passthrough

Unlike most legal-practice tools, AnoLawg does not store customer matter documents.When a firm, attorney, or client uploads a matter document through AnoLawg, the file is transmitted directly from the uploading browser to the firm’s own OneDrive or Google Drive using a short-lived, pre-authenticated upload URL we generate on the provider’s behalf. The file bytes do not traverse AnoLawg servers, are never written to AnoLawg databases or backups, and are never cached.

What AnoLawg does keep is a pointer: the file’s ID in your provider’s system, the file name, the size, the upload timestamp, the uploader’s user account, and which matter it belongs to. That pointer is what lets you find the document again inside the AnoLawg UI and click through to open it in your drive.

Downloads use the same passthrough model in reverse — AnoLawg generates a short-lived signed URL from your provider and the browser fetches the file directly. Bytes do not pass through AnoLawg on the way out either.

If you revoke AnoLawg’s access to your drive (from Microsoft or Google’s account-security page), the files remain in your drive untouched, but the pointers in AnoLawg become dead links until you reconnect. If you delete a document record in AnoLawg, we unlink it — the underlying file in your drive is not affected.

Google API Services — Limited Use disclosure

AnoLawg’s use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. Specifically:

• We use Gmail, Google Drive, and Google Calendar data only to provide the user-facing features the user has explicitly connected their account for — sending email from the user’s own mailbox, browsing Shared Drives or folders during document-storage setup, and creating or attaching files the user has picked or that AnoLawg created, or syncing calendar events the user chooses to connect.
• When a user sends a Gmail message from matter communications, AnoLawg may retain the message body in the firm’s communication record so the firm can preserve its matter history.
• We do not use Gmail, Drive, or Calendar data to serve advertising.
• We do not sell, transfer, or share Gmail, Drive, or Calendar data to any third party, except as necessary to provide and secure the service (e.g., our hosting and database providers), to comply with applicable law, or as part of a merger, acquisition, or sale of assets with successor obligations to honor this policy.
• We do not allow humans to read Gmail, Drive, or Calendar data except (a) with the user’s explicit consent for user support, (b) for security purposes such as investigating abuse, (c) to comply with applicable law, or (d) where the data has been aggregated and anonymized for internal operations.

The same disclosures apply to Microsoft Graph data (Mail.Send, Files.ReadWrite, Calendars.ReadWrite) by policy, even though Microsoft does not require this language.

How long we keep it

We keep personal data only as long as we need it for the purposes above, or as required by law.

For the full per-table schedule (sessions, login events, audit log, messages, bills, email logs, invites, and deleted-user residue), see our internal data retention policy.

Privileged communications

Messages exchanged in a matter’s Client Portal channel (firm-to-client) and messages exchanged in an accepted referral channel (CRM sender to recipient attorney or expert) are treated by AnoLawg as attorney-client privileged by default. Each channel carries a privileged metadata flag, and the ClientMessage database table mirrors the same flag on every stored message. Colleague DMs and informal group chats are not flagged as privileged unless the conversation is matter-scoped.

The flag constrains AnoLawg’s own access in two ways:

• Webmaster impersonation. An AnoLawg webmaster can impersonate a firm user for support and incident response under the controls described in the security page. Impersonation into a privileged channel additionally requires a written reason beyond the standard impersonation reason, plus an attached legal-review flag in the audit record. Sessions that do not satisfy both requirements are rejected at the chat layer.
• Firm-scoped message exports. Exports initiated by a webmaster or firm admin redact rows where privileged = true unless the export is accompanied by an explicit client-consent record naming the matter and scope.

Every impersonation and every export writes an immutable audit row containing the actor, the target, the stated reason, and the legal-review flag when applicable. Firm admins can request a copy of the audit records that touched their firm’s data.

Your rights

Depending on where you live, you have some or all of the following rights. We will respond to verified requests within 30 days (or the shorter period your local law requires).

• Access a copy

  Request a copy of the personal data we hold about you. CRM users can also ask their firm admin for an export.

• Correct or update

  Fix inaccurate or incomplete data directly in your account settings, or by emailing us.

• Delete

  Request deletion of your personal data, subject to legal retention obligations (tax, audit, active disputes) we must honor.

• Portability

  Receive your data in a portable, machine-readable format (JSON or CSV).

• Object / restrict

  Object to or restrict specific processing activities that rely on legitimate interest.

• Lodge a complaint

  EEA/UK residents can complain to their local supervisory authority. US state residents may have analogous rights under CCPA/CPRA, VCDPA, CTDPA, and similar statutes.

To exercise any of these rights, email privacy@anolawg.com. We may ask you to verify your identity before we act on the request. If you use an authorized agent, we will require written proof of authorization and may verify the request directly with you. You may appeal a denial by replying to our response; we will respond to appeals within 45 days.

State-specific privacy rights (United States)

AnoLawg is offered to residents of every U.S. state. The following state laws create additional or overlapping rights for their residents. These rights are in addition to the core rights listed above, and we honor them for the states that have enacted a comprehensive privacy statute in force as of the version date of this policy.

• California (CCPA / CPRA)

  Right to know, access, delete, correct, and portability; right to opt out of "sale" or "sharing" for cross-context behavioral advertising (we do not sell or share in that sense); right to limit the use and disclosure of sensitive personal information to what is necessary to provide the service; right to non-discrimination for exercising these rights. Complaints may be filed with the California Privacy Protection Agency. We do not use sensitive personal information for purposes outside those disclosed here. We do not knowingly sell or share the personal information of consumers under 16.

• Virginia (VCDPA), Colorado (CPA), Connecticut (CTDPA), Utah (UCPA), Texas (TDPSA), Oregon (OCPA), Montana (MCDPA), Iowa (ICDPA), Tennessee (TIPA), Indiana (ICDPA), Delaware (DPDPA), New Hampshire (NHPA), New Jersey (NJDPA), Kentucky (KCDPA), Maryland (MODPA), Minnesota (MCDPA), Nebraska (NDPA), and Rhode Island (RIDPA)

  Right to confirm processing, access, correct, delete, and receive a portable copy of personal data. Right to opt out of targeted advertising, sale of personal data, and profiling in furtherance of decisions that produce legal or similarly significant effects. We do not engage in any of these activities; exercising these opt-outs therefore has no practical effect on our processing, but you may still submit a request and we will confirm our status in writing. Where required, we obtain opt-in consent before processing sensitive data (as defined by each statute).

• Nevada (SB 220)

  Right to opt out of the sale of "covered information" as defined by Nevada law. We do not sell covered information.

• All other states

  Residents of states without a comprehensive privacy statute can still exercise the core rights listed above. We apply a single high-water-mark standard across the United States rather than varying our practices by state.

To exercise any state-specific right, email privacy@anolawg.com and identify the state whose law you are invoking.

International transfers

AnoLawg is operated from the United States. If you access the service from the EEA, the UK, or elsewhere, your data will be transferred to the US and may be processed by subprocessors located in other countries. We rely on Standard Contractual Clauses (2021/914/EU) and the UK Addendum, together with supplementary technical safeguards, as the transfer mechanism. A copy of the applicable SCCs is available on request.

Children

AnoLawg is not directed to children under 16, and children may not create accounts unless their firm or legal representative has authorized access. Firms may enter information about minors as part of client, contact, matter, document, billing, or communication records; for that firm-controlled matter data, the firm is the controller and AnoLawg acts as processor. If you believe a child has created an unauthorized AnoLawg account or provided personal data directly to us outside firm-controlled matter records, please contact us and we will address it.

Security

Detailed controls — encryption, authentication, penetration testing, incident response — are described on our security page. No system is perfectly secure, but we apply layered, least-privilege controls and meaningful audit logging so that incidents are detected and contained quickly.

OAuth access and refresh tokens for linked Microsoft and Google accounts are encrypted at rest using authenticated symmetric encryption with a deploy-time OAuth encryption key; plaintext tokens exist only in server memory for the duration of an API call. Passwords are hashed with scrypt. TOTP / WebAuthn secrets for webmaster MFA are encrypted under a separate per-deploy key.

Changes to this policy

When we make material changes, we update the version stamp at the top and — for firms and paid profile holders — notify the account owner by email at least 14 days in advance. Continued use of the service after the effective date means you accept the updated policy.