Privacy-first by design, not as an afterthought
PrivacyResize is structured so the core resizing workflow stays on-device by default. When you enable account features, the app stores metadata needed for those features, not your original images.
What stays local
Standard image resizing, cropping, compression, and ZIP export happen in your browser. Original image files are not uploaded by default.
What can be stored
When Firebase features are enabled, the app may store preset configurations, usage metadata, favorites, and feedback submissions.
What Firebase is for
Firebase Auth supports sign-in. Firestore stores metadata. Storage is reserved for site assets or admin demo files, not default user uploads.
If you deploy this codebase yourself, you are responsible for your Firebase configuration, retention settings, access controls, and any legal notices required for your jurisdiction or customers.
If a future feature introduces uploads or storage of source files, that behavior should be made explicit in product UI before users enable it.