AL'S-OPS LLC

Privacy policy

Last updated: November 5, 2026

This policy describes how AL'S-OPS LLC ("we", "us", "our") collects, uses, and protects information when you use Vigilhold and related services (collectively, the "Service").

1. Information we collect

Account information. When you register, we collect your email address, username, and password hash. For paid plans, billing is processed by Stripe — we store only your plan tier and subscription status, not payment card numbers.

Server telemetry. Agents installed on your servers transmit the following to the Service for the purpose of threat detection and alerting: CPU, memory, disk and network metrics; process lists with command lines; listening ports and connections, with outbound destinations as fingerprints made on your server, except your own servers, addresses on public threat lists and a reverse shell's destination; login events with usernames and source addresses; new lines from your server's authentication, system and kernel logs, and system error messages; the text of certain system configuration files (SSH, sudo, cron, /etc/hosts, /etc/passwd and nginx site settings) with values that look secret blanked; installed packages, services and containers; and hashes, paths and change events for monitored files. This data belongs to you. Every row is tagged with its organization and every query is scoped to it.

Security events. The Service stores alerts, audit logs, and forensic artifacts generated from your servers. These records are stored for the retention period defined by your plan and deleted at cancellation (see §4).

Usage data. We collect pseudonymised product usage metrics (feature interactions, error counts) to improve the Service. We do not use this data to identify individual users or reconstruct server activity.

Slack. If you connect Slack with Add to Slack, we store the webhook address Slack issues for the channel you pick (encrypted), plus the channel and workspace names and IDs. If you link your Slack account so you can approve actions from Slack, we store your Slack user ID and display name with your Vigilhold account. Vigilhold only posts to the channel you picked; it cannot read messages, files or members in your workspace. Removing the app from Slack turns the connection off, and you can delete it and any linked accounts in Settings → Integrations.

Communications. If you contact us by email or through the dashboard, we retain those communications to resolve your request.

2. How we use your information

We use the information we collect to:

We do not sell your data to third parties. We do not use your server telemetry or security event data to train machine learning models for use outside your org.

3. How we share your information

We share your information only in the following circumstances:

Service providers. We use the sub-processors below to operate the Service. Each is contractually bound to process data only on our instructions and only for the purpose listed.

Sub-processorPurposeData processed
ContaboServer hosting for backend nodesAll Service data, processed and briefly cached (encrypted in transit)
CloudflareDatabase (D1), edge routing, CDN, DDoS protection, shard directory, sending our emailsAll Service data in the database (encrypted at rest), request metadata, cached API responses (org-scoped), agent connection routing, and the emails we send you (address, subject, content)
StripePayment processing and billingBilling contact info, payment method (Stripe-hosted — never touches our servers), subscription status
AnthropicPlain-English explanations of Cortex plans, write-ups of incident cases, and natural-language search, when these AI features are on (the Service works without them)What each explanation needs: server hostnames, process names, IDs, command lines and process trees, IP addresses and ports, file paths and usernames; for incident cases also short excerpts of the logs, network connections and configuration collected for that case; for search, the matching alerts and audit-log entries. Never vault contents or terminal recordings. Sent through Anthropic's commercial API, under terms that do not allow training models on it.
ApplePush notifications to the Vigilhold iOS appYour device's push token and each notification's title and text (server name and alert summary)
Browser push services (Google, Mozilla, Apple, Microsoft)Browser notifications you turn onEach notification, encrypted so the push service cannot read it, and your browser's push address

This list may change as we add or replace vendors. Material changes are reflected here with an updated revision date; enterprise customers with a signed DPA are notified per that agreement's terms.

IP addresses. We look up the country and network of IP addresses (attackers' and your own sign-ins) on our own servers, in DB-IP's databases. No address is sent to an outside service for this. IP Geolocation by DB-IP.

Integrations you connect. When you connect a service such as Slack, PagerDuty or Jira, the alerts and approval requests you choose to send there (server name, alert type and details, requested action) are delivered to that service and handled under its own terms. If you add your own AbuseIPDB or VirusTotal key, the IP addresses of attackers we check are sent to that service.

Legal requirements. We may disclose information if required by law, court order, or to protect the rights, property, or safety of AL'S-OPS LLC, our users, or the public.

Business transfers. If AL'S-OPS LLC is acquired or merges with another entity, your information may be transferred as part of that transaction. We will notify you before your data becomes subject to a different privacy policy.

With your consent. We will share information in other ways only with your explicit consent.

4. Data retention

Server telemetry and alert history are retained for the period defined by your plan:

PlanMetricsAlerts & audit logs
Developer7 daysAlerts 90 days, audit log 1 year
Business7 days, or up to 90 days if your admin sets itAlerts 90 days, audit log 1 year, or up to 1 and 2 years if your admin sets it
Enterprise7 days, or up to 1 year if your admin sets itAlerts 90 days, audit log 1 year, or up to 5 years if your admin sets it

After account cancellation, or (from 17 November 2026) when a free trial ends without a subscription, you have 30 days to export your data, and the account owners are emailed a week before deletion. After 30 days, all org data — including server telemetry, alerts, audit logs, and stored agent tokens — is permanently deleted from our systems. Encrypted backups that still contain it expire within a further 30 days. We keep only a record that the organization was deleted, and Stripe keeps the invoices that tax law requires.

Forwarded log lines are kept for 30 days on every plan.

Account information (email, username) is deleted on request (see §6).

5. Security

We take the security of your data seriously:

To report a security vulnerability, email security@vigilhold.com. See our vulnerability disclosure policy.

6. Your rights

Depending on your jurisdiction, you may have the following rights regarding your personal data:

To exercise any of these rights, email privacy@vigilhold.com. We will respond within 30 days. We may need to verify your identity before acting on your request.

If you are located in the European Economic Area, you have the right to lodge a complaint with your local data protection authority.

7. Cookies and tracking

The Service uses two cookies: a session cookie (HttpOnly, Secure) and a CSRF protection cookie (Secure). In production both are SameSite=None.

Our public marketing pages (the home page, sign-up and sign-in, pricing, FAQ, Trust, and similar pages) can load Google's advertising tag (Google Ads) so we can count how many visitors who clicked one of our ads go on to sign up. It loads only after you choose "Allow ad cookies" in the notice those pages show; if you choose "No thanks" or do not answer, it does not load. When it loads, Google may set its own cookies and receives the page address, with only Google's ad-click and campaign parameters kept. The tag never loads in the dashboard, or on pages opened from links in our emails (password reset, invitations, email confirmation, Slack linking). Your choice is kept in this browser only.

Usage analytics described in §1 are collected server-side using pseudonymised identifiers.

8. Children

The Service is not directed at children under the age of 16. We do not knowingly collect personal data from children. If you believe we have collected data from a child, contact us at privacy@vigilhold.com and we will delete it promptly.

9. Changes to this policy

We may update this policy from time to time. When we make material changes, we will notify you by email (to the address on your account) at least 14 days before the changes take effect. The "Last updated" date at the top of this page reflects the most recent revision.

Continued use of the Service after the effective date of a revised policy constitutes acceptance of the changes.

10. Contact us

For privacy questions, data requests, or to exercise your rights:

AL'S-OPS LLC

971 S University Ave #1103, Provo, UT 84601, United States

Phone: (435) 281-6083

Email: privacy@vigilhold.com

Security disclosures: security@vigilhold.com

Trust and security →Permissions matrix →FAQ →privacy@vigilhold.com →