Privacy Policy

Information the service handles

• Account information: your name, email address, verification status, and sign-in records. If you use an optional Google or GitHub sign-in, this may also include your provider account identifier, profile image, and authentication tokens. Passwords are stored as hashes, not readable passwords.
• Workspace content: spaces, topics, messages, side discussions, artifacts and their revision history, saved instructions, and model preferences. The service also stores tool activity and model usage information such as model identifiers and token counts.
• Voice conversations: session records, captured conversation context, and text transcriptions of your speech and AI replies. Fukurama does not store raw audio recordings.
• Files: uploaded originals, file metadata, extracted text, and images you select for a model request.
• Provider connections: API keys you supply for AI providers. These are encrypted on the server and used to authenticate requests to the corresponding provider.
• Technical information: session identifiers, browser information, request and security records, and usage counts. IP addresses may be processed by hosting infrastructure and, where configured, for sign-in security and abuse prevention.

How information is used

Information is used to create and secure your account, save and display your workspace, generate AI responses and artifact changes, perform the tools you enable, deliver verification and password-reset emails, prevent abuse, enforce resource limits, and diagnose service failures.

AI providers and enabled tools

Generating a response sends relevant context to your selected model provider. This can include messages, the current artifact, saved instructions, resolved side discussions, selected images, and text or other results retrieved by enabled tools. The server decrypts a saved provider API key when it needs to authenticate a request.

Depending on your selection, requests may go directly to OpenAI, Anthropic, DeepSeek, Google, Alibaba Cloud (Qwen), Moonshot (Kimi), or Mistral, or through OpenRouter, OpenCode Zen or Go, or Vercel AI Gateway to a model provider. These services have their own terms and privacy practices. Their data use, retention, and processing locations depend on the provider, model, and account settings. Review those practices before sending sensitive information. Removing content from Fukurama does not recall information already sent to a provider or erase that provider's records.

Starting voice mode sends microphone audio directly from your browser to Google Gemini and plays Google's audio replies. The server provides a short-lived, single-use credential constrained to the voice session; your saved Google API key is not sent to the browser. Google also receives the conversation context and applicable saved instructions. Microphone access requires browser permission, and you can mute or end the session. Google's audio processing and retention follow its own terms and account settings, separately from Fukurama's stored text transcripts.

OpenCode generation requests also include an opaque conversation identifier for routing and prompt caching. This identifier is separate for each conversation path and side topic; it does not contain your name, email address, or conversation title.

When web tools are enabled, search queries and page URLs are sent to web-search and retrieval infrastructure, currently Firecrawl. Queries may contain text the AI takes from the context of your request. The retrieval service contacts external websites, and relevant results can be saved with the discussion and sent to the selected model.

File-reading and topic-reference tools can bring authorized material from your own workspace into the model's context. Do not enable a tool or supply information that you are not permitted to share.

Other service providers and disclosures

Hosting, database and file storage, email delivery, and optional third-party sign-in services process information as needed to provide those functions. Infrastructure and AI providers may process information outside your country. Fukurama may also disclose information where required by law or necessary to address fraud, security incidents, or unlawful use.

Better Stack receives technical error reports to help diagnose failures. Reports include the application version, error categories, code locations, model/provider identifiers where relevant, and opaque message or review references. A limited trail of review actions and state changes may accompany a report. The reporting service also receives connection information, such as the sending IP address, when a browser or server connects to it.

Error reporting excludes conversation and artifact text, uploaded files, form contents, account names and email addresses, API keys, cookies, request bodies, URL query values, and raw exception messages. Session replay, screenshots, advertising tracking, and AI input/output recording are not enabled.

Cookies and browser storage

Fukurama uses sign-in and security cookies, a cookie that remembers whether your sidebar is open, and local browser storage for your theme preference and the last conversation path selected for each topic in your account. Blocking necessary cookies can prevent sign-in from working. The application uses technical error reporting as described above, not advertising trackers or product-usage analytics.

Retention and deletion

Saved account and workspace records are not currently subject to an automatic deletion schedule. Revision and branch history preserve earlier content when you edit or continue your work.

Deleting a space or topic removes it from normal access but does not permanently erase its messages, artifacts, history, or attached files. Removing a file from a selection does not delete a file already bound to a saved topic. There is currently no self-service permanent account or workspace-data erasure function. Do not treat a workspace Delete action as a guarantee of permanent erasure.

Unsent, staged uploads expire from access after 24 hours. Physical removal is performed by scheduled storage maintenance rather than instantly at expiry. This expiry does not apply to files already attached to a saved topic.

Database records, stored files, backups, operational logs, and external provider records are separate copies of information. An action in the workspace does not establish that all of those copies have been removed.

Security

Fukurama uses account-based access controls, private file storage, password hashing, and encryption for stored provider credentials. These controls do not make the workspace end-to-end encrypted: the server must process content to provide the service, and selected AI providers receive the context needed for requests. No service can guarantee absolute security.

Your choices and rights

You choose which model provider to connect and which tools and files to use. You can remove a provider connection to remove its saved API key from active use. You can also clear browser cookies and local storage, although this does not delete information held on the server.

Depending on the law that applies to you, you may have rights to access, correct, obtain a copy of, or request deletion of personal information, or to object to or restrict certain processing. You may also have the right to complain to your local data-protection authority. Those legal rights are not limited by the absence of a self-service erasure button.

Payment information

Fukurama does not currently provide a checkout or collect payment-card details. If paid subscriptions become available, their payment-data handling will be disclosed before purchase.

Changes to this policy

This page will be updated when the service's information handling changes. The date above identifies the current version. Use of the service is also covered by the Terms of Service.