LivingRegister application privacy notice

Controller and contact

ColivingLiguria S.r.l., registered at Strada Chiappella 21, 17014 Cairo Montenotte (SV), Italy, VAT and tax number 01939660096, controls your LivingRegister application data. You may contact colivingliguria@gmail.com or colivingliguria@pec.it with questions or rights requests, even without an account.

The request you choose

This notice covers the limited initial application flow in LivingRegister, separate from your basic account. You may request review of your own stay, contribution, professional role, study project, tutor programme, creator collaboration, founder or land project, preliminary visa-support information or advisory enquiry. The partner, founder and financial-advisory routes also permit an identified organisation-contact role for the enquiry you initiate; local-community enquiries have a separate limited reply purpose. Starting a request is not room reservation, programme approval, confirmation of company authority, protected access or a right to compensation.

The exploratory “Not sure yet” route, identified as UNKNOWN, stays account-only and has no application questionnaire. You may read public information and keep your basic account without an application or contract. Personal requests and organisation contacts must use their appropriate displayed role; an account is not proof of authority to bind another person or organisation.

Initial data and optional answers

We use the categories you select and only the initial fields relevant to their displayed role: the response language; requested dates and practical stay or workspace needs; relevant personal skills, study, working languages and your own portfolio; a requested contribution, programme, project or creator proposal. Organisation contacts provide their professional role and the organisation/project enquiry, rather than personal demographics. To save an application route, choose at least one category and acknowledge this application notice. General questionnaire answers may be left blank and saved as a draft; an incomplete request may need clarification before it can be assessed. A saved or submitted state does not certify completion of a specialised procedure or approval of a request. You may keep your basic account without starting an application.

Stay routes cover relevant availability, arrival, companions or pets and practical space needs; companions are described without identifying them. Volunteer and professional-role requests cover relevant contribution, skills and availability. Student requests cover the student’s own learning/project plan and relevant experience, not the promoting institution’s declarations. Tutor proposals cover the programme concept, season, maturity and aggregate intended audience/capacity, not actual child enrolment or contract economics. Creator proposals cover applicant-controlled channels, own work, relevant aggregate audience context, content and deliverables, not follower or lead lists. Partner, founder and advisory enquiries are limited to the requested role/project discussion. Preliminary visa-support enquiries do not collect immigration documents or decide eligibility; local-community enquiries do not subscribe you to civic updates or grant protected access.

This initial application does not newly request a full residential address, date of birth, gender/self-description, citizenship, a general social-profile list, deposit declarations, contract acknowledgements or document uploads. A relevant personal portfolio or applicant-controlled creator channel is distinct from a general list of social profiles. Existing basic-account data and historical information keep their separate scope. Describe practical functional needs without diagnoses or other health information. All general questionnaire answers remain optional; a saved or submitted state is not a certificate that every declaration is true or a specialist review is complete.

Information retained from earlier communications or applications keeps its original source and purpose; showing it in your private area does not make it a new declaration or a new acknowledgement. You can review it and ask where it came from. Information received from other people or public sources requires its own source information and applicable notice handling; your new checkbox does not replace that obligation. In general forms, describe other participants or team members by roles or counts, without unnecessary identifying details.

Do not enter identity-document numbers or scans, passwords, health information, bank evidence, private messages, children’s personal data or individual immigration files in these general forms. Use only roles, counts and non-identifying aggregate context for teams, companions or audiences. A visa, insurance or finance label does not activate a document service. Specialised health/immigration documents, promoting-entity declarations, final creator activation and contracts require their own available workflow, information and safeguards.

Purposes and legal bases

For your own personal request, we use information objectively needed to receive, retain, let you correct and assess the relationship or service you actually ask to explore. GDPR Article 6(1)(b) applies only where these are steps requested by you toward your own contemplated contract or are necessary to your requested contractual service. A track label, useful background information or an organisation’s possible contract does not by itself establish that basis. The initial field scope is limited to the relevant request; reading this notice is not consent or blanket permission.

For an organisation contact using the partner, founder or financial-advisory route, the separate basis is Article 6(1)(f): our legitimate interest in privately replying to the professional enquiry that contact initiates and considering the requested next discussion. The contact and project context are limited to that purpose, without claiming the person is party to the organisation’s contract. Local-community enquiries use the interest in answering the individual’s specific event, information or reviewed-access request. These purposes do not include staff-list acquisition, unrelated marketing, political-affiliation inference, automated admission or publication. You may object and contact us without an account.

Limited technical information and operation receipts support access security, abuse prevention, data integrity and reconciliation of the particular operation, under Article 6(1)(f). These records do not authorise another use of the application answers. An acknowledgement records the information shown and reading; it is neither a legal-basis substitute nor a contract or Attachment D signature.

This initial application flow does not request new optional marketing or research consent. An existing optional choice remains separate: you may withdraw it by contacting us without an account and identifying the purpose you want to withdraw. Withdrawal does not affect the lawfulness of earlier processing based on that consent or remove basic-account access. A new optional use requires its own information and separate choice. Applying as a marketing collaborator is a requested role, not consent to receive promotional messages.

Recipients and services

Authorised operators access the information pertinent to handling your request, protecting the service or responding to a rights request. Cloudflare provides the private account and database infrastructure and processes personal register content on our behalf under the DPA incorporated into its service terms, including the Free plan. Register data and operation history are private. Authorised operators may also handle relevant data in the private local register and controlled local recovery copies, subject to the retention criteria below.

We use colivingliguria@gmail.com on consumer Gmail for operational messages and correspondence you send to that contact. Access messages contain the recipient address, code, expiry and first-name greeting, with transmission metadata, rather than the complete profile or application documents. Application or rights correspondence contains the information exchanged for that case. Google, generally Google Ireland Limited for EEA users, provides its consumer service under its own privacy terms and regional service arrangements. ColivingLiguria chooses each message’s recipient, purpose and content; Gmail does not manage the register or decide applications.

Applications, private correspondence and contact details are used for authorised private handling and recovery; they are not published through this flow. Where an additional service is used for these purposes, the applicable information must identify its provider, role, transfers and retention before that use starts.

Processing outside the EEA

Provider processing may occur outside the EEA, including the United States. Cloudflare’s DPA, sections 6.2–6.4 addresses covered Data Privacy Framework transfers and applicable standard contractual clauses; the controller-to-processor module applies to our register where required. Google describes its own adequacy, DPF and clause arrangements, rather than a consumer DPA signed with us. Ask the controller for information or relevant safeguards. A European database location does not exclude every transfer.

Retention and case closure

Our retention rule is to keep a saved draft or open application for the handling you request and to review its data when you withdraw it or its review ends without a separate relationship. You may withdraw a request through the contacts above. A register operator records the request or review outcome, identifies the relevant data and copies and arranges removal of information no longer needed. Any distinct legal duty or live dispute requires a recorded purpose and limited scope. Keeping your account open does not justify retaining every finished application indefinitely.

The review is handled manually for the particular person, application route and purpose. A separate relationship, concrete legal duty, live dispute or strictly limited recovery need requires its own relevant data subset and a next review or action determined by that reason. A fiscal or accommodation period does not automatically apply to a preliminary enquiry. Notice acknowledgements and operation records are kept only for their limited accountability or reconciliation purpose; they must not become an additional archive of unnecessary application answers.

The review covers the current private records, operation history, local register and histories, case correspondence and relevant recovery copies. Provider-managed recovery can retain an earlier database state for its applicable recovery window. Information removed from ordinary use must be dealt with in the relevant copies and excluded from restored data before those data are made available again. Closing account access, withdrawing an application and erasing data are distinct actions. We communicate the outcome of a removal request separately from acknowledging that request. You may contact us without an account to ask for a data review or exercise your rights.

Rights

You may request access, correction, erasure, restriction and applicable portability, and object to legitimate-interest processing. You may complain to the Italian Garante or another competent supervisory authority. We respond without undue delay and within one month. If the complexity or number of requests justifies an extension of up to two additional months, we explain the extension and its reasons within the first month. Do not send sensitive documents with your first message.

Decisions and disclosure

Applications and declarations are subject to review. Saving a category or answer does not automatically decide admission, employment, housing, visa eligibility or a contractual relationship. The general questionnaire is not an application to a public authority and does not produce a visa or public decision. Ordinary service checks and data sorting are distinct from an individual decision.

The information you submit remains private to authorised handling. Aggregated public statistics or optional named publication require their separate applicable scope and safeguards; no raw answer, contact detail or document becomes public merely because it is useful for administration.

Version

This notice is separate from the basic-account notice and Attachment D. Earlier acknowledgements keep the information, version and purpose shown at the time. When the relevant application information changes, we make the current text available before collecting new application data. An acknowledgement of the account notice or Attachment D does not replace the information for a different application purpose.