Security and trust
Security, stated plainly. Gaps included.
A CRM holds your customers, your deals and your conversations. This page describes what protects them today, area by area, and says what we do not have yet. We would rather give you an accurate answer than an impressive one.
In brief
Six things to know.
Every workspace is isolated with row-level security enforced by the database itself, and the isolation rules are tested automatically on every change.
Roles and record-level access are enforced on the server. Two-factor sign-in, an IP allowlist and login hours are available to admins.
Genie runs with the signed-in user's permissions, pauses for confirmation on significant actions, and can be switched off per workspace or per person.
Record rooms follow the record's visibility. Messages can be scanned for secrets and card numbers, kept for a period you choose, audited and exported.
Deleted records go to a recycle bin for 24 hours, and admins can export a complete copy of the workspace at any time.
We do not yet hold SOC 2 or ISO 27001, and single sign-on is not available today. Details are in the status table below.
Workspace isolation
One workspace cannot read another.
Every table is tied to its owning workspace, and the database itself refuses to return one company's records to another. A software bug in the application cannot cause a leak between customers, because the rule does not live in the application.
People join a workspace by invitation, and invitations expire. Each person acts with the role and feature permissions their administrator assigned.
Access control
What admins can set.
| Control | How it works |
|---|---|
| Roles and record-level access | Per person and per type of record: everything, their team's records, only their own, or none. Enforced on the server, never only by hiding a button. |
| Two-factor sign-in | Available to everyone and can be required for the whole workspace. Exporting all data, creating a login and resetting a password also need the administrator to have completed two-factor sign-in. |
| IP allowlist and login hours | Admins can restrict sign-in to approved IP addresses and to set hours of the day. |
| Sessions and passwords | Sessions end after seven days. The workspace sets a minimum password length. |
| Feature switches | Features, including Genie, can be switched off per plan, per workspace and per person. |
| Our own staff access | Veliq staff reach customer workspaces only through a separate operator panel that requires two-factor sign-in for every action and writes to a tamper-resistant log. |
AI and your data
What happens when you use Genie.
Genie acts as the person asking, so role and record-level access apply to it exactly as they apply to a human. It cannot show anyone a record they could not open themselves.
- What is sent. Only what a request needs: your question and the records the answer depends on, not your database. Requests carry an anonymous identifier, never your name or email.
- Masking. Recognizable secrets such as keys, tokens and card numbers are masked before text leaves our systems.
- Training. Your data is never used to train AI models.
- Retention. The provider may keep request data for a limited period, up to 30 days, solely to detect abuse.
- Confirmation. Merges, invoices, bulk changes, owner changes and large deals always pause for your explicit confirmation. If Genie has just read something written by someone outside your company, every change it proposes needs confirmation.
- Controls. Admins can switch Genie off per workspace or per person, switch Research Mode off separately, and see usage and cost.
Inchat
Chat that follows the record.
A deal, account, contact or ticket room is readable only by people who can open that record, and its files and search results follow the same rule. If someone loses access to the deal, they lose the room immediately. Public channels, private channels and direct messages follow channel membership.
Admins can scan messages for API keys, private keys and card numbers and either redact or block them, set retention from 30 days to 7 years, review flagged messages, and export messages. An admin audit log records changes to chat settings, channels, moderation, exports and webhooks. Message contents are never written to it.
Data lifecycle and hosting
Where data lives, and how it leaves.
Customer data is hosted in the Asia-Pacific region (Singapore). Connections are encrypted, and stored data is encrypted at rest by our infrastructure provider. We never sell customer data or use it to advertise.
Admins can export a full copy of the workspace as a set of CSV files at any time. Deleted records are held in a recycle bin for 24 hours. When a customer leaves, its workspace is permanently deleted through a deliberate two-step process with a waiting period, on written request under the data processing agreement.
We use sub-processors for hosting and the database, email delivery, AI processing and bot protection. The named list is provided with the data processing agreement.
Current status
What we do not have yet.
| Area | Status | Detail |
|---|---|---|
| SOC 2 or ISO 27001 | Not yet | We provide a security overview, a data processing agreement and a completed questionnaire on request, and an assurance roadmap is planned. |
| Independent penetration test | Planned | We have completed an internal security review whose findings were fixed and retested. A summary of the independent test will be shared when it is complete. |
| Single sign-on (SAML or OIDC) | Not available | On the roadmap. |
| Setup and permission audit log | Seven days | Retention is currently seven days. Longer retention is planned. |
| Hosting region choice | Not available | Data is hosted in Singapore only. |
On request we can complete your own security questionnaire and arrange a call between our team and your IT or legal team. For how veli(Q Lab approaches security more widely, see veliqlab.com/security.
Security
Security, answered.
Is our data kept separate from other companies?
Yes. Every table is isolated per organization with row-level security enforced by the database itself, so one workspace cannot read another's records even if the application layer were bypassed. The isolation rules are tested automatically on every change.
How do roles and access work?
Admins set, per person and per type of record, whether someone sees everything, their team's records or only their own. These rules are enforced on the server. Two-factor sign-in is available to everyone and can be required for the whole workspace, admins can restrict sign-in to approved IP addresses and set login hours, and sessions end after seven days.
Where is our data stored?
In the Asia-Pacific region (Singapore) on our cloud infrastructure provider. Connections are encrypted, and stored data is encrypted at rest by our infrastructure provider. We never sell customer data or use it to advertise.
What happens to our data when we use AI?
Only what a request needs is sent: your question and the records the answer depends on, not your database. Recognisable secrets such as keys, tokens and card numbers are masked first, requests are labeled with an anonymous identifier, and your data is never used to train AI models. The provider may keep request data for a limited period, up to 30 days, solely to detect abuse.
Do you hold SOC 2 or ISO 27001, and do you support single sign-on?
Not yet to either. We would rather say so plainly. Today we provide a security overview, a data processing agreement and a completed security questionnaire on request, and an independent penetration test is planned. Single sign-on is on the roadmap. The full picture is on our security page, and we will tell you plainly whether a control you need exists, can be built, or is a gap.
Is there an audit trail, and can we recover deleted records?
Every record has an activity timeline, and Genie's actions are logged and attributed. Administrative and permission changes are written to an audit log, currently retained for seven days, with longer retention planned. Deleted records go to a recycle bin before they are removed, and admins can export a complete copy of the workspace at any time.
What happens to our data if we leave?
Export your workspace whenever you like. When a customer leaves, its workspace is permanently deleted through a deliberate two-step process with a waiting period, on written request under the data processing agreement.
Bring your toughest questions.
Tell us what your IT or legal team needs to see. We will say plainly whether a control exists, can be built, or is a gap.