Alin-Gabriel Busescu

Privacy policy

This policy explains personal information associated with browsing the Alin-Gabriel Busescu website and contacting the business. It distinguishes information used to display the website, a message you choose to send, and records that may arise from later dealings with the company. The fields and notices presented for a particular interaction should be read together with this policy.

ALIN-GABRIEL BUSESCU, at Strada Televiziunii 32, 062363 București, Romania, is identified as the publisher of this portfolio. Contact [email protected] about the handling of a project conversation or a privacy question. This policy distinguishes browser activity from a message you choose to send through your own email provider. It covers the portfolio's general contact route; a commissioned project may require additional, specific instructions for supplied documents and personal information. A new project does not automatically authorise unrestricted processing of all material within a manuscript, drawing, storyboard or brief.

The hosting service must process connection details to deliver a page or image, such as the requested resource, network address and request time. Error and security records may also include browser or connection information. Cloudflare may provide network protection, Web Analytics, email-address protection and network error reporting; these processes are distinct from the enquiry form. The page loads its own font and example artwork locally. It has no embedded social feed, externally hosted video player, advertising pixel authored in the page, payment widget or account sign-in.

You can supply a name, reply email, optional company or project label, selected project interest and message. The selected interest may be prefilled from a link so that a project enquiry retains its context. JavaScript uses these fields to compose a draft within your current browser page. The draft is not submitted to a website database or saved in local storage by this form. Refreshing or leaving the page may discard it; browser autofill and your device's own recovery features have separate behaviour that you control through browser settings.

Preparing a draft shows its text for review. The optional email link passes the recipient, subject and message to an email application configured on your device. You decide whether to send from that application. Opening a draft alone is not delivery, and this website cannot verify that a mailbox received it. Your email provider processes messages under its own privacy terms. If a conversation is received, the recipient can use the information needed to understand and answer the project request; do not include material you cannot authorise that recipient to review.

A first storyboard conversation can use a nonconfidential outline: subject, audience, approximate duration and intended format. Avoid attaching unreleased scripts, personal case histories or customer recordings before confirming who may review them. If a project proceeds, agree permitted use and retention of reference media and production files separately. Enquiry information may be needed to respond, define a requested service, negotiate an agreement or satisfy legal recordkeeping duties. The appropriate legal basis and access should follow those real purposes, with additional safeguards for information that needs special protection.

A script can contain personal stories even when a film is only an idea. Initial storyboard enquiries should avoid identifying customers, employees, children or research participants. Use a neutral synopsis where possible. Permission to tell a story and permission to use a person’s voice, likeness or recording are separate questions to settle before production. This form accepts text only and has no recording or media upload. If a later board requires a real case study, establish the authority and review process before exchanging its source material.

Storyboard projects can produce many script versions, frame exports and review comments. There is no repository for those files on this portfolio. If a project starts, agree how working versions, approvals and final boards will be retained and when unnecessary copies can be removed. Instructions and records establishing a licence or a dispute may need different retention from unused thumbnails. The site does not promise a fixed deletion interval for every future engagement; ask about the relevant file category and any legal obligations before supplying sensitive content.

The hosting network delivers the portfolio, and your chosen email provider handles a message you send. An animator, narrator or editor is not automatically appointed by an enquiry to this storyboard practice. If other production participants need access to a script or a board, identify their role and the authorised material in the project arrangement. A collaboration should not turn a private outline into a public portfolio sample without the appropriate permission. A legal requirement to disclose information would be assessed under its actual terms and applicable law.

A board may be discussed across countries, and internet delivery can use infrastructure outside Romania. That does not establish that every participant may receive all source recordings or private information. Before a cross-border project shares personal material, determine the recipients, purpose and safeguards appropriate to the transfer. The examples currently served here use invented subjects and local static panels. Browsing or preparing a draft does not require a production account, the identity of a real narrator or access to a client’s media library.

A short project summary is safer for an initial conversation than a complete confidential campaign script. Verify email recipients and agree a suitable file route before sending unreleased material. Passwords and production-system access do not belong in the form. Security measures reduce risk but cannot guarantee that every email, device or provider will be free of error. If you discover a misdirected script or suspect unauthorised access, identify the affected version and relevant conversation without spreading further copies of the material.

A request about personal information should indicate the storyboard conversation or project context concerned. Rights under applicable law can include access, correction, deletion, restriction, objection, portability and withdrawal of consent where consent is the relevant basis. Their conditions and exceptions depend on the actual handling. Do not attach an entire script merely to prove that a conversation exists. Reasonable verification should protect the information rather than collect unnecessary new records. You can also raise an unresolved concern with a competent data protection authority.

This professional portfolio does not invite children to create accounts or submit media. A client considering an explainer for children should describe the audience in general terms. Do not send children’s names, contact details, images or recordings through the initial enquiry route. A real project involving identifiable participants needs appropriate authority and additional safeguards before those materials are reviewed. A parent or guardian can contact the publisher about a specific disclosure, giving enough context to investigate without unnecessarily repeating the child’s information.

The current enquiry interaction stays in the page until you elect to open an email application. Adding hosted uploads, a production review portal or a mailing list would change that interaction and require a suitable notice at the point of collection. No such feature is offered by the static storyboard examples. Check the date when retaining a copy of this policy. Any later policy change must be considered alongside the purposes and permissions under which an earlier script or other personal material was originally supplied.

The website presents business information and enquiries rather than an experience designed for children. A parent or guardian concerned that a child has supplied personal information can contact the operator, describe the relevant interaction and ask about appropriate action. An adult making an enquiry should avoid including unnecessary information about a child or another person. Where a particular service legitimately requires such information, the purpose, authority and appropriate channel should be clarified for that situation instead of placing the details in a general contact message.

The publication date identifies the version currently displayed. Changes to website features or business handling may require revisions or an additional notice at the point of collection. A later policy statement does not by itself authorise a materially different use of information already received where further notice, a legal basis or consent is required. Keep a copy relevant to your interaction if you need one. Questions about this policy, a particular data category or a request that remains unresolved can be raised through the Contact page, without limiting any available complaint to a supervisory authority.

Related information: Professional details · Contact · Privacy policy · Terms of use.