How does iDBQuery support CCPA compliance?
iDBQuery is designed to support your CCPA obligations by keeping consumer personal data in your own systems, where you handle access, deletion, and opt-out requests. iDBQuery does not sell your data and does not use it to train an AI model, and query-in-place means there is no separate copy to manage.
The California Consumer Privacy Act gives consumers rights over their personal information, and iDBQuery's architecture helps you honour them.
- You stay in control - personal data remains in your source systems; iDBQuery queries it in place rather than force-copying it, so your records stay authoritative.
- No sale of data - iDBQuery does not sell your data, and it does not use it to train any AI model.
- Request support - to answer an access or deletion request, you can ask iDBQuery in plain language where a consumer's records appear across your sources, with every result cited to its exact source row, then act in the source system.
- Deployment choice - VPC, on-prem, or air-gapped installs keep the data inside the boundary you require.
For example, when a consumer requests deletion, you remove their records in your systems and iDBQuery no longer surfaces them, because it never held its own copy. It is important to frame this accurately: iDBQuery provides architecture designed to support your CCPA compliance - it is not a legal certification, and you remain the responsible business. That is a more honest and, ultimately, stronger position than a compliance badge: privacy is enforced by where processing happens, reinforced by RBAC, field masking, and encryption in transit and at rest. Contact us to fit iDBQuery into your CCPA request workflow.
Updated 2026-06-22