Where your data lives

Where does what you write in Slima actually live? This page walks through the four storage layers — so you know the full path from keystroke to cloud.

Four storage layers

Layer	Where	What
Cloud database	Slima's primary database (PostgreSQL)	Chapter text, file structure, version history, AI conversations, account
Object storage	Slima-managed object storage	Cover images, embedded media in chapters (images, PDFs)
Frontend IndexedDB	Your browser, locally	Local cache; buffers pending changes when offline
Desktop local files 🚧	Electron app folder (once Desktop ships)	Desktop's independent cache, encrypted token

A paragraph's journey from keystroke to cloud

You type
  ↓
IndexedDB local cache (instant write)
  ↓
Background buffer + push to cloud DB
  ↓
Cloud confirms receipt
  ↓
IndexedDB marks "synced"

Other devices pull the other way:

Device opens the book
  ↓
Fetch latest content from cloud DB
  ↓
Write into that device's IndexedDB
  ↓
Render in the editor

Media (images / covers / PDFs) — separate path

Media is stored separately from text:

1. You drag an image into Slima
2. The image uploads to object storage (not the cloud DB)
3. The cloud DB only records the file's URL
4. Other devices: IndexedDB cache + direct fetch from object storage when viewing

This split exists because a text database isn't great for large binary files — images and PDFs go to dedicated object storage for efficiency.

Desktop extra local storage (🚧 in development)

Once the Electron desktop app ships, it'll have its own app folder:

OS	Path
macOS	~/Library/Application Support/Slima/
Windows	%APPDATA%\Slima\
Linux	~/.config/Slima/

It contains:

• Token (OS-encrypted)
• Local cache
• Preferences

Deleting this folder = the desktop app resets to fresh-install state. Your cloud data is untouched — just sign in again.

Regions / multi-region

For where data is stored and the data-residency policy, see the Slima Privacy Policy.

Related

• Who can see your content
• AI training policy
• Export data