DocsPrivacy

Privacy

Privacy and Permissions

12 min read

On this page

  1. 01Local state
  2. 02Only add needed material
  3. 03Model requests
  4. 04Tool approval
  5. 05Decide what belongs in Lumo
  6. 06Understand provider boundaries
  7. 07Review generated files before sharing
  8. 08Use permissions as a working habit

Local state

In a Mac workspace, Lumo stores sessions, runtime state, and app settings locally. Generated Artifacts can be saved to the selected Mac workspace when auto-save is enabled. Cloud Agent is a separate managed workspace with its own cloud sessions and Artifacts; it is not an automatic copy of your Mac.

Only add needed material

Creator projects often include unpublished scripts, sponsor notes, and raw footage. Only attach the material needed for the current task, and keep original source files under your own folder structure.

Model requests

When AI assistance is used, the selected provider may receive the prompt and attached context needed for the task. Review provider and account settings before adding sensitive content.

Tool approval

Permission prompts exist so you can inspect file writes, shell commands, protected path access, and network-related actions before they run.

Decide what belongs in Lumo

Lumo works best with material directly needed for the task: briefs, scripts, subtitles, title notes, platform notes, and selected assets. Keep contracts, private account data, unneeded client files, and unrelated raw folders outside the active request unless the task truly requires them.

Understand provider boundaries

Your local app can hold sessions and files, but AI requests still go through the selected provider or Lumo Cloud route when assistance is used. Before adding unreleased or sensitive content, check which route is active and whether that route matches your privacy expectations.

Review generated files before sharing

Artifacts may contain source snippets, private notes, draft sponsor wording, or file paths. Before sending an Artifact outside your team, open it and remove internal comments, unused sections, and sensitive references.

Use permissions as a working habit

Permission prompts are not just security friction. They are also a moment to check whether the task is about to touch the right folder, write the right file, or run the right command.

If a prompt asks to write outside the active workspace, pause and read the path before approving.

Docs feedback

Tell us if this page does not match your current build.

Send feedback
PreviousNext
Lumo

One focused workspace for every step from creating to publishing.

Product

  • Features
  • Use Cases
  • Pricing
  • Download
  • Changelog

Resources

  • Documentation
  • FAQ
  • Support
  • Blog

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service

© 2026 Lumo. All rights reserved.

|

Built for creators. Free, Pro, and Max plans available now.

Download Lumo
Skip to main content
Lumo
FeaturesUse CasesPricingFAQBlog
Download