Before you share
How your data moves.
A practical guide to what is saved, what is sent to providers, and what happens when you use tools or delete your work.
At a glance
This is a saved-workspace service, not a zero-retention inference service. Winfield Research Corporation does not sell your content or use it to train models. Saved chats, uploads, execution files, logs, and backups can persist, and external providers handle information needed for inference and enabled tools.
This guide supplements our Privacy Policy. The operator is Winfield Research Corporation, a Canadian federal corporation. Contact [email protected] for account or data questions.
What can persist
| Information | How it is handled | Important limitation |
|---|---|---|
| Saved chats and responses | Stored to support conversation history and returning to your work. | History can include thinking output, attachments, and tool results. This is not memory-only processing. |
| Uploads, notes, and knowledge | Files, extracted text, and material you create can be stored in the workspace. | Removing a conversation does not necessarily remove separately stored material. |
| Code and terminal work | Execution uses server-side tool services. Created files and work directories can persist. | The current deployment does not provide a dedicated, separately isolated machine for each account. Do not put secrets or confidential third-party data in tool files. |
| Account and usage records | Identity, role, starter-credit eligibility, token counts, balances, and ledger entries support access and billing. | Records needed for accounting, legal obligations, and disputes may survive account deletion. |
| Payments | Payment attempts, transaction references, addresses, and verification records support crediting and reconciliation. | Blockchain transfers are public and cannot be erased or reversed by deleting an account. |
| Operational logs and backups | Services produce request and diagnostic logs; operators may retain backup copies. | No fixed automatic purge is guaranteed. Logs are not promised to exclude all content or query details. |
Upload size and supported files
Uploads must fit within a 100 MB request-body limit, including multipart metadata. Keep individual files below 100 MB, and send smaller files separately. If an upload is rejected, reduce its size or compress it before trying again. Larger-file uploads are not available yet. File size does not override the model's context limits or supported input types; video inspection is limited to clips up to 60 seconds, without audio.
Inference and optional tools
Generating an answer
The inference provider receives the context needed to answer: prompts and system instructions, selected conversation history, images or video frames, relevant document excerpts, and tool results. Our no-training statement describes Winfield Research Corporation's own use. We do not promise that all provider retention, geographic-processing, or independent data-use terms are identical to ours.
Searching and fetching
Search sends queries to search engines, and fetching contacts the target website. Queries, URLs, network information, and relevant text may be handled by external providers. Results can become part of your conversation and subsequent inference context. Turning off search does not turn off normal inference processing or saved chat history.
Code, terminal, and connected tools
Enabled tools may execute code, read or create files, contact websites, and send selected information to connected services. Tool descriptions and results can be sent back to the model. Inspect tool permissions and review generated code before execution. A tool can involve data flows and retention beyond the chat interface.
Images and video
Image inputs can be sent for inference. Supported video uploads are converted to timestamped frames for inspection; this does not include processing video audio. Uploads and generated or extracted material can remain in storage. Native audio input is not supported.
Deletion and retained copies
Use the workspace's available controls to delete or export conversations and manage stored material. For an account-level request or removal of associated uploads and tool files, contact [email protected]. We may need to verify ownership and clarify what you want removed.
Deletion in one screen does not automatically prove erasure from another storage area, a shared copy, a log, a manually retained backup, or an external provider. We do not guarantee an immediate purge across all those locations or a fixed backup-rotation period. When handling a request, we will explain the scope and any legal or operational exception. Applicable privacy rights remain available.
Financial and transaction records may be retained where required for accounting, legal compliance, or dispute resolution. Public blockchain records and independent copies held by others are outside our ability to erase.
Practical choices
- Upload only material you are authorized to use and comfortable having processed as described here.
- Keep passwords, authentication tokens, recovery phrases, private keys, and confidential secrets out of prompts, uploads, and execution files.
- Enable only the tools needed for a task and review sharing permissions before publishing a link.
- Export work you need to keep, and contact support for broader removal or account-closure requests.
- If your work requires strict zero retention, dedicated execution isolation, or a guaranteed processing region, do not assume this deployment meets that requirement.
We will update this guide if operational practices change. Material changes are also addressed in the Privacy Policy and Terms of Service.