A Local-First App Privacy Checklist
Local-first privacy is strongest when the product page, support page, and privacy policy all say the same plain thing.
LOCALOPTIONAL
CLOUD
Three takeaways.
Keep the useful core visible and under the user's control.
Start with the data map
List the inputs the app handles, where each input is stored, and whether the app needs an account, server, analytics tool, or upload path for the core workflow. If the useful job can happen on device, say that directly.
Name what stays on device.
Describe user-controlled sharing
A local-first app can still let the user export, email, screenshot, back up, or share a result. The important boundary is whether sharing happens only when the user chooses it, not because the app quietly sends private work somewhere else.
Separate optional exports from automatic uploads.
Keep every surface consistent
The product page, support page, privacy page, store copy, and help answers should use the same privacy story. Mixed language creates doubt, especially for apps that handle purchases, photos, claims, offers, notes, or private workflows.
Keep policy copy aligned with the real app.
Local-first privacy is strongest when the product page, support page, and privacy policy all say the same plain thing.