Privacy Policy
Last updated: 17. november 2026
1. Introduction
Virkly is operated by Dvinge ApS (CVR: 42992135), a Danish company. We are committed to protecting your privacy and handling your data responsibly. This privacy policy explains how we collect, use, and protect your information when you use our CVR API service.
By using Virkly, you accept the collection and use of information in accordance with this policy.
2. Information We Collect
2.1 Account Information
When you create an account via WorkOS authentication, we collect:
- Email address (required)
- Name (optional)
- Company name (optional)
- CVR number (optional, if provided during onboarding)
- Company size (optional, if provided during onboarding)
Note: We never store your password. Authentication is handled exclusively by WorkOS, our authentication provider.
If you sign up from a button about a feature we haven't built yet (e.g. a complete company check), we note which feature you were interested in, so we can let you know if it launches. It is deleted when you delete your account.
Once you are logged in, we ask once what you will use virkly for. We store your answer (one of the fixed choices, no free text) on your account to tailor the product. It is deleted when you delete your account.
2.2 API Usage Data
When you use our API, we automatically collect:
- API endpoints called and HTTP methods used
- Response status codes and response times
- IP addresses
- User agent strings
- Request parameters (searched CVR numbers)
- Cache hit/miss status
- Request timestamps
This data is retained for 90 days and automatically deleted thereafter.
2.3 Billing Information
For payment processing, we store:
- Stripe customer ID (reference to your Stripe account)
- Subscription status and tier
- Billing periods and amounts
- Invoice records
Note: We never store credit card numbers or payment details. All payment information is handled securely by Stripe.
3. How We Use Your Information
We use collected information for the following purposes:
- Service delivery: To deliver and maintain our API service
- Billing: To process payments and manage subscriptions via Stripe
- Usage analytics: To display your API usage in the dashboard and calculate billing
- Security: To detect and prevent abuse, enforce rate limits, and protect our infrastructure
- Communication: To send transactional emails (payment confirmations, API key notifications) via Resend. Registered users also get a welcome email and a small number of account and product tips and reminders (such as a summary of their watches after the first week), based on our legitimate interest (Article 6(1)(f)): at most one every 3 days and no more than 6 in the first 30 days. Every one has a one-click unsubscribe link; individual watch alerts, receipts and security emails continue after you unsubscribe. We do not track whether our emails are opened or which links are clicked.
- Error monitoring: To track and resolve technical issues via Sentry
- Compliance: To comply with legal obligations and enforce our terms
4. Third-Party Services
We share your information with the following carefully selected service providers that help us operate Virkly:
4.1 Authentication: WorkOS
WorkOS handles user authentication, including password storage and session management. We never have access to your password.
- Data shared: Email, name
- Purpose: User authentication and session management
- Privacy policy: workos.com/privacy
4.2 Payments: Stripe
Stripe processes all payments and stores payment method details. We only receive a customer reference ID.
- Data shared: Email, billing address (when provided)
- Purpose: Payment processing, subscription management, invoicing
- Privacy policy: stripe.com/privacy
4.3 Email Delivery: Resend
Resend delivers our emails: transactional emails (API key and watch notifications) and the welcome and account tips emails described in section 3.
- Data shared: Email address, email content
- Purpose: Delivery of transactional emails and account tips emails
- Privacy policy: resend.com/legal/privacy-policy
4.4 Error Monitoring: Sentry
Sentry helps us identify and fix technical issues. We have implemented filters to prevent personal data from being sent to Sentry.
- Data shared: Technical error data, anonymized request information
- Purpose: Error tracking and debugging
- PII filtering: Email addresses, API keys, tokens, and sensitive fields are automatically redacted
- Privacy policy: sentry.io/privacy
4.5 Analytics: Plausible Analytics
Plausible Analytics is a privacy-friendly analytics service that helps us understand how our website, API and MCP server are used.
- Data shared: Statistics without names, email addresses or user IDs: page views, referral sources, country (derived from the IP address), device and browser type. We also count logins, sign-ups and API and MCP calls as anonymous events (see section 8.2). For this, the IP address of the visitor or API caller is passed on to Plausible, which does not store it
- Purpose: Analytics of website, API and MCP usage, and improving the user experience
- No cookies: Plausible uses no cookies or persistent identification
- EU hosting: All data is stored in the EU
- GDPR compliant: No consent required, as no cookies are used and neither raw IP addresses nor persistent user identifiers are stored
- Privacy policy: plausible.io/privacy
4.6 Infrastructure: Hetzner (EU)
Our servers are hosted on Hetzner infrastructure in the European Union.
- Location: Germany/Finland (EU)
- Purpose: Hosting our application and database
- Privacy policy: hetzner.com/legal/privacy-policy
4.7 CDN and Security: Cloudflare
All traffic to virkly.io passes through Cloudflare, which delivers the website and protects it against attacks and abuse.
- Data shared: IP address and all traffic to and from virkly.io, including request metadata (URL, user agent, time of request), on every visit
- Purpose: Content delivery, caching and protection against attacks
- Legal basis: Legitimate interest in delivering the service securely (GDPR Article 6(1)(f))
- Transfers outside the EU: Cloudflare, Inc. is based in the USA and certified under the EU-US Data Privacy Framework
- Privacy policy: cloudflare.com/privacypolicy
4.8 Legal Requirements
We may disclose your information if required by law or to:
- Comply with legal processes or government requests
- Enforce our terms of service
- Protect our rights, privacy, safety, or property
- Investigate fraud or security issues
5. CVR Data and Public Registries
The CVR data provided through our API comes from the Danish Business Authority's public registries. This data is:
- Publicly available information about Danish companies
- Provided by the Danish Business Authority
- Subject to Danish data protection rules
- Temporarily cached for 15 minutes to improve performance
- Phone numbers and email addresses of sole proprietorships with advertising protection (reklamebeskyttet) are not shown on company pages, in the API or via MCP, because they are a private person's contact details
- We also republish three other public registers: authorisations from the Danish Safety Technology Authority (Sikkerhedsstyrelsen), food inspection results from the Danish Veterinary and Food Administration (Fødevarestyrelsen) and the company register of the Danish FSA (Finanstilsynet). We store no person names from them: only the CVR number, the authorisation area and number, when it was seen in the register and changes to it, inspection counts, dates and results, and the company type and start date in Finanstilsynet's register
We do not claim ownership of CVR data. Users must comply with applicable legislation when using this data.
6. Data Retention
We retain your information according to the following schedule:
- API usage logs: 90 days (automatically deleted)
- Account data: Until account deletion
- Billing records: 5 years (required by Danish accounting law)
- API keys: Until revocation or account deletion
- Web server access logs (IP address, URL, user agent): 14 days, then deleted
After account deletion, your profile data is anonymized, but billing records are retained to comply with legal requirements.
7. Legal Basis for Processing
Under GDPR Article 6, we process your personal data based on the following legal grounds:
- Contract performance (Article 6(1)(b)): We process your account information, API usage, and billing data to provide our service to you. Without this processing, we cannot deliver the Virkly API service.
- Legal obligation (Article 6(1)(c)): We retain billing records for 5 years to comply with Danish accounting law (Bogforingsloven).
- Legitimate interest (Article 6(1)(f)): We process API usage logs, IP addresses, security data, and your email address to:
- Prevent abuse and ensure service security
- Enforce rate limits and fair use terms
- Identify and resolve technical issues
- Protect our infrastructure against attacks
- Send a welcome email and a few account tips, such as a summary of your watches (see section 3)
Our legitimate interest in these activities is balanced against your privacy through:
- Automatic deletion of API usage logs after 90 days and web server access logs after 14 days
- PII filtering in error reports
- No resale or sharing of log data
- A one-click unsubscribe link in every welcome and tips email, and at most one such email every 3 days
- Consent (Article 6(1)(a)): We use your consent to collect and process:
- Sentry Session Replay data (session recordings)
You can withdraw your consent at any time by changing your cookie preferences. This does not affect the lawfulness of processing based on consent before withdrawal.
Note: Analytics via Plausible (website, API and MCP usage) does not require consent, as the service uses no cookies and stores neither raw IP addresses nor persistent user identifiers. The IP address is only passed on to Plausible for the daily visitor count and an approximate location (see section 8.2). Plausible is processed under our legitimate interest in improving the service (Article 6(1)(f)).
8. Cookies and Tracking Technologies
We use cookies and similar technologies to deliver and improve our service. You can change your cookie preferences at any time via the banner at the bottom of the page or on our cookie page.
8.1 Essential Cookies (no consent required)
These cookies are necessary for the service to function:
- wos-session: Authentication session cookie
- Purpose: Keeps you logged in and ensures session security
- Duration: Until you log out or the session expires
- Type: HttpOnly, SameSite=Lax (cannot be read by JavaScript for security reasons)
8.2 Analytics (no consent required)
We use Plausible Analytics to understand how users interact with our service. Plausible is a privacy-friendly analytics service that:
- Uses no cookies: Plausible does not require cookies to function
- Stores no IP addresses or persistent identifiers: Plausible receives the IP address and the browser's user agent and uses them only to count unique visitors per day (as a daily identifier: a hash with a salt that is deleted every 24 hours, so it cannot be linked across days) and to look up an approximate location. The raw IP address is never stored. No persistent user identifiers, no cross-site tracking
- GDPR compliant: Fully compliant without requiring a cookie banner
- EU hosting: All data is stored in the EU
- Data collected: Page views, referral sources, country (derived from the IP address), device and browser type (no fingerprinting)
- API and MCP usage: Logins, sign-ups and calls to our API and MCP server are also counted as anonymous events in Plausible. An event says which type of endpoint or tool was called and carries technical details of the call (such as HTTP method, status code, cache hit, batch size, the names of the filters used, authentication method and plan). It never contains the search text, the company or person looked up, your email, user ID or API key. The caller's IP address is passed on to Plausible for this and handled as described above. Events from our own background jobs are sent without a caller IP address
- Plausible privacy policy: plausible.io/privacy
Note: Because Plausible uses no cookies and stores neither raw IP addresses nor persistent identifiers, it does not require your consent under GDPR.
8.3 Session Recording (requires your consent)
We use Sentry Session Replay to identify and resolve technical issues:
- Type: Stored in sessionStorage (disappears when you close the browser)
- Purpose: Record user interactions to reproduce bugs and improve user experience
- Sampling: 10% of normal sessions, 100% of sessions with errors
- Duration: 30 days after collection
- Privacy: All text is masked, all media is blocked to protect your confidentiality
- Data collected: Anonymized clicks, navigation, scroll behavior
- Sentry privacy policy: sentry.io/privacy
8.4 Manage Your Cookie Preferences
You can at any time:
- Change your cookie settings via the banner on the page
- Visit our dedicated cookie page
- Delete cookies via your browser settings
- Use browser extensions to block tracking cookies
Note: If you reject Sentry Session Replay, it does not affect your ability to use Virkly. All core features will continue to work.
8.5 What We DO NOT Use
We do not use:
- Advertising cookies or remarketing pixels
- Social media tracking pixels (Facebook Pixel, LinkedIn Insight, etc.)
- Third-party ads or advertising networks
- Affiliate tracking
9. Your Rights Under GDPR
As a user in the European Union, you have the following rights:
- Right of access: Export all your data from your dashboard settings
- Right to rectification: Update your profile information in the dashboard
- Right to erasure: Delete your account from the dashboard settings
- Right to restriction of processing: Contact us to restrict how we use your data
- Right to data portability: Export your data in a structured JSON format
- Right to object: Object to processing of your personal data
- Right to withdraw consent: Withdraw consent at any time
How to exercise your rights
You can exercise most of your rights directly in the Virkly dashboard:
- Data export: Settings - Export data
- Account deletion: Settings - Delete account
- Profile updates: Settings - Profile
For other requests, contact us at [email protected]
10. Data Security
We implement industry-standard security measures to protect your data:
- Encryption in transit: All connections use TLS/SSL
- API key security: API keys are hashed with bcrypt (we never store them in plaintext)
- Password security: Handled exclusively by WorkOS (we never see your password)
- Rate limiting: Protection against abuse and brute-force attacks
- Input validation: All inputs are validated to prevent injection attacks
- PII filtering: Sensitive data is automatically redacted from logs and error reports
While we strive to protect your data, no method of transmission over the internet is 100% secure. We cannot guarantee absolute security.
11. International Data Transfers
Your data is primarily processed within the European Union (Hetzner hosting in Germany/Finland). Some data may be transferred to service providers outside the EU:
- WorkOS: USA-based (EU Standard Contractual Clauses)
- Stripe: USA-based (EU Standard Contractual Clauses, EU data residency available)
- Resend: USA-based (EU Standard Contractual Clauses)
- Sentry: USA-based (EU Standard Contractual Clauses)
- Cloudflare: USA-based (EU-US Data Privacy Framework, EU Standard Contractual Clauses)
Plausible Analytics Plausible Analytics is hosted in the EU (Germany), so no data leaves the EU for web analytics.
All our service providers maintain GDPR-compliant data processing agreements and use appropriate safeguards for international transfers.
12. Children's Privacy
Virkly is a business service intended for use by developers and businesses. We do not knowingly collect personal information from individuals under 18 years of age. If you believe we have collected information from a child, please contact us immediately.
13. Changes to This Policy
We may update this privacy policy from time to time. We will notify you of significant changes by:
- Publishing the new policy on this page
- Updating the "Last updated" date
- Sending an email notification for significant changes
Continued use of our service after changes constitutes acceptance of the updated policy.
14. Monitoring of Individuals ("Watch a Person")
Virkly lets signed-in users "watch" a named individual and receive an email when a company associated with that person enters a distress status in the Danish Central Business Register (CVR) — bankruptcy (konkurs), restructuring, compulsory or voluntary dissolution, or being dissolved. We do not send alerts for routine or positive changes.
What we process and why
When you watch a person, we store your account ID and the public CVR identifier (enhedsnummer) of the person watched. When a company linked to that person enters one of these statuses, we send you an email stating that single, already-public fact. You can also watch a specific company; we then store your account ID and the company's public CVR number, and email you when that company changes its status, name, address, industry, capital, legal form or employee count. In both cases we do not store a copy of the watched person's or company's profile — details are looked up live from the public register at the time of sending — and our alerts contain no risk assessment, scoring, commentary, or private information.
For a watched company, webhooks and our MCP connector also report owner changes (ejerskifte) from the public register of owners; these are not emailed. An owner company (such as an ApS, A/S or fund) is named by name and CVR number; every other owner shows only as "other owners changed", never named or counted, and a natural person is never named.
Who this concerns
A watched person is typically a director, board member, founder, or registered owner of a Danish company. The information we surface (company status, role) is already public in CVR by law.
Lawful basis
We process the watched person's identifier on the basis of legitimate interests (Article 6(1)(f) GDPR): the legitimate interest of users in carrying out due diligence on people they do business with, using facts that are already public. We have carried out a balancing test (a Legitimate Interest Assessment) and apply safeguards: alerts contain only factual, already-public information; we store the minimum data necessary; we never tell a watched person who is watching them; and monitoring is capped per user to prevent large-scale profiling.
If you are watched — your rights
You have the right to object to being monitored (Article 21). If you object, we will stop monitoring you: we remove existing watches on you, delete the related alert history, and block future watches and alerts. We honour such requests on light identity verification, because objecting only reduces the processing of your data. You also have the right to erasure (Article 17) and to access your data; because these expose or restore information, we apply a stronger identity check before acting. To exercise any of these rights, contact us at [email protected].
Retention
Alert history is automatically deleted after 12 months.
15. Contact Us
For questions about this privacy policy or to exercise your rights, contact us:
- Email: [email protected]
- Company: Dvinge ApS
- CVR: 42992135
- Country: Denmark
You also have the right to file a complaint with the Danish Data Protection Agency at datatilsynet.dk
This privacy policy is in compliance with GDPR (General Data Protection Regulation) and Danish data protection legislation. Virkly is operated by Dvinge ApS, a Danish company committed to protecting your privacy and handling your data responsibly.