CADGROUND CLOUD / LEGAL
Privacy Policy
Review draft · 16 October 2026. This version is for review and has not been adopted as the final policy.
This notice describes information processed when you use CADground Cloud. In this document, “we” refers to the operator of CADground Cloud. Your organization decides what information to upload and whom to authorize; project content is processed to carry out the work requested through the service.
1. Account and organization information
We process your email address, account and profile information you provide, organization name, memberships, permissions and project metadata. Authentication records include password hashes and verification or reset information. The application hashes account passwords rather than storing them as readable passwords.
2. Project content and AI conversations
The service stores uploaded scans, point clouds, meshes, documents, images, saved scenes, conversations, tool results and generated files needed for your projects. This material may contain personal or confidential information. Only upload information you are authorized to process through CADground and its external providers.
Relevant messages, project files, rendered scene views and tool context may be sent to external AI providers to answer your requests or perform requested work. Agent tools may also contact external websites or services, transmitting search queries or other information needed for the requested operation. AI-related request records may include model information, content needed for processing and diagnostic context. The Usage page reports requests and input, output and cached tokens; usage totals do not imply that no other AI processing records exist.
3. Voice input
Voice recording starts when you activate voice input and grant microphone access. Audio is sent for transcription through AppWizzy to OpenAI, and the returned text is placed in your message draft. When you send that message, its text becomes part of the conversation.
The current CADground transcription service processes audio in memory and does not intentionally save an audio file in the project. This does not describe or guarantee deletion from infrastructure logs or external providers’ systems. Provider retention and data-use practices also apply to audio sent for transcription.
4. Technical and usage information
Hosting, routing and service operations process technical information such as IP addresses, request metadata, browser or connection information, session identifiers, service errors and resource usage. We use account and project information to provide access and run your projects, and operational information to maintain security, diagnose failures and account for resource and AI usage.
5. Browser storage and sessions
The application uses browser local storage for your sign-in token, user information and preferences such as language and appearance. The protected editor also uses session cookies to authorize project access. Clearing browser storage or blocking required cookies can sign you out or prevent the editor from opening.
Browser permission for the microphone is separate from sign-in and can be withdrawn in browser settings.
6. Service providers and authorized access
AppWizzy provides hosting integration and infrastructure services. External AI providers process information needed for AI requests; current integrations include OpenAI. Email delivery providers process addresses and message information for account verification, password resets and other service emails. Authorized organization members can access information allowed by their project permissions, and authorized operators may access information needed to run and support the service.
On Pro, the service may run an internal browser beside your project data so requested AI work can continue after you close the editor. If you connect an external AI client through MCP, it can receive project information and tool results within the permissions you approve. Its provider’s data practices also apply. You can revoke the connection on the project page; revocation does not erase information already received by that client or provider.
External providers process information under the arrangements and policies applicable to the enabled service. We cannot currently guarantee a uniform retention period or exclusion from model training across every AI provider and account configuration. Contact support before submitting information subject to specific confidentiality or data-processing restrictions.
Information may also be disclosed where required by applicable law or necessary to investigate abuse, protect service security or address legal claims. This notice does not grant a general permission to publish private project files.
7. Retention and project deletion
Account and project information is retained while needed to provide your account and projects. Operational, usage and other records may be retained for security, service administration, applicable legal obligations and resolving disputes. Retention depends on the purpose and where the information is stored.
Stopping or archiving a project retains its files. Confirmed project deletion removes its active runtime environment. It does not automatically erase every related record: historical usage and chat or session records stored separately may remain, and backup copies and external-provider records can have different retention schedules. Moving Free work to Pro also leaves earlier chat history in Free.
You can download available project files before deletion. Requests about closing an account or deleting retained personal information can be sent to support; project deletion and account-data requests are separate actions.
8. Security and international processing
CADground uses authenticated project access, organization permissions, protected editor sessions and password hashing. These measures reduce risk, but no service can guarantee absolute security.
Hosting and external providers may process information in countries other than your own. Applicable transfer requirements and the arrangements with the relevant providers must be considered when using the service. This draft does not claim that data stays in a particular country or that every provider uses a particular transfer mechanism.
9. Your choices and privacy requests
You can manage available profile information, choose what to upload, download available project files, control microphone permission and ask support about retained personal information. Depending on applicable law, you may have rights to access, correct, delete, restrict or object to processing, receive a portable copy, or complain to a competent data-protection authority. We may need to verify your identity and authority to act for an organization before fulfilling a request.
Where processing relies on consent, you may withdraw that consent without affecting prior lawful processing. Some information may need to be retained under applicable legal obligations or to protect other people’s rights.
10. Payments and future changes
Live paid checkout and credit purchases are not currently enabled. The current Mollie integration supports test payments only. If test checkout is enabled and you use it, CADground sends Mollie the organization name, identifiers and payment details such as the amount, currency and subscription reference. Payment-method entry happens on Mollie’s hosted checkout. CADground retains provider references, payment and subscription status and transaction history; its billing integration does not receive your full card number or security code.
Mollie processes payment-related information under its privacy statement. Test checkout is clearly marked and does not charge real money; it can still process information you provide. Before live payments or material changes to data uses, we will update this notice and obtain consent where required. A change to this notice does not itself authorize a new use of previously collected information.
11. Contact
For privacy requests or questions about this notice, contact support@flatlogic.com. Include enough information to identify your account or request, but do not send passwords or access tokens. See the Terms of Use for the rules governing use of the service.