Data retention
Last updated: 22 October 2026
Removing something from view is not always the same as erasing every copy. Here is how retention currently works.
This page supplements our privacy policy. QuineOS is operated by Timur Carpeev. For data we control, contact info@quineos.com. If you connect to a separately operated server, its operator manages the data held there.
Beta waitlist
We store your email address and signup time with Cloudflare while managing beta invitations. These entries do not expire automatically. Email info@quineos.com to leave the list or request removal. Submission rate limits use IP addresses in temporary memory with a one-minute window; they are not saved with your waitlist entry.
Website traffic and enquiries
The public pages do not maintain a visitor account or an application database of page visits. Cloudflare may retain network and security information under its service settings and privacy policy; there is no single QuineOS expiry period for those provider records.
For enquiries we control, retention is based on the time needed to resolve the request, complete relevant follow-up, and meet any applicable legal obligations or resolve a dispute. You may request removal when the enquiry is finished.
Tasks, goals, notes, and calendar records
Records remain in the connected installation until they are removed or its storage is cleaned up. Completing, rejecting, or archiving a record changes its state; it is not erasure. The current software has no general age-based expiry for this content.
Deleting a record can retain its previous content in revision history. Full erasure therefore requires attention to history and other copies as well as the active record. Imported source files or connected services can contain additional copies and may recreate a record if synchronization continues.
Conversations and submitted images
Requests, transcripts, replies, and delivery records may remain in the assistant journal and the connected Codex conversation. Starting a new conversation or archiving a thread does not erase the old one. There is no general automatic expiry for QuineOS conversation journals.
Queued screenshots may be stored until processing begins. The bridge then removes the queued image bytes and retains a digest, but the image may remain in the AI conversation or its provider's history. Removing one copy does not remove those other copies.
Voice
The current Mac dictation implementation processes audio buffers using on-device speech recognition and does not save an audio recording. The assistant bridge receives text, not raw microphone audio. The resulting text follows the conversation retention described above. Apple's system dictation and Shortcuts have their own processing behavior and settings.
Backups
The server's default backup configuration runs every 24 hours and retains the newest 30 verified snapshots. The operator can change these settings. This is a snapshot count, not a guaranteed 30-day deletion deadline: missed runs, changed settings, or failed verification can keep older copies for longer.
Snapshots include records and revision history. Older snapshots are removed during successful retention cleanup; independently exported backups are outside that rotation. Erasure requests must account for backup copies and avoid restoring erased information into active use.
Device storage, credentials, and logs
Apps can retain cached content, connection credentials, notification identifiers, and preferences on the device. Revoking a connection stops its authorized access; it does not automatically erase local caches or server history. Uninstalling an app does not erase the connected server, and protected credential storage may persist separately.
Operational logs and request records depend on the installation and hosting configuration. There is no single automatic expiry across all of these stores. The operator must review their purpose and remove data that is no longer needed.
AI and other connected services
Provider-held copies follow the relevant provider's retention rules and account settings. Deleting local QuineOS content does not itself delete an OpenAI conversation, a calendar event at its source, or a record held by another connected service. Provider deletion controls or a separate request may be needed.
Request access or erasure
Email info@quineos.com and describe the data and installation concerned. Do not include passwords or access tokens. We will identify the copies we control, verify identity where needed, and explain the steps and any limits that apply. For a self-managed installation, removal also needs to be carried out by its operator.
Where the law requires a record to be retained, or retention is necessary for a legal claim, we will explain that exception and its scope. This page describes retention behavior; it does not limit any right to request earlier erasure under applicable law.