How TeranoveCore protects data, who our providers are, and what we do and don't yet claim. Written straight — no badges we haven't earned. Last updated .
Traffic to the service is encrypted in transit (HTTPS/TLS, terminated at the edge). Sensitive personal data — such as an employee's government ID or bank details, where a company records it — is encrypted at rest and only decrypted for a person with a specific right to see it. Access to everything else is governed by the platform's own permission model, not left open by default.
Access is layered. A person acts through a profile; a company grants an employee an authority tier (owner, admin, manager, employee) and a role that unlocks specific function families. Purchasing, approving requests, and seeing prices are limited to authority-holders. Company profiles themselves are approval-gated, so an account can't stand up a company it has no right to represent. Every grant is explicit and revocable.
Profiles and operational metadata are held in TeranoveCore Cloud, running on infrastructure we operate. Document content is the customer's choice — TeranoveCore storage, a third-party cloud you already use (Google Drive, OneDrive, S3), or a device you control, with Cloud as the router. We rely on a small set of processors: Cloudflare for DNS and edge delivery, and Microsoft 365 for business email. Each operates under its own terms.
Companies get an audit trail of activity in their workspace — work orders, assignments, document actions, automation changes, and more — with retention a company can configure. We also keep standard request and security logs for operating and protecting the service.
Individuals can view and correct their profile, manage visibility and notification preferences, export their data, and request a deletion review — from inside the Portal or by contacting us. Where local law gives additional rights (access, correction, portability, objection, restriction), those are handled the same way. A company that needs a data-processing agreement for its own compliance can request one.
If we become aware of a security incident affecting your data, we will investigate, act to contain it, and notify affected customers and, where required, regulators, without undue delay. To report a vulnerability or suspected abuse, email [email protected] — please don't publicly disclose an issue before we've had a chance to address it.
Today, the database is backed up by hand before every change we deploy — not yet on an automatic schedule. An automated nightly backup exists and is being finished; until it's switched on, a manual backup immediately before each deployment is the real, current safety net. TeranoveCore currently runs from a single region and does not offer a formal recovery-time or uptime guarantee at this stage; both will be revisited as the platform matures.
TeranoveCore is not currently certified against SOC 2, ISO 27001, or similar frameworks. The practices on this page are what we operate to today. If your organisation needs a formal attestation before adopting the platform, get in touch and we'll tell you where we are.
Security and vulnerability reports: [email protected]. Data-protection requests: [email protected]. Anything else: the contact page.
This page describes TeranoveCore's current security and compliance posture in plain language. It is not a warranty or a certification, and it may be updated as the platform and applicable law change — the "last updated" date above reflects the latest revision.
