Skip to main content
CLAVIRA
QA engineerDelivery managerInstalledPricingSecurityCustomers
Customer login
CLAVIRA
QA engineerDelivery managerInstalledPricingSecurityCustomers
Customer login

Privacy Policy

Last updated: October 16, 2026

Introduction

At Clavira, we take your privacy seriously. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you visit our website or use our services.

Information We Collect

Personal Information

We may collect personal information that you provide directly to us, such as:

  • Name and contact information
  • Email address
  • Company name and job title
  • Phone number
  • Information provided in forms or correspondence

Automatically Collected Information

When you visit our website, we may automatically collect:

  • IP address and browser information
  • Device and operating system information
  • Pages visited and time spent on our site
  • Referring website information

How We Use Your Information

We use the information we collect to:

  • Provide and improve our QA and testing services
  • Respond to your inquiries and provide customer support
  • Send you updates about our services (with your consent)
  • Analyze website usage to improve user experience
  • Comply with legal obligations

Data Security

We implement appropriate technical and organizational security measures to protect your personal information against unauthorized access, alteration, disclosure, or destruction.

Data Retention

We retain your personal information only for as long as necessary to fulfill the purposes outlined in this privacy policy, unless a longer retention period is required by law.

Your Rights

Depending on your location, you may have the following rights regarding your personal information:

  • Access to your personal information
  • Correction of inaccurate information
  • Deletion of your information
  • Data portability
  • Opt-out of marketing communications

Cookies and Tracking

This site stores very little, and this section says exactly what. Updated 8 October 2026.

What we store in your browser

Necessary (always)

  • Your cookie choice — kept in your browser's local storage so we don't ask again. Nothing is sent to us.
  • Portal sign-in session — only if you sign in to the customer portal (clavira.dev/app): a session cookie that keeps you signed in, and the state needed to complete the sign-in securely. Deleted when the session ends or you sign out.

Analytics (only with your permission)

We use Vercel Analytics to count page views and a few named events — a call booked, the case study read — so we know which pages help. It is loaded only after you allow it in the banner or in cookie settings.

  • It sets no cookies and keeps no identifier that follows you across sites.
  • It records no personal data: no names, e-mails, or form contents.
  • Withdraw at any time in cookie settings; nothing further is counted.

What we do not use

No marketing or advertising cookies, no retargeting pixels, no cross-site tracking, no profiling, no preference cookies. If that ever changes, this page and the banner change first and your permission is asked again.

Managing your choice

  • The banner on your first visit — accept, reject, or choose.
  • Cookie settings — the link in the footer, at any time.
  • Your browser — clearing site data removes your choice; we ask again on the next visit.

GDPR

  • Analytics run only after your explicit permission; necessary storage needs none, as the law allows.
  • You can withdraw permission at any time, and ask what we hold about you or have it deleted — write to the address at the end of this page.

Data processed by your Jarred instance

This website stores almost nothing. A Jarred instance — the digital employee a customer runs — processes the data of the systems its owners connect it to. For that data the customer is the controller and Nsight sp. z o.o. is the processor, under a data processing agreement available on request.

What it processes

  • Messages in the chat channels its owners approved (and direct messages, if the owners allow them); names and e-mail addresses of workspace members, to address people and to recognise owners.
  • Tickets, comments, pull requests, code, CI logs and deployment records of the connected projects.
  • Screenshots and logs from test runs against the customer's test environments.
  • Audio of calls it is invited to. It joins only on a teammate's invitation, as a visible participant named Jarred, and the inviting teammate is responsible for telling the participants; recording starts when it joins and ends when it leaves. Audio is transcribed inside the instance (not sent to a transcription service); the audio segments and the transcript are kept on the instance as a source in the project memory until deleted on request or at offboarding. Voice in calls is off by default; enabling it uses a speech model (OpenAI) and requires the customer's recorded consent. Participants who object ask the inviting teammate to remove him from the call.
  • Access tokens, stored encrypted in the instance, never shown to the AI model.

Where, and for how long

Each customer has its own isolated instance and storage on servers we operate in the European Union (Hetzner, Germany), or in the customer's own cloud on request. Conversation state is kept for days, the project memory for the life of the contract, backups for 30 days. When a contract ends the instance is stopped and its storage deleted within 30 days, or handed to the customer first if they ask.

What our platform sees

Our operations telemetry carries counts, statuses and identifiers only — never ticket titles, code, messages or names of the customer's systems. Staff access to an instance is logged and reported in the customer's own weekly note.

International transfers

Instances and their storage are in the European Union. Some subprocessors process data outside the EU, chiefly in the United States (Anthropic, OpenAI when enabled, Slack, Microsoft, Vercel, Google); those transfers rely on the EU Standard Contractual Clauses or an adequacy decision, as provided in each subprocessor's terms. The data processing agreement lists the mechanism per subprocessor.

Subprocessors

  • Anthropic — the AI model, under the customer's own account (or ours, all-in); no training on customer data.
  • Slack and, where used, Microsoft (Teams) — the chat surface.
  • Hetzner Online GmbH (Germany) — hosting of the instances.
  • OpenAI — only when voice in calls is enabled, for speech; off by default.
  • Vercel — this website and the customer portal; Google — portal sign-in.

The customer's own connected services (issue tracker, repositories, CI, deployment tools) are not our subprocessors — the instance acts in them with the customer's authorisation. We notify customers before adding a subprocessor.

Children's Privacy

Our services are not directed to individuals under the age of 16. We do not knowingly collect personal information from children.

Changes to This Policy

We may update this privacy policy from time to time. We will notify you of any changes by posting the new privacy policy on this page and updating the "Last updated" date.

Contact Us

If you have any questions about this Privacy Policy or our privacy practices, please contact us at:

Clavira — a service of Nsight sp. z o.o., a limited liability company registered in Poland

Email: privacy@clavira.dev

Registered address: provided on request at the e-mail above.

Clavira

Clavira installs digital employees into software teams' processes — a QA engineer first. Made by Nsight sp. z o.o., Poland. Working with teams in Europe, the US and Australia.

Contact

Email

Built by certified QA leadership

ISO 9001 Lead Auditor
ISTQB Certified

© 2026 Nsight sp. z o.o. · Clavira. All rights reserved.

Privacy PolicyTermsCookie settings