What TeranoveCore is, and what it is not. Written in plain language. Last updated .
Draft. This page is a draft pending legal review. The name of the legal entity that operates TeranoveCore and the governing-law details are still to be finalised, and the wording here may change.
On this page
Nothing on this site or in the product is legal, tax, accounting, financial, medical, or other professional advice. Information, templates, reminders, and AI-assistant output are general in nature and may not fit your situation. Talk to a qualified professional who is licensed where you operate before you rely on any of it.
TeranoveCore provides tools for recording information, tracking deadlines, and sending reminders. Using the platform does not make a company compliant with any law, standard, or regulation, and TeranoveCore does not certify or audit your compliance.
Flags, warnings, and "blocked" or "due soon" states are aids to your own process, not determinations that something is or is not permitted. Each company is responsible for its own compliance, and a company may configure what blocks an action and what only warns. See also Compliance.
TeranoveCore is not an electronic health record (EHR) and is not certified as one. It is not described as "HIPAA compliant", and TeranoveCore does not sign business associate agreements unless and until it says so in writing.
Do not store regulated health information in the platform unless you have turned on the sensitive-data controls and you hold the agreements you need under the law that applies to you. We make no claim that records kept here are protected as peer-review or other privileged material, and we make no claim of protection for substance-use treatment records under 42 CFR Part 2. Where a company confirms in its settings that it holds the agreements it needs, that is the company's own statement; TeranoveCore does not review, sign, or vouch for it. If you would rather not store health information here at all, keep it in your own clinical system and link to it.
TeranoveCore makes no claim of compliance with FERPA, Title IX, IDEA, 42 CFR Part 2, or public-records laws. It is not a student-information system, a case-management system, or a government system of record. If you work in these areas, you remain responsible for keeping official records in the systems your organisation or regulator requires.
TeranoveCore is not a core banking, loan-origination, policy-administration, or claims system. It does not perform BSA/AML, OFAC screening, KYC, rate-filing, claims adjudication, or regulatory-filing functions. In these fields it offers records and reminders only, and it does not replace the systems and controls your regulators expect.
TeranoveCore is not a law firm and does not give legal advice. It does not provide trust or IOLTA accounting. Document templates are starting points, are not legal advice, and are not a substitute for a lawyer.
Electronic signatures may not be valid for some types of document, such as certain wills, family-law, or real-estate documents; this depends on your jurisdiction. Check before you rely on one.
The accounting and general-ledger features are bookkeeping tools. They are not a certified accounting or audit product, and they do not file taxes or calculate or remit payroll tax. An hours export is not payroll processing. Sales-tax settings are your company's own, and you are responsible for choosing them and for what you collect and remit. Reports, trial balances, and account mappings are generated from what was entered or posted and can only be as complete and correct as that; a bank reconciliation shows whether your records agree with a statement, not that either is right. Closing a period stops postings in the platform, it does not make the books audited or final. Have a qualified accountant review anything you rely on for tax, lending, or reporting.
Starter checklists are examples to adapt. They are not a substitute for the regulation that applies to you, the manufacturer's instructions, a competent person, or professional judgment. No checklist guarantees safety, and completing one does not mean a task, site, or piece of equipment is safe.
Rule tables and other reference data in the platform may be out of date, incomplete, or different in your jurisdiction. Verify anything that matters with the issuing authority before you act on it.
Connections made through the Hub link TeranoveCore to services we do not control. Their availability, how they handle data, and any fees they charge are theirs, not ours. Connecting a partner is your decision, and you should read that partner's own terms and privacy notice first.
Encryption and two-factor sign-in options reduce risk but cannot remove it. You choose your settings and are responsible for them, for who has access to your company and what that access allows, and for the security of the devices you use. Sealing (encryption at rest) protects stored content; it does not protect against a person who has legitimate access, a stolen or unlocked device, a shared code, or a company that has turned the protection off. A two-factor check only helps if people have turned two-factor on, and a company can choose to ask for it only from those who have. If the server's encryption key is not configured, protected content cannot be sealed, and the platform will tell you rather than quietly storing it unsealed for the newer record types. See Privacy for how we handle data.
TeranoveCore can record consent and do-not-contact status, but it does not send regulated messages on your behalf. You are responsible for meeting the requirements that apply to your outreach, which may include the TCPA, CAN-SPAM, and state laws. The email opt-out list is a record of addresses that asked not to be emailed and a way for your own email tool to ask before it sends. TeranoveCore sends no marketing email, cannot see messages sent through other tools, and does not check that a message is truthful, labelled as an advertisement, or carries the sender details the law may require. An opt-out reported by a connected mail platform is only as complete as that platform's report. Call-recording and privacy-request records are logs of what you decided and when, not advice on which laws apply to you.
Starter documents and checklists are examples. The starter documents offered for fields such as healthcare, banking, insurance, education, legal, and government are working forms with reminders. They are not official forms, they are not filed with anyone for you, and they are not a substitute for the form, process, or advice your regulator, accreditor, funder, or counsel requires.
Dates and clocks are reminders, and they can be wrong for your situation. A due date the platform works out (for example "60 days from discovery" or "20 business days from receipt") uses the rule written into that starter, which may be a commonly stated period rather than the one that applies to you. It may not account for holidays, court or agency calendars, tolling, extensions, state or local variations, or the way your agreement or policy counts time. Confirm every date with the rule that actually governs you, and keep your own calendar for anything that matters.
Screening, credentialing, and verification records are logs, not checks. TeranoveCore does not screen anyone against any exclusion list, query any database, verify any licence or credential at its source, or run a background check. A record that says something was screened or verified only records that you say you did it.
Outside systems. A record that links to an outside program (for example a clinical or case-management system connected by API) holds a reference, not the outside system's records. TeranoveCore does not verify what the outside system holds, and what that system does with data is governed by its own terms and your agreements with it.
You decide what must be kept and for how long. A legal hold or a retention period in TeranoveCore is a setting you choose and a reminder to the people in your company. It does not decide whether a duty to preserve exists, how long a record must be kept, or whether a deletion is lawful. By default the platform warns and records the action in a log rather than stopping it; you can change that, and if you set it to "do nothing" it will not warn at all. Deleting a company or exercising a data-deletion request can remove records that a hold or retention rule would otherwise cover; check first.
Consent records are records. A consent entry records what a person agreed to, as you entered it. It is not a determination that the consent is valid, informed, sufficient, or covers a particular use or disclosure, and it does not replace the signed form or the evidence you keep elsewhere.
The access log shows what the platform saw. It lists who opened, changed, exported, or deleted protected content through the platform, and what the protections did. It is not a complete audit of everything that happens to your data, and it is not a legally sufficient accounting of disclosures. Turning logging off, or turning a protection down, is allowed and is itself recorded.
Service-level promises are your own targets. A response or completion time you set in TeranoveCore is a target you chose, counted in calendar minutes (not business hours). It is not a contract term, a warranty, or a legal finding, and the platform does not decide whether you owe a customer anything. "Missed" only means your own target passed; it is a prompt to look into the work order. When you stop a work order's clock because it is waiting on the customer, the reason is a record you entered and is not verified.
"On the way" messages are best effort. A visit estimate is the technician's own guess, and a message may be delayed, filtered, or not read. Messages go to the customer's inbox in the platform; email is sent only if you turn it on, never to an address that has opted out, and is not guaranteed to be delivered. TeranoveCore does not send text messages for visit notices. You remain responsible for what you promise your customers.
The overtime flag is a label, not a legal determination. Marking someone exempt or non-exempt records your decision. Whether a person is actually exempt depends on their duties, how they are paid, their pay level, and the rules where they work, which can be stricter than the federal ones. By default the flag changes no pay calculation; if you choose to count an exempt person's hours as regular time, that is your setting. Check with counsel or your labor department. This is not payroll or legal advice.
Procedure history shows what was written and who said they read it. The saved wordings, approvals, and "I have read it" entries are records of what people did in the platform. They do not show that a procedure is adequate, current, or lawful, or that anyone followed it. A second-person approval is only as meaningful as the review behind it.
Project trades record what people say, not what was built. When a project manager adds the companies it hired and lays out the steps, each company marking its own step done is that company's own statement, and the manager's confirmation is the manager's. Neither is an inspection, an acceptance of the work, a code-compliance check, a lien or payment release, or a sign-off, and TeranoveCore does not verify that any work was done or done correctly. Whether a step may be marked while an earlier one is unfinished is a setting the manager chooses; by default it only warns. A hired company sees only its own steps and the steps directly before and after them. Schedules and "ready to start" notices are reminders, not a promise that anyone will show up. A hired company can add steps to its own part and either side can leave notes on a step; a note is only what that person wrote, and a step reported automatically because a linked work order was completed is still only that company's own statement.
Inspections and lien waivers are tracked, not decided. An inspection record shows who inspects, when it was asked for and held, and the result as the person who entered it typed it. It is not a finding by TeranoveCore, a permit, or a determination that work meets any code, and a step that "needs an inspection" only warns, or refuses if you set it to. A waiver record shows whether you asked a company for a lien or payment waiver, whether it says it sent one, and whether you say you hold the signed document. TeranoveCore does not provide statutory waiver forms, does not say whether a waiver is valid, enforceable or required where you work (states differ, and some void waivers that do not use their own form), does not release or protect any lien right, and "received" does not mean the waiver is effective. Keep the signed documents yourself and ask a lawyer.
Retention periods are suggestions. The proposed retention periods are commonly cited minimums and nothing more. They do nothing until you adopt them, they never replace a choice you already made, and the right period for you depends on your jurisdiction, your industry, and any pending dispute.
Online selling. If and when online selling is offered, you remain responsible for your listings, your prices, the taxes that apply, and your obligations to your customers.
AI assistant. Nova and Apothos can be wrong. Review anything they produce, and check it, before you rely on it or act on it.
Availability. The service is provided "as is" and "as available", and some parts are still under development or marked "coming soon".
Liability. Limits on our liability are set out in the Terms (see sections 8 and 9). Nothing on this page limits a right you cannot give up by law.
These disclaimers are general statements, not a substitute for legal advice, and what applies to you depends on your jurisdiction and your industry. They sit alongside the Terms, Privacy, and Compliance pages. The governing law and the name of the legal entity that operates TeranoveCore will be stated once finalised. Questions: [email protected].
