Terms of Service

Effective 2026-10-25 · Version 2026-10-25.2

These terms cover your account, this portal, and the licensing service behind it — the parts that are the same whichever of our products you use. The software itself is covered by that product's End User Licence Agreement, and what we store about you by the Shared Privacy Notice.

Who you are contracting with

Dmytro Vakulenko, freelance software developer, Franklin Rooseveltlaan 19, Ghent, Belgium. VAT BE 1018.539.293. Telephone +32 492 92 86 95. Email dmytro.vakulenko.mail@gmail.com.

The short version

These are young products. They change often, may break, and come with no uptime promise. Don't rely on them for anything where a failure would be costly. The licensing API does not collect drawing contents; the hosted Drawing service does, as its product privacy addendum explains. The Shared Privacy Notice describes what we store, including any optional support report you choose to send.

Your account

One account, identified by a verified email address, serves every product here. You are responsible for keeping your API keys confidential — anyone holding one can act on your account's behalf. Revoke a key the moment you suspect it has leaked.

Some keys are publishable and ship inside a public web page by design. Those are bound to the web origins you register, and that binding is what protects them; the same confidentiality expectation does not apply, and cannot.

Plans, limits and what a limit does

Each product is sold on a plan with published limits — see pricing. Where a plan carries more than one limit, the tighter one binds. Reaching a limit does not break anything: calls are refused with the time your allowance resets, and everything works again after it.

Every plan also carries a per-minute ceiling. That is abuse protection rather than a sold limit, and it exists because a runaway automated loop can otherwise hammer both our service and your own machine at machine speed. We may publish limits upward; we will not quietly reduce what a paid plan offers.

A plan applies to one product. Subscribing to one does not change your limits on another.

Paying

Subscriptions are monthly and renew until you cancel. Public consumer prices show a Belgian VAT-inclusive reference total (21% VAT) alongside the net price. Your final tax-inclusive total is shown by Stripe before you pay and depends on the applicable tax rules and your billing details. Eligible cross-border business purchases may qualify for reverse charge after validation; entering a VAT number alone is not a promise of exemption. Every payment produces an invoice carrying our Belgian VAT number.

Payment is processed by Stripe. We never see or hold your card details. If a payment fails we will keep your plan running while Stripe retries; if the retries are exhausted the subscription is cancelled and your account returns to the free tier.

You can cancel at any time from the Account page. Your plan then runs to the end of the period you have already paid for and reverts to free — nothing is deleted, and your keys keep working under the free limits.

Your right to withdraw

You can submit a withdrawal online using Withdraw from a purchase. Enter or confirm your name, purchase details and confirmation email, review the statement and select Confirm withdrawal. No sign-in, reason or new agreement is required. We record the submission time and send a receipt containing your statement and that time. You may also withdraw by an unequivocal statement to the contact email above. Withdrawal concerns that purchase and any refund due; it is separate from deleting your account or cancelling future renewals.

If you are a consumer buying a paid subscription, you may withdraw within 14 days from conclusion of the contract without giving a reason. Starting access or accepting our terms does not waive this right. We do not require a withdrawal waiver or charge for use during that withdrawal period.

To withdraw, send an unequivocal statement to Dmytro Vakulenko, Franklin Rooseveltlaan 19, Ghent, Belgium, telephone +32 492 92 86 95, email dmytro.vakulenko.mail@gmail.com. Sending your notice before the 14-day deadline is sufficient. You may use the form below, but do not have to. We reimburse all payments for the withdrawn subscription without undue delay and within 14 days of your notice, using the original payment method unless you expressly agree otherwise, without a reimbursement fee. Access to the withdrawn paid service ends.

Model withdrawal form

Complete and return this form only if you wish to withdraw:

To: Dmytro Vakulenko, Franklin Rooseveltlaan 19, Ghent, Belgium; dmytro.vakulenko.mail@gmail.com
I/We (*) hereby give notice that I/We (*) withdraw from my/our (*) contract for the provision of the following service: __________
Ordered on (*) / received on (*): __________
Name of consumer(s): __________
Address of consumer(s): __________
Signature of consumer(s) (only if this form is notified on paper): __________
Date: __________
(*) Delete as appropriate.

You can print or save this document, including the form, from its exact-version page.

Acceptable use

Use each product for its intended purpose. Don't attempt to circumvent usage limits, share credentials to avoid them, or use the service in a way that disrupts it for others.

Availability, and what you can expect

We supply the service in conformity with these terms and with what you can reasonably expect of it. If it does not conform, you are entitled to have that put right, and where that fails, to a proportionate price reduction or to end the contract. Directive (EU) 2019/770 gives you these rights by law once you pay; nothing here reduces them.

What is reasonable to expect is shaped by what we say plainly: these are young products with no uptime guarantee, and the portal may be unavailable while we change it. Where a product holds a signed licence lease, it keeps working offline for the remainder of that lease and the allowance already granted to it.

Our liability

We are fully liable for death or personal injury caused by our negligence, for damage caused intentionally or by gross negligence, and for anything else the law does not permit us to limit. Our liability is not limited where we fail to perform a main obligation of these terms. For other breaches, except where the law requires otherwise, liability is limited to foreseeable loss typical for a contract of this kind.

In practice the risk worth naming is this one: an assistant driving your software can make a change you did not intend. Review what it does before you rely on it, the same way you would review a colleague's edit. Nothing here limits liability we cannot lawfully limit under the law of your country of residence.

Ending your account

You can delete your account at any time from the Account page, and we will not ask you to accept anything new before letting you. Note that deleting your account does not cancel a Stripe subscription — only you can do that, in the billing portal. Cancel first if you mean to stop paying.

We may end or suspend your account for a material breach you have not put right within 14 days of us asking, or immediately where a breach is causing ongoing harm — and we will tell you why. Some records are retained after deletion; the Shared Privacy Notice says which, and for how long.

Changes to these terms

We may update these terms as the products mature. A change that affects what you agreed to will ask you to accept the new version before you can create a new key or connect a new device — your existing connections keep working.

Law and disputes

Belgian law applies. If you are a consumer, this does not deprive you of the mandatory protection of the country where you habitually reside. You may bring proceedings in that country or in Belgium; we may only sue you in the courts of your country of residence.

First contact us about a complaint. A consumer may approach the Belgian federal Consumer Mediation Service (Service de Médiation pour le Consommateur / Consumentenombudsdienst), North Gate II, Boulevard du Roi Albert II 8 bte 1, 1000 Brussels — consumerombudsman.be, French-language contact +32 2 702 52 20, contact@mediationconsommateur.be. We are not obliged to participate in an out-of-court settlement procedure and do not commit in advance to doing so.

Product agreements

Control MCP Server agreements · Drawing MCP Server agreements. These documents are public and can be read before signing in.

Each product has its own terms and privacy addendum, shown when you enable that product. Enabling another product does not accept its documents on your behalf. You can read and download the exact documents and acceptance receipts from your account. Existing connections are not disabled merely because another product's documents change.

Adapted from Basecamp's open-source policies, licensed under CC BY 4.0.

Shared Privacy Notice

Version 2026-10-25.6

Who processes your data

Dmytro Vakulenko, freelance software developer, Franklin Rooseveltlaan 19, Ghent, Belgium. VAT BE 1018.539.293. Telephone +32 492 92 86 95. Email dmytro.vakulenko.mail@gmail.com.

This notice covers the shared account, licensing and billing services. The product-specific privacy addendum explains what happens to your drawings and other product data. Only the addendum for a product you enable applies to that product's processing.

Account and licensing data

We receive your verified email and identity-provider subject when you sign in, and keep an internal account ID, linked sign-in identities, account status, product enrolments, subscription references and plan expiry. Licensing stores key hashes, key labels, device identifiers and names where supplied, software versions, usage counts and timestamps. It does not receive drawing bytes, local file paths, prompts or CAD tool arguments.

Acceptance records

When you explicitly accept a product's terms and acknowledge its privacy notices, we store an append-only receipt: account and product IDs, authenticated sign-in subject, timestamp, action source, the exact confirmation wording, and each document's identifier, version and SHA-256 hash. Immutable copies of the displayed documents are archived separately. Older version-only records remain marked as legacy evidence; we do not claim that you accepted newly introduced addenda. Your account can retrieve its receipts. Receipts are kept while your account exists and removed on account deletion; document archives contain no account identifiers and remain available.

Payments

Stripe receives your payment details directly. We receive customer, checkout, subscription, invoice and payment-status references, and information needed to supply your plan. We do not receive your card number. Stripe's own privacy notice applies to its processing.

Purpose and legal basis

Account, licensing and billing processing supplies the services you request and performs our contract. Required financial records meet legal obligations. Security, fraud prevention, usage enforcement and audit records serve our legitimate interests in operating and defending the service. Privacy acknowledgement is a record that a notice was supplied; it is not blanket consent to optional processing. Optional measurement and contact permissions are separate, can be refused, and have their own withdrawal controls.

Providers and location

Shared account and licensing storage is hosted in Microsoft Azure West Europe. Clerk provides sign-in; your identity information may reach the United States. Stripe handles billing and tax; its group may process data outside the EEA. Microsoft Azure Communication Services delivers purchase confirmations, privacy-update service notices and withdrawal receipts. Withdrawal receipts use the address you provide on the public form; other service notices use the verified account address. Google processes correspondence you send to our Gmail contact address. Support report contents stay in private product-specific Azure storage; only a content-free notification reaches the maintainer's Gmail mailbox. The relevant product addendum explains report storage and retention. Your chosen AI host processes the tool results you send through it under its own terms and privacy notice. Clerk describes EU–US Data Privacy Framework transfers and fallback standard contractual clauses in its Data Processing Addendum. Stripe describes its Data Privacy Framework and fallback clauses in its Data Transfers Addendum; it acts as both a controller and a processor depending on the service. Microsoft publishes its contractual transfer safeguards in the Microsoft Products and Services DPA. Google publishes its transfer information in its transfer framework notice. Contact us to request further information or a copy of the applicable safeguards. These provider documents do not mean all data remains in the EEA.

Retention and deletion

Cleanup is scheduled; physical deletion can lag a deadline during downtime, a storage outage or a backlog, and is retried.

CategoryRetention / deletion
Licensing account, local identity links, product enrolments, keys and outstanding allowancesRemoved on account deletion. Key revocation disables access; revoked metadata remains until pruning or account deletion.
Detailed acceptance receiptsUntil account deletion. Exact non-personal document archives remain available.
Contract-confirmation delivery queueVerified account email, product, plan, first-period total/currency, subscription reference, frozen document bundle and delivery identifiers/status. Removed on account deletion or after 90 days. A confirmation containing the actual contract documents is emailed after a new checkout; your mailbox provider controls the copy delivered to you.
Device sign-in records, including approved credentials awaiting collectionSign-in expires after 15 minutes. Collection removes the record immediately; expired abandoned records are cleaned by a worker scheduled every five minutes.
Daily, weekly and monthly usage countsPurged nightly using a 14-day cutoff after the relevant periods. Current allowances survive account deletion under a stable hashed identity to prevent quota resets. Hashes are pseudonymous, not anonymous.
Trial-abuse markerRetained while used by an account and up to 12 months after account deletion to prevent immediate trial resets. Returning to use the account preserves its original trial start. Expired deleted-account markers are removed by scheduled cleanup.
Optional Control advertising measurementClick identifier removed after Google confirms conversion processing, on withdrawal, or after 90 days from the click. Consent/version and request diagnostics remain until account deletion; withdrawal markers remain while a deletion request is pending.
Security and account audit eventsOne year, including after account deletion, then scheduled deletion.
Stripe webhook deduplication identifiers30 days. Events older than that are not applied again.
Drawing account-erasure workAccount ID and request time only, retained for seven days after an erasure request while the worker repeatedly removes that old account's Drawing files. Failures remain queued for retry.
Payment and invoice records at StripeRetained under applicable financial and legal obligations, independently of account deletion here.
Support reportsPrivate product-specific Azure Blob storage for 90 days from submission. Imported legacy emails keep their original deadline. Deduplication metadata is retained for one year; rate-limit counters for 14 days. Generic owner notifications contain no report contents or reporter identifiers.

Cookies and browser storage

The account portal uses Clerk authentication cookies, including __session and __client_uat, to maintain and check your sign-in session. Clerk also manages cookies on its sign-in domain. These are necessary for the sign-in service you request, not advertising consent. Session tokens are renewed during an active session; persistence depends on the sign-in/session settings. You can sign out or clear site data to remove browser access. Blocking these cookies can prevent sign-in. See Clerk's cookie documentation.

Payments take place on Stripe's own hosted checkout, where Stripe uses cookies for payment and fraud prevention. See Stripe's cookie policy for its names, purposes and lifetimes. We do not embed Stripe tracking scripts in the portal.

Portal local-storage keyPurpose and retention
control:google-ads-consent:v2Remembers your allow/reject choice, disclosure version and decision time. No automatic browser expiry; retained until replaced or site data is cleared. A changed disclosure version prompts a new choice.
control:google-ads-click:v2Only after opt-in: holds the ad click identifier and withdrawal token pending authenticated transfer to our backend. Removed after successful transfer or rejection; identifiers older than 90 days are rejected and removed when processed on a later signed-in visit.
control:google-ads-attached:v2, control:google-ads-withdraw:v2Withdrawal token and pending withdrawal choice, so measurement can be withdrawn even before sign-in. The pending marker is removed after successful withdrawal. Otherwise these values persist until processing succeeds or you clear site data.

No Google advertising cookies or Google tracking script are loaded by the portal. When an ad click identifier is present in a landing URL, it remains in memory until you choose; it is not persisted or reported without permission. You can allow, reject or withdraw measurement through Advertising choices in the footer. Rejecting does not affect licensing. The public website has its own cookie and storage notice; its choice is separate.

Your choices and rights

You may request access, correction, deletion, portability or restriction of your personal data, and object to processing based on legitimate interests. Where processing relies on consent you may withdraw it without affecting earlier lawful processing. Contact the operator above. You may complain to the Belgian Data Protection Authority at dataprotectionauthority.be, or your local supervisory authority. Supplying identity and licensing data is necessary for an account; without it we cannot provide authenticated services. We do not use this data for automated decisions producing legal or similarly significant effects.

Changes

Shared documents and each product addendum have independent versions. We show the affected documents before a new acceptance and retain the previous versions. Adding another product does not change what an existing product user has accepted.

Privacy update notices

For material privacy changes, we use your verified account email to inform affected existing users. A shared-service change may affect every account; a product-specific change is addressed only to users of that product. This is a service communication to meet transparency obligations, not marketing or a request for blanket consent.

We keep the campaign identifier, exact document versions and hashes, the notice supplied, recipient account and email, queue and send-attempt timestamps, Azure operation identifier and delivery status while the account exists. These records prevent duplicate notices and show what was communicated. Account deletion removes them. Azure status means submission or sending, not proof that you received or read the message. We do not add open or click tracking, and a notification is never recorded as your acceptance of terms or consent.

Online withdrawal requests

The public withdrawal form records your name, confirmation email, product, purchase details, exact withdrawal statement, request identifier and server submission time. We use these to receive and handle your withdrawal, identify the purchase, send its acknowledgement and process any cancellation or refund due. This performs the contract and meets consumer-law obligations; it is not marketing or optional measurement consent.

The private licensing database also records processing status, completion notes/reference numbers and email operation identifiers, attempt timestamps and status. The operator receives a generic alert without customer details. Pending requests are kept until handled; completed requests are deleted 90 days after completion. They remain independent of account deletion so erasure cannot lose a withdrawal or refund request. Stripe retains its own required financial records. We do not automatically cancel subscriptions, issue refunds, delete accounts or change other products merely from an unverified form submission.

Sign-in profile and complete erasure

The portal's Delete account action deletes our licensing account and local identity links, revokes its keys and connections, and queues hosted Drawing-file erasure. It signs you out of the portal. It does not delete your separate Clerk sign-in profile or automatically cancel a Stripe subscription. To request erasure of the sign-in profile and other personal data, email the operator above. We verify your identity, process the request with the relevant providers and explain any records that must lawfully remain. We normally respond within one month; any lawful extension is explained within that period.

Withdrawal-form abuse protection

To keep the public withdrawal form and email service available, we retain hourly/daily counters keyed by hashes of the supplied email address and caller network address. These pseudonymous counters are used only for abuse prevention (our legitimate interest), not advertising, and are purged using a 14-day cutoff after their periods. A limit does not affect your withdrawal right: you can always send an unequivocal statement by email. Separate private email-delivery diagnostics contain the recipient address, message identifier, delivery/bounce/suppression status and timestamps, retained for 30 days even if the licensing account is deleted in that period. We use them for our legitimate interests in reliable service communications and investigating failures. They contain no drawing contents or open/click tracking. Sending success is not proof of inbox delivery.

Drawing MCP Server — End User Licence Agreement

Version 2026-10-25.2

This product agreement covers Drawing MCP Server's local software and hosted drawing service. Shared account and billing rules are in the platform terms. Its privacy addendum explains local and hosted data processing.

1. Who you are contracting with

Drawing MCP Server is supplied by Dmytro Vakulenko, a freelance software developer established in Belgium, at Franklin Rooseveltlaan 19, Ghent, Belgium. Enterprise and VAT number BE 1018.539.293. Telephone +32 492 92 86 95. Email dmytro.vakulenko.mail@gmail.com — write there about anything in this agreement, including a complaint, and we will reply to the address you write from.

In this agreement "we" and "us" mean that person, and "you" means the individual or organisation accepting it. Where a term applies only if you are a consumer — someone acting outside their trade, business or profession — it says so.

2. What is supplied

Drawing MCP Server lets an MCP client extract data from, edit and view supported CAD drawings. It includes the local executable we distribute and our hosted HTTPS service. It does not require AutoCAD. Autodesk, AutoCAD and DWG-related trademarks belong to their respective owners; this product is not endorsed by Autodesk.

3. Local software and hosted access

This agreement covers software obtained from our official distribution and access to our hosted endpoint. It does not grant redistribution or embedding rights to the underlying DWH SDK. Use only drawings you are entitled to process and share. You retain your drawing rights; we process them only to provide the requested service, storage and explicitly requested support.

4. Grant and plans

We grant you a non-exclusive, non-transferable licence to run the supplied executable on computers you control and use the hosted service through your own account. Your plan defines separate local and hosted allowances, cloud capacity and retention; current purchase details are shown at checkout. These are account/product entitlements, not rights to other products. Local files do not use cloud storage. The software remains ours and our licensors'.

5. What you may not do — and what you may, whatever this says

You may not:

  • redistribute, sell, rent, sublicense or publish the Software;
  • remove or alter its copyright or licence notices;
  • circumvent, disable or falsify the licence check, the device registration or the usage metering, or pass your credentials to other people so that they use the Software on your plan;
  • present a modified build as Drawing MCP Server, or distribute a build whose digest is not in a manifest we published.

Rights this agreement does not take away. Nothing above restricts what Articles 5 and 6 of Directive 2009/24/EC give you as a lawful acquirer, and any term here that would is void to that extent. In particular you may make a back-up copy where that is necessary to use the Software; you may observe, study and test how it works while running it; and you may decompile it so far as that is indispensable to make independently created software interoperate with it. If interoperability is what you are after, ask us first — we would rather document the interface than have you take it apart.

6. Open source components

The Software includes third-party components under their own open source licences. Those licences govern those components, and where one grants you more than this agreement does, it wins. Ask us at dmytro.vakulenko.mail@gmail.com for the current list of components and their notices.

7. Conformity — what the Software has to do

We supply the Software in conformity with this agreement and with what you can reasonably expect of it. If it does not conform, you are entitled to have it brought into conformity, and where that fails, is disproportionate, is unduly delayed, or we do not do it, to a proportionate price reduction or to end the contract and be refunded. Once you pay for a plan, Directive (EU) 2019/770 gives you these rights by law and you benefit from the legal guarantee of conformity; while the alpha is free we commit to them anyway. Nothing in this agreement reduces them.

What you can reasonably expect is shaped by what we say plainly: Drawing MCP Server is developing software, sold as such. It changes often, and an assistant can request a change you did not intend. Review what it does before you rely on it, and keep your drawings under version control or backup — the same care you would take with a colleague's edit.

8. Updates

For as long as you are entitled to the Software, we will supply the updates — including security updates — needed to keep it in conformity, and tell you about them. If you choose not to install an update we have made available and told you about, we are not responsible for a lack of conformity that the update alone would have fixed.

9. Withdrawal

You can submit a withdrawal online using Withdraw from a purchase. Enter or confirm your name, purchase details and confirmation email, review the statement and select Confirm withdrawal. No sign-in, reason or new agreement is required. We record the submission time and send a receipt containing your statement and that time. You may also withdraw by an unequivocal statement to the contact email above. Withdrawal concerns that purchase and any refund due; it is separate from deleting your account or cancelling future renewals.

The 14-day consumer withdrawal right, instructions and optional model form in the shared Terms of Service apply to paid subscriptions. Starting access or accepting this agreement or a privacy notice does not waive that right.

10. Drawings, rendering and storage

Extraction and rendering have documented format and geometry limits. Unsupported entities, fonts or surfaces may be missing; inspect coverage diagnostics and verify results before relying on them. Edits are session-local unless an explicitly supported save operation says otherwise. Hosted file retention follows the policy selected at upload and your signed plan entitlement. This service is not a backup: retain your originals. Deleting a hosted file cannot be undone. The Drawing privacy addendum describes storage, cleanup, the AI host boundary and optional support reports.

11. Our liability

We are fully liable for death or personal injury caused by our negligence, for damage caused intentionally or by gross negligence, and for anything else the law does not permit us to limit — including our obligations under § 7.

Where we fail to perform one of the main obligations of this agreement, our liability is not limited. For anything else, and except where we acted intentionally or with gross negligence, our liability is limited to the loss that was foreseeable and typical for a contract of this kind. Nothing here limits liability we cannot lawfully limit under the law of your country of residence.

12. Term and ending it

This licence runs while your account does. You may stop using the Software and delete it at any time. We may end this licence if you materially breach it and do not put the breach right within 14 days of us asking — for a breach of § 5 that is causing ongoing harm, we may suspend access immediately and tell you why. When the licence ends you must stop using the Software and remove it; § 4 (ownership), and §§ 11 and 13, survive.

13. Law and disputes

Belgian law applies. If you are a consumer, this does not deprive you of the mandatory protection of the country where you habitually reside. You may bring proceedings in that country or in Belgium; we may only sue you in the courts of your country of residence.

First contact us about a complaint. A consumer may approach the Belgian federal Consumer Mediation Service (Service de Médiation pour le Consommateur / Consumentenombudsdienst), North Gate II, Boulevard du Roi Albert II 8 bte 1, 1000 Brussels — consumerombudsman.be, French-language contact +32 2 702 52 20, contact@mediationconsommateur.be. We are not obliged to participate in an out-of-court settlement procedure and do not commit in advance to doing so.

14. Changes

We may update this agreement as the product matures. A change to what you agreed to asks you to accept the new version before you can create a new key or connect a new device; connections you already have keep working. The version you accepted, and when, is recorded against your account.

We may also change the Software itself, or what a plan includes, where there is a valid reason — a new technical environment, a security fix, more users to serve. It will not cost you extra, and we will tell you clearly and in advance. If a change makes the Software materially worse for you than only slightly, you may end this agreement free of charge within 30 days of being told or of the change taking effect, whichever is later, and we will refund the unused part of anything you paid — unless we keep the unmodified version available to you at no extra cost.

Drawing MCP Server — Privacy Addendum

Version 2026-10-25.3. Read with the shared privacy notice.

Local and hosted processing

Local stdio reads and processes drawings on your computer. Routine licensing sends credentials, device/build identifiers and usage counts, not drawing contents or local paths. Hosted HTTPS processes drawings on our Azure service: uploading, importing a URL or opening a stored file sends the drawing to that service. Your AI host receives requested query results, images and 3D geometry and controls onward processing under its own privacy terms. An attachment to a chat is not automatically uploaded to our server.

Stored files

Original DWG files are stored in a private Azure Blob container in a separate Drawing storage account in West Europe. Account-scoped metadata contains filename, size, random file ID, creation and last-activity timestamps, retention policy, expiry and upload/deletion state. URLs used for import, credentials and drawing contents are not retained in this metadata. Storage uses encryption at rest, HTTPS in transit, and service managed identity. Files are not publicly accessible.

Session memory and edits

Parsed drawings, edits and render scenes are held in server memory independently per MCP session. Temporary decoding copies are held in private container directories. Closing a session, inactivity cleanup or restarting the server removes session state; in-memory edits are not saved back to the stored source. Images and 3D geometry are sent to the viewer for display. Browser orbiting and zooming may use already-downloaded geometry without a server request.

Retention

New temporary uploads expire after 24 hours without server-side drawing activity. Existing temporary files keep their recorded deadline until drawing use or an explicit retention change renews it under the 24-hour policy. Opening, querying, rendering and editing renew that deadline; listing files and local 3D camera movement do not. The file manager displays expiry and lets you change a stored file's retention policy. Fixed periods are measured from the original upload and remain within your current plan's calendar-month maximum. Listing files and changing retention do not update the last-activity time. A selected deadline that has already elapsed is rejected. A downgrade does not shorten an existing file's original deadline, but may prevent further uploads above the new allowance. There is no permanent storage option.

Deletion

You can delete a stored drawing immediately in the file manager or through the deletion tool. Access is revoked and the service deletes the source, metadata and open cached copies; there is no product recovery or backup for deleted drawings. Expired files become inaccessible immediately; physical deletion is retried by cleanup and may be delayed by downtime, storage failures or a backlog. Revoking a connection or signing out does not delete stored drawings. Deleting the licensing account queues deletion of that account's hosted drawings. A worker scheduled every five minutes revokes file access and removes the source and metadata, retrying failures; session caches are then cleared by the Drawing server's cleanup. The erasure job repeats for seven days to catch uploads already in flight before credentials were revoked. You may also delete drawings directly before closing the account.

Issue reports

Only after your approval, the issue-reporting tool sends the report, supplied environment details and approved attachments to the product's separate Azure feedback service. A reporter address is included only when you explicitly opt into contact. Drawings, local files and logs are never attached automatically.

Report contents, approved attachments, contact preferences and any opted-in address are kept in a private Azure Blob container for 90 days from submission. Access requires the operator's authenticated Azure account; no public download link or access token is emailed. Daily cleanup and an Azure lifecycle rule delete expired reports; physical deletion can be delayed by downtime or service failure and is retried. Legacy emails migrated to this store retain their original submission-based deadline. Account deletion does not by itself find reports, because reporting is independent of licensing and reports can be anonymous. Contact us with the report ID to request earlier deletion.

The maintainer receives only a generic email notification with a fixed Azure Portal link. It contains no report title, body, report ID, attachments or reporter email. The feedback Table database holds IDs, payload hashes, delivery status and abuse counters, not report contents. Deduplication metadata is cleaned after one year and rate-limit counters after 14 days.

Purpose and choices

Hosted drawing processing and storage supply the service you request. Security and quota controls protect it from abuse. Support processing responds to the issue you choose to report; optional contact permission is separate. Do not upload drawings you are not entitled to share, including confidential or personal data without the necessary authority. The shared privacy notice supplies operator details, provider transfers and how to exercise your privacy rights.