Last updated 14 September 2026
Omnivisum is a product of Dignizant Technologies LLP, which operates it. This page describes what we collect, why, and what we do with it. It describes the product as it actually works rather than covering every possibility in general terms.
Your account. Your email address and the name of your workspace, so you can sign in and so we know which data is yours.
Your website. We fetch and read the public pages of the site you give us, the same way a search engine does, to understand what you publish and where the gaps are.
Accounts you connect. If you connect Google Search Console, Google Analytics, Google Business Profile, Microsoft Clarity, Meta, LinkedIn, your email sender or your CMS, we store an access credential for each and use it only for the specific things described below.
What the platform produces. Drafted articles, keyword rankings, AI-engine answers about your brand, outreach messages and the leads that arrive through your site.
Sign-ins. For each sign-in we keep the browser type, the network address and the time, for as long as that session is active. You can see and end every session under Settings. We use this to email you when your account is signed in to from a browser it has not used before, and for nothing else.
Cookies. One, strictly necessary: it keeps you signed in between visits. It holds an encrypted reference to your session, nothing readable, and it is not used for tracking or advertising. There are no analytics or advertising cookies on this site, so there is nothing to consent to and no banner asking you to. Our public pages (this site's front page, the comparison, this policy) count visits with Google Analytics in its cookieless mode: no cookie, no identifier, and nothing inside your workspace is ever measured; if your browser sends "Do Not Track", not even that.
Google Search Console is read only. We read impressions, clicks and indexing status for your own site, to tell you which pages earn attention and which are not indexed. We never modify anything in your Search Console account.
Google Analytics is read only. We read aggregate traffic figures for your own property, to attribute results to the work the platform does.
Google Business Profile is read and write. We read your reviews and, only when you approve each one individually, publish a reply you have seen.
Meta, LinkedIn and your CMS are write access, used only to publish content you have approved. We never post without an explicit approval from someone in your workspace.
We do not use data from any connected account to train models, and we do not sell or share it with anyone. Data from your workspace is never used to produce anything for another customer.
This section says exactly what happens to data from a Google account you connect, in the terms Google asks every app to use.
What we access. Search Console: search queries, pages, impressions, clicks, average position and indexing status for the property you choose (scope webmasters.readonly). Analytics: aggregate sessions, users and page views per page for the property you choose (scope analytics.readonly); never individual visitors. Business Profile: the locations you choose, their reviews, and the replies and updates you approve (scope business.manage). Nothing else from your Google account is read: no email, no files, no contacts, no other properties.
How we use it. Only to provide the features you see: showing your queries, rankings and traffic in your workspace, choosing which pages to write or improve, replying to your reviews after you approve each reply, and writing your weekly and monthly reports. Never for advertising, never for profiling, never to build anything for another customer.
Who else sees it. The figures (never your Google credentials) can be included in the material sent to the AI providers listed below to write your reports and drafts. Those providers process it to return a result and, under their API terms, do not use it to train their models. We do not sell, license or otherwise transfer Google user data to anyone, and never to data brokers or advertisers.
How it is protected. The connection tokens are stored encrypted in a vault inside our database and are never shown to anyone, including us, after you connect. Data is held on our own servers, isolated per workspace by database rules, reachable only over encrypted connections, and every automated action that touches it is written to an audit log that cannot be edited.
How long we keep it, and how to delete it. Google data is kept while the connection is active and for the reports it produced. Disconnect in Settings and we stop reading immediately and delete the stored tokens; the figures already in your reports remain part of your workspace until you close it, at which point everything is erased on the schedule in "Closing a workspace" below. You can also revoke our access at any time from your Google account's security page, and it takes effect on our side at the next run.
Limited Use. Our use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Raw or derived Google user data is used only to provide and improve the user-facing features described here, and is never used to develop, improve or train AI or machine-learning models.
Writing and analysis use third-party AI providers. Content and prompts are sent to them to produce a result and are not used by us for anything else. Their own retention policies apply to what passes through them.
These are the companies your data reaches, and why. We do not add one without updating this list.
| Who | What reaches them |
|---|---|
| Railway | Hosting. The database and every service run here, in Europe. All of your data is on this infrastructure. |
| Anthropic | Writing and analysis. Article drafts, your brand voice, and the page content being analysed. |
| OpenRouter | Routes some AI requests to other model providers. The same content as above passes through. |
| DataForSEO | Rankings and search volumes. The keywords you track and the domain being measured. No customer content. |
| Resend | Email delivery, for campaigns and outreach you send. Recipient addresses and message content. |
| Search Console, Analytics and Business Profile, when you connect them. Your own data, read on your behalf. | |
| Meta | Facebook and Instagram, when you connect them. Posts we publish for you, and comments we read. |
| Your company page, when you connect it. Posts we publish, and comments we read. | |
| Microsoft | Clarity behaviour analytics, when you connect it. Page-level statistics about your own site. |
| Unsplash | Article images. A search term derived from the article title. No customer data. |
| Razorpay | Payments. Your billing details, handled by them - we never see or store a card number. |
Business customers in the EU or UK can ask us for a data processing agreement naming these as subprocessors. Email support@omnivisum.com.
Data is stored in a database hosted in Europe. Each workspace is isolated at the database level, so one customer's data is not readable by another. Within your own workspace, anyone you have invited can see it.
Our staff do not read your content in normal operation. Access to production data is limited to what is necessary to fix a fault you have reported or one we have detected.
While your workspace is open, for as long as it is open. Disconnect an integration and its stored credential is deactivated immediately.
Erase your workspace yourself, in Settings, and its content and credentials are deleted at once - leaving only the billing record and the audit trail, which are append-only, legally required, and no longer name you.
If a workspace is closed and not erased, the same erasure runs automatically after the retention period stated in your plan. Ask us for the current period at support@omnivisum.com and we will tell you in days, not in general terms.
You do not have to ask us for any of this. In Settings, under Your data, you can download everything your workspace holds as a file, and you can erase the workspace yourself. Both take effect immediately.
The download contains every article, keyword, ranking, subscriber, post and report in your workspace. It deliberately excludes your stored credentials: those are keys to your accounts on other systems, held on your behalf, and handing them back in a file would be a risk to you rather than a service.
Erasing deletes your content and every stored credential, and removes your business details from the workspace record. Two things survive, and cannot be deleted by anyone including us: the billing record and the log of what the platform did. They are append-only by design, which is what stops them being quietly rewritten, and after erasure they no longer name you or your business. We keep them because tax and accounting rules require a financial record be retained.
If you would rather a person did it, or you want something corrected rather than deleted, write to support@omnivisum.com and we will respond within 30 days.
Dignizant Technologies LLP ยท support@omnivisum.com