Infrastructure Security
- Information backups evidenced
- Redundancy treatment decision tracked
- Logging enabled for production services
Teho Trust Centre
Security, privacy, compliance resources, subprocessors, FAQs, and review materials for Teho.
Controls
View allOrganizational Security
- Information security policies maintained
- Security roles and responsibilities assigned
- Access control policy enforced
Internal Security Procedures
- Incident response plan maintained
- Security events assessed
- Incident response procedures defined
Product Security
- Privileged access controlled
- Information access restricted
- Secure authentication enforced
Data and Privacy
- Privacy and PII responsibilities documented
- Baseline boundary documented before rollout
- Team-level reporting thresholds enforced
AI Security & Compliance
- Optional AI providers named before signature
- Deployment-specific AI classification
- Non-LLM deployment paths available
Subprocessors
Google Cloud • Infrastructure hostingCore product
UK regionsAPI, worker execution, database, object storage, secrets
Supabase • Application database and storagePortal infrastructure
Named per deploymentPortal data storage, application data access, and supporting backend services where configured
OpenAI • Optional AI classificationOptional deployment path
Named per deploymentOptional classification path when enabled by deployment settings
Resend • Customer notification deliveryCustomer communications
Named per deploymentTransactional messages and customer communications
FAQ
Where does Teho process data?
The Activity Analysis baseline is UK-hosted. Deployment-specific data flows, regions, transfer mechanisms, and optional evidence paths are named before contract signature.
Can we review Teho subprocessors before signature?
Yes. The final subprocessor list is narrowed to the actual deployment scope before signature and is not changed mid-pilot without notice.
Does Teho use AI providers by default?
Optional LLM or semantic classification paths are deployment-specific. Where used, the vendor, data category, region, and transfer mechanism are listed in the DPA or subprocessor schedule.
Is the Teho Baseline employee monitoring?
No. The Baseline is designed for team-level work-pattern evidence, not individual productivity scoring, rankings, leaderboards, pace metrics, or supervisor-facing activity feeds. The Baseline Privacy page explains the product-specific boundary.
Are screenshots required for a Baseline?
No. Screenshot, semantic, or LLM-enabled evidence paths are optional and deployment-specific. They are used only where needed for the agreed business question and only with explicit approval.
Where is the Baseline privacy material?
The Baseline Privacy page is the canonical product-specific privacy resource for Teho Baselines. Use the main Trust Centre for vendor assurance, security controls, subprocessors, and DPA posture.
Updates
Need the full review pack?
Email info@teho.ai with your company, reviewer audience, and review scope. Teho will route you to the right questionnaire, security pack, subprocessor schedule, or data-flow material.