Repository navigation
Privacy and Model Use
Culvia is local-first.
By default, runtime data stays on the user's machine:
- Source folder paths
- SQLite application state
- Generated thumbnails and previews
- Upload cache
- Export output
- Local model cache
Photos are sent to an external service only when the user explicitly enables and starts an OpenAI-compatible vision review.
Local scoring and local thumbnail generation do not require uploading photos to a hosted Culvia service.
API keys should be provided through the app configuration flow, environment variables, or secure runtime configuration. They should not be committed to Git, written into docs, stored in fixtures, or pasted into public issues.
When reporting issues, avoid sharing:
- Real API keys
- Private photo paths
- Client names
- Original full-resolution photos unless you intentionally want them public
- Runtime SQLite databases
- Logs containing secrets or private paths
Screenshots are usually safer than archives, but still check for private file names or client information.
Manual judgment remains the final culling layer. Model output is treated as guidance for sorting, explanation, and review.