LegalPRIVACY
Privacy Policy
How Lovcad handles account information, cloud workspaces, AI requests, and credit billing records.
- Document
- Privacy Policy
- Version
- 2026-10-13
- Language
- English
- Sections
- 11
Contents
- 01Who is responsible for your information
- 02Browser computation, cloud storage, and AI requests
- 03Information we process
- 04Why we use information and our legal bases
- 05Cookies and local storage
- 06Service providers, disclosures, and international processing
- 07How long we keep information
- 08Your rights
- 09Security and incident response
- 10Minors
- 11Changes and contact
Last updated: October 13, 2026
Effective date: October 13, 2026
1. Who is responsible for your information
Lovcad is independently developed and operated by an individual, primarily serves the US market, and is available in English and Chinese. The operator is responsible for the personal information Lovcad collects and for determining how it is used. This does not imply that the operator has incorporated a US company or is a US tax resident. Contact support@lovcad.com about privacy, data rights, or security.
This policy explains how information is handled across our website, accounts, CAD workspace, subscriptions, and credit services. Using the website does not amount to blanket consent to every processing activity. Where the law requires consent, we will ask for it separately.
2. Browser computation, cloud storage, and AI requests
CAD geometry is computed in your browser, but design materials do not always stay solely on your device. Project names, ownership, and status are stored in the account system. Synced conversations, source code, parameters, execution logs, model files, thumbnails, and saved versions are stored in private cloud storage, with access separated by account and project.
Your browser's IndexedDB stores a local workspace cache and changes awaiting sync. Once a cloud save is confirmed, you can sign in on another device to restore the saved work. Signing in again does not automatically restore unsynced changes. Before clearing browser data, wait for cloud save confirmation and back up important designs.
When you use AI modeling, the conversations, source code, tool results, model preview images, and other content needed to generate or modify a design are sent through our service gateway to external AI infrastructure and model providers for inference. Modeling in your browser does not mean all information stays on your device.
If you email screenshots, design files, or project information to support, we also receive that content as part of the support record. Do not include passwords, API keys, or unnecessary sensitive personal information in design requests or support attachments.
3. Information we process
- Account information: Display name, email address, email verification status, and creation and update timestamps. Email-and-password registration stores a password hash, and email verification codes are also hashed. We do not store plaintext passwords.
- Session and security information: Session identifiers and expiration times, IP addresses, browser user agents, and verification and rate-limiting records used to recognize signed-in users and prevent abuse.
- Design and workspace information: Project names, prompts, conversations, source code, parameters, tool inputs and outputs, models, thumbnails, run records, saved versions, and design materials you submit through available features. Design content may include personal information you choose to enter.
- Order, subscription, and credit information: Account identifiers, checkout email, plan, order and payment provider identifiers, amount, currency, payment status, billing periods, renewal cancellation status, refunds, credit allocations, balances, reservations, and usage ledger entries, including model usage and cost records used for billing. Waffo Pancake and its payment providers handle full card numbers and security codes; those details are not stored in Lovcad's database.
- Network and operational information: Request paths, timestamps, IP addresses, errors, and operational logs needed for hosting and security, along with request identifiers, transfer diagnostics, and workspace sync status used to investigate problems.
- Support information: Emails, feedback, order details, and files you choose to attach. Do not send passwords, full payment card details, or unnecessary sensitive information.
Google sign-in is not currently available, so we do not collect third-party account information through that method.
4. Why we use information and our legal bases
We use account, session, design, and workspace information to fulfill our contract to provide modeling, storage, syncing, and recovery. We use order, subscription, and credit information to verify payments, issue credits, settle usage charges, process refunds, and provide support.
Where necessary to protect accounts, prevent fraud, diagnose problems, and maintain the service, we rely on legitimate interests where permitted by applicable law, taking your rights and interests into account. We rely on legal obligations for tax compliance, required transaction records, and valid legal requests. Optional processing that requires consent is based on your separate consent.
Verification codes, password resets, and necessary billing and security notices are service communications. We do not currently offer a marketing email subscription. We do not use nonpublic design content for advertising profiles or sell it. Without your separate, express authorization, Lovcad will not use nonpublic inputs, conversations, source code, or outputs to train its own AI models or feature them in public showcases.
Sending necessary content to external AI services is part of inference. Their retention and training restrictions depend on the actual service configuration and applicable contracts. We do not treat use of modeling features as blanket permission for additional training purposes, and we do not promise end-to-end zero retention where that has not been verified.
5. Cookies and local storage
Essential session cookies keep you signed in. Language preference cookies and browser storage support interface settings, while IndexedDB stores workspace caches and unsynced changes. During email verification, the current browser tab also temporarily stores the email address awaiting verification.
You can block or clear this data, but doing so may sign you out, reset preferences, or remove unsynced work. Signing out does not delete all account data, and clearing browser data does not delete cloud projects. See our browser storage notice for more information.
The current public website does not load third-party browser behavior analytics, advertising trackers, or third-party chat widgets, and it does not have a dedicated cookie preference center. If we introduce optional analytics or tracking that requires consent, we will first update this notice and provide the appropriate choices. Waffo's payment pages use their own storage mechanisms.
6. Service providers, disclosures, and international processing
We do not sell personal information or share it for cross-context behavioral advertising. We process relevant information with the following providers only for necessary purposes:
- Cloudflare: Website hosting, security, account and billing databases, private workspace databases and file storage, and transactional email. This involves the account, project, design, request, and email information needed to provide those services. See Cloudflare's Privacy Policy.
- AI infrastructure and model providers: Conversations, source code, tool results, model preview images, and other request content needed to generate or modify designs, for inference and necessary operational support. Inference requests are not intended to transmit payment card details.
- Waffo Pancake: Payments, subscriptions, transaction taxes, refunds, and fraud prevention as Merchant of Record. Checkout passes account identifiers, email, the selected plan or credit pack, and order references so payment can be linked to the correct account. It does not pass CAD design files or modeling conversations. Refer to the privacy policy shown at checkout for your transaction.
- Support email providers: Messages and attachments you send, and the information needed to reply.
Where a payment provider independently processes information to meet its own transaction, tax, and fraud-prevention obligations, its own policy applies to those activities. This does not remove our responsibility for our own processing.
We may also make necessary disclosures in response to valid legal requirements, to protect lawful rights, or with your express authorization. If a business transfer involves personal information, we will notify affected users and require the recipient to comply with applicable data protection obligations.
These providers may process information in the United States and other countries. Serving the US market does not mean information is stored only in the United States. International processing must comply with applicable law. Where safeguards such as standard contractual clauses are required, the applicable mechanism must be in place before the transfer. We do not claim specific storage locations or agreements that have not been verified. Contact us to learn about the arrangements applicable to your information.
7. How long we keep information
The following retention schedule is proposed and remains subject to confirmation and implementation by the operator. It does not mean the system already has automated deletion for these periods:
| Category | Proposed retention and deletion |
|---|---|
| Local workspace cache and unsynced changes | Until you clear site data, the browser removes it, or a local cleanup process runs. Removing a local copy does not delete the cloud copy. |
| Account and session records | While the account is active, followed by deletion or anonymization of information no longer needed within 30 days after verified account closure, except transaction records that must be retained by law. |
| Cloud workspaces and design files | While the project is active. We propose completing cleanup of unnecessary content within 30 days after verified account closure or confirmed project deletion. Access is revoked first, followed by cleanup in batches. Minimal deletion markers may remain to prevent old requests from restoring deleted content. |
| Orders, refunds, and necessary transaction and credit records | Proposed retention of seven years from transaction completion for accounting, tax, and dispute purposes, subject to confirmation under the laws actually applicable to the operator. Usable nonexpiring credits and the records needed to support them are not deleted merely because the original transaction is seven years old. Once those benefits are settled, records are deleted or anonymized in accordance with applicable retention requirements. |
| Support records | Up to two years after the issue is closed, then deleted. Records for unresolved disputes remain until resolution and the end of any legally required period. Unnecessary identity verification materials are proposed to be deleted within 30 days after verification. |
| Separate operational, security, and rate-limiting logs | A proposed maximum of 90 days, subject to verification of infrastructure and email provider settings and implementation of site cleanup processes. Conversations and execution logs needed to restore a project follow the cloud workspace schedule; they are not deleted simply as diagnostic logs. |
| Backups and provider copies | Rotation and deletion periods still need to be verified individually. Deletion from the primary system does not mean every copy disappears at the same time. Copies isolated for legal retention are not used in day-to-day operations. |
Verification codes are valid for 10 minutes. Login sessions are valid for seven days and may be refreshed as you use the service. These are authentication validity periods, not confirmation that the records have been physically deleted. Canceling renewal is not account closure and does not automatically delete projects or unused nonexpiring credits.
Where the law requires longer retention, we limit the records to what is necessary and do not use them for other purposes. Payment providers follow the rules applicable to their own independent transaction retention obligations.
8. Your rights
Depending on applicable law, you may request information about and access to your personal information, obtain a copy, correct errors, request deletion, restrict or object to certain processing, receive a portable copy, and withdraw consent. Withdrawal does not affect processing that was lawful before you withdrew. Eligible US state residents may also have opt-out, authorized-agent, and appeal rights under local law. We will not discriminate against you for exercising your legal rights.
Email support@lovcad.com from your account email address and describe your request. We will ask only for information needed to verify your identity, not your password or full payment card number. Our proposed response target is 30 calendar days after receipt, subject to applicable legal deadlines. If a lawful extension is needed, we will explain why and give an expected timeframe. If we deny a request, you can appeal by email or complain to a data protection or consumer protection authority with jurisdiction.
You can clear local caches in your browser and remove cloud projects using the project deletion feature. Full account deletion requires a request to us for manual handling. Account deletion may affect subscription and credit access, so first check outstanding orders, cancel renewal, and arrange for any remaining balance to be addressed. Transaction records retained by law will not all be deleted at the same time.
9. Security and incident response
We use HTTPS, hashed passwords and verification codes, authentication, and server-side project ownership checks to protect information. Private workspace files are accessed through authorized routes. Payment callbacks must pass signature and environment checks before entering billing processing. No network or storage system can be completely secure; protect your email account and devices.
If a personal data breach occurs, we will investigate, contain the impact, and notify regulators and affected users as required by applicable law and within the applicable deadlines. For example, where the GDPR's supervisory reporting requirement applies, we will report without undue delay and, where feasible, within 72 hours of becoming aware of the breach. This is not a universal notification deadline for every incident or every user, and it is separate from the refund receipt timeframe in our Terms of Service.
10. Minors
Accounts and paid services are for users aged 18 or older. The service is not directed at minors, and we do not knowingly collect personal information from users below that age. If a parent or guardian believes a minor has provided personal information, contact us so we can investigate and take appropriate steps, including deletion where required by law.
11. Changes and contact
We will update this policy when our actual processing practices change. We will give at least 14 days' notice of material changes through the website or account email, except where legal or urgent security requirements apply. We will seek separate consent for new purposes that legally require it; continued use is not a substitute for consent.
The individual operator described above is the privacy contact. For privacy, data rights, security, and support, email support@lovcad.com. Support is provided by email; we do not promise immediate, round-the-clock responses. Purchase terms are set out in our Terms of Service.