About us

AISP builds tools for the document work that sits behind trade. Our test is narrow on purpose: does this let somebody who handles dozens of documents a day read one fewer, and get one fewer wrong? A feature that fails that test does not get built.

How your documents are handled

· Uploaded originals are never written to disk — they are processed in memory, and a result is deleted automatically after 24 hours. You can delete one the moment you are done with it.
· Documents are never used to train models.
· The application and its database run on a server in Hong Kong.
· When a scanned page needs OCR, the image is sent to Baidu's text-recognition service. A PDF that already carries a text layer does not go there.
· Payments and mail are handled by third-party processors; the full list is in the privacy policy.

Every line above is in the code rather than in a policy: a result is a row with an expiry, and an original exists only in memory for the length of one request. There are tests that hold both to that.

How we work

· If it can be configuration, it is not hardcoded. Rules, fields and prices live in configuration files, so one change is one edit.
· We do not overstate. A function we do not have says "not supported"; an accuracy figure we have not measured is not printed anywhere.
· Uploaded originals are never written to disk, and results delete themselves. That is in the footer of every page, and in the code.

Contact

Email is enough — there is no call to book. Everything goes through the mailbox, and we reply within 48 hours.

support@aisp.work

Custom integrations, volume purchases and API access all go to that address. What is live is listed on the home page, and the list grows as each one ships.

This site

Domain: aisp.work

It comes in two languages: this one, and a Chinese portal at /zh. They share the product and the prices; the tabs are the same three on both.