Security and privacy

Your data kept separate, every approval recorded.

Kinsu ERP separates each account’s data in the database itself, gives each person and each agent only what they were granted, and records who approved and when.

Director reviews the team’s access on a laptop at an office desk

Data isolation

Each account kept separate by the database itself.

Isolation is done by the database itself, by account, by company, and by country.

By account

One account’s data is kept separate from that of all the others.

By company

Within the account, each company’s records are kept separate, and each person works in the companies they have access to.

By country

Data is also kept separate by country.

Access

People and agents with only what they were granted.

For people, access is defined by area. For AI agents, action by action.

For your team

Access groups by area

Anyone not granted the area doesn’t see the menu or open the screen

For AI agents

Each agent’s permissions, action by action

People-only actions out of the agents’ reach

Agents can be turned off in the account by the administrator

Approvals and records

Some actions belong to people only, and each approval is recorded.

People-only actions

Approving a quote, paying, and issuing an invoice are actions marked as people-only. If the request comes from an agent, the system declines it.

A note on sensitive actions

Marking a sale as lost, reopening a record, or requesting a change to a quote requires a note from whoever decided.

Who approved and when

Each approval keeps who approved and when on the record itself.

Each agent’s limits

In each module, the “What stays with people” section shows what the agent prepares and what stays with your team.

Consent

Recording and personal documents, only with consent.

In video meetings, recording only happens with each participant’s consent. In document reading, a personal document is only read with consent.

Meeting recording

Each participant’s consent, logged person by person

Anyone who withdraws consent is logged

Local rules are respected: in some places, everyone has to agree

Personal documents

Personal documents, such as an employee’s hiring documents, are only read with consent

The document is stored in the record

The record only takes effect after a person confirms it

Kinsu team access

Emergency access with a set end time.

Emergency access by the Kinsu team is time-limited: 60 minutes by default and 8 hours at most. Each access is recorded.

Example · emergency accessKinsu team
Default duration60 minutes
Maximum duration8 hours
RecordAccess recorded
Illustrative example.

Compliance checks

Hourly checks, with a record of each run.

Compliance checks run every hour, and each run is recorded with the date and time.

Example · checksToday
14:00Run recorded
13:00Run recorded
12:00Run recorded
Illustrative example.

Website cookies

On your company’s website, analytics only after acceptance.

The website your company builds in Kinsu ERP asks for cookie consent (LGPD/GDPR) and only loads analytics after acceptance.

Example · company websiteFirst visit
CookiesConsent requested
AnalyticsOnly after acceptance
Illustrative example.

Questions about security and privacy.

Data is kept separate by the database itself, by account, company, and country. Each person sees only the areas they were given, each agent uses only the actions enabled for it, and actions reserved for people are refused when the request comes from an agent. Emergency access by the Kinsu team is time-limited and logged, and compliance checks run every hour. Recording meetings and reading personal documents only happen with consent.
Through emergency access, with a time limit: 60 minutes by default and 8 hours at most. Each access is recorded.
No. Each agent has permissions action by action, people-only actions are out of its reach, and the administrator can turn off the agents in the account.
Yes. Each approval keeps who approved and when on the record itself, and sensitive actions require a note from whoever decided.
No. Recording only happens with each participant’s consent, logged person by person. Anyone who withdraws consent is logged, and local rules are respected: in some places, everyone has to agree.
Only with consent. This applies, for example, to an employee’s hiring documents. The record only becomes valid after a person on your team confirms it.
Every hour, with a dated record of each run.
The website you build in Kinsu ERP asks for cookie consent (LGPD/GDPR), and analytics only loads after acceptance.

See access and records at work.

In the demo, we show how the administrator grants areas and actions to each person and each agent, an action declined when the request comes from an agent, and the record of who approved.

Join the waitlist