1. Purpose of this Document
1.1. The version 1.0 documents — the License Agreement, the Offer, the Personal Data Processing Policy and their appendices — describe BF Designer with an account confirmed by a phone number and with optional linking of Telegram. Until the release of the Software version with such registration, the Software operates in closed early access, and the departures listed below apply to it. In all other respects the version 1.0 documents apply in full; in case of conflict, this appendix applies during the transitional period.
1.2. This appendix is displayed together with the License Agreement and accepted by the same checkbox (License Agreement, clauses 1.2 and 1.5).
2. Account and Key
2.1. During the transitional period the User's account is the key issued to the User. There is no registration by phone number, no login by confirmation code, no automatic starter license and no starter tokens. The Telegram bot @bfdesigner_bot (the "Bot") is closed to users: it does not register users, issue keys, accept requests or perform generations; linking Telegram to an account is unavailable.
2.2. The Licensor issues the key manually, free of charge, at its own discretion, with a stated validity period, and passes it to the User directly; the User enters the key in the Software. Trial access, where granted, takes the form of such a key with a limited term; the starter license rules (License Agreement, Section 5) on its automatic issue and one-time nature do not apply.
2.3. The two-device limit, device unlinking, key verification and restricted mode apply as described in the License Agreement.
3. Age and Payment
3.1. Only persons aged 18 or over may use the Software; age is confirmed by the checkbox on first launch (License Agreement, clause 1.6).
3.2. Sales of subscriptions and tokens are not open, and payments are not accepted. The Offer applies only to free use of the AI services within the tokens credited by the Licensor. The sections of the Offer on payment, auto-renewal and refunds, the "Pricing" appendix, the "Auto-Renewal Consent" and the "Refunds and Delivery Terms" take effect when sales open, which the Licensor will announce in the Software.
4. Support and Notifications
4.1. Support requests are accepted through the Software and at support@blenderfamily.com; personal data matters and complaints — at legal@blenderfamily.com. In a request the User states an e-mail for the reply; it is used only to answer that request. The Bot does not accept requests.
4.2. Notifications are delivered in the Software. Service e-mails are not sent; no e-mail is collected in the Software settings; no mailings are made.
5. Personal Data
5.1. Wherever the version 1.0 documents refer to an account by phone number, during the transitional period this is read as the key. The rows of the Policy on registration and login by number, confirmation codes, the login log, starter license protection, the optional e-mail in the Software, linking Telegram, and generations and conversations in the Bot, as well as the clauses of the Policy on the number confirmation service (clause 8.6) and on Telegram (clause 8.3), do not apply. The account is described by the row "Server: licenses and devices"; requests — by the row "Support, errors, suggestions" without a Telegram ID.
5.2. During the transitional period cross-border transfer takes place only for cloud generation (Policy, clauses 8.2 and 9.1, first case). No transfer to Telegram takes place: the Bot is closed, and requests are not forwarded to Telegram.
5.3. Telemetry is accepted by the server only with the User's consent (the "Consent to Optional Processing of Personal Data" document); without consent, crash reports are anonymized (Policy, clause 5.5).
5.4. Deletion of data, cancellation of a key and withdrawal of consents are performed on request to support@blenderfamily.com or legal@blenderfamily.com stating the key; the Licensor performs them manually within the time limits set by the Policy.
6. Transition to the New Version
6.1. Upon release of the version with registration by phone number, the User registers an account by number and enters their key in it — whether current or expired; the key, its term and the token Balance are transferred to the new account as they are. The transfer is performed once: after it the key is bound to the number, the previous account is closed, and a notification to that effect is shown on the previous devices. Until the transfer, the key continues to work under the rules of this appendix.
6.2. This appendix ceases to apply from the release date of such version stated in the Licensor's announcement. The version 1.0 documents in force on that date apply without departures.