What protects the data you put in.

Separation between customers

Every one of our systems is multi-tenant: your workspace lives alongside others, and the separation is enforced at the database layer. Records carry the account and property they belong to, and queries are scoped automatically rather than relying on each screen to remember a filter. One account can hold several hotels, schools or companies, each with its own users, settings, currency and calendar, and staff see only the properties they are granted.

Who can do what

Access is checked in three places, not one:

• The database — queries are scoped to your tenant automatically.
• The route — a request for a module a user is not granted is refused before any code for that module runs.
• The interface — the user never sees a screen they cannot use.

Permissions are per role and per module, and each product ships roles that match how that business actually works — an owner, a front-desk agent and a housekeeper do not need the same system.

Audit trail

Changes to records are written to an activity log that records what changed, who changed it and when, stamped with the tenant and property so an audit can be filtered per site. This is on by default, not an upgrade.

In transit and in the browser

Every system is served over HTTPS only. Each application sends hardening headers on every response — a content security policy that blocks scripts and frames from foreign origins, MIME-sniffing protection, clickjacking protection, a privacy-preserving referrer policy, and HSTS so a browser will not silently fall back to an unencrypted connection. Session cookies are encrypted and marked secure. Passwords are never stored in a readable form.

Backups

Each system's database is dumped automatically every night on a schedule, old copies are pruned so storage cannot silently fill, and a health check runs afterwards and reports if a backup did not appear. Restores are performed by us on request.

Errors and personal data

When something breaks we want to know before you have to tell us, so the applications report errors to a monitoring service. Those reports pass through a scrubber first, which strips personal data — guest, student and customer details — out of the payload. Diagnostics should tell us what broke, not who it happened to.

Your data belongs to you

We do not sell, mine or share the data in your workspace, and we do not use it to train anything. It is yours: ask and we will export it. If you ever leave, you leave with your data.

Found a problem?

If you believe you have found a security issue in any ineed.now system, email info@ineed.now with the details and how to reproduce it. We will confirm we received it, and we will not pursue anyone who reports a genuine issue in good faith and gives us a reasonable chance to fix it before making it public.

Questions we get asked

Where is the data hosted, can we sign a specific agreement, do you support single sign-on, can we get a copy of the database on a schedule? Ask us — info@ineed.now. We answer these in writing.