Beta Privacy Notice

Last Updated: June 2026 · Beta notice

        Local-first direction: Palim is designed so drafts, sources, and manuscripts stay in a local workspace by default. Palim accounts are used for official entitlements, feedback attribution, update eligibility, and Beta Core grants; they do not create remote manuscript storage.
      

This beta privacy notice explains the intended privacy boundaries for Palim preview materials and public web pages. A final Privacy Policy will be published before general availability or paid distribution.

1. Manuscript & Writer Assets

Palim is being built as a self-contained local workspace. In the intended desktop architecture, files, assets, databases, configuration keys, and story branches are stored in local project directories:

No website manuscript upload: The public website does not accept manuscript uploads.
User-managed synchronization: Any future project synchronization must be explicitly configured by the user or introduced under a separately reviewed policy.

2. AI Collaboration & API Boundaries

Palim provides optional AI-assisted writing tools such as AI Copilot and Revision Workbench. In the current product direction:

User-selected services: AI features depend on services the author configures or explicitly enables.
Provider policies apply: Data sent to external providers is governed by those providers' terms and privacy policies.
Review before sharing: Authors should avoid sending sensitive drafts to any external service unless they understand that service's data terms.

3. Website Tracking & Diagnostics

The current static website does not include advertising trackers, checkout scripts, or third-party support widgets. Beta desktop builds use Palim-owned telemetry to improve reliability and product quality:

Product improvement events: Palim may collect bounded first-party events such as opened surfaces, command ids, account state outcomes, AI settings outcomes, model choice refs, third-party subscription action outcomes, update outcomes, coarse duration buckets, and error fingerprints.
Content boundary: telemetry must not include manuscript text, prompts, generated text, source file paths, provider tokens, cookies, passwords, raw logs, or third-party account identifiers. Optional product improvement events can be disabled in the desktop Support and Feedback panel; essential operations, security, and reliability events remain on.

4. Data Retention & Control

Because Palim is designed around local project files, authors should maintain their own backups during beta. Palim accounts and first-party telemetry are retained separately from local manuscripts and do not become a cloud manuscript repository.

5. Desktop Updates

The beta installer, updater feed, and artifact hosting are published on the official update domain and are integrity-verifiable. The website still does not accept manuscript uploads, connection keys, passwords, or full local paths.

6. Contact & Data Rights

For privacy or local-first boundary questions, contact contact@nyxevo.com.