Privacy Policy

QueryRev AI is a software service for organic search growth, made for businesses. It reads search and analytics data that you choose to connect, crawls websites that you are authorised to have crawled, and turns that data into recommendations and decisions for your team.

QueryRev AI is provided by STOA Global Corporation, a Delaware corporation with its business address at 169 Madison Ave STE 89775, New York, NY 10016, United States. STOA Global Corporation is responsible for the information described in this policy. You can reach us at business@queryrev.com.

Section 11 explains when we act for ourselves and when we act for a customer whose workspace holds your information.

• We use the data you connect only to provide and improve the QueryRev features you use. We may also improve QueryRev with aggregated, de-identified information that never includes data from Google APIs; a workspace can opt out by email (section 4).
• Access to Google Search Console and Google Analytics is read-only. QueryRev cannot change anything in your Google accounts.
• We do not sell your data, we do not use it for advertising, and we never use data from Google APIs, or anything derived from it, to train AI or machine-learning models.
• Each workspace's data is kept separate from every other workspace's.
• You can disconnect a data source at any time, and you can ask for its data to be deleted.

Account information

When you create an account we collect your name, your email address and a password. We never store your password itself, only a one-way hash of it. When you choose a new password, we check it against a public list of passwords known from data breaches, in a way that never sends your password, or anything from which it could be recovered, outside our systems.

Your name and email address are shown to the other members of the workspaces you belong to, and are used in the invitations you send.

If you sign in with Google, Google tells us your name, email address, profile picture and a stable account identifier, and gives us the tokens of that sign-in. We use these only to sign you in and to show your name and picture in QueryRev. We keep them with your account record and store the access and refresh tokens of that sign-in encrypted. None of them gives access to your Search Console or Google Analytics data.

We also keep the workspaces you belong to, your role in each, and the invitations you send or accept. Your light or dark appearance choice is stored only in a cookie on your device (section 15).

When you sign in, we record the IP address and the browser type (user agent) of that sign-in session, to keep your account secure. To stop password guessing, we also count recent sign-in and similar attempts by network address for a short time.

Data you connect from Google

When you connect Google Search Console or Google Analytics 4 to a workspace, you sign in with Google and grant QueryRev access. We ask only for these permissions:

• openid and email: to know which Google account you connected, so we can show it as "connected as".
• https://www.googleapis.com/auth/webmasters.readonly: read-only access to the Search Console properties of that account.
• https://www.googleapis.com/auth/analytics.readonly: read-only access to the Google Analytics properties of that account.

You can grant one of the two data permissions and not the other. QueryRev never asks for permission to change anything in Search Console or Google Analytics.

With this access we read, for the properties you attach to a site in QueryRev:

• From Search Console: performance data by date, page, search query, country and device (clicks, impressions and average position), for up to the 16 months Google keeps, and then day by day.
• From Google Analytics 4: organic search sessions, engaged sessions, key events (by event name) and reported revenue, by date, hostname, landing page and session source. These are aggregated reports; we do not receive records about individual visitors.
• The list of properties your Google account can see, so you can choose which one to attach.

Search queries and page addresses can contain personal information if people type it into a search or a site puts it in its addresses. Before we store a page address, we remove tracking parameters and values that look like personal data or secrets, such as email addresses.

Google gives us a refresh token, which lets QueryRev read this data on a schedule without asking you to sign in every day. How we protect it is described in section 7.

Website crawl data

If you confirm that you own a website or are authorised to have it crawled, our crawler (QueryRevBot) visits the public pages of that site. It obeys robots.txt and identifies itself with its own user agent. More about the crawler is at https://app.queryrev.com/bot.

The crawler records what search engines see: addresses, status codes, titles, meta descriptions, headings, canonical and robots instructions, structured data, links between pages, robots.txt files and sitemaps. Some pages are loaded in a browser so that content drawn by JavaScript is seen too. We store these fields, not a full copy of each page, and we keep a new version of a page only when it changed. A crawled page can contain personal information if the site publishes it (for example an author's name); we collect it only as part of the page as published.

Information about how you use QueryRev

We record actions taken in a workspace, such as connecting or disconnecting a source, authorising a crawl, inviting a member or deleting data, together with the member who took them. This audit trail is part of the product and protects you.

Our hosting providers receive the technical information any website receives, such as your IP address, browser type and the pages you request. When something breaks, we send an error report to our error-tracking service. We remove personal information from these reports before they leave our systems: they contain no user identifier, email address, cookies or the contents of your requests, and the service is set not to store IP addresses. It may record an approximate location, such as a country, derived from the connection that delivered the report.

We do not use advertising trackers, and the QueryRev application has no product analytics. On our website we use Google Analytics, described under "Website analytics" below.

The waitlist

On our website, queryrev.com, you can join a waitlist to hear when early access to QueryRev opens. We ask for your email address, and you may add your name, your company's website and whether you work in-house, at an agency or elsewhere. We record when you joined, when you confirmed, and which version of the consent text you saw.

We send one email to confirm the address. Your place counts only once you open the link in it and press the button on the linked page ("double opt-in"); until then we send nothing more. Every waitlist email carries a link to a page where a button removes your entry. To stop abuse of the form, we count recent attempts by network address and by email address, storing only a one-way hash of each, never the address itself.

The llms.txt Generator and Checker

On queryrev.com, the llms.txt Generator and Checker reads a website's public files for you. The web address you enter is sent to our server, which reads the public files the tool's page names from that website (its robots.txt, llms.txt and llms-full.txt; for the generator, also its sitemap and, when that sitemap lists other sitemaps, one of them, and some of its pages) and shows you the result. We do not store the address you enter or the result. To stop abuse of the tool, we count recent uses by network address and by the website checked, storing only a one-way keyed hash of each, never the address itself. When a check is refused, our logs record the reason and the host name of the website, never your network address.

Website analytics

On our website, queryrev.com, we use Google Analytics 4, a service of Google LLC, to count visits and to see which pages are useful. It is not used in the QueryRev application (app.queryrev.com), on its sign-in pages or in our emails.

Google Analytics records the pages you view on our website and how you move through them (for example, how far you scroll a page and links you follow to other websites), the page that sent you to us, the date and time, your browser, device type, screen size and language, and an approximate location, such as a country and city, that Google derives from your IP address. Google Analytics 4 does not log or store IP addresses. When analytics cookies are allowed, a random identifier kept in a cookie lets it recognise later visits from the same browser. We do not send Google Analytics your name, your email address, anything you type into our forms, or any user identifier, and we do not use it for advertising: advertising cookies, ad personalisation and Google signals are switched off.

In the European Economic Area, the United Kingdom and Switzerland, and wherever we cannot tell where you are, we ask for your consent with a banner, and our website loads nothing from Google Analytics until you choose "Accept". Elsewhere, Google Analytics runs with analytics cookies unless you turn them off. You can change your choice at any time with "Cookie Settings" at the bottom of every page of our website. If you choose "Reject", wherever you are, Google Analytics stops sending information from the page you are on, the analytics cookies it had set are removed, and our website no longer loads it. Section 15 lists the cookies and how long they last.

Google processes this information on our behalf, as our service provider.

Emails and messages to us

If you write to us, we keep the correspondence so we can answer and follow up.

Job applicants

When you apply for a role on queryrev.com/careers, STOA Global Corporation is responsible for your application (the controller); you can reach us at research@queryrev.com. We collect what you give us in the form: your name, your email address, a LinkedIn or portfolio link, your CV if you attach one (PDF or DOCX), your answers to the role's questions, which version of the consent text you agreed to and when, whether you joined the talent pool, and the website that sent you to the form, if any. Later we may add notes about your application and the stage it is at. To stop abuse of the form we count recent attempts by network address and by email address, storing only a one-way hash of each.

We use this information only to assess your application, to contact you about the role, which is independent contract work, and, if you join the talent pool, about other roles. The legal basis is your consent and the steps you ask us to take before a possible contract. Please do not send sensitive information, such as your date of birth, a photo, your health, religion, nationality, marital status, a government identity number or your salary history; we do not need it.

Only the people at QueryRev who hire read your application. Our hosting and email providers (section 6) process it for us; no software scores or ranks applicants, and no decision about you is made by a computer. Your application is stored in the United States, and a CV in a private file store that has no public address.

We keep an application for 12 months after a decision on it, then delete it with its CV. If you join the talent pool, which is a separate choice from applying, we keep it for up to 24 months from your application so we can write to you about other roles; you can leave the pool at any time. If you are offered a contract, your application moves to our contractor records and is deleted from the careers records. You can ask to see, correct or delete your application, or withdraw your consent, at any time by writing to research@queryrev.com; we answer within 30 days and tell you when it is deleted. Deleted applications leave our database backups within the period stated in section 9.

We use the information above to:

• provide the service: sign you in, keep your workspaces, read and store the data you connect, crawl authorised sites, and show the results;
• produce recommendations and decisions for your workspace from its own data;
• send email you need: account verification, password resets, invitations, and notices about your data sources (for example that a connection needs to be renewed);
• if you joined the waitlist, confirm your address and tell you when early access opens, and about nothing else;
• keep the service secure, prevent abuse, and find and fix errors;
• measure our own costs of serving each workspace;
• improve QueryRev using aggregated, de-identified information that does not include data received from Google APIs or anything derived from it, as described in our Terms of Service, unless your workspace has opted out;
• meet legal obligations, answer requests about your rights, and enforce our Terms of Service.

Apart from the waitlist emails you asked for, we do not send marketing email today. If we start, we will send it only where the law allows, and every message will include a way to unsubscribe.

We do not sell personal information, and we do not share it for cross-context behavioural advertising.

QueryRev AI's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

In particular, for data we receive through Google APIs (Search Console, Google Analytics and Google sign-in):

• We use it only to provide or improve the user-facing features of QueryRev that you use, such as your reports, page inventory, recommendations and decisions.
• We transfer it to others only as needed to provide or improve those features (for example to the service providers in section 6 that host or process it for us), to comply with applicable law, for security purposes, or as part of a merger, acquisition or sale of assets with your explicit prior consent.
• We do not sell it, and we do not use or transfer it for serving advertisements, including retargeting, personalised or interest-based advertising. We do not transfer it to data brokers or information resellers.
• We do not use it to determine creditworthiness or for lending purposes.
• We never use it, or anything derived from it, in any form, including aggregated or anonymised, to develop, improve or train any AI or machine-learning model, and we do not allow our service providers to do so.
• People at QueryRev do not read it unless you give us your permission for specific data (for example when you ask for support), it is necessary for security purposes such as investigating abuse, it is needed to comply with applicable law, or the data has been aggregated and anonymised and is used for our internal operations as applicable law allows.

We use the following companies to run QueryRev. Each processes data only on our instructions and only for the purpose stated.

• Neon (database hosting on Amazon Web Services, United States): stores all account, workspace, search, analytics and crawl data.
• Vercel (web application hosting, United States, with content delivered through Vercel's global network): runs the QueryRev website and application, and keeps the CVs of job applicants in a private file store in the United States.
• Railway (background worker hosting, United States): runs the scheduled jobs that read your Google data and crawl authorised sites.
• Fly.io (page rendering, United States): runs the browser that renders pages of authorised sites for our crawler. It receives the public web pages being rendered, and no account information, Google data, credentials or tokens.
• Inngest (workflow scheduling, United States): receives scheduling messages that contain no search, analytics or crawl data, email addresses or tokens.
• Resend (email delivery, sent from Japan): receives the recipient's name and address and the content of the emails we send, such as verification links, waitlist confirmations and source notices. Source notices name the site and the kind of source; they contain no search data.
• Sentry (error tracking, United States): receives the error reports described in section 3.
• Google LLC (website analytics, United States): runs Google Analytics on our website, queryrev.com, and receives the information about website visits described under "Website analytics" in section 3. It receives no account, workspace or payment information and no data from Google APIs.

Planned, not receiving data today: an AI model provider in the United States, described in section 8.

Apart from Google Analytics on our website, Google is not our service provider: at your direction we retrieve your own Search Console and Google Analytics data from Google, under your own relationship with Google.

We will update this list before a new provider starts to receive personal information. Customers with a Data Processing Addendum also receive the notice it describes. A list of our subprocessors is available on request at business@queryrev.com.

• Workspace isolation. Each workspace's data is isolated from every other workspace's, and access is enforced on every request, in the database as well as in the application. Agencies' client workspaces are separate in the same way.
• Protected tokens. For Search Console and Google Analytics connections we store only the long-lived refresh token, encrypted at rest with industry-standard encryption, with keys kept separate from the data, and access to them is strictly limited. Short-lived access tokens are never stored. The access and refresh tokens of Sign in with Google are also stored encrypted, and the sign-in details Google gives us are used only for signing you in. Tokens never appear in logs, error reports or web addresses.
• Encryption in transit and at rest. Connections to QueryRev and to our database are encrypted. Our database provider encrypts stored data at rest.
• Least privilege. Google access is read-only. Our systems and people get only the access they need to do their job.
• Staff access. People at QueryRev do not look at a workspace's data except with the customer's permission for a support request, to investigate a security issue or abuse, or to comply with the law.
• Account security. Passwords must be strong and are checked against known breaches; email addresses are verified; sign-in attempts are limited; sensitive actions ask you to have signed in recently; and a password reset signs out your other sessions.
• Audit trail. Connections, crawl authorisations, invitations, disconnections and deletions are recorded with who took them.

No system is perfectly secure. If we learn of a security incident that affects your personal information, we will tell you without undue delay, and we will notify authorities where the law requires. For customers, our Data Processing Addendum sets the notice for incidents that affect personal data we process for them: without undue delay and within 72 hours of our becoming aware of it.

QueryRev's AI-assisted features are not live yet: today no workspace data is sent to any AI provider.

When they launch, QueryRev will use AI models from an AI model provider in the United States, through that provider's commercial API, to explain data and to propose recommendations and decisions for your workspace. Before any data is sent, we will update this section and our list of service providers, including how long that provider keeps the data it receives. When an AI-assisted feature works on your workspace, we will send only the parts of that workspace's data the task needs, for example page content and structure from the crawl, search queries and their performance figures, or organic traffic figures. We will never send your password, Google tokens or payment details.

That provider will process this data on our behalf. Under its commercial terms, data sent through its API is not used to train its models.

Data we receive from Google APIs will be used by AI features only to provide features for the workspace that connected it. We never use it, or anything derived from it, in any form, including aggregated or anonymised, to train, fine-tune or improve any AI or machine-learning model, and we do not allow our service providers to do so.

AI output is an estimate. A person in your workspace decides what to act on.

• Account information: for as long as your account exists. When your account is deleted, we delete or irreversibly anonymise your account information within 30 days. We keep audit records, in anonymised form where they name you, and other information where the law requires or allows us to keep it.
• Sign-in session records (including the IP address and browser type of the session): until you sign out of that session; a session you do not sign out of is deleted 30 days after it expires, and every session ends no later than 90 days after sign-in. All of them are deleted when your account is deleted. Counts of sign-in attempts by network address are kept for no more than a few hours, and verification and password reset links are deleted within about an hour after they expire.
• Waitlist entries: until you remove your entry through the link in any waitlist email or ask us to delete it, and in any case 24 months after our last contact with you. An entry that was never confirmed is deleted 30 days after its confirmation email. Counts of waitlist attempts are kept for about two days.
• Counts of llms.txt Generator and Checker uses: no period they count is longer than a day, and each count is deleted within a few hours after its period ends.
• Job applications (including a CV): 12 months after a decision on the application, or up to 24 months from the application for people who joined the talent pool, or sooner when you ask (see "Job applicants" in section 3). Counts of application attempts are kept for about two days.
• Workspace invitations (including the invitee's email address): until they are accepted, withdrawn or expire; an invitation that expires unused is deleted 90 days after it expires.
• Search Console and Google Analytics data: for as long as the source is connected, and after you disconnect it unless you ask for it to be deleted (see section 10). History older than what Google itself keeps is part of the value of the service, so we do not delete it on a timer.
• Crawl data: for as long as the site's crawl source exists in the workspace, until you delete it.
• Google refresh tokens of data connections: deleted promptly, normally within minutes, once no connected source in the workspace uses that connection any more.
• Audit records, job records and cost records: kept for the life of the workspace. They record who did what and when, and contain no search or analytics data.
• Customer data after a subscription ends: kept for 30 days so the customer can export it or come back, then deleted, as our Terms of Service describe.
• Error reports: kept by our error-tracking provider for up to 90 days.
• Website analytics: Google Analytics keeps the records of visits linked to a cookie identifier for 2 months; after that, only aggregated reports remain. Your cookie choice is kept in your browser for six months.
• Backups: our database provider keeps restore points for a limited period, no more than 30 days, after which deleted data is gone from backups too. We do not restore deleted data from backups except to recover from a disaster.

• Disconnect a data source. In Integrations, a workspace administrator can disconnect any source at any time. Once no other source in the workspace uses the same Google connection, its stored refresh token is deleted promptly, normally within minutes. If no other QueryRev connection uses the same Google account, we also ask Google to revoke QueryRev's access.
• Delete a source's data. When you disconnect a source you can choose to delete its data. Deletion happens 24 hours later, so a mistake can be undone; during those 24 hours an administrator can press Undo. After that, the source's search, analytics or crawl data is removed. The audit record that the deletion happened remains.
• Revoke access at Google. You can also remove QueryRev's access yourself at any time at https://myaccount.google.com/permissions. QueryRev then stops reading your data and shows the source as needing to be reconnected.
• Stop the crawler. A site owner can block or slow QueryRevBot in robots.txt, as described at https://app.queryrev.com/bot, or write to bot@queryrev.com.
• Opt out of improvement data. A workspace administrator can opt the workspace out of aggregated improvement data by writing to business@queryrev.com.
• Delete your account or workspace. Write to business@queryrev.com from the address on your account. Within 30 days we will delete the data, or irreversibly anonymise it, keeping audit records as the law allows. Self-service deletion in the product is planned; until it is available, deletion is done on request.
• Leave the waitlist. Use the remove link in any waitlist email, or write to business@queryrev.com; we delete your entry.
• Access, correct or export your information. Write to business@queryrev.com. Corrections, including a change of name, and exports are done on request, within the response times in section 11.

To use any of the rights below, write to business@queryrev.com. We may need to confirm your identity first; if you have an account, we do this by matching your request to the email address on it. We will not discriminate against you for using your rights.

We acknowledge requests promptly. We respond within one month if you are in the European Economic Area, the United Kingdom or Switzerland, and within 45 days under US state privacy laws; either period may be extended where the law allows (by up to two more months, or 45 more days), and we will tell you if it is. Everyone else receives a response within 30 days.

Who is responsible for your information

For your account information and for how we run QueryRev, STOA Global Corporation decides how your information is used (in European terms, we are the controller). For data that a customer puts into or connects to its workspace, such as Search Console, Google Analytics and crawl data, the customer decides, and we process that data on its behalf as its processor or service provider, under our Data Processing Addendum. If your question is about data in a workspace, please contact that customer first; we will promptly forward requests we receive to it and help it answer.

If you are in the European Economic Area, the United Kingdom or Switzerland

We process personal information on these legal bases:

• Providing the service to you and to the organisation you work for: necessary for the contract with you, or, where the contract is with your organisation, in our and that organisation's legitimate interests.
• Security, preventing abuse and fixing errors: our legitimate interests, and our legal duty to protect personal information.
• Billing and accounting records, once paid plans are available: necessary for the contract and to meet legal obligations, such as tax law.
• Improving QueryRev with aggregated, de-identified information: our legitimate interest in improving the service. It never includes data received from Google APIs, and a workspace can opt out as described in our Terms of Service.
• Website analytics: your consent, which you can withdraw at any time with "Cookie Settings" on our website.
• Product news, if we send it: only with your consent, or where the law allows us to write to existing business customers, always with a way to unsubscribe.
• Answering requests and legal claims: to meet legal obligations, and our legitimate interests.

Where we rely on legitimate interests, you can ask us for information about the balancing test we carried out.

You have the right to access your personal information, to have it corrected or erased, to restrict or object to its processing, and to data portability. Where we rely on consent, you can withdraw it at any time without affecting earlier processing. You may complain to the data protection authority where you live or work, to the Information Commissioner's Office in the United Kingdom, or to the Federal Data Protection and Information Commissioner in Switzerland. We would appreciate the chance to address your concern first.

QueryRev does not make decisions about individuals that have legal or similarly significant effects on them. Its recommendations concern websites and search performance.

Section 14 explains how we protect transfers of your information outside your country.

If you are in the United States

Some US state laws, such as the California Consumer Privacy Act, give residents rights over their personal information. Many of these laws apply only to businesses above size thresholds, and several do not cover people acting in a business role. We may not meet those thresholds today, but we follow the practices below for everyone.

Depending on the state where you live, you may have the right to know what personal information we hold about you and how we use it, to get a copy of it, to have it corrected or deleted, and to opt out of its sale, its sharing for cross-context behavioural advertising, targeted advertising and certain profiling.

What we do not do. We do not sell personal information, we do not share it for cross-context behavioural advertising, we do not use it for targeted advertising, and we do not use it for profiling that produces legal or similarly significant effects. We do not knowingly collect personal information of anyone under 16. We do not collect sensitive personal information as defined in California law, other than account log-in credentials, which we use only to sign you in and keep your account secure.

Categories (California). In the past 12 months we have collected these categories of personal information: identifiers (name, email address, Google account identifier, IP address); professional information (your organisation and your role in a workspace); internet or other electronic network activity (actions in the service, pages viewed on our website, browser type, error reports); and account log-in credentials. Sources are you, your organisation, Google when you sign in or connect a source, and public web pages of sites your workspace authorises us to crawl. We use them for the purposes in section 4, disclose them to the service providers in section 6 for those purposes, and keep them for the periods in section 9.

Making a request. Write to business@queryrev.com. We respond within the times at the start of this section. If you do not have an account, we may ask for information in proportion to the request to confirm who you are. You may use an authorised agent; we may ask the agent for your signed permission and ask you to confirm your identity directly.

Appeals. If we decline your request, you may appeal by replying to our decision with the subject line "Privacy appeal". We will answer within 45 days. If you are not satisfied, you may contact your state attorney general.

Data in a customer's workspace. If your personal information is in a workspace we host for a customer (for example, your name appears on a website a customer's workspace crawls), we process it as that customer's service provider. Please contact the customer; we will forward requests we receive to it and help it respond.

Global Privacy Control. We do not sell or share personal information, so there is nothing for a Global Privacy Control signal to opt you out of; if that changes, we will honour the signal.

Many workspaces are run by agencies for their clients. In that case the agency decides which data is connected and who can see it, and the agency must hold its clients' written authorisation before it connects their accounts or has their sites crawled. For the data in those workspaces we act on the agency's instructions, under our Data Processing Addendum. A client of an agency who has a question about their data should contact the agency first; we will help the agency answer it.

QueryRev is a business service and is not meant for anyone under 16. We do not knowingly collect information from children. If you believe a child has given us personal information, write to business@queryrev.com and we will delete it.

We store and process data in the United States, with the service providers listed in section 6. If you use QueryRev from another country, your information is transferred to the United States. Our emails are sent through Resend's service in Japan, so the recipient's name and address and the content of each email are processed there.

When we receive personal information from the European Economic Area, the United Kingdom or Switzerland, we protect the transfer to the United States with the European Commission's Standard Contractual Clauses, with the UK International Data Transfer Addendum and the Swiss amendments where they apply. For customers, these are part of our Data Processing Addendum. Our service providers offer the same safeguards in their data processing terms. For the email processing in Japan, the European Commission and the United Kingdom recognise Japan as providing an adequate level of data protection, and that processing is also covered by our email provider's data processing terms. You can ask us for a copy of the relevant safeguards at business@queryrev.com.

QueryRev uses the cookies it needs to work, preference cookies that remember choices you make and, on our website only, analytics cookies if you allow them.

These cookies are needed for the service or remember a choice you made:

• queryrev.session_token (on secure connections its name starts with __Secure-): keeps you signed in. It lasts for your browser session or, if you choose to stay signed in, keeps you signed in for at most 90 days. It is removed when you sign out.
• queryrev.dont_remember: records that you chose not to stay signed in; it lasts for your browser session.
• queryrev.state: protects Sign in with Google against forged requests; it expires within minutes.
• qr_google_connect and qr_google_handoff: security cookies used while you connect a Google data source; they expire within minutes.
• qr-theme: remembers your light or dark appearance choice for one year. It is set only when you choose light or dark; with "system" there is no cookie.
• qr-sidebar and qr-details: remember whether the sidebar and the details panel are open, for seven days.
• qr-consent: on our website, remembers whether you accepted or rejected analytics cookies, for six months. After that we ask again.

These analytics cookies are set on our website, queryrev.com, by Google Analytics (section 3, "Website analytics"), only when analytics cookies are allowed:

• _ga: a random identifier that distinguishes one browser from another, for two years from your last visit.
• _ga_WCNVNR9ZCQ: keeps the state of your current visit, for two years from your last visit.

QueryRev also uses your browser's local storage, which stays on your device, to remember the workspace name you typed at sign-up until you have confirmed your email address, and the way you arranged a table (such as its columns, sorting and filters).

We do not use advertising or cross-site tracking cookies. To accept or reject analytics cookies, or to change your choice, use "Cookie Settings" at the bottom of any page of our website. You can also block or delete cookies in your browser settings; the service needs its sign-in cookies to work.

When we change this policy, we will update the effective date above. If a change is significant, we will tell workspace administrators by email or in the product before it takes effect.

STOA Global Corporation, provider of QueryRev AI
169 Madison Ave STE 89775, New York, NY 10016, United States
Email: business@queryrev.com