How kwery handles data protection, sub-processors, GDPR obligations, audit trails for compliant dynamic pricing, and acceptable use.
kwery provides three layers of defensibility: audit trails (every observation includes timestamp and source attribution), confidence scores (document which results you filtered and why), and signed change events (your repricing reacts to actual market movement, not noise). Together this gives compliance teams a clear record of how each pricing decision was reached using market data — not personal consumer data. Compliance & Provenance.
Yes. kwery publishes a pre-signed Data Processing Addendum (GDPR Art. 28) that is incorporated by reference into our Terms when you accept them. No countersignature is required for self-serve customers. View DPA.
Our sub-processor list is public and kept up to date. Today it includes Supabase (auth and identity), Hetzner (application servers, PostgreSQL, and data pipelines, hosted in Germany), Cloudflare (DNS, CDN, WAF), and Resend (transactional email). View Sub-processors.
Operational pricing data and event history are retained for the active term of your subscription and a short window thereafter for audit and replay. Account data follows the retention rules in the Privacy Policy. Privacy Policy.
Yes. kwery is intended for legitimate market intelligence and pricing use cases. You are responsible for keeping your API keys confidential, complying with applicable law, and not using the data to harm consumers or violate marketplace terms. Terms of Service.
Request API access and the team will walk through sources, volumes, and integration in detail.