This notice describes the application’s intended data use. Operator contact details and final retention settings must be confirmed before public launch.
Conversations and contact
Enable Assistant processes what you type using OpenAI. Conversation text stays in browser memory and is sent to the application server and OpenAI to answer. It is not saved in ENABLE’s customer records unless you explicitly save it in your account or submit an inquiry and separately choose to include the conversation. Avoid confidential, sensitive, or identifying information in chat.
OpenAI requests use store: false. This does not guarantee zero provider retention; provider processing and abuse monitoring policies also apply. Closing or reloading the page clears the unsaved conversation from this browser session.
Client accounts and projects
Client accounts use necessary authentication cookies. Saving a project requires consent; including the conversation is a separate choice. Saved drafts are private in the application. Submitting a project shares a snapshot with authorized ENABLE staff for review. Later edits to your private draft do not change the submitted snapshot. Staff-published statuses and milestones are visible in your account.
You can delete unsubmitted drafts in My projects. Saved projects remain until you delete them or request account/project deletion through Contact. Submitted records require an operator-assisted deletion request. Backups may retain deleted data until their retention window expires. Access by infrastructure administrators remains subject to operational controls.
Basic email/password signup does not verify email ownership. Password recovery by email is not available yet. Account access does not grant ENABLE staff permissions.
Conversation limits use an opaque session token and server-side counts, not stored message text. Quota records expire after 90 days and are removed by scheduled maintenance. Anonymous conversations allow 11 successful user messages; signed-in accounts allow 50 per conversation. Failed model requests do not consume a turn.
Inquiries and consent
The form asks for your name, email, optional company, and reviewed project brief. An unchecked consent box controls submission. Consent covers storing the inquiry and contacting you about it; it is not marketing consent. Including a conversation is optional and uses separate consent.
Storage, access, and retention
When configured, Supabase stores inquiries and approved content. Authorized staff review inquiries in a protected inbox. Open inquiries are scheduled for deletion after 180 days from submission; staff must obtain renewed authorization before retaining records longer. Database backups may keep deleted records until their independent retention window expires. Hosting and notification providers also process limited operational information.
Analytics and browser storage
The application counts page categories and selected engagement events in daily aggregates. It does not use advertising cookies, tracking IDs, fingerprinting, or conversation text for analytics. It honors Do Not Track and Global Privacy Control for optional browser events. A theme preference is stored locally. Administrative sign-in uses necessary authentication cookies. Client sign-in uses the same necessary session mechanism. Security limits use a keyed network hash, not a stored raw IP address; infrastructure providers may keep their own access logs.
Your choices
You can use the public pages without chat, submit a brief without a transcript, and request access or deletion of a submitted inquiry. The operator’s privacy contact will be added before public launch.
Notice version: 2026-10-12-v1. Deployment-specific provider locations, operator details, and backup retention must be confirmed before launch.