Visirush · Last updated: November 21, 2026
Privacy policy
This policy describes the personal data Visirush actually stores and processes. It does not describe a process that does not exist in the product. It applies to visirush.com and the Visirush service operated by SKA Digital LLC.
Controller
SKA Digital LLC, a member-managed Wyoming limited liability company, United States. Registered office: c/o Registered Agents Inc, 30 N Gould St Ste R, Sheridan, WY 82801, USA. Contact: contact@visirush.com.
SKA Digital LLC has no establishment in the European Union. For privacy requests from the EEA, the United Kingdom or Switzerland, you may contact us directly at contact@visirush.com. We have not appointed a separate Article 27 representative.
Accounts and access
- Account: email, name, password hash (scrypt), creation date. If two-factor authentication is on, a TOTP secret is stored, together with hashed backup codes.
- Google sign-in: provider id, subject, email, and the photo URL if it is accepted. The image file is not copied into the repository.
- Session: token hash, current organization, expiry, user-agent, and IP address.
- Password reset and email confirmation: hash of a signed token, expiry, time of use. The raw token is not written to logs.
- Organization: name and id. Role of each member. Invitation: email, role, token hash.
- Acceptance of the terms and the privacy policy: version 2026-11-21, timestamp, context (signup or payment), and the request IP address.
- Account audit log: action and related metadata.
Workspace
For each organization, the workspace keeps projects (name, client, URL), audits and their findings, report settings (agency name, color, footer), actions, activity, keywords, competitors, backlink summaries, brand profiles, plans and articles, plus GEO audits and their proposals. This customer workspace data is processed on the customer’s instructions, as described in the Data Processing Addendum.
Billing
Payments go through Stripe in the United States. Visirush stores the Stripe customer id, subscription id, plan, status, period end, and the cancellation flag. The card number is not stored by Visirush. Prices are in US dollars and exclude applicable taxes, which may be added at checkout where required by law. SKA Digital LLC does not display a VAT number.
Public requests
- Demo request: name, email, company, phone, and the short exchange if the request comes from the assistant.
- Appointment: name, email, company, and time slot. The public interface does not publish the names of team members.
- Site assistant: counters and a technical session (IP address, expiry, question count). Question text is not the durable log, unless it is copied into a demo request.
A demo or booking request is also copied to the Visirush team’s HubSpot account (contact and follow-up task) and sent as an internal Telegram alert, as listed on the Subprocessors page.
Integrations and secrets
When you connect a service, its OAuth tokens (Google Search Console, Google Analytics 4) and site or provider credentials (WordPress, Shopify, Webflow, Cloudflare, DataForSEO) are stored on the Visirush server in one secret store per organization, outside the application source repository. They are encrypted at rest with AES-256-GCM, with an encryption key kept outside the source repository and outside the data directory, in files readable only by the application (Unix permissions 0600). They travel only over HTTPS and are never sent to the browser. Visirush API keys are kept only as a hash, with a call log (path and date, not the secret).
Website and CMS connections
Visirush reads and writes a customer site only through the connection the customer sets up, and writes only after a person clicks to apply or validate a change. For each platform:
- WordPress, Visirush plugin. Stored: the site address and name, the WordPress, plugin and SEO plugin versions, the site key created by the plugin, and a log of applied changes (page id, field, change id, date). Read: the list of pages and posts (id, type, status, title, address, SEO title, meta description, last change date) and, when needed, a page’s content. Written, on your click: the SEO title and the meta description (in the Yoast SEO, Rank Math, All in One SEO or SEOPress fields, or in the plugin’s own fields), the page title and the page content. The previous value is kept on your site so the change can be undone.
- WordPress, application password. Stored: the site address, the user name and the application password. Read and written through the WordPress REST API: the same fields as above, plus drafts you validate.
- Shopify. Stored: the store’s .myshopify.com address and an Admin API access token. Read: pages and products (id, title, handle, status, SEO title and description). Written, after your validation: the SEO title and description of pages and products, and page drafts. A snapshot of the previous values is kept for rollback.
- Webflow. Stored: an API token and the site id. Read: pages (id, title, slug, SEO and Open Graph fields) and, if you configure it, a collection. Written, after your validation: the SEO and Open Graph fields of pages, and draft collection items. The site is published only when you choose to publish. A snapshot of the previous values is kept for rollback.
- Cloudflare. Stored: an API token, the account and zone ids, the route ids and the Worker name. Visirush creates one Worker and its routes on your zone; the Worker writes the titles and descriptions you approved into your pages and changes nothing else. Disconnecting deletes the routes, the Worker and the token.
- Visirush Script (Wix, HubSpot, Squarespace or any site). No account credential is stored. The script records the measurement data described under Measurement and pixel, and shows the titles and descriptions you approved.
- Wix and HubSpot. There is no direct connection to Wix or HubSpot accounts today. On these platforms, Visirush works only through the Visirush Script that you paste yourself, and stores no Wix or HubSpot credential.
Deleting a connection in Visirush deletes the stored credential. Changes already applied stay on your site unless you undo them.
Google user data
When you sign in with Google or connect a Google service, Visirush accesses only the data described below, and only with your consent:
- Google sign-in (OpenID Connect): your name, email address, and profile photo URL. The image file itself is not copied into the Visirush source repository.
- Google Search Console: performance data for the properties you authorize (queries, pages, clicks, impressions, and position), in read-only mode. Visirush does not change your Search Console settings or content.
- Google Analytics 4: report data for the properties you authorize (including traffic and channel metrics), in read-only mode. Visirush does not change your Analytics settings or data.
- Google Calendar: used only for the Visirush team’s own calendars, not a customer’s calendar. Visirush reads free/busy availability and creates or cancels demo-booking events on those team calendars.
This data is used only to operate your Visirush account, to show you your own reports and dashboards, and to run features you request (including booking a demo). Visirush does not sell Google user data, does not use it for advertising, and does not use it to train generalized AI or machine-learning models. Humans at Visirush do not read this data unless you consent, it is necessary for security or to investigate a fault, or we are required to do so by law.
Security. Google data travels only over HTTPS (TLS). OAuth tokens used to call Google APIs are encrypted at rest with AES-256-GCM; the key is kept outside the application source repository and outside the data directory, and the token files are readable only by the application (Unix permissions 0600). Tokens are never sent to the browser. Synced Search Console and Analytics data is stored on the Visirush server in your organization’s workspace, with access limited to your organization’s members according to their role.
Retention. Visirush keeps the Search Console and Analytics data it syncs (totals, top queries, pages and traffic channels for the selected period) while the integration stays connected. Each sync replaces the previous one. Operational backups that may contain this data are deleted after 30 days.
Deletion. When you disconnect Search Console or Google Analytics 4 in Visirush, the token is revoked with Google, deleted from the server, and the synced data for that service is deleted from your workspace. When you delete your Visirush account (or your organization), Visirush revokes the Google tokens and deletes the tokens and the workspace data, including the synced Google data. Backups follow within 30 days.
Sharing you control. You may include Search Console or Analytics figures in client reports, PDF exports or read-only client links that you create and share yourself. Visirush shares nothing on its own. You can revoke a client link at any time.
Use with OpenAI. Three features you start yourself send a small part of your Google data to the OpenAI API, only to produce the result you asked for: answering a question people search for (the Search Console query text, with the text of your page), planning articles in “We write for you” (your top Search Console queries, with their position and impressions), and Visi, the in-app assistant (the total clicks and sessions shown on your results screen). Nothing else from Search Console or Analytics is sent to OpenAI. Visirush does not use Google data to train AI models. OpenAI states that it does not use data sent through its API to train its models, and may keep it for a limited time for abuse monitoring.
You can revoke access at any time by disconnecting the integration in Visirush, and/or by removing Visirush in your Google account permissions at https://myaccount.google.com/permissions. To request deletion of your data, email contact@visirush.com.
Visirush's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. See https://developers.google.com/terms/api-services-user-data-policy.
Measurement and pixel
The Visirush pixel, if installed on a client site, stores a site key, the URL, and the referrer path and host. The client portal keeps the link hash, a label, and a view count.
Audience measurement on visirush.com uses Google Analytics 4 (id G-GFP8D441XE) only after consent. Consent Mode v2 is denied by default. Fonts are served by Visirush: there is no call to Google Fonts. You can change your choice at any time via Cookie settings. Details are in the Cookie policy.
Artificial intelligence
When an OpenAI key is configured, excerpts of public pages, briefs, and generation instructions are sent to OpenAI in the United States to produce recommendations, brand profiles, plans, articles, or GEO proposals. Without a key, those remote generations are not sent. What may be sent from Google Search Console and Analytics is described under Google user data.
Transactional email (address confirmation, welcome, invitation, reset, subscription, failed payment, cancellation, usage cap) is sent from contact@visirush.com through the host’s SMTP when the variables are set. Otherwise it stays in a local queue (recipient, subject, body, status). Server logs include neither the SMTP password nor the body of messages that contain a token.
Subprocessors and international transfers
We use the providers listed on the subprocessors page (hosting and email, payments, Google sign-in and analytics, OpenAI, and DataForSEO when that integration is enabled). Some of them are in the United States. Where required, transfers from the EEA, the United Kingdom or Switzerland rely on the Standard Contractual Clauses, as described in the Data Processing Addendum.
Retention
- Account data: for the life of the account, then 30 days after deletion.
- Billing records: 7 years.
- Technical logs: 90 days.
- Demo leads and booking requests: 24 months.
- Backups: rolling 30 days.
- Cookie choice: 6 months in your browser.
Your rights
Depending on where you live, you may have rights under the GDPR, the UK GDPR and the CCPA/CPRA, including access, correction, deletion, restriction, portability, and objection to certain processing. SKA Digital LLC does not sell personal data and does not share it for cross-context behavioral advertising.
You can delete your account yourself from Settings. We ask for your password, a two-factor code if two-factor authentication is on, and a typed confirmation. If you are the only owner of a workspace, this erases that organization’s projects, audits, API keys, sessions and white-label settings. A paid subscription is cancelled at the end of the current billing period; billing records are kept for 7 years as required. If other members remain, transfer ownership first. A minimal compliance record (a hash of the email address and the date of deletion, not the email itself) is retained.
To exercise these rights, or if you cannot access your account, email contact@visirush.com. We aim to respond within 30 days. You also have the right to lodge a complaint with a competent supervisory authority, including in your country of residence.
Language
These pages are provided in English and French. If there is any conflict between the two versions, the English version prevails.
Last updated: November 21, 2026.