Privacy

Obscura Flow follows a local-first model: workspaces, project folders, and archives are stored in locations chosen by the user. API synchronization is used only when the service is available and enabled.

Data kept locally

The following elements are managed locally in the workspace or configured folders:

.obf workspace file;
names, descriptions, projects, collections, and settings;
local paths, recent files, and archive history;
EXIF metadata extracted from projects;
logs and technical states visible in the application.

Data that can be synchronized

When synchronization is enabled, Obscura Flow can send to the backend the information required to track workspaces, projects, collections, archives, and synchronization operations. Source photo files and archives remain in configured local paths unless a specific action or integration in the installation provides otherwise.

Photo metadata

EXIF metadata can include sensitive information depending on camera and capture settings. Before sharing a workspace, screenshot, or export, review the fields shown in the project detail.

Good practices

Use controlled and backed-up work folders.
Avoid personal information in project names unless needed.
Review EXIF metadata before external sharing.
Do not publish screenshots containing tokens, emails, personal paths, or client information.
Disable or defer synchronization when a workflow must stay strictly local.

Support

For support requests, share only what is needed for diagnosis: application version, observed behavior, error message, and functional context. Mask client data and personal paths when needed.