Lydia Bauer

Private studio

About the assistant & your studio data

A practical description of this private website-editing tool, its saved content and how to get help.

Back to the studioContact Iyan for support

AI drafts, human decisions

Lydia’s Website Assistant uses an Azure-hosted AI model. Conversation content, relevant website content and attached images may be sent to that model to generate a reply or proposed change. AI replies can be wrong: review wording, facts, images and the preview before approving anything.

The application gives the assistant a limited website snapshot, image inspection and revision-proposal toolset. The model does not receive a publishing tool. This is application-level restriction, not a claim that the computer runs in an operating-system sandbox.

Publishing is a separate process requiring an authorized editor’s explicit approval of a checked revision. Released snapshots are kept so an earlier release can be restored.

Two authorized editors, one shared website

Lydia and Iyan are the two authorized editors. There is no public signup. Saved conversations, images and website revisions are shared between those editors, not separate private accounts. Sign-in links expire and can be used once.

What is stored and where it goes

This page does not promise a particular AI-provider retention period or deletion from provider logs, backups or previously published copies. Ask Iyan about the configured service if that affects what you can share.

When the assistant computer is offline

The worker runs on Iyan’s existing PC. If that PC or worker is offline, the online studio can still save requests to its cloud queue; they wait until the worker reconnects. A saved or queued message does not mean the assistant has completed it. Processing uses the PC as well as the Azure-hosted model service.

Browser drafts are different from saved conversations

Unsent text and completed upload references can be kept in this browser’s local storage, scoped to the signed-in editor and tab. They are not a server backup and are not synchronized to another device. A completed image upload is already stored on the server even if its message has not been sent. Signing out clears studio drafts where browser storage is available; clearing this browser’s site data removes its local copies, not server conversations. Avoid a shared browser profile for sensitive drafts.

Retention and deletion requests

Shared conversations and attached images are retained until an explicit deletion is reviewed and carried out. There is no automatic conversation expiry. Expired operational records and provably abandoned, never-attached uploads can be considered by a bounded maintenance process; it defaults to a dry run, and no scheduled cleanup is enabled by this change. Legacy, referenced or ambiguous images are not treated as safe to delete.

Release audit records and rollback snapshots are protected from routine cleanup. Deleting a conversation does not by itself erase those copies or a published website. A request affecting those records needs a separate review of what must be retained and what rollback capability would be lost.

Export or request a review

The JSON export includes both editors’ shared conversations, image metadata, revision summaries and release records. It excludes image bytes, operational credentials, private preview links and snapshot files. Download individual images while signed in to the studio, or contact Iyan for an assisted content/image export. Pause editing while exporting; it is a paged content copy, not an atomic backup.

Keep downloaded files private: signing out will not remove a downloaded copy.

To request review of shared studio data for deletion, type REQUEST SHARED DATA DELETION below. This saves a request only: it does not delete data, stop running work or authorize bulk deletion. Iyan must review scope with both editors and stop active jobs before any approved content removal.

Support and follow-up

Email iyanbarry@gmail.com for help, data questions or a deletion review. Include the request ID if one was saved. The studio does not automatically email requests or promise a response deadline. Do not email passwords or sign-in links.