Privacy Policy
Last updated: March 24, 2026
Errova is an error monitoring and log monitoring service operated by Cynera Labs LLC, located in Arkansas, USA. This Privacy Policy explains how we collect, use, disclose, and protect personal information when you visit errova.com, use the Errova application, send data to Errova through our SDKs or APIs, receive emails or alerts from us, or otherwise interact with the service.
In this policy, personal information means information that identifies, relates to, describes, or can reasonably be linked to a person or household. In some jurisdictions this is called personal data.
We do not sell personal information, and we do not share personal information for cross-context behavioral advertising.
1. Who controls the data
Cynera Labs LLC is the controller for information we collect directly about our relationship with you, including website usage, account registration, authentication, billing, support, and similar business-administration data.
When an Errova customer sends telemetry, logs, stack traces, end-user identifiers, or other content to Errova for its own applications or systems, Errova generally processes that content on the customer's behalf as a processor or service provider. In those cases, the customer is responsible for deciding what data is sent to Errova and for providing any notices or obtaining any permissions required under applicable law.
If you use Errova through your employer, client, or another organization, that organization may manage your workspace, control account membership, configure integrations, and access telemetry or billing information associated with its workspace.
2. Information we collect
Account and workspace data
Information such as your email address, name, password hash, email-verification status, notification preferences, account memberships, organization and project names, roles, and workspace settings.
Billing and subscription data
Plan details, subscription status, Stripe customer and subscription identifiers, billing events, invoice-related records, and limited payment-method details such as card brand, last four digits, and expiration data. Full payment card numbers are handled by Stripe, not stored directly by Errova.
Customer-submitted telemetry and content
Data sent through Errova SDKs, APIs, or integrations, which may include titles, messages, stack traces, exception details, log data, tags, context, release and environment metadata, server names, timestamps, user IDs, user email addresses, user IP addresses, and similar operational data.
Security, session, and usage data
IP addresses, browser and device information, user-agent strings, session records, request logs, login attempts, rate-limit events, audit logs, abuse-prevention signals, and security-anomaly data used to protect the service.
Communications and integration data
Support requests, verification emails, password-reset emails, invitation emails, alert notifications, usage or billing notices, digest emails, and customer-configured webhook destinations such as Slack.
Website and app preference data
Theme preferences and limited browser storage used to remember interface settings, along with standard web server logs generated when you use our websites or app.
Waitlist and launch-interest data
When prelaunch signup is available, we collect the email address you submit to the waitlist form, related submission timestamps, and delivery status metadata used to deduplicate entries, retry failed notifications, and send launch updates.
Bot-protection data
When we protect signup, login, or recovery flows with services such as Cloudflare Turnstile, hCaptcha, or Google reCAPTCHA, those providers may receive device, browser, network, and interaction signals needed to distinguish humans from bots.
3. Sources of personal information
- Directly from you when you create an account, manage a workspace, or contact us.
- From your browser, device, and network when you access the website or application.
- From your applications, SDKs, APIs, and integrations when they send telemetry to Errova.
- From your organization's administrators, owners, or teammates when they invite or manage you in a workspace.
- From payment, email, security, and integration providers that support billing, communications, and abuse prevention.
- From records generated automatically by our systems as you use the service.
4. How we use personal information and our legal bases
Provide Errova and manage your account
Contract; steps taken before entering a contract
We use personal information to create accounts, authenticate users, run organizations and projects, receive and display telemetry, send service emails, and deliver the core error-monitoring and alerting features you request.
Process billing and manage subscriptions
Contract; legal obligations
We use billing data to administer plans, checkout sessions, customer portals, overage controls, invoices, payment events, and accounting records.
Secure the service and prevent abuse
Legitimate interests; legal obligations where applicable
We use security and usage data to rate-limit requests, detect spam and fraud, protect authentication flows, investigate suspicious activity, enforce quotas, maintain backups, and keep Errova reliable.
Support, troubleshoot, and improve Errova
Legitimate interests; contract
We use account, telemetry, and support information to answer questions, debug issues, diagnose incidents, improve product reliability, and maintain operational quality.
Operate prelaunch waitlists and release notifications
Consent; legitimate interests
We use waitlist signup information to prevent duplicate submissions, apply abuse controls, and send prelaunch, launch-access, or onboarding updates for Errova.
Comply with law and enforce our rights
Legal obligations; legitimate interests
We may process information to comply with tax, accounting, audit, legal, or law-enforcement requirements, and to establish, exercise, or defend legal claims.
Where we rely on legitimate interests, those interests generally include running a secure, reliable, privacy-conscious error-monitoring service, preventing abuse, maintaining the availability of the platform, and improving operational quality for our customers.
5. Customer-submitted telemetry and sensitive data
Errova is designed to process operational telemetry. Depending on how a customer configures its applications, that telemetry may contain personal information and, in some cases, sensitive information.
Customers control what their applications and SDKs send to Errova. For example, a customer may choose to include stack traces, log messages, request context, user IDs, email addresses, IP addresses, or custom metadata in event payloads.
Unless you have a clear legal basis and a genuine operational need, you should not send secrets, passwords, authentication tokens, full payment card data, government ID numbers, health information, or other special-category or highly sensitive data to Errova.
6. Cookies, local storage, and similar technologies
- The Errova application uses a necessary session cookie to keep authenticated users signed in and to maintain account context.
- The marketing site and application use limited browser storage to remember user interface preferences such as theme and layout settings.
- We keep standard server and request logs needed to run, secure, and troubleshoot the service.
- Authentication and recovery flows may load bot-protection services such as Cloudflare Turnstile, hCaptcha, or Google reCAPTCHA. If Google reCAPTCHA is used in a particular flow, it may set the necessary
_GRECAPTCHAcookie. - We do not currently use personal information collected through Errova for third-party advertising or cross-context behavioral advertising.
7. How we share personal information
- Service providers and subprocessors that help us host, secure, back up, operate, bill for, and communicate about Errova, such as infrastructure, database, storage, email-delivery, payment, and bot-protection vendors.
- Other authorized members, administrators, or account owners within your organization or workspace, who may be able to view telemetry, billing, members, and project settings.
- Customer-selected integrations and destinations, such as Slack webhook endpoints, when your organization enables them.
- Professional advisers, auditors, insurers, or acquirers where reasonably necessary for business operations, diligence, or a corporate transaction.
- Government authorities, courts, regulators, or law enforcement when required by law or when necessary to protect rights, safety, and the integrity of Errova.
We require service providers to process personal information only for authorized purposes and to protect it with appropriate safeguards. Our providers may change over time as we update the service.
8. International data transfers
Errova and our service providers may process personal information in countries other than the country where you live, including the United States and other countries where our vendors or infrastructure operate.
Where required by applicable law, we use appropriate safeguards for international transfers, such as contractual commitments or other recognized transfer mechanisms.
9. How long we keep information
- Account, workspace, and support data are kept while your account or business relationship remains active and thereafter only as long as reasonably necessary for security, dispute resolution, backup restoration, and compliance.
- Billing and tax records are kept for the periods required by applicable accounting, tax, audit, and financial-reporting laws.
- Session, request, abuse-prevention, and security logs are retained for as long as reasonably necessary to detect and investigate fraud, abuse, and service incidents.
- Customer-submitted telemetry is retained according to the retention settings associated with the relevant workspace or plan. On our current hosted pricing, advertised retention periods are 90, 180, or 365 days depending on plan and entitlements.
- Prelaunch waitlist records are retained for launch operations and abuse prevention until they are no longer needed for those purposes, after which they are deleted or de-identified, subject to legal retention obligations and backup rotation windows.
- Deleting a project stops new event ingestion, but historical telemetry may remain in active systems until the applicable retention period expires and may persist temporarily in backups until those backups are rotated or securely overwritten.
10. Your rights and choices
Depending on where you live, you may have some or all of the following rights:
- Access or know what personal information we hold about you.
- Correct inaccurate personal information.
- Request deletion of personal information, subject to exceptions allowed by law.
- Receive a copy of certain personal information in a portable format where required by law.
- Object to or request restriction of certain processing where applicable.
- Withdraw consent where we rely on consent, without affecting prior processing.
- Complain to a supervisory authority or regulator if you believe your rights have been violated.
We may need to verify your identity and, where permitted by law, the authority of an authorized agent before completing a request. If your information was submitted to Errova by one of our customers as part of telemetry or similar content, we may direct your request to that customer because it is usually the relevant controller for that data.
11. Additional California disclosures
During the preceding 12 months, depending on how you used Errova, we may have collected categories of personal information that correspond to California categories such as identifiers, customer records information, commercial information, internet or other electronic network activity information, professional or employment-related information, account credentials, and sensitive personal information contained in authentication data or customer-submitted telemetry.
We collect this information from the sources described above and disclose it to the categories of recipients described in this Privacy Policy, including service providers, payment providers, email and security vendors, integrations you enable, other authorized workspace members, and legal authorities when required.
We do not sell personal information, we do not share personal information for cross-context behavioral advertising, and we do not use sensitive personal information to infer characteristics about consumers. Because we do not sell or share personal information for those advertising purposes, Errova does not currently offer a separate sale or sharing opt-out mechanism for the service.
12. Automated processing and security tools
We use automated tools such as rate limiting, challenge-response bot protection, outage-detection logic, and security-anomaly detection to protect Errova and our users from spam, credential attacks, abuse, and malicious traffic.
We do not use personal information to make decisions about you that produce legal or similarly significant effects in the sense used by applicable data-protection law.
13. Children's privacy
Errova is not directed to children under 16, and we do not knowingly collect personal information from children under 16 for our own purposes. If you believe a child has provided personal information to us inappropriately, contact us and we will take appropriate steps to investigate and address the issue.
14. Security
We use technical and organizational measures designed to protect personal information, including access controls, authentication controls, service monitoring, bot protection, rate limiting, and transport security where supported. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.
15. Changes to this Privacy Policy
We may update this Privacy Policy from time to time to reflect product changes, legal requirements, or operational changes. When we do, we will post the updated version here and revise the "Last updated" date above. If a change is materially important, we may also provide additional notice through the service or by email where appropriate.
16. Contact us
Errova is operated by Cynera Labs LLC, located in Arkansas, USA. If you have privacy questions, want to exercise your rights, or need to contact us about this Privacy Policy, use the contact form available at cyneralabs.com.
If you are in the EEA, UK, or another jurisdiction with a data-protection regulator, you may also lodge a complaint with the regulator in the place where you live or work, or where you believe a violation occurred.