Privacy policy

Jarvis SEO Engine. Last updated 9 October 2026.

Summary

Jarvis reads search performance and traffic reports from Google Search Console and Google Analytics, with read-only access, for websites we own or manage. We use these reports only to analyse and improve those websites. We do not request your name or email address, we do not sell data and we do not use it for advertising. We keep the reports while a website is connected to Jarvis, and we keep aggregated statistics and Jarvis's own analyses as long-term history. We delete data on request and when a website is disconnected.

1. Who is responsible

Jarvis SEO Engine ("Jarvis") is operated by VersaVantage LLC, trading as WebServ ("we", "us"), 1309 Coffeen Avenue, STE 17547, Sheridan, WY 82801, United States. We are responsible for the data described in this policy. You can reach us at privacy@webserv.online.

2. What this policy covers

This policy covers the data Jarvis receives from Google APIs when the owner of a website connects their Google account, and the data this public website (jarvis.webserv.online) handles when you visit it.

Jarvis is a private tool. There is no public sign-up. The Google consent screen is shown only to people who connect a website they own or manage to Jarvis.

3. Google user data Jarvis accesses

When you connect your Google account, Jarvis asks for two read-only permissions (OAuth scopes):

Permission Data Jarvis receives

Permission	Data Jarvis receives
Google Search Console, read only `https://www.googleapis.com/auth/webmasters.readonly`	The list of Search Console properties your account can access. Search performance reports for the connected properties: date, search query, page address, clicks, impressions, click-through rate and average position. Search Console leaves out rare queries to protect searchers' privacy, so Jarvis never receives them. The index status of published articles from the URL Inspection report: whether the page is indexed, its coverage state, the last crawl time and the canonical address. Jarvis asks for this on request and stores only whether each page is indexed and when it was checked.
Google Analytics, read only `https://www.googleapis.com/auth/analytics.readonly`	Aggregated daily totals for the connected Google Analytics 4 property: active users, sessions and page views. The same totals per day and page path.

Google Search Console, read only
https://www.googleapis.com/auth/webmasters.readonly

The list of Search Console properties your account can access.
Search performance reports for the connected properties: date, search query, page address, clicks, impressions, click-through rate and average position. Search Console leaves out rare queries to protect searchers' privacy, so Jarvis never receives them.
The index status of published articles from the URL Inspection report: whether the page is indexed, its coverage state, the last crawl time and the canonical address. Jarvis asks for this on request and stores only whether each page is indexed and when it was checked.

Google Analytics, read only
https://www.googleapis.com/auth/analytics.readonly

Aggregated daily totals for the connected Google Analytics 4 property: active users, sessions and page views.
The same totals per day and page path.

To keep this access working, Google gives Jarvis an access token and a refresh token. Jarvis uses them only to read the reports listed above.

4. What Jarvis does not access

Jarvis does not request your name, email address, profile or any other Google account data.
Jarvis does not request user-level or demographic reports from Google Analytics. The reports it reads are aggregated and do not identify individual visitors.
Jarvis cannot change anything in your Google account, Search Console or Google Analytics. It cannot add or remove users, change settings or submit anything on your behalf.

5. How we use the data

We use Google user data only to provide the features of Jarvis:

to analyse how the connected website performs in Google Search;
to find pages and topics that can be improved, such as pages with many impressions but few clicks, outdated content, competing pages and missing internal links;
to prepare recommendations, which a person reviews before anything changes on the website;
to measure whether an approved change improved search performance and traffic;
to keep a long-term history of the website's search performance, so that trends can be compared across several years;
to let Jarvis learn from the measured results of earlier changes when it prepares new recommendations for the websites it manages;
to report these results to the owner of the website.

We do not sell Google user data. We do not use it to serve advertising, to build profiles of people, or to determine credit-worthiness or for lending. We do not use it to develop, improve or train generalised artificial intelligence or machine learning models.

Our basis for this processing is the website owner's authorisation and our legitimate interest in analysing and improving websites we own or manage.

6. How we store and protect it

Imported reports are stored in a database on systems operated by us. The Jarvis application and its interfaces are not reachable from the public internet.
Google access and refresh tokens are kept in access-restricted files, separate from the database and never in source code.
Access to these systems is limited to the people who operate Jarvis and requires key-based authentication.
Data is encrypted in transit between Google and Jarvis. Backups are encrypted.

If a security incident is likely to affect your rights, we will tell you and the relevant authority within seventy-two hours of becoming aware of it, and explain what happened and what to do about it.

7. How long we keep it

Jarvis keeps a long-term history, so that search performance can be compared across several years and new recommendations can build on the results of earlier ones. We keep three kinds of data apart:

Kind of data	What it is	How long we keep it
Raw reports from Google	The report rows as Google sends them: search performance per day, query and page, Google Analytics totals per day and page, and whether each checked article is indexed.	While the website is connected to Jarvis. Deleted within 30 days after the website is disconnected or access is removed.
Aggregated statistics	Totals per site, page, search query or topic over a day, week or month, such as clicks, impressions, average position, sessions and page views. They contain no data about individual visitors.	While the website is connected to Jarvis, and after that as part of the website's history. Deleted within 30 days when the website owner asks.
Jarvis's analyses and learnings	Jarvis's own records: recommendations, decisions, the measured effect of each change and the conclusions drawn from it. They can quote figures from the reports.	As long as they are useful for future analysis. Deleted within 30 days when the website owner asks.

How deletion works. Jarvis does not delete data on a timer. The people who operate Jarvis carry out each deletion, within the periods above.
Google tokens. When you remove Jarvis's access in your Google account, Google stops the tokens from working at once, so no new data can be read. We delete our stored copy within 30 days.
Backups. Jarvis is backed up every night. Backups are encrypted, kept on storage we control and used only to restore Jarvis. Data deleted from Jarvis can remain in earlier backups until those backups are removed. If we ever restore Jarvis from a backup, we delete again any data that had been deleted after that backup was made.
If Google's terms or applicable law require a shorter storage period for any of this data, we follow that requirement.

We share Google user data only in these cases:

The website owner. Reports and recommendations about a website go to its owner and the people they authorise.
Service providers acting for us. To draft recommendations, Jarvis may send parts of the aggregated data, such as a page address and the search queries it appears for, to an artificial intelligence service provider that processes it on our instructions. We use only providers whose terms do not allow them to use this data to train their models.
Legal requirements. We disclose data to a law enforcement or regulatory body only where we are legally required to.

We do not transfer Google user data to data brokers, advertisers, advertising platforms or information resellers.

9. Limited Use

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

10. Removing access and deleting data

You can remove Jarvis's access to your Google account at any time on your Google Account permissions page. Jarvis then can no longer read your reports.

To have data deleted, including aggregated statistics and analyses, or earlier than described in section 7, write to privacy@webserv.online and name the website or Search Console property. We confirm when it is done.

11. This website

This website sets no cookies. It uses no analytics, advertising or tracking scripts, and it loads no fonts or other files from third parties.

Our web server records a standard access log entry for each request: IP address, time, requested page and browser string. We use these logs to operate the site, diagnose faults and investigate abuse. The server keeps them in compressed monthly archives and builds traffic statistics from them. Both stay on our own server, are not shared, and currently have no fixed deletion date. You can ask us to delete them as described in section 12.

12. Your rights

You can ask us to:

give you a copy of the data we hold about you or your website, in a portable format;
correct anything inaccurate;
delete your data;
restrict or object to a particular use;
withdraw your authorisation, which you can also do yourself as described in section 10.

Write to privacy@webserv.online. We respond within thirty days. We may ask you to confirm your identity first, so that we do not hand your data to someone else. There is no charge. You also have the right to complain to the data protection authority in your country.

13. Children

Jarvis is a business tool and is not directed at children. We do not knowingly collect data from anyone under eighteen.

14. Changes to this policy

If we change how Jarvis uses Google user data, we update this policy before the change takes effect and ask for your consent again where Google's policies require it. The date at the top of this page always shows the current version.

15. Contact

VersaVantage LLC, trading as WebServ
1309 Coffeen Avenue, STE 17547
Sheridan, WY 82801
United States
privacy@webserv.online