Does NeoGlint's Autosave Ever Write My Drafts to a Temporary or Cloud Location I Don't Control?

Every piece of writing in NeoGlint is called a Space, and every Space is stored as a standard JSON file on the machine you're typing on. There is no intermediary. The app writes to the local filesystem and stops there — no upload step, no sync queue, no background process sending your text anywhere else.

The default location is your Documents folder, under NeoGlint/Spaces. That means you can navigate to it in File Explorer, see the files, open them in a text editor, and confirm for yourself what autosave is doing. The files are standard JSON, not a proprietary binary format, so they remain readable artifacts of your own work.

• Autosave target: a local JSON file inside Documents/NeoGlint/Spaces
• No server round-trip: there is no NeoGlint backend receiving your drafts
• No cloud by default: no Dropbox, Google Drive, or iCloud integration is bundled or required
• No account: you never log in, so there is no identity linked to your writing

If you want redundancy, you add it yourself: point a sync client at the folder, or copy it to an external drive. NeoGlint does not do that for you, and it also does not do anything behind your back.

The temporary space is often the part people worry about, because temp anything sounds ephemeral. In NeoGlint, Ctrl+T opens a temporary space and starts autosaving right away — not into RAM, not into a browser cache, but onto your own disk. The reason it can survive a crash or an app close is precisely that it has already been written to a file.

When you reopen NeoGlint, it brings you back to that space. You can keep writing, rename it later, and at that point it joins your permanent Spaces list. If you never name it, it still lives as a file you control, not as a draft trapped inside the app.

1. Press Ctrl+T — a temporary space opens and autosaving begins immediately
2. Keep typing — content is written locally as you go, no save prompt
3. Crash or close the app — the temporary space is not lost
4. Reopen NeoGlint — you are returned to the same temporary space
5. Name it — it becomes a permanent Space in your list

Two design choices reinforce this. The app runs as a single instance, specifically so a second window cannot overwrite a Space another session is editing. And it has no save button, because saving is not an event you trigger — it is a continuous local write.

NeoGlint is free for personal and commercial use, and its pricing line is simply "$0 FOREVER." None of that changes the file path: your writing lives on your machine.

The privacy claim here is not a policy promise about how data is handled — it is an architectural fact. NeoGlint has no server, so there is no endpoint for telemetry, no account database, and no sync service. There is simply nothing on the other end to receive your drafts.

That has a consequence the product states flatly rather than softening: because there is no cloud sync, you are responsible for your own backups. The recommended approach is whatever you already trust — an external drive, Dropbox, Google Drive, or another tool pointed at the Spaces folder. That is a design tradeoff, not an oversight, and it is the same honesty that applies to the platform itself.

• No account: there is nothing to sign up for or log into
• No cloud sync: no drafts are mirrored to a remote service
• No telemetry: no usage analytics are sent anywhere
• No ads: nothing in the app is monetised by attention or data
• Backups: entirely your responsibility, by design

It is also worth being precise about scope, since precision is the point. NeoGlint is currently Windows only — there is no mobile app, no web app, and no browser extension. Possible future additions mentioned by the studio, such as encrypted Spaces and some form of FTP integration for backup, are not built today, so they should not be relied on. For now, the answer is the simplest one: your drafts go to a folder on your own disk and nowhere else.

Because NeoGlint stores everything locally, verification requires no special tools. Open File Explorer, navigate to Documents/NeoGlint/Spaces, and you will see a JSON file per Space. Open one in Notepad or any code editor and you will see your text and formatting represented as structured data—not an encrypted blob or a binary format you cannot read.

To confirm autosave is working, make an edit in a Space, note the file's last-modified time in Explorer, wait a moment, and refresh. The timestamp should update without you pressing any save command. Because there is no save button, the absence of a prompt is expected; the file write is continuous and silent.

• Open the Spaces folder from File Explorer.
• Check that each Space appears as a .json file.
• Edit a Space and observe the file's modified time change.
• Inspect the JSON to see your content in plain form.

This local, inspectable design is the opposite of a cloud service that stores drafts in an opaque database. It also means there is no "temporary" location in the operating system sense—no %TEMP% folder holding your words, no browser cache, no app-managed shadow copy. The only place your writing lives is the file you can see.

If you move the file or back it up, you are moving the actual source of truth. That is the practical test: the file is not an export from some hidden store; it is the store.

Since NeoGlint has no server and no sync service, backups are entirely the user's responsibility. This is not a limitation the product apologizes for; it is a deliberate consequence of being offline-first. The upside is that you are not locked into any particular backup provider—you can use whatever you already trust.

Common approaches include pointing a folder-sync client (Dropbox, Google Drive, OneDrive) at the NeoGlint/Spaces directory, regularly copying the folder to an external hard drive, or using a versioned backup tool that snapshots your Documents folder. Because each Space is a standard JSON file, any file-level backup method will capture your work.

1. Locate your Spaces folder at Documents/NeoGlint/Spaces.
2. Choose a backup method: sync client, external drive, or backup software.
3. If using a sync client, configure it to include that folder.
4. Test restoration by copying a file back and opening it in NeoGlint.

The absence of built-in sync means there is also no chance of a silent conflict or a merge gone wrong—what you see on disk is what you have. That simplicity is consistent with the product's positioning: local-first file storage, zero vendor lock-in, and no account.

Future additions like encrypted Spaces or FTP backup integration have been mentioned as possibilities but are not available today. For now, the backup strategy is yours to define, using tools you already control.

The word "temporary" in Ctrl+T refers to the space's status in the app's UI—it has no name yet—not to its storage location. The file is written to your disk immediately, just like any other Space. It is not stored in %TEMP%, not in AppData, and not in any location that gets cleaned up automatically.

This matters because some applications use temporary files for autosave and then discard them on a successful save. NeoGlint has no such two-stage process: the file on disk is the primary storage, always. There is no moment where your work exists only in a volatile location.

• No OS temp folder usage for autosave.
• No browser cache or local storage (it is not a web app).
• No app-managed cache directory for drafts.
• The only storage location is the Spaces folder you control.

If you are auditing where an application writes data, you can use process monitoring tools to observe file writes. With NeoGlint, you will see writes to the Documents/NeoGlint/Spaces path and nowhere else for content. That transparency is a direct result of the offline-first architecture.

In short, there is no hidden temporary location. Your drafts are always in a file you can find, open, and back up.