Privacy policy

Who is responsible for your data

The company below decides what happens to the personal data collected through this website. Under the Swiss Data Protection Act and the EU General Data Protection Regulation, that makes us the controller for it.

Company

Twin Pines GmbH

Address

Denter Ers 14
7403 Rhäzüns
Switzerland

Email

hello@quaryan.com

Our representative in the EU

We are based in Switzerland. Anyone in the European Union can raise anything in this policy with the representative below, as well as with us directly:

What this policy covers

This page covers both halves of Quaryan: this website, the pages you are reading now, and the Quaryan app at app.quaryan.com, which you sign in to. Where a section is about only one of them, it says which.

We do not sell personal data, and we pass it to nobody except the providers named further down, who handle it on our instructions.

When you open a page

Our hosting provider records every request to the server. That log is how we know the site is up, and how we find the cause when it is not. Each entry holds:

• the IP address the request came from
• the date and time it arrived
• the page or file asked for, and whether it was delivered
• the browser and operating system the request announced
• the page that linked you here, when your browser sends one

We do not use these logs to work out who anybody is, and we do not join them to anything else. The legal basis is our legitimate interest in running a site that stays up and is not under attack (Art. 6(1)(f) GDPR).

When you type your web address into the field

The field on the home page sends nothing to us. Submitting it opens the Quaryan app with what you typed in the address, and from there the sections about the app below apply. What you type is not stored on this website, and it never goes to analytics.

When you write to us

If you email us, we have your address, your message and anything attached to it. We use that to answer you and for nothing else — the basis is our legitimate interest in replying to people who write to us, or taking steps at your request before a contract (Art. 6(1)(b) and (f) GDPR). We keep the correspondence while the matter is open, and afterwards for as long as commercial and tax law require.

Analytics, and your choice

We would like to know which parts of this page get read and which buttons get pressed, because that is how the page gets better. We use Google Analytics 4 for it, offered in Europe by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.

None of it runs unless you say yes. Until then no Google script is loaded, no request goes to Google, and nothing is stored on your device. If you do agree, Google Analytics sets cookies that recognise your browser on a later visit, and records which pages you open, roughly where you are — worked out from a shortened IP address, not from a street — what kind of device and browser you use, and clicks on the buttons that lead to the app. It never receives your name, your email address, or the web address you typed into the field on the home page.

If an advertisement brought you here and you said yes, one more thing travels with you. The link that brought you carries an identifier the advertising platform issued for that one click, and it is passed to the app when you open it. If you later take out a paid plan, we report that purchase to Google Analytics against it — which is how we can tell, weeks later, which advertisement actually paid for a subscription rather than only which one was clicked. The identifier says nothing about you: it is the platform's own reference for a click it had already recorded. Decline, and it goes nowhere — nothing is kept, nothing is carried into the app, and a purchase is reported with nothing linking it to an advertisement or to your browser.

The legal basis is your consent (Art. 6(1)(a) GDPR, Art. 31(1) of the Swiss Data Protection Act, and § 25(1) TDDDG in Germany). You can take it back at any time, with the same single click the yes cost you — that stops any further collection, though it cannot undo what was collected while it stood.

What is stored on your device

Three things, all small, and only one of them needs no permission:

• Your language, and your answer to the banner. Kept in your browser's own storage rather than in a cookie, and sent nowhere. They are why this site does not guess your language again on every visit, and does not ask about analytics twice. This is the site doing what you asked of it, so it needs no consent.
• Google Analytics cookies, if you accepted them: _ga and _ga_ plus the measurement ID. They expire two years after your last visit, and they are what tells Google Analytics that two visits came from the same browser.
• Where you came from, if an advertisement brought you here and you accepted. The identifier the advertising platform issued for that click, kept in your browser's own storage so that it survives the pages in between, and passed to the app when you open it. It is what lets a subscription taken out weeks later be credited to the advertisement that earned it. Decline the banner and nothing of the kind is kept or passed on.

You can clear any of it at any time in your browser's settings — and declining the banner means the last two are never set in the first place.

When you open an account in the app

The app at app.quaryan.com is the part of Quaryan you sign in to. This section and the four after it are about it rather than about these pages.

To hold an account we store your email address, the name you give, the language you work in, whether you asked for our emails, and which plan you are on. Signing in itself is handled by Firebase Authentication, a Google service: if you use a password, Firebase holds it and we never see it. Paying is handled by Stripe — we see that an account is paid and until when, never your card.

We also store what you put into the app: the website or store listing each campaign is about, what you write about it, and what Quaryan works out from that — the summary, the audits, the marketing plan and the ad plan.

The basis is the contract between us: without this there is no account and nothing to show you (Art. 6(1)(b) GDPR).

When you sign in with Google

Beside the email and password fields, the app offers a Continue with Google button. Pressing it opens Google's own sign-in screen, and what happens there is between you and Google — no password of yours ever reaches us.

When you come back, Google tells us four things about you. This is the whole of the Google account data Quaryan receives:

• Your email address, and whether Google has confirmed it is yours.
• The name on your Google account.
• The profile picture on it — a link pointing at Google, not a copy of the image.
• The identifier Google files you under, which is a number rather than a name.

Those four do one job: create your Quaryan account the first time you press the button, recognise it as yours every time after that, show your name and picture in the app so you can see whose account is open, and let us write to you about it — support, receipts, security notices. They are used for nothing else. We do not sell them, we do not advertise to you with them, and we do not train any AI model on them. The basis is the contract between us (Art. 6(1)(b) GDPR).

What Quaryan reads from your Google Ads account

The app's search advertising page can connect to a Google Ads account you already have. Pressing Connect sends you to Google's own consent screen, and the access exists only if you grant it there — there is no key to paste, and your Google password does not reach us here either.

With that grant, and only for the account you pick, Quaryan reads:

• Which Google Ads accounts your login reaches — the account number, the name on it, its currency, and whether it is a manager or a test account. This is how the app can ask which one a campaign is about instead of guessing.
• What the account you picked has been doing over a recent window: impressions, clicks, cost, conversions and the value of those conversions.
• The campaigns inside it — their name, status and type — with the same figures for each.
• What the money went to inside them: keywords, ads, audiences and placements as they are written in your account, each with its own figures.
• The same figures by day, which is what the chart on the measurement page is drawn from.

That is the whole of what is read. Quaryan has no access to your Gmail, your Drive, your contacts or your Google profile beyond the four things in the section above, and has never asked for any of it.

What Quaryan does with your Google Ads data

It is shown back to you, and that is most of the answer. The figures fill the search advertising and measurement pages of your own account: what your advertising spent, what came back, and which keywords earned their place.

When you press Publish, and not before, Quaryan writes to the account you connected: the campaign, its daily budget, its dates, its keywords and match types, its targeting and its ad text, exactly as they stand on the screen you approved. Pressing publish again later updates that same campaign. Nothing else in your account is created, changed or spent.

We do not sell this data and we do not advertise to you with it. Writing is done by AI models we rent rather than own, so the material a plan is drafted from — these figures included — goes to the provider running the model and comes back as a draft; the next section names the two of them. It is not used to train, improve or develop any artificial intelligence model, ours or anybody else's: a model is run on it, never taught from it. Nobody here looks at an account's figures except where you ask us to in support, or where security or the law requires it, and the providers named below process it only to keep the service running.

Quaryan's use and transfer of information received from Google APIs to any other app adheres to the Google API Services User Data Policy, including the Limited Use requirements. That policy is at developers.google.com/terms/api-services-user-data-policy.

Who we share Google data with

Google asks that this be stated plainly, and the question deserves a plain answer. The Google data described in the sections above — what your Google account tells us when you sign in, and everything Quaryan reads from a connected Google Ads account — is shared, transferred and disclosed to three places, and to nobody else:

• Our hosting provider, named at the end of this section. It runs the servers and the database the app lives on, so everything stored — the email address, name and picture Google gives us, the figures read from Google Ads, the encrypted access tokens — sits on infrastructure it operates for us. It acts only on our instructions, under a data processing agreement, and makes no use of any of it for itself.
• Google itself. This data comes from Google and goes back to Google: Firebase Authentication handles the sign-in behind your account, every figure on the search advertising and measurement pages is read through the Google Ads interface, and the campaign you approved is written to your own account when you press Publish.
• The two providers whose AI models do the writing: OpenAI and Anthropic. Quaryan does not own the models that draft your summaries, audits, marketing plans and ad copy — it rents them. Drafting one sends the material it is written from to whichever of the two runs the model that task uses, and the draft comes back. For anything about your advertising, that material includes the figures read from your Google Ads account: what a campaign spent, what came back, which keywords carried it. It does not include who you are — the email address, name and picture from your Google account stay with us and go into no prompt. Both handle it on our instructions under a data processing agreement, keep it only briefly to check that their own systems are not being misused and then delete it, and do not train their models on it.

Nobody else receives it: not advertisers, not ad networks, not data brokers, not analytics providers — the analytics on this website never sees any of it — and not Stripe, which takes the payments and receives none of it. We do not sell it, rent it or trade it, and it is not used to train, improve or develop any artificial intelligence model — not ours, and not the models of the two providers above, which are paid to run on your data rather than to learn from it. The only exceptions: when you ask us to, such as when support looks at a campaign with you; when a law, a court or a supervisory authority obliges us to hand it over, or when we have to act on fraud, abuse or an attack; and, were the company ever sold or merged, the buyer would take on this policy unchanged and we would tell you before anything moved, in time for you to close your account.

Hosting provider

Render Services, Inc.

Address

San Francisco, California, United States

Taking the Google access back

Disconnect, on the same page that connected it, stops Quaryan reading the account there and then — and hands the grant back to Google in the same step, so the permission is gone at our end and at Google's.

You can also withdraw it from Google's side at any time, under Third-party apps & services in your Google account at myaccount.google.com/connections. That stops the access just as surely; the app then shows the connection as no longer working and offers to make it again.

Either way we delete the tokens Google issued us. Figures already fetched are deleted with the campaign they belong to, and all of it goes when you close your Quaryan account.

Those tokens sit encrypted on our servers, are never sent to your browser, and are used for nothing but the account you connected them to.

Who else handles data for us

Our hosting provider runs the servers that deliver these pages and, in doing so, processes the request logs described above on our behalf, under a data processing agreement:

If you accepted analytics, Google Ireland Limited processes the analytics data described above, likewise under a data processing agreement.

Hosting provider

Render Services, Inc.

Address

San Francisco, California, United States

Who handles the app's data for us

The app runs on the same hosting provider as this site, under the same data processing agreement. Four more companies are involved in it, and no others:

Google Ireland Limited runs the sign-in behind the app (Firebase Authentication) and provides the Google Ads interface the connections above read from, in both cases on our behalf. What Google does with your Google account and your Google Ads accounts as the company that operates them is Google's own affair, and its privacy policy at policies.google.com/privacy covers that side.

Stripe takes the payments. It acts for us rather than as the seller in its own right, so the subscription is bought from us — but the checkout is Stripe's own page and no card number ever reaches us. Stripe works out the VAT for your country and holds the billing address and any VAT number you enter; the invoice is issued in our name and rendered by Stripe, and none of it is stored here. What Stripe does with that data is covered by its own privacy notice, linked at its checkout.

OpenAI and Anthropic provide the models that write. A summary, an audit, a marketing plan, the text of an ad — each is drafted by a model at one of the two, from the material the work is about, which for advertising work includes the figures read from your connected Google Ads account. Both act on our behalf under a data processing agreement, and their terms for business use put the rest of it in writing: they do not train their models on what we send, and they keep it only briefly, to check that their systems are not being misused.

Data that leaves Switzerland and the EU

Our hosting provider and Google both belong to groups whose parent companies are in the United States, and OpenAI and Anthropic are American companies too, so some of this data can be processed there. Where it is, the transfer rests on the adequacy decisions for the EU-US and Swiss-US Data Privacy Framework, so far as a company is certified under it, and otherwise on the European Commission's standard contractual clauses, which we have in place with each of them.

That is the honest legal position rather than a promise: authorities in the United States have powers of access that European and Swiss law do not match. If that matters to you, declining analytics keeps your visit out of everything except the server logs.

The app is the same story. What Google tells us when you sign in, and everything read from a connected Google Ads account, sits with the same group and travels on the same two bases; the app's servers are with the same hosting provider as this site; and what goes to OpenAI or Anthropic to be drafted travels on the standard contractual clauses.

How long any of it is kept

• Server logs: a few weeks, then deleted or stripped of anything identifying.
• Email you send us: while the matter is open, then as long as commercial and tax law require.
• Analytics data: at most 14 months from your last visit, the shortest retention Google Analytics offers.
• Your answer to the cookie banner: until you change it, or clear your browser storage.
• Your account, and everything you put into the app: while the account exists. Close it and it is deleted, apart from what commercial and tax law require us to keep.
• What Google tells us when you sign in with Google: as long as that account, and deleted with it.
• The tokens that reach a connected Google Ads account: until you disconnect it, or until the account is closed.
• Figures read from Google Ads: while the campaign they belong to exists.
• What is sent to OpenAI or Anthropic so a model can draft something: kept by them only briefly, to check that their systems are not being misused, then deleted. The draft comes back to your account and goes when the campaign it belongs to goes.

Your rights

Whatever else is on this page, these are yours. Write to the address at the top and you get an answer within a month, free of charge:

• Access — what we hold about you, and where it came from.
• Correction — anything wrong, put right.
• Deletion — your data removed, unless the law requires us to keep it.
• Restriction and objection — processing paused, or stopped where it rests on our legitimate interest.
• Portability — a copy in a machine-readable form, where the GDPR gives you one.
• Withdrawing consent — for analytics, at any time, no reason needed.

You can also complain to a supervisory authority: in Switzerland the Federal Data Protection and Information Commissioner in Bern, and in the EU the data protection authority of the country you live or work in.

Security

This site is served over HTTPS, so what passes between your browser and the server is encrypted. It loads no fonts, no images and no scripts from other companies, which is the other half of why there is so little on this page to describe.

The app is served the same way, and the tokens that reach your advertising accounts are stored encrypted on our servers and never sent back to the browser.

Children

Quaryan is a tool for people running a business. This site is not aimed at children, and we do not knowingly collect anything about them.

Changes to this policy

When the site changes, this page changes with it. The date at the top is when it was last edited, and the version you are reading is the one that applies.