Privacy Policy

1. Who we are

Vigilia ("we", "us") is a monitoring service operated by Pablo Matias Perez Piskunow (sole trader, Spain) that watches web applications, explains problems in plain language, and generates fix prompts. This policy explains what data we handle and how. It is written to comply with the GDPR and CCPA.

Vigilia plays two distinct roles: we are the data controller for the information of people who create a Vigilia account, and a data processor for the technical telemetry our monitoring snippet collects from our customers' applications on their behalf.

2. Data we collect from you (account holders)

Account: email address and authentication data, handled by Firebase Authentication (Google), which Google runs in the United States. If you sign in with Google, we receive your email from Google. If you sign in with your email address alone, we email you sign-in links: we keep only a one-way fingerprint of each link, for up to 30 days, so that an old link can offer you a new one, and count sign-in attempts per address for a day to stop abuse.

Apps you register: app name, URL, and the builder tool you use — needed to monitor your app and tailor fix prompts.

How you found us: we record which link or code brought you to Vigilia (the site you came from, the campaign tags on the link such as utm_campaign, an ad click id from Google or Reddit, a creator's link or discount code, and the first page you opened), to pay referral commissions and to see which channels work. It is saved once, on your account, when you sign up, and never changed afterwards. If you also tell us how you heard about us (we ask once, just after you sign up), we store your answer with it.

Billing: payments are processed by Creem, our merchant of record. We never see or store your card details; we store only your Creem customer reference, your subscription's status and billing period, and any discount code it was bought with.

Emails we send: incident alerts and (if enabled) a weekly health report, delivered via Resend. You control both in Settings → Notifications.

3. Data our snippet collects from your app's visitors

When you install vigilia.js on your app, it collects technical error telemetry: error messages and stack traces, failed network request URLs and status codes, page URLs, browser/user-agent strings, basic performance metrics, and short "breadcrumb" descriptions of recent interactions (e.g. "clicked 'Pay now'").

Privacy by design: before anything leaves the visitor's browser, the snippet scrubs personal data patterns — email addresses, access tokens, API keys, card-like numbers, phone numbers, IP addresses — and strips query strings from URLs. The same scrubbing runs a second time on our servers. Errors from your backend (our server package, or OpenTelemetry) are scrubbed the same way on arrival, and bank account numbers (IBANs) are redacted there too. The snippet sets no cookies and does no cross-site tracking; it uses a random per-tab session identifier that is not linked to a person.

Retention: raw events are automatically deleted after ~30 days (database-level TTL). Aggregated error groups and incident diagnoses persist until you delete them or your account.

As the operator of your app, you remain the controller of your visitors' data. We recommend mentioning your use of an error-monitoring service in your own privacy policy.

4. Free tools and public pages

Launch check (no account needed): when you check an address at getvigilia.com/check, we fetch that public page, its own scripts and its security certificate, and keep the address and the resulting report for 30 days so the report's link keeps working. Secret keys found in a page are only ever stored and shown in masked form. We don't store who ran a check: your IP address is held in memory for a few minutes, only to limit how many checks one visitor can start.

Public status pages: if you publish one for your app, its uptime history and past downtime are visible to anyone with the link until you unpublish it. It never shows errors or anything about your visitors.

5. Connecting an AI assistant (MCP and API)

You can connect an AI assistant or coding agent, such as Claude, Cursor, Lovable or Bolt, to your Vigilia account through our MCP server or REST API, by signing in on a Vigilia page (OAuth) or with a token you create. Once connected, it can read your apps, their incidents and evidence (the scrubbed telemetry described in section 3), fix prompts and install instructions. With read & write access it can also mark incidents fixed, ignore or reopen them. You choose read only or read & write when you connect.

What we receive and keep: the requests the assistant makes to Vigilia's tools (for example, which incident to open), never your conversation with it. We store each access token only as a one-way hash, with its name, access level and creation date. For an OAuth connection we also keep the name the assistant registered under and the address it returns to after sign-in; sign-in codes are single-use and expire after 10 minutes. For rate limits we keep a daily count of requests per account, deleted after about a week.

After it leaves Vigilia: what Vigilia returns to your assistant is then handled by that assistant's provider, under your agreement with them. They are not our subprocessors, and we share nothing with them beyond what your assistant asks for.

Disconnecting: revoke any connection in Settings → API tokens; it stops working within a minute. Deleting your account deletes every token.

6. How we use data

To operate the service: detect errors and downtime, group similar errors, and notify you. To generate diagnoses, we send the (scrubbed) error context, and only that, to Anthropic's Claude API; Anthropic does not train models on this API data. Anthropic's API does not offer EU-only processing, so that context may be processed outside the EU. We do not sell data, run ads, or share data with third parties beyond the subprocessors listed below.

7. Subprocessors

The full list, with what each company does, what it handles and where, is at getvigilia.com/subprocessors. In short:

In the EU: Google Cloud (database and services, in Belgium and the Netherlands), where your account, your apps and the events they send are stored.

In the United States: Firebase Authentication (your sign-in email, and a password hash if you set one), Anthropic (AI diagnosis of scrubbed error context), Resend (the emails we send you).

Others: Firebase Hosting (serves our pages from Google's worldwide network), Creem (payments, as merchant of record, in the EU), Google Analytics (visit statistics for this website and the dashboard).

Transfers outside the EU rely on the EU Standard Contractual Clauses in each provider's data processing terms.

8. Your rights

Access / portability: Settings → Privacy → "Export my data" downloads everything we hold about your account as JSON.

Erasure: Settings → Privacy → "Delete account" immediately and permanently deletes your account, your apps, all collected events, error groups, incidents, and cancels your subscription.

Rectification / objection / complaints: email us at support@getvigilia.com. EU users may also lodge a complaint with their supervisory authority.

9. Cookies & local storage

The Vigilia dashboard uses Firebase Authentication's local storage to keep you signed in. This website and the dashboard use Google Analytics to count visits, which sets its own cookies (_ga); your IP address is shortened before it is stored. There are no advertising cookies. The monitoring snippet on your app sets no cookies at all.

Your choice: in the EU and EEA, the UK and Switzerland, Google Analytics stays off until you accept it; we tell where you are from your device's time zone. Elsewhere it is on unless you turn it off. Either way you can change your cookie choice at any time, here or from "Cookie settings" at the foot of any page, and declining deletes the Google Analytics cookies. We remember your answer for a year in a cookie of our own (vigilia-consent), and your day or night theme in another (vigilia-theme); neither identifies you.

Where you came from: if you open a link with campaign tags or an ad click id, and you have agreed to cookies where we ask first, we keep those tags in one cookie of our own (vigilia-attribution) for 30 days, so that if you sign up later we still know which link brought you. It is set once and not overwritten. It is only ever read when you sign up, and it is deleted when you decline cookies. Without it, the same tags still travel in the link when you go from this site to the dashboard.

Visit counts without cookies: this website also counts its own visits, for everyone and without asking, because it stores nothing on your device and cannot tell one visitor from another. For each page you open, your browser sends our own site the page, the campaign tags on the link you followed, the name of the site you came from, the country your device's time zone belongs to, your browser's language, the kind of device and the app the page opened in (worked out from your browser's user agent, which is not kept), how long the page was open and how far down you scrolled, and whether you went on to the dashboard, another page, a link elsewhere, or the launch check. An ad click id is never kept, only whose ad it was. The record holds no cookie, no identifier and no IP address (we use your address for a moment to stop abuse, and don't store it), and it is never connected to your account if you sign up. We keep these records for 90 days, only to see which pages and campaigns work.

10. Changes & contact

We'll update this page when our practices change and note the date above. Questions: support@getvigilia.com. Pablo Matias Perez Piskunow (sole trader, Spain), Carrer de Gorina 4, Sant Cugat del Vallès, Barcelona, Spain 08172.