How does iDBQuery handle GDPR data-subject access and erasure requests?

Data-subject requests - access, rectification, and erasure - are the controller's responsibility, and iDBQuery is architected to make them easier rather than harder.

• Data stays with you - iDBQuery queries your sources in place, so the authoritative personal data remains in your databases, which is where you fulfil a request.
• Fewer copies to chase - because it does not bulk-export your records, there is no shadow copy inside iDBQuery to hunt down when someone asks to be forgotten.
• Faster location - ironically, iDBQuery can help you answer a subject-access request by letting you ask, in plain language, where a person's records appear across connected sources, with each finding cited to its exact source row.
• Deployment options - on-prem, air-gapped, or EU-region deployments keep personal data within the boundary and jurisdiction you require.

For example, when an erasure request comes in, you delete the records in your source systems as usual; iDBQuery simply stops seeing them, because it read them live rather than storing its own copy. To be clear, this describes architecture designed to support your GDPR obligations - it is not a certification, and you remain the controller. That structural honesty is the point: strong privacy comes from where and how data is processed, backed by RBAC, masking, and encryption in transit and at rest. Contact us to align iDBQuery with your data-subject-request process.