LegAI Assistant, Inc. ("Company") is a Delaware, U.S., corporation that operates the Kurzly mobile app and web service. This Privacy Policy explains how we collect, use, store, and protect personal information. We comply with U.S. federal and state privacy laws (including, where applicable, California, Virginia, Colorado, and other state laws). Where you are located in the EU/EEA, the UK, Korea, or another jurisdiction, we also comply with applicable local law (e.g., GDPR, Korean PIPA) to the extent it applies.
1. Information We Collect
- Account data such as email, name, organization details, profile information, authentication tokens, and contact preferences.
- Workspace data including cases, evidence, timelines, summaries, analyses, chats, plans, and related metadata; and, where community features are offered and you use them, community data such as posts, comments, and report records.
- Email you add to a case: the whole message (headers, body and attachments), including the sender and recipient addresses, subject and date in it. For email forwarded to a case email address, we also store the address it was sent to and the result of our sender check; for email added with the Gmail add-on, Gmail’s message and thread IDs. When you link the Gmail add-on, we store that Google account’s ID and email address, how and when it was linked, when you accepted the add-on’s notice, and when it was last used. If you open the add-on before linking, we briefly store that Google account’s ID and email address with a link so the link page can show the account. The link works for 15 minutes and is deleted once used, or usually within a day after it expires.
- Usage data such as device identifiers, IP address, browser/OS information, timestamps, feature usage, logs, and cookies. This may include an anonymous device identifier used to count landing/marketing page visits (cookie or local storage).
- How you found us: when you create an account, the campaign tags on the link you first followed, whether it was an ad click (which kind of ad click id only, never its value), the domain of the site that linked to us (never the full address), the first page you opened and when, and whether you used the web or our app. It is recorded once on your account so we can tell which channels bring people. Before you accept cookies, it is not stored on your device.
- Plan and usage metering such as subscription tier and monthly AI usage allowance and consumption (for fair use and billing).
- Billing data such as invoicing contact details and payment method references (full card numbers are not stored by us).
2. How We Use Information
- To operate authentication, case/evidence management, AI analysis, chat, export, and collaboration; and, where community features are offered, posts, comments, reporting, and moderation.
- To improve performance, reliability, and security, including abuse prevention.
- To provide customer support and service notices.
- To comply with legal obligations and protect rights and safety.
3. AI Processing and Model Policy
- AI features, including summaries, timelines, analysis, legal research, and chat, run on Google’s Gemini models through Google Cloud Vertex AI. The input data each feature needs is sent to Vertex AI for processing.
- Before your first AI action, we ask for your separate consent to send the case material that action needs to Google’s Gemini models on Google Cloud Vertex AI, and record when you gave it. AI features stay off until you agree. To withdraw your consent, email privacy@kurzly.net from the address on your account: we remove the recorded consent, and AI features stop for your account until you agree again. Deleting your account also ends it. Withdrawing does not undo processing already done, and it does not delete your cases or the AI outputs already in them.
- Evidence files you upload are read by the same Gemini models on Vertex AI. Gemini transcribes audio and video, and for video it also analyzes what appears on screen. Gemini reads images and scanned PDFs directly. We do not use a separate speech-recognition or optical character recognition (OCR) service.
- In chat, the AI can use tools built into Vertex AI: web search with Google Search, opening a web link you share, and running calculations as code. These tools run within Google Cloud. Under Google’s terms for its web search feature (Grounding with Google Search), Google keeps logs of search queries and related context for up to three days, not linked to you or to us, and uses them only to debug that feature.
- When AI retrieves reference material, minimal request data (such as search queries) may be sent to external legal and web search providers to fetch public sources only. Your case documents are not transmitted, although a query the AI composes may contain case-related terms such as names or dates.
- The external providers we use, by jurisdiction: Korea — National Law Information Center Open API. United States — CourtListener (case law) and Congress.gov (federal bills and statutes). European Union — EUR-Lex. Germany — Gesetze im Internet and EUR-Lex. United Kingdom — legislation.gov.uk. Japan — e-Gov statute API. All jurisdictions — Google web search (Grounding with Google Search on Vertex AI). Retrieved results are used only to produce your answer; we do not accumulate or redistribute them.
- We do not use your case data to train or fine-tune AI models. The Google Cloud terms that govern Vertex AI also prohibit Google from training its models on customer data.
- Processing is limited to service delivery purposes and subject to provider data protection terms.
3A. Google User Data (Gmail Add-on, Google Drive, Gmail Import)
- The Kurzly add-on for Gmail is a Google Workspace add-on that runs inside Gmail. We are rolling it out, so it may not be available to you yet. When you install it, Google asks you to allow three things: running as a Gmail add-on (gmail.addons.execute), reading the email you have open when you use the add-on (gmail.addons.current.message.action), and seeing your Google Account email address (userinfo.email).
- The add-on reads one email, the one you have open, and only when you choose Add to case. It saves that email as evidence in the case you pick, as Gmail stores it (headers, body and attachments), and attachments of supported types also become their own evidence. It stores Gmail’s message and thread IDs so the same email is not added twice. It does not search your mailbox or read other email. The access Gmail grants for that request is used only for it and is not stored, so Kurzly cannot go back and read your mail later.
- To show your cases, the add-on needs your Google account linked to your Kurzly account. If you sign in to Kurzly with that same Google account, it links automatically; otherwise you sign in to Kurzly on the link page and connect there. That page may ask you to Continue with Google to show the Google account is yours. This only checks who you are, grants no Gmail or Drive access, and Kurzly does not keep that sign-in. Once linked, the names of the cases you can edit (up to 100, most recently updated first) and your Kurzly account email are sent to Google so Gmail can show them in the add-on.
- You can disconnect under Account → Gmail add-on. If you sign in to Kurzly with that same Google account, the add-on links again the next time you open it in Gmail, so to stop it completely, uninstall it in Gmail. Email you already added stays in its case until it or the case is deleted. Deleting your account deletes email you added to your own cases; email you added to someone else’s case is part of that case and stays there (section 4).
- Google Drive: signing in with Google does not ask for any Drive access. Kurzly asks for Drive access only when you open Import from Google Drive, and only for the files you pick (drive.file). With it, Kurzly can open only the files you choose in Google’s file picker; it cannot see your other files or list your folders. Your browser downloads the files you pick and saves them to your case as evidence, with Google Docs, Sheets and Slides saved as PDF. Kurzly only reads these files and never creates, changes or deletes anything in your Drive. The Drive access token is used only in your browser and is never sent to our servers. If you signed in with Google on the web or imported from Drive before November 4, 2026, your Google Account (myaccount.google.com/permissions) may still list the read-only Drive access (drive.readonly) Kurzly asked for then. Kurzly no longer asks for it, and you can remove it there.
- Gmail import (gmail.readonly, on the web) is switched off, so no one can connect Gmail or import from it now. While it was on, connecting Gmail asked for read-only Gmail access through a separate Google consent. Kurzly used that access only to find messages related to your case and save the ones you picked as evidence, and never synced your mailbox or imported in the background.
- If you connected Gmail import, an encrypted Gmail refresh token may still be stored on our servers. It is not used while the import is off. You can cut off that access in your Google Account (myaccount.google.com/permissions) and ask privacy@kurzly.net to delete the stored token; deleting your Kurzly account revokes the token at Google and deletes it. Email imported that way (.eml files and message and thread details) stays in its case as evidence, under the same retention and deletion rules as other evidence.
- Data from Google, such as email you add with the add-on or import from Gmail and files you import from Drive, is handled like your other evidence. It is stored on Google Cloud (section 5), read by Google’s Gemini models on Vertex AI as each AI feature needs (section 3), and timestamped by sending only its SHA-256 fingerprint, never its contents, to the services in section 5A. A search query the AI writes may include words from it, such as a name or date (section 3), and previewing a Word, Excel or PowerPoint file sends it to the Microsoft viewer in section 5A. The case’s owner and collaborators can see it; anyone else only if you share it, for example with a brief link.
- No one at Kurzly reads data we receive from Google unless you ask us to (for example by allowing support access, which shows our support team your case titles and evidence file names for 7 days; for an email, the file name is its subject line), it is needed for security, such as investigating abuse, or the law requires it.
- We do not sell Google user data, use it for advertising or credit decisions, or give it to data brokers, and we do not use it to create, train or improve any AI or machine-learning model.
- Kurzly’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy and the Google Workspace API User Data and Developer Policy, including the Limited Use requirements.
3B. Email Forwarded to a Case Address
- We are rolling out case email addresses, so they may not be available to you yet. Where they are, each case can have its own email address (…@in.kurzly.net). Only people who can edit the case, including its owner, can create it, see it, turn it off or replace it with a new one. Mail sent to an address that is off or was replaced is not saved.
- Mail sent to the address is received and held by Mailgun, our email provider in the United States (section 5A), and our servers fetch it over an encrypted connection. After handling it, we ask Mailgun to delete its copy, and Mailgun keeps received mail for up to 3 days.
- Mail becomes evidence automatically only when all of these hold: the sender’s email service signed it (DKIM, checked with DMARC) in a way that shows it came from the verified email address of a Kurzly account that can edit the case; that signature also covers this case’s address in the To or Cc line; that person has agreed to AI processing; and Mailgun’s spam filter did not mark it as spam.
- Anything else waits in the case’s review list instead of becoming evidence. That usually includes mail from other people, mail with the address in Bcc, and mail sent from Outlook services such as Microsoft 365, whose signatures leave out the To and Cc lines. The list shows the sender, subject, size, arrival time and why it is waiting, and only people who can edit the case can see it.
- An editor can choose Add to case, which makes it evidence, or Discard, which deletes the original. If no one chooses within 14 days of its arrival, it drops off the list and is deleted (section 4). The editor who adds it must also have agreed to AI processing. While it waits, the original is kept apart: no one, not even the case owner, can open it in Kurzly, and AI does not read it before it becomes evidence.
- We do not save mail over 25 MB or mail over our receiving limits. Per address and hour, the limits are 30 emails added automatically, 30 waiting for review that the case’s editors sent, and 30 waiting for review from anyone else. Separately, an address accepts at most 150 emails an hour of any kind. Up to 200 emails a day are added automatically per case owner, and each case holds up to 50 emails waiting for review from its editors and 50 from anyone else. The case’s email address panel shows how many emails were not saved. Case email addresses are not available for sample cases or password-protected cases.
- Once mail becomes evidence, it is handled and kept like your other evidence (sections 3 and 4), and attachments of supported types become their own evidence.
- Anyone who knows the address can send mail to the case’s review list, and anyone who can view the case can see the address in the To line of a stored email, so keep it private.
4. Retention
- Personal data is retained only as long as necessary for the stated purposes and legal obligations.
- After account closure, workspace data is deleted or anonymized unless legal retention applies. Cases created in incognito mode are deleted automatically after they expire. Where you have used community features, posts and comments may be removed on request or under policy; report and moderation records may be retained for safety and compliance for a limited period.
- Deleting a case deletes the case and everything attached to it: its evidence records and files (including files collaborators uploaded), its analysis, notes and history, generated documents, integrity certificates, any share links made from it, and its email address and the mail waiting for its review. Deleting your account does the same for every case you own, and also deletes your profile, your files and your other records, including the link between the Gmail add-on and your Google account. What remains: your name, email and messages in cases you joined as a collaborator, and email you added to those cases with the Gmail add-on or a case email address (all part of that owner’s case); and billing records that Stripe, Apple and Google keep under their own policies.
- Forwarded email waiting for review can be added to its case for 14 days after it arrives; after that it is deleted. If an editor adds or discards it sooner, the original is deleted then, and only a record without the sender or subject stays, for 3 days. The deletion itself can take a few more days. Waiting email is also deleted with its case. Mailgun deletes its copy within 3 days (section 5A). Turning a case address off or replacing it does not delete email already saved.
- Backups: we keep backups of our database for up to 98 days, and deleted uploaded files stay recoverable for 7 days. Data you delete, including a deleted case or account, can therefore remain in backups for up to 98 days before it is permanently removed.
- Billing records (such as invoices, payments, and subscription history) are kept for as long as tax and accounting laws require, including after you close your account. Stripe and the app stores keep their own records under their own policies.
5. Sharing and Processors
- We may engage cloud, authentication, payment, analytics, support, legal/web search, email receiving, and abuse-prevention (App Check / reCAPTCHA Enterprise) processors as needed to provide the service. The providers we use today are listed in section 5A.
- Hosting, our database, storage of uploaded files, and account authentication run on Google Cloud Platform and Firebase (Cloud Firestore, Cloud Storage, Cloud Run, Firebase Authentication, Firebase App Check). Account information and your case and evidence data are stored and processed on that infrastructure.
- Processors are bound by confidentiality and security obligations and may not use data for unrelated purposes.
- We may disclose information, including case content, when we believe in good faith that the law requires it, for example in response to a valid subpoena, court order, search warrant or other legal process, or to protect someone’s safety. Storing a case in Kurzly does not make it protected by attorney-client privilege.
5A. Service Providers We Use
- Google Cloud and Firebase (Google LLC): hosting, sign-in, database, file storage, push notifications (Firebase Cloud Messaging), and abuse prevention (Firebase App Check with reCAPTCHA Enterprise).
- Google Vertex AI (Google LLC): AI processing of the case data each feature needs, as described in section 3. AI chat answers are written in Japan (Tokyo region; see section 6).
- Stripe, Inc.: payments for subscriptions bought on the web. You enter card details on Stripe’s checkout page; we never receive full card numbers.
- Apple (App Store) and Google (Google Play): payments and refunds for subscriptions bought in our mobile apps.
- RevenueCat, Inc.: keeps track of in-app subscription status. It receives your Kurzly account ID and your App Store or Google Play purchase records.
- PostHog, Inc. (United States): product analytics such as pages viewed and features used, linked to your account ID once you sign in (we do not send your email). On the website, only after you accept analytics cookies; in our iOS and Android apps it is on by default and can be turned off under Account → Cookie settings.
- Functional Software, Inc. (Sentry): error reports, such as the page, browser, and error message, used to find and fix bugs.
- Google Analytics for Firebase and Firebase Performance Monitoring (Google LLC): usage statistics and page-load measurements. On the website, only after you accept analytics cookies; in our iOS and Android apps they are on by default and can be turned off under Account → Cookie settings.
- Google Ads (Google LLC): conversion measurement, which tells us whether a sign-up came from one of our ads. Only on the website, and only after you accept analytics cookies; never in the mobile apps.
- Google Workspace (Google LLC): sends our service emails, such as invitations and notifications, and hosts our support and privacy mailboxes.
- Mailgun Technologies, Inc. (United States), once case email addresses are offered: receives email sent to a case email address and holds it until Kurzly fetches it. It receives the whole email, including attachments, keeps it for up to 3 days, and keeps delivery logs for 1 to 30 days depending on our Mailgun plan. Nothing is sent to it unless someone emails a case address (see section 6).
- Microsoft Corporation (Office Online viewer): when you preview a Word, Excel or PowerPoint evidence file, a private download link to that file is sent to Microsoft, which fetches the file to display it. Nothing is sent if you do not preview such a file.
- OpenTimestamps public calendar servers and FreeTSA (freetsa.org): when evidence is processed, a SHA-256 fingerprint (hash) of the file is sent to these timestamping services to prove when the file existed. They receive only the fingerprint, never the file or its contents.
- The legal and web search providers listed in section 3: they receive search queries only.
5B. Cookies and Local Storage
- Necessary (always on, because the service does not work without them): session (the sign-in cookie, up to 5 days, not readable by page scripts); Firebase Authentication’s sign-in state, kept in your browser’s local storage; legai-language and legai-language-user-set (your language, 1 year); legai-sidebar-collapsed (a layout preference, 1 year); kurzly_brief_share_unlock (remembers that you opened a password-protected shared brief); case:<case ID>:briefEdit (an unsaved edit of a lawyer brief, kept only on this device until you save or discard it, sign out, or delete the case; a copy older than 30 days is discarded); and the entries reCAPTCHA Enterprise stores so Firebase App Check can tell people from automated traffic.
- Your cookie choice: cookieConsentStatus and the time you chose (cookieConsentDecidedAt) are saved in local storage, not a cookie, so we remember your answer.
- Home-page headline test and visit count: on your first visit to our home page we set kurzly_hero, a cookie (about 1 year) that keeps showing you the same version of the headline we are testing. On the English home page we also save kurzly:heroVariant (the version shown) in local storage. These two hold only which of three headline versions you see, so they are set without waiting for the cookie banner, and they are not shared with third parties. The random ID we use to count unique visitors (kurzly:marketingDeviceId, sent only to our own server) is created only after you accept analytics, and Reject deletes it.
- Analytics and advertising (only after you accept): Google Analytics for Firebase sets the _ga and _ga_<ID> cookies (up to 2 years), used together with Firebase Performance Monitoring and Google Ads conversion measurement; PostHog stores a ph_<project>_posthog cookie and a local storage entry. On the website, none of these are loaded unless you accept. In our iOS and Android apps, analytics other than Google Ads is on by default.
- To change your choice or withdraw consent, use Cookie settings (at the bottom of our pages, in Account, or at the top of this page) and choose Reject. Analytics stops at once and the identifiers listed above are deleted. In the mobile apps, use Account → Cookie settings. You can also write to privacy@kurzly.net.
6. Data Location and Multi‑Jurisdiction
- We are a U.S. company. Data may be stored and processed in the United States and in other regions where we or our service providers operate (e.g., Korea and Japan).
- AI chat answers are written by Gemini in Google Cloud’s Tokyo region (asia-northeast1) in Japan, so your questions, the conversation, and the case material needed to answer them are processed there. So that the next question about the same case is answered faster, the case material may be held there temporarily, for about 10 minutes after it was last used. Supporting steps, such as classifying a question or suggesting follow-up questions, run on Google Vertex AI’s default route (e.g., the United States), and if the Tokyo region has not started answering after about 15 seconds or is busy, the same request may also be sent to the same Gemini model on that route. Either way it is processed by Google LLC, and the terms in section 3, including no training on your data, apply unchanged.
- Email sent to a case email address is transferred to Mailgun Technologies, Inc. in the United States (a Sinch company; privacy contact dpo@sinch.com). What is transferred: the whole email (headers, body and attachments), the sender and recipient addresses in it, and delivery records. When and how: each time mail is sent to a case address, it travels over the email network to Mailgun’s servers in the United States, and our servers fetch it over an encrypted connection. Purpose and retention: to receive the mail and pass it to Kurzly; Mailgun keeps the mail for up to 3 days and delivery logs for 1 to 30 days depending on our plan. How to refuse, and what happens: if no case email address is created, or no one sends mail to it, nothing is transferred. Mail sent to an address after it is turned off or replaced still passes through Mailgun; Kurzly does not save it and asks Mailgun to delete its copy. You can upload email files (.eml or .msg) instead, and everything else works the same.
- We comply with U.S. federal and state privacy laws, including where applicable the California Consumer Privacy Act (CCPA/CPRA), Virginia CDPA, Colorado CPA, and similar state laws. Where you are in the EU/EEA, the UK, Korea, or another jurisdiction, we comply with applicable local law (e.g., GDPR, Korean Personal Information Protection Act) to the extent it applies to our processing.
- Residents of California and other U.S. states with privacy laws, and of the EU/EEA, UK, or Korea, may have additional rights (access, deletion, portability, opt‑out of sale/sharing, correction). Submit requests to privacy@kurzly.net.
7. Your Rights
- Under U.S. and applicable state law you may request access, correction, deletion, and related rights. California and other state residents, and users in the EU/EEA, UK, or Korea, may have additional rights under local law (e.g., CCPA, GDPR).
- Requests can be submitted to privacy@kurzly.net or +1-978-878-7437. Identity verification may be required.
8. Security Measures
- We use encryption in transit and at rest, access controls, and security monitoring.
- Access to personal data is restricted on a need-to-know basis and auditable.
9. Children's Privacy
- The service is not intended for individuals under 18.
- If we discover child personal data, we will delete it promptly.
10. Policy Updates
- We may update this policy to reflect legal or service changes.
- Material changes will be announced before they take effect.
11. Contact
- Privacy Officer, LegAI Assistant, Inc.
- Email: privacy@kurzly.net
- Phone: +1-978-878-7437
- Address: 1111B South Governors Avenue, Dover, DE 19904, USA