Privacy policy

Visifluent (visifluent.com) is run by Marketing Chains LLC, a limited liability company registered in Delaware, United States ("we", "us"). You can write to us about anything in this policy at info@visifluent.com.

Visifluent is invitation-only for now: only people we have invited, or that the owner of an account has invited to work in it, can create an account. A sign-in by someone nobody has invited creates no account.

We collect only what the tools need to work.

• Your Google account. When you sign in with Google we receive your name, email address, profile picture and Google's stable ID for your account. We use them to create your account and to recognize you when you return.
• What you add. The websites you add; the results of audits and page-speed tests of them; the keywords, rankings and competitors you track; the questions you put to AI engines and their answers; tasks, notes and files you attach; content drafts and the documents in a website's knowledge base; report branding (a logo, a color and a name); the clients you group your websites under, with a brand of their own if you give them one; and your settings.
• Teammates, if you invite any. On the Agency plan the owner of an account can give other people a seat in it, by their Google address. We keep the address you type, and we send that address one email, which says who invited it and links to the sign-in. A teammate signs in with their own Google account and then works in the owner's account: they can see and change everything in it, and the owner sees the teammate's Google name, address and photo, and when they were last here. A teammate's own account, if they have one, is kept apart and is not touched.
• Google Search Console, if you connect it. Read-only access to the search performance and indexing data of the websites your Google account can see in Search Console. We fetch it when you use a feature, and we save some results, such as the before-and-after measurement of a change you log. The login is stored encrypted.
• Google Analytics, if you connect it. Read-only access to the Google Analytics 4 properties your Google account can see: their names and the addresses of their web streams, so that you can pick the one that belongs to a website, and the reports of that property, such as visits, where they come from, the pages they land on, countries and devices. They are totals and lists, not records of single visitors. We fetch the reports when you open your Dashboard, or when you ask the SEO Assistant a question that needs them, and keep them in the server's memory for a few minutes; we do not save them. We save which property you picked for each website. The login is stored encrypted, separately from your Search Console one.
• Google Merchant Center, if you connect it. Access to the Merchant Center accounts your Google account can see. Google has no read-only permission for Merchant Center, so its screen asks you to let this app manage your product listings; we only read, our code sends no other kind of request about your account, and a test checks it. We read each account's name, home page address and time zone, so that you can pick the one that belongs to a website; its products, with their title, brand, price, availability, whether Google shows them and the problems Google found; the problems with the account as a whole; and performance reports, such as the clicks and impressions of your products and of your store's links. We fetch them when you open the Shopping page, or when you ask the SEO Assistant a question that needs them, and keep them in the server's memory for a few minutes; we do not save them, except that when you add a problem to your tasks, the text of that task is saved. We save which account you picked for each website. The login is stored encrypted, separately from your Search Console and Analytics ones. Google asks us to tell you that, depending on how your account is set up, the data of apps connected to it may be shared with Business Manager. If you want Merchant Center itself to refuse any change, connect with a Google account that has the “Read only” access level in your Merchant Center: Google describes it as having no access to any mutating methods.
• Bing Webmaster Tools, if you connect it. Your Bing login, or an API key you paste, is stored encrypted. Only the websites that login lists are requested from Bing.
• Technical data. Our servers keep short technical logs, mostly errors and security events. They can contain your IP address and your browser's description of itself. They are rotated automatically, so they are kept for days, not months.
• Visits to our public pages. On the home page, the sign-in page and our other public pages we use Google Analytics to count visits. Without your yes it runs without cookies: for each page you open, your browser sends Google a signal with the page's address and title, where you came from, your browser, language and screen size, and your IP address, which Google uses to work out roughly where you are (country and city) and, as Google states, does not store. It cannot tell that two visits come from the same browser. If you accept the question we ask on those pages, it also sets cookies, so that it can recognize you when you come back. Nothing is recorded inside your account.
• LinkedIn, only if you say yes. Our public pages can carry the LinkedIn Insight Tag, which we use to measure and improve our LinkedIn advertising and to see which LinkedIn members visit our public pages. Until you accept the question we ask about it, none of LinkedIn's code is on the page and nothing is sent to LinkedIn. If you accept, your browser loads LinkedIn's script and sends LinkedIn, for each public page you open, the page's address and title, where you came from, your browser and device, your IP address and the time, and LinkedIn sets its own cookies, so that it can recognize you if you are a LinkedIn member. LinkedIn states that it removes members' direct identifiers within seven days, deletes the rest within 180 days, and gives us reports that do not identify individual members. It never runs on the sign-in page or inside your account.
• The waitlist, if you join it. On the pricing page you can give us your email address and the plan you are interested in, so that we can write to you when we can invite you to an account, and when paid plans open. You need no account for it. We keep the address, the plan and the day you joined, and nothing else, and we get a notice of each new sign-up by email at info@visifluent.com, sent through our email provider (Resend, below). Please use only your own address. To be taken off the list, write to info@visifluent.com.
• Email updates, if you ask for them. On the home page and the blog, once you have said yes to the cookie question, a pop-up can ask for your email address, so that we can send you occasional ideas for your SEO and news about Visifluent. You need no account for it. We keep the address, the day you signed up and the page you were on, and nothing else, and we get a notice of each new sign-up by email at info@visifluent.com, sent through our email provider (Resend, below). Please use only your own address. To be taken off the list, write to info@visifluent.com.
• Daily usage counters. To keep actions that cost money within daily limits we keep counters tied to a one-way hash of your Google account ID, or, for the public waitlist form and the email pop-up, of your IP address. A counter holds no email, profile, website, question or result. It stops counting after 24 hours, and the ones tied to an account are kept even if you delete it, so deleting and re-creating an account cannot reset the limits.

When you ask us to audit a website, our crawler reads its public pages. It says who it is, reads only public pages, and obeys the website's robots.txt. Our crawler's page explains how a website owner can keep it out.

We use what is needed to run the service. Google Analytics (to count visits) and the LinkedIn Insight Tag (advertising) set cookies only if you say yes to each of them.

• A sign-in cookie keeps you signed in. It is marked secure and HTTP-only, so scripts on the page cannot read it.
• Short-lived sign-in cookies (about ten minutes) carry the state of a Google or Bing sign-in from the moment you leave to the moment you return.
• Analytics cookies, only if you say yes. If you accept, Google Analytics sets two cookies, _ga and one that starts with _ga_, which last up to two years and let it recognize the same browser on your next visit. They are set on our public pages only, never inside your account. If you decline, or do not answer, it sets no cookies and works as described under "What we collect". You can change your answer at any time with Cookie settings at the bottom of the home page, and saying no removes the cookies.
• LinkedIn cookies, only if you say yes. If you accept the LinkedIn question, the tag keeps a few cookies on our site, li_adsId, li_fat_id, li_giant, ar_debug, oribi_cookie_test, oribili_user_guid and ln_or, which last from the length of a visit to a year, and the same identifier in your browser's local storage. Your browser also exchanges LinkedIn's own cookies with linkedin.com, such as bcookie, lidc, UserMatchHistory, AnalyticsSyncHistory, li_sugr, lms_ads and lms_analytics, which LinkedIn lists in its cookie table. All of this happens on our public pages only, never on the sign-in page or inside your account. If you decline, or do not answer, none of it is set. You can change your answer at any time with Cookie settings at the bottom of the home page: saying no removes what the tag kept on our site and reloads the page without the tag, and the cookies at linkedin.com can be removed in your browser or in your LinkedIn settings.
• Your browser's local storage keeps interface choices, such as the website you selected, which sidebar groups are folded and your answers about analytics and LinkedIn, whether you closed or signed up through the email pop-up, and small copies of lists the app has already shown you. You can clear it in your browser at any time.
• Map pictures in the Local SEO tools are loaded from OpenStreetMap's tile servers. Your browser asks them directly, so they see your IP address.

• To provide the service you asked for: to sign you in, run audits, fetch your Search Console, Google Analytics and Merchant Center data, track rankings, answer your questions and send the alerts you switched on. Our legal basis is performing our agreement with you.
• To keep the service safe and fair: to stop abuse, enforce the daily limits and fix problems. Our legal basis is our legitimate interest in running a secure service.
• To connect Search Console, Google Analytics, Merchant Center or Bing: only when you choose to, and you can withdraw at any time. Our legal basis is your consent.
• To see how our public pages are used: how many people visit them, which pages they read and where they come from, so we can improve them. Without your yes this is cookie-free counting, based on our legitimate interest in knowing how our public pages are used. With your yes it also uses cookies, based on your consent, which you can withdraw at any time.
• To measure our LinkedIn advertising: which of our public pages LinkedIn members visit, so that we can measure and improve our campaigns there. This happens only if you say yes, and our legal basis is your consent, which you can withdraw at any time.
• To send you email updates, if you asked for them: occasional ideas for your SEO and news about Visifluent, to the address you gave. Our legal basis is your consent, which you can withdraw at any time.

We do not sell your personal information, we do not use what is in your account for advertising, and we do not use it to train AI models. The one advertising tool is LinkedIn's tag on our public pages, which runs only after your yes.

We use a small number of providers to run the service. Each receives only what its job needs.

Paid plans are not available yet. When they are, a payment provider (Stripe) will handle card details; we will not see or store your card number, and we will update this policy before payments start.

We may also disclose information if the law requires it, or to protect the service and its users from harm.

The servers and the database are in Germany, in the European Union. Some of the providers above may process information in other countries, including the United States. They do so under the safeguards they offer, such as the European Commission's standard contractual clauses.

• Your account and what you added: until you delete your account or ask us to.
• Teammates: an invitation or a seat is kept until the owner takes it back, the teammate leaves or the account is deleted; deleting an account ends its teammates' seats.
• When you delete your account: your data is deleted, and the Search Console, Google Analytics and Merchant Center permissions are withdrawn at Google. Encrypted backups are kept for up to 30 days and then expire, so deleted data can remain in them until then.
• Technical logs: days, as above.
• Usage counters: about a day, as above.
• Your place on the waitlist: until we have written to you about the plans, or until you ask us to take you off, whichever comes first.
• Your place on the email list: until you ask us to take you off.
• Analytics data: kept by Google Analytics for 14 months at most, the longest it allows.
• LinkedIn data: LinkedIn states that it removes members' direct identifiers within seven days and deletes the rest within 180 days.

• Delete your account in Settings, under Account. It removes your data and withdraws the Search Console, Google Analytics and Merchant Center permissions at Google.
• Disconnect Google Search Console, Google Analytics, Google Merchant Center or Bing in Settings, under Connections. Disconnecting a Google service also withdraws its permission at Google.
• Turn off alert emails in Settings, under Account, and stop a scheduled report in Settings, under Reports.
• Leave the waitlist by writing to info@visifluent.com.
• Leave the email list by writing to info@visifluent.com.
• Change your answers about analytics and LinkedIn with Cookie settings at the bottom of the home page. Saying no to analytics removes its cookies and keeps Google Analytics cookie-free; saying no to LinkedIn removes what its tag kept on our site and reloads the page without it. To keep even that signal from reaching Google, block Google Analytics in your browser or with an extension.
• Ask us to show, correct or export what we hold about you, or to delete it, by writing to info@visifluent.com. We answer within 30 days.

If you are in the European Economic Area or the United Kingdom, you also have the right to restrict or object to how we use your information, to receive it in a portable form, to withdraw your consent and to complain to your data protection authority.

If you live in California or another US state with a privacy law, you can ask what we hold about you and ask us to correct or delete it, and we will not treat you differently for asking. We do not sell personal information. The only sharing for advertising is the LinkedIn Insight Tag on our public pages, which runs only if you accept it; we share nothing from inside your account.

Visifluent'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.

• We ask for read-only access to Search Console and, separately, read-only access to Google Analytics. Google offers no read-only permission for Merchant Center, so for that one we ask for the permission it has, which lets an app manage product listings: we use it only to read, and never to change, add or delete anything in your account. We ask for each only when you choose to connect it. Signing in alone gives us your name, email address and picture.
• We use Search Console data to show it to you and to produce the reports, opportunities and suggestions you ask for. When you put a question to the AI assistant or another AI feature, the data it needs goes to the AI provider named above to produce that answer, and for no other purpose.
• We use Google Analytics data to show it to you on your Dashboard, next to your Search Console figures, and to answer the questions you put to the SEO Assistant: the reports it needs go to the AI provider named above to produce that answer, and for no other purpose. No other AI feature reads Analytics data. We do not store it.
• We use Merchant Center data to show it to you on the Shopping page and to answer the questions you put to the SEO Assistant: the products and reports it needs go to the AI provider named above to produce that answer, and for no other purpose. No other AI feature reads Merchant Center data. We do not store it, except that when you add a problem to your tasks, the text of that task is saved with it.
• We do not sell it, use it for advertising, or let people read it, except to fix a problem you ask us about, to follow the law, or where it is needed to protect the service.

• Everything travels over encrypted connections (HTTPS).
• Google and Bing logins are stored encrypted, and so are the database backups.
• Only the operator can reach the servers, with a key and not a password, and the database accepts no connections from the internet.
• Daily limits and one-at-a-time rules guard against abuse.

No service is perfectly secure. If a breach affects your information, we will tell you as the law requires.

Visifluent is not for anyone under 16, and we do not knowingly collect information from children. If you think a child has an account, write to us and we will delete it.

We will change this page when the service changes, for example when payments are added, and the date at the top changes with it. If a change matters to you, such as a new way we use your information, we will tell you by email before it applies.

Marketing Chains LLC. Email: info@visifluent.com.