What data we process
- Account details: email address, phone number, your password in encrypted form, a so-called hash (we do not store the password itself, cannot see it and cannot recover it), and a name. If you did not give a name when you registered, the part of your email address before the @ sign is recorded instead.
- Sign-in with Google: if you press Continue with Google, Google tells us your email address and the identifier of your Google account. We keep the email as the address of your account. We keep the identifier only as a hash (an encrypted fingerprint), to recognise the same Google account at the next sign-in. We do not ask Google for your name, photo or other data, and your Google password is not available to us. A phone number and a password are not needed for this kind of sign-in.
- Work in Orikami: your messages to the assistant, conversation history and the files of your workspace. They sit in your private workspace on our servers.
- Task board (when it is on): your request for the site word for word; task cards with titles, goals and acceptance criteria; your comments and the assistant's; the history of card moves (without texts: codes, numbers and time); check scenarios; check results: what was checked, what was expected and what was received, short excerpts from the site's responses; screenshots of your site's pages taken by the checks; the link between a board and your Orikami conversations. Whatever the assistant reads from the board goes to the model provider, just like your messages.
- Published sites: site files, their names and addresses.
- Requests from your site forms: the fields a visitor filled in (for example, name and phone), the page, language and time, and a hash of the IP address for spam protection (the address itself is not stored with the request). Only you see requests: in the dashboard (all of them), in the email about a new request sent to the account address (no more than 20 emails an hour per site) and through your own assistant with data access. The site owner is the controller of this data; we store it on the owner's behalf.
- Data of your sites' visitors: if a site has a server part and a database (such sites are not available on the task board yet), the data the site keeps about visitors, such as accounts and orders, sits in the site database on our servers. The site owner is the controller of this data; we store it on the owner's behalf.
- AI usage records: account, model, number of tokens (the way the amount of text for the AI is measured) and units, cost, outcome and time of the request. These records contain no conversation content.
- Account activity log: sign-in, publishing, stopping, deletion, plan changes. For developers: the log keeps not the access tokens and sessions themselves but their hashes (encrypted fingerprints).
- Technical data: IP address, time, request address without parameters and browser type in web server logs, kept for about two weeks.
- Payment: your Stripe customer ID, subscription status and its end date. We do not receive your card details.
- Domains: when you buy a domain, the owner details you enter (first and last name or organization name, email, phone, postal address), the domain name, the amount and time of the order, the version of the terms you agreed to, and the IP address; when you connect your own domain, its name and the site it is connected to.
- Visit statistics of orika.me: the page address without parameters, the domain the visitor came from, utm tags (including the ad keyword) and the Google ad click identifier (gclid) if you came from an ad, device type, browser, system, language and time. On the sign-in and registration page we count steps without personal data: the form was opened, a button was pressed, the form was sent, the code screen was shown, the code was accepted or not, the error code. Your email, phone and password never get into the statistics. A visitor is counted by a daily hash (salt, day, site, IP address and browser): the IP address and the browser string themselves are not stored, and the hash changes the next day. Our own statistics set no cookies, and the Do Not Track signal is honored. Separately, orika.me runs Yandex Metrica (see the cookies section).
- "About you" questionnaire: while the assistant builds the site, Studio offers a few questions: how to address you, last name and patronymic, phone, age range, country and city, who you are and what you do, the size of your business, the goal of the site, a link to an existing site, your experience with websites and how you heard about us. Everything except the first name is optional, and the questionnaire starts with your consent to storing the answers. We use the answers to understand who the service helps, to tailor advice and to contact you about the site and the subscription. The answers are stored only with us, are not passed to Yandex, Google or other third-party services, and are deleted together with the account. You can close the questionnaire, and we will not show it again.
- Telegram: if you connect Telegram, we store your chat number and your Telegram name to deliver the assistant replies. We do not store the message texts: they are passed to the assistant the same way as messages in Orikami. You can unlink the chat in Orikami or with the /stop command.
- Account journey events: sign-up, first message to the assistant, first publication, upgrade to a paid plan, failed payment: the event code, time, a pseudonymous account number and, for sign-up, the source (domain, utm tags and the Google ad click identifier if you came from an ad). These records contain no email, name or texts.
Why
So you can sign in, work with the assistant, publish sites and pay for a plan, so that we can count limits and protect the service from abuse. Visit statistics and source tags help us understand where people come from and at which registration step they stop. We do not sell data and do not pass it to advertising networks.
Who receives data
- The language model provider (DeepSeek). For the assistant to answer, the provider receives your messages, parts of files and tool results that go into the request, and search queries if the assistant searches the web. Requests go through our server; we send the provider an account pseudonym, not your name or email. The provider processes data under its own policy and may do so outside your country.
- Stripe processes payments for the Start and Club plans and for domains.
- Name.com (the domain registrar), only if you buy a domain: it receives the domain owner details, a domain cannot be registered without them. In the public WHOIS record they are hidden where the zone supports it.
- Cloudflare delivers our sites and protects them from attacks: all requests to our addresses pass through it. If you connect your own domain, Cloudflare receives its name and issues an HTTPS certificate for it.
- Google, only if you sign in with Google: you confirm the sign-in on a Google page, and we receive your email address and account identifier from it. We do not send Google anything about your work in Orikami.
We have no other recipients, except where the law directly requires it. Do not type passwords, keys, payment details or other people's personal data into the chat: everything the assistant reads to answer goes to the model provider.
Public content
Everything you publish at the address of your site (name.orika.me or your own domain) is visible to anyone who has the link. On the Free plan sites are hidden from search engines (but not locked), on Start and Club they are open to them. Do not publish secrets or third parties' personal data.
Cookies and browser storage
Orikami uses a sign-in cookie (up to 7 days), a service cookie of your workspace, a service cookie of an unfinished registration (up to 12 hours, while you confirm your email with the code from the message) and short-lived service cookies at sign-in, including sign-in with Google (up to 10 minutes); the interface language and a mark of an unfinished registration (only the time, without your email or password) are remembered in the browser. The Host dashboard uses one session cookie (up to 30 days). All of them are needed for sign-in to work.
There are no advertising cookies. The orika.me site runs a Yandex Metrica counter with Webvisor: it records mouse movement, clicks and scrolling on orika.me pages (input fields and key presses are hidden from the recording), sets its own cookies (_ym_uid, _ym_d and others) and sends Yandex data about the visit: the page, the referrer, device type, browser and IP address; Metrica does not honor the Do Not Track signal. You can turn it off with a tracker blocker or by refusing cookies in your browser. We also count visits ourselves (see above), and Cloudflare may collect anonymized statistics (Web Analytics) without cookies.
Where and how long we keep data
- Account data and the workspace: while the account exists. They sit on our servers with restricted access.
- Published sites: until you delete them; deleted ones are kept in an archive for up to 30 days and then erased.
- Form requests: while the account exists; an archived request stays in the database. The site owner can ask for requests to be erased permanently at [email protected].
- Visit statistics and account journey events: kept without a fixed term for now; they contain no email or name (an account event can be tied to an account only by its number).
- AI usage records and the activity log are needed for billing, limits and security; after you delete the account they remain without your name and email (the address is replaced by an anonymous one).
- The task board, its cards, comments, scenarios and check results: while the account exists.
- Screenshots from checks: the last 10 check runs of each board and the screenshots referenced by the release that is live now; the others are erased after 14 days, and the check record stays without the screenshot.
- Boards of a deleted account: right after deletion they go to an archive, their texts (the request, cards, criteria, comments, scenarios and check results) are replaced by a deletion mark and screenshots are erased. Codes, numbers and times needed for billing, limits and security remain.
- The files and conversations of the workspace are erased on your request within 30 days after you delete the account (see Account deletion).
Your rights
You can ask for a copy of your data, its correction or deletion. You delete your account in the Host dashboard; if you cannot sign in, write from the address on the account to [email protected]: the request is handled within 30 days. Details: orika.me/en/delete-account/.
Age
The service is not intended for people under 18, and we do not knowingly collect their data.
Changes to this policy
If the policy changes materially we will notify users by email or in the dashboard before the changes take effect. The current version: orika.me/en/privacy/.
Contacts
Data operator
Sole proprietor Dias Zhumagaliyev
Email: [email protected]
Payments and refunds: [email protected]
Website: orika.me