Privacy Policy
1. Who this covers
casewise is an AI-powered educational study tool for legal study and general legal research, operated from New South Wales, Australia by CaseWise Technologies Pty Ltd. This policy explains what personal information we collect when you use casewise, why, where it is processed, and your choices. For privacy questions, requests or complaints, contact us at info@gocasewise.com.
2. What we collect
- Account data: email address, password credentials (held by our authentication provider; we never see or store your raw password), display name, and optional profile details you choose to add (role, firm or chambers, home jurisdiction, avatar, preferences). If you sign in with Google, Apple or Microsoft, we receive your account identifier and email address from that provider instead of a password.
- Content you submit: questions and prompts, documents you upload, documents you draft in the editor, saved sources, and settings.
- Dictation. When you use the microphone in the message box, your browser's own speech service turns your voice into text. Your voice goes from your browser to that service's provider (Google in Chrome, Microsoft in Edge, Apple in Safari), not through casewise, and it may be processed outside Australia. Casewise receives only the words that land in the message box, and only if you send them.
- Generated content: answers, memos, summaries and citation-check results produced for you.
- Billing data: your plan, subscription status, trial and billing events. Payment card details are collected and held by our payment provider (Stripe), not by us.
- Usage and technical data: authentication events, feature usage and spend metering (used to enforce fair-use limits), error reports you submit, IP address and device/browser information, and service logs.
- Acknowledgement records: timestamps of notices and terms you accept (for example the Terms of Use acceptance, the upload notice and, for practitioners, the practitioner acknowledgement).
- Advertising measurement (on unless you turn it off in Australia and New Zealand; elsewhere, only if you allow it, except on our public website: see section 9): public campaign, ad and creative labels and recognised referring-source categories (such as search, social or email), account attribution, and signup, trial and payment outcomes. Meta receives a SHA-256 hash of your verified email for matching; hashing does not make it anonymous.
We do not ask for, and you must not submit, client-confidential or privileged material, court-restricted material, or personal information about another person.
3. Why we use it
- to provide the service: answering questions, retrieving authorities, showing evidence states, drafting and exporting;
- to operate accounts and subscriptions, enforce fair-use limits and protect the service from abuse;
- to review error reports and improve reliability;
- to communicate service messages (verification, password reset, billing notices, important changes); and
- to meet legal obligations; and
- to measure which advertisements lead to signup and subscription outcomes, unless you turn this off (outside Australia and New Zealand, only with your permission).
When you send an error report, the text of your report is recorded against your account so we can investigate, and where a monitored support inbox is configured the report is also delivered to it. Do not include personal or confidential details in an error report.
We review conversations to find and fix problems, and keep personal details out of anything we record from that review.
We do not use your prompts, uploads or outputs to train casewise or third-party AI models. Our AI providers are engaged on commercial API terms. Provider non-training is not the same as non-retention: providers may retain request content for abuse monitoring under their own policies and service configurations, and while an answer is being written OpenAI stores its working steps, which we ask OpenAI to delete as soon as the answer is complete.
4. Who processes it (providers)
We use the following providers; Meta also processes optional advertising data under its own privacy policy:
| Provider | What it does | What it receives | Where processed |
|---|---|---|---|
| Vercel | application hosting and optional privacy-first usage measurement | requests, service logs and, while analytics is on, page-use and product-event measurements. Our analytics integration does not send legal questions, documents, sources or email addresses | Sydney region configured |
| Meta | advertising measurement, while it is on | public website visits, browser/click and connection information; signup, trial and payment events, payment amount/currency and a SHA-256 email hash for matching. No legal content or private workspace pages | outside Australia, including the United States |
| PostHog | optional product analytics and session recordings on gocasewise.com and every page of the casewise app, while analytics is on | page views, clicks and form submissions (never what you type), clicks that do nothing, page loading speed, error messages with email addresses and sign-in codes removed (outside the sign-up, sign-in and plans pages, only the kind of error), session recordings with typing, page text, titles and file names hidden, the kind of page with ad campaign labels, the campaign, ad and creative labels and source category of the visit that brought you and of your first visit, steps such as plans viewed, checkout, questions asked (with how many in that chat), answers arriving, answers copied, rated, continued or downloaded and sources opened with their kind (never the words of a question, answer or source), trial, payment and cancellation steps with the plan and a cancel reason from our list, answers to our short questions, browser and connection information such as IP address, a random identifier and, once you sign in, a coded account identifier. No legal content, email address or name, unless you write it in an answer to one of our short questions | European Union (Frankfurt), with access from other countries including the United States |
| Supabase | database, file storage and authentication | account data, content, usage records | AWS Asia-Pacific, Sydney |
| Stripe | subscription payments and billing | your payment card details (entered directly with Stripe, never stored by us), billing contact details and subscription status | United States and other locations |
| Anthropic | AI model and web-retrieval API for enabled auxiliary features | prompts, relevant documents, retrieved sources or public source URLs when an enabled feature uses it | outside Australia, including the United States |
| OpenAI | AI model API (answers, research, drafting, checking and embeddings) | prompts, relevant documents, retrieved sources and text being processed per request | outside Australia, including the United States |
| Cohere | search re-ranking API | text snippets being ranked per request | outside Australia, including the United States |
| ZenRows / Zyte | retrieval of public legal sources on our behalf | the public URLs to fetch (not your prompts) | outside Australia |
| Cloudflare (Turnstile) | sign-in anti-abuse check | technical browser signals at sign-in | outside Australia, including the United States |
| optional Google Drive import; optional Google sign-in | the files you choose to import; your Google account identifier and email if you sign in with Google | United States and other locations | |
| Microsoft | optional OneDrive/SharePoint import; optional Microsoft sign-in | the files you choose to import; your Microsoft account identifier and email if you sign in with Microsoft | United States and other locations |
| Apple | optional Apple sign-in | your Apple account identifier and the email you choose to share | United States and other locations |
If you import a document from Google Drive or OneDrive, that file passes from your cloud account to casewise at your instruction.
Some of these providers process data outside Australia, including in the United States, as marked above. Their handling is governed by their terms and our service arrangements, but overseas processing means your information may be handled under another country's laws. If you are not comfortable with that, do not submit content to casewise. We will keep this list current; using a provider not listed here would require updating this policy first.
5. Retention and deletion
- Your account content (conversations, documents, sources, versions) is retained while your account is active so the product works.
- You can delete uploaded documents from your library in-product. Where a stored copy backs a feature (for example document versions), deletion controls are as shown in-product.
- Usage metering and abuse-guard counters are retained for service protection. For the free signup offer, we use a signed device cookie and keyed hashes of account, provider identity, device and IP information to prevent repeated claims. The cookie expires after 30 days; IP signals are removed after 7 days and device signals after 30 days by a daily cleanup job. Offer records linked to a deleted account are retained for 180 days after deletion to prevent repeat claims, then removed by that job.
- You can delete your account from Settings. Before you confirm, we show you what will be deleted. Deleting your account removes your conversations, uploaded documents and their extracted text, drafts and versions, research sessions, saved sources and collections, error reports you have sent us, preferences and profile, and we verify afterwards that no rows remain. Deletion is permanent and we cannot restore the content. Deleting your account also cancels any active subscription with our payment provider; Stripe retains billing records it is required to keep under its own policies.
- Except for the free-offer records described above, we do not currently promise automated expiry schedules.
6. Security
Traffic is encrypted in transit (HTTPS). Data is stored with our named providers with encryption at rest and row-level access controls scoped to your account. Administrative access is limited. No system is perfectly secure and we make no absolute security claims. If a data breach likely to result in serious harm occurs, we will follow the OAIC Notifiable Data Breaches scheme, notifying affected users and the OAIC where required.
7. Age
casewise accounts require you to be at least 18 years old. We collect only the information described here, do not use your content for model training, and do not run advertising based on your legal questions, documents or research activity.
8. Access, correction and complaints
You can access and correct your profile in Settings, and delete your account from Settings. For other access, correction or deletion requests, or privacy complaints, contact us at info@gocasewise.com. If you are unsatisfied with our response you can complain to the Office of the Australian Information Commissioner (oaic.gov.au).
9. Cookies and analytics
casewise uses cookies necessary to keep you signed in and to remember your preferences, including your theme, your measurement choice, and whether the opt-in or opt-out rule applies to you, and, for 30 days after you arrive from one of our ads, which version of our ad page you were shown (the page itself or straight to sign-up), so you see the same one each time. We also try two versions of the top of each ad page. A second cookie (cw_fs, 30 days) remembers which you got, so you see the same each time; it holds only that. If product analytics is on, the version is noted with that page’s events. While analytics is on, we use privacy-first Vercel Web Analytics to measure page use and a small number of product actions, such as starting checkout or exporting a document. We do not send the content of legal questions, documents, sources, emails, client names, account identifiers or matter identifiers through that analytics integration. In Australia and New Zealand it is on unless you turn it off; elsewhere, or if we can’t tell where you are, it stays off unless you opt in. Our public website is different: PostHog, described below, runs there unless you turn it off under Cookie preferences, wherever you are, and we don’t ask first; Vercel Web Analytics starts there only if you allow it. You can change it in Settings, Cookies and privacy, at any time.
While measurement is on (in Australia and New Zealand unless you turn it off; elsewhere once you allow it), Casewise also keeps a first-party journey record of fixed steps such as sign-in attempts, plan selection, checkout handoff and completed answers. A random, first-party session cookie lasts up to 24 hours; signed-in journeys are linked internally to your account so we can compare these steps with actual account and billing outcomes. Records expire after 90 days and linked records are removed when your account is deleted. No legal content, raw error messages, email addresses or private page addresses are included. Account identifiers are not shared with Vercel Web Analytics. Turning measurement off stops new collection. Advertising source information is joined only while advertising measurement is on.
While analytics is on, we also use PostHog on the pages of gocasewise.com and on every page of the casewise app, chat included, to see how people find and use casewise. It records page views, clicks (including clicks that do nothing), form submissions, how quickly pages load and respond, errors (with email addresses and sign-in codes removed, and outside the sign-up, sign-in and plans pages only the kind of error and where it happened) and session recordings of how pages are used, with everything you type and all page text hidden. Boxes where you write are blanked out, page titles, file names and other details on the page are removed, and links and page addresses keep only the kind of page, so PostHog never receives your legal questions, answers, documents or matter details. It also receives steps such as viewing plans, starting checkout, asking a question (and how many you have asked in that chat), whether an answer arrived, and copying, rating, continuing or downloading an answer or opening one of its sources, with the kind of source (never the words of a question, answer or source), and, from our server, when a trial starts, a payment goes through or fails, or a plan is cancelled, resumed or ends, with the plan and the reason you chose from our list when cancelling (never your note, an amount or card details). We keep a copy of your choice with your account so our server follows it too. If you answer one of our short questions, such as why you closed the plans without choosing one, PostHog receives your answer and any words you add, including any name or case detail you write there (we take out email addresses and long numbers). A random PostHog identifier is kept in a first-party cookie shared between gocasewise.com and app.gocasewise.com, and expires 90 days after your last visit. While you are signed in, we link the activity to a coded identifier made from your account, not your email address or name. PostHog stores this data in the European Union. Recordings are kept for 30 days and events for 12 months. Turning analytics off stops recording and removes PostHog’s identifier from this browser; it does not recall data already sent. See advertising measurement for details.
Advertising measurement is optional. In Australia and New Zealand it is on unless you turn it off; elsewhere, or if we can’t tell where you are, it is off unless you allow it. Our public website is different: wherever you are, we keep the visit’s campaign and source labels in your browser unless you turn measurement off, and we don’t ask first. A Global Privacy Control signal turns it off. Separately, whatever you choose, we count visits that arrive from our ads as daily totals for each ad, placement and page. These counts contain no cookie, browser, account or click identifier and no IP address. While advertising measurement is on, Meta Pixel runs on public marketing pages (outside Australia and New Zealand, only if you allow it), and server events report verified signup, trial and payment outcomes. The app sends manually defined image events for public auth/chat entry and verified conversions, using fixed page addresses; it does not load Meta’s JavaScript or automatically inspect private pages. Source evidence can be retained before email verification while measurement is on, and anonymous signup-step records expire after 90 days. We do not send legal questions, documents, answers, client/matter details, raw email addresses or sign-in codes to Meta. Browser attribution expires after 90 days; a choice to turn measurement off lasts about 13 months in this browser and on your account until you change it; linked account attribution and delivery records are deleted with your account. Turning measurement off stops new collection and, when signed in, cancels pending server events. It does not recall data already delivered. See advertising measurement for details, retention and how to change your choice, and Meta’s Privacy Policy.
10. Changes
We show the date of the current version at the top of this page and will notify material changes in-product or by email.
See also the Terms of Use and the signup collection notice.