Contour Studio Online contour maps for specialists
Home Open workspace Terms Contact privacy

Legal

Privacy Policy

Last updated: June 6, 2026

Contour Studio helps specialists and small technical teams create contour maps and grid outputs from engineering data. This policy explains how we handle data in browser-local workflows, cloud features, uploaded files, API calls, and support requests.

1. Data We Process

Depending on the features you use, we may process point data, CSV or XYZ files, fault or boundary files, project settings, interpolation parameters, grids, contours, map styles, exports, project snapshots, account identifiers, collaboration records, support messages, and service logs.

2. Browser-Local Workflows

Core browser-local workflows read files in your browser and can store local drafts, style templates, and workspace preferences in browser storage. Browser-local data remains on your device until you clear it through the product or your browser settings.

3. Cloud Processing

When you use cloud-backed features such as high-resolution processing, saved projects, collaboration, batch jobs, exports, style synchronization, or AI assistance, the related project data is sent to our servers to provide those features.

Saved cloud project data is permanently deleted after 30 days. Saved cloud project data includes project records, project settings, snapshots, generated grids, contour results, export outputs, and other saved computation artifacts. It does not include raw uploaded source files or transient API payloads, which follow the shorter deletion windows below.

4. Raw Uploaded Engineering Files

Raw uploaded engineering files are deleted approximately one hour after upload. This applies to the original source files you upload for processing, such as CSV, XYZ, boundary, or fault files.

5. API Calls

API input and output payloads are deleted after the API call is processed, unless you explicitly save the result into a cloud project. We may retain minimal operational logs needed for security, abuse prevention, billing, or debugging, but those logs should not contain complete engineering project files.

6. AI Assistance

If you use AI assistance, we may send the necessary project context, summaries, grid information, style settings, and quality-check inputs to the service components needed to generate recommendations. Do not use AI assistance for data that you are not allowed to submit to cloud services.

7. Cookies and Local Storage

Contour Studio currently relies on browser storage for local drafts and templates. We do not use advertising cookies in the current product. If we introduce analytics, login cookies, or other cookie-based tracking, we will update this policy and provide the required notice or controls.

8. Third-Party Service Providers

We may use hosting, storage, compute, email, analytics, payment, or AI service providers to operate Contour Studio. These providers may process data only as needed to provide the service, maintain security, complete user requests, or comply with legal obligations.

9. Security

We use reasonable technical and organizational safeguards, including access controls, transport encryption, limited retention, and deletion workflows. No online service can guarantee absolute security, so you should avoid uploading data that you are not authorized to process in an online tool.

10. Your Choices

You may use browser-local workflows without cloud project storage when available. You may clear local browser data through your browser settings. You may also contact us to request access, correction, or deletion of server-side data associated with your account or project.

11. Contact

For privacy questions or deletion requests, contact privacy@quickcontour.com.

12. Changes

We may update this Privacy Policy as the product, infrastructure, or legal requirements change. The updated policy will show a new effective date.

Contour Studio
Terms of Service Privacy Policy
Professional contour maps for focused technical work.