atmoriPreferences and Chrome Sync
Validated themes, fonts, conversation width/size, scenery presets, motion settings, sound levels, interaction sound switches, and timer preferences are stored locally and copied to chrome.storage.sync. Chrome transports these preferences between installations of the same extension when your Chrome account and extension sync settings permit it. Google manages that transport; Atmori does not receive the preferences.
Custom wallpaper image data, imported music and rain recordings, music selection, playback, mute and current timer progress remain on the device. Files use extension-local IndexedDB; preferences use local storage and session storage. Conversations and input contents are not included in Sync. Sync is not instant: writes are batched, and failures retry while local changes remain usable.
Website access
Adapters style the supported sites and observe UI elements and render mutations to detect send, waiting, response, error and cancellation states. They do not collect conversation text or input values, intercept requests, or send browsing data to Atmori servers. Native websites retain their own privacy practices.
Permissions
storage: preferences, local cache and Chrome Sync.alarms: retry and batch preference writes across service-worker restarts.offscreen: audio continues when the popup closes.activeTab: identify the current supported workspace for popup controls and fullscreen.- Content scripts are limited to ChatGPT (including chat.openai.com), Gemini and Claude.
Your controls
New installs enable interaction sounds at 100%; the continuous thinking loop starts off. Background music and rain require Play. Saved sound choices are preserved. Restore the native site appearance from the popup, disable sound/motion, or add or remove custom music tracks, or replace imported rain recordings through the audio controls. Custom music has no track-count limit and is not uploaded or synchronized. The remove button deletes a selected library file. The default-rain control deletes the imported rain recording; uninstalling clears other local files. Manage extension synchronization in Chrome's account/sync settings. Uninstalling removes extension-local data; Google controls retention and deletion of synchronized data. There is no developer-held account or conversation database to delete.
Reference: Chrome storage documentation