Jilu

Security is the foundation, not a feature.

Jilu holds the record of how a company works: its decisions, its reasoning, and the evidence behind both. Because so much sits in one record, every safeguard on this page matters more. The programme below follows the order a security team runs its own review: protect the data, control access, detect and respond, then prove it. Jilu states its commitments plainly.

Every control on this page carries a state label, Designed or Planned. Designed means the control is specified in the locked architecture and stated as a commitment. Planned means Jilu has committed to it and has not built it yet.

Limit what any breach can reach.

The first question is not how to stop every attack. It is how little an attacker gains when one succeeds. Keeping workspaces apart, encrypting the data, and letting the customer choose what Jilu may collect set that limit before any other safeguard runs.

01

Workspaces kept apart

Designed

Workspaces share one database (Postgres), but each workspace's data is sealed off from the others. Every search runs under that workspace's own rules, so no search can cross into another workspace's record.

02

Encryption in transit and at rest

Designed

Encryption protects data as it moves between the customer's tools and Jilu, and as it sits in Jilu's stores. Keys stay separate from the data they protect.

03

Separate keys for each workspace, on the roadmap

Planned

The roadmap adds a separate encryption key for each workspace, so one workspace's key never unlocks another workspace's record. This page lists the item as a plan because Jilu has not shipped it yet.

04

You choose what Jilu collects

Designed

The customer decides which channels, spaces and kinds of data Jilu collects, and can leave any of them out entirely. Direct messages and HR spaces stay out unless the customer deliberately includes them. Meetings follow the same rules: one-to-ones and HR meetings stay out by default, and a meeting joins the record only when the customer has included meetings.

Access runs through your identity provider.

The customer already runs an identity provider and a joiner and leaver process. Jilu plugs into both instead of building a second, weaker copy beside them.

01

Single sign-on (SSO) and MFA through your identity provider

Designed

People sign in with SSO through the customer's identity provider. MFA is enforced through that provider, under the customer's own policy, not through a separate Jilu password with its own rules. Available on Business and Enterprise.

02

SCIM: accounts created and removed automatically

Designed

SCIM, the standard system for managing accounts automatically, creates accounts when people join and ends them when the account at the identity provider ends. A leaver's access to Jilu ends with the account that gave it, in the same process the customer already trusts for every other tool. Available on Enterprise.

03

Separate admin roles, no more access than needed

Designed

Admin roles stay separate from everyday use, and each role holds only the access its work needs. Changing what Jilu collects is an admin action: Jilu logs every such change and shows the log to the customer.

04

No standing staff access

Designed

No one at Jilu can read customer data by default. When support needs access to fix a problem, Jilu grants it only then, for a named reason, for a limited time, and only after the customer's workspace admin approves it. Each grant is written to a log the customer can see.

Every read leaves a record.

A control the customer cannot inspect is a claim, not a control. Jilu writes its own activity down, exports the record, and states its incident commitment in the contract.

01

An audit log that cannot be rewritten

Designed

Every read writes to the audit log, whether a person or the agent did the reading. The log only ever grows; no entry can be edited or removed. Each entry carries a fingerprint (a hash) of the entry before it, and the latest fingerprint is stored outside the database every hour and checked every day, so a changed entry breaks the chain and is caught. The log records who or what read the data, what it read, and when. Audit events are kept for the life of the workspace and for one year after the workspace closes, then deleted. How long they are kept can be set for each workspace.

02

Logs you can take with you

Designed

Logs are exportable, so a customer's security team can pull Jilu events into its own monitoring and review them beside the rest of its systems, on its own retention schedule. The customer-visible audit log is included on Business and Enterprise.

03

Incident response, in the contract

Designed

The data processing agreement will carry the notification commitment. Jilu will notify a customer within 48 hours of confirming an incident that touches that customer's data. The notice states what was affected, what Jilu has done, and the name of the person to contact. During an investigation, a workspace admin can pause collection, and collection stays paused until the customer restarts it.

04

Outside security testing, as a promise

Planned

Jilu commits to an independent security test every year once the service is running for real, with findings tracked through to a fix. Summaries are available to customers under NDA when they exist. Until the first test runs, this page calls it a commitment, because that is what it is.

Ask for the evidence, not the adjectives.

A security review runs on documents. The list below states what a team can request today, what sits behind an NDA, and where the certification roadmap honestly stands.

On requestPlanned

The review pack is in preparation. On request today, a reviewer can receive the security programme summary and the certification roadmap. The data processing agreement and the sub-processor list are not final documents yet, and Jilu will not present them as ready.

Under NDAPlanned

Penetration test summaries, when they exist. Jilu shares summaries under appropriate confidentiality terms and states plainly when no test has run yet.

Other companies that handle dataPlanned

A public list, published before any provider touches customer data, with regions and a change-notice window. Model providers will sit on that list. Keeping nothing and training nothing are requirements Jilu will place in each provider agreement.

ExitDesigned

Stop, export, delete. A customer can stop Jilu collecting, export the full record in open formats, and have its live data and everything built from it deleted; the deletion is logged, and backups are emptied within 35 days. A legal hold by the customer pauses deletion for the held material only, and the hold belongs to the customer.

Status today

No certification claimed. Jilu holds no SOC 2 or ISO 27001 certification today, and this page shows no badge for one.

Year one plan

SOC 2 Type I. Type I checks that controls are designed and in place at a point in time.

After year one

SOC 2 Type II, then ISO 27001. Type II checks that controls keep working over a period of operation. ISO 27001 is planned as international sales begin.

Dates on the roadmap are plans. Jilu will list a certification on this page only after an auditor has issued it.

For what this website itself collects and the rights you have over it, see the privacy page.

Bring your security review.

Enterprise teams: request access and state that the request is for a security review. Jilu will share the review pack and route technical questions to people who can answer them in writing.

Request access