Privacy, in plain words.
ozyy is an independent AI workspace created by Ozy. This page describes the controls implemented in this version.
What we store
We store your verified email identity, account preferences, conversations, attachments you upload, sessions, and request usage on the operator’s Windows backend. The primary persistent database and files stay on that computer. Conversation text, account email addresses, preferences, and uploaded text are encrypted in storage using an application key held on the same computer. This protects stored files; it is not end-to-end encryption and does not prevent the operator from accessing data.
Where requests go
The public frontend runs on Vercel. Requests travel to the local backend over an HTTPS tunnel when production is configured. AI requests include conversation context and custom instructions sent to MWAPI and its upstream model providers. Google processes Google sign-in. A configured SMTP service delivers email verification codes. These services process the information needed to perform those tasks under their own terms.
Private from other users
Your conversations require an authenticated account and are never shown to other users. Only you can create a public sharing link. A shared link exposes a fixed snapshot to anyone with the URL until you revoke it or it expires. Editing your conversation does not update an existing snapshot. Administrators can review account and usage metadata.
Safety and moderation access
To keep the platform safe and enforce these terms, the platform owner can read your conversations, sign in to your account to investigate a problem, sign out your sessions, and ban accounts or network addresses. These tools are limited to the owner's account. Each conversation review, account access and action taken while signed in as you is recorded in an audit log. While the owner is signed in as you, account deletion and identity linking are disabled.
Session and network information
For security and abuse prevention, each signed-in session records the IP address it was used from, your browser's user-agent string, and when it was last active. Your account keeps the most recent IP address. This information is encrypted in storage, is visible to the platform owner, and is deleted with the session or your account. Banned IP addresses and ranges are kept until the ban is removed or expires.
Your controls
Export conversations as Markdown, text, or JSON, or export your account from settings. You can delete conversations, attachments, shared links, and your account. Deleting an uploaded file does not remove its text from messages where you included it; delete or edit those messages as well.
Retention and backups
Conversations remain until you delete them or your account. Sessions expire after 30 days. Verification codes expire after five minutes and expired challenges are cleaned up by backend maintenance. Local database and attachment backups are kept for up to seven days and deleted on the next maintenance run. Deleted records may remain in a backup during that period. The backend must be running for cleanup to occur. The encryption key must be backed up separately by the operator.
Anonymous model, token, cost, and request outcome totals remain after account deletion to enforce the platform budget. These totals contain no email address, account identifier, prompt, or response. Administrative audit records retain action identifiers and timestamps for operational accountability.
Browser storage and availability
ozyy uses an HttpOnly session cookie to keep you signed in and a short-lived cookie for Google sign-in state. It does not add third-party advertising trackers. Unsent drafts live in the current tab’s memory while the backend is offline. Closing or reloading the tab can discard an unsent draft. Downloaded exports are saved wherever you choose on your device.
Questions
Use the Contact page to send a workspace support request. This policy must be reviewed against the operator’s actual deployment and service agreements before a public launch.