Platform
Your business data is yours. Our software is ours.
Those are different things, and conflating them is how technology relationships go wrong. TGL operates a layered model that keeps the line explicit.
Three layers
What belongs to whom.
Customer-Private Data
Business-specific information — customers, orders, documents, records — stays isolated within that customer's environment, subject to their agreement, permissions, and access controls.
- Logical tenant isolation
- Role-scoped access
- Encryption in transit and at rest
- Audit trail of access and change
TGL Proprietary Intelligence
TGL owns its software, reusable components, architectural patterns, platform improvements, and intellectual property. Customers license their customized environment; they do not license the platform itself.
- Source code and architecture
- Capability Library
- Platform improvements
- Operational tooling
Governed Cross-Domain Intelligence
Where legally and contractually authorized, appropriately governed information may contribute to generalized patterns and improvements — without exposing one customer's private information to another.
- Explicit authorization required
- Data provenance tracked
- Generalized patterns, not records
- Reviewable governance policy
Isolation
One customer's data never becomes another customer's data.
Environments are logically isolated. What is shared between deployments is TGL's software and architectural patterns — the capability library — not the records inside any customer's environment.
Where TGL learns something generalizable from operating many businesses, what carries forward is the pattern: that a certain workflow shape recurs, that a category of process benefits from a particular structure. Not the underlying records, and not one customer's information surfacing in another's system.
Practices
How this is enforced.
Controls, not assurances. Each of these is something a customer can ask us to demonstrate.
Tenant isolation
Each customer environment is logically separated, and access is scoped by identity at every layer.
Access controls
Permissions are enforced by role at the data layer, not only in the interface.
Encryption
Traffic is encrypted in transit; sensitive fields are encrypted at rest.
Data provenance
Where information came from and what it may be used for is tracked, not assumed.
Auditability
Access and change are recorded, with retention appropriate to the record type.
Operational hardening
Default-deny network policy, monitored authentication, and reviewed infrastructure change.
What we will not claim
No system is perfectly secure, and any vendor telling you otherwise is selling something. TGL commits to specific controls, to disclosing incidents that affect your data, and to answering questions about how your environment is actually configured — not to guarantees nobody can honor.
Ownership
What a customer receives.
The customer holds
- Their business data
- A license to operate their customized environment
- The ability to export their data
- Control over who on their team can reach what
TruGen Labs holds
- Platform source code and architecture
- The Capability Library and reusable components
- Generalized improvements and patterns
- Operational tooling and infrastructure
Specific terms are set by the agreement between TGL and each customer. This page describes the model; the agreement governs.
Questions about how your data would be handled?
Ask them before you sign anything. We would rather answer specifics than offer reassurance.