Privacy Policy & Data Sovereignty

StoryScrib is engineered from the ground up with a Zero-Backend architecture. StoryScrib operates no centralized servers, no cloud databases, and no telemetry infrastructure to ingest, store, or monitor your files.

All project files, novel drafts, acts, chapters, scenes, character dossiers, world-building lore entries, scene snapshots, and notes are saved directly to your local computer's file system. Zero manuscript data is ever transmitted to StoryScrib.

We use standard, documented file formats (open SQLite databases, standard UTF-8 plain text, and Markdown JSON structures). You can freely backup, copy, move, sync via personal cloud folders (such as Dropbox, Google Drive, iCloud, or Nextcloud), or version-control your manuscripts without any proprietary cloud dependency.

StoryScrib does not collect, record, or transmit:

• Any keystrokes, character inputs, or prose written in the editor.
• Your manuscript titles, scene synopsis, world bible notes, or revision histories.
• Writing analytics, sprint speeds, daily schedules, or session timestamps.
• Device file system paths or folder structures outside your chosen project directory.

The software functions with 100% full capability with your network connection turned off.

StoryScrib provides modular, opt-in AI assistance (ScribAI). We adhere to strict author-first privacy safeguards:

1. Disabled by Default: All AI integrations and features are completely turned off by default upon installation. StoryScrib never makes unsolicited network calls to AI servers.

2. Local Models (Ollama, LM Studio, KoboldCPP, vLLM): If you choose to enable a local model, all prompts, scene context, and responses process 100% on your local hardware. No packets leave your computer.

3. Cloud Providers (BYOK - Bring Your Own Key): If you choose to connect Anthropic Claude, OpenAI, Google Gemini, DeepSeek, or OpenRouter, your application communicates directly with the respective API provider using your personal secret key. StoryScrib operates no intermediary logging servers.

4. Zero Model Training: StoryScrib does not use, aggregate, or sell your writing or prompt data to train machine learning models.

When you purchase a license or register for customer support, we collect only the minimal data necessary to deliver your software:

• Your Email Address: Used to deliver your license key, purchase invoice, and critical version update notices.
• Cryptographic Device Identifier: A hashed identifier generated when activating your perpetual license on your up to 10 authorized personal machines.

We will never sell, rent, or trade your email address to advertisers or data brokers.

All financial transactions are processed securely through Stripe, the global gold standard in PCI-DSS Level 1 payment infrastructure. Stripe allows authors from over 195 countries to purchase securely using local and international credit cards, debit cards, Apple Pay, Google Pay, and regional payment methods across 135+ global currencies.

StoryScrib never receives, handles, or stores your credit card numbers, bank details, or CVV codes. All checkout processing occurs directly within Stripe's encrypted payment vault.

Because your projects reside on your personal hardware, you possess immediate, autonomous control over your files at all times. If you wish to delete your account or customer record from our license recovery database, email us at privacy@storyscrib.com and we will permanently purge your records within 30 days.