Skip to content
Writenex
Open Editor

Privacy Policy

Last updated: December 13, 2025

At Writenex, we believe your content is yours and yours alone. This Privacy Policy explains how data is handled when you use Writenex products. In short, Writenex is designed so your content stays on your device and is not collected or processed by us at the application level.

The Short Version

  • We do not collect your data. Your content does not leave your device.
  • We do not sell or share data. We have no user data to sell or share.
  • We do not use analytics or tracking. No cookies for tracking, no telemetry, no analytics services.
  • We do not require an account. No email, no password, no personal information.
  • Your content stays local. Writenex Editor stores data in your browser. @writenex/astro stores data in your project files.

Data Storage

Writenex Editor

Writenex Editor stores the following data locally in your browser using local storage (IndexedDB):

  • Documents: Your Markdown documents and their content
  • Version History: Previous document versions for recovery
  • Images: Images inserted into documents, stored as base64 for local portability
  • Preferences: Theme selection, view mode, and other interface preferences

All of this data is stored entirely on your device. We do not have access to it, and it is never transmitted to any Writenex server.

@writenex/astro

@writenex/astro is an npm package that runs entirely on your local machine. It stores:

  • Content files: Markdown files inside your project's src/content directory
  • Version history: Shadow copies in your project's .writenex/versions directory
  • Images: Uploaded images stored within your project, either alongside content or in the public folder

All data remains inside your local project directory. The package does not include telemetry, does not send data to external servers, and does not communicate with Writenex services.

How to Delete Your Data

Because all data is stored locally, you have full control over deletion:

  • Writenex Editor: Delete documents using the editor interface or clear site data for writenex.com in your browser settings
  • @writenex/astro: Delete files from your project directory or remove the .writenex folder to clear version history

Deletion is permanent and cannot be undone.

No Tracking or Analytics

Writenex does not use:

  • Analytics services of any kind
  • Tracking pixels or beacons
  • Third-party cookies
  • Fingerprinting or identification technologies
  • Telemetry or usage reporting in npm packages
  • Usage data collection of any kind
  • Error tracking or crash reporting services

Service Worker and Offline Usage

Writenex Editor uses a Service Worker to support offline functionality. The Service Worker:

  • Caches application assets such as HTML, CSS, JavaScript, and fonts
  • Allows the editor to function without an internet connection
  • Operates only within the writenex.com origin
  • Does not collect, process, or transmit user data

npm Package Privacy

@writenex/astro is distributed via npm. When installing or using the package:

  • npm itself may collect installation statistics according to npm's own policies
  • The package does not send any data to Writenex or third parties
  • All execution happens locally on your machine
  • Network access is limited to localhost usage required to serve the local editor interface

Third-Party Services

Writenex does not integrate with third party services that collect user data.

Our website is hosted on infrastructure that may generate standard web server access logs, such as IP addresses, timestamps, and requested pages. These logs:

  • Are used only for basic maintenance and security
  • Do not include document content or editor activity
  • Are not used for analytics or user profiling

Data Security

Writenex Editor

Data security relies on browser built in protections:

  • IndexedDB data is sandboxed and accessible only to the writenex.com origin
  • HTTPS encryption protects application assets during loading
  • No server side database means there is no server side content storage

Because data is stored locally, you are responsible for backing up important documents. Clearing browser data, uninstalling the browser, or using a different device will remove access to stored content.

Browser extensions may have access to local data depending on permissions you grant to them.

@writenex/astro

Security considerations for the npm package include:

  • The package is intended for development use and is disabled in production by default
  • Filesystem access is limited to your project directory
  • The editor interface is served locally and not exposed to the public internet
  • Version control systems such as Git are recommended for backup and recovery

Important: Do not enable @writenex/astro in production environments without proper authentication, as it provides write access to your filesystem.

Children's Privacy

Writenex does not knowingly collect information from anyone, including children under the age of 13. Because Writenex does not collect personal data, no age related data is processed.

If you are a parent or guardian and believe a child has provided personal information through misuse of the service, please contact us.

Changes to This Policy

We may update this Privacy Policy from time to time. Any changes will be posted on this page with an updated "Last updated" date. Since we do not collect email addresses or user accounts, we cannot provide direct notifications of policy changes.

Contact

If you have questions about this Privacy Policy or Writenex's privacy practices, you can contact us through the Writenex GitHub repository at https://github.com/erlandv/writenex.

This Privacy Policy is effective as of December 13, 2025.