Portfolio content and processed images are stored in this browser and are not uploaded by the Phase 1 builder. No account exists. Download a project backup because browser storage can be cleared.
Portfolio projects stay in the browser
When you use the builder, the current portfolio project is saved to IndexedDB in the browser profile on this device. Supported images are resized and compressed in the browser, then stored in IndexedDB as local blobs. The current application does not send that content to Portfolio Work Studio, a database, or a cloud-storage service.
Small interface preferences, such as a dismissed orientation message or the selected editor panel, may be stored in localStorage. They do not contain the body of your portfolio project.
No account system exists in this release
There is no registration, login, password, email-verification, session, cloud-sync, or password-recovery system. You do not need to provide an email address to build or download. An email address you enter as portfolio content is intended for the portfolio you create; it is not used to create a Portfolio Work Studio account.
Browser storage can disappear
Local storage is controlled by your browser and device. Clearing site data, private-browsing behavior, storage pressure, browser resets, device loss, or some privacy tools can remove a local project. Portfolio Work Studio cannot restore a project that existed only in deleted browser storage.
Use “Download project backup” after meaningful edits. The `.pws-project` file is controlled by you and can include your structured content and processed images. It is readable JSON and is not encrypted, so store and share it with the same care as the information inside it.
Website downloads are controlled by you
The website ZIP is assembled locally in browser memory. It contains files intended for publication. Before uploading it to a host, review email addresses, phone numbers, project details, names, image content, and any confidential material. Publishing the exported site to a third-party host makes your relationship with that host subject to its terms and privacy practices.
Ordinary infrastructure logs may exist
The infrastructure serving the Portfolio Work Studio application may create ordinary request logs, such as request time, requested path, IP-derived network information, user agent, response status, and security events. Those logs are separate from portfolio content stored in the builder. This release does not install marketing trackers or product analytics scripts.
Future publishing is not active
A future phase may add hosted publication, mandatory email verification, passwordless magic links, and wildcard portfolio subdomains. Those features would require a separate privacy update before launch. They are not present or silently collecting information now.
Your practical controls
- Download a project backup from the builder.
- Reset the project to clear the active project and stored images from the application database.
- Use browser settings to clear all data stored for this site.
- Remove private details before downloading or publishing a website.
Questions and review
This page describes the implemented Phase 1 behavior. A production operator contact channel and professionally reviewed privacy notice must be established before commercial launch or any future data-collecting feature.