Security at AxisIQ
Per-organisation databases encrypted at rest and in transit, field-level permissions, audit trail, 2FA, passkeys and how to report a vulnerability.
AxisIQ holds the records a business runs on — orders, customers, invoices, money — so security is part of the product rather than a feature of one plan. This page describes how the platform actually works today.
Your data is isolated
- One database per organisation. Every AxisIQ organisation gets its own database. Your records are never rows in a table shared with another customer.
- Encrypted at rest. Databases are encrypted on disk with AES-256-GCM.
- Encrypted in transit. All traffic to axisiq.co is served over HTTPS, and the connection between our application and the database is TLS-encrypted as well.
- Backups. Databases are backed up every night.
- Hosted in India. Our application and database servers are located in India. Web traffic passes through a content delivery network for delivery and attack protection.
Access is yours to decide
- Roles and permissions. Owners decide, per app, who can view, edit or manage each part of the business. Anyone without a permission is simply refused — the default is no access.
- Field-level permissions. Individual fields (a cost price, a salary, a phone number) can be hidden from roles that should not see them; hidden values are removed from screens, exports, reports and the AI assistant alike.
- Audit trail. Every change to a record is logged with who made it, when, and what the value was before.
- The AI assistant follows the same rules. Ask Axis acts under the permissions of the person asking — it cannot read or change anything that person could not. Actions that move money, send messages, invite people or delete data wait for an explicit confirmation.
Accounts are protected
- Passwords are stored only as bcrypt hashes; we never see or store your password itself.
- Two-factor authentication with an authenticator app, plus one-time recovery codes.
- Passkeys for passwordless sign-in with your device's biometrics or security key.
- Verified phone numbers. A phone number is saved to an account only after a one-time code sent to it is confirmed.
- Security notices are emailed when a password changes, two-factor authentication is switched on or off, or a passkey is added.
- Password resets use single-use links that expire after an hour, and a reset signs out your other sessions.
- API keys belong to service accounts with their own roles, are shown once at creation, and are stored only as hashes.
Connections and custom code
- Stored credentials are sealed. Keys and tokens you give AxisIQ for other services — payment gateways, stores, ad platforms, messaging providers, external databases — are encrypted with AES-256-GCM before storage and are never sent back to the browser.
- Your code runs in a sandbox. Custom JavaScript functions run in isolated V8 sandboxes with a time limit, a memory limit and no access to the server, the network or other organisations. They reach your data only through the same permission checks as a person.
- Outbound requests are fenced. Automations and integrations that call external URLs cannot reach our internal network or cloud metadata services.
Payments
Subscription payments are processed by a third-party payment processor. Card, UPI and bank details are entered on its checkout and never pass through or rest on AxisIQ's servers.
Certifications
AxisIQ does not currently hold third-party certifications such as SOC 2 or ISO 27001. If your procurement process needs a security questionnaire answered, email us and we will answer it in writing.
Reporting a vulnerability
If you believe you have found a security issue in AxisIQ, email hello@axisiq.co with "Security" in the subject line, the steps to reproduce it and the impact you expect. Please:
- give us reasonable time to fix the issue before disclosing it publicly;
- test only against your own account and organisation, and never access, change or delete other people's data;
- avoid anything that degrades the service for others, such as load testing or spam.
We will acknowledge your report, keep you informed while we fix it, and will not pursue legal action against research done in good faith within these rules.
More
How we collect and use personal data is described in the privacy policy; the rules for using the service are in the terms of service.