Hybrid cloud platform for businesses

Your interactions with Tapas are to achieve outcomes without the need of a Non-Disclosure Agreement (NDA).

Once onboarding terms are accepted, Tapas will assist you in defining the plan of record to achieve your desired outcome.

If the outcome requires extra physical equipment, Tapas owns, installs, and maintains it — you are not responsible for its upkeep. Tapas carries the liability that comes with owning and operating that equipment (property damage, safety incidents arising from the equipment itself), separate from the software terms in clause 4. When the relationship ends, Tapas-owned equipment is retrieved or bought out as the Plan of Record sets out. If you provide the equipment yourself, you keep legal title. You agree, with a separate yes when you sign, that Tapas wipes, re-images and runs it under the same terms as Tapas-owned equipment. When the relationship ends, control is handed back to you.

The agent templates (the core logic every agent starts from) are licensed under the Apache License 2.0 and provided "AS IS," without warranty, as set out in sections 7 and 8 of that licence. Other Tapas components may be licensed differently. No agent runs until your named person has approved its configuration. Behaviour of an unmodified template is covered by the licence above; behaviour from a configuration traces to your approval. Nothing in these terms, or in any licence or disclosure, limits liability for gross negligence or wilful misconduct, or any legal obligation that cannot be disclaimed.

No action runs on its own. Tapas drafts every alert, and a named person at your business releases it; Tapas never decides for you. You confirm whether each report was accurate. If one was not, we work together to find the cause and correct it, at no charge. Tapas makes no warranty that any report is accurate.

Your data stays on your premises. Personal data in anything processed there, such as camera footage, is yours; Tapas knows only the outcome. What may be shared is agreed when you onboard: only the items you choose from Tapas's catalogue leave your premises, and only as values, never images, video, audio or free text. Some items are needed for the service to work; declining one of those means declining the service. Neither party discloses the other's information beyond what the outcome needs. No data of yours reaches Tapas, not even for testing. The checks that enforce this before anything leaves your premises are not built yet.

Neither these terms nor the Plan of Record that follows creates a payment obligation, now or later. Every engagement today runs without payment. Once you have confirmed outcomes, you decide whether the platform is worth paying for. The evaluation ends only when both of us agree; if no commercial agreement is reached, either of us may end the relationship.

Either party may end access at any time, effective within 24 hours. You need no reason; Tapas always states its reason. On termination, Tapas purges all data, credentials and cached state held by its agents within 24 hours of the moment access ends, and records proof of the purge. It leaves your own records with you, resolves any equipment on your premises per clause 3, and provides a closure report.

The logins you hold for your own accounts and portals, such as a tax portal, are never shared with Tapas. Tapas never asks for them, receives them, holds them or stores them. Where a filing or a payment is needed, your own named person makes it.

You choose now whether anonymised patterns from your premises may ever contribute to improving Tapas's templates: yes or no. Your choice is recorded as given. Nothing uses it today.

You choose now whether Tapas may open routine remote sessions on your premises under standing consent: yes or no. Routine sessions use a restricted account, and you are told of each one. Any other session needs the consent of your own named person, given for that session alone. Recordings stay on your premises; Tapas keeps only details about the session and a fingerprint of the recording.

The equipment needs outbound connections only, to the destinations listed in a disclosure Tapas gives you; nothing is opened inbound, and you are never asked to. The disclosure also says where Tapas's hosted components run. You confirm you have read it, and the version you accepted is recorded. The checks that enforce this on the box itself are not built yet.