Luke Research Preview Terms — thinking oracle
Luke Research Preview Terms
Last updated: June 2026
Overview
Luke is an experimental research preview provided by Thinking Oracle for limited evaluation and exploratory use. It is not a finished or commercially supported product and may change or be discontinued at any time without notice. This page explains how Luke works, how it handles your data, and how this relates to Thinking Oracle’s main Terms of Use and Privacy Policy.
Research preview nature
Luke is offered solely for experimentation, prototyping, and personal workflows, not for production or safety-critical use. Features, performance, and behavior may be unstable or incomplete. You should not rely on Luke for medical, legal, financial, or other high-risk decisions.
Access to Luke may be limited, suspended, or withdrawn at any time as we iterate on the product.
No unnecessary data collection or tracking
Luke is built to minimize how much data is collected and how long it is kept. In everyday use, Luke only sends your prompts and context to the AI services you configure, for the purpose of generating responses.
Thinking Oracle does not use your in-product prompts, responses, or files for cross-site tracking, ad-tech style profiling, or invasive analytics. Any analytics we use are designed to rely on limited, high-level signals rather than detailed records of individual conversations.
For a more detailed description of how data moves through Luke and the services you choose to connect, see “Data flow, storage, and tracking” below and the Thinking Oracle Terms of Use and Privacy Policy linked in the site footer.
Data flow, storage, and tracking
Luke is designed with a local-first and data-minimization approach: Thinking Oracle aims to receive and retain as little of your content as is reasonably necessary to provide the service.
In normal use, your prompts, context, and responses are sent to AI model providers via APIs in order to generate answers. How those providers process and store your data is governed by their own terms and privacy policies.
Depending on how you configure Luke, this may work in one of two broad ways:
If you connect your own accounts or API keys (for example, to third-party model providers), your requests are sent from Luke to those services using the credentials you provide. In that mode, data handling is primarily governed by the terms and policies of the services you choose.
If you use access options offered by Thinking Oracle (such as bundled model access or hosted routing), your prompts may be relayed through Thinking Oracle or its infrastructure partners solely for the purpose of delivering the requested functionality and maintaining security and reliability. Thinking Oracle does not use this content for unrelated purposes such as advertising or building independent behavioral profiles.
Luke is not intended to collect or retain your prompts, responses, or files beyond what is operationally necessary to provide, secure, and improve the service in a proportionate way, and emphasizes aggregate or de-identified information over detailed records of individual interactions.
Luke does not use your in-product prompts, responses, or files for cross-site tracking, ad-tech style profiling, or invasive analytics. Any analytics in use are designed to minimize personal data and focus on high-level, aggregate patterns rather than individual user journeys.
Account and website data
Separately from Luke’s local behavior, Thinking Oracle may collect limited information related to your account, billing, or website usage, as described in the main Terms of Use and Privacy Policy (for example, when you visit thinkingoracle.com, sign in, or subscribe to updates).
This account and site data is processed and stored according to the practices described in those documents.
Luke itself does not add any additional server-side collection of your prompts, conversations, or local files.
If there is any inconsistency between this page and the Thinking Oracle Terms of Use or Privacy Policy, those documents will prevail with respect to account and website data handling.
Your control and local storage
Luke is designed so that you stay in control of whatever it keeps over time.
Any ongoing state that Luke maintains for you (such as conversation history or workspace state) is stored locally in your app or browser storage on your device.
You can clear or reset Luke’s local state at any time where supported in the UI.
You can remove all Luke data on a device by uninstalling the app/extension or clearing its storage from your system or browser settings.
Any backups of your device (for example, platform-level backups like iCloud or system backups) are governed by the policies of your operating system and backup provider, not by Thinking Oracle.
Thinking Oracle does not store your Luke conversation content; hosted prompts pass through transiently to deliver answers and are not retained, so there is no central conversation store to access, restore, or delete.
Security
Since your Luke data is stored only on your device, the security of that data depends primarily on:
Your device’s operating system security.
Your local configuration (such as disk encryption, lock screen, and backup settings).
Keeping your operating system up to date.
Thinking Oracle does not have access to your local Luke data and cannot view or recover it if your device is lost, compromised, or reset.
Changes to this notice
We may update these Luke Research Preview Terms from time to time, for example if:
- We introduce an optional cloud-sync feature.
- We change how Luke integrates with your Thinking Oracle account.
- We need to clarify language for legal or regulatory reasons.
When we make material changes, we will update the “Last updated” date on this page and, where appropriate, provide a notice within the Luke interface or on the Thinking Oracle website.
Contact
If you have questions about Luke’s research-preview status or these terms, please contact Thinking Oracle using the methods listed in our main Privacy Policy and Terms of Use.
- Email: privacy@thinkingoracle.com