Skip to content
Hemion
ProfileSign inOpen studio
Back to Hemion

Trust & policies

Privacy Policy

Clear information about your work, your account and the service you use.

Effective
November 2, 2026
Last updated
November 9, 2026
Operated by
Khueon Studios

At a glance

  • Your browser saves designs, chat, references and renders. Signed-in services also retain recent conversations, private working project data and cloud backups.
  • AI requests send relevant messages, images and design context to our providers. Requested renders also send a studio reference image.
  • We do not sell your information, use it for advertising, or train our own models on your work.
  • Paddle handles payments as our Merchant of Record.

This overview is a guide. The full policy below explains the details.

Terms of ServicePrivacy PolicyRefund Policy
On this page 14 sections
  1. Who we are
  2. Information we collect
  3. How we use information
  4. Legal bases (EEA and UK)
  5. AI features
  6. Who we share information with
  7. Cookies and local storage
  8. International transfers
  9. How long we keep information
  10. Your choices and rights
  11. Security
  12. Children
  13. Changes to this policy
  14. Contact

On this page

  1. Who we are
  2. Information we collect
  3. How we use information
  4. Legal bases (EEA and UK)
  5. AI features
  6. Who we share information with
  7. Cookies and local storage
  8. International transfers
  9. How long we keep information
  10. Your choices and rights
  11. Security
  12. Children
  13. Changes to this policy
  14. Contact

A question about this policy?

Contact Khueon Studios.

khueonstudios@gmail.com

01Who we are

This Privacy Policy explains how Khueon Studios (“we”, “us”), the operator of Hemion at hemion.studio, handles personal information. We are the controller of the personal information described here. Paddle, our Merchant of Record, controls the payment information it collects at checkout; see Who we share information with.

02Information we collect

Account information

When you sign in with Google, we receive your email address and Google account identifier, and the basic profile details that Google shares, such as your name and profile picture. We record when you sign in, and we keep the session records needed to keep you signed in securely.

Your designs and messages

  • Saved in your browser. Projects, design history, design-chat conversations, attached reference images, generated renders and preferences are stored in your browser on your device. Signing out does not erase those local copies. The signed-in services described below also send information to our servers.
  • Private working project data. When you use signed-in server-backed editing and AI design tools, we process and store project snapshots, geometry recipes, requested edits, previews, job status and recovery records in our private backend. These records let us prepare geometry, apply changes consistently and recover interrupted work. This working storage is separate from the cloud-backup allowance shown with your package.
  • Cloud backups. When you are signed in and cloud storage is available, we store copies of your projects (the design data, project name and version information) so that you can download them later.
  • Account conversation history. When you are signed in, we also save recent project conversations in our Supabase account database so that they can be restored. This includes messages and responses, public reasoning summaries, attached reference images, and action and continuation activity used to recover unfinished work. This is bounded recent history, rather than a complete archive: up to 40 messages and 2 MiB per project conversation, with a 64 MiB total per account. We do not store raw private model reasoning in these conversations.
  • AI requests. When you use AI design assistance, your messages, attached reference images and relevant project data pass through our servers to our AI provider. The assistant can also request images of your current Plan, 3D or Walk view to inspect the design. Saved conversations retain the chat content described above; usage and billing records are separate.
  • Photorealistic renders. If you request a render, we send an image of the current studio view, relevant design and material context, and your visual brief to OpenAI’s image service. The resulting image and its reference view are saved in your browser so you can review and download them. A render is a visualization and may differ from the saved geometric model.

Usage and billing records

We keep records of your package, credit balance and credit transactions, and of each AI request’s usage (the model, token counts, status and cost, rather than its prompt content in the usage ledger). Render records include allowances, request identifiers, quality, status and processing cost. We also keep the identifiers that Paddle gives us for your customer account, subscription and transactions. We do not receive your full card number.

Technical information

Like most websites, our hosting and authentication providers process technical data such as IP addresses, browser type, timestamps and request logs. We use this data to deliver the Service, keep it secure and investigate problems.

Communications

If you email us, we keep the message and our reply so that we can help you.

03How we use information

  • To provide the Service: sign-in, preparing and saving designs, recovering editing jobs, restoring project conversations and cloud backups, generating AI responses and renders, and keeping your package, credits and render allowances in sync with Paddle.
  • To keep Hemion secure and reliable: verifying sessions, preventing fraud and abuse, enforcing usage limits, and diagnosing errors.
  • To support you and send service messages, such as billing or account notices.
  • To meet legal, tax and accounting obligations.

We do not sell personal information, use it for advertising, or use your designs, messages or images to train our own AI models. AI providers process requests under the data policies described below.

04Legal bases (EEA and UK)

Where the GDPR or UK GDPR applies, we rely on:

  • contract: to provide the Service you signed up for;
  • legitimate interests: to secure the Service, prevent abuse and improve its reliability;
  • legal obligation: to keep billing and tax records;
  • consent, where the law requires it, which you can withdraw at any time.

05AI features

Hemion’s AI assistants use OpenAI or Cloudflare Workers AI, depending on the Service’s configuration. Photorealistic renders use OpenAI. Requests can include messages, reference images, relevant architectural project data and screenshots of the model. Include only information you have the right to share, and avoid sensitive personal information that is unnecessary for your design.

We request that OpenAI not store assistant responses as API application history. This does not mean that provider-side retention is zero: security monitoring, prompt caching and legal obligations can involve separate processing or retention. OpenAI states that API content is not used for training by default; Cloudflare states that it does not train models on Workers AI customer content. Their current policies explain the applicable controls and exceptions: OpenAI data controls and Cloudflare Workers AI data usage.

Public progress and reasoning summaries can appear in your chat and saved conversation. Raw private model reasoning and encrypted provider reasoning are not saved in that conversation record.

06Who we share information with

We share personal information only with providers that help us run Hemion, and only for that purpose:

ProviderPurpose
GoogleGoogle sign-in and the profile information you authorise it to share
SupabaseAuthentication, accounts, credit and usage records, recent conversations and private working project data
VercelWebsite hosting, request processing and architectural geometry computation
CloudflareCloud backups in R2, and AI assistant processing through Workers AI when configured
OpenAIAI assistant responses, visual model inspection and requested image renders
PaddleCheckout, payments, tax, invoicing and billing support, as our Merchant of Record

Paddle processes payment information as an independent controller under its own privacy policy. We may also disclose information if the law requires it, to protect rights and safety, or as part of a merger, acquisition or sale of assets; in that case this policy, or one at least as protective, will continue to apply.

07Cookies and local storage

  • Sign-in cookies. We use essential session and sign-in verification cookies through Supabase. Production session cookies are secure and HttpOnly. A separate return-location cookie lasts 10 minutes so we can return you to the right page after Google sign-in.
  • Browser storage. We use browser databases and local storage for projects, history, conversations, AI change review snapshots, reference images, renders and preferences. AI change reviews retain the latest request’s starting and resulting designs in that project’s browser database so you can compare, keep or revert the request. These review records stay on the device; ordinary project processing and cloud backup continue as described above. Storage is separated for the account using the browser. Signing out changes the active account; it does not clear all saved data from that device.
  • No analytics or advertising cookies. We do not use tracking or advertising cookies. Paddle’s checkout may use its own cookies to process payments and prevent fraud, under Paddle’s policies.

08International transfers

Using Hemion can involve processing outside your country, including in India, the United States and other countries where our providers operate. A database’s hosting region does not mean every authentication, AI, support or hosting request stays in that region.

The applicable provider terms and data-processing arrangements govern these transfers, alongside legal requirements that apply to us. We do not offer a customer-selectable data-residency option. Contact us if you need information about a particular transfer or safeguard before submitting your data.

09How long we keep information

  • Account information, saved project conversations and cloud backups are retained while your account is active, subject to the conversation history bounds described above. Contact us to request account closure or deletion; some billing, security or dispute records may need to be kept to meet legal obligations.
  • Private working project snapshots and design-job records are retained to support editing and recovery, within storage and revision-history limits. Older working revisions and completed job records can be replaced as new work is saved. This storage is not a permanent backup archive.
  • Saved project conversations contain the latest bounded record. Older chat content is replaced as new history is saved or the conversation is cleared.
  • Billing, credit and usage records: for as long as we need them to provide the Service and to meet tax, accounting and legal obligations.
  • Technical logs: for limited periods set by our hosting and infrastructure providers.
  • Browser-saved information remains until you remove it or your browser clears it. Download renders and export important designs if you need a copy independent of browser storage.
  • AI-provider retention is separate from our account and browser storage; see AI features.

10Your choices and rights

Depending on where you live, you may have the right to access, correct, delete or export your personal information, restrict or object to processing, and withdraw consent. You can export designs as JSON from the studio, download renders, and manage available cloud backups in your profile.

Clearing browser data or removing a local project does not by itself delete the private working data, conversations or backups saved to your account. Starting a new conversation replaces its saved recent chat when synchronization succeeds. For account-wide deletion or information you cannot remove in the product, contact us.

To exercise your rights, email khueonstudios@gmail.com from the email address of your Google account. We aim to respond within 30 days, subject to applicable legal deadlines and any permitted extensions, and may ask you to confirm your identity. You may also complain to your local data protection authority where that right applies.

11Security

We protect information with encryption in transit, secure HttpOnly session cookies, strict database access controls, and integrity checks on cloud backups. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.

12Children

Hemion is intended for people aged 18 or over, and we do not knowingly collect personal information from children. If you believe a child has given us personal information, contact us and we will delete it.

13Changes to this policy

We will update this policy when our practices change, and we will notify you of material changes before they take effect. The date at the top shows when this policy was last updated. See also our Terms of Service.

14Contact

Khueon Studios · hemion.studio · khueonstudios@gmail.com

Need help with your account? Open your profile or contact us.

Back to top
Hemion

© 2026 Khueon Studios. Hemion is a product of Khueon Studios.

Orders are processed by Paddle.com, our Merchant of Record.

PackagesCloud backupsSign in
Terms of ServicePrivacy PolicyRefund Policykhueonstudios@gmail.com