Beta notice · Updated 25 October 2026. Operator contact details, retention schedules, and regional eligibility must be confirmed before public launch. This notice is not a legal compliance certification.
This notice describes the Orion Beta as currently implemented. Orion is operated by The Orion Project. Privacy contact: the-orion-project@zohomail.eu. Do not use the service to submit sensitive or confidential information.
Orion does not save demo conversation content to its chat database. Your browser keeps the current conversation in page memory and submits recent turns with each message. Google processes the content to generate responses. This does not mean that the hosting or model provider retains nothing.
The demo allows three messages per network identifier in a rolling 24-hour window, with a five-second cooldown. Usage and abuse-prevention records store a keyed pseudonymous identifier derived from your network address, rather than the raw address in the application's usage tables. This identifier is not guaranteed anonymous. People sharing a network may share its allowance. Infrastructure may process network addresses independently.
We store your messages, replies, chat titles, message status, timestamps, and related usage metadata. Orion sends the last four completed user/assistant pairs, compact summaries of older chat content, and selected profile memory facts to the model when relevant. Orion saves durable profile facts as part of its normal reply, and periodically condenses older messages into dated summaries.
You can disable profile memory, review or edit facts, delete individual facts or all profile memory, and delete chats in the app. Deleting a chat removes its messages and chat summary from the live application records, but does not remove separately stored profile facts. Delete those separately in Settings. Disabling memory is not a deletion request and does not disable per-chat summaries.
In Beta chats, file names, text excerpts and analyses of documents, images, audio and video are retained with the original message and timestamp for follow-up questions. These are condensed context, not a permanent copy of the original file. Deleting the chat deletes these saved analyses. Demo analyses remain only in the current page session.
Files you choose are read by your browser and submitted to Orion and Google when you send the message. The current attachment limit is three files totalling 50 MB. Original attachment bytes are not saved in Orion's chat database or file storage; file names and related text may remain in messages, and generated responses may contain information from the files. Files are not automatically reattached to later turns. Larger uploads (over about 12 MB in one message) are sent through Google's Gemini Files API using the same key; Google states such files are stored for up to 48 hours and then deleted automatically.
Voice recording begins only after your action and browser microphone permission. Recording stops when you finish or after 60 seconds. The complete recording is sent to Gemini to produce an editable text draft. It is not automatically sent as a chat message. You can correct or delete the draft before sending. Original audio is not saved by Orion, but Google processes it under the provider terms below. Do not record other people without an appropriate right to do so.
Orion uses Google's Gemini API. Submitted content can include messages, files, recordings, recent conversation turns, summaries, and memory facts. Google's unpaid-service terms allow content and responses to be used for product and model improvement, with possible human review, and say not to submit sensitive, confidential, or personal information to unpaid services. Regional exceptions and account configuration affect these terms; Orion cannot promise that content is never used for training.
Google requires API clients made available to people in the EEA, Switzerland, or the UK to use paid services. The existence of a free model tier does not override that requirement. Each demo and participant project must meet Google's applicable eligibility and billing requirements before use in those regions. See Google's Gemini API terms and pricing and data-use disclosures.
Orion access keys and revocable session tokens are stored as keyed hashes on the server. The browser stores a session token and expiry in local storage so you can return without re-entering the key; the raw access key is not stored there. Signing out removes this browser session and revokes it on the server. Administrative Google API keys are encrypted server-side and never displayed back to participants.
Administrators can review access requests, participant records, key status, usage, and audit events. Chats are isolated by participant access. Transport encryption and credential encryption are not end-to-end encryption. Never share your access key or use a shared device without signing out.
If you submit reply feedback, Orion stores your rating, optional comment, the submitted reply and timestamp for administrators to review. Beta submissions are associated with your participant record. Demo replies are stored only when you explicitly submit feedback. Sharing copies or sends the selected reply through your browser; it does not create a public chat link. PDF and HTML exports are generated locally in your browser.
Requests store a normalized email address, submission timestamps and counts, a notice version, and the review outcome. Network-derived abuse controls help limit repeated submissions. An administrator approves or rejects applications; approval creates a key if a dedicated slot is available. At present, the administrator delivers that key manually by email. Submitting a request is not consent to marketing.
Beta chats, memory, feedback, application, session and usage records are deleted within 90 days after the Beta ends, or sooner if you ask by email at the-orion-project@zohomail.eu. You can also delete chats and memory yourself in the app at any time. A quota reset does not delete its underlying record. Deletion from backups, operational logs and provider systems may follow those providers' own schedules.
Where applicable law provides them, you may have rights to access, correct, delete, restrict or object to processing, request portability, and withdraw consent for processing based on consent. These rights have legal conditions and exceptions.
Service delivery, optional personalization, security controls, and access applications need their own documented lawful bases. Hosting and Google processing may involve international transfers; actual locations, contractual safeguards, and subprocessors have not been verified. This notice does not assert that all processing occurs in the EU. See the GDPR, particularly Articles 12–14.
We will update this notice when processing or product behavior changes. Material changes should be communicated before they apply. The date above identifies this version. Contact email: the-orion-project@zohomail.eu The Orion Project