NOGL / Trust center
Know the scope behind the signal
Understand which data a workflow uses, where it runs, how credentials are handled and where to ask security questions. This page describes the current public-market experience and the boundaries to agree before connecting private data.
Public-market scope
The public-market workspace uses selected public market and product signals. A public store scan does not connect a retailer's private store account or import customer records. Public scans read data that a source publishes openly; they do not log in, bypass access controls or collect personal visitor data. Source availability and category coverage can vary; review the evidence shown for your specific market.
- Published market signals are different from your own sales, inventory or CRM data.
- A public-data example is not evidence that a private-data integration is ready.
Public signals and connected private data
Some questions can be explored with public sources. Others need authorised private customer, inventory, sales or product data. Before a connected workflow, agree what is needed, who may access it, how it will be used and the applicable retention and deletion terms. Private data is only processed inside the scope agreed for your pilot, never inside the public demo.
- Do not upload private datasets into a public-source setup flow.
- Discuss processing terms and access requirements before sharing customer information.
Hosting and operations
This website, the NOGL application and the integrations service run on NOGL-operated, self-hosted infrastructure under our own operational control. Source code lives in private repositories with limited access. Operational secrets are held in a dedicated secret manager and injected at runtime; they are not embedded in the website or its repository. This site adds no third-party advertising or analytics scripts; the cookie policy documents the current storage and cookie inventory.
- Infrastructure, deployments and monitoring are operated by the NOGL team, not a managed cloud tenant shared with other customers.
- Ask for the current operational documentation if your security review needs more detail than this page provides.
Connection credentials and data handling
For an agreed pilot connection, source credentials are exchanged through a controlled setup with the account owner, stored encrypted by the integrations service and scoped to the agreed read or delivery rights. Current connector implementations keep credentials in encrypted in-memory storage and do not retain them in long-term customer archives; a service restart requires reconnecting. Delivery destinations and recipients are validated before use, and per-tenant access rules decide which channel may receive which report.
- Credentials for your systems are never requested through the website, a contact form or a documentation page.
- Report and alert content is delivered only to channels your tenant has explicitly approved.
Decision review and provenance
Review the source, freshness, coverage and whether an output is observed, modelled or a sandbox example. Keep a human responsible for consequential decisions. The documented stage journey includes review, override or revision and an audit record where that workflow is available.
- Agree permissions and review responsibilities before connecting operational systems.
- A recommendation or modelled outcome is not a guaranteed commercial result.
What this page does not claim
NOGL does not claim any security certification or independent audit status for the current platform. Hosting location, processing terms, retention periods and deletion handling are documented per agreement in the pilot contract, not promised on this page. Integration pages distinguish connectors that are implemented but still unverified from those that are planned; no page claims a live customer connection that has not been demonstrated. Where a claim on this site cannot be evidenced to your satisfaction, treat it as unsupported and ask us.
- No certification badges, audit reports or residency guarantees are published here because none are currently held.
- Retention, deletion and processing terms are agreed in writing per pilot before private data is shared.
Ask for the evidence relevant to your use case
Contact NOGL for a security review, a privacy question or to report a suspected issue. Describe the affected page, approximate time and impact; send no passwords, keys or personal records. We can discuss the specific controls and processing scope needed for your pilot.
- Request the current security documentation and processing terms relevant to your pilot.
- Review the privacy information and terms, and request current evidence before making a procurement decision.