Account privacy

What data the service uses

• Account: the verified Yandex user ID, display name or login, primary email address, internal support ID and registration date. Yandex may return other basic profile fields under the permission you grant; AIDrafting extracts these account fields. We do not receive your Yandex password.
• Activation: computer name, a derived device identifier, activation/release status, license validity, authorization-session records and security events. Update reports can include the installed version, update result and diagnostic reason code.
• Orders: order and provider-payment IDs, amount, currency, payment and refund status, access dates, receipt references, and your refund/support messages. Payment card details are entered on YooKassa's payment page; this account service does not store full card numbers or CVC codes.
• Service messages and operation: recipient address, message type, delivery attempts and status; technical request data such as IP address and time may be processed by the web infrastructure for security and troubleshooting.

Why these data are needed

The service uses these data to identify your account, fulfil and verify orders, activate up to two computers, refresh access, deliver updates, issue receipts, process refunds and support requests, and prevent misuse. Necessary messages cover account creation, confirmed payment, confirmed refund and receipt availability. This account service does not use those messages as a marketing subscription.

Yandex asks you to authorize basic-profile and email access when you sign in. Creating an account does not charge you or activate paid access. If required account or device information is unavailable, sign-in or activation may not be possible.

Providers and storage

The Russian account service and its databases are hosted in Yandex Cloud in Russia. Yandex ID handles sign-in, YooKassa processes payments and refunds, and Yandex Postbox sends service emails. The seller uses My Tax for receipts. Data needed for each operation are handled by the corresponding provider and the people responsible for running the service or resolving your request. These providers also apply their own privacy terms.

AYDrafting administers the service from Canada; authorized administrators can access account and order data from Canada for operation and support. Hosting the database in Russia does not mean that all administrative access takes place only in Russia.

Access to account and order data is separated from ordinary customer access. Data needed for active accounts, license checks, payment reconciliation, receipts and claims are retained for those purposes and applicable legal requirements. Account deletion is not automatic when an annual period ends. Requests to access, correct or delete data are reviewed through support; transaction records that must be retained cannot always be erased immediately.

Cookies and your Revit model

The account service uses cookies for your authenticated session, protection of forms and language preference. Signing out ends the local AIDrafting session; it does not sign you out of Yandex everywhere. Blocking necessary cookies can prevent sign-in or form submission.

Account activation does not upload your Revit project to this account service. When you ask an AI application to inspect or edit the model, the plugin's command results are sent to that application according to the tools you use. Check your AI provider's privacy rules before sharing model data. Do not attach confidential projects to a support request unless you have agreed that separately.

Optional browser connections

When you enable browser access on your computer and authorize ChatGPT or Claude, the AIDrafting server relays tool requests and responses between that AI service and your selected computer. Depending on the tools you request, this can include project and view names, element identifiers and properties, images, code and operation results. This is additional processing through the AIDrafting server, separate from account activation. Your chosen AI provider also receives the requested results under its own privacy rules.

The service stores connection authorization records linking your account, computer and AI provider, along with authorization dates, expiry and revocation status. Tool payloads are relayed to perform the request; the browser connection tables do not store a copy of your model or chat history. Technical diagnostics record bounded outcome codes rather than tool request or result bodies. Expired authorization records are removed by the service's periodic cleanup.

You can revoke a browser connection on the browser connections page or switch off browser access on the Revit computer. This stops future access through that connection; it does not remove information already received by your AI provider. Use that provider's controls for its chat history and data settings. Connect only projects you are authorized to share with the chosen services.

Manage browser connections

When you authorize a shared AIDrafting connection through account.aydrafting.com, requests and results also pass through the shared service on Microsoft Azure before reaching this Russian account service on Yandex Cloud and your selected computer. Your chosen AI provider receives the results. This additional route does not transfer your purchase or merge your accounts; your Russian account and activation remain with customers.aydrafting.com.

The shared service stores an account-service reference, provider and computer authorization, connection status and expiry, and encrypted credentials for calling the authorized account service. These credentials allow renewal and revocation and are not your Yandex password. Revoke the connection or disable browser access to stop future authorized requests; data already received by the AI provider remains subject to its controls.

Data controller and contact

AIDrafting by ООО Координатор. Contact: aidimir95@yandex.com. Controller and seller details.

State your request and support ID. We may need to verify that the account belongs to you before releasing or changing its data. Do not send a password, full card details or identity documents in your first message. You can request information about processing, correction, deletion or restriction where applicable, and contact the competent authority to protect your rights.