Brandon Mysliwiec Contact

Privacy

Your manuscript doesn't need the Internet.

This page describes what QuillArk actually does, not what it intends to do. Every claim here is something you could verify by reading the source or watching the network.

What QuillArk does not do

  • No account. There is nothing to register, nothing to sign in to, and no identity attached to your work.
  • No subscription or licence check. Nothing phones anywhere to ask whether you are allowed to keep writing.
  • No telemetry. Not anonymous usage statistics, not crash reports, not feature counts. There is no opt-out because there is nothing to opt out of.
  • No analytics. None in the application, and none on this website.
  • No advertising.
  • No manuscript upload. Not for backup, not for sync, not for AI, not for anything.
  • No background transfers. QuillArk does not check for updates on its own.

The two network connections

QuillArk can talk to a local AI engine — Ollama or llama.cpp — running on your own computer. That connection is guarded rather than trusted:

Before any request is made, the endpoint address is checked to be a loopback address: localhost, 127.0.0.1 or ::1. If it is anything else, the request is refused with an error and nothing is sent. Prompts and manuscripts travel the same guarded path, so there is no route by which one could leave and the other not.

The second is the version check. If you press Check for updates in About, QuillArk asks this site for a version number. It happens only when you press it — never on launch, never on a timer — and it sends nothing but the request: no account, no identifier, and nothing you have written. It downloads and installs nothing; if there is a newer version, it tells you and links here. The whole of that code is src/main/services/updateCheck.ts.

Our server sees what any web server sees when you visit a page: an address and a time. If you would rather it saw nothing at all, do not press the button — nothing else in QuillArk will.

If you never set up a local model, QuillArk never opens a socket at all. The built-in AI engine runs inside the application.

Where your writing is

In a folder you chose, on your own disk. QuillArk asks for it on first launch and never moves it. Inside are ordinary folders and ordinary files:

  • Chapters are Markdown files.
  • Characters, places and every other record are Markdown files with a readable header.
  • Reading order is a YAML file you can edit by hand.
  • Settings are JSON.

The only database is a search index, and it is disposable — deleting it costs nothing, because QuillArk rebuilds it from your files. Nothing about your book exists only inside a database.

What the log file contains

QuillArk keeps a small troubleshooting log in your Books folder, under _QuillArk/Logs. It records events, file paths and errors. It does not record the text of your manuscript. You can read it, and you can delete it.

Uninstalling

Uninstalling QuillArk removes the program. It does not touch your Books folder, and it does not touch your settings. Everything you have written stays exactly where it is, as files you can open without QuillArk.

This website

The same standard applies here.

  • No analytics, no tag manager, no pixel, no fingerprinting.
  • No cookies. There is no consent banner because there is nothing to consent to.
  • No third-party requests. The fonts, styles, scripts and images all come from this domain. Nothing is loaded from a CDN, so no other company learns that you visited.
  • No forms. Nothing here collects anything from you.

A web server necessarily sees requests it is asked to serve. Beyond whatever access logs your host keeps by default, nothing about your visit is recorded, stored or shared.