Privacy statement

This statement explains what personal data the Querly website (getquerly.com) processes, why, who else receives it, how long we keep it and what your rights are. It covers the website, the call replay, the early-access list, subscriptions and signing in to the app. When a business uses the Querly desktop app in its calls, it decides what happens to that call data and we process it on its behalf; that is set out in our Data Processing Agreement, not here.

Who is responsible?

L&T Studio V.O.F. (vennootschap onder firma, a Dutch general partnership), established in Castricum, the Netherlands, registered with the Dutch Chamber of Commerce (KvK) under number 98045075, is the controller for the processing described here. For anything about your data, email teun@getquerly.com; our postal address is on our contact page.

In short

• We don't use analytics, advertising or tracking cookies, and we don't sell or rent personal data.
• If you join the early-access list, we keep your email address to send your invite, for at most 24 months.
• If your business subscribes, we keep your company and billing details for the subscription and, as Dutch tax law requires, seven years after.
• If you replay a call, the transcript is never saved to disk. It stays in our server's memory and is cleared at the latest 10 minutes after the replay ends.
• To run the replay, text is sent to AI providers in the United States. They are listed below, with what each one receives.

The early-access list

What we collect: your email address, what you write under "What calls do you run?" (optional), and the time you signed up.

Why: to send you an invite when you can try Querly, and to reply if you write to us. We send one confirmation email when you sign up. We don't send newsletters or marketing to this list, and we don't combine it with other data.

Legal basis: your consent (Article 6(1)(a) GDPR). You can withdraw it at any time by replying to our email or writing to teun@getquerly.com; we then delete your sign-up.

Where it is kept: in a file on our server, hosted by Hostinger in Germany. A copy of each sign-up is also emailed to our own mailbox, which is hosted by Hostinger as well. Emails are sent through Hostinger's mail servers.

How long: until you ask us to remove it, and at most 24 months after you signed up. The server deletes older sign-ups automatically, and we delete the email we received about a sign-up from our mailbox when the sign-up itself is deleted. A daily backup of our server is kept for 30 days, so a deleted sign-up disappears from the backups within 30 days as well.

The call replay

When you replay a call, you paste a transcript, say which speakers are on your side, and write the goal of the call and optionally a line about the client. The transcript contains the words and usually the names of the people in that call.

What happens to it:

1. Our server reads the transcript and keeps it in memory only. It is never written to disk or to a log.
2. To suggest questions and write the summary, the transcript text, the speaker names, your goal and your line about the client are sent through OpenRouter to DeepInfra, which runs the language model.
3. To write the briefing, only your goal, your line about the client, the number of speakers and the language are sent to Anthropic. The transcript is not.
4. The results are shown in your browser.

How long we keep it: a transcript you paste but don't replay is cleared from memory within about 30 minutes. Once the replay starts, the pasted transcript is cleared, and the replay's results are cleared from memory at the latest 10 minutes after the replay ends. If you close the page while the replay is still running, it stops within about a minute and is cleared straight away. Nothing from the replay is kept after that.

What the AI providers do with it:

• DeepInfra (Deep Infra Inc., United States) keeps inputs in memory only while processing them, deletes them when the answer is sent, and doesn't use them for training (DeepInfra data privacy). We have set the replay to use DeepInfra only, with no fallback to other hosts.
• OpenRouter (United States) passes the request on to DeepInfra. It does not retain prompts unless the account owner opts in to prompt logging (OpenRouter zero data retention). We have not opted in, and our account allows no workspace to opt in.
• Anthropic (United States) deletes API inputs and outputs within 30 days and doesn't use them for training. It can keep them longer if a request is flagged for violating its usage policy, or where the law requires (Anthropic privacy center).

Legal basis: our legitimate interest, and yours, in showing you what Querly would have suggested in your own call, at your request (Article 6(1)(f) GDPR). We process the transcript for nothing else.

Your responsibility for the people in the call: the transcript is personal data of the other people in the call too. Only paste a call you are allowed to share, and leave out special categories of personal data, such as health information. Don't use the replay if you're not sure.

Customers and payments

When your business subscribes, we process the details of the subscription and of the person who arranges it.

What we collect: your company name, address and VAT number, the work email you give us, the plan you choose, extra hours you buy, when and which versions of our Terms of Service and Data Processing Agreement you accepted, and which version of this statement was shown to you. We don't receive your card or bank details: you enter those with Stripe.

Why and on what basis: to enter into and perform the contract with your business (Article 6(1)(b) GDPR), to check that you are a business and charge VAT correctly, and to keep the invoices and records Dutch tax law requires (Article 6(1)(c) GDPR).

VAT check: for customers in the EU, we check the VAT number with VIES, the European Commission's VAT register, before you pay. The number is sent to VIES; VIES tells us whether it is valid and which company it belongs to.

Payments: payments, invoices and the billing portal are handled by Stripe (Stripe Payments Europe, Limited, Ireland). Stripe processes payment details as a controller for its own obligations, such as fraud prevention and financial regulation, under its own privacy policy.

Where it is kept: at Stripe, and a record of each subscription (company, email, country, plan, status) on our server, hosted by Hostinger in Germany. We receive an email about each new subscription, purchase of extra hours, cancellation and failed payment.

How long: for as long as the subscription runs, and afterwards for seven years, because Dutch law requires us to keep our administration, invoices included, for that long (Article 52 of the General Tax Act, Algemene wet inzake rijksbelastingen). After that we delete it.

Signing in to the app

What we collect: the work email you sign in with, the sign-in code we email you, a name for each device you sign in on (your computer's network name, which often contains your own name), and a random token per device. Of the code and the token we store only a hash. While you use the app, our server records per request the device, the kind of request, the model, whether it worked and what it cost, and per call when it started and ended and how many minutes it counted. It never stores what is said in a call.

Why and on what basis: to let only your business's subscription use the app, to count the call hours of your plan, and to stop misuse such as a leaked token, as part of the contract with your business (Article 6(1)(b) GDPR) and our legitimate interest in preventing misuse (Article 6(1)(f) GDPR).

Where it is kept: on our server, hosted by Hostinger in Germany. The sign-in code is sent through Hostinger's mail servers.

How long: a sign-in code works for 10 minutes and is deleted within an hour after that. A device stays signed in until you sign it out, until a third device signs in, or until the subscription ends; it is deleted 30 days after that. The record per request is kept 90 days, and the record per call 13 months, because the hours of a period and extra hours (valid for 12 months) are counted from it. Our server's daily backups are kept for 30 days, so deleted records disappear from them within 30 days as well.

Security and preventing abuse

To stop the replay, the forms and signing in to the app from being misused, our servers count requests per IP address, and for sign-in codes also per email address. These are kept in memory only, never written to disk, and forgotten within about an hour. Our reverse proxy keeps no access logs, and our error logs don't contain email addresses, IP addresses or what you paste. Our hosting provider may process connection data to run and protect its network. The legal basis is our legitimate interest in keeping the site secure and available (Article 6(1)(f) GDPR).

Cookies and local storage

The website sets no cookies for visitors: no analytics, advertising or third-party cookies. Fonts and images are served from our own server, so your visit is not shared with font or image services.

• If you paste a transcript on the home page, it is held in your browser's session storage until the replay page opens it, and removed from there as soon as it is read.
• The site's own admin area uses one strictly necessary sign-in cookie for the site's editors. It is never set for visitors.

Because this storage is strictly necessary for what you ask for, it needs no consent.

Emails you send us

If you email us, we use your message and address to answer you, and keep the correspondence as long as it is useful for that conversation, and no longer than two years after it ends, unless the law requires otherwise.

Who receives personal data

We share personal data only with the service providers that run the site for us, as described above:

• Hostinger International Ltd. (Cyprus), hosting of our server in Germany, and our email.
• OpenRouter (United States), routing of replay requests.
• Deep Infra Inc. (United States), running the language model for the replay.
• Anthropic (United States), writing the replay briefing.
• Stripe Payments Europe, Limited (Ireland), payments, invoices and the billing portal, for subscribers. Stripe also acts as a controller for its own obligations.
• The European Commission (VIES), checking EU VAT numbers of subscribers.

We don't give personal data to anyone else unless the law requires us to.

Transfers outside the EU

OpenRouter, DeepInfra and Anthropic are in the United States. Anthropic's commercial terms include its data processing addendum with the European Commission's standard contractual clauses. For OpenRouter, which passes replay requests on to DeepInfra, we rely on the standard contractual clauses in OpenRouter's data processing agreement, which is part of its terms of service.

Do you have to give us your data?

No. But without an email address we can't send your invite or a sign-in code, and without your company, address and VAT number we can't sell you a subscription.

Your rights

You have the right to access your personal data, have it corrected or deleted, restrict or object to its processing, receive it in a portable format, and withdraw your consent at any time. Email teun@getquerly.com; we reply within one month. We may ask you to confirm your identity first.

Your right to object. Where we rely on our legitimate interest (the replay, and security and preventing misuse), you can object at any time, on grounds relating to your situation. Email us and we stop, unless we have compelling legitimate grounds that override your interests.

If you think we handle your data wrongly, please tell us. You also have the right to lodge a complaint with the Dutch Data Protection Authority, the Autoriteit Persoonsgegevens.

Automated decisions

We don't make decisions about you that are based only on automated processing and have legal or similarly significant effects. The questions the replay suggests are suggestions for you to use or ignore.

Changes

We update this statement when what we do with personal data changes. The date at the top shows the latest version.