Kept apart where it counts: in the database.

Every row of data carries its unit. The database refuses to return a row to anyone outside it, whatever screen, report or export asks.

DATABASE UNIT ROLE Your records 2,914 rows · Gurugram

Three layers close around every record: the database, the unit and the role.

Row-level security, on every table.

Isolation is a rule in the database. A request arrives with its user, role and unit, and the database filters every query by them before any data leaves.

  • Units never read each other's records. A campus cannot see another campus, and a dealership cannot see another dealership.
  • The group sees roll-ups. Totals per unit for pipeline, conversion and usage, never the records behind them.
  • Roles narrow it further. Own, team or unit scope applies to screens, reports, exports and Appy alike.
GROUPSees totals only totalstotals Unit AUnit B 0 visible

Each unit's rows carry its unit. The database filters every query by it.

Every change has a name against it.

Field history keeps the old and new value on every record. Approvals keep the person who gave them. The audit trail cannot be edited.

  • Field history on every record, with who and when.
  • Approvals and returns recorded with the approver's name and comment.
  • Changes to stages, roles, workflows and connectors logged for admins.
  • Audit kept for 1 year on Startup and Growth, or 7 years with the retention add-on.
Field history · QT-5521cannot be edited
14:02Discount 6% → 9% · Plant Sales Engineer
14:20Approval granted by Rajesh Kulkarni, plant head · "repeat buyer, volume order"
14:21Stage Costing → Quotation Sent · workflow
15:40Owner Neha Joshi → Arjun Patil · Sales manager

When support signs in for you, you know.

Sometimes our support team needs to see what you see. Every such session is bounded, visible and permanent on the record.

Justification

Customer reports the SLA clock on CS-7188 did not pause while awaiting the owner; checking the case settings.

Blocked in this session

Try one of the blocked actions.

  • A reason code and a written justification. No session starts without both, and the justification must be at least 40 characters.
  • A time cap. The session ends on its own when the time is up.
  • Blocked actions. Export, delete, billing, credentials and permissions are off limits in every session.
  • Logged for good. The session log cannot be deleted, by us or by you.
  • You are told. The tenant is notified when a session starts.

More of the same care.

Credentials stay yours

Connector keys are write-only. Nobody can read them back, including platform support.

No card data

Card and UPI details stay with your payment gateway. We keep the payment status.

Children's data

K-12 records carry stricter consent, retention and access rules.

Appy within bounds

The assistant reads only what your role can open, and drafts wait for approval.

Talk to us about your security review

Questions and answers

How is our data kept separate from other companies and units?

Every row of data carries its unit, and the database itself refuses to return a row to anyone outside it (row-level security), so every screen, report and export inherits the isolation.

Where is Curve CRM data stored?

Curve CRM’s servers and database are hosted by Contabo GmbH in Germany, inside the European Union. The Privacy Policy explains this transfer from India, which the Digital Personal Data Protection Act, 2023 permits.

Can Curve CRM staff see our records?

Only through a support session that needs a stated reason, ends on its own after 15, 30 or 60 minutes, shows a banner, cannot export, delete or change permissions, and is written to a log nobody can edit.

Is there an audit trail?

Yes. Every change has a name against it: field history on every record, approvals with the person who gave them, and a log of every support session.

All questions and answers ›