Is Grok AI Private for Practice Work in 2026?

Assess Grok privacy before using practice information. Check the product, account controls and data path, then define what staff can enter and retain.

Published
Updated

It depends: Grok’s privacy protections depend on the product, account and settings you use. Approve a specific use before staff enter confidential practice information.

A training opt-out controls one use of your content. The practice must also assess storage, provider access, sharing and its authority to disclose client information.

Identify the Grok Product and Account

Record the access route before assessing Grok privacy. A paid personal subscription, a business workspace and an application using the API can have different terms.

Access routeApplicable documentsWhat the practice must identify
Standalone consumer website or mobile appConsumer terms, privacy policy and Consumer FAQsSigned-in account, training setting and chat mode
Grok within XX terms, X privacy policy and About Grok helpX account, training and personalisation settings
Grok Business or Enterprise team workspaceBusiness agreement and the workspace’s documented termsTeam, licensed user and agreed retention
An application using the Grok APIEnterprise terms, data processing addendum and API documentationAPI team, application operator and storage outside the model provider

Grok’s standalone privacy policy distinguishes its consumer service from business processing and Grok on X. An X login to the standalone service does not make it the same service as Grok within X.

The Grok Business user guide distinguishes personal and team workspaces. Staff must select the approved team workspace before starting work. A business licence alone does not show where a particular conversation occurred.

Map the Information Sent

List what the proposed task sends beyond the visible prompt. For a document summary, include the uploaded file, its identifying details and any earlier conversation used as context.

The standalone policy covers prompts and files, including images, audio and video. It also covers generated responses, account information and technical usage data. Personal information supplied in a prompt can reappear in an answer.

For connected services, record the permitted content and who can access it. For an API application, include the application’s own logs and saved conversations. Provider deletion does not automatically delete copies held by that application.

Check Data Use and Retention Controls

Assess training separately from retention and sharing. Each question changes what the practice can permit, even when another setting is satisfactory.

Consumer Website and Apps

The Consumer FAQs say content and responses can be used for training. Turning off Improve the Model excludes new conversations from training. Private Chat also excludes its content from training. Voluntary feedback can still be used for training.

Private Chat hides a conversation from the user’s history. The privacy policy describes deletion within 30 days, subject to legal, compliance or safety retention. Treat it as a limited-retention mode, not immediate deletion.

The Consumer FAQs also describe retention exceptions for de-identified or pseudonymised conversations disassociated from the account. Save the applicable wording when assessing deletion requirements.

The Consumer FAQs permit limited personnel review for specified business purposes. The privacy policy also allows disclosure to contracted service providers and related companies.

Consumer share links expose conversations to people who receive them. Publicly shared links can be indexed. The documented share-link controls allow access to be revoked, but the practice must account for copies already taken by recipients.

Grok Within X

X’s About Grok help says public X data and Grok interactions, inputs and results can be shared for model training. It documents separate settings for training and personalisation.

X also describes a feedback exception to its training opt-out. Its conversation-deletion instructions specify removal within 30 days, with security or legal exceptions. X advises users against entering personal, sensitive or confidential information into Grok conversations.

Record the X settings themselves. A screenshot of the standalone website’s training setting cannot establish the setting for Grok within X.

Business Workspaces and the API

The Enterprise FAQs describe business inputs and outputs as excluded from training, while allowing an express agreement to training in exchange for credits. Read the practice’s actual agreement and any optional data-sharing choice.

Grok’s administration documentation lets organisations cap sharing at Private, Team, Organization or Public. Public conversation links can reach people outside the team. Set and record the permitted level.

The business user guide identifies custom retention for Enterprise. Retain the agreed period and exceptions instead of assuming the consumer chat rules apply.

The API security documentation says inputs and outputs are not used for training without explicit permission. Its default is 30-day request and response storage for abuse auditing.

The same documentation describes team-level Zero Data Retention. Where enabled, it prevents persistence of API prompt and response content to disk, with restrictions on storage-dependent features. Confirm the team setting and the application’s separate storage before relying on it.

A no-training term leaves other processing in place. Review the business data processing addendum for subprocessors and disclosure arrangements. Include any onward transfer through connected services in the practice’s assessment.

Fictional Practice Decision

A practice wants help drafting a generic document-request email. Its permitted prompt uses an invented entity and asks for wording only. Staff exclude client names, tax identifiers and the actual client file.

If staff paste a real engagement letter instead, client details enter the service as input and can appear in the response. Training opt-out does not remove that disclosure or establish permission for it.

For an approved business workflow, record the team workspace and agreed retention before use. For an API workflow, trace the same input through the application’s logs as well as the provider’s processing. Keep downloaded answers within the practice’s approved records.

Make and Retain the Practice Decision

Approve a defined task and information category, with a named person responsible for the decision. A setting labelled private cannot establish legal compliance or satisfy every client confidentiality requirement.

The OAIC’s guidance on commercially available AI recommends avoiding personal information, particularly sensitive information, in publicly available generative AI tools. Its guidance covers personal information in outputs as well as inputs.

The TPB’s AI guidance requires client permission before divulging client information to a third party. That can include entering information into an AI tool, depending on its configuration and use.

Use the following approval record before staff begin.

  1. Name the product and permitted account. Record the team or workspace and who administers access.
  2. Define permitted information. Allow public source material or invented examples for general drafting. List confidential information that staff must exclude, including TFNs and credentials.
  3. Retain the terms and settings. Keep the relevant agreement, training choice, retention exceptions and sharing permissions with the decision.
  4. Set the output review. A practitioner checks tax statements against primary sources, checks calculations and removes invented facts before an answer reaches a client.
  5. Define access removal. When staff leave or approval ends, revoke organisational access, disconnect integrations and rotate any exposed API credentials. Apply the agreed retention procedure to provider and local copies.

Before approving a client-information workflow, document the authority for disclosure and the assessment of storage, recipients and overseas handling. If the proposed task exceeds the approved category, keep that information out until the practice approves the expanded use.

Verify the decision with an invented example. Confirm that staff use the approved workspace, that sharing stays within the permitted audience and that the reviewed output is retained correctly. Record what was observed without treating it as proof of backend deletion.

One client form. One finished return.

Your client completes one guided form. Tax Genie checks it, chases mistakes and sends the details to your engagement letter and tax software.

See how Tax Genie works

Made for Australian accounting firms

Tax GenieSee how Tax Genie works