Privacy Policy
Last updated: January 2025
Overview
qvctrs ("we", "our", or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and safeguard information when you use our qualified view tracking service.
What Data We Collect
Our SDK collects behavioral interaction data to measure engagement quality. This includes:
- Mouse movements and scroll patterns
- Click and keyboard interactions
- Time spent on page and attention metrics
- Device type and browser information
- Page URLs and referrer information
Zero PII Collection
We do not collect personally identifiable information (PII). No names, emails, IP addresses, or other data that could identify individual users.
How We Use Data
The behavioral data we collect is used to:
- Calculate quality scores to distinguish genuine engagement from bots
- Train and improve our AI-powered attention verification models
- Generate aggregated analytics for publishers
- Calculate earnings based on qualified view counts
All data is processed in anonymized, aggregated form. We do not sell or share individual-level data with third parties.
Data Retention
Session-level behavioral data is retained for 90 days for quality scoring and analytics purposes. Aggregated statistics are retained indefinitely for historical reporting. Publishers can request deletion of their site's data at any time through the dashboard settings.
GDPR Compliance
We are committed to GDPR compliance. Since we collect only behavioral data without PII, most GDPR individual rights do not directly apply. However:
- Right to Information: This policy explains our data practices
- Right to Erasure: Publishers can delete their site data
- Right to Object: Website visitors can use browser privacy settings or ad blockers
- Data Minimization: We only collect data necessary for quality scoring
Cookies
Our SDK uses a session identifier stored in localStorage to track engagement within a single browsing session. This is not a persistent tracking cookie and does not track users across sites or over time.
Third-Party Services
We use the following third-party services:
- Supabase: Database and authentication
- Stripe: Payment processing (for publisher payouts)
- Cloudflare: CDN and security
Security
We implement industry-standard security measures including encryption in transit (TLS), encryption at rest, and regular security audits. Access to data is restricted to authorized personnel only.
Changes to This Policy
We may update this Privacy Policy from time to time. We will notify registered publishers of any material changes via email. Continued use of our service after changes constitutes acceptance of the updated policy.
Contact Us
If you have any questions about this Privacy Policy or our data practices, please contact us at: