UPDATED 2026-11-15
Privacy policy
Pre-launch documentation: the provider’s legal identity is incomplete. Public subscriptions remain closed; this page is not a completed offer to contract.
Contact and controller
- Provider and controller
- Pending completion before commercial launch
- Tax identification
- Pending completion before commercial launch
- Provider address
- Pending completion before commercial launch
Main contact, support and privacy requests: welcome@vulnaria.com.
What we process and why
Account email, display name, password hash, membership and permissions support account access, recovery and collaboration. Providing the required account data is necessary for these functions. The basis is the requested service and pre-contractual steps.
Declared products and versions, assessments, triage, assignees, notes and reports support your workspace. Do not enter passwords, tokens or unnecessary personal data. When a team provides other people’s data, its organisation determines the purposes; the processor agreement and instructions must be completed before commercial onboarding.
Security records, IP-derived rate-limit identifiers, session information and audit events protect access and investigate incidents, on the basis of the legitimate interest in securing the service. They are not used for advertising.
Contact messages are used to answer the request. Billing identifiers, subscription status and invoice data are used for the contract and applicable legal obligations when billing opens. Card entry is hosted by Stripe; Vulnaria does not store the full card number or security code.
Optional analytics
Only after consent, and when the integration is configured, PostHog Cloud EU measures visits, conversion and explicit feature events. Its EU storage is in Frankfurt. Product events exclude inventory, notes, searches, prompts, tokens and MCP content. Account identifiers are pseudonymous; they are not anonymous data.
Session replay and heatmaps are restricted to the public landing pages, with an initial 10% sample. Inputs, forms and video are blocked. The application is never recorded. You can reject or withdraw analytics without losing access. See the cookies policy.
Providers, assistants and transfers
We use contracted hosting and backup infrastructure, OVHcloud for the contact mailbox and Brevo for transactional email. Stripe will process payments when activated. PostHog is optional. The final processor list, hosting location and contractual safeguards must be completed before public onboarding; an EU analytics region does not by itself exclude international access or transfers.
Connecting an MCP assistant shares the information allowed by your authorisation with the chosen client. Its provider applies its own terms and privacy policy. Review them and grant only the permissions you need. You can revoke the connection in Vulnaria.
X and LinkedIn links are plain external links, not embedded widgets. Those services receive your visit when you open them and apply their own policies. Social publication content uses public vulnerability information, not customer workspaces.
Retention and your rights
Workspace data remains while needed for the requested service. You may request account closure, export or deletion at welcome@vulnaria.com. Legal retention and proportionate incident handling may require restricted retention. Encrypted external backups keep up to 14 daily and four older weekly recovery points; the server keeps three recent copies and one older point. Storage caps apply. A deleted record may remain in a restricted backup until rotation. No fixed analytics retention is claimed until the project is configured and verified.
You may request access, rectification, erasure, restriction, portability or object where applicable, and withdraw consent. We may request proportionate identity verification. You may complain to the Spanish Data Protection Agency (AEPD). Risk scoring supports an analyst’s decision; it does not make legal or similarly significant decisions about people.