Privacy Policy
Last updated: October 28, 2026
Operator and contact
HAI Orbit is operated by Fu, Chih-Chen. For privacy, account or support requests, contact support@haiorbit.com.
What Orbit processes
Orbit processes account identity and authentication information, display names, workspace membership and permissions, website content and images, private drafts, AI messages and selected elements, formal proposals, review decisions and published versions. Beta and Team waitlists separately store the submitted email, preferences, consent information and time.
Why the information is used
We use this information to authenticate accounts, enforce access, save and restore work, continue private AI conversations across sign-ins, support collaboration and publishing, operate the invite-only Beta and prevent abuse. Orbit does not build cross-workspace personal-memory summaries or user profiles for AI personalization.
Private conversations and shared work
AI conversations are saved in each collaborator’s private branch within a workspace. New proposals store formal work snapshots, a description, author and review information, without copying the full private conversation. Proposal responses filter historical chat copies as well. Older copies may still exist in stored proposal records and backups; this release does not erase them. Published work and history remain subject to workspace permissions. Publishing a workspace version does not by itself make the workspace publicly accessible.
AI processing
For an edit, Orbit sends the current private website, selected elements, design context and bounded recent messages from that collaborator’s workspace chat. Even a local element edit can include the full current website. Context minimization and separate named conversations are still under development and are not promised as available in this Beta. OpenAI processes text requests with store:false; this is not a promise of zero provider retention. Image workflows can also send design context, a visual brief and generated images for processing. Content or URLs you supply can themselves contain personal information; do not include unnecessary sensitive information. Provider security, abuse-monitoring and other applicable retention can still apply. See OpenAI API data controls.
The ChatGPT connection
OAuth authorizes your Orbit account and requested capabilities. Access follows your current workspace ownership or membership, rather than a separate per-workspace OAuth grant. The plugin can return authorized website content, styles, image references or bytes, version information and visible proposal metadata to ChatGPT. It does not provide private-chat or unsubmitted-draft retrieval tools. Copies received by ChatGPT are governed separately by your ChatGPT service and account settings; Orbit cannot retract previously delivered copies.
Storage, sessions and service providers
Production authentication and collaboration data use Supabase and Postgres; the application is hosted on Vercel and uses OpenAI for AI processing. The browser persists its Supabase authentication session and local interface preferences. Operational and provider logs can include request, error and security metadata. Waitlist abuse prevention stores a keyed network identifier and timestamps, rather than raw IP in that feature’s records; hosting and security providers can maintain their own logs. External image and font hosts receive requests when their resources are displayed.
Retention and removal
Private messages are stored server-side and can remain available across sign-ins. There is no default 30-day automatic chat deletion and no published fixed retention deadline for chats, works, versions, images, proposals, logs or backups. Some workspace actions, including resetting a branch to the latest published version, clear that branch’s chat and Undo records; do not use reset as a privacy-erasure guarantee. The current Beta does not offer a dedicated conversation-only deletion control or automatic account/workspace erasure. Shared work and restoration history have a different purpose from private chat. Contact support for a verified removal request and an explanation of what can be removed or needs to be retained. Historical backups, operational copies and content already sent outside Orbit can remain separately.
Access, correction and broader removal requests
Contact support@haiorbit.com to request access, correction or removal. We need to verify your identity and authority over the affected work and consider other collaborators’ legitimate access and applicable obligations. We do not promise immediate erasure of every backup or third-party copy. Do not send passwords, API keys, OAuth tokens or unrelated sensitive conversations with a request. Contact us for current backup and operational-retention details.
Waitlists and security
Waitlist information is used for Beta or Team selection and outreach, not as AI memory. Contact support to request correction or removal. Server-side checks protect workspace access and private branches; Orbit OAuth and sharing tokens are stored as hashes. No system can promise absolute security, and store:false does not control every third-party copy or log.