Rikuvo Studio — Privacy Policy

Draft for founder review — not yet lawyer-reviewed. Effective date: to be set when published.

This policy explains what information Rikuvo Studio collects, why, who it is shared with, and the choices you have. It covers the hosted dashboard at studio.rikuvo.us.com, the dedicated server we run for you, and the emails we send you. It does not cover the apps you build with the Service — you are their publisher and they need their own policy.

The person responsible for your data ("controller") is Kareem Kader, doing business as Rikuvo, 25 Watch Hill Drive, East Greenwich, Rhode Island 02818, United States. Contact: kareemkader2006@gmail.com.

1. What we collect

Account and organisation. Your name, email address, the public half of each passkey you register (we never see the private half), your organisation's name, and the people you invite and the access you give them.

Billing. Your plan, app count, invoices and payment history. Card details go directly to Stripe; we store only what Stripe returns (the last four digits, card brand and expiry) so you can recognise the card.

Your apps and their work. Everything the engine needs to build your apps lives on your dedicated server: your source code, tickets, build logs, test results, screenshots and recordings from automated testing, generated artwork, and the engine's working state. The dashboard reads summaries and snapshots of that state so you can see it from anywhere, and stores what you approve, reject, or answer.

Your Claude connection. If you sign in with a Claude subscription, that sign-in happens between you and Anthropic on your server; we never collect, store, or read your Claude.ai credentials or session tokens. If you give us an API key instead, it is stored only on your server and never copied to the dashboard or anywhere else we control.

Connected services. The credentials you connect for Apple, Google Play and Expo are stored on your server and used only to build and submit your apps. We do not use them for anything else.

Chats with Rikuvo AI. The messages you exchange with the dashboard's assistant, and the assistant's replies, are stored so the conversation can continue across sessions and devices.

Usage and technical data. Server logs (IP address, browser and device type, pages requested, timestamps), error reports, and how the dashboard is used. We use these to run the Service and fix problems. We do not run third-party analytics or advertising trackers.

Support. Emails you send us and our replies.

We do not collect data from children; the Service is for adults and businesses only (see the Terms).

2. Why we use it

To provide the Service you pay for: run your server and the engine, show you your fleet, act on your decisions, bill you, and answer support requests. (Legal basis where one is required: performing our contract with you.)
To keep the Service secure and reliable: detect abuse, debug outages, and keep backups. (Our legitimate interest in running a working, safe service.)
To tell you things you need to know: receipts, failed payments, security notices, and, on Premium, your weekly note. (Contract and legitimate interest.) We do not send marketing email unless you ask for it, and you can unsubscribe from anything optional.
To improve the Service. We look at how the dashboard is used in aggregate and at error reports. We do not use your source code, your apps, or your chats to train any AI model.
To comply with the law and enforce our Terms.

We share data only with the providers we need to run the Service, and only what each needs:

Hetzner Online GmbH (Germany) hosts your dedicated server. Their data centres are in the EU and the US; your server's location is shown in your dashboard.
Stripe processes payments and holds your card details.
Anthropic receives the prompts, code and context the engine sends when it works on your apps — through your own Claude subscription or API key, under your agreement with Anthropic. Rikuvo is not a party to that data flow and does not see it.
Expo builds your iOS apps on your own Expo account and receives the project code needed for each build.
Apple and Google receive the builds and store listings you choose to submit.
Resend delivers our transactional email (receipts, verification, notices).
Rikuvo's staff. Today that is the founder alone. On Premium they look at your fleet daily as part of the service; on any plan they may access your server's logs and engine state to support you or fix an outage, and will tell you when they have.

We do not sell your personal information, and we do not share it with advertisers or data brokers. We may disclose data if the law requires it, or to protect the rights and safety of Rikuvo, our customers, or the public.

If we ever transfer the business, your data may move to the new owner under this policy; we will tell you first.

4. Where your data lives

The dashboard and its database are operated from the United States. Your dedicated server is at Hetzner in the EU or US. If you are in the EU, UK or Switzerland, transferring your data to the US is done under standard contractual clauses or another lawful transfer mechanism; email us for a copy.

5. How long we keep it

Account, organisation, billing records: for as long as you have an account, then as required for tax and accounting (typically 7 years for invoices).
Your server and everything on it: for as long as you subscribe, plus a 14-day export window after your subscription ends. Then the server is destroyed.
Backups of your server: rotate out within 30 days of being taken; a deleted server's backups therefore disappear within 30 days of deletion.
Rikuvo AI chats and dashboard snapshots: for as long as you have an account; deleted with the account.
Server logs and error reports: 90 days.
Support email: 2 years after the thread closes.

You can ask us to delete your account and data sooner (section 7). Some records we must keep by law.

6. How we protect it

Sign-in uses passkeys, not passwords. All traffic between your browser, the dashboard, and your server is encrypted in transit. Your server accepts no inbound connections; it only reaches out to the dashboard. Each customer's server is separate, and dashboard data is scoped to your organisation so no customer can see another's. Access by Rikuvo staff is limited to what support and operations require.

No system is perfectly secure. If we learn of a breach affecting your data, we will tell you without undue delay and, where the law requires, within the required time.

7. Your rights and choices

You can, at any time from the dashboard or by emailing us:

See and export your data, including your repositories;
Correct your account details;
Delete your account, which destroys your server and removes your data as described in section 5;
Object to or restrict a use of your data that rests on our legitimate interests;
Withdraw consent where we relied on it;
Complain to a data-protection authority if you are in the EU, UK or another place that has one.

If you are a California resident, the rights above cover what the CCPA/CPRA gives you; we do not sell or share personal information for cross-context advertising, and we will not treat you differently for exercising your rights.

We will answer requests within 30 days and may need to verify that the request comes from you.

8. Cookies

The dashboard uses a session cookie to keep you signed in and a small number of functional cookies for your preferences. It does not use advertising or third-party analytics cookies. You can clear cookies in your browser; you will need to sign in again.

9. Changes to this policy

We will post any changes here and update the effective date. If a change materially affects how we use your data, we will email you at least 30 days before it takes effect.

10. Contact

Rikuvo — Kareem Kader

25 Watch Hill Drive, East Greenwich, RI 02818, United States

Email: kareemkader2006@gmail.com