Privacy · Kroma
What stays on your device.
Purpose-bound data use. Kroma is built around local creator work. This policy describes data handling verified in the current app source: local media and records, optional platform connections, Apple purchases, and opt-in diagnostics.
01 · Local app data
Creator content is stored locally.
Kroma lets you save videos, images, files, URLs, captions, notes, tags, platform selections, OCR text, transcripts, publishing records, and related media metadata. The app stores its catalog in its local SwiftData store and stores media under the app’s local CreatorVault directories.
Imported media files are encrypted with AES-GCM. The vault key is stored in the device Keychain with device-only accessibility. The SwiftData store can contain plaintext metadata such as titles, notes, OCR text, and transcripts, and is protected with iOS file protection. Kroma does not upload this local catalog or private media to NexaraTech servers as part of ordinary local use.
Local storage does not stop data leaving the device when you choose to publish, share, export, connect an account, import a remote URL, or use a system feature that has its own provider.
02 · Platform connections
Connections run only when you start them.
Kroma supports direct publishing to YouTube and LinkedIn when the required account connection, permissions, network, and platform state are available. Kroma also prepares assisted sharing flows for TikTok, Instagram, X, and Facebook. Assisted sharing hands the prepared content to the platform or system share surface; Kroma cannot confirm the final post there.
Account credentials and refresh data for YouTube, LinkedIn, and TikTok are stored in the device Keychain. OAuth exchange endpoints handle authorization codes or refresh requests using provider client secrets on the backend. The reviewed source shows no database-backed storage for those tokens.
When you publish or share, the selected media, caption, tags, and other required fields are sent to the platform you selected. Those platforms process that data under their own policies.
03 · Diagnostics
Diagnostics are optional and off by default.
Kroma has a Privacy & Security setting for diagnostic sharing. The default preference is disabled. If you enable it, Kroma may send limited error and workflow events to Sentry to investigate crashes, failed imports, publishing failures, OAuth failures, transcription or transcode failures, export failures, deletion failures, payment events, and known action taps.
The app’s diagnostic payload is restricted to enum-based event data and approved technical fields such as app version, build, OS version, platform, provider, reason, operation, product or entitlement identifiers, result, and duration bucket. The app disables screenshots, view hierarchy, session replay, automatic breadcrumbs, network breadcrumbs, default personal data, stacktraces, request data, user data, and free-form error text.
The reviewed source does not show an advertising analytics SDK in Kroma. Sentry collection depends on a valid production DSN and your diagnostic-sharing choice.
04 · Your controls
Use settings to manage local access.
- Delete saved clips, collections, variants, and publishing records in Kroma.
- Disconnect connected platform accounts in Settings.
- Clear thumbnail or other local caches in Privacy & Security.
- Turn diagnostic sharing off at any time.
- Manage or cancel subscriptions through Apple account settings.
- Contact support about privacy questions or data-handling concerns.
The reviewed app source does not define a fixed retention period for provider-held diagnostics, subscription records, or support correspondence. Provider retention follows the relevant provider policy. Local app data remains until you delete it, clear it, or the operating system removes the app data.
Questions
Ask about data handling.
Contact support@nexaratech.ca. Do not email private media or credentials unless support asks for a specific, redacted example.