Privacy and your data
Opssembly is a personal infrastructure planning project maintained by Onur Özgültekin. You can use the local designer as a guest; a Google account is optional.
Google sign-in
When Google sign-in is enabled and you choose to use it, Opssembly receives your Google account identifier, display name and email address to create or recognize your account. Your Google password is not sent to Opssembly. We do not request access to Gmail or Google Drive, and do not keep Google access or refresh tokens after sign-in.
Your account projects
Projects you explicitly save to your account are stored in Opssembly's server database with their name, diagram content, owner, version and timestamps. Signing in does not automatically upload your local projects. The application checks account ownership before listing, opening, updating or deleting a personal project.
You can download designs as .opssembly files and delete saved account projects from Projects. Deleting an account project removes the active database record, not copies you downloaded, local copies, shared room copies or any existing server backups. Server storage and operational backups are managed by the developer.
Local storage and cookies
Local projects, local recovery drafts and editor preferences use browser storage. Unsaved account-project drafts use account-separated storage in the current tab's session. Essential cookies identify your guest session, maintain a signed-in account and protect requests against forgery. Signing out ends the current account session; it does not delete your local projects.
Live rooms and feedback
Live rooms use a separate browser-session identity for membership and ownership. If you are signed in, your Google profile name is shown to room participants and used on new chat messages and feedback; otherwise a guest name is used. Sharing a room sends its design to the server and makes it available to admitted participants. Room designs, chat messages and uploaded attachments are separate from personal account projects. Feedback messages and any contact details you provide are sent to the developer.
Take care with infrastructure details
Do not put passwords, access tokens or other secrets in diagrams, chat or feedback. Keep downloaded backups of important work. Only share room links with people you trust.
Contact and deletion requests
For questions about stored data or to request removal of your account profile, contact the developer through the feedback form. Please provide a way to reply; ownership may need to be verified before account data can be removed.