Data and trust
Know what you share,
who can retrieve it and where it goes.
Understand what you connect, who can access it and where it is processed. These are the boundaries of the current hosted service. Any different deployment must be agreed and verified with your team.
Trying a public watch?
Use a public business description. It can inform external searches and model requests. Do not enter confidential shipment, customer or supplier details.
Planning a company-record review?
Agree organization access, permitted records and model-provider terms before sharing private information. An enquiry alone does not connect your systems.
Public evidence
Public Briefs use external reporting. They distinguish reported facts from possible consequences and unknowns; they do not establish a customer's supplier or shipment exposure. Verify the evidence before making a commercial decision.
Business context
The hosted demo processes the description and monitoring concerns you supply. Those details and questions can inform requests to external search and model providers. Use public business context in the anonymous demo.
Company records
Signed-in company connections scope records to an organization and its authorized users. Relevant record excerpts and payloads may be sent to the configured model endpoint for an answer. Retrieved private records are not added to public web extraction requests.
Model processing
Training, retention, residency and subprocessors depend on the selected provider and contract. An API connection alone does not establish a zero-training or zero-retention guarantee. Confirm these terms before connecting sensitive information.
Connection paths
Typed records can be imported through files or authenticated API ingestion. REST polling supports bounded pagination and checkpoints. Provider-specific authentication, mappings and database change capture require separate setup.
Access and deletion
Organization access checks and database row policies restrict retrieval. Record deletion uses tombstones to prevent replay. Tombstoning is not a promise of immediate erasure from backups, logs or a provider's retained data.
Before a supported pilot
Agree the record scope, access owner, model provider, retention requirements and permitted external requests. Veyro provides selected ingestion and processing logs; comprehensive or immutable communication auditing is not established for every path. A customer-controlled endpoint or private deployment needs a separate technical review and is not the default demo.