Beta Privacy Notice
Local-first direction: Palim is designed so drafts, sources, and manuscripts stay in a local workspace by default. The website does not currently provide accounts, checkout, analytics pixels, or manuscript upload features.
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. Zero Telemetry & Diagnostics
The current static website does not include analytics pixels, advertising trackers, checkout scripts, or third-party support widgets. For the desktop product:
- Diagnostics by action: Diagnostic logs should be exported and shared only by explicit user action.
- Policy before telemetry: Any future telemetry or crash-reporting feature must be disclosed before it is enabled in a public build.
4. Data Retention & Control
Because Palim is designed around local project files, authors should maintain their own backups during beta. The website does not currently host user accounts or remote manuscript storage.
5. Desktop Updates
Public beta readiness requires a verified HTTPS desktop updater before downloads open. Update metadata and artifact hosting will be documented before the updater is enabled in a public build.
6. Contact & Data Rights
For privacy or local-first boundary questions, contact [email protected].