Skip to content
KLOPT
ID Sign in Book a demo
Product Tax engine Two books AI Demo Pricing Security About Contact
Book a demo Sign in to the app
Security & data

Safe because the system refuses, not because we promise

Security pages usually list nice words. This one shows the mechanics: what is guarded, where, and what happens when our own code is wrong.

Record integrity

Books that cannot be quietly changed

The question “were these books changed after posting?” cannot be answered with a promise. It must be provable, and someone other than us must be able to run the proof.

Jurnal hanya bisa ditambah

A posted entry has no update or delete. Not merely “hidden from the screen” — the operation does not exist anywhere in the system.

Each entry is locked to the one before it

Each entry stores a fingerprint of the previous entry. Change one figure and the lock breaks at that row and every row after it. The break shows immediately on the next check.

Before-and-after change log

Every data change records the old value, the new value, who made it, and when. Attempts refused for lack of permission are logged too.

Separation between companies

Guarded by the database, not by app code

If separation is guarded only by adding a filter to every read, safety depends on no read ever missing it. Sooner or later one will.

In KLOPT the database itself refuses to return another company’s data, even when a read is written wrongly. Wrong code ends as an empty result, not as a leak.

Roles × permissions
Locked rules

Eight rules the application itself cannot break

A rule guarded only by code will eventually be broken. The eight below are locked into the database. Break one and the transaction fails — the data does not go wrong.

Every entry must balance

Total debits always equal total credits, in every entry and every report.

Posted entries never change

There is no update or delete. Corrections go through a reversing entry linked to the original.

Closed months reject new entries

Including entries backdated into a locked month.

The chain between entries is unbroken

Checkable any time, with the result and its timestamp recorded.

No computer floating point on money

Fixed-precision decimals from database to screen.

Rounding is always spelled out

The method comes from the tax rule itself, not from a programming-language default.

Sent twice, still one entry

A request sent twice because of a network hiccup still creates one entry.

Cross-references always hold

An invoice cannot reference a customer that does not exist. The database refuses.

Data location & privacy law

Your data stays in Indonesia

For a system holding Indonesian companies’ accounting and tax records, where the servers sit is not a matter of technical taste. It is a legal obligation, and we have treated it that way from the start.

Placement

  • The primary database and its backups reside in Indonesia.
  • The disaster-recovery site is also in Indonesia, in a separate zone.
  • Documents you upload are stored in the same region.

Personal data

  • Payroll data can be opened only by people with payroll permission.
  • Personal data is replaced with random codes before any document reaches an AI provider.
  • Erasure requests are honoured as far as tax-record retention rules allow.

Our team’s access

  • Access to live data needs approval and expires.
  • Every access is logged, and the log is available to you on request.
  • There is no way for us to change your journals without leaving a trace.

Data ownership

  • Your books are your legal record, not our asset.
  • A complete export in formats other software can open, any time, at no charge.
  • We do not use customer data to train any model.
Operations

Uptime, backups, and what we do when things break

Backups

Regular backups with point-in-time recovery, restore-tested on a schedule. A backup never test-restored is not a backup, it is a hope.

Availability

Availability and response targets are written into the service agreement for Group, and published plainly for every plan.

Incidents

We announce outages while they are happening, not after. Root-cause explanations go to affected customers, including the parts that embarrass us.

Where responsibility sits

Better said now than found out later

KLOPT is a bookkeeping and tax tool. It does not replace your tax adviser, does not take over your filing obligations, and does not guarantee your tax positions will be accepted on audit. Nobody can guarantee that.

What it does is make every figure defensible: where it came from, which rule applied, who approved it, and what changed since. When the question comes, you answer with a file, not from memory.

Full terms of service, the data processing agreement, and the privacy policy are available on request before contract signature. Send your request to halo@klopt.id.

Next step

Send us your security checklist

If your IT team or auditors have a vendor questionnaire, send it. We fill it in with specifics, including naming what we do not yet meet. Far more useful than a checklist that is green all the way down.

Book a demo About us

No credit card. No commitment. We prepare the sample data.