We take a practical approach to security. Every PQ Intel customer — from solo founders to growth-stage teams — gets the same encryption, access controls, and data protection standards. This page documents exactly how we handle your data, what third parties we rely on, and what happens in the event of a breach. There are no empty certifications here — just verifiable practices.
All customer data stored in our databases is encrypted at rest using AES-256 (Advanced Encryption Standard with 256-bit keys). This includes prospect data, signal history, ICP definitions, contact enrichment results, email templates, and all pipeline configuration. Database volumes use operating-system-level encryption with keys managed separately from the data they protect. Database backups are encrypted before leaving the server and remain encrypted in cold storage.
All network traffic between your browser and our servers uses TLS 1.3 (Transport Layer Security, the current industry standard). We enforce HTTPS on every subdomain and every route — there are no plain-text endpoints. API traffic from our platform to third-party services (enrichment APIs, LLM providers) also uses TLS. We do not support legacy TLS versions or unencrypted connections.
API keys, access tokens, and secrets are stored using hardware-backed encryption with separate key management. Secrets are never logged, never exposed in API responses, and never visible in the browser. Access to secret management infrastructure is logged and restricted to essential personnel only.
We enter into a Data Processing Agreement (DPA) with every customer who processes EU personal data. The DPA covers our obligations under Article 28 of the GDPR. You can request a pre-signed copy by emailing [email protected]. We sign standard contractual clauses (SCCs) for international data transfers where required.
We process personal data on the basis of legitimate interest (Article 6(1)(f) GDPR) — providing prospect intelligence and lead enrichment services to B2B customers. We do not process special category data. Data subjects have the right to object to processing, request access, rectification, erasure, and data portability under Articles 15–20 of the GDPR.
Any individual can submit a DSAR by emailing [email protected]. We acknowledge receipt within 24 hours and fulfil the request within the statutory 30-day window. If we need to verify your identity before fulfilling a request, we ask only for information reasonably necessary to prevent unauthorised disclosure.
We support EU data residency for customers who need their data hosted within the European Economic Area. Contact [email protected] to enable EU residency on your account. By default, data is processed on infrastructure in Europe (Hetzner, Germany) and North America (DigitalOcean, US East).
We maintain an internal Record of Processing Activities (ROPA) as required by Article 30 GDPR. Our data protection impact assessment (DPIA) for prospect intelligence processing is available for review under NDA. Contact [email protected] to arrange a review.
We collect and process only the data necessary to deliver prospect intelligence. For ICP definitions, we store firmographic attributes you configure (industry, company size, location, tech stack). For prospect profiles, we store publicly available professional data and firmographic signals. We do not store sensitive personal data, financial data, health data, or any special category information.
We never share your prospect data, ICP definitions, signal history, or email templates with third parties. Your data is yours. We do not sell data, license it, or use it to train models. The only exception is processing via our sub-processors (listed below) strictly for the purpose of delivering the service.
You can export all your data at any time from the settings page. Exports include prospect profiles, signal history, enrichment results, email templates, and pipeline configuration. The export is delivered as structured JSON files. We do not charge for data export and will not hold your data hostage.
By default, customer data is stored on infrastructure located in Germany (Hetzner) and United States (DigitalOcean). We route signal pipeline traffic and enrichment queries through the nearest available region to minimise latency. Cache data may be temporarily stored at CDN edge locations via Cloudflare, but no persistent customer data is stored outside your designated region.
We use the following sub-processors to deliver PQ Intel. Each one has been evaluated for security practices and contractual data protection obligations. We update this list when sub-processors change and notify customers via the changelog.
Purpose: CDN, DNS, DDoS protection, edge caching.
Data: IP addresses, edge cache fragments (no persistent customer data).
Location: Global edge network.
Certifications: SOC 2 Type II, ISO 27001, Privacy Shield.
Purpose: Cloud infrastructure — compute, database, storage.
Data: All persistent customer data (prospect profiles, signal history, pipeline config).
Location: United States (NYC1, SFO3) or Europe (FRA1) — configurable per account.
Certifications: SOC 2 Type II, ISO 27001, PCI DSS Level 1.
Purpose: Cloud infrastructure — EU compute and storage.
Data: Customer data for EU residency accounts.
Location: Nuremberg, Germany (FSN1) / Helsinki, Finland (HEL1).
Certifications: ISO 27001, C5 Type II (BSI).
Purpose: LLM inference for signal analysis, content generation, and enrichment classification.
Data: Text prompts (no customer data stored by OpenRouter — inference-only processing).
Location: US and EU.
Privacy: API data is not logged or stored beyond request-response cycle.
Purpose: Contact email verification and enrichment data.
Data: Email addresses and professional profile URLs for verification lookups.
Location: US.
Compliance: DPA available, GDPR-compliant data processing.
Access to production infrastructure is limited to essential engineering personnel only. All access requires SSH key authentication — password-based access to servers is disabled. Infrastructure access is logged, and logs are reviewed weekly. Access keys are rotated quarterly and immediately upon personnel change. We enforce least-privilege access: no single individual has unrestricted access to all systems.
PQ Intel supports role-based access. Account owners can invite team members with configurable permission levels. Session management includes automatic timeout after 30 minutes of inactivity, forced re-authentication on sensitive actions, and the ability for account owners to revoke any session from the settings panel. We support single sign-on (SSO) for team accounts on the Pro plan and above.
All authentication events, configuration changes, data exports, and team member modifications are logged with timestamp, actor, and action description. Audit logs are immutable — they cannot be modified or deleted by any user. Account owners can view audit logs from the settings panel. Logs are retained for a minimum of 12 months.
API access requires a valid API key generated from the settings panel. API keys can be scoped to specific capabilities (read-only, write, admin) and can be revoked individually. API requests are authenticated via Bearer token in the Authorization header. Rate limiting applies per key to prevent abuse.
We operate 24/7 automated monitoring for unauthorised access attempts, anomalous traffic patterns, and configuration drifts. Intrusion detection systems (IDS) are deployed on all production servers. When a potential incident is detected, our on-call engineer is notified within 5 minutes and begins assessment within 30 minutes.
In the event of a confirmed data security incident involving customer data, we will:
Within 24 hours: Acknowledge the incident internally and begin containment.
Within 48 hours: Provide initial notification to affected customers via email.
Within 72 hours: GDPR-compliant notification to supervisory authority (where required).
Within 7 days: Full incident report to all affected customers including scope, data involved, root cause, and remediation steps.
If you discover a security vulnerability or suspect a breach, email [email protected] immediately. You can also report via our GitHub repository security advisory process. We acknowledge receipt within 24 hours and provide a fix timeline within 72 hours for confirmed vulnerabilities. We support responsible disclosure and do not pursue legal action against researchers acting in good faith.
We retain your data for the duration of your active subscription plus a 30-day grace period after cancellation. This grace period allows you to reactivate your account without data loss or export your data at your own pace. After 30 days, all customer data is permanently deleted from production databases, backups, and any cached copies.
Automated backups are retained for a rolling 14-day window. Encrypted backups older than 14 days are automatically purged. Backups are stored in a separate geographic region from the primary database and are encrypted with a different key set.
You can cancel your subscription at any time from the settings panel — no need to contact support. Upon cancellation, you immediately lose access to premium features, but all your data remains accessible in read-only mode for the 30-day grace period. To request expedited deletion, email [email protected] with your account email.
We are not SOC 2 certified. As a growth-stage company, we focus resources on product development and verifiable security practices rather than certification audits. We maintain the same controls that SOC 2 requires — encryption, access logging, incident response, and change management — without the annual audit overhead. If SOC 2 is a requirement for your procurement process, contact [email protected] to discuss an alternative assessment.
By default, customer data is stored on DigitalOcean infrastructure in the United States (NYC1, SFO3) or Germany (FRA1) depending on your account configuration. EU data residency is available on request. Edge-cached data may temporarily pass through Cloudflare's global network, but no persistent customer data is stored at edge locations.
Yes. Email [email protected] with your company name and legal contact, and we will provide a signed DPA within one business day. Our standard DPA covers Article 28 GDPR obligations and includes Standard Contractual Clauses for international transfers.
Go to Settings > Data Export in the app. You can export all prospect data, signal history, ICP definitions, and email templates as structured JSON. Export is immediate and free. There is no limit on the number of exports.
When your subscription lapses, your account enters a 30-day grace period during which data remains accessible in read-only mode. After 30 days, all customer data is permanently deleted from production databases, backups, and cached copies. We do not retain any customer data beyond the grace period.
Never. Each customer operates in an isolated workspace tenant. Prospect data, signal history, ICP definitions, and email templates are scoped to a single tenant and never visible to any other customer. We do not aggregate customer data, sell it, or use it to train models.
No. Your data — including prospect profiles, email templates, and ICP definitions — is never used for model training. LLM inference requests sent through OpenRouter are processed ephemerally and not stored or logged. Our enrichment pipeline sends structured queries to TinyFish and OpenRouter APIs solely for the purpose of returning results to your account.
Try PQ Intel for $5. No commitment, no credit card required for trial.
Try for $5 — 3 days