From 47a584c05dd24347d8958888d2fedb4a896c0293 Mon Sep 17 00:00:00 2001 From: dunegxn Date: Mon, 17 Aug 2026 22:29:56 +0530 Subject: [PATCH 1/7] Blog:+allTypesOfeSIM --- app/blog/[slug]/page.tsx | 2 +- components/blog/callouts.tsx | 16 +- components/blog/mdx-components.tsx | 3 +- components/blog/post-card.tsx | 2 +- content/blog/all-kinds-of-no-kyc-esims.mdx | 82 +++++ public/blog/heroes/no-kyc-esims.svg | 341 +++++++++++++++++++++ 6 files changed, 442 insertions(+), 4 deletions(-) create mode 100644 content/blog/all-kinds-of-no-kyc-esims.mdx create mode 100644 public/blog/heroes/no-kyc-esims.svg diff --git a/app/blog/[slug]/page.tsx b/app/blog/[slug]/page.tsx index e26b655..718edb9 100644 --- a/app/blog/[slug]/page.tsx +++ b/app/blog/[slug]/page.tsx @@ -152,7 +152,7 @@ export default async function BlogPostPage({ params }: { params: Params }) { src={post.hero} alt="" fill - className="object-cover" + className="object-cover object-top" sizes="(min-width: 832px) 832px, 100vw" priority /> diff --git a/components/blog/callouts.tsx b/components/blog/callouts.tsx index e17d06e..84418ee 100644 --- a/components/blog/callouts.tsx +++ b/components/blog/callouts.tsx @@ -1,5 +1,5 @@ import type { ReactNode } from "react"; -import { Sun, TriangleAlert } from "lucide-react"; +import { Flashlight, Sun, TriangleAlert } from "lucide-react"; export function Tip({ children }: { children: ReactNode }) { return ( @@ -15,6 +15,20 @@ export function Tip({ children }: { children: ReactNode }) { ); } +export function Highlight({ children }: { children: ReactNode }) { + return ( +
+
+ ); +} + export function HeadsUp({ children }: { children: ReactNode }) { return (
diff --git a/components/blog/mdx-components.tsx b/components/blog/mdx-components.tsx index 6dd1b07..2020668 100644 --- a/components/blog/mdx-components.tsx +++ b/components/blog/mdx-components.tsx @@ -2,7 +2,7 @@ import type { AnchorHTMLAttributes, ImgHTMLAttributes } from "react"; import Link from "next/link"; import { InlineCTA } from "@/components/blog/inline-cta"; -import { Tip, HeadsUp } from "@/components/blog/callouts"; +import { Tip, HeadsUp, Highlight } from "@/components/blog/callouts"; import { Steps } from "@/components/blog/steps"; function SmartLink({ @@ -69,6 +69,7 @@ export function getMdxComponents(slug: string) { InlineCTA: () => , Tip, HeadsUp, + Highlight, Steps, }; } diff --git a/components/blog/post-card.tsx b/components/blog/post-card.tsx index 829cbb9..943c6d6 100644 --- a/components/blog/post-card.tsx +++ b/components/blog/post-card.tsx @@ -16,7 +16,7 @@ export function PostCard({ post }: { post: Post }) { alt="" fill sizes="(min-width: 640px) 256px, 100vw" - className="object-cover transition-transform duration-300 group-hover:scale-105" + className="object-cover object-top transition-transform duration-300 group-hover:scale-105" />
diff --git a/content/blog/all-kinds-of-no-kyc-esims.mdx b/content/blog/all-kinds-of-no-kyc-esims.mdx new file mode 100644 index 0000000..1d806c8 --- /dev/null +++ b/content/blog/all-kinds-of-no-kyc-esims.mdx @@ -0,0 +1,82 @@ +--- +title: "All types of No-KYC eSIMs" +description: "No-KYC is not one thing. An analysis of the categories of privacy-preserving eSIM providers, the layers they actually protect, and what none of them can claim." +date: "2026-08-17" +author: "arpit" +tag: "Privacy & Security" +hero: "/blog/heroes/no-kyc-esims.svg" +tldr: + - "No-KYC describes what a provider skips at signup, not what it protects afterwards." + - "Providers cluster into four approaches, each securing a different layer." + - "None of them make you anonymous: the carrier still sees the device, the network still logs an IP." + - "The useful question is which layer a given provider actually removes you from." +draft: false +--- + +Disclosure before anything else: we build one of the products described here. Read accordingly. + +This analysis was prompted by [a comparison of no-KYC eSIM providers posted on r/best_eSIM_providers](https://www.reddit.com/r/eSIMforTravelers/), written by someone who tested several over a few weeks and spent as much space on what these services *cannot* do as on what they can. That framing is the more valuable contribution, and it is the one this post tries to extend. + +For the purposes of this analysis, "no-KYC eSIM" refers to any mobile data service that provisions a profile (an eSIM plan or subscription) without collecting verified identity documents at purchase. That definition is narrow on purpose. It describes an absence at one moment and says nothing about what happens at every other layer, which is where most of the confusion in this category lives. + +## The layers, first + +A traveller's connectivity touches at least four distinct layers, and a provider may protect one while leaving the others entirely open: + +1. **Registration,** whether your legal identity is attached to the SIM at purchase. This is the layer "no-KYC" refers to. +2. **Account,** whether a durable record of you (email, login, order history, dashboard) exists on the provider's side after purchase. +3. **Payment,** whether the transaction can be traced to you through the rail used to pay. +4. **Network,** what the carrier and the exit route can observe once you are connected: device identifiers, IP, traffic metadata. + +Almost every disagreement about privacy eSIMs is a disagreement about which of these layers someone meant. + +## Four approaches + +Providers in this space cluster into recognisable groups. The categories below are approaches rather than brands; most real services combine two. + +**Anonymity-first, crypto-native.** Purchases in cryptocurrency, no account of consequence, coverage across most of the world with limited and costly plans, often with activation strings for degoogled devices. Strong at registration and payment; the trade is price and user experience. + +**Routing-focused.** Choose which carrier or country your traffic appears to come from. Strong at the network layer in the specific sense of decoupling your visible location from your physical one. Whether the exit is disclosed before purchase varies, and that variance matters more than it sounds: a foreign IP you cannot verify in advance is a claim, not a feature. + +**Privacy suites.** eSIM bundled with a VPN, virtual numbers, sometimes more. The appeal is coverage across several layers at once from one vendor. The cost is concentration: a single provider now sits at more of your stack, which is a reasonable trade only if you trust that provider more than the alternative. + +**Consumer-facing.** Card and wallet payments alongside crypto, an app rather than a dashboard, aimed at people who will never hold crypto, resulting in a well-established design for consumers. Strong at reach; historically the weakest at the technical rigor the other three compete on. This is the category we are in, and its central tension is stated plainly below. + +## What none of them can claim + +The Reddit comparison makes the point that most marketing in this category obscures: no-KYC is not anonymity. The carrier still sees the device identifier. The network layer still logs an IP. An eSIM adds no encryption to anything. + +What a no-KYC eSIM removes is your identity from the registration record and, if the provider routes traffic through a foreign exit, your real-country IP from the network's view. Encryption is a separate purchase, a VPN or proxy on top. Any provider implying otherwise is selling something. + +This distinction is worth holding firmly, because the alternative is a familiar failure. In its study *Smartphone as Lifeline*, Tactical Tech observes: + +> Identity is increasingly less a matter of what you say you are and more what a particular service provider says you are. + +A provider that overstates its protections is still the party defining you — only now with your confidence attached. + +## Two perspectives + +Following the structure that study uses, the category reads differently depending on where you stand. + +**The individual.** For a traveller, the practical question is not "is this anonymous" but "which record am I trying not to create?" Someone avoiding a foreign carrier's identity database has a different requirement from someone avoiding a correlation between their location and their home ISP. The four approaches above answer different questions, and the honest recommendation depends entirely on which one you are asking. + +**The structural.** Registration requirements are not distributed evenly. Those who can produce local ID on demand experience KYC as friction; those who cannot experience it as exclusion. The same study notes that mass analysis of mobile data during lockdowns revealed, in effect, who could afford to stay home and who could not. A reminder that connectivity data has never been socially neutral. Identity-free connectivity is, among other things, a way of not requiring people to be legible before they are allowed to connect. + +## Where Koki'o sits + +We are the consumer-facing category, and the central trade is deliberate: we accept cards, Apple Pay and Google Pay alongside crypto. That widens reach beyond people who already hold crypto, and it is the choice this audience will scrutinise hardest. It is also the choice we would make again, sovereignty that only reaches people who already understand wallets is not much of a sovereignty. + + + What we do differently sits at the **account** layer. There is no signup at + all: no name, no email, no KYC. Your account is a smart contract wallet + bound to your device's secure enclave via passkeys, so there is no password + to phish and no account record to subpoena or breach. + + +The architecture is the guarantee rather than the policy, and it is checkable, the [contracts and app are open source](https://github.com/Blockchain-Powered-eSIM/smart-contract-suite), enabled by a grant from [Ethereum Foundation PSE](https://pse.dev/) (Privacy Stewards of Ethereum) grant, audited by PSE and externally by CD Security, with a final audit in progress before mainnet. + +Beyond the architecture, the product itself is the point. Koki'o innovates as a consumer telecom application built around digital well-being practices. With a well-curated eSIM catalogue (cheap plans, unlimited plans, special regional plans) that travellers actually want, Koki'o sets users free to cross borders around the globe without worrying about connectivity roadblocks, and with sovereignty intact. Where the rest of this category asks you to choose between privacy and usability, we are working to make that choice unnecessary. + +The category does not need another provider claiming to solve everything. It needs providers stating precisely which layer they operate at, and being checkable about it. That is the standard the Reddit comparison applied, and it is the right one. + +*Quoted material in this post comes from* Smartphone as Lifeline: Designing Technology for a Changing World *by Stephanie Hankey, Cade Diehm, Rose Regina Lawrence and Marek Tuszynski, published free by Tactical Tech. Our own position is set out in full in the [Koki'o Manifesto](/manifesto).* diff --git a/public/blog/heroes/no-kyc-esims.svg b/public/blog/heroes/no-kyc-esims.svg new file mode 100644 index 0000000..b2862ed --- /dev/null +++ b/public/blog/heroes/no-kyc-esims.svg @@ -0,0 +1,341 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + From 70cf6bd1bf42d11a05055548c06d95ec04988cc5 Mon Sep 17 00:00:00 2001 From: dunegxn Date: Mon, 17 Aug 2026 22:34:00 +0530 Subject: [PATCH 2/7] +ManifestoWiredIn/blogs --- app/blog/page.tsx | 4 ++++ components/blog/manifesto-card.tsx | 34 ++++++++++++++++++++++++++++++ 2 files changed, 38 insertions(+) create mode 100644 components/blog/manifesto-card.tsx diff --git a/app/blog/page.tsx b/app/blog/page.tsx index 4194f3e..73f552c 100644 --- a/app/blog/page.tsx +++ b/app/blog/page.tsx @@ -2,7 +2,9 @@ import type { Metadata } from "next"; import Image from "next/image"; import { getAllPosts } from "@/lib/blog"; +import { getManifesto } from "@/lib/manifesto"; import { PostCard } from "@/components/blog/post-card"; +import { ManifestoCard } from "@/components/blog/manifesto-card"; import BeachFun from "@/assets/seb/Beach Fun.svg"; export const metadata: Metadata = { @@ -19,6 +21,7 @@ export const metadata: Metadata = { export default function BlogIndexPage() { const posts = getAllPosts(); + const manifesto = getManifesto(); return (
@@ -43,6 +46,7 @@ export default function BlogIndexPage() {
+ {posts.map((post) => ( ))} diff --git a/components/blog/manifesto-card.tsx b/components/blog/manifesto-card.tsx new file mode 100644 index 0000000..58ed248 --- /dev/null +++ b/components/blog/manifesto-card.tsx @@ -0,0 +1,34 @@ +import Image from "next/image"; +import Link from "next/link"; + +import type { Manifesto } from "@/lib/manifesto"; + +export function ManifestoCard({ manifesto }: { manifesto: Manifesto }) { + return ( + +
+ +
+
+ + Manifesto + +

+ {manifesto.title} +

+

+ {manifesto.description} +

+
+ + ); +} From 26f7c068f93bab514daf8d291f43c896cca3908a Mon Sep 17 00:00:00 2001 From: dunegxn Date: Tue, 18 Aug 2026 03:40:55 +0530 Subject: [PATCH 3/7] +blog3contentUpdate --- content/blog/all-kinds-of-no-kyc-esims.mdx | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/content/blog/all-kinds-of-no-kyc-esims.mdx b/content/blog/all-kinds-of-no-kyc-esims.mdx index 1d806c8..2f5c14a 100644 --- a/content/blog/all-kinds-of-no-kyc-esims.mdx +++ b/content/blog/all-kinds-of-no-kyc-esims.mdx @@ -73,10 +73,15 @@ We are the consumer-facing category, and the central trade is deliberate: we acc to phish and no account record to subpoena or breach. -The architecture is the guarantee rather than the policy, and it is checkable, the [contracts and app are open source](https://github.com/Blockchain-Powered-eSIM/smart-contract-suite), enabled by a grant from [Ethereum Foundation PSE](https://pse.dev/) (Privacy Stewards of Ethereum) grant, audited by PSE and externally by CD Security, with a final audit in progress before mainnet. +The architecture is the guarantee rather than the policy, and it is verifiable, Koki'o is based on [open source eSIM wallet smart contract suite](https://github.com/Blockchain-Powered-eSIM/smart-contract-suite), enabled by a grant on eSIM Wallet from [Ethereum Foundation PSE](https://pse.dev/) (Privacy Stewards of Ethereum), audited by PSE and externally by [CD Security](https://cdsecurity.io/), with a final in-house audit in progress before mainnet. -Beyond the architecture, the product itself is the point. Koki'o innovates as a consumer telecom application built around digital well-being practices. With a well-curated eSIM catalogue (cheap plans, unlimited plans, special regional plans) that travellers actually want, Koki'o sets users free to cross borders around the globe without worrying about connectivity roadblocks, and with sovereignty intact. Where the rest of this category asks you to choose between privacy and usability, we are working to make that choice unnecessary. +Beyond the architecture, the product itself is the point. Koki'o innovates as a consumer telecom application built around consumer data security practices for digital well-being. +- Onboarding and wallet usage via biometrics(secured in your mobile hardware), +- Well-curated eSIM catalogue (cheap plans, unlimited plans, special regional plans) that travellers actually want, +- Seamless activation with friendly and practical design mechanism, + +Koki'o sets users free to cross borders around the globe without worrying about connectivity roadblocks, and with sovereignty intact. Where the rest of this category asks you to choose between privacy and usability, we are working to make that choice unnecessary. The category does not need another provider claiming to solve everything. It needs providers stating precisely which layer they operate at, and being checkable about it. That is the standard the Reddit comparison applied, and it is the right one. -*Quoted material in this post comes from* Smartphone as Lifeline: Designing Technology for a Changing World *by Stephanie Hankey, Cade Diehm, Rose Regina Lawrence and Marek Tuszynski, published free by Tactical Tech. Our own position is set out in full in the [Koki'o Manifesto](/manifesto).* +*Quoted material in this post comes from* Smartphone as Lifeline: Designing Technology for a Changing World *by Stephanie Hankey, Cade Diehm, Rose Regina Lawrence and Marek Tuszynski, published free by Tactical Tech, a must read btw. Our own position is set out in full in the [Koki'o Manifesto](/manifesto).* From 14f86af751c72671ef8bd590525e0d229ef8778c Mon Sep 17 00:00:00 2001 From: dunegxn Date: Wed, 19 Aug 2026 07:48:06 +0530 Subject: [PATCH 4/7] Blog:+updatedBlog3 --- components/blog/manifesto-cta.tsx | 44 ++++++++++++ components/blog/mdx-components.tsx | 2 + content/blog/all-kinds-of-no-kyc-esims.mdx | 82 ++++++++++++++-------- 3 files changed, 99 insertions(+), 29 deletions(-) create mode 100644 components/blog/manifesto-cta.tsx diff --git a/components/blog/manifesto-cta.tsx b/components/blog/manifesto-cta.tsx new file mode 100644 index 0000000..f075a3d --- /dev/null +++ b/components/blog/manifesto-cta.tsx @@ -0,0 +1,44 @@ +import Image from "next/image"; +import Link from "next/link"; +import { ArrowRight } from "lucide-react"; + +/** Teaser card for /manifesto, dropped into blog posts that reference it. + * Carries the meadow background from the manifesto page itself (behind a + * frosted sand panel, same trick as ManifestoShell) so the click-through + * reads as a continuation of that page rather than a footnote link out. */ +export function ManifestoCTA() { + return ( + + +
+ + The Koki'o Manifesto + +

+ Connectivity is a human right. Privacy is its guardian. +

+

+ Koki'o is also a provider, and we say it upfront: don't + trust Koki'o, verify it. This is our position, written out in + full. +

+ + Read the Manifesto + +
+ + ); +} diff --git a/components/blog/mdx-components.tsx b/components/blog/mdx-components.tsx index 2020668..50b280e 100644 --- a/components/blog/mdx-components.tsx +++ b/components/blog/mdx-components.tsx @@ -4,6 +4,7 @@ import Link from "next/link"; import { InlineCTA } from "@/components/blog/inline-cta"; import { Tip, HeadsUp, Highlight } from "@/components/blog/callouts"; import { Steps } from "@/components/blog/steps"; +import { ManifestoCTA } from "@/components/blog/manifesto-cta"; function SmartLink({ href = "", @@ -71,5 +72,6 @@ export function getMdxComponents(slug: string) { HeadsUp, Highlight, Steps, + ManifestoCTA, }; } diff --git a/content/blog/all-kinds-of-no-kyc-esims.mdx b/content/blog/all-kinds-of-no-kyc-esims.mdx index 2f5c14a..1994976 100644 --- a/content/blog/all-kinds-of-no-kyc-esims.mdx +++ b/content/blog/all-kinds-of-no-kyc-esims.mdx @@ -13,58 +13,64 @@ tldr: draft: false --- -Disclosure before anything else: we build one of the products described here. Read accordingly. +Someone on Reddit recently [compared the major no-KYC eSIM providers](https://www.reddit.com/r/eSIMforTravelers/) after testing them properly over a few weeks, and spent as much space on what these services *cannot* do as on what they can. That honesty is the more valuable half of the post, and it is the half this analysis tries to extend. -This analysis was prompted by [a comparison of no-KYC eSIM providers posted on r/best_eSIM_providers](https://www.reddit.com/r/eSIMforTravelers/), written by someone who tested several over a few weeks and spent as much space on what these services *cannot* do as on what they can. That framing is the more valuable contribution, and it is the one this post tries to extend. +Be mindful as you read, we build one of the products in this category, and we brief on Koki'o later in this post. -For the purposes of this analysis, "no-KYC eSIM" refers to any mobile data service that provisions a profile (an eSIM plan or subscription) without collecting verified identity documents at purchase. That definition is narrow on purpose. It describes an absence at one moment and says nothing about what happens at every other layer, which is where most of the confusion in this category lives. +For the purposes of this analysis, "no-KYC eSIM" means any mobile data service that provisions a profile (an eSIM plan or subscription). In simple terms, "without any knowledge of the consumer", or "the provider literally doesn't know you". So, without collecting any personal information, without creating a profile, and without verified identity documents at purchase. + +Of course, that definition is narrow on purpose. Various providers describe it in different words depending on how their system is built, sometimes even for the same setup. + +Mainly, it describes an absence at one moment, and says nothing about what happens at every other layer. Which is where most of the confusion in this category lives. ## The layers, first -A traveller's connectivity touches at least four distinct layers, and a provider may protect one while leaving the others entirely open: +A traveller's connectivity touches at least four distinct layers, and a provider can protect one while leaving the rest wide open: -1. **Registration,** whether your legal identity is attached to the SIM at purchase. This is the layer "no-KYC" refers to. -2. **Account,** whether a durable record of you (email, login, order history, dashboard) exists on the provider's side after purchase. -3. **Payment,** whether the transaction can be traced to you through the rail used to pay. +1. **Registration & Authentication,** whether your legal identity is attached to the SIM at purchase. This is the layer "no-KYC" refers to. +2. **Account,** whether a durable record of you (email, login, order history, dashboard) exists on the provider's side afterwards. +3. **Payment,** whether the transaction can be traced back to you through the rail you paid with. 4. **Network,** what the carrier and the exit route can observe once you are connected: device identifiers, IP, traffic metadata. -Almost every disagreement about privacy eSIMs is a disagreement about which of these layers someone meant. +Almost every argument about privacy eSIMs is really an argument about which of these four layers someone meant. ## Four approaches -Providers in this space cluster into recognisable groups. The categories below are approaches rather than brands; most real services combine two. +Providers cluster into recognisable groups. These are approaches rather than brands, and most real services combine two of them. -**Anonymity-first, crypto-native.** Purchases in cryptocurrency, no account of consequence, coverage across most of the world with limited and costly plans, often with activation strings for degoogled devices. Strong at registration and payment; the trade is price and user experience. +**Anonymity-first, crypto-native.** Payment in cryptocurrency, no account worth the name, coverage across most of the world with limited and costly plans, often with activation strings for degoogled devices. Strong at registration and payment. The trade is price and user experience. -**Routing-focused.** Choose which carrier or country your traffic appears to come from. Strong at the network layer in the specific sense of decoupling your visible location from your physical one. Whether the exit is disclosed before purchase varies, and that variance matters more than it sounds: a foreign IP you cannot verify in advance is a claim, not a feature. +**Routing-focused.** You choose which carrier or country your traffic appears to come from. Strong at the network layer, decoupling your visible location from your physical one. Make sure to check which country you'll exit from before you pay, since in some cases you only find out after activation. A foreign IP you can't verify in advance is a claim, not a feature. -**Privacy suites.** eSIM bundled with a VPN, virtual numbers, sometimes more. The appeal is coverage across several layers at once from one vendor. The cost is concentration: a single provider now sits at more of your stack, which is a reasonable trade only if you trust that provider more than the alternative. +**Privacy suites.** An eSIM bundled with a VPN, virtual numbers, sometimes more. The appeal is covering several layers at once from one provider. The cost is concentration: that provider now sits across more of your stack, which is only a good trade if you trust them more than you trust the alternatives. -**Consumer-facing.** Card and wallet payments alongside crypto, an app rather than a dashboard, aimed at people who will never hold crypto, resulting in a well-established design for consumers. Strong at reach; historically the weakest at the technical rigor the other three compete on. This is the category we are in, and its central tension is stated plainly below. +**Consumer-facing.** Card and wallet payments alongside crypto, an app rather than a dashboard, built for people who will never hold crypto, and because of that, usually the most considered design in the category. Strong at reach. Historically the weakest at the technical rigour the other three compete on. This is our category, and its central tension is stated plainly further down. ## What none of them can claim -The Reddit comparison makes the point that most marketing in this category obscures: no-KYC is not anonymity. The carrier still sees the device identifier. The network layer still logs an IP. An eSIM adds no encryption to anything. +Here is the part most marketing in this category quietly skips, and the part the Reddit post got right: **no-KYC is not anonymity.** + +The carrier still sees the device identifier. The network layer still logs an IP. An eSIM adds no encryption to anything. -What a no-KYC eSIM removes is your identity from the registration record and, if the provider routes traffic through a foreign exit, your real-country IP from the network's view. Encryption is a separate purchase, a VPN or proxy on top. Any provider implying otherwise is selling something. +What a no-KYC eSIM actually removes is your identity from the registration record and, if the provider routes traffic through a foreign exit, your real-country IP from the network's view. Encryption is a separate purchase, a VPN or proxy on top. Any provider implying otherwise is selling you something. -This distinction is worth holding firmly, because the alternative is a familiar failure. In its study *Smartphone as Lifeline*, Tactical Tech observes: +This distinction is worth holding onto, because the alternative is a familiar failure. In its study [*Smartphone as Lifeline*, Tactical Tech observes](https://cdn.ttc.io/s/tacticaltech.org/smartphone-as-lifeline.pdf): > Identity is increasingly less a matter of what you say you are and more what a particular service provider says you are. -A provider that overstates its protections is still the party defining you — only now with your confidence attached. +A provider that overstates its protections is still the party defining you. Only now with your confidence attached. ## Two perspectives -Following the structure that study uses, the category reads differently depending on where you stand. +Following the structure that study uses, this category reads differently depending on where you are standing. -**The individual.** For a traveller, the practical question is not "is this anonymous" but "which record am I trying not to create?" Someone avoiding a foreign carrier's identity database has a different requirement from someone avoiding a correlation between their location and their home ISP. The four approaches above answer different questions, and the honest recommendation depends entirely on which one you are asking. +**The individual.** For a traveller, the useful question is not "is this anonymous" but "which record am I trying not to create?" Avoiding a foreign carrier's identity database is a different requirement from avoiding a link between your location and your home ISP. The four approaches answer different questions, and the honest recommendation depends entirely on which one you are asking. -**The structural.** Registration requirements are not distributed evenly. Those who can produce local ID on demand experience KYC as friction; those who cannot experience it as exclusion. The same study notes that mass analysis of mobile data during lockdowns revealed, in effect, who could afford to stay home and who could not. A reminder that connectivity data has never been socially neutral. Identity-free connectivity is, among other things, a way of not requiring people to be legible before they are allowed to connect. +**The structural.** Registration requirements are not felt evenly. If you can produce local ID on demand, KYC is friction. If you cannot, it is exclusion. The same study notes that mass analysis of mobile data during lockdowns showed, in effect, who could afford to stay home and who could not, a reminder that connectivity data has never been socially neutral. Identity-free connectivity is, among other things, a way of not requiring people to be legible before they are allowed to connect. ## Where Koki'o sits -We are the consumer-facing category, and the central trade is deliberate: we accept cards, Apple Pay and Google Pay alongside crypto. That widens reach beyond people who already hold crypto, and it is the choice this audience will scrutinise hardest. It is also the choice we would make again, sovereignty that only reaches people who already understand wallets is not much of a sovereignty. +We are the consumer-facing category, and our central trade is deliberate: we accept cards, Apple Pay and Google Pay alongside crypto. That widens reach well beyond people who already hold crypto, and it is the choice this audience will scrutinise hardest. It is also the choice we would make again. Sovereignty that only reaches people who already understand wallets is not much of a sovereignty. What we do differently sits at the **account** layer. There is no signup at @@ -73,15 +79,33 @@ We are the consumer-facing category, and the central trade is deliberate: we acc to phish and no account record to subpoena or breach. -The architecture is the guarantee rather than the policy, and it is verifiable, Koki'o is based on [open source eSIM wallet smart contract suite](https://github.com/Blockchain-Powered-eSIM/smart-contract-suite), enabled by a grant on eSIM Wallet from [Ethereum Foundation PSE](https://pse.dev/) (Privacy Stewards of Ethereum), audited by PSE and externally by [CD Security](https://cdsecurity.io/), with a final in-house audit in progress before mainnet. +The architecture is the guarantee rather than the policy, and it is verifiable. Koki'o is built on an [open source eSIM wallet smart contract suite](https://github.com/Blockchain-Powered-eSIM/smart-contract-suite), enabled by an eSIM Wallet grant from [Ethereum Foundation PSE](https://pse.dev/) (Privacy Stewards of Ethereum), audited by PSE and externally by [CD Security](https://cdsecurity.io/), with a final in-house audit in progress before mainnet. + +Beyond the architecture, the product is the point. Koki'o is a consumer telecom app built around data security practices for digital well-being: + +- onboarding and wallet usage through biometrics, secured in your phone's own hardware +- a curated eSIM catalogue with cheap plans, unlimited plans and special regional plans that travellers actually want +- activation in a few taps, nothing to study first +- and more . . . 👀 + +The point of all of it is that you can cross borders without worrying about connectivity roadblocks, and without giving up sovereignty to do it. Where the rest of this category asks you to choose between privacy and usability, we are trying to make that choice unnecessary. + +## Test it, and tell us what's missing + +We are early, and we would rather build from what testers ask for than from what we assume. The Android app is live, iOS lands shortly. + +What we don't know is the rest. So, what would you add? What would make you switch, and what would stop you? If something breaks, tell us. If it works, we did our job well! + +## The standard worth keeping + +This category does not need another provider claiming to solve everything. It needs providers stating precisely which layer they operate at, and being checkable about it. That is the standard the Reddit post applied, and it is the right one. + +And if you have tested the others, we would like to know one thing above all: what would a provider have to disclose before you believed them? That answer shapes what we build next more than any roadmap does. -Beyond the architecture, the product itself is the point. Koki'o innovates as a consumer telecom application built around consumer data security practices for digital well-being. -- Onboarding and wallet usage via biometrics(secured in your mobile hardware), -- Well-curated eSIM catalogue (cheap plans, unlimited plans, special regional plans) that travellers actually want, -- Seamless activation with friendly and practical design mechanism, +*Now,* -Koki'o sets users free to cross borders around the globe without worrying about connectivity roadblocks, and with sovereignty intact. Where the rest of this category asks you to choose between privacy and usability, we are working to make that choice unnecessary. +Koki'o is also a provider, and we say it upfront: *"Don't trust, but verify.* -The category does not need another provider claiming to solve everything. It needs providers stating precisely which layer they operate at, and being checkable about it. That is the standard the Reddit comparison applied, and it is the right one. + -*Quoted material in this post comes from* Smartphone as Lifeline: Designing Technology for a Changing World *by Stephanie Hankey, Cade Diehm, Rose Regina Lawrence and Marek Tuszynski, published free by Tactical Tech, a must read btw. Our own position is set out in full in the [Koki'o Manifesto](/manifesto).* +*Quoted material in this post comes from* [Smartphone as Lifeline: Designing Technology for a Changing World](https://cdn.ttc.io/s/tacticaltech.org/smartphone-as-lifeline.pdf) *by Stephanie Hankey, Cade Diehm, Rose Regina Lawrence and Marek Tuszynski, published free by Tactical Tech, a must read btw.* From e895bc6de053321c87357581eba3b566bece9268 Mon Sep 17 00:00:00 2001 From: dunegxn Date: Wed, 19 Aug 2026 19:44:55 +0530 Subject: [PATCH 5/7] Blog:+mentionedChanges --- content/blog/all-kinds-of-no-kyc-esims.mdx | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/content/blog/all-kinds-of-no-kyc-esims.mdx b/content/blog/all-kinds-of-no-kyc-esims.mdx index 1994976..d5d0c2b 100644 --- a/content/blog/all-kinds-of-no-kyc-esims.mdx +++ b/content/blog/all-kinds-of-no-kyc-esims.mdx @@ -13,9 +13,9 @@ tldr: draft: false --- -Someone on Reddit recently [compared the major no-KYC eSIM providers](https://www.reddit.com/r/eSIMforTravelers/) after testing them properly over a few weeks, and spent as much space on what these services *cannot* do as on what they can. That honesty is the more valuable half of the post, and it is the half this analysis tries to extend. +Someone on Reddit recently [compared the major no-KYC eSIM providers](https://www.reddit.com/r/best_eSIM_providers/comments/1v2dbtd/compared_major_nokyc_esim_providers_sharing/) after testing them properly over a few weeks, and spent as much space on what these services *cannot* do as on what they can. That honesty is the more valuable half of the post, and it is the half this analysis tries to extend. -Be mindful as you read, we build one of the products in this category, and we brief on Koki'o later in this post. +Disclosure before anything else: we build one of the products described here. Read accordingly. For the purposes of this analysis, "no-KYC eSIM" means any mobile data service that provisions a profile (an eSIM plan or subscription). In simple terms, "without any knowledge of the consumer", or "the provider literally doesn't know you". So, without collecting any personal information, without creating a profile, and without verified identity documents at purchase. @@ -38,13 +38,13 @@ Almost every argument about privacy eSIMs is really an argument about which of t Providers cluster into recognisable groups. These are approaches rather than brands, and most real services combine two of them. -**Anonymity-first, crypto-native.** Payment in cryptocurrency, no account worth the name, coverage across most of the world with limited and costly plans, often with activation strings for degoogled devices. Strong at registration and payment. The trade is price and user experience. +**Anonymity-first, crypto-native.** Payment in cryptocurrency, no account with PII(personal identifying information), coverage across most of the world with limited and costly plans, often with activation strings for degoogled devices. Strong at registration and payment. The trade is price and user experience. **Routing-focused.** You choose which carrier or country your traffic appears to come from. Strong at the network layer, decoupling your visible location from your physical one. Make sure to check which country you'll exit from before you pay, since in some cases you only find out after activation. A foreign IP you can't verify in advance is a claim, not a feature. **Privacy suites.** An eSIM bundled with a VPN, virtual numbers, sometimes more. The appeal is covering several layers at once from one provider. The cost is concentration: that provider now sits across more of your stack, which is only a good trade if you trust them more than you trust the alternatives. -**Consumer-facing.** Card and wallet payments alongside crypto, an app rather than a dashboard, built for people who will never hold crypto, and because of that, usually the most considered design in the category. Strong at reach. Historically the weakest at the technical rigour the other three compete on. This is our category, and its central tension is stated plainly further down. +**Consumer-facing.** Card and wallet payments alongside crypto, an app rather than a dashboard, built for people who will never hold crypto, and because of that, most widespread design in the industry. Strong at reach. Historically the weakest at the technical rigour the other three compete on. This is our category, and its central tension is stated plainly further down. ## What none of them can claim @@ -64,13 +64,13 @@ A provider that overstates its protections is still the party defining you. Only Following the structure that study uses, this category reads differently depending on where you are standing. -**The individual.** For a traveller, the useful question is not "is this anonymous" but "which record am I trying not to create?" Avoiding a foreign carrier's identity database is a different requirement from avoiding a link between your location and your home ISP. The four approaches answer different questions, and the honest recommendation depends entirely on which one you are asking. +**The individual.** For a traveller, the useful question is not "is this anonymous" but "which record am I trying not to create?" Avoiding a foreign carrier's identity database is a different requirement from avoiding a link between your location and your home ISP(Internet Service Provider). The four approaches answer different questions, and the honest recommendation depends entirely on which one you are asking. -**The structural.** Registration requirements are not felt evenly. If you can produce local ID on demand, KYC is friction. If you cannot, it is exclusion. The same study notes that mass analysis of mobile data during lockdowns showed, in effect, who could afford to stay home and who could not, a reminder that connectivity data has never been socially neutral. Identity-free connectivity is, among other things, a way of not requiring people to be legible before they are allowed to connect. +**The structural.** Registration requirements are not felt evenly. If you can produce local ID on demand, KYC is friction. If you cannot, it is exclusion. The same study notes that mass analysis of mobile data during lockdowns showed, in effect, who could afford to stay home and who could not, a reminder that data connectivity has never been socially neutral. Identity-free connectivity is, among other things, a way of not requiring people to be legible before they are allowed to connect. ## Where Koki'o sits -We are the consumer-facing category, and our central trade is deliberate: we accept cards, Apple Pay and Google Pay alongside crypto. That widens reach well beyond people who already hold crypto, and it is the choice this audience will scrutinise hardest. It is also the choice we would make again. Sovereignty that only reaches people who already understand wallets is not much of a sovereignty. +We are the consumer-facing category, Self-sovereign and our central trade is deliberate: we accept cards, Apple Pay and Google Pay alongside crypto. That widens reach well beyond people who already hold crypto, it is a deliberate choice to cater to a larger audience in lieu of a more anonymous and technically stricter architecture. What we do differently sits at the **account** layer. There is no signup at @@ -92,7 +92,7 @@ The point of all of it is that you can cross borders without worrying about conn ## Test it, and tell us what's missing -We are early, and we would rather build from what testers ask for than from what we assume. The Android app is live, iOS lands shortly. +We are early, and we would rather build from what testers ask for than from what we assume. The Android app is live, iOS lands shortly. Find the link to early access at the bottom of this page. What we don't know is the rest. So, what would you add? What would make you switch, and what would stop you? If something breaks, tell us. If it works, we did our job well! @@ -104,7 +104,7 @@ And if you have tested the others, we would like to know one thing above all: wh *Now,* -Koki'o is also a provider, and we say it upfront: *"Don't trust, but verify.* +Koki'o is also a provider, and we say it upfront: *"Don't trust, but verify."* From 2aa0d127bfcbd02a265589302c0939e6c83544c9 Mon Sep 17 00:00:00 2001 From: dunegxn Date: Wed, 19 Aug 2026 23:48:08 +0530 Subject: [PATCH 6/7] Blog:+fix --- content/blog/all-kinds-of-no-kyc-esims.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/all-kinds-of-no-kyc-esims.mdx b/content/blog/all-kinds-of-no-kyc-esims.mdx index d5d0c2b..8f3f91f 100644 --- a/content/blog/all-kinds-of-no-kyc-esims.mdx +++ b/content/blog/all-kinds-of-no-kyc-esims.mdx @@ -15,7 +15,7 @@ draft: false Someone on Reddit recently [compared the major no-KYC eSIM providers](https://www.reddit.com/r/best_eSIM_providers/comments/1v2dbtd/compared_major_nokyc_esim_providers_sharing/) after testing them properly over a few weeks, and spent as much space on what these services *cannot* do as on what they can. That honesty is the more valuable half of the post, and it is the half this analysis tries to extend. -Disclosure before anything else: we build one of the products described here. Read accordingly. +Be mindful as you read, we build one of the products in this category, and we brief on Koki'o later in this post. For the purposes of this analysis, "no-KYC eSIM" means any mobile data service that provisions a profile (an eSIM plan or subscription). In simple terms, "without any knowledge of the consumer", or "the provider literally doesn't know you". So, without collecting any personal information, without creating a profile, and without verified identity documents at purchase. From 4bfeccad242f55b22c87b6a0bf884a7d58731c58 Mon Sep 17 00:00:00 2001 From: dunegxn Date: Thu, 20 Aug 2026 00:18:15 +0530 Subject: [PATCH 7/7] Blog:+androidAppCTA --- components/blog/app-download-cta.tsx | 59 ++++++++++++++++++++++ components/blog/mdx-components.tsx | 2 + content/blog/all-kinds-of-no-kyc-esims.mdx | 4 +- 3 files changed, 64 insertions(+), 1 deletion(-) create mode 100644 components/blog/app-download-cta.tsx diff --git a/components/blog/app-download-cta.tsx b/components/blog/app-download-cta.tsx new file mode 100644 index 0000000..2b3078f --- /dev/null +++ b/components/blog/app-download-cta.tsx @@ -0,0 +1,59 @@ +import Image from "next/image"; +import { ArrowRight } from "lucide-react"; + +import Logomark from "@/assets/logomark.svg"; + +const PLAY_STORE_URL = + "https://play.google.com/store/apps/details?id=app.kokio.mobile"; + +/** Download card for the Android app, dropped into blog posts that mention + * it. Mirrors ManifestoCTA's image + frosted-panel structure, but the image + * is the same beach-scene art behind the homepage hero (see components/hero.tsx) + * — clouds ~y0-600, ocean band ~y995-1120, sand + a bucket shape from ~y1120 + * down to ~y1582 (out of a 2068-tall viewBox). At the frosted panel's usual + * height, object-top only shows plain sky, so the crop is pulled down to + * ~58% to land on the ocean-to-sand-and-bucket band instead. */ +export function AppDownloadCTA() { + return ( + + +
+ + + Koki'o on Android + +

+ Koki'o is live on Android — iOS lands shortly. +

+

+ Pick a plan that fits how you travel in over 200 countries. Pay + with crypto or card, no KYC, no data collection. Simple, private + and secure. +

+ + Get it on Google Play + +
+ + ); +} diff --git a/components/blog/mdx-components.tsx b/components/blog/mdx-components.tsx index 50b280e..f2d37b6 100644 --- a/components/blog/mdx-components.tsx +++ b/components/blog/mdx-components.tsx @@ -5,6 +5,7 @@ import { InlineCTA } from "@/components/blog/inline-cta"; import { Tip, HeadsUp, Highlight } from "@/components/blog/callouts"; import { Steps } from "@/components/blog/steps"; import { ManifestoCTA } from "@/components/blog/manifesto-cta"; +import { AppDownloadCTA } from "@/components/blog/app-download-cta"; function SmartLink({ href = "", @@ -73,5 +74,6 @@ export function getMdxComponents(slug: string) { Highlight, Steps, ManifestoCTA, + AppDownloadCTA, }; } diff --git a/content/blog/all-kinds-of-no-kyc-esims.mdx b/content/blog/all-kinds-of-no-kyc-esims.mdx index 8f3f91f..7cace74 100644 --- a/content/blog/all-kinds-of-no-kyc-esims.mdx +++ b/content/blog/all-kinds-of-no-kyc-esims.mdx @@ -92,7 +92,9 @@ The point of all of it is that you can cross borders without worrying about conn ## Test it, and tell us what's missing -We are early, and we would rather build from what testers ask for than from what we assume. The Android app is live, iOS lands shortly. Find the link to early access at the bottom of this page. +We are early, and we would rather build from what testers ask for than from what we assume. + + What we don't know is the rest. So, what would you add? What would make you switch, and what would stop you? If something breaks, tell us. If it works, we did our job well!