Vox Land Privacy Policy
Updated October 3, 2026
This Policy explains how Canada Sirius Studio ("we") collects, uses, shares and protects your personal data when you use Vox Land (https://voxland.app, the "Service"), and the rights you have. We have tried to keep it plain; if anything is unclear, ask us at support@voxland.app.
1. Who we are
The Service is operated by Canada Sirius Studio, the controller of your personal data: we decide how and why it is processed. Contact: support@voxland.app.
The Service runs in regions: the Americas (voxland.app, servers in Virginia, USA) and Asia (asia.voxland.app, servers in Hong Kong, China). Each region has its own database, and your account exists only in the region where you signed up; uploaded and generated files are stored in Cloudflare R2 in North America. At sign-up we check with the other regions whether the address is already registered there, so the same person does not end up with two accounts; only the address itself is sent.
2. What we collect
We collect only what the Service needs:
- Account data: email address, password (stored only as an irreversible hash), display name, language and UI preferences; in the Asia region, also when you consented to cross-border processing.
- Third-party sign-in: when you choose to sign in with Google or GitHub, we receive your email address, whether it is verified, your account ID there and your display name. We never receive your password there.
- Content data: reference images you upload, sketches, block structures, prompts, the models and images generated for you, and organisational data such as projects and folders.
- Job and credit records: time, type, provider, status and error messages of each generation job, credit consumption and refund records, orders, and in-app messages.
- Feedback and support tickets: the messages you send us through "Contact us" or "Question these credits?" inside the site, the page and interface language you sent them from, and our replies.
- Invites: when you sign up through someone's invite link we record who invited you, to pay the inviter's reward; the link is remembered in your browser for 30 days with a cookie (vl_ref).
- Sign-up source: when you arrive through a link that carries source tags (one of our ads, for example) or from another website, and sign up during that same visit, we keep those tags (source, medium and campaign name) or that website's domain with your account, to learn which channels bring sign-ups. It is recorded once, at sign-up; no cookie or local storage is used for it, and ad platforms' click identifiers are not kept.
- Forum: your forum nickname, the posts and comments you publish with the copies of the works attached, and the reports you file. Posts and comments are public: anyone can see them (under your nickname, never your e-mail address). Whatever region your account is in, the forum is stored in the Americas region.
- Activity record: for each account, only the first and last time it was seen on each day, to count active users. What you looked at or clicked is not recorded.
- API keys and the command line: we store keys only as hashes. When you sign in from the command line, the new key's name includes that computer's host name, so you can recognise and revoke it in Settings.
- Payment data: when you buy, the payment provider returns the order ID, amount, currency, payment method type, status and its transaction reference. We never receive or store your full card number or payment account password.
- IP addresses: the address you signed up from is kept with your account, to limit how many welcome grants one network can claim; when you pair the command line, the requesting address is shown on the approval page so you can spot a pairing you did not start; addresses used for rate limiting are only counted briefly in server memory and never written to the database.
- Server logs: errors and key events (an account deletion, for example), which may include an account ID, email or IP address.
We do not deliberately collect sensitive data such as government ID numbers, precise location or biometrics. Please keep such data out of prompts and uploads.
3. Why we use it
We process your data for these purposes and on these bases:
- Providing the Service (our contract with you): creating and maintaining your account, running generation jobs, storing and displaying your assets, settling credits.
- Payments and accounting (contract and legal obligation): processing orders, issuing receipts, meeting accounting and tax requirements.
- Security and compliance (legal obligation, and our legitimate interest in a safe Service): login verification, the human check at sign-up, preventing abuse and fraud, content moderation, handling complaints and legal requests.
- Improving the product (legitimate interest, or consent where the law requires it): usage statistics, active-user counts and troubleshooting, using aggregated or anonymised data wherever possible.
- Keeping generation quality up (legitimate interest): our operators can look at what went into a generation job and what came out — prompts, block renders, reference images, the models and images made — in the admin area, to check quality, troubleshoot and handle your feedback. Only operators see it; it is never shown publicly or used for anything else.
- Communicating with you: service notices such as job results, credit changes or changes to our terms, mostly as in-app messages and by email where needed (a password reset, for example). Marketing is sent only with your consent, and you can opt out at any time.
We do not sell your personal data. Unless we expressly tell you otherwise, and obtain consent where the law requires it, we do not train AI models of our own on your content or outputs.
4. Cookies and local storage
We use only cookies the Service needs to work: no advertising or tracking cookies, and no third-party analytics, advertising or tracking SDKs.
- vf_session: keeps you signed in; httpOnly (browser scripts cannot read it); ends when you sign out or when it expires;
- vf_locale: remembers your interface language, for a year;
- vf_nav: remembers whether the sidebar is collapsed, for a year;
- vf_oauth: used during a Google / GitHub sign-in only, expires after 10 minutes and is sent only to the sign-in endpoints.
UI preferences, such as collapsed panels, your progress through the tour and the region you chose, live in your browser's localStorage. They are never sent to our servers and disappear when you clear browser data.
In the Americas region, the sign-up and password-reset pages use Cloudflare Turnstile as a human check, which may set its own cookies; payment providers may set cookies on their checkout pages. These fall under their own privacy policies.
5. How we share data
We share data only as needed to run the Service, with the providers below, which process it on our instructions or under their own terms of service. The website in brackets is where each can be contacted:
- Tencent Cloud (tencentcloud.com): server and database hosting (Virginia, USA and Hong Kong, China).
- Cloudflare (cloudflare.com): file storage (R2, North America), database backup storage, DNS; Turnstile human check on the Americas sign-up pages.
- Stripe (stripe.com): processing payments (cards, Alipay and others) and returning order results.
- Resend (resend.com): sending account emails (password resets, for example).
- Google (google.com), GitHub (github.com): only when you choose to sign in with them.
- AI model providers: fal.ai (fal.ai; hosts 3D models such as Hunyuan3D, Rodin and TRELLIS and image models such as GPT Image, Nano Banana and FLUX, and is also used to translate prompts into English and to cut out backgrounds; closed models are passed on by fal to their developers, for example GPT Image to OpenAI, and Nano Banana and the Gemini model used for translation to Google), Tripo (VAST, tripo3d.ai) and PiAPI (piapi.ai). To run a job we send your prompt, reference images, sketches, and the views and depth maps rendered from your block structure to the provider behind the tier or model you picked. These are independent third parties; whether they retain the data, for how long, and whether they use it to improve their models depends on each provider.
- Content moderation: the moderation API of OpenAI (openai.com) checks prompts and images (moderation requests from the Asia region are relayed through the Americas region).
- Third parties your browser contacts directly: the Material Library in the pro model editor loads textures and lighting straight from the servers of Poly Haven (polyhaven.com), which then see your IP address.
We may also disclose data where the law requires it, on a lawful request from a court or authority, or to protect our rights and those of our users. In a merger, acquisition or asset transfer your data may be transferred as part of it; we will notify you in advance.
6. International transfers
Most of the servers and providers listed above sit outside your country or region, so your data is stored or processed abroad.
If you are in mainland China, note in particular: the Asia region's servers are in Hong Kong, files are stored in Cloudflare's North American storage, and every generation sends your prompt, reference images and block renders to the overseas AI providers named in section 5. The names of these recipients and where to contact them are in section 5; the purpose is to run the jobs you submit and to operate the Service, the processing consists of storage, generation and content moderation, and the personal data involved is mainly account identifiers, prompts and the images you upload. You can exercise your rights of access, correction, deletion and so on by writing to support@voxland.app; where an overseas recipient is involved, we coordinate it.
In the Asia region we ask for your separate consent to these transfers: a box you tick at sign-up, or a confirmation page before you start. You may withdraw it at any time by writing to support@voxland.app, or by deleting your account in Settings. Without it we cannot generate for you.
If you do not want your personal data sent abroad, keep personal data out of your prompts and uploads.
7. How long we keep data
- Account, content and records: account data, uploads, generated files, job records, credit records, orders, the activity record and in-app messages are kept while your account exists (at most the latest 200 messages per account; older ones are deleted automatically). You can delete assets and files individually at any time; when you delete your account, all of this is deleted from our database and file storage immediately.
- Database backups: one a day, kept 30 days in cloud storage and 3 days on the server disk, then deleted automatically. After you delete your account, the copies in backups are gone within 30 days at the latest; until then backups are used only for disaster recovery.
- Server logs: kept for troubleshooting and security; they rotate by size and are cleared at every service update, so they are normally kept for days to weeks.
- Payment records: transactions and payer details are kept by Stripe under its own policy and the law; to meet accounting and tax obligations we can retrieve them from Stripe for the period required by the law of Ontario, Canada.
8. Security
Passwords are stored only as salted hashes; data in transit is encrypted with TLS; the session cookie is httpOnly and Secure; API keys are stored only as hashes; access to production data and provider keys is limited to what running the Service requires.
No system is perfectly secure. If a personal-data breach may affect you, we will notify you and the relevant authorities as the law requires.
9. Your rights
Depending on where you live, laws such as China's PIPL, the GDPR, the UK GDPR or the CCPA/CPRA give you rights over your personal data. In plain terms, you may:
- Access: learn what data we hold about you and receive a copy.
- Correct: have inaccurate or incomplete data fixed. Display name and language can be changed in Settings.
- Delete: have your content or your whole account deleted (see retention above); you can delete your account yourself in Settings.
- Export (portability): receive your content and generated files in a common, machine-readable format.
- Withdraw consent: at any time, where processing is based on consent (including the Asia region's cross-border consent), without affecting earlier processing.
- Object or restrict: object to processing based on legitimate interests, or ask us to restrict it, where the law provides.
- Opt out of sale: we do not sell personal data, and we will not discriminate against you for exercising your rights.
- Complain: to your local data-protection authority.
To exercise these rights, email support@voxland.app. We may need to verify your identity. We normally respond within 15 working days, and always within any shorter period the law requires.
10. Children
The Service is for adult developers. We do not offer it to children under 14 and do not knowingly collect their data; if we learn that we have, we delete it promptly. Parents or guardians who become aware of this should contact us.
11. Changes to this Policy
We may update this Policy. Material changes, such as new data categories or new recipients, are announced before they take effect by in-app notice or email, with fresh consent requested where required. The latest update date is shown at the top of this page.
12. Contact
For any privacy question, request or complaint, contact Canada Sirius Studio at support@voxland.app.