Privacy and safe sharing

Identify the service first#

Before changing settings, note whether you are on grok.com, in the standalone app, on X or using an API-connected tool. For a work account, check the workspace name too. The steps below were verified in official guidance, not personally tested in a signed-in Slovak account.

Separate four questions: is content used for training, does it personalise your answers, does it remain in history, and can other people access it? Answering one does not settle the others.

For Bot, continue to Grok Bot privacy and permissions. Before connecting work accounts, decide which materials it should access and which actions it should first submit for review. Do not assume ordinary chat settings also apply to Bot.

Training and personalisation from X#

After changing a setting, return to that screen and check its state. If labels differ in your version, compare the explanatory text rather than a similar name alone. Check personal and work accounts separately.

Practical choice: if you do not want content used for training, disable the relevant option before your first sensitive task. Still send only the material the task needs.

Memory is not training#

Cross-chat memory carries context about you between conversations. Personalisation from X uses a different data source. Review them separately.

Not verified: current memory availability for a Slovak account and the exact controls for viewing, correcting or deleting it. Do not assume that disabling training also disables memory. Look for the explanation of memory or history in settings; if unavailable, provide a short context with each request and ask support about availability.

Context for this task: I write for Slovak beginners. Answer in Slovak, explain abbreviations and separate facts from suggestions. Use only the information supplied in this request.

This avoids making your result depend on unclear saved preferences. A prompt does not change the service’s technical retention rules.

Private Chat#

1. Before typing, look for Private Chat if your account offers it.
2. Check that it is active in this conversation; if uncertain, do not start with confidential data.
3. Save the result you need somewhere you control and check that it opens before ending the session.

For an anonymised test, replace names with “client A” and “colleague B”. Keep identifiers, passwords and keys out of example prompts.

Review a public link as a publication#

1. Read everything you intend to share, including the prompt and attachments. Hiding text in a preview is not a substitute for removing sensitive source material.
2. Remove unnecessary personal information. If the result alone is enough, prepare a separate cleaned text.
3. Before sending the generated link, open it signed out and inspect what is accessible.
4. To revoke access, use the documented workflow above and test the link signed out again. Without that check, do not claim it has stopped working.

If revocation is unavailable or you cannot verify the scope, do not share a sensitive conversation. Create a new document containing only the necessary result.

Export, deletion and your account#

Before bulk deletion, prepare an export using the data settings above. Open the downloaded archive, check a sample of conversations and store it with appropriate access controls. The export may itself contain sensitive information.

Then choose the scope: one conversation, all history or the entire account. Read the confirmation before accepting. After deletion, check visible history and old shared links separately; one test does not prove the other.

When closing an account, separately check subscriptions and access by associated applications. If export or a required option is missing, use the data request portal. Do not send support your password or an entire private archive.

X settings and API policies#

For a third-party tool, check that provider’s own storage practices too. A model provider’s rules do not establish what an intermediary application stores.

EU, EEA, United Kingdom and Switzerland#

A shared addendum does not mean identical legal regimes or feature availability. For business personal data, review the specific contract and your organisation’s approval.

Next: apply the source-material check in Files.

A one-minute check before sharing materials#

1. Open the correct personal or work account.
2. Send only the pages, rows and fields the task needs. Replace names or identifiers with neutral labels when the output does not need them.
3. Check the connector’s access scope; a small task does not automatically mean narrow permissions.
4. Before sharing, open the finished document and inspect attachments, comments and hidden spreadsheet content.
5. When finished, disconnect unnecessary access and remove public links you no longer want to use.

A prompt is not an account setting. Writing “do not store this text” does not change the service’s rules. Check training, history, access and sharing controls in the relevant product.