VERSION 2026-10-01-beta-13 · 30 SEPTEMBER 2026
Privacy notice
CHUMA team authors can translate their community post text using OpenRouter and the Novita Ling endpoint. Only the entered post text is sent on request or when publishing without translations. Project files and support messages are not included. Members can also request a translation of a visible community comment into English, Russian or Danish using the same provider. Only that comment text is sent; a notice appears next to the comments. Comment translations are cached and can contain errors. Saved translations are shown according to the reader’s selected language; the original text remains available. Posts are originally written in English; comments may be written in other languages.
Community and support (updated 29 September 2026)
The optional community is shared by signed-in members. Names chosen for posts and comments, optional profile photos, messages, posted images and videos, replies and reaction counts are visible to those members. You can remove a profile photo in Profile and security. Your archive is not published to the community. The operator is the controller for community participation and moderation. Participation is optional. Providing the community requested by an individual user relies on Article 6(1)(b); for studio representatives, Article 6(1)(f) supports providing that requested service. Translation uses the same applicable basis for the requested function. Preventing abuse and reviewing complaints rely on Article 6(1)(f). Video recording requests camera and microphone access only when you choose to record. Recordings stay on your device until you submit a post, when the video is uploaded before the post is saved; uploaded drafts are removed after 24 hours if not published. Published videos are stored in private Cloudflare R2 and available to signed-in members. Our legitimate interest in preventing abuse also supports moderation. Do not share confidential project information or another person's personal details without an appropriate basis. Authors can hide their comments; the CHUMA team can moderate posts and comments. The Delete action hides material from members; it does not immediately erase database copies, translations or attached media. The team can restore hidden material. Hidden posts and comments are normally permanently removed 30 days after they are hidden, together with their stored translations, reactions and attached media. For an existing hidden item, the 30 days begin when this rule is introduced. An authorized team member can place a documented hold while a specific complaint or legal claim is open; the hold must be released when that need ends, after which an overdue item is removed by the next cleanup. Restricted historical backups may retain older copies until their separate deletion schedule. Contact us for a specific erasure request or backup information. Contact us to request correction or permanent removal, including when closing your account.
The support form sends your reply email, subject, message and optional reduced screenshot through Cloudflare to our Gmail support mailbox, chumastudiobyelena@gmail.com. We use these records to respond to your request. Google processes the mailbox and replies. Other members cannot view your support requests. Application copies are deleted after 180 days; mailbox correspondence is handled separately and reviewed when a request is resolved or an erasure request is received. No automatic mailbox deletion is configured. Existing international processing and rights information below also applies to these functions.
Optional link imports
When you submit a supported public Google Drive, Yandex Disk, Dropbox or OneDrive link, we contact that provider to list and copy the selected files into your workspace. We retain the source identifiers, file paths and transfer status to run the import and report errors. Inactive import records are removed after seven days; imported files follow the normal project retention rules. Link discovery and transfer do not send file contents to an AI provider. Cloud providers may record these download requests under their own policies.
Who is responsible
Olga Aleksandrovna Sukhova, Denmark. Email: chumastudiobyelena@gmail.com. The operator is the controller for account administration, service security and support records. A studio normally controls personal data in its project content; for that content we act on its instructions as a processor under our data processing terms. If you are depicted or named in a studio's material, contact that studio or contact us and we will help route the request.
Data, purposes and legal bases
We collect your account name or nickname, studio name, contact email and accepted document version to create and administer the account. For an individual customer this is necessary to perform the service contract (GDPR Article 6(1)(b)). For a studio representative, our legitimate interest is administering the studio's requested service (Article 6(1)(f)). Required registration fields are needed to open an account.
Access key and session hashes, expiry times, short lived IP based rate limit hashes, request metadata and support audit records protect accounts, prevent abuse and help investigate incidents. We rely on the legitimate interests of operating a secure service and resolving problems, with restricted access and limited retention. For a binding legal obligation we rely on Article 6(1)(c). We do not rely on a blanket consent to the privacy notice.
Project data includes uploaded images, documents, drawings, tables, 3D files, textures and any embedded metadata, filenames, credits, location, descriptions, year and memorable details entered by the studio. Do not include unnecessary personal information in files or their metadata. We use project content to provide the functions requested by the studio, not for advertising. There is no advertising profiling, sale of personal data, or solely automated decision with legal or similarly significant effects. AI provides editable suggestions only.
Administrative access
Authorized administrators may access a workspace where necessary to investigate a reported problem, correct project metadata, restore a project from Trash, or address a security incident. This is part of providing support; a separate access permission button is not required. Administrators must record a specific reason and limit access to the affected data. The support interface permits previews and metadata corrections but blocks original and ZIP downloads, uploads, AI requests and permanent deletion. Support actions are logged. Access for curiosity, marketing, portfolio use, sale or model training is prohibited. Viewing a preview necessarily transmits that preview to the administrator's browser. Infrastructure administrators retain technical access beyond these interface controls and are subject to the same purpose and confidentiality restrictions.
Providers and international processing
Cloudflare, Inc. supplies hosting, Workers, the D1 database and R2 storage, including request delivery and security. Optional project drafting uses OpenRouter, Inc. Free Ling requests are processed by Novita; free Gemma requests use the configured Google model endpoint. Paid Gemini drafting is restricted to the CHUMA team workspace. Availability depends on an eligible endpoint, and no paid fallback is automatic. Separately, community post translations requested by the team and comment translations requested by any signed-in member use OpenRouter and Novita, as described above. Community translation does not access private project files. For description drafting, submitted text and up to 80 filenames are sent, together with up to three project source URLs and retrieved text excerpts if you include source links for that request. Project originals are not sent for description drafting. If you request room labels in the CHUMA pilot, reduced image previews are also sent through OpenRouter to Google Gemini with the same provider privacy controls; original images are not sent. AI request records contain time, status and cost, not a separate prompt history. Saved project details and cached source excerpts remain part of the archive until removed under the project retention rules.
Requests use settings that prohibit provider data collection and require a provider endpoint marked as having zero data retention. This is a routing restriction, not a guarantee that no legal, security or usage metadata exists anywhere. If no eligible endpoint is available, the AI request fails rather than relaxing the restriction.
These suppliers operate internationally, including in the United States. The current deployment does not promise exclusive EU or EEA storage or processing. The published Cloudflare and OpenRouter processing agreements describe contractual safeguards, including EU standard contractual clauses where applicable. The operator must ensure the correct contracting party, applicable transfer module and any necessary supplementary measures are in place; publishing this notice is not evidence that those checks have been completed. Contact us for the applicable safeguards and relevant copies, with unrelated confidential details removed.
Retention
Login sessions expire after at most 7 days; signing out invalidates the session. Rate limit records expire according to the protected operation and are removed by background cleanup. Expired authentication and email links are also removed by that cleanup. Support audit entries are kept for up to 90 days. AI request status and cost records are retained for up to 30 days to enforce request limits and investigate errors, then removed by background cleanup.
Account details and active projects remain while your account is open. Trash has a 30 day recovery period. When an owner requests deletion in Profile and security, access stops immediately and a 30 day cancellation period begins. After that period live account and project data are removed by background processing. Other verified erasure or closure requests are handled through support, including any agreed retrieval period or specific legal obligation requiring retention. We will explain any exception and its scope. Restricted operational backups may retain older copies for up to 30 days after live deletion. Encrypted operational snapshots expire 28 days after creation. Automated daily cleanup is configured for encrypted GitHub backups; local cleanup runs with the backup job and requires the operator’s computer to be available. The operator monitors failures, must resolve missed cleanup within the stated period and confirm completion of affected copies. Older manual copies outside this schedule require a separate review and cleanup. This does not extend the agreed retention period. We do not promise instant erasure from all historical copies. Older CHUMA import previews may also exist in prior deployment packages and require manual cleanup.
Your rights
You may request access, correction, erasure, restriction and, where applicable, a portable copy of personal data. You may object to processing based on legitimate interests. If a separate optional activity relies on consent, you can withdraw that consent without affecting earlier lawful processing. Email the operator. Requests are normally free; we may ask for proportionate information to verify your identity, rather than routinely asking for identity documents.
We respond without undue delay and normally within one month. If an extension is legally allowed because of complexity or volume, we will explain it within the first month. You can complain to Datatilsynet, Denmark's data protection authority, or another competent supervisory authority, including where you live or work in the EEA. You do not have to contact us before complaining.
Security and updates
We use HTTPS, private storage, workspace access checks, password hashes, encrypted authenticator secrets, recovery code hashes and legacy access key hashes and secure session cookies. Support access is restricted and logged. This is not end to end encryption: the operator can technically access content. No security certification or guarantee of absolute security is claimed. We will handle personal data breaches, notify affected studios and, where required, authorities and individuals. Material changes to this notice will be communicated through the service or your contact email.
Account security and service email
Resend (Plus Five Five, Inc.) delivers email confirmation, password recovery and project invitations. It receives the recipient address and message contents, including temporary links, but not project originals. The sending region is Ireland; this does not mean all processing stays in the EEA. International processing, including in the United States, is subject to applicable safeguards and provider agreements. Email click and open tracking are not enabled. Replies go to the published support mailbox. See Resend DPA and subprocessors.
Cloudflare Turnstile checks registration requests to reduce automated abuse. Browser and request signals are processed by Cloudflare and verification is checked on the server. It does not verify legal identity. This widget uses Managed mode without pre-clearance.
Internal customer administration
Account email addresses, account administration records and aggregate customer and storage statistics are internal service information. Only the authenticated Olga and Elena team accounts with second factor protection can access customer administration. These records are not published to community members. Your own account details remain visible to you. Sharing a project reveals only the project information required for that invitation, not the customer register. Infrastructure providers process data to operate the service under the provider arrangements described above.
Security and diagnostic records
We retain limited operational events such as errors and request durations for 30 days, and security/support audit records for 90 days, except documented preservation needs. Diagnostics do not intentionally include file contents, search text, passwords, cookies or authentication codes. No screen recording or keystroke tracking is enabled. Support sessions require a reason and recent second factor verification, expire after 60 minutes and are recorded under the staff identity. Users can view their account activity.
Unused accounts
We do not automatically delete accounts for inactivity. An empty customer account may be submitted for manual review after 60 days without use. We send three service reminders, normally after 45, 52 and 58 days without use. Review cannot begin until at least 15 days after the first reminder and two days after the third reminder. If reminders are delayed or fail, review is delayed. Olga or Elena must explicitly approve deletion and the service checks again that the account is empty and has not been used. Signing in cancels the review. Accounts containing any projects, files, a profile photo, community contributions, support correspondence or project memberships are excluded from inactivity deletion. Accounts with content may be marked inactive after 90 days; that label never deletes their content. For accounts existing when this policy begins on 30 September 2026, the inactivity clock starts no earlier than that date. User-requested closure follows the separate 30 day cancellation process. Encrypted backup retention also applies to approved empty account deletion.
Account use and customer administration
For service administration and safe handling of unused accounts, we record the last use of signed-in account pages or successful service actions, a visit count and daily activity dates. A new visit is counted after at least 30 minutes away; this is not a count of people or devices. Daily dates are kept for 90 days. Last-use timestamps and cumulative visit counts remain while the account exists and are removed with live account deletion, subject to the backup policy. Activity begins when this feature is enabled; earlier visits are not inferred. To show unread community posts, we also store which team posts your account has opened. These read marks are removed when the post or your account is permanently deleted. The customer register combines these records with registration date, email, nickname, project count and archive storage usage. Payments are not connected in this free beta. Only Olga and Elena can open this register, with account checks on the server and recent second factor verification. No customer register data is returned to ordinary members or project guests.
The legal basis is our legitimate interest in administering the service, evaluating adoption and closing genuinely unused empty accounts after warning. This limited internal record uses no advertising identifiers, additional analytics cookies, tracking pixels, screen recording or keystroke capture. It is separate from optional third-party analytics, which are not enabled. You may object to this processing by contacting the operator; we will assess your request and explain the outcome. Resend also processes recipient addresses and service messages for unused-account warnings.