AI & Tools / Article
How to Use AI Without Sharing Private Files: Privacy Settings and Safer Workflows
Photo by Aerps.com on Unsplash

How to Use AI Without Sharing Private Files: Privacy Settings and Safer Workflows

Using AI tools to write emails or analyze documents seems convenient, but sharing sensitive information can expose you to privacy risks. The good news: you can minimize these risks by adjusting privacy settings, choosing local AI models, and using secure workflows. Here’s how. For a related guide, see File Sync Conflicts? How to Resolve Duplicate or Overwritten Files.

Quick Privacy Fix: Check App Settings First

Before diving deeper, stop and look at your AI tool’s privacy settings. Many apps let you disable data collection or restrict file uploads. For example:

  • ChatGPT: Navigate to Settings > Data controls to opt out of training data use. Avoid uploading files unless necessary.
  • Google Gemini: Check your Google Account data settings. Review what Bard stores under Activity Controls.
  • Microsoft Copilot: Review your Microsoft account privacy settings to limit data sent to Microsoft.

If a tool doesn’t offer granular privacy controls, consider alternatives.

Why Your Data Might Be Shared

Three common reasons explain why privacy lapses happen:

  1. Cloud-based processing: Most AI tools analyze text locally on your device but send data to remote servers for complex tasks like file analysis or image generation.
  2. Default data collection: Many apps collect user inputs to improve models unless users opt out explicitly.
  3. Lack of transparency: Users often accept default terms without realizing their files (like documents or spreadsheets) could be stored or analyzed.

Safer Alternatives to Sharing Private Files

Here’s how to work with AI tools without sending sensitive data to third parties:

1. Use Local AI Models

  • What it is: Install AI tools that run entirely on your device, like LM Studio, Ollama, or LocalAI.
  • Benefits: No data leaves your computer. Your documents stay private.
  • How to start:
    • Download a local model from Hugging Face (e.g., Microsoft Phi or Mistral).
    • Install it through Ollama (macOS/Windows/Linux) using simple commands.
    • Use the model via a local terminal or tool like ChatDL for a chat interface.

2. Process Data Locally

If you must use a cloud-based tool, extract key data first. For example:

  • Split sensitive files into non-identifiable summaries before upload.
  • Use built-in redaction tools to remove personal details (names, addresses, etc.).
  • Prefer text-only inputs over file uploads wherever possible.

3. Browser-Based Privacy Modes

For web-based AI tools:

  • Use private browsing modes (Chrome Incognito, Firefox Private Window) to limit cookie tracking.
  • Install privacy extensions like uBlock Origin to block trackers.
  • Clear browser cache and history after sessions.

Open-Source AI Tools for Privacy-Loving Users

If mainstream AI tools feel too invasive, consider these open-source alternatives:

  • Hugging Chat: A privacy-focused chatbot built by the same community behind Hugging Face models.
  • Text Generation WebUI: Runs locally and supports many open models. Less user-friendly but highly private.
  • PhoTok: A Mac app that processes text on-device using Apple’s ML frameworks.

These tools prioritize user control and data ownership. Check GitHub repositories for setup guides and community recommendations.

What If Privacy Settings Don’t Work?

If adjusting settings doesn’t solve your issue:

  1. Test data leakage: Check if your files appear in the AI tool’s interface or account logs. Use a dummy file first.
  2. Try a different network: Public Wi-Fi or VPNs can complicate tracking, but use caution—they aren’t foolproof.
  3. Contact support: Verify whether your data is encrypted or stored long-term. Avoid unresolved privacy concerns.

If a tool repeatedly ignores privacy settings, switch providers. Your data isn’t worth the risk.

Final Tips for AI Privacy in 2024

  • Start with settings first: Always check privacy options before uploading anything.
  • Assume cloud AI reads your files: Even if a tool claims “no storage,” trust but verify.
  • Prioritize local tools: Open-source and on-device models offer the best privacy.
  • Stay updated: AI tools evolve monthly. Re-check privacy policies annually.

Using AI doesn’t have to mean sacrificing privacy. By adjusting settings, leveraging local models, and being mindful of inputs, you can work smarter—and safer—today. Start with one small change today. Your private files deserve protection.

Start With Data Minimization

The safest file to upload is often the smallest amount of information needed to complete the task. Instead of uploading a complete document, remove unrelated pages, personal identifiers, account numbers, private correspondence, or confidential attachments. If the AI only needs a paragraph to summarize, provide the paragraph rather than the entire file.

Review the Service's Current Data Controls

Privacy settings differ between AI products, account types, and plans. Read the current settings for the specific service you use rather than assuming that one product's rules apply to another. Look for controls related to training, history, retention, sharing, file storage, and administrator access.

Be Careful With Business and School Information

Documents from work, school, clients, or other organizations may be subject to rules that you cannot override yourself. Before uploading them, check the organization's policy and the AI service approved for that environment. A document can contain sensitive information even when it does not look like a traditional password or financial record.

Consider Local Processing When Appropriate

Local or on-device AI can reduce the amount of data sent to an external service, but it is not automatically private. Review the software, model source, logs, extensions, and device security before relying on local processing for sensitive information.

Remove Secrets Before Asking AI for Help

Never paste passwords, API keys, recovery codes, private encryption keys, session tokens, or similar credentials into a chat just to explain an error. Replace them with placeholders such as [API_KEY] or [PASSWORD]. If a secret has already been exposed, rotate or revoke it through the appropriate service.