HHISAB 360 Get HISAB

Privacy Policy

Last updated 29 September 2026. HISAB 360 is an Excel add-in that works on your own computer. This policy explains what we collect, where your data goes when you use AI, and who we share it with.

Information we collect

Account. Your name and email address, and how you sign in. If you sign in with Google, GitHub or Microsoft, we receive your name and email address from them. If you use a password, we store only a one-way hash of it.

Licence. Your plan, your licence activations and a device identifier used to activate your licence.

Billing. Payments are handled by Paddle. We receive the status of your subscription and payments, not your card details.

HISAB AI usage. If you use HISAB AI, for each AI request we record the date and time, the model and its provider, the number of tokens, the cost, and the credits charged. Your account page shows this usage to you.

Support. Messages you send through the website's support chat or contact form, and emails you send us.

Security. Sign-in and security records needed to protect the service.

Your workbooks and the AI

Your workbook files stay on your computer; HISAB never uploads them. When you ask the AI to do something, it reads what that request needs: sheet names, headers, the cells it works on (a few hundred at a time), and any file, screenshot or ERP data you ask it to use. That content is sent to an AI model in one of two ways, depending on the AI source you choose in Settings.

Own AI (your Claude or OpenAI account). Requests go directly from your computer to Anthropic or OpenAI, under your own account and their terms. HISAB is not in that path and does not see them.

HISAB AI (credits). Requests go from your computer through HISAB's server to the provider of the model you choose: Anthropic (Claude models), Z.ai (GLM models), Moonshot AI (Kimi models) or DeepSeek (DeepSeek models). Z.ai, Moonshot AI and DeepSeek are based in China.

We use your AI requests only to meter your credits, and we never store them. Our server passes each request to the AI provider, measures how many credits it uses, and returns the answer. It does not keep the content of your requests or of the answers, and does not use them for anything else, such as training AI models. The only thing kept is the usage record for each request (date, model, tokens, cost and credits). You can switch to Own AI at any time if you prefer your requests not to pass through our server.

ERP passwords and keys are encrypted on your computer and are never sent to the AI.

How we use information

We use information to provide licences, the HISAB AI service and its credits, support, billing, security monitoring, product improvements, and compliance records. We email you about your account, and occasionally about the product; every announcement has an unsubscribe link. We do not sell personal information.

Who we share it with

We use service providers that process data on our behalf, only as needed to run the service:

Some of these providers process data outside your country, including in the United States and, for the HISAB AI providers named above, in China.

Storage

Local configuration, credentials, skills, and audit logs are stored on the device where HISAB runs. Your account, licence, billing and HISAB AI usage records are stored on our servers while your account is open and afterwards for as long as billing, tax and security rules require. Payment records are also kept by Paddle.

Security

Connections to our servers are encrypted. Credentials on your computer are protected with platform security controls such as Windows DPAPI. See Security model for the product-level controls.

Cookies

The site uses two kinds of cookie and similar local storage.

Essential. These keep you signed in, carry your session between pages, and remember the cookie choice you make below so you are not asked again. The site cannot work without them, so they are set without consent, as the rules for strictly necessary storage allow.

Advertising (optional). If you accept them, Google Ads conversion tracking sets a _gcl_au cookie so we can tell whether an advertisement led to a sign-up. It is set by Google on our behalf and is not used to build an advertising profile of you across other websites. If you decline, it is never set: the tag runs in Google Consent Mode with advertising storage denied by default, and is only granted if you choose to accept.

We do not use analytics cookies, social media pixels or third-party tracking beyond the single advertising cookie described above.

You can change your choice at any time: open cookie settings. You can also clear cookies in your browser, though clearing them will also remove the record of your preference, so you will be asked again on your next visit.

Your rights

You can request access, correction, export, or deletion of your data by emailing support@hisab360.net. Some billing and security records may be retained where required by law.