TokenOps
Multi-Agent HarnessRun across any providerRuntime ControlsControl access, behavior, risk
LLM RouterCost that scales with difficultyMCP GatewayAny tool, one controlled doorArtifact RegistryShip agents like software
PublicationsBlogsDocs
Get Nasiko on your desktop For macOS, Windows and Linux. Download
EventsAbout usGitHub
EnterprisePricingSecurity
11.9Kstars Get StartedGet Started Book a DemoBook a Demo
TokenOps

Platform

Multi-Agent HarnessRuntime ControlsLLM RouterMCP GatewayArtifact Registry

Resources

PublicationsBlogsDocs Get Nasiko on your desktop

Company

EventsAbout usGitHub
EnterprisePricingSecurity
Get StartedGet Started Book a DemoBook a Demo

Privacy Policy

Last updated Nov 16, 2026Effective Nov 16, 2026Version 1.0

Table of contents

  1. Introduction
  2. Scope of This Policy
  3. Who Controls Your Data
  4. Personal Information We Collect
  5. How We Collect Personal Information
  6. How We Use Personal Information
  7. Sharing and Subprocessors
  8. Cookies and Similar Technologies
  9. How We Protect Personal Information
  10. Data Retention
  11. Security Incidents
  12. International Data Transfers
  13. Deleting Your Account
  14. Your Rights and Choices
  15. Children’s Privacy
  16. Limitation of Liability
  17. Changes to This Policy
  18. Contact Us

1. Introduction

This Privacy Policy explains how Nasiko Inc. (“Nasiko”, “we”, “us” or “our”), of 555 University Ave, Palo Alto, CA 94301, collects, uses, shares and protects personal information when you use our products, apps, websites and services (together, the “Services”), and the rights you have over that information. One policy applies to every Nasiko product, app and marketplace listing.

We do not sell your personal information for money, and we do not use it for behavioral advertising on other sites. Some US state laws treat our use of Reo.dev, which tells us which companies visit us, as “sharing”; Section 7 explains this and how to opt out. We do not train or fine-tune any AI model, ours or anyone else’s, on your prompts, code, agent activity or tool output unless you explicitly agree in writing.

This policy should be read together with our Terms of Service. If you have any questions, contact us at [email protected].

2. Scope of This Policy

This policy covers:

  • Nasiko Cloud, our hosted service at app.nasiko.com and its workspaces.
  • The Nasiko CLI, including nasiko agents discovery and coding-agent connections.
  • The Nasiko desktop app (com.nasiko.desktop), including versions distributed through the Apple App Store and Microsoft Store.
  • Our listings on GitHub, the DigitalOcean Marketplace and other marketplaces.
  • Our websites, documentation and support channels, including nasiko.com.

If you get Nasiko through an app store or marketplace, that platform handles your purchase and your account with it under its own privacy policy. We receive only the details we need to provide and license Nasiko, and never your payment card details. If you deploy Nasiko from a marketplace into your own cloud account, it is a self-hosted deployment and Section 3 applies.

3. Who Controls Your Data

Our role depends on how you use Nasiko:

Nasiko Cloud (individual accounts) and our websites. We are the controller (under Indian law, the “data fiduciary”) of your personal information, and this policy applies in full.

Enterprise customers. When an organization uses Nasiko for its staff, that organization is the controller of its workspace data. We process that data only on its documented instructions, under our Data Processing Agreement. We will tell the organization if we believe an instruction breaks applicable law. Questions about that data should go to your organization first.

Self-hosted and open-source deployments. When you run Nasiko on your own infrastructure (the open-source edition, an enterprise install on AWS, Google Cloud, Azure, DigitalOcean or your own servers, or the CLI connected to a server you run), your data stays on your infrastructure and we do not receive it. Coding-agent activity, prompts, model traffic and credentials go only to your own Nasiko server. You are the controller of personal information in your deployment and are responsible for your own notices to your users. We may still receive:

  • License checks for paid editions: the license key, edition and an install identifier, used to verify and renew the license confirm exact fields.
  • Information you choose to send us, such as support requests, logs or bug reports.
  • Download records from GitHub, container registries or marketplaces, which those platforms log under their own policies.

No sale for money. In every case, we do not sell personal information for money or use it for behavioral advertising on other sites.

4. Personal Information We Collect

We collect only what the Services need to work. You need to give us your account details to use Nasiko Cloud. Most other information depends on which features you turn on and the choices you make.

CategoryWhat it includes
Account and workspaceName, work email, organization, role, workspace membership, and your sign-in identity from your SSO provider (Okta, Entra ID, Google or another OIDC provider)
Coding-agent activityFor agents you connect (such as Claude Code, Codex, Cursor and OpenCode): session and turn records, model used, token counts (input, output, cache read and write), tool calls, timestamps, and the content of prompts, responses and tool output
Model and tool trafficRequests your agents send through the Nasiko LLM router and MCP gateway, including prompts, responses, tool calls and their results, plus usage, cost and latency metrics
Connected servicesIdentifiers and permissions for tools you connect, such as through Composio. We store access grants, not your passwords to those services
Credentials you storeAPI keys and secrets you add to the Nasiko credential manager. They are stored encrypted and used only to call the service you configured
BillingPlan, license and transaction records. Card details are handled by the marketplace or payment provider and are not stored by us
Device and usageIP address, browser or app version, operating system, crash reports and product usage events (in Nasiko Cloud, linked to your account ID, never your email)
Website analytics and marketingVisits and clicks on our websites; an anonymous identifier if you allow analytics cookies; and, if marketing is on, the company you visit from, IP address, device information and, for signed-in users, your email address (see Sections 7 and 8)
Lead formsName, work email and company you enter in our demo, audit or pilot forms, and the campaign tags (UTMs) of that visit
Support and communicationsWhat you send us by email, chat or forms, and event or demo sign-ups

Content may contain personal information. Prompts, code, tool output and files your agents handle can include personal information about you or others. You decide which agents and tools to connect, and enterprise administrators can limit what is captured.

You can review, update or delete your information in Settings > Account or by emailing [email protected].

5. How We Collect Personal Information

  • From you, when you sign up, are invited to a workspace, buy a plan, fill in a form, add credentials or contact us.
  • From your coding agents, only after you run nasiko agents setup or install, which adds a hook to each agent you choose. When you run setup, past sessions are imported from that agent’s local history. Running nasiko agents discover only lists the coding agents on your computer and sends nothing until you choose to connect one.
  • From traffic you route through Nasiko, for agents or tools you send through our LLM router or MCP gateway.
  • From third parties you authorize, such as your SSO provider, connected services, and the app store or marketplace you buy through.
  • From data and enrichment partners. When you submit a lead form, Clay adds public business information about you and your company. If marketing is on, Reo.dev matches visit information with data from its partners to identify the visiting company.
  • Automatically, through our apps, websites, cookies and similar technologies when you use the Services (see Section 8).

6. How We Use Personal Information

We use personal information to run the Services you asked for, and to understand how people find and use them.

PurposeExamplesLegal basis (EU/UK)
Provide the ServicesShow agent inventory, cost and usage; route model and tool calls; enforce your policies, budgets and approvals; keep audit recordsContract
Optimize your usageCompress requests, choose models and measure tokens saved, as you configureContract
Secure and support the ServicesAuthenticate users, detect abuse, monitor errors and crashes, fix bugs, answer support requestsLegitimate interests
Billing and licensesIssue and verify licenses, process marketplace purchases, keep tax recordsContract and legal obligation
Improve the productProduct analytics keyed to your account ID, and aggregated, de-identified metrics on which features are usedLegitimate interests
Website analyticsCount visits anonymously; with your consent where required, use cookies to see which pages help people sign upLegitimate interests; consent for cookies where required
Marketing and salesLearn which companies visit us, respond to demo requests, enrich lead information, measure campaignsConsent where required; otherwise legitimate interests
Communicate with youService notices, and product updates you can opt out ofContract, or consent where required
Comply with lawRespond to lawful requests, enforce our termsLegal obligation and legitimate interests

No AI training on your content. We do not use your prompts, code, agent activity or tool output to train or fine-tune any model, ours or anyone else’s, unless you explicitly agree in writing.

Model providers. When you route requests through Nasiko, we send them to the model provider you configured (for example OpenAI, Anthropic or Google), under your account or ours as your plan specifies. That provider’s own terms govern how it handles the request.

Automated decisions. We do not make decisions about you based solely on automated processing that have legal or similarly significant effects on you.

7. Sharing and Subprocessors

We share personal information only to run the Services, at your direction, as described below, or when the law requires it.

  • Service providers (subprocessors) that host, store, secure and support the Services, such as Google Cloud, Vercel, Neon, Sentry, Resend and Calendly (booking demos), under contracts that limit their use of the data to the work we give them.
  • Analytics and marketing providers: PostHog (website and product analytics), Reo.dev (company identification, see below) and Clay (lead enrichment), in line with your choices.
  • Model providers you route requests to, such as OpenAI, Anthropic or Google, to answer those requests.
  • Tool and connector providers you connect, such as Composio and the services behind it, or MCP servers you register, to carry out the actions your agents request.
  • Your organization. If you use a work account, your workspace administrators can see your agents, usage, costs and activity records.
  • Marketplaces and payment providers (Apple, Microsoft, GitHub, DigitalOcean, Stripe) to process purchases and licenses.
  • Legal and safety. When required by law, to protect rights and safety, or to enforce our terms.
  • Business transfers. As part of a merger, acquisition or sale of assets, with notice to you.

Our current list of subprocessors is at nasiko.com/security. We remain responsible for the work our subprocessors do for us.

Selling and sharing

We do not sell personal information for money, and we do not use it for behavioral advertising on other sites.

We use Reo.dev, a service that tells us which companies, and sometimes which developers, visit our websites and use Nasiko Cloud. Reo.dev may match visit information, such as an IP address, device information, or the email address of a signed-in user, with data from its partners. Under some US state privacy laws, including California’s, this can count as “sharing” personal information, or as a “sale”.

You can opt out at any time:

  • On our websites, select Your privacy choices in the footer and turn off Marketing.
  • In Nasiko Cloud, go to Settings > Privacy.
  • Turn on Global Privacy Control (GPC) in your browser. We treat a GPC signal as an opt-out of sale and sharing for that browser.

Where the law requires consent first (the EU, EEA, UK and Switzerland), Reo.dev runs only after you agree. In Nasiko Cloud it runs only after you agree, wherever you are.

In the 12 months before this policy’s date, the categories of personal information we may have shared in this way are identifiers (such as IP address and business email) and internet activity (pages visited on our sites). We do not knowingly sell or share the personal information of anyone under 16.

8. Cookies and Similar Technologies

Our websites and Nasiko Cloud use cookies, local storage and similar technologies. Some are needed to run the Services. Others help us understand how the Services are used, or which companies visit us; those depend on your choices.

CategoryWhat it doesProviderYour choice
NecessaryKeeps you signed in, keeps the Services secure, remembers your privacy choicesNasikoAlways on
Error monitoringReports crashes and errors so we can fix them. Does not store your IP address and sets no tracking cookieSentryAlways on
Anonymous visit countingCounts visits and clicks on our websites without cookies and without storing an identifier in your browser. Each visit is counted on its own and cannot be linked to you or to your other visitsPostHogEU, EEA, UK and Switzerland: only if you agree. Elsewhere: on unless you turn it off in Your privacy choices
Analytics cookiesA PostHog cookie links your visits, so we can see which pages help people sign up. No names, emails or screen recordingsPostHogEU, EEA, UK and Switzerland: only if you agree. Elsewhere: on unless you opt out
Product analytics (Nasiko Cloud)How features are used, keyed to your account ID, never your email. No cookie in your browserPostHogOn by default; turn it off in Settings > Privacy
MarketingIdentifies which company, and sometimes which developer, is visiting. See “Selling and sharing” in Section 7Reo.devWebsites: EU, EEA, UK and Switzerland only if you agree, elsewhere on unless you opt out. Nasiko Cloud: only if you agree
Aggregate statisticsPage counts without cookies or identifiersVercelAlways on

Browser signals. If your browser sends Global Privacy Control or Do Not Track, we turn off analytics cookies, anonymous visit counting and marketing for that browser. You can turn them back on in Your privacy choices.

Where data goes. PostHog and Sentry process data in the United States. PostHog keeps analytics events for 12 months and then deletes them.

You can also set your browser to block cookies. Some parts of the Services may not work without necessary cookies.

Cookie list

The cookies and browser storage our websites use. Analytics and marketing items are set only when your choices, or the default for your region in the table above, allow them.

NameProviderPurposeTypeLifetime
nasiko-geoNasikoRemembers which privacy rules apply in your regionCookie, necessary24 hours
nasiko:consentNasikoRemembers your privacy choicesLocal storage, necessaryUntil you change your choices or clear your browser
nasiko:source, nasiko:demo-fromNasikoThe page, button and campaign tags you arrived with; sent only with a form you submitSession storage, necessaryUntil you close the tab
nasiko:seen, nasiko:curtain, nasiko:starsNasikoShows page animations once per visit; caches our public GitHub star countSession storage, necessaryUntil you close the tab
__ph_opt_in_out_phc_…PostHogRemembers whether PostHog may use analytics cookies in this browserLocal storage, analyticsUntil you change your choices or clear your browser
ph_phc_…_posthogPostHogAn anonymous identifier that links your visitsCookie and local storage, analytics cookies1 year
ph_phc_…_window_id, ph_phc_…_posthogPostHogTells your browser tabs apart within one visitSession storage, analytics cookiesUntil you close the tab
__sec__cid, __sec__fid, __sec__ghost, __sec__token, __sec__crid, __sec__tidReo.devIdentifies which company, and sometimes which developer, is visitingCookies, marketing300 days
Calendly scheduling cookiesCalendlySet by Calendly’s booking calendar on the Book a demo page, under Calendly’s own policyThird-party cookiesSet by Calendly

Sentry and Vercel set no cookies on our websites. Withdrawing a choice removes that provider’s items from your browser.

9. How We Protect Personal Information

  • We encrypt data in transit and at rest.
  • We isolate each workspace from every other workspace.
  • We give agents short-lived credentials, and store the credentials you add in encrypted form.
  • We keep audit logs of access, and limit staff access to what support requires.

Add SOC 2 / ISO 27001 status once certified.

No system is perfectly secure, but we take reasonable steps to protect your information.

10. Data Retention

We keep personal information only as long as we need it for the purposes in Section 6.

DataHow long we keep it
Account and workspace dataWhile your account is active, then deleted within 30 days of account deletion
Coding-agent activity, model and tool trafficFor the retention period set by your plan or administrator, by default 90 days
Credentials you storeUntil you remove them or delete the workspace
Website and product analytics events12 months
Lead form informationRetention period to confirm
Billing and license recordsAs long as tax and accounting law requires, typically 7 years
BackupsOverwritten on a rolling 35-day cycle

We may keep information longer only where the law requires it or to establish, exercise or defend legal claims.

11. Security Incidents

If we become aware of a security breach that affects your personal information, we will notify you, and any regulator, as the law requires. For EU and UK personal data, this means notifying the supervisory authority within 72 hours where required, and affected individuals without undue delay where the risk to them is high. Enterprise customers are notified without undue delay so they can meet their own obligations.

12. International Data Transfers

We are based in the United States, and our service providers, including PostHog and Sentry, may process data in the United States and other countries. For transfers from the EU, UK or Switzerland, we use the European Commission’s Standard Contractual Clauses and the UK addendum or the EU-US Data Privacy Framework, if we certify. Enterprise customers can choose a hosting region where available.

13. Deleting Your Account

This policy applies for as long as we hold your personal information. You can delete your Nasiko account at any time, including from inside our apps at Settings > Account > Delete account. We then delete your data within the periods in Section 10. When an enterprise agreement ends, we return or delete the organization’s workspace data as our Data Processing Agreement provides.

14. Your Rights and Choices

Wherever you live, you can ask us to access, correct, delete or export your personal information, and we will not treat you differently for asking.

EU, EEA, UK and Switzerland

You can also:

  • Object to or restrict our processing, including anonymous visit counting.
  • Withdraw consent at any time, where we rely on consent.
  • Complain to your local data protection authority.

California and other US states

You have the right to:

  • Know what personal information we collect, how we use it and who we share it with.
  • Delete and correct your personal information.
  • Opt out of sale, sharing or targeted advertising, including through Global Privacy Control (see Section 7).

India

You can also:

  • Nominate another person to exercise your rights if you die or become unable to.
  • Raise a grievance with our Grievance Officer (Section 18). If we do not resolve it, you can complain to the Data Protection Board of India.

Work accounts

If your organization administers your account, we may refer your request to them, as they control that data.

Your privacy choices

  • Websites. Select Your privacy choices at the bottom of any page on nasiko.com. You can turn anonymous visit counting, analytics cookies and marketing on or off at any time. Turning one off removes what it stored in your browser.
  • Nasiko Cloud. Go to Settings > Privacy to change product analytics and marketing.
  • Browser signals. We honor Global Privacy Control and Do Not Track as described in Section 8.
  • Your choice is per browser. It is stored on your device, so you may need to set it again on another browser or device.

How to make a request. Email [email protected] or use Settings > Account in the app, including to opt out of sale or sharing. We will verify your identity and respond within the time the law requires: usually 30 days for GDPR requests and 45 days for California requests.

15. Children’s Privacy

Nasiko is a business product and is not directed at anyone under 18. We do not knowingly collect information from children. If you believe a child has given us personal information, contact us and we will delete it.

16. Limitation of Liability

To the extent the law allows, each party’s liability relating to this policy is subject to the limits set out in our Terms of Service or your organization’s agreement with us.

17. Changes to This Policy

We will post updates on this page and change the “Last updated” date at the top. For material changes, we will notify account holders by email or in the product before the changes take effect.

18. Contact Us

For questions, requests or complaints about this policy, contact:

CompanyNasiko Inc.
Address555 University Ave, Palo Alto, CA 94301
Email[email protected]
Grievance Officer (India)name and email
EU/UK representativename and address, if required

Address

555 University Ave
Palo Alto, CA 94301
United States

Platform

  • TokenOps
  • Multi-Agent Harness
  • Runtime Controls
  • LLM Router
  • MCP Gateway
  • Artifact Registry
  • Desktop app

Get started

  • For enterprise
  • Pricing
  • Free Agent Audit
  • Book a Demo
  • Login

Resources

  • Publications
  • Blogs
  • Docs
  • Security

Company

  • Events
  • About us
  • GitHub

© 2026 Nasiko. All rights reserved.·

  • Terms of Service
  • Privacy policy