Privacy Policy

1. Scope and the short version

This policy covers the NeoWriter apps for iPhone, iPad, and Mac, including their optional integrations, and support communications with Genjux, the independent developer publishing under the GenjuxApps name.

Not operating a data-collection backend is different from saying that no data is ever processed outside your device. Apple, your chosen providers, recipients of exports, and the email service used for support may process data when you use those services.

This website stores your selected site language locally in your browser under genjuxapps.locale. The preference is not separately sent or used for analytics or tracking; no separate analytics or preference upload is introduced. Ordinary requests for /zh/... pages naturally disclose the requested URL to the hosting provider. This website preference is separate from NeoWriter's native-app data and settings.

2. What stays on your device

NeoWriter stores the information needed to provide its writing features locally. Depending on the features you use, this includes:

• Articles, books and folders, tags, links, images, version history, and Trash items.
• Editor preferences, writing goals, custom templates and prompts, and other app settings.
• Sync and publishing metadata, locally cached purchase entitlements, and local diagnostic information.

Integration secrets, such as AI API keys and WebDAV or WordPress credentials, are kept in device-local credential storage and used to authenticate with the service you configure. They are not sent through a NeoWriter-operated proxy or included in custom-prompt sync content.

Local storage, an app privacy lock, operating-system data protection, and optional backup encryption are different protections. None is a promise that every copy of your writing is encrypted everywhere or that recovery is always possible.

3. Optional sync and backups

iCloud / CloudKit: if you enable iCloud sync, NeoWriter uses your Apple account's private CloudKit database. Synced records can include your writing, organization and recovery metadata, and custom prompts. This is Apple's infrastructure, not a writing database operated by Genjux.

WebDAV and cloud storage: if you configure a WebDAV server or a cloud-backed folder, the selected provider receives the data needed for the sync or backup operation. Its operator, access controls, location, security, and retention policies matter. Use a destination you trust and a secure connection where supported.

Readable and encrypted vault modes are different choices. Readable mode stores ordinary Markdown with readable filenames. In encrypted vault mode, article content, image objects, and the index are encrypted on your device with AES-256-GCM; the remote object names are opaque. File counts, sizes, dates, and access patterns can still be visible. This vault mode is not a claim that ordinary exports or every iCloud copy uses the same protection.

A new encrypted vault uses a separate, empty remote folder. Enabling it does not erase plaintext previously uploaded to another folder or versions retained by a provider. Preserve a usable backup before managing those older copies.

The vault protects remote copies, not the live local library with the same passphrase. An intact local working copy remains independent of that vault credential. Vault-mode records and protection counters can synchronize through iCloud Keychain, while cached vault keys are device-local. We do not hold a developer recovery key for your encrypted content.

Enabling automatic sync or backups can authorize later background transfers; you do not necessarily approve every transfer separately. You can disable these features in the app. A cloud-folder provider may also continue synchronizing files according to its own settings.

Backups may be stored locally or in a destination you choose. With encrypted backups enabled, the destination receives a sealed .nwbackup container, not a plaintext snapshot that is encrypted afterward in the cloud folder. Protect the passphrase and recovery material: we cannot recover your secret or decrypt those backups for you. Turning off a feature does not remove copies already stored elsewhere.

4. Optional AI and what is sent

Writing does not require AI. On-device AI and external AI are different processing modes. When you choose an external provider and invoke an AI action, NeoWriter sends the request directly to the configured service, not through a developer-operated relay.

The supported external choices include Anthropic, OpenAI, DeepSeek, OpenRouter, xAI (Grok), Google AI Studio, and a custom OpenAI-compatible endpoint. A routing service such as OpenRouter may forward requests to the selected model provider. A custom endpoint has its own operator and data practices.

The input is not always just selected text. The command and displayed scope determine what is used: a selection, the current paragraph or section, an article, or text before the cursor. A summary without a selection can use an entire article; continuation can use everything before the cursor.

The request includes the resolved source text, NeoWriter's effective prompt or instructions, the selected model, relevant request settings, and the authentication needed by that service. Review the request details, scope, and recipient before sending. External processing requires the app's applicable consent; changing the provider, concrete model, or recipient can require confirmation again.

Providers may also receive ordinary network information, such as your IP address and request metadata. Their retention, logging, training, and international-processing practices are governed by their own terms and your provider settings. NeoWriter cannot promise that every provider retains nothing or never uses submitted content for training.

Disabling external AI or cancelling a request can prevent further app processing or future requests, but it cannot retract bytes already received by a provider. Do not submit confidential material unless you are authorized to share it with that recipient.

5. Publishing, exports, and local transfer

WordPress publishing on Mac: publishing sends the article's title and formatted body to your configured WordPress site using its authentication credentials. The action can create a live post or update an existing one after confirmation. Published material may become public. Removing a local article does not remove the remote post.

Export and sharing: when you export files or use system sharing, the destination app, storage provider, or person receives the content you choose. Their handling of the resulting copy is outside NeoWriter's control.

Wi-Fi Transfer on iOS: this optional feature temporarily runs a local transfer server on your device, not on a developer backend. Devices that can reach the displayed local address may access the articles made available by the transfer feature. It uses local HTTP, which should not be described as end-to-end encrypted. Use a trusted network and stop the transfer server when finished.

6. Images, system features, and local components

Images or files you choose to import are processed for the requested feature, such as image insertion or on-device text recognition using Apple Vision. Later sync, export, publishing, or sharing may transmit imported content as part of your work.

System features, permissions, authentication, and services are governed by your device settings and Apple's disclosures. For example, Face ID authentication supplies an authentication result to the app, not the biometric template. Using an operating-system service is distinct from uploading a report to the developer.

NeoWriter does not include advertising or third-party analytics trackers. Its local components include GRDB, swift-markdown, KaTeX, Mermaid, and syntax-highlighting resources. These support storage and rendering; their presence is not analytics collection. The Markdown preview uses bundled rendering assets rather than a hosted document-rendering service.

7. Apple purchases

NeoWriter is not yet listed on the App Store as of this policy's date. This section explains the purchase integration if purchases are offered through Apple; it is not an announcement of availability or pricing.

Apple processes the purchase and associated account and payment information under its own terms. NeoWriter uses transaction or entitlement information needed to unlock and restore features. The developer does not receive your full payment-card information from StoreKit.

8. Support emails and diagnostics

NeoWriter does not automatically send diagnostic reports or usage statistics to the developer. If you choose to email support, we receive your sender address, message, and any screenshots, diagnostic files, or other attachments you include.

We use that information to respond, investigate the issue you reported, and handle related follow-up. Email is processed and stored by the developer's email provider and mailbox; the absence of an app backend does not mean support correspondence is never stored.

Send only what is needed. Review and redact reports before attaching them, and do not send API keys, passwords, recovery phrases, payment details, or unrelated private writing. Providing diagnostics is voluntary. See Support for a minimal report checklist.

9. Retention and deletion

Different copies need to be managed separately:

• Local library and Trash: app data remains until removed through the app or appropriate platform controls. Deletion into Trash is not the same as permanent deletion. Keep a backup before removing data you may want to recover.
• Mac app data: deleting the application itself may leave its Application Support or sandbox-container data and backups behind. Do not assume uninstalling the app clears every local copy.
• CloudKit: private CloudKit records are distinct from ordinary iCloud Drive files. Deleting a Drive folder alone should not be treated as deletion of the CloudKit database. Use the appropriate app-specific iCloud storage controls where available, or contact support for guidance.
• WebDAV, cloud folders, backups, exports, and published posts: remove unwanted copies at their actual destinations, considering their retention and recovery settings.
• External AI requests: copies or logs already held by a provider are governed by that provider's retention and deletion options.

Support correspondence is kept for handling your request and related follow-up, subject to applicable record-retention obligations. You may ask us to delete correspondence we hold; we will explain any information that must be retained. Provider-managed backups and retention are subject to the email service's policies.

We do not sell support information or use it for advertising. Disclosure may be necessary to the email service that handles the correspondence, to respond to a legal obligation, or to establish or defend a legal claim.

10. Choices and privacy requests

You can write locally without enabling external AI or sync. You can change or disable integrations and decide whether to send a support report. Changing these settings does not automatically erase copies already delivered to another destination.

Depending on applicable law, you may have rights to access, correct, delete, restrict, or object to processing of personal information. Contact genjux1024@gmail.com about information held in support correspondence. We may need proportionate information to identify the relevant request, but do not send unrelated identity documents or secrets unless a necessary, appropriate process has been agreed.

We cannot independently access or erase your private cloud account, published site, or an AI provider's records. Requests about those services may need to be made to the relevant provider. Depending on your location, you may also have a right to complain to the relevant privacy authority.

11. Age ratings and external services

No App Store age rating has been confirmed for NeoWriter, which has not yet been listed. External AI providers and other services may impose their own age and account requirements.

If you are a parent or guardian and believe a child has provided personal information through support, contact us so the request can be handled under applicable law. Chosen external services may process data in different countries; review their data-region and transfer terms before sharing material.

12. Changes and contact

We will update the date on this page when the policy changes. Where required, material changes will be accompanied by appropriate notice or consent. A website policy update does not itself grant permission for a new external AI destination or broader text scope.

For questions or privacy requests, email genjux1024@gmail.com. Read the Terms of Use for information about using the app and third-party services.