Last updated: March 27, 2026
PixelSave ("we", "our", "the app") is a journaling application built with a local-first architecture. Your journal entries are stored on your device by default. We are committed to protecting your privacy and being transparent about how your data is handled.
All journal entries, checkpoints, tags, and app preferences are stored locally on your device. We do not have access to this data unless you opt in to cloud sync.
If you enable cloud sync, your journal data is transmitted to our servers to keep your devices in sync. Sync infrastructure is hosted on Fly.io with data stored in Neon Postgres. End-to-end encryption for synced data is planned and will be added in a future update.
Local storage: Journal data is stored in an on-device database. It never leaves your device unless you enable sync.
Cloud sync: If enabled, data is encrypted in transit (TLS) and stored on servers hosted by Fly.io with Neon Postgres as the database provider. End-to-end encryption (where we cannot read your data even on the server) is planned for a future release.
PixelSave uses the following third-party services only when cloud sync is enabled:
No other third-party services receive your data. We do not use analytics platforms, crash reporting services, or advertising networks.
You can export all your journal data at any time in Markdown (with YAML frontmatter) or JSON format. Export is always available regardless of your subscription status. Your data is yours.
You can delete individual entries or all your data from within the app at any time. If you use cloud sync, you can request full deletion of your server-side data by contacting us at the email below.
PixelSave is not directed at children under 13. We do not knowingly collect personal information from children.
We may update this privacy policy from time to time. Changes will be posted on this page with an updated revision date.
If you have questions about this privacy policy or your data, contact us at: