Draft dated 6 September 2026. Not approved or in effect. This text describes the implemented Intro cloud website. Before publication, complete the marked details, define retention periods and verify the basis for each processing purpose. Belarus is the working market assumption.
1. Who handles the data
The operator is ООО «Интроклауд» (Introcloud LLC), 37 Klenovaya Street, Grodno, Republic of Belarus. Website and data enquiries: info@intro.by, +375 33 656-95-69. UNP (taxpayer registration number): 123456789. The official address for legally significant requests and responsible contact must be confirmed before approval. The English version describes the same processes.
2. Website enquiries
Visitors provide a name, email and description of their request so the company can review it and respond. A phone number, company name and selected service are optional. The language, submission time and consent record, including the accepted policy text and version, are stored. The policy can be read before submission. The form requires a separate consent choice and does not accept an outdated version.
Campaign source tags, the first page path and the referring page address without query parameters may accompany the request to explain its context. Do not include passwords, payment details or unnecessary information about other people. Not submitting a request does not prevent browsing. Visitor consent is the proposed basis for enquiries; its duration and retention periods for completed requests and consent records must be approved.
3. Accounts and support
The account stores a name, email, language, organization membership and access permissions. An authorized employee creates accounts; there is no open self-registration. These details support sign-in and access to the organization's requests, projects and licenses.
Support requests include a subject, messages, optional attachments, author, organization, status and action times. Organization members can access its requests; staff notes remain internal. Consider your organization's membership before attaching a file. Determine the basis for processing client representatives' data, account closure arrangements and retention after the business relationship ends from the actual contracts.
4. Licensing and account security
License checks process product, plan, term, organization and activated installation details. Connected software supplies an installation identifier and permitted binding parameters, such as a domain; the exact fields depend on the product. Access is restricted to the license owner and authorized staff.
Passwords are stored as verification hashes. Optional two-factor protection stores a protected authenticator secret and hashed recovery codes. Sign-ins, sessions and administrative changes support account protection and incident investigation. Application and server logs may contain IP addresses, times, request paths and error information. Define the basis and separate retention periods for licenses, sessions, audit records and server logs before launch.
5. Notifications and service providers
Email supports enquiry confirmations, invitations and account recovery. The configured sender is no_reply@initium.by through mail.initium.by, with replies addressed to info@intro.by. These are service messages; the enquiry form does not request permission for advertising.
Optional Telegram notifications use @INTRO_BY_Bot after confirmed account linking. The website stores the chat identifier and connection state, and the user can disconnect it in their profile. Telegram processes data under its own terms. Recipients and transfer arrangements must be documented before enabling this channel. Browsing does not require opening Telegram.
Before publication, identify the legal entities providing hosting, email and backup storage, their roles, processing locations, data received, contractual arrangements and any cross-border transfers. A mail server hostname does not establish these facts. The production hosting environment has not yet been selected.
6. Cookies and optional analytics
The ci_session cookie connects requests to a session for sign-in, form protection and submission feedback. The current session duration setting is two hours; activity and session renewal can extend access. Blocking necessary cookies may prevent sign-in and form functions.
Analytics is currently disabled. Its separate allow or decline choice is stored in the browser for 180 days and can be changed. Declining leaves the website available. When enabled, analytics counts approved page views, successful form submissions and contact clicks. Events omit message content, email, URLs with query parameters and visitor identifiers. The configured retention for aggregates is 90 days. This operation must be reconciled with the published policy before activation.
7. Retention, access and ending processing
Staff access is limited by work roles; account attachments require authorization. Backups support recovery and may contain records from the backup date. Approve deletion rules for each purpose, backup rotation, reapplying deletions after recovery and responsibility for those tasks. A universal automatic personal-data deletion period is not currently implemented.
Use the contacts above to request information, corrections, an end to processing or withdrawal of consent. The company clarifies the request and checks authority where needed. Do not send an identity document without a justified need. Consequences depend on the purpose: stopping use of contact details may prevent a reply, and account closure ends access to the portal. Data subject to applicable retention obligations must be considered separately. Formal submission requirements and response periods need to be aligned with applicable rules.
8. Versions and changes
Add an approval and effective date and remove editorial notes before publication. Revised text is published at the same address; the accepted version remains recorded with each enquiry. A new processing purpose or recipient requires assessment and updated information before that use begins.