Codename NikaLegal

Privacy Policy

Last updated: November 11, 2026

This policy explains what personal information Codename-Nika, Inc. collects when you use Nika and Capri, how we use and share it, how long we keep it, and the rights you have. If you have a question, email support@codename-nika.com.

Who we are and what this covers

Codename-Nika, Inc. (“Codename Nika”, “we”, “us”) makes Nika, an AI business platform, and Capri, a steering model for coding agents. This policy covers our website at www.codename-nika.com, Nika’s desktop and mobile apps, our APIs and Capri. We decide why and how personal information is used to provide these services, so we’re responsible for it as its controller.

Nika Browser has its own privacy notice, which also applies when you use it. Where the two differ, this Privacy Policy applies.

When our customers use Nika to keep information about other people, such as their leads, buyers, patients or the users of apps they build, we handle it for them: see Information our customers put into Nika.

This policy describes how Nika works today. Where something isn’t built yet, we say so.

Information we collect

From you

  • Account details: your name, email address, profile photo and sign-in activity, which our sign-in provider handles for us, and the companies and workspaces you belong to.
  • Profile and preferences: your Nika Social profile (such as your name, bio, age range, location, website, links, company, role, skills and interests), which is public by default; details you ask Nika to remember for filling in forms, such as your phone number and address; and your phone number if you text Nika.
  • Payments: our payment processor collects your card details, and we never receive your full card number. We keep records of what you buy, your credit balance and transactions, and the processor’s references to your customer record, subscriptions and payments. If you sell or receive payouts, the processor holds your payout account details. If an agent pays for something or signs up for a paid service for you (when that feature is switched on and you’ve allowed it), our payment processor issues a single-use card, and Nika passes the card’s details to the agent’s cloud browser to pay.
  • Your content: prompts, messages, files, images, video, audio, documents, projects, tasks and business records; what Nika makes for you, including the code and data of apps you build; and the record of what your Master Agent did (its goal, plan, steps and result).
  • Voice, images and video: recordings you make so Nika can turn them into text; a recording you use to create a voice clone; photos you use to create your avatar; video you provide for a video avatar, after we ask for your consent; your voice during voice calls with Nika’s AI voices, such as your Master Agent, which streams to our voice provider (Nika’s own systems keep only each call’s length and the credits it used; our voice provider keeps the call’s transcript, and its audio if recording is on, for the retention period set in our account with it); and transcripts, and sometimes recordings, of calls made by the AI caller and voice agents, of presentation calls, and of dictation.
  • Connected accounts: when you connect another service, the access it grants (tokens we keep in our database, most of them encrypted, or that our integrations provider holds for us), and the data Nika reads from or sends to that service at your direction. API keys and passwords you store in Nika are encrypted.
  • Messages to us: what you send our support team, and what you enter in our contact form (your name, email address and message).

When Nika acts for you

  • The pages Nika’s agents visit for you and what they type into forms. Our cloud browser provider records video of these sessions, unless a feature turns recording off.
  • If you use desktop computer use, screenshots of your screen go to AI providers so they can choose each step. Only the text of each step is stored, not the screenshots.
  • If you use the Accounts feature, Nika signs up for other services for you with an email inbox it gives you and, where a service asks for a phone number, a number from the phone account Nika set up for you (Nika buys one only if you allow it) or a mobile number you give it. It stores the passwords it generates encrypted (and, when switched on, in a password vault).
  • Nika may also create an account for you with one of its AI providers, using that inbox, so AI features can run in your browser. Nika keeps that account’s password encrypted (and, when switched on, in a password vault, and in your own vault if you’ve connected one) and stores its session encrypted.

Automatically

  • Technical information when you use our site and apps, such as your IP address, browser and device details, the pages and features you use, and the request logs our hosting provider keeps.
  • Cookies and similar technologies: see Cookies, analytics and the radio.

From other people and sources

  • People who invite you to a workspace, send you a document to sign, book time with you or call you through Nika give us your name and contact details.
  • Our sign-in provider and payment processor tell us about your account and payments.
  • Services you connect, and public sources Nika searches at your direction, such as websites, search engines and public business directories.

Information our customers put into Nika

Nika customers use Nika to keep and process information about other people, including business leads, creators they contact, their shops’ buyers, people who view their presentations or book time with them, people they call or meet, patients, support customers, people who sign documents they send, and the users of apps they build.

We handle this information for our customers and under their instructions, and each customer is responsible for having the right to use it. If your information is in a Nika customer’s account, please contact that customer. You can also email us at support@codename-nika.com, and we’ll pass your request on or help where we can.

Nika’s lead harvester gathers business contact details from public business directories and company websites. Other tools collect information about people at our customers’ direction: Nika Browser’s lead tool saves the people a web page shows (names, titles, email addresses, phone numbers and profile links); lead search looks people up in sales databases; and creator collabs read creators’ public profiles on social media and video platforms, including an email address shown in a bio or channel description.

Apps built with Nika may keep their users’ data in a database we manage for our customers, and some apps’ code and hosting run under our accounts.

How we use information

We use personal information to:

  • provide the services you ask for: run your account, AI features, agents, calls, apps and Capri (to perform our contract with you);
  • process payments, credits, subscriptions and payouts, and prevent fraud and payment abuse (contract; our legitimate interest in preventing fraud; legal obligations);
  • keep the services secure, enforce limits and investigate abuse (legitimate interests);
  • personalize Nika: your assistant remembers your conversations and preferences, including traits it infers about you (such as preferring short answers), and the results of your past runs shape your own future runs (contract; legitimate interests);
  • tell you about your account, purchases, security and changes to our services (contract; legitimate interests);
  • understand how our site is used, by counting visits, and improve it (legitimate interests);
  • comply with the law, respond to lawful requests, and protect the rights and safety of our users, the public and us (legal obligations; legitimate interests); and
  • do other things you agree to when we ask, such as creating a video avatar from your video (consent, which you can withdraw at any time).

Legal bases. If you’re in the European Economic Area, the United Kingdom or Switzerland, the words in parentheses are the legal bases we rely on: performing our contract with you, our legitimate interests (which we balance against your rights), our legal obligations, and your consent.

We don’t sell your personal information, and we don’t use it to show you ads.

AI features and model providers

When you use an AI feature, what it needs, such as your prompt, files, page text, screenshots or audio, is sent to an AI model provider to produce the result. Nika uses several providers and switches between them when one is unavailable or out of capacity, so a request may go to a different provider each time.

Some of the providers we fall back to are free services. Their terms may let them keep what they receive, or use it to improve their models. Don’t put information into AI features that you aren’t comfortable sending to these providers. Our providers are listed on our Sub-processors page.

Nika doesn’t train its own AI models on your content. The results of your runs are used only to improve your own future runs.

Model Mode. If you choose to train a model in Model Mode, the dataset you provide is stored with your files and sent to a model-hosting provider for training, in our managed account or in your own, and the trained model is saved privately.

Capri works differently: see Capri.

Cookies, analytics and the radio

Our site sets a small number of cookies on its own domain, to make it work and to keep payments safe. None of them is for advertising.

Cookies on our domain
Sign-in cookies (named by our sign-in provider)What it’s for: Keep you signed in, securelyHow long: Set by the provider
nika_memberWhat it’s for: Remembers that you’ve signed in before, so we can take you to sign inHow long: 1 year
nika_clone_doneWhat it’s for: Remembers that you finished setting up your digital cloneHow long: 1 year
nika_seen_landingWhat it’s for: Remembers that you’ve seen the welcome pageHow long: 1 year
nika_versionWhat it’s for: Remembers which version of Nika you pickedHow long: 30 days
nika_pickWhat it’s for: Remembers a choice you made on the welcome pageHow long: 1 day
nika_next, nika_founders_sessionWhat it’s for: Carry you through Founder’s Edition checkoutHow long: 1 hour
Account-connection cookies (such as oauth_…_verifier)What it’s for: Protect the step where you connect another serviceHow long: 10 to 15 minutes
Payment cookies (named by our payment processor, whose script sets them)What it’s for: Fraud prevention on pages where you can pay, such as Nika SocialHow long: Up to 1 year

Some features also keep settings in your browser’s storage, such as your light or dark theme and the radio’s station and volume.

Analytics. We use our hosting provider’s web analytics to count visits and see which pages are used. It runs on every page of our site, but not on self-hosted copies of Nika.

The radio. Our site’s radio is built on a video platform’s embedded player. On every page, the site loads that player in the background, before you press play. When it loads, the platform receives your IP address and information about your browser, and it may set its own cookies or similar identifiers under its own privacy policy. The platform may collect information about your activity over time and across different websites. We don’t receive what it collects. You can stop it setting cookies by blocking third-party cookies in your browser, or block the player entirely with a content blocker; the radio won’t play if you block it. The platform is named on our Sub-processors page.

Other features load scripts or images from other companies, such as maps in the real-estate tools, a voice widget when you start a voice chat, the AI tools that run in your browser, and stock images on some pages. Those companies receive your IP address and what the feature sends them. Our payment processor’s script loads with pages where you can pay, such as Nika Social, before you start a payment, and sets the payment cookies listed above. Our Sub-processors page lists these companies.

Apart from the radio’s player described above, we don’t put advertising cookies or ad trackers on our site. Our site doesn’t yet respond to Do Not Track or Global Privacy Control signals.

How we share information

We share personal information only in these ways:

  • Service providers that help us run Nika and Capri: hosting, databases, file storage, sign-in, payments, email, messaging and phone, AI models, media generation, cloud browsers and sandboxes, search, and integrations. We send each one what it needs for its work. They’re listed, with what each receives, on our Sub-processors page.
  • Free AI services: when our paid AI providers are unavailable, some features fall back to free AI services, which may keep or use what they receive under their own terms (see AI features and model providers).
  • People you choose to share with: members of your workspaces, people you send links, documents or messages to, the other party to a marketplace purchase, and everyone, for content you make public.
  • Apps you sign in to with Nika (“Sign in with Nika”) get only the information you approve, such as your name, email address, profile and brand details. If you approve sharing your clone avatar, the app gets a permanent public link to its image.
  • Services you connect, when Nika reads from or acts in them for you.
  • Legal and safety: when the law or legal process requires it, or to protect the rights, property or safety of our users, the public or us.
  • Business transfers: if we’re involved in a merger, acquisition, financing or sale of assets, as part of that deal and under this policy’s protections.

Share links. Some features make links that anyone with the link can open while it works, such as file links (which expire after 7 days), presentation and generation share links, and a live view of an agent’s cloud computer. Anyone who has such a link can see what it shows.

We don’t sell personal information.

How long we keep information

We keep personal information while your account is open and for as long as we need it for the purposes in this policy. Unless this policy gives a specific period, information stays until you delete it, where a feature lets you, or until we delete it at your request. We don’t yet delete inactive accounts automatically.

  • Files stay in storage until they’re deleted. Links to them expire after 7 days.
  • Records of payments, subscriptions and the terms you accepted are kept as long as we need them for accounting, tax and legal purposes.
  • Contact form messages and waitlist sign-ups are kept until you ask us to delete them.
  • Rate-limit counters are deleted after they expire.
  • Capri and Capri Shield have their own periods, set out in Capri and Capri Shield.

Our providers keep information under their own retention rules.

Security

We protect information with measures that include encryption in transit (HTTPS); AES-256-GCM encryption of the API keys you save, the passwords Nika generates and most connected accounts’ access tokens; per-record encryption of Capri session content; and storing Capri API keys only as hashes. File links expire after 7 days.

No system is perfectly secure. If you think your account or data is at risk, email us straight away. If a breach affects your personal information, we’ll tell you as the law requires.

International transfers

We’re based in the United States. Our main database and file storage are in the United States, and our hosting provider serves the site from locations around the world. Some of our providers, including some AI providers, may process information in other countries. Where we’ve confirmed a provider’s location, our Sub-processors page shows it.

If you’re in the European Economic Area, the United Kingdom or Switzerland, your information is transferred to the United States and to other countries whose data protection laws may differ from yours. Where the law requires safeguards for these transfers, we work to put them in place, such as the European Commission’s standard contractual clauses. You can ask for a copy of these safeguards by emailing support@codename-nika.com.

Your rights and choices

For everyone

  • You can see and change much of your information in Nika, delete individual items where a feature lets you, and download your files and documents.
  • There isn’t a self-serve tool yet to delete your whole account or to export all your data. Email us and we’ll do it for you. Deleting your sign-in profile on its own doesn’t delete your Nika data.
  • Voice clones. When you create a voice clone, your recording goes to our voice provider (or to your own account with it, if you’ve added your key), which keeps a voice model so Nika can speak in your voice. Nika keeps only an ID for it, and uses it only to speak in your voice in Nika, not to identify you. It stays until you ask us to delete it, including when you ask us to close your account. There isn’t a delete button yet: email us and we’ll delete it.
  • You can ask us to make your Nika Social profile private.

In the EEA, the UK and Switzerland

You have the right to access your personal information, correct it, delete it, restrict or object to how we use it (including where we rely on legitimate interests), receive it in a portable format, and withdraw consent at any time. You can also complain to your local data protection authority.

In California and other US states

If you live in California or another state with a consumer privacy law, you may have the right to know what personal information we collect, use and disclose (including specific pieces of it), to delete it, to correct it, to opt out of its sale, of its sharing for cross-context behavioral advertising and of targeted advertising, and not to be treated differently for using these rights. You can use an authorized agent to make a request.

We don’t sell personal information or use it for targeted advertising. The radio’s player may collect information directly from your browser while you’re on our site; Cookies, analytics and the radio explains it and how to block it.

In the past 12 months we collected these categories of personal information, from the sources and for the purposes this policy describes, and disclosed each of them to our service providers for those purposes and, when an AI feature falls back to a free AI service, to that service, which may keep or use what it receives under its own terms (see AI features and model providers): identifiers (such as your name, email address, IP address and account IDs); customer records (such as your phone number, address and payment records); commercial information (purchases, subscriptions and credits); internet or other electronic network activity (how you use our site and apps); audio and visual information (recordings, photos, video and screenshots); biometric information (the voice recordings you use for voice clones); professional information (such as your company and role); inferences (such as preferences your assistant infers); and sensitive personal information, described next.

We use sensitive personal information, such as the passwords Nika stores for accounts it creates for you, the contents of inboxes and messages Nika handles for you, health information and voice recordings, only to provide the services you ask for and for other purposes the law allows. We keep each category for the periods in How long we keep information.

How to make a request

Email support@codename-nika.com from the email address on your account and tell us what you’d like. We’ll check that the request comes from you before acting, respond within the time the law requires, and explain if we can’t do everything you asked. If we decline, you can reply to ask us to reconsider. If we still decline, we’ll explain why; in the US, you can then contact your state’s attorney general.

Children

Nika is for adults: you must be at least 18 to use it. We don’t knowingly collect personal information from anyone under 18. If you believe a child has given us personal information, email support@codename-nika.com and we’ll delete it.

Health information

Some Nika tools can store patient and health information that our customers enter. Unless we’ve signed a business associate agreement with you, don’t enter protected health information, as the U.S. HIPAA rules define it, into Nika.

Capri

This section covers Capri, Codename Nika’s steering model for coding agents, used through the Capri API, console, playground and hook pack.

What Capri receives

  • What your harness or the hook pack sends: the session’s goal; events from your coding agent, such as the files an edit touched and its line counts, the commands it ran (scrubbed, up to 300 characters) and their exit codes, test counts and failing test names, the files and folders it read, the patterns it listed files with, the web addresses it fetched (without query strings), its to-do list and its last message at each stop; plans; and the questions you ask Capri. With the hook pack, the goal is your first prompt, without code blocks, up to 2,000 characters.
  • The hook pack never sends file contents, diffs, command output (apart from test counts and failing test names), tool results, code blocks, the text of your later prompts, or web search queries.
  • Capri scrubs secrets, email addresses and phone numbers from that text before reading it.
  • Optional metadata you attach to a session, up to 2 KB, which a model never reads.
  • Your account and Basic subscription details, and your API keys, which we store only as hashes.

How Capri uses it

Only to answer your calls with predictions, notes, plans and decisions for that session, and to bill and secure your account. Capri doesn’t use your code or content to train any model, and it doesn’t pool your data with other accounts’ data. If we ever start pooling content-free outcome numbers across accounts (such as the kind of prediction made, its probability and whether it came true), we’ll update this policy first and give you a way to opt out.

Where it goes

Capri sends session content to one AI model provider, directly, on our account, tagged with a hashed account ID instead of your name or email address. It doesn’t fall back to other AI providers. Under its commercial terms, that provider doesn’t train its models on this content; it may keep it for up to 30 days, or up to 2 years if its safety systems flag a request, and a flagged request’s safety classification scores for up to 7 years.

Capri’s other processors are our database, hosting and file storage (file storage only for narration audio), our sign-in provider, our payment processor, our email provider (for allowance and webhook notices) and our voice provider (for narration audio and Talk to Capri, when they’re available to you). Narration audio sends the narration text Capri writes to the voice provider to be spoken. Talk to Capri runs on the voice provider’s agent platform: what you say on a call is transcribed and answered there by a language model the voice provider supplies, which may be another company’s model run through it. Apart from that, Capri uses no other AI provider and no background-job service. They’re listed on our Sub-processors page. Capri’s web pages, like the rest of our site, also load the radio’s player and our web analytics (see Cookies, analytics and the radio).

How long Capri keeps it

How long Capri keeps data
Session content: the goal, Capri’s memory of the run, plans, queued items and stored replies (sealed at rest, bound to the session and your account)How long it’s kept: An open session expires after 24 hours without events, and its content is erased then. After you close a session, its content stays for its retention days (7 unless you set 0 to 30), then it’s erased. With 0, it’s erased when you close the session.
Metadata you attach to a session (up to 2 KB, never read by a model, and not sealed, so keep secrets out of it)How long it’s kept: Erased with the session’s content.
A session’s record without its contentHow long it’s kept: Deleted 30 days after the session expires.
Stored replies for repeated requestsHow long it’s kept: 24 hours, and never longer than the session’s content.
Usage numbers (calls and credits, no content)How long it’s kept: 90 days.
Webhook payloadsHow long it’s kept: Sealed until delivery finishes, then erased. Delivery records are kept for 30 days.
Narration audio (not available yet)How long it’s kept: Served from a link that works for 24 hours; the file is deleted when the link expires.
Talk to Capri callsHow long it’s kept: Nika keeps no recording or transcript. The voice provider keeps its record of a call for at most a day. We keep the call’s numbers, such as its length and cost, for 90 days.
Overage records: the Nika credits set aside, drawn and returned, when you turned overage on or off, and the overage terms version you acceptedHow long it’s kept: Credits set aside for calls: 90 days after they’re used or returned. Records of Nika credits drawn and returned: 400 days (one waiting for review stays until it’s resolved). Your overage setting stays with your account.
Your Basic subscription records, including the terms version you accepted and whenHow long it’s kept: As long as we need them for accounting, tax and legal purposes.
Waitlist sign-ups (your email address, your account if you were signed in, and where you signed up)How long it’s kept: Until you ask us to delete them.

Content past its time isn’t served. Capri’s clean-up erases it on its next run; the clean-up runs as the service handles requests, not on a fixed timetable.

Deleting

You can delete a session at any time through the API or in the console. That erases its content, queued items, plans and stored replies at once; its usage numbers stay. You can do this even after Basic ends. There isn’t a way yet to delete all your Capri data at once: email us and we’ll do it.

Automatic pauses

If a Basic payment is disputed or flagged as likely fraud, Basic pauses on your account automatically. Email us and a person will review it.

Capri Shield

Capri Shield helps developers make their web apps harder to copy. This section is for developers who use it and for visitors to their sites. The site’s owner chooses to use Shield and is responsible for telling its visitors.

On a protected site

  • The site’s own code, not Nika, sets one first-party security cookie: a random session ID, with its times and, in Strict mode, the browser’s public signing key, signed by the site. It lasts up to 12 hours, scripts can’t read it, and it isn’t used for analytics or advertising. Nika never receives it.
  • In Strict mode, or while the site is testing it, the browser also keeps a private signing key for the session, which can’t be exported and is replaced with each new session.
  • The site’s server keeps short-lived counts by session and by a hash of the visitor’s address, in memory only, for an hour at most.

What reaches Nika

  • From a copy of a protected site on another address, each visitor’s browser sends Nika two requests once per browser session: a report with that address, the page’s path without its query, and the time; and a question about whether to show a copy notice. No cookies and no referrer are sent.
  • Each request reaches Nika from the visitor’s IP address. Nika uses it only as a daily-salted hash in an expiring rate-limit counter, never stored with a report. Our hosting provider’s request logs follow its own retention.
  • From the site owner’s servers: counts of refused requests by day, route pattern and reason, with no address, session, cookie, query or header.
  • Nika may fetch a reported page, at most once per address a day, to check whether it carries the site’s key.

What Nika keeps

  • Copy reports: one record per address a copy was seen on (the address, one sample path, a count, and the first and last time), while the site is registered. A report Nika never verified stops showing after 30 days without a new one. A verified copy also keeps its evidence: the address checked, when, and a hash of the page.
  • Refusal counts: 90 days.
  • When a site is removed, its counts and reports are deleted 30 days later.

What Shield never does

No fingerprinting, device attestation, third-party cookies or cross-site identifiers, mouse or keystroke tracking, session replay or user-agent profiling.

Why

We process this information to secure the protected site against automated copying and abuse, a legitimate interest in network and information security. For copy reports, we act on the site owner’s behalf.

Changes to this policy

We’ll post changes here and update the date at the top. If a change is material, we’ll tell you by email or in Nika before it takes effect.

Contact us

Codename-Nika, Inc.

Email: support@codename-nika.com

Privacy Policy | Codename Nika