Privacy Policy

1. Who we are

"Sokudo" (also referred to as "we", "us", or "our") provides an agentic IDE that lets developers plan, break down, and ship software alongside AI agents, and sells Sokudo merchandise through the Sokudo Shop. This policy applies to the Sokudo marketing website (including the Shop at sokudo.dev/shop), the Sokudo desktop application, and the backend services that power them (together, the "Services").

If you have any questions about this policy or how we handle your data, contact us at support@sokudo.dev.

2. Information we collect

We collect only what we need to operate the Services. Specifically:

Account information. When you sign in with a third-party identity provider (GitHub, GitLab, or Bitbucket), we receive your name, email address, profile image, a stable user identifier from that provider, and the OAuth tokens needed to maintain your session. We store this information in our authentication database.

Session information. We create a session record when you sign in. Each session stores the session token, the IP address you signed in from, your browser or desktop user-agent string, and the session's expiry. We use this information to keep you signed in and to detect abuse.

Beta access records. During our earlier private beta, accounts were placed on a waitlist. We retain those records (your account identifier and an access status) until they are deleted along with your account.

Workspace content. If you use the desktop application, you can create workspaces that contain tasks, chats, notes, custom AI agents, knowledge items, and rules. Most of this content is stored on our servers so that it is available across devices. Specifically, we store:

• Workspace metadata (name, description, indexing status).
• Tasks and kanban data (titles, descriptions, labels, columns, comments, activity).
• Chat history (messages, message blocks, attachments, the AI model selected, and token-usage metadata).
• Memory entries and summaries generated by agents.
• Custom agents, rules, and knowledge items you create.

Source-code index. When you index a workspace, your desktop app sends file paths and file contents to our server. The server splits the content into chunks, generates vector embeddings using a third-party embedding model (see "Service providers and other recipients" below), and stores those embeddings in a vector database. We do not retain the original source-code text after the embedding step; only the vector representations and a chunk identifier are kept.

Token-usage metadata. When you run an AI agent through Sokudo, we record metadata about each call: which CLI and model were used, input/output token counts, cache statistics, latency, the workspace and chat it belonged to, and an estimated cost in USD. We do not record the prompt or completion text in this metadata.

Telemetry (opt-in). The desktop application can send anonymous engine telemetry — for example, sandbox-environment startup timings and error categories — to our collector service. Telemetry is off by default until you enable it, can be turned off at any time from inside the desktop app, and is tagged with an anonymous install identifier rather than your user account. Telemetry records are retained for up to 90 days.

Shop orders. If you buy from the Sokudo Shop, we collect the contact and delivery details you enter at checkout and a record of your order. Section 5 explains what we collect, why, and who receives it.

Website analytics (only if you accept). If you accept optional analytics on our website, Google Analytics and the Meta Pixel collect information about your visits, and our server reports your confirmed Shop purchases to Google and Meta. If you decline, or never make a choice, none of this happens. Section 6 explains what is collected and how to change your mind.

Support correspondence. If you email us, we keep your message and our reply so we can follow up.

3. What stays on your device

The Sokudo desktop application is a hybrid local/server product. The following information stays on your machine and is never transmitted to our servers unless you take a specific action that requires it:

• The contents of files in your local working directory, until you explicitly trigger indexing for that workspace.
• Drafts of chat messages you have not yet sent.
• Local development-environment state (containers, sandboxes, Docker Compose files, virtual-machine state).
• Cached telemetry batches when telemetry is disabled — they are wiped immediately when you opt out.

4. AI providers and your prompts

Sokudo integrates with multiple AI command-line tools (such as Claude Code, OpenAI's Codex CLI, Google's Gemini CLI, and OpenCode). When you send a prompt to an AI agent, the desktop application calls the chosen CLI locally on your machine. That CLI then sends the prompt and any context it needs directly to the underlying provider (Anthropic, OpenAI, Google, etc.) over a connection between your machine and that provider.

Your prompts and the AI's responses are not proxied through Sokudo's servers. We do not receive a copy of the prompt or completion text. Once the AI's response is returned to your machine, the desktop application stores the resulting chat message — including the response text — in your workspace, which is synchronized to our servers as described in section 2.

The terms and privacy policies of those AI providers apply to the requests they receive. You are responsible for choosing which provider to use and for any credentials you supply.

5. Shop orders and payments

Anyone can browse the Shop and fill a shopping bag. To check out, you sign in with your Sokudo account. We currently deliver only within Indonesia.

What we collect at checkout

• Your email address, for your receipt and messages about your order.
• Your name, street address, city, province, postal code, and country, to deliver your order.
• Your phone number, if you choose to give one, for delivery.
• What you ordered: products, options such as colour and size, quantities, prices, and the order's totals.
• The Sokudo account you were signed in with, so the order appears in your order history.
• The payment's status and the references Stripe gives us for it. We never receive your card details (see below).

Your shopping bag

Your bag is kept in your browser's local storage on your device, not on our servers, until you check out. While a checkout is in progress, your browser also keeps a small record of it — the items, quantities, and total, a private reference to the checkout, and a one-way code derived from your account identifier — so the checkout can continue after a reload or after you return from the payment page. That record never contains your email address, name, address, or phone number; those leave your browser once, in the checkout request.

Payments are handled by Stripe

When you pay, you are taken to a payment page hosted by Stripe. You enter your card details there, directly with Stripe. Sokudo never receives or stores your card number. To set up the payment, we send Stripe your email address, your name, delivery address and phone number (if given), the items and amounts of your order, and our reference for your checkout. Stripe tells us whether the payment succeeded.

Stripe processes this information to provide the payment for us. As its privacy policy explains, Stripe also uses some of it for its own purposes, such as preventing fraud and meeting its legal obligations, and it may collect information on its payment page, such as details about your device and browser. See Stripe's Privacy Policy.

Delivering your order and keeping you informed

We email you a receipt when your payment is confirmed and a shipping notice with tracking details when your order ships, through our transactional email provider. Our team uses your name, address, and phone number to send your order, and the delivery company we hand it to receives the details it needs to deliver it.

Your contact and delivery details are used to process your order. They are never sent to Google or Meta and are not used for analytics.

6. Optional analytics and marketing measurement

Our website offers one optional choice, shown in our cookie banner as "Optional analytics & marketing". It covers Google Analytics 4, from Google, and the Meta Pixel and Meta Conversions API, from Meta. With your consent, we use them to understand how visitors use Sokudo, to measure Shop purchases, and to measure and improve our marketing, including which ads and campaigns lead to visits and purchases.

Nothing runs until you accept

Until you choose Accept, our pages do not load Google's or Meta's analytics or advertising code, do not set their cookies, and send them nothing about your visit for analytics, and our server does not report your purchases to them. What you do before accepting is not recorded and is not sent later. If your browser still holds Google or Meta cookies from an earlier visit to our site, we remove them unless you accept. Declining changes nothing else: the website, the Shop, and checkout work the same either way.

One choice, remembered for six months

One choice covers both Google and Meta. We store it in a first-party cookie named sokudo_consent for six months, after which we ask again; a decline is remembered the same way. We also ask again if we change what this choice covers. If your browser does not let us store the cookie, your choice lasts only for the page you are on.

What your browser sends after you accept

• Page views. The address of the page you are on, which includes any Shop search you made, and the page you came from, plus the technical information browsers send with every request, such as your IP address and browser type. Private references in checkout and order links are removed from the address before Google's or Meta's code runs. Depending on how our Google Analytics property is set up, Google Analytics can also record some interactions on its own, such as scrolling, searches on our site (including the words you searched for in the Shop), clicks on links to other websites, file downloads, and form use. Meta's automatic recording of button clicks and page details is switched off.
• Sokudo events. Clicks on "Get Started", completed sign-ups (with the sign-in provider used), and app downloads (with the platform, processor type, and file format).
• Shop events. Product lists and product pages you view, products you open, items you add to or remove from your bag, viewing your bag, starting checkout, and confirming delivery details, each with product names, product codes, options, quantities, prices, and currency. Google receives all of these. Meta receives product page views, additions to your bag, and the start of checkout.
• Confirmed purchases, to Meta only. After our server has confirmed your payment, the page you return to from Stripe sends Meta a Purchase event with the order's product codes, quantities, prices, merchandise total, and currency, and a random event code that our server also sends, so Meta can count the purchase once. Your browser never reports a purchase to Google.

These events never include your name, email address, delivery address, phone number, or payment details, and the Shop events never include what you searched for.

Cookies Google and Meta set

After you accept, Google sets the _ga and _ga_<id> cookies, and Meta sets _fbp and, when you arrive from a link in a Meta ad, _fbc. These are cookies on sokudo.dev that contain identifiers Google and Meta use to recognise your browser across visits and, for _fbc, the ad click that brought you. Section 9 describes them further.

What our server reports when you buy

If you had accepted when you pressed Pay, your checkout carries the identifiers from those cookies (a Google Analytics browser identifier and visit identifier, and the Meta browser and click identifiers), your browser's user-agent string (added by our server from your checkout request, and only alongside a Meta identifier), and the version and time of the choice you accepted. Only after Stripe confirms your payment, our server sends:

• To Google (Google Analytics Measurement Protocol): the Google identifiers, your order number, the time of payment, the currency, the merchandise total, the shipping and tax amounts, and each item's product code, name, option, size, price, and quantity. Our server tells Google that you have not consented to this purchase being used for advertising or ad personalisation.
• To Meta (Meta Conversions API): the Meta identifiers, your browser's user-agent string, the time of payment, the random event code, the address of our order confirmation page without any private reference, the currency, the merchandise total, and each item's product code, quantity, and price.

Our server never sends Google or Meta your name, email address, delivery address, phone number, IP address, account identifier, or payment details. If your browser had no Google or Meta identifiers — for example because you declined, or your browser blocked their code — nothing about your purchase is reported, and checkout works the same.

How Google and Meta use this information

Google and Meta receive information directly from your browser, including your IP address, and from our server. They use it under their own terms and privacy policies. Meta may combine it with other information it holds and use it, for example, to measure, deliver, and personalise ads, whether or not you have a Facebook or Instagram account. Learn more in how Google uses information from sites that use its services, Google's Privacy Policy, Meta's Privacy Policy, and Meta's Cookies Policy. Meta's Pixel code may be downloaded through a content delivery network (Amazon CloudFront) instead of directly from Meta; that changes only where the code comes from, not what Meta receives.

Changing your mind

To withdraw, choose Cookie preferences at the bottom of any page, then Decline. When you do:

• Your browser stops sending information to Google and Meta straight away. Code they already loaded stays on the page until you leave or reload it, switched off through their own opt-out controls.
• We delete Google's and Meta's cookies from sokudo.dev, and delete them again on later visits if they reappear.
• If you are signed in, your browser tells our server, which deletes the Google and Meta identifiers it holds for your account's checkouts — including checkouts made in other browsers — and cancels purchase reports it has not yet sent. If you are signed out, or the request fails, your browser tries again on your signed-in visits for up to 8 days.

Withdrawing has limits:

• It does not delete information Google or Meta has already received. Deleting that is handled through their own processes, not automatically by us; contact us and we will help.
• A request already in progress when you withdraw, from your browser or from our server, may still complete.
• Declining in one browser does not stop Google's or Meta's code in another browser or on another device where you accepted; make your choice there too. Once your withdrawal reaches our server, though, its deletion covers your whole account, and purchases you make from that other browser are not reported until you accept there again.

Whether or not you withdraw, our server deletes the Google and Meta identifiers from a checkout about seven days after its payment session ends, and sooner once it has finished reporting the purchase or the checkout ends without an order.

7. How we use information

We use the information described above only to:

• Authenticate you and keep you signed in.
• Provide the core product — your workspaces, tasks, chats, and indexed code search.
• Process Shop orders: take payment through Stripe, deliver your order, send your receipt and shipping notice, and answer questions about your order.
• Manage access to the beta.
• Measure aggregate token usage and cost so we can size capacity.
• With your consent only, understand how visitors use our website, measure Shop purchases, and measure and improve our marketing (section 6).
• Diagnose bugs, debug crashes, and improve performance (using opt-in telemetry where available).
• Detect, investigate, and prevent abuse, fraud, or security incidents.
• Communicate operational notices (security advisories, downtime, access approvals) by email.
• Comply with legal obligations.

We do not sell your personal information for money. If you accept optional analytics, information about your visits and purchases is shared with Google and Meta as described in section 6, and they may use it for their own purposes, including advertising; you can withdraw at any time. We do not use your workspace content, chat history, or indexed code to train AI models — neither our own nor anyone else's.

8. Service providers and other recipients

Sokudo relies on the following categories of providers to run the Services:

• Identity providers — GitHub, GitLab, and Bitbucket — for OAuth sign-in.
• Embedding model provider — used to generate vector embeddings of indexed code chunks.
• Vector database — used to store and query the embeddings produced above.
• PostgreSQL, Redis, and MongoDB hosting — used to store account data, session data, workspace data, Shop orders, rate-limit state, and (for opt-in telemetry) anonymous engine events.
• Website hosting provider — serves our website and runs the server functions that pass your checkout details to our servers.
• Transactional email provider — used to send account-related email such as email verification and password reset, and Shop receipts and shipping notices.
• Stripe — processes Shop payments on its hosted payment page (section 5).
• Delivery companies — receive the details needed to deliver your Shop order.
• Google and Meta — only if you accept optional analytics: Google Analytics 4, the Meta Pixel, and the Meta Conversions API (section 6).
• Content delivery network — only if you accept optional analytics: Amazon CloudFront may deliver the Meta Pixel's code to your browser.

We engage our infrastructure, hosting, and email providers under terms that require them to handle data only on our instructions and to keep it secure. Stripe, Google, and Meta also process some of the information they receive for their own purposes, under their own terms and privacy policies (sections 5 and 6).

9. Cookies and similar technologies

Our cookie banner groups what we store in your browser into two categories.

Essential site & checkout (always active)

• Sign-in cookies. First-party cookies that store your session token and related authentication state, to keep you signed in.
• sokudo_consent. Remembers whether you accepted or declined optional analytics, when you chose, and, after a withdrawal, whether our server has been told yet. It lasts six months.
• Shop storage. Your bag, the checkout in progress (section 5), and the steps needed to update your bag after a payment, kept in your browser's local storage rather than in cookies.

Optional analytics & marketing (only if you accept)

• _ga and _ga_<id> — Google Analytics cookies that tell browsers apart and keep track of visits. Google sets them to last up to two years by default; browsers may delete them sooner.
• _fbp and _fbc — Meta Pixel cookies: a browser identifier and, when you arrive from a Meta ad link, the ad's click identifier. Meta decides how long they last.
• Purchase record. When the Meta Pixel reports a purchase, your browser keeps that purchase's random event code in local storage for up to 8 days, so the same purchase is not reported twice.

When your browser contacts Google or Meta, it may also send cookies those companies set on their own websites, depending on your browser's settings.

You can change your choice at any time from Cookie preferences at the bottom of every page, and clear cookies and site data from your browser. Clearing them will sign you out and empty your bag, and we will ask for your analytics choice again.

10. Data retention

We keep your account information for as long as your account exists. Workspace content, chat history, and indexed embeddings are kept until you delete the relevant workspace or your account. Session records expire automatically. Anonymous telemetry events are deleted after 90 days. If you ask us to delete your account, we will remove your personal information within a reasonable period, except where we are required to keep records to comply with a legal obligation, resolve disputes, or enforce our agreements.

For the Shop:

• We keep orders as the record of your purchase. 180 days after an order is delivered or cancelled, we remove the name, street address, and phone number from it; the email address, items, amounts, and the city, province, postal code, and country stay with the order. An order that is never marked delivered or cancelled keeps these details; you can ask us to remove them (section 12).
• The email address, name, street address, and phone number held for each payment attempt are removed 7 days after the attempt ends, whether or not it became an order.
• Payment event data we receive from Stripe, from which contact, billing, shipping, and card details are removed before we store it, is cleared 30 days after we process it. The details we pass to our email provider for a receipt or shipping notice are cleared from our records 30 days after the email is sent or finally fails.
• Price quotes, whose only delivery details are the country, province, and postal code, are deleted after 24 hours.
• The Google and Meta identifiers our server holds for a checkout are deleted as described in section 6. We keep a record of the version and time of the analytics choice a checkout carried, and of the time of your latest withdrawal, without those identifiers, as a record of your choice.

Stripe, Google, and Meta keep the information they receive according to their own terms and settings. The six months for which we remember your cookie choice is not how long we, or anyone else, keep analytics or order information.

11. Security

We use industry-standard measures to protect your information: encrypted connections (HTTPS), encrypted storage of OAuth tokens at rest, scoped database credentials, rate limiting on authentication endpoints, and least-privilege access controls for our team. Card details are entered on Stripe's payment page and never reach our servers. No system is perfectly secure, however, and we cannot guarantee absolute security.

12. Your choices and rights

You can:

• Update your name and profile image with your identity provider — those changes flow back to Sokudo the next time you sign in.
• Change or disable telemetry from inside the desktop app.
• Accept, decline, or withdraw optional analytics at any time from Cookie preferences at the bottom of every page (section 6).
• Block Google Analytics in your browser with the Google Analytics opt-out browser add-on, and manage how Meta uses information for ads in your Meta account settings. Industry tools such as WebChoices and Your Online Choices let you opt out of interest-based advertising from participating companies.
• Delete individual workspaces, chats, tasks, knowledge items, agents, and rules from the desktop app.
• Request a copy or deletion of your personal information, including your Shop orders, by emailing support@sokudo.dev.

Depending on where you live, you may also have additional rights — for example, to object to processing, to restrict processing, or to lodge a complaint with a data-protection authority. Email us and we will help.

13. Children

Sokudo is not directed at children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided us with personal information, please contact us so we can delete it.

14. International transfers

The Services are operated from infrastructure that may be located in countries other than your own. Stripe, Google, and Meta also operate internationally and may process the information they receive in other countries, including the United States. By using the Services you understand that your information may be transferred to, stored in, and processed in those countries.

15. Changes to this policy

We may update this Privacy Policy from time to time. When we do, we will update the "Last updated" date at the top of the page, and — if the changes are material — we will notify you by email or in-product before the new version takes effect. If we change what optional analytics covers, we will ask for your choice again.

16. Contact us

For any privacy-related question or request, email support@sokudo.dev. We will do our best to respond within a reasonable timeframe.