Privacy (draft)

Draft of 10 November 2026. Effective date: [to be set when reviewed]

Who we are

Riku is run by Riku AI LLC, a Wyoming limited liability company (“Riku”, “we”, “us”). Our registered address is [registered address]. You can reach us about anything on this page at [contact email].

Riku has two kinds of people in it, and this page covers both:

Builders: people with a Riku account who make chat apps and share them.
Visitors: people who open a builder’s app through a link, their team, or a chat widget on the builder’s website.

What we collect from builders

Your email address, so we can send you sign-in links. Riku has no passwords.
Your name and workspace details, if you add them, and who you’ve invited to your workspace.
What you put into your apps: the persona, instructions, pasted text, documents you upload and web pages you point an app at.
Model keys, if you add your own OpenAI, Anthropic, Google or OpenRouter key. We store them encrypted and only use them to run your apps.
Billing details. Payments go through Stripe. We see your plan, invoices and the last digits of your card, never the full card number.
Basic technical data, such as when you signed in and error logs, so we can keep the service working and secure.

What we collect from visitors

The conversation: the messages you send to an app and the answers it gives.
Your email address or name, only if the app’s owner asks for it before you start (an “email first” link or opening questions).
A small cookie that tells the app you’re the same visitor next time, so the owner sees unique viewers rather than a count of every page load. A password-protected link also sets a cookie so you don’t have to type the password again.
When you opened the link, and the first questions you asked.

The builder who made the app can see all of this for their own apps. That’s the point of the product: they see who opened their link and what was asked. The builder decides what their app is for and what it asks you, so for visitor data they are in charge and we handle it on their behalf. If you want something removed from someone’s app, ask them first; you can also contact us.

How we use it

To run Riku: sign you in, answer chats, show builders their links and conversations, and send the emails you’d expect (sign-in links, invites, receipts).
To bill paid plans.
To keep Riku safe, stop abuse, and fix problems.
To tell builders about important changes to Riku. We won’t send marketing email without a way to opt out.

We don’t sell personal data, and we don’t show ads. We don’t use your apps’ content or conversations to train AI models.

Who else handles it

We use a small number of companies to run Riku. Each one only gets what it needs for its job:

Cloudflare hosts Riku, its database and uploaded files.
AI model providers. To answer a message, the app’s instructions, the relevant context and the conversation are sent to the model the builder picked. The house model runs through OpenRouter. If the builder added their own key, the request goes to that provider (OpenAI, Anthropic, Google or OpenRouter) under the builder’s own account with them. [Reviewer: check each provider’s retention and training terms before publishing.]
Postmark sends our emails.
Stripe handles payments.
Google Fonts serves the typefaces on this website, so Google sees your IP address when the page loads.

Some of these companies are in the United States or process data there. [Reviewer: confirm transfer wording for UK/EU visitors.]

How long we keep it

We keep your account and your apps while your account is open. Conversations stay until the builder deletes them or the app, or until the account closes. When you close your account we delete its data within [30] days, apart from what we must keep by law, such as billing records.

Your choices

You can see, change or delete your apps and their content in Riku at any time.
You can ask us for a copy of your personal data, to correct it, or to delete it. Write to [contact email]. We’ll reply within 30 days.
Depending on where you live, you may have more rights, including the right to complain to your local data protection authority.

Cookies

This website doesn’t set any cookies. Inside Riku we use only the cookies the product needs to work: keeping you signed in, recognising a returning visitor to an app, and remembering an unlocked password link. No advertising or tracking cookies.

Children

Riku isn’t meant for children. Builders must be at least 18. If a builder makes an app for younger visitors, they are responsible for getting any consent the law requires.

Changes

If we change this page in a way that matters, we’ll update the date at the top and email builders before the change takes effect.