Privacy policy

Hawkra is built for people who read privacy policies, so this one is written to be read: what we collect, where it goes, how long we keep it, and what we never do with it.

Effective October 20, 2026

No tracking
No analytics, no pixels, no fingerprinting. We do not watch what you do on the platform.
Encrypted at rest
Each workspace has its own AES-256-GCM key for credentials, notes, compliance responses, and files.
Never sold
Your data is yours. No advertising, no data brokers, no third-party monetization.

Who we are

Hawkra is a vulnerability management and penetration testing platform operated by ReconhawkLabs LLC, based in Richmond, Kentucky. This policy covers the cloud-hosted service at hawkra.io. If you run the self-hosted edition on your own infrastructure, your workspace data never reaches our servers and this policy does not apply to that deployment (see Self-hosted deployments below).

What we collect

Only what the platform needs to work. This is the complete list.

CategoryDataPurpose
AccountEmail address, display name, and password hash (Argon2; we never see or store your plaintext password). A record of the Terms of Service and privacy policy versions you accepted, with the time, IP address, and browser user-agent string of that acceptance.Signing in, managing your account, and proof of agreement
AuthenticationSession tokens in HTTP-only cookies. If you set up an authenticator app, an encrypted TOTP secret and hashed recovery codes. If you choose “Remember this device”, a hashed device-trust token.Keeping you signed in and verifying it is you
Workspace dataNetworks, assets, vulnerabilities, notes, credentials, files, compliance responses and evidence, and workspace chat messages.The platform itself. Credentials, notes, compliance responses, and files are encrypted with a key unique to the workspace.
BillingStripe customer ID, subscription status and plan, and self-hosted licence records (licence ID, expiry, Stripe payment reference). We never see or store your card number; Stripe handles that.Payment processing and licence issuance
Audit logsActions performed, the resources they touched, old and new values, IP address, and timestamps.Your workspace audit trail
Ask AIThe messages you send, the replies, and a summary of the workspace items you selected as context.The Ask AI feature
Usage metricsWorkspace and asset counts, storage used, and monthly counts of reports, OSINT calls, and AI messages.Enforcing plan limits

Legal basis for processing

Under the EU General Data Protection Regulation (GDPR), each processing activity needs a lawful basis. These are ours.

Processing activityLawful basis
Account creation and authenticationPerformance of a contract (Art. 6(1)(b)): necessary to provide the service you signed up for
Workspace data managementPerformance of a contract (Art. 6(1)(b)): core service delivery
Payment processing via StripePerformance of a contract (Art. 6(1)(b)): necessary to fulfil your subscription or licence
Ask AIPerformance of a contract (Art. 6(1)(b)): a feature of the platform that you choose to use
OSINT lookups (WHOIS, DNS, Shodan, Have I Been Pwned, GeoIP)Performance of a contract (Art. 6(1)(b)): on-demand lookups that you start
Transactional emails (verification, MFA codes, password reset)Performance of a contract (Art. 6(1)(b)): necessary service communications
Audit logging and Terms acceptance records (actions, IP addresses)Legitimate interest (Art. 6(1)(f)): security monitoring, fraud prevention, and evidence of agreement
Contact form processingLegitimate interest (Art. 6(1)(f)): responding to your inquiry

We do not rely on consent for any core service processing, so we will not ask you to consent to processing that is necessary to deliver the service. Where we rely on legitimate interest, we have weighed that interest against your rights.

What we do not collect

The part most privacy policies leave out.

No analytics
No Google Analytics, no Mixpanel, no Amplitude, no tracking pixels of any kind.
No fingerprinting
No browser or canvas fingerprinting and no advertising identifiers. Device trust for MFA uses a random token, not a device profile.
No tracking cookies
Every cookie we set is functional and required for secure operation. There are no third-party cookies.
No telemetry
No usage data is collected beyond the plan-limit counters listed above.
No device profiling
We do not collect browser or hardware details for profiling. The only records that include your IP address are workspace audit logs and your Terms of Service acceptance, which also stores the browser user-agent string sent with it.
No hardware access
Camera, microphone, and geolocation are disabled for the whole site through the HTTP Permissions-Policy header.

Cookies

Hawkra sets three functional cookies, all required for secure operation, and a fourth only if you opt in to “Remember this device” during multi-factor authentication. None are used for tracking.

hawkra_access

Your session token. HTTP-only (JavaScript cannot read it), Secure (HTTPS only), expires after 1 hour.

hawkra_refresh

Renews your session without re-entering your password. HTTP-only, Secure, expires after 7 days.

hawkra_csrf

Prevents cross-site request forgery. This is the only cookie readable by JavaScript, by design.

hawkra_mfa_device

Optional. Set only when you choose “Remember this device” during multi-factor authentication. Holds a random token (not device fingerprinting data) so that browser can skip the MFA challenge. HTTP-only, Secure, expires at the end of the device-trust period, which is 7 days unless we change the setting.

There is no cookie consent banner because every cookie is functional.

Third-party services

Some data leaves our servers when you start an action that needs an outside service. Separately, a background scheduler contacts public security intelligence sources to keep the Threat Dashboard current.

  • Stripe - When you subscribe or buy a self-hosted licence, we send your email address, account ID, and plan selection to Stripe to run the checkout. Stripe handles all card data directly; your payment details never pass through our servers.
  • AI provider - When you send an Ask AI message, your message and the workspace items you selected as context (assets, vulnerabilities, notes) are sent to our AI provider, currently Google Gemini, to generate the reply. Nothing is sent until you select items and send a message. Your account details, stored credentials, and other workspaces are never included.
  • OSINT lookups - When you run a lookup, the value you enter is sent to the service that answers it: Shodan for host lookups, Have I Been Pwned for breach and paste checks, ipgeolocation.io for GeoIP, the registry WHOIS server for the domain's top-level domain for WHOIS, and Google Public DNS for DNS records. These queries run only when you start them.
  • Vulnerability intelligence (background) - A background scheduler contacts public security intelligence sources to keep the Threat Dashboard current: the National Vulnerability Database (NVD) every 2 hours, the CISA Known Exploited Vulnerabilities catalog every 6 hours, FIRST EPSS scores daily, and MITRE ATT&CK weekly. No personal data is included in these requests.
  • Brave Search (background) - Once a day the scheduler queries Brave Search for security news used in the Threat Dashboard briefing. No personal data is included.

International data transfers

ReconhawkLabs LLC is based in the United States. If you use Hawkra from outside the US, your personal data is transferred to and processed in the United States.

For users in the European Economic Area (EEA), United Kingdom, or Switzerland, we rely on the following safeguards for these transfers:

  • Standard Contractual Clauses (SCCs) - We use the European Commission's 2021 Standard Contractual Clauses with our third-party processors so that your data receives an adequate level of protection when transferred outside the EEA.
  • Encryption as a supplementary measure - Sensitive data is encrypted with AES-256-GCM before storage. Even with access to the underlying infrastructure, encrypted data is unreadable without the workspace-specific keys.
  • Processor agreements - Third-party services that process personal data on our behalf (Stripe, our AI provider, OSINT providers) are bound by data processing agreements that include transfer safeguards.

Self-hosted deployments are not affected by this section. Your data stays on your own infrastructure in the region you choose.

How we protect your data

  • Per-workspace encryption - Every workspace has its own encryption key. Credentials, notes, compliance responses, and uploaded files are encrypted with AES-256-GCM before they reach the database or file storage, so workspaces are cryptographically isolated from each other.
  • Encryption in transit - All connections use TLS. HTTPS is enforced in production.
  • Password security - Passwords are hashed with Argon2 using OWASP-recommended parameters. Passwords must be at least 10 characters with 3 of 4 character classes, and are checked against a common-password blocklist.
  • Multi-factor authentication - MFA is required on hawkra.io. By default a one-time code is emailed to you at sign-in; you can add an authenticator app (TOTP) instead. Recovery codes are stored hashed and encrypted. If you choose “Remember this device”, a random token in a cookie lets that browser skip the challenge for the trust period.
  • Access control - Every API request checks workspace membership and role permissions. Four workspace roles (Owner, Editor, Remediation Analyst, Viewer) enforce least privilege.
  • Rate limiting - All endpoints are rate-limited to slow brute force and abuse. The counters live in memory only.
  • Security headers - Content Security Policy, X-Frame-Options, HSTS, Referrer-Policy, and Permissions-Policy headers are applied to every response.

Data retention

We keep data only as long as the purposes above require.

  • Account data - Kept while your account exists. Deleting your account permanently removes the account, your billing records, and every workspace you own, immediately; only audit log entries remain, as described below. Registrations that are never verified are removed after 24 hours.
  • Workspace data - Kept until the workspace is deleted. Deletion permanently removes all of its data, including encrypted fields and files, immediately.
  • Audit logs - Append-only. Entries are kept after the workspace or account they refer to is deleted, with the link to that workspace or account cleared. They still include the action, timestamp, and IP address.
  • Payment records - Stripe customer, subscription, and licence records are kept while your account exists and removed with it. Stripe retains payment data under its own policy.
  • Rate limiting data - Held in memory only while the service runs. Never written to a database.
  • Contact form submissions - Emailed to our contact address. Not stored in any database.

You can delete your account from your account settings. Deletion is permanent and immediate, so export anything you want to keep first.

Your rights

Wherever you are, you have the right to:

  • Access - Request a copy of all data we hold about you
  • Correction - Update or correct inaccurate information
  • Deletion - Delete your account yourself from account settings, or ask us to
  • Export - Download your asset and vulnerability data as CSV from inside the platform, no request needed
  • Objection - Object to specific processing of your data
  • Complaint - If you are in the EEA, lodge a complaint with your national data protection supervisory authority if you believe your data has been processed unlawfully

To exercise any of these rights, contact us at contact@reconhawklabs.com. We respond within 30 days.

Self-hosted deployments

If you run the self-hosted edition, your workspace data never passes through our servers. You control the database, file storage, encryption keys, and all configuration. You are the data controller, and this policy does not govern your deployment.

A self-hosted instance contacts hawkra.io in two cases only: when you issue or renew a licence from your hawkra.io account, and once at startup to check whether a newer release is available. The update check sends no workspace or account data.

Changes to this policy

When we update this policy we revise the effective date at the top and, for material changes, notify you at the email address on your account. We will not reduce your rights under this policy without your explicit consent.

Contact

Questions about this policy or how your data is handled:

ReconhawkLabs LLC

Richmond, Kentucky

contact@reconhawklabs.com