Terms of Service

Last updated: 2026-08-15. Draft — pending legal review.

These terms describe EEC as it exists today. The app is in early development. It now has user accounts, but there is still no billing, no paid plan and no trial.

Getting an account

There is no sign-up form. Companies are set up by us, by hand, after a conversation. Everyone else gets an account by being invited by someone at their company.

Your account belongs to the company that invited you. That company decides who has access. Removing someone's access is currently done by asking us — there is no button for it yet.

Using EEC today

EEC is provided as-is and free of charge while it is in this stage. There is nothing to pay and nothing to cancel.

You are responsible for keeping your password to yourself and for what happens under your account. Tell us if you think someone else has access to it.

What you can currently do with it: create events for your company, record the functions inside them, build the guest list — people, households, their stays, and any fields you add yourself — and archive an event when it's finished. With Guest Communications switched on you can also record, for each guest, how they should be addressed, a second phone number, the details of somebody who answers for them, their date of birth, their gender and how far along their travel documents are. You can also mark which functions each guest is invited to, record the date each round of contact reached them, and keep a log of every call and message about them — including free text describing what was said, any follow-up you promised, and anything you mark as a query somebody still owes an answer on. You can also record the hotels you work with and the rooms in each, which is kept at company level and reused across events rather than re-entered. Nothing in the app deletes an event — archiving moves it out of your active list and keeps everything in it. Removing a person does delete them, and their stays with them. If you need something else genuinely removed, ask us.

The people you put into EEC

Most of what you store here is about other people — guests, crew, artists and drivers who have no account with us and no relationship with us. You are the one who decides what to collect about them and why.

You are responsible for having the right to enter those details and for telling those people what you do with them. Please do not put anything in here that you would not be able to justify holding — the free-text and custom fields will accept anything you type, and we do not inspect them.

That applies most of all to the conversation log. "What was said" is an open box with no shape to it, and it will hold whatever the person at the desk thought worth writing down. It is the easiest place in this app to record something about a guest's health, family or finances without having decided to. Treat it as notes you would be content for that guest to read.

The same goes for who is holding a query: that is a person's name, often somebody outside your company, recorded with a deadline against them.

Every change you make is recorded, field by field, with your name against it, and every action is recorded on your company's audit trail. Neither record can be edited or removed from inside the app, by you or by anyone else at your company. This is deliberate, and everyone at your company can see the audit trail.

Acceptable use

Don't use EEC in a way that attempts to disrupt, damage, or gain unauthorized access to the systems that serve it, or to reach data belonging to a company you are not part of.

No warranty

EEC is under active development and provided without any warranty of any kind, express or implied. Features may change or be removed without notice while the app is in this early stage. Do not rely on it as the only copy of anything that matters to you yet.

TODO — sections this document still needs before it can be published

Deliberately left unwritten rather than guessed at:

• Who owns the data a customer puts in, and what happens to it when they stop using EEC — including how they get it out and how long we keep it.
• Limitation of liability and indemnity, stated in a form that is actually enforceable in India.
• Termination and suspension — on what grounds, with what notice, and what happens to the data.
• The customer's own obligations regarding the guests whose personal details they upload: consent, accuracy, and lawful basis. EEC is a tool they operate; the terms need to say so precisely. The plain-English paragraph above is a placeholder for this, not a substitute — as of 2026-08-15 the app really does hold guests' names, numbers, households and movements, so this is the section that has become urgent. As of 2026-08-19 it also holds dates of birth, gender, document status, and the contact details of a third person who answers for the guest — which widens the obligation rather than changing its shape, and makes the child-data question in the privacy policy a live one. As of 2026-08-20 it holds free-text notes of every conversation about a guest, which is a change of shape rather than of width: every other field has a defined purpose that bounds what it can hold, and this one does not. The customer's obligation here is not the same obligation in a wider form — it is a new one, about what they choose to write down.
• A data-processing agreement, separate from these terms. If EEC is a processor acting for the customer company — which is the likely reading — most of what matters about guests' data belongs there rather than here, and it does not exist.
• Billing, trial and plan terms — none exist yet. Phase I of the build order.
• Governing law, jurisdiction and dispute resolution.
• Service levels, or an explicit statement that there are none.
• How these terms change, and what notice customers get.

Changes to these terms

This document is kept in sync with what the app actually does, in the same change that introduces a new capability. It has not been reviewed by a lawyer, and must be before this app is publicly reachable or before any money changes hands.