Privacy Policy

Last updated: October 10, 2026

What Kanso keeps, and what it never keeps

Kanso does not keep your voice. When you talk to your Chief, the sound is sent to a speech service to be turned into text, and Kanso does not store the recording. Kanso keeps the written conversation and the numbers it works from. It does not keep other people's comments, captions or videos, only numbers about them.

1. Introduction

Kanso is an AI marketing and growth platform at kansoai.in. You give Kanso your website; Kanso analyses it, builds a picture of your business, and uses AI-powered assistants to suggest and draft marketing work such as SEO and search recommendations, content, and social posts. Optionally, you can connect Google Search Console and Google Analytics so that Kanso can use your own search and traffic data, connect social accounts so that you can publish drafts you approve, and connect a GitHub repository so that Kanso can prepare website changes as pull requests for you to review.

This Privacy Policy explains what information Kanso collects, how it is used and shared, how long it is kept, and the choices you have. It applies to the Kanso website (including the sign-in page) and the Kanso workspace (dashboard). Section 5 is specifically about information we receive from Google.

2. Who we are

Kanso is a product of Fermor Technologies Private Limited, a company incorporated in India (CIN U62099KA2026PTC228995), whose registered office is at 144, Shop No. SF 41, Bashyam Road, Cottonpet, Chickpet, Bengaluru, Karnataka 560053, India. In this policy, “Kanso”, “we”, “us” and “our” mean Fermor Technologies Private Limited, which is responsible for the information described here. You can reach us about anything in this policy at support@kansoai.in (see Section 21).

3. Information we collect

We collect only what Kanso needs to run. In particular, we do not ask for a password, phone number, postal address, government ID or payment card, and Kanso does not currently take payments.

Information you provide

Email address. You use it to sign in (a one-time code sent to your email, or Google Sign-In). Your email address, together with the workspace it belongs to and your role in it (Owner, Admin or Member), is your account. Kanso does not collect your name; the name shown inside the app is derived from the part of your email address before the “@”.
Your website address and any changes you make to the information Kanso generates about your business (for example the description, the company documents, or the list of competitors).
Messages you send to the AI assistants (for example to the CMO chat), including any images you attach.
Social content you approve. If you connect a social account and choose to publish a draft, the text you approve.
Communications with us, such as emails you send to the address in Section 21.

Information created or collected as you use Kanso

Sign-in records. When you request a sign-in code we store your email address, the code, its purpose, when it expires (10 minutes), whether it has been used, and the number of incorrect attempts.
A session token. After you sign in, Kanso issues a signed token, valid for 30 days, that contains your email address, your workspace’s internal ID and your role. It is stored in your browser (see Section 17).
Workspace data generated by Kanso: documents and a structured “website context” describing your business, suggested competitors and research targets, SEO and GEO findings, recommendations, tasks and code-change proposals, AI-generated drafts, and a per-workspace activity log describing what the analysis and agents did (including errors).
Connected-account data described in Sections 5 and 6.
Technical data. Our hosting providers process ordinary request data (such as IP address and browser type) to deliver the service and keep it secure. Kanso’s own database does not store your IP address.

Kanso does not store your chat conversations or attached images in its database. A conversation exists in your browser while the page is open, and is sent to our AI provider each time you send a message (Section 8).

4. Website URLs and website content

When you enter a website, Kanso receives the address you typed. Before you sign in, that address is kept only in your browser (for up to 24 hours) so it can be carried through sign-in. After you sign in and confirm it, Kanso stores the website address for your workspace. Once confirmed, it is locked to that workspace.

To set up your workspace Kanso then analyses publicly accessible content on that website:

It fetches your home page and up to three other pages of the same site that the home page links to, and uses the first part of the text of each page.
That text is sent to our AI provider (Section 8), which produces five documents (product information, marketing strategy, brand voice, competitor analysis and an articles plan), a suggested list of competitors, and suggested search queries and communities for Kanso’s agents to check. Kanso then builds a structured summary of your business (the “website context”) from those documents.
Kanso stores the generated documents, summary and suggestions. It does not keep a copy of the raw page text.
The SEO and GEO workspace can run a public baseline check of your site, on request or during onboarding. It fetches up to 25 public pages, plus robots.txt, sitemaps and llms.txt, checks whether the links on those pages work (including links to third-party sites), and uses Google’s PageSpeed Insights service. Kanso stores the findings and the page facts it extracted (such as titles, descriptions, headings, link and image counts, and response details).
Further public checks can be run on request or on a schedule, including a link audit that looks up the country where your website’s server is hosted, using the server’s IP address, through the third-party service ip-api.com.

This is public website content only. Kanso does not log in to your website or your hosting, and does not access private systems by virtue of you entering a URL. Information from services you deliberately connect (Google, X, LinkedIn, Reddit, GitHub) is covered separately in Sections 5 and 6. Kanso’s fetching is restricted to publicly routable internet addresses.

5. Google account and Google API data

Kanso uses Google in two separate, optional ways. This section says exactly what we access, why, where it is stored, who receives it, and how you can stop it.

5.1 Google Sign-In (identity only)

On the sign-in page you can choose “Continue with Google”. Google gives Kanso a signed credential which Kanso verifies on its server (signature, issuer, audience, expiry, and that the email address is verified by Google). Kanso uses only your verified email address from it, to find your existing workspace and sign you in. Google’s credential can also contain other basic profile details such as your name and picture; Kanso does not read, use or store them, and does not store your Google account ID. Signing in with Google does not give Kanso access to your Gmail, Drive, Calendar, Contacts or any other Google service, and does not create a workspace on its own (a new workspace is created after you verify an email code). Google Sign-In loads a script from Google on the sign-in page; Google’s own privacy policy governs what Google collects through it.

5.2 Google Search Console and Google Analytics (optional, read-only)

If you choose to connect them in your Kanso workspace, Kanso asks Google for the following permissions. Both are read-only. Kanso cannot change anything in your Search Console or Analytics accounts. A separate Google authorization is requested for each service and you can grant one without the other. Only a workspace Owner can connect or disconnect them.

Google permission (scope)	What Kanso receives	Why	Where it is stored
Search Console `webmasters.readonly`	The list of Search Console properties your account can access (read once, so you can choose one). For the property you choose: total clicks, impressions, click-through rate and average position for a period, compared with the previous period, broken down by date, page, search query, country, device and search appearance. Kanso also reads page-and-query breakdowns on demand.	To show you how people find your site in Google, to let the CMO assistant answer questions about your search performance, to generate SEO and GEO recommendations, and to let the Articles agent pick a real search query worth writing about.	A refresh token (so Kanso can keep reading on your behalf) is stored encrypted (AES-256-GCM) in a connection record for your workspace, together with the property you chose. Summaries of the data above are stored as snapshots. Google access tokens are requested when needed and are not stored.
Google Analytics `analytics.readonly`	The list of Google Analytics accounts and properties visible to the account you connect (read once, so you can choose one). For the property you choose, aggregate reports for a period, compared with the previous period: sessions, active users, new users, engaged sessions, engagement rate, bounce rate, average session duration and key events, broken down by date, channel, source and medium, landing page, device category, country and event name. Kanso does not receive individual visitor records.	To show your traffic and engagement in your dashboard, to generate SEO and GEO recommendations, and to let the CMO assistant answer questions about them.	A refresh token is stored encrypted (AES-256-GCM) in a connection record for your workspace, together with the property you chose. The aggregate reports are stored as snapshots.

Kanso does not request access to Gmail, Google Drive, Google Calendar, Google Contacts or any Google service other than those described in this section.

5.3 How Google data is used

We use Google user data only to provide or improve these user-facing features inside your workspace:

displaying your search and traffic data and how it is changing;
answering questions you ask the CMO assistant about your own search and traffic data;
generating the SEO and GEO recommendations shown in your workspace, and choosing a search query for the Articles agent to write about;
refreshing that data periodically (Kanso refreshes connected Google data once a day in the background).

5.4 Who receives Google data

You and your workspace’s members see it in the dashboard.
Our AI provider (Section 8). When you ask the CMO assistant something that needs your search or traffic data, the relevant rows or totals are returned to the AI model as part of that conversation so it can answer. When Kanso generates SEO and GEO recommendations, a bounded, cleaned summary of your public-site findings and the matching Google figures for those pages is sent to the AI model. When the Articles agent runs, the chosen search query is sent to the AI model to write the article. These transfers happen only to provide the feature you are using.
Our infrastructure providers (hosting and database, Section 10) store and process it on our behalf.
We do not sell Google user data, do not rent it, and do not share it with advertisers, data brokers or other third parties for their own purposes.

5.5 Limited Use

Kanso’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. In particular:

We use Google user data only to provide or improve the user-facing features described above.
We do not transfer it to others except to provide those features (for example to our AI provider and infrastructure providers, Section 10), to comply with law, or as part of a merger, acquisition or sale of assets with notice to you.
We do not use it for serving advertisements, including retargeting or interest-based advertising.
We do not use it to develop, improve or train generalized artificial-intelligence or machine-learning models.
We do not allow people to read it except with your consent for a specific purpose such as support, where necessary for security or to investigate abuse, to comply with law, or when it is aggregated and used for internal operations in line with applicable law.

5.6 Retention, disconnecting and deletion of Google data

The stored Google refresh token is kept, encrypted, only while the connection is active. Snapshots of the data above are kept while your workspace exists, until you delete your account or ask us to delete them (see Section 12).
To stop Kanso accessing your Google data, a workspace Owner can use Disconnect on the Google Search Console or Google Analytics card in the workspace. Kanso then asks Google to revoke the token and deletes the stored token. Snapshots already stored, and your chosen property, are kept until you delete your account or ask us to delete them. You can also revoke Kanso’s access at myaccount.google.com/permissions. Revoking there stops Kanso from reading new data immediately, and Kanso clears the stored token when it next finds that Google has revoked it.
To have the Google data we hold deleted (the stored token, property selections and snapshots), use Delete account in Settings, under Account & Security, or email support@kansoai.in from your account email address (Section 13).

Kanso includes optional integrations with X, LinkedIn, Reddit and GitHub. Availability of each depends on the connection being set up and on the platform, and some may not be available to every workspace. Only a workspace Owner can connect or disconnect them.

Platform	Permission requested	What Kanso stores	How it is used
X	Posting on your behalf (OAuth 1.0a)	Your X user ID and @username, and your access credentials (encrypted).	To show which account is connected and to post a draft when you approve it.
LinkedIn	Sign-in profile and posting: `openid profile w_member_social`	Your access token and its expiry (encrypted). Your profile name is read to show which account is connected and is not stored in Kanso’s database.	To show which account is connected and to publish a post when you approve it.
Reddit	Identity and submit: `identity submit`	Your Reddit user ID and username, and your access and refresh tokens (encrypted).	To show which account is connected and to publish a reply when you approve it.
GitHub	Installation of the Kanso GitHub App: read and write access to Contents and Pull requests, and read-only Metadata	The installation ID; the GitHub account name, ID and type; whether you gave access to all or selected repositories; the email of the person who connected it. For the repository you choose: its ID, owner, name, default branch and whether it is private. No GitHub token is stored.	To prepare website changes as pull requests that you review and confirm (see below).

Kanso publishes only when a person presses the publish action for a specific draft. Nothing is posted automatically.
Kanso also reads public information to prepare drafts and ideas: public posts and discussions on Reddit and Hacker News, and public web search results. Kanso does not connect to a Hacker News account and never posts to Hacker News.
To disconnect X, LinkedIn or Reddit, use Settings in your workspace. Disconnecting stops Kanso using the connection and clears the stored credentials; for X and Reddit Kanso also asks the platform to revoke the token. You can also revoke access in each platform’s own settings.

How the GitHub connection works

You install the Kanso GitHub App on a GitHub account or organization and choose one repository that holds your website’s code. To confirm that you can really access the installation, GitHub sends Kanso a one-time user token; Kanso uses it once, then revokes it and does not store it.
Each time Kanso acts, it asks GitHub for a short-lived access token limited to that one repository and the minimum permissions for that action. These tokens are used immediately and are not stored.
Only when you ask for a code-change proposal for a specific SEO recommendation (a missing page title, meta description or canonical tag), Kanso reads the repository’s file list and the one relevant HTML file. A bounded excerpt of that file (up to 3,000 characters, with anything that looks like a secret removed) and facts about the page are sent to our AI provider (Section 8), which suggests wording for a missing title or description. Kanso builds the edit itself and stores a preview of it.
Nothing is written to GitHub until you review the proposal and confirm it. Kanso then creates one commit on a new branch and opens a pull request, and stops. It never merges, approves, deploys, changes existing branches or edits workflows.
You can remove Kanso’s access at any time by uninstalling the Kanso GitHub App in your GitHub settings. Deleting your Kanso account removes Kanso’s own link to the installation and repository; only the owner of the GitHub account can uninstall the App.

7. How we use information

To create and secure your account, sign you in, and keep your workspace separate from other workspaces.
To analyse your website and build your workspace, and to generate the recommendations, drafts and answers you ask for.
To show your connected Google data, to publish to social accounts you connect when you approve a post, and to prepare pull requests in a GitHub repository you connect when you confirm them.
To operate, maintain, troubleshoot and secure Kanso, including preventing abuse and diagnosing errors.
To communicate with you about your account or requests (for example sign-in codes and replies to your emails).
To meet legal obligations and to enforce our Terms of Service.

We do not use your information for advertising, and we do not sell it.

8. AI and automated processing

Kanso is built on AI models operated by third-party providers. Kanso is built to work with Anthropic, OpenAI, xAI (Grok) and Groq, and uses the provider(s) it has configured at a given time. Depending on the feature you use, the following can be sent to the configured AI provider:

the public text of pages from your website, when your workspace is analysed;
your workspace’s generated documents, website context, competitor list and recent recommendations;
the messages you type to an assistant (up to the ten most recent turns of a conversation) and any images you attach;
results of tools the assistant uses on your behalf, which can include Search Console and Analytics data you connected (Section 5), and public web search or page results;
a bounded, cleaned summary of your public-site findings and, if connected, the matching Google figures, when SEO and GEO recommendations are generated;
a bounded, secret-redacted excerpt (up to 3,000 characters) of one repository file, when you ask for a code-change proposal (Section 6);
public posts and articles that Kanso is helping you reply to or write about.

Kanso does not use your information, including Google user data, to train or fine-tune AI models. We use the providers’ services to generate the output you asked for. Kanso also uses a web search and page-fetch service (Section 10) for research the assistant performs; the search queries and page requests it makes are chosen by the assistant and can relate to what you asked about.

AI output can be wrong or incomplete. Kanso drafts and recommends; a person decides what to publish or merge. Kanso does not make decisions about you that have legal or similarly significant effects.

We do not sell your personal information. We share information only:

Within your workspace. Other members of your workspace can see the workspace’s data, including connected Google data.
With service providers that process it for us to run Kanso (Section 10).
With the platforms you connect, when you publish or confirm a change (X, LinkedIn or Reddit receive the post you approved; GitHub receives the branch and pull request you confirmed).
For legal reasons, to comply with law or valid legal process, to protect the rights, safety or security of Kanso, our users or others, or to investigate misuse.
In a business transfer, such as a merger, acquisition or sale of assets, in which case we will tell you and this policy’s protections for your information (including Google user data) will continue to apply.

10. Third-party service providers

Provider	Role	Information involved
Vercel	Hosts the Kanso website and API, and runs scheduled jobs. The API currently runs in Vercel’s Tokyo, Japan region.	All data in transit and the request data needed to serve Kanso.
Supabase (PostgreSQL)	Database that stores Kanso’s data.	Account and workspace records and everything described in Section 12.
Resend	Sends sign-in code emails.	Your email address and the sign-in code.
AI providers: Anthropic, OpenAI, xAI, Groq	Generate the analysis, recommendations, drafts and answers (Section 8). Kanso uses the provider(s) it has configured at a given time.	The inputs listed in Section 8.
TinyFish	Web search and page fetching used by the assistant’s research.	Search queries and page addresses chosen by the assistant.
Google	Sign-In (Identity Services); Search Console and Analytics data (Section 5); the PageSpeed Insights service used for SEO audits; and a favicon service Kanso’s pages use to show company and website icons.	As described in Section 5; your website address for audits; and the domain names of sites shown in Kanso for icons.
Google AdSense	Shows advertising on the Kanso home page and blog articles, and pays Kanso for it. It is not loaded inside the app.	Visitors to those public pages: Google and its advertising partners may use cookies and your device and browser details to show and measure ads. Kanso does not send them your workspace data.
YouTube (Google)	Public YouTube information read through YouTube API Services for the YouTube Agent.	Search terms taken from your website description, and requests for public channel and video information (Section 18). No account access.
GitHub	Hosts the repository you connect through the Kanso GitHub App and receives the branch and pull request you confirm (Section 6). Also runs the job that scans public Reddit posts for the Reddit agent.	Repository identifiers and the change you confirmed; for the Reddit scan, a workspace identifier and the subreddit names to scan.
X, LinkedIn, Reddit	The platforms you connect and publish to.	Section 6.
Reddit, Hacker News (Algolia)	Public sources Kanso reads to find relevant discussions.	Public content and search terms.
ip-api.com	Looks up the hosting country of your website’s server for the link audit.	The server’s IP address (not your personal IP address).

These providers may process information in countries other than yours (Section 15). We choose providers to run the specific functions above and give them only what those functions need.

11. Data security

We use reasonable technical and organizational measures designed to protect information. Measures that exist in Kanso today include:

Kanso is served over HTTPS.
Signing in requires either a one-time email code (a code stops working after five wrong guesses, and a new code cannot be requested more often than once a minute) or a Google credential that Kanso verifies on its server.
Every request for workspace data must carry a valid session, and data is looked up only within the workspace of the signed-in session; other workspaces’ data is not reachable through it. Connecting or disconnecting Google, social and GitHub accounts is limited to the workspace Owner.
Google refresh tokens and the access credentials for X, LinkedIn and Reddit are encrypted (AES-256-GCM) before they are stored. GitHub access uses short-lived tokens that are not stored.
Google and GitHub connection attempts use short-lived, single-use state values, stored only as a hash and tied to the signed-in Owner, so a connection cannot be started by someone else or replayed.
Kanso’s website fetching is limited to publicly routable internet addresses, so a submitted address cannot be used to reach internal systems.

No system is perfectly secure and we cannot guarantee absolute security. Your session token is stored in your browser’s local storage (Section 17), so keep your devices and browser secure and sign out on shared computers.

12. Data retention

Kanso does not currently apply a general automatic expiry to workspace data. In practice:

Information	How long we keep it
Account, workspace and membership records	For as long as the workspace exists, until you delete your account or ask us to remove it (Section 13).
Sign-in codes	A code stops working after 10 minutes or once used. Codes for an email address are deleted when that account is deleted; otherwise the record is not deleted automatically.
Website address, generated documents, website context, competitors and agent settings	For as long as the workspace exists, until removed.
Recommendations, drafts and other agent output	Kept until removed. Reddit and Hacker News items that have been completed or dismissed are automatically deleted after a retention period (currently 90 days by default).
SEO and GEO findings, recommendations, tasks and code-change proposals	For as long as the workspace exists, until removed.
Activity logs and analytics snapshots, including snapshots of connected Google data	For as long as the workspace exists; there is no automatic expiry.
Google refresh tokens	Deleted when you disconnect Google, and cleared when Google reports that access was revoked. Your chosen property and the stored snapshots stay until you delete your account or ask us to delete them (Section 5.6).
X, LinkedIn and Reddit credentials	Until you disconnect the integration, which clears them.
GitHub installation and repository details, and code-change proposals	Until you delete your account or ask us to delete them. Kanso stores no GitHub token.
Public YouTube data saved by the YouTube Agent, and its saved research and ideas	Saved YouTube data is not used after 30 days and is removed automatically after that. The current research summary and ideas stay until the next run replaces them; earlier versions are then deleted once 30 days old (Section 18).
Chat conversations and attached images	Not stored by Kanso. They exist in your browser while the page is open.
Backups and provider logs	Our providers may keep backups and logs for a limited time after deletion.

We may also keep information for as long as needed to provide the service, comply with legal obligations, resolve disputes and enforce our agreements, subject to applicable law.

13. Data deletion and revoking access

Disconnect Google or social accounts yourself in the workspace (Owner only), or revoke access in the platform’s own settings. See Section 5.6 for Google.
Stop Google access at myaccount.google.com/permissions.
Delete your account yourself. In Settings, under Account & Security, choose Delete account and confirm. Before anything is erased, Kanso disconnects your connected accounts on a best-effort basis (Google tokens are revoked at Google, X tokens are invalidated and Reddit tokens are revoked). Kanso then removes your membership and your sign-in codes. If no other member remains, the whole workspace is permanently erased, including its documents, findings, snapshots (including snapshots of Google data), proposals, activity logs and connected-account records. If other members remain, the workspace stays for them, because their data is not yours to delete, and if you were its only Owner the longest-standing remaining member becomes Owner. Only the owner of a GitHub account can uninstall the Kanso GitHub App; deleting your Kanso account removes Kanso’s own link to it.
Ask us to delete data (all of it, or specific data such as stored Google tokens and snapshots) by emailing support@kansoai.in from the email address on your account. We will confirm it is you, then delete the data we hold, within a reasonable time and any time limit the law sets.
We may keep limited information we are legally required or permitted to keep, and information may remain briefly in backups.

14. Your privacy rights

Depending on where you live and the law that applies (for example India’s Digital Personal Data Protection Act, 2023, or laws in other countries), you may have rights to: access the personal information we hold about you; have it corrected or completed; have it erased; withdraw consent you have given; object to or restrict certain processing; receive a copy of it in a portable form; and nominate someone to exercise your rights. To exercise a right, email support@kansoai.in. If you are not satisfied with our response, contact our grievance officer (Section 21 and the Grievance Redressal page), and you may have the right to complain to a data-protection regulator. We will respond as the law requires. We do not claim that Kanso complies with the law of every jurisdiction; these rights apply only where the law provides them.

15. International data transfers

Kanso is operated from India, but the providers in Section 10 process information in other countries, including Japan (where the Kanso API currently runs) and countries where our AI, database and other providers operate, which may include the United States. By using Kanso you understand that your information can be transferred to and processed in countries whose data-protection laws differ from those of your country.

16. Children’s privacy

Kanso is a business tool and is not directed to anyone under 18. We do not knowingly collect personal information from children. If you believe a child has given us personal information, contact us at support@kansoai.in and we will delete it.

17. Cookies and local storage

The Kanso app does not set cookies for sign-in or analytics, and does not use third-party analytics trackers. The home page and the blog show ads from Google AdSense, and Google and its advertising partners may set cookies there to show and measure ads (see our Cookie notice and the Google row in Section 10). No advertising runs inside the app. The app stores the following in your browser’s local storage:

Item	Purpose	Kept until
ops_token	Your signed-in session (the session token in Section 3).	You sign out, or it expires after 30 days.
kanso_pending_website	Carries the website you typed on the home page through sign-in.	24 hours, or once you confirm it or sign out.
kanso_theme, kanso-theme	Your light/dark preference.	You clear browser storage.
kanso_workspace_view, kanso_workspace_layout_, kanso_workspace_shell_, kanso_terminal_cleared_before, kanso_ci_watchlist	Remember dashboard layout and view choices for you.	You sign out, or clear browser storage.

The sign-in page loads Google Sign-In from Google, and Kanso’s pages request website icons from Google’s favicon service; Google may use its own cookies or local storage for those services under Google’s policies. Clearing your browser’s site data removes the items above and signs you out.

18. YouTube API Services

Kanso’s YouTube Agent uses YouTube API Services to read public information from YouTube. By using the YouTube Agent you also agree to be bound by the YouTube Terms of Service, and the Google Privacy Policy applies to information handled through YouTube API Services.

What it reads. Only public YouTube information: search results, public channel information (such as a channel’s name and, where the channel shows it, its number of subscribers), public video information (titles, view, like and comment counts, upload dates and lengths), lists of a channel’s public uploads, and a list of popular videos in a country.
What it does not do. It does not ask for access to your YouTube or Google account and requests no Google permission for this feature. It does not post, upload or change anything on YouTube, and it does not read the analytics of your own channel.
Why. To suggest video ideas and a two-week plan for your business. The titles, channel names and numbers it found are shown to you as evidence, with links to the videos on YouTube. The research results, together with the description of your business that Kanso built from your website, are sent to our AI provider to write the ideas (Section 8). Kanso does not sell this information or use it for advertising.
How long it is kept. Public YouTube data is saved temporarily so that Kanso does not ask YouTube for the same thing again and again. Kanso does not use saved YouTube data that is older than 30 days, and removes entries older than that automatically. The research summary and ideas shown to you are kept in your workspace until the next run replaces them; earlier versions are then deleted automatically once they are 30 days old. You can ask us to delete your workspace data at any time (Section 13).

19. Third-party links

Kanso links to and connects with third-party sites and services. We do not control them and this policy does not apply to them; please read their policies.

20. Changes to this policy

We may update this policy as Kanso changes or the law requires. We will post the new version at this address with a new effective date, and where a change is material we will notify you by email or in Kanso. Continued use after a change means you accept the updated policy, except where the law requires your consent.

21. Contact us and grievance officer

Fermor Technologies Private Limited
CIN: U62099KA2026PTC228995
Registered office: 144, Shop No. SF 41, Bashyam Road, Cottonpet, Chickpet, Bengaluru, Karnataka 560053, India
Privacy and data requests: support@kansoai.in
General enquiries: contact@fermor.in

Grievance officer. If you have a complaint about how your information is handled, contact our grievance officer: Challa Naveen Reddy, Director, support@kansoai.in, at the address above. If the complaint is not resolved within 15 days, or you do not accept the answer, you can escalate to Bollu Gunawanth, Director, at contact@fermor.in. How complaints are handled, and our response times, are on the Grievance Redressal page.