Short version: Visiby only processes what you tell us to track plus a small amount of usage data to keep the service running. We never sell your data or use it to train AI models. It is encrypted in transit and at rest, and you can ask us to export or delete everything at any time.
This notice covers visiby.net and all Visiby sub-domains. It applies to anyone who visits, signs up, or uses the service. Visiby is run by FNA Technology LLP, Mumbai, India, which decides how and why your personal data is processed: the “controller” under the EU and UK GDPR and the “data fiduciary” under India's Digital Personal Data Protection Act, 2023 (DPDP Act). Our contact details are at the end of this notice.
Data we collect
| Account | Name, work email, password hash, workspace name, role |
|---|---|
| Free report | The email address, website domain and country you enter to get a free report, and the report we generate for it |
| Contact & demo requests | What you type into our contact form (name, email, phone, postal code and message) and into a demo booking (name, email, guests' emails, phone and message, plus the date, time slot and timezone you pick). We keep free-report requests, contact-form messages and demo requests in Google Sheets, run by Google, so our team can follow up. |
| WordPress (optional) | If you connect a WordPress site: the address of your WordPress site, your WordPress username and an application password (encrypted). We send draft posts (title, text, excerpt, slug and images) to that site. Disconnect it at any time. |
| Google account (optional) | If you connect Google: your email and basic profile, plus read-only Search Console and Google Analytics 4 metrics for the properties you select. Covered in detail in section 5. |
| Brand config | Keywords, competitor URLs, prompts, geographies, schedules |
| Engine responses | Answers from ChatGPT, Perplexity, and Google AI Overviews (plus Google AI Mode and Claude where enabled for your account) — including citations and timestamps |
| Cloudflare (optional) | If you connect Cloudflare: an API token with read-only Zone Analytics access and your zone ID, used to sync daily AI-crawler request counts for your site. |
| Usage | Pages viewed, reports run, browser, OS, truncated IP |
| Billing | Plan, seats, invoices, and the card summary our payment processor returns (last 4 and brand). Full card numbers stay with Razorpay and never reach us. |
Why we collect it, and our legal basis
We use personal data only for the purposes below. For each one we name the legal basis under the GDPR (Art. 6) and, where the DPDP Act applies, under that Act (consent under s. 6, or a legitimate use under s. 7).
| Service delivery | Authentication, scheduled reports, dashboards, weekly digests. GDPR: performance of our contract with you. DPDP: your consent, given when you sign up. |
|---|---|
| Free report | Running the report you asked for and emailing it to you. GDPR: steps you asked for before a contract. DPDP: you give us the data for this purpose (DPDP s.7(a)). |
| Contact & demo requests | Answering the message or booking you sent and following up. GDPR: our legitimate interest in answering a request you made. DPDP: you give us the data for this purpose (DPDP s.7(a)). |
| Follow-up emails | A small number of emails about your free report or account. GDPR: our legitimate interest in following up on a request you made. DPDP: your consent. You can opt out at any time by replying to any of them or emailing contact@visiby.net, and we stop. |
| Optional connections | Google Search Console, Google Analytics and Cloudflare data, and your WordPress site, only if you connect them. GDPR and DPDP: your consent, which you withdraw by disconnecting. |
| Product improvement | Aggregated, de-identified usage only. We never train models on your prompts or responses. GDPR: our legitimate interest in improving the service. We do not rely on a DPDP basis for it, because it is aggregated and de-identified. |
| Billing | Enough to process payments via our payment processor. We only store what's safe to show on an invoice. GDPR: contract and legal obligation. DPDP: consent, and compliance with law. |
| Security & legal | Audit logs (90 days), rate limiting, tax records, and lawful disclosure when ordered. GDPR: legal obligation and our legitimate interest in keeping the service secure. DPDP: compliance with law and other legitimate uses under s. 7. |
Who can see it
By default: you, your workspace members, and a small subset of Visiby on-call engineers. Outside that boundary, only:
Where your data is stored and transferred. Your account, workspace and report data are stored on servers in India, except the Google Sheets records, which Google may store outside India (see section 1). Some providers process data in other countries: the AI engines and search-data providers (mostly in the United States), our content delivery network (worldwide edge locations), and Google (for the Google Sheets records, and for the account you connect if you do). When personal data from the EU, EEA or UK is transferred to a country without an adequacy decision, we rely on the European Commission's Standard Contractual Clauses (and the UK addendum) or the provider's certification under the EU-US Data Privacy Framework. You can ask us for a copy of the relevant safeguards. Transfers out of India follow s. 16 of the DPDP Act: we do not transfer personal data to any country the Indian government has restricted.
How we protect it
Sensitive data (your credentials, the third-party tokens you grant us, and any Google account data you connect) is protected by the controls below. These are the mechanisms actually in place, not aspirations.
| In transit | Every connection to visiby.net and to our API is encrypted with HTTPS/TLS, including the hop from our CDN edge to our origin servers. We serve no plaintext HTTP. |
|---|---|
| At rest | Databases, report files, and backups sit on provider-managed AES-256 encrypted volumes. |
| Credentials | Passwords are stored only as one-way hashes (Argon2id for every password set or changed since June 2026, bcrypt for older ones), never in plaintext or a reversible form. Session refresh tokens are hashed the same way. |
| Third-party tokens | OAuth refresh tokens you grant us (including Google), and the WordPress application password, are sealed with AES-256-GCM authenticated encryption before they are written to the database, using a key held outside it. They are decrypted only in memory, only to make the API call you asked for. |
| Network isolation | The database server has no public IP address and no internet-facing port. It accepts connections only from the application server, over a private network, enforced at the firewall. |
| Administrative access | Staff reach production only through identity-aware tunnels bound to their own named accounts, never shared logins or shared keys. Database roles are per-person, least-privilege, and read-only unless a role needs otherwise. Access is removed when someone leaves the project. |
| In-product access | Your data is scoped to your workspace by signed, workspace-scoped tokens. Access tokens expire after 1 hour, refresh tokens after 7 days, and both can be revoked. |
| Logging & monitoring | Authentication and administrative access are logged and retained for 90 days. Logs are scrubbed of tokens and secrets. |
| Change control | Production releases are manual and gated on automated type, lint, and test checks. No pipeline can push to production unattended. |
If a breach affects your personal data, we notify the affected workspace owners and, where the law requires it, the relevant supervisory authority within 72 hours of becoming aware.
Google user data
Connecting Google is optional. Visiby works without it. If you do connect, we ask for the narrowest scopes that let the feature work, and every one of them is read-only.
| openid, email, profile | Identifies you at sign-in and links the connection to your Visiby account. |
|---|---|
| webmasters.readonly | Google Search Console: reads clicks, impressions, average position, and the queries and pages behind them, for the properties you pick. Read-only, so Visiby can never change or delete anything in your Search Console. |
| analytics.readonly | Google Analytics 4: reads traffic and engagement metrics for the property you pick. Read-only, so Visiby can never change your GA4 configuration or data. |
What we do with it. This data is used only to produce the reports and dashboards you see inside your own workspace: search performance views, and prompt and topic suggestions derived from the queries your site already ranks for. Prompts you approve are then run against AI engines on your behalf. Your Google account identity, your OAuth tokens, and raw Search Console or Analytics exports are never sent to those engines or to any other third party.
How it is protected. The refresh token is AES-256-GCM encrypted at rest as described in section 4. Cached Search Console and Analytics results live in the same isolated database, scoped to your workspace, reachable only by your workspace members and the small on-call engineering group named in section 3.
How to disconnect. Settings, then Integrations, then Disconnect. That call revokes the token with Google immediately and erases it from our database in the same operation. You can also revoke access at myaccount.google.com/permissions. Cached Google-derived data is deleted within 30 days of disconnecting, and immediately on account deletion.
Retention & deletion
| Account & workspace | Kept while your account is open. When you ask us to delete your account or workspace, we remove it within 30 days. |
|---|---|
| Google connections | Token erased the moment you disconnect. Cached Search Console and Analytics data deleted within 30 days of disconnecting, immediately on account deletion. |
| WordPress connections | Disconnecting erases the stored application password at once. We keep a record of the connection (site address, username, dates) and of the drafts we sent, for audit. |
| Reports & engine responses | Kept while your account is open so you keep your history, then deleted with the account. |
| Access & audit logs | 90 days, then deleted. |
| Billing records | Retained as long as tax and accounting law requires, typically 7 years. This is the one category we cannot delete on request. |
Your rights
Wherever you live, these rights apply. Where the GDPR, UK GDPR, CCPA or DPDP Act grants more, we honour the higher bar. To use any right you can't exercise in the product, email contact@visiby.net. We may ask you to confirm your identity, and we reply within 30 days.
| Access & export | Get a copy and a summary of the personal data we hold about you and how we use it. Email contact@visiby.net and we send it within 30 days, in a machine-readable format (data portability). |
|---|---|
| Correction | Correct, complete or update inaccurate or incomplete data, from your profile settings or by email. |
| Deletion | Ask us to delete your account or workspace at any time by emailing contact@visiby.net. We delete it within 30 days, except the billing records the law makes us keep (section 6). Your contact, demo and free-report details, which we keep in Google Sheets, can also be deleted on request: email us at the same address and we reply within 30 days. |
| Restriction | Ask us to pause the use of your data while a correction or objection is being resolved. |
| Objection | Object to processing based on our legitimate interests. You can always object to follow-up emails, and we stop. |
| Withdraw consent | Where we rely on your consent, withdraw it as easily as you gave it: disconnect an integration, reply to opt out of follow-up emails, or email us. Withdrawing doesn't affect processing that already took place. |
| Nominate someone | Under the DPDP Act, you can nominate another person to exercise your rights if you die or become unable to. |
| Complain | Raise a grievance with us first (see Contact & grievances). You can also complain to your local data protection authority in the EU or EEA, to the UK Information Commissioner's Office, or, in India, to the Data Protection Board of India once our grievance process is complete. |
Other information
| Is providing data required? | Your name, email and password are needed to create an account; without them we can't provide the service. Everything else, including Google and Cloudflare connections, is optional. |
|---|---|
| Automated decisions | We don't make decisions about you based solely on automated processing, including profiling, that have legal or similarly significant effects. |
| Children | Visiby is a business tool and is not meant for anyone under 18. We don't knowingly process children's personal data. If you think a child has given us data, tell us and we will delete it. |
| Language | You can ask for this notice in English or in any language listed in the Eighth Schedule to the Constitution of India. |
| Changes | We will post any change here and update the effective date. If a change materially affects how we use your data, we'll tell account owners by email before it takes effect. |
Contact & grievances
FNA Technology LLP (controller / data fiduciary)
10th Floor, C/125, Ganjawala Apartment, Mandpeshwar Road, near Chamunda Circle,
Borivali West, Mumbai, Maharashtra 400092, India
Privacy questions, rights requests and grievances: contact@visiby.net
We reply within 30 days.