1. Account and session data
Google provides your basic profile and email for sign-in. We store the information needed for your account and sessions; we do not request Google Drive, Photos or social account access. Essential HttpOnly session cookies keep you signed in. Sessions expire after seven days.
2. How photos are processed
Choosing a photo creates a local preview. Before you submit, the photo stays in this browser. When you choose Generate image, Monora sends the photo to its server and OpenAI. Monora validates file contents, normalizes orientation and removes EXIF and GPS metadata. The AI provider receives the normalized input and the style reference needed for your chosen effect.
A generated image is briefly kept on a private server volume and delivered only to the signed-in account that requested it. Photos and generated images are not public URLs, are not served through a public image CDN, and are excluded from application logs and database backups.
3. Storage in this browser
IndexedDB stores a photo-and-style draft for up to 24 hours without activity. A successful delivery or sign-out removes the persisted draft photo. Your creations store the output image, a thumbnail and basic style metadata, with a limit of 100 images or 300 MiB including thumbnails.
Local images are not synced, backed up or separated by account. Anyone using this browser may be able to view them. Browser cleanup or changing browsers, devices or website origin may remove access. Download files you want to keep. Writing-tool drafts and results, when enabled, stay in this tab for up to 24 hours and are cleared on sign-out.
4. Monora retention and cleanup
Server input photos are removed within five minutes after the task ends. Successful server results stop being available after one hour and are removed within the next five minutes. Temporary files have an absolute two-hour cleanup limit. Pending tasks without a known result expire no later than 30 minutes.
Task metadata, idempotency records, usage counters and minimal events are retained for 30 days. Support tickets and text-only image feedback are retained for 90 days unless an earlier verified deletion request applies. Writing output, when enabled, is cached for ten minutes for response recovery, not a permanent writing history.
Deleting an account revokes sessions and stops new requests. Identifiable account-related server data is removed within 24 hours while already-started processing is safely concluded. Local creations remain in this browser. Operational database backups rotate after seven days; deleted records may persist in those restricted backups until rotation. Temporary image files are never included in those backups.
5. OpenAI and Google
OpenAI performs requested AI processing; Google handles sign-in. Their processing and retention are governed separately by their applicable policies and our account settings. Monora’s own cleanup deadlines are not promises that these providers delete data on the same schedule.
We do not claim zero provider retention. Applicable provider settings, processing terms and international transfer details must be verified for the actual operational accounts before public launch. Enabled writing requests use the Responses API with storage disabled, which does not itself establish zero retention across all provider systems.
6. Support, feedback and limited events
The contact form stores your email, topic, message and a reference number. An optional task ID is linked only after ownership is verified. Image feedback stores a reason and text, without attaching your original or result. Avoid including sensitive information in either form.
Minimal product events may record an allowed action, anonymous session identifier, style/version or task identifier and time. They exclude image content, prompts, original filenames, form bodies, OAuth tokens and full IP addresses. Rate limiting uses a protected hash rather than a stored full IP address. There are no advertising pixels, session replay or marketing trackers in this build.
7. Your choices and requests
You can download and delete local creations, sign out, or initiate account deletion from Account. For questions about data access, correction or deletion, contact us using the Privacy topic. We may need to verify identity before acting on a request. Browser controls can clear cookies and local data; doing so can also delete your creations.
8. Operator and policy changes
Operator identity, contact address and policy date are configured before public launch. This development policy is a draft until those details and actual provider settings are reviewed. Contact us through the on-site form for privacy questions.