METACONCollective decidement
Project service

Privacy policy

How we process the data of individuals, organization representatives and participants, who receives it, how long it is retained, and how you can exercise your rights.

Version 1.2 · Updated 15 November 2026

Website enquiry forms

The home page and project catalog forms collect your name, reply email address, question and selected topic; your organization and the expected participant count in the catalog form are optional. We use this information to respond to your enquiry and, if you wish, agree on a suitable project. Submitting a form does not constitute consent to receive marketing emails.

Enquiries are delivered to METACON email through FormSubmit. The completed form, the source page address, and technical data necessary for communication and protection against misuse are transmitted to this service. Submission is subject to the FormSubmit privacy policy. We do not store the contents of the form in your browser’s local storage.

Do not send passwords, banking login details or sensitive data about other people. For general service enquiries, we apply the legal bases for responding to enquiries described below and the retention period specified for custom project proposals. Contractual, accounting and dispute documents are subject to the relevant periods set out in this policy.

For individual and organizational orders.

This policy explains data processing when using the METACON order form and customer dashboard and when administering collective decidement clusters and projects. It also applies to real personal data used in testing. Separate notices from payment and participation platforms supplement information about their processing.

Reading this policy does not constitute blanket consent to processing for all purposes. Where consent is required, we request it separately.

1. Who is responsible for your data

The following entity is responsible for processing data for orders, project administration, access security and direct communication:

Controller
OC Projektai, MB, legal entity code 306701107.
Address
Pylimo g. 61-7, LT-01137 Vilnius, Lithuania.

The organization is responsible for deciding whom to invite to a cluster and for the lawfulness of other people’s data it provides to us. Where we process participant data solely on its documented instructions, we act as a processor under a separate data processing agreement. For our own accounting, account security and legal requirements, we act as an independent controller. Participants in a particular cluster must be informed which organization is responsible for the processing that applies to them.

2. Data we may process

Data categoryExamples
Account and customer profilesFirst and last name, email address and its verification, personal profile, represented organizations and access roles. One account may be used for orders in a personal capacity and on behalf of an organization.
Order, payment and refundAn individual’s first and last name or an organization’s name, legal entity code, billing address, VAT number (where applicable), email address, order number, amount, payment and refund identifiers, statuses, invoice and the choice to receive a copy.
Order confirmationsThe version of the service terms and the time of acceptance, confirmation concerning the recruitment of participants, an individual’s request to start the service before the withdrawal period expires, and related correspondence where such a request is made.
Coordinator detailsFirst and last name, role (if provided), work email address, telephone number and organization.
Project dataSelected question, situational context, desired outcome, working language, planned number of participants, statuses, notifications and report.
Custom project proposal dataProposed question or title, problem context, desired outcome, intended participant group, preferred start time (if provided), confidentiality notes, review status, correspondence and agreed wording.
Invitation dataThe invitee’s email address and the status of sending, delivery and use of the invitation link. The total number of registrations is counted separately, without linking it to a specific invitation address.
Participation dataThe new or existing account status selected on the invitation page, acceptance of the short participation rules, platform account identifier, submitted ideas, evaluations, points, specialization weights and project activity.
De-identified activity summariesAggregate counts manually entered by the administrator: Project participants, participants who have submitted or evaluated an idea at least once, inactive participants, ideas and evaluations, without participant identifiers.
Recognition and consent dataThe number of participants selected by the Customer and the requested scope of disclosure, the consent link and response status, the participant’s choice, the date and scope of consent, and, where the participant agrees, the name or pseudonym they provide, their final position in this Project, points earned in this Project and contact information they provide for this purpose.
Technical and security dataLogin time, IP address, browser or device technical information, the status of one-time links, and security and error logs.
CommunicationContents of enquiries, support messages, complaints and replies.

We do not request or store banking login passwords, payment confirmation codes or full card authentication details in the METACON order form. Payments are processed by Montonio and the selected financial institution. We transmit the order, amount and payer contact details necessary to link the payment to the order; we receive payment identifiers, status and information relating to payment or refund.

The METACON management module does not automatically import participant registration email addresses, individual ideas or evaluations from omnicracy.net. The administrator manually enters only de-identified aggregate summaries and, upon receiving a Customer’s recognition request, the final position and points necessary for that request, together with an internal participant reference.

3. Why we process data and our legal bases

PurposeLegal basis
Accept an order, confirm payment, create a cluster and, once at least 8 participants have joined, a Project, and provide project management.For orders in your own name: entering into and performing a contract (GDPR Article 6(1)(b)). For an organization representative’s data: the legitimate interest in concluding and administering a contract with the organization they represent (GDPR Article 6(1)(f)).
Assess a Customer’s custom project proposal, request clarification, agree on the wording and, once approved, prepare the order.Steps prior to entering into a contract (GDPR Article 6(1)(b)) and/or, where an organization representative makes the enquiry, the legitimate interest in responding to a professional service enquiry (GDPR Article 6(1)(f)); the specific basis depends on the circumstances.
Issue and retain accounting documents and comply with legal obligations.Legal obligation (GDPR Article 6(1)(c)).
Send Customer-initiated invitations and administer participant access.Where we act as controller: the legitimate interest in administering a work-related invitation for a specific project and secure access (GDPR Article 6(1)(f)), taking account of the recipient’s expectations and rights. Where we act as processor, the organization determines the legal basis and we follow its documented instructions. Documented instructions are not, by themselves, a separate GDPR legal basis.
Ensure the security of accounts, tokens, payments and the system; investigate incidents and misuse.The legitimate interest in ensuring service security and protecting rights (GDPR Article 6(1)(f)).
Respond to enquiries, resolve disputes and substantiate performance of the contract.Performance of a contract, legal obligation, or the legitimate interest in establishing and defending claims.
Provide a consent link to a selected participant and, following separate consent, disclose to the Customer only the participant-approved name or pseudonym, final position in this Project, points earned in this Project or separately provided contact details, for acknowledgement or an award.Participant consent (GDPR Article 6(1)(a)). Consent applies to disclosure; calculation of the final result is carried out under a separate legal basis applicable to the service.
Send optional marketing information.Separate consent (GDPR Article 6(1)(a)). Order or access emails do not, by themselves, create a subscription. Consent may be withdrawn at any time.

Data marked as mandatory in a form is needed to administer an account, order, invoice or access. Without it, we cannot provide the relevant function. Optional fields may be left blank; consent to marketing or disclosure for acknowledgement is not a condition of ordering. Do not include unnecessary information about other people or sensitive information, such as health, political opinions or religion, in free-text fields.

Where we rely on legitimate interests, we assess the Provider’s needs, the data subject’s reasonable expectations and the potential impact on their rights. You may request information about that assessment or object.

4. Where we obtain data

We obtain data directly from the Customer and coordinator, from the list of invitees entered by the Customer, from participants when they register and take part in a project, from payment statuses provided by Montonio, and automatically from technical service logs.

By providing another person’s work email address, the Customer confirms that they have a lawful basis to use it for an invitation and undertakes to provide the necessary information to that person. The invitee is informed about the source of their data and its processing at the first contact. An invitation to a specific project is not consent to receive advertising.

We obtain custom project proposal data from the proposer and subsequent correspondence. We obtain the scope of a recognition request from the Customer, the final position and points from the results calculated for that Project on the platform, and the disclosure choice, name or pseudonym and contact details only from the participant. The administrator provides the individual consent link through a separately verified private channel, or records consent received through another verifiable channel and retains supporting evidence of its receipt. An invitation or registration email address is not automatically linked to a participant for this purpose and is not used on the basis of an assumption alone.

5. Who may receive data

Recipients receive only the data needed to perform their particular function:

  • Montonio and the financial institutions involved in the payment;
  • Interneto vizija, the website and database hosting provider, and the providers of the backup and participation platform infrastructure used;
  • email and messaging infrastructure providers, including Google Workspace for METACON email correspondence;
  • authorized persons providing technical maintenance of the omnicracy.net platform;
  • the Customer, where, after the Project ends, a participant separately agrees to disclose specific information about the name or pseudonym they provide, their final position in this Project, points earned in this Project or contact details they provide; only the categories covered by consent are disclosed;
  • accountants, lawyers or information security specialists bound by confidentiality;
  • public authorities where disclosure is required by law.

When international service providers’ infrastructure is used, processing or technical access may involve countries outside the European Economic Area. Such transfers are permitted only with a basis under GDPR Chapter V: an adequacy decision applicable to the particular recipient or appropriate safeguards, such as standard contractual clauses and, where necessary, supplementary measures. You may request information about the basis for a particular transfer of your data and a copy of the safeguards at info@metacon.lt. This policy does not mean that all providers store data exclusively in Lithuania.

Montonio and banks process data needed for their payment services under their own obligations and privacy notices. See the Montonio privacy policy. Processors are granted access only to perform their assigned functions.

6. How long we retain data

Data is retained according to its purpose. The service retention periods and the criteria for calculating them are set out below. Cancellation of an order or a refund does not, by itself, remove the obligation to retain accounting documents and necessary evidence relating to claims.

DataPeriod or criteria for determining it
Account and profile dataFor as long as the account is used for the service. On receiving a request to close it, data no longer needed is deleted; order, accounting and dispute data is subject to the separate periods below. Retaining a profile does not extend the period for individual incomplete orders.
Incomplete orderUp to 90 days after the last action, unless longer retention is needed to investigate a security incident or claim.
Custom project proposal not converted into an orderUp to 12 months after the last correspondence or decision on the proposal, unless a request, dispute or legislation provides a basis for a shorter or longer period. If the proposal becomes an order, the retention period for order and project administration applies.
Order and project administration dataWhile the project or cluster is active and for up to 24 months after closure, except for separately justified retention to comply with a legal obligation or handle a dispute.
Accounting documentsFor the period required by the accounting, tax and document retention legislation applicable to the document type. The period is calculated from the relevant document’s issue date or reporting period and may continue after the account is closed.
Unused invitationsUntil the project ends, but no longer than 90 days after the last invitation, except for data needed to investigate an incident or dispute.
One-time access link recordsThe link is valid for a limited period and cannot be reused to log in after use. Once it expires, its technical record is retained only for security or misuse investigations, no longer than security logs. A link’s validity period and its record’s retention period are different.
Project content and reportsWhile the cluster is active and for up to 24 months after closure so that the Customer can retrieve the results, unless earlier lawful deletion applies or separate archiving is agreed, with its purpose and duration explained in advance.
Recognition requests, consents and disclosure logTogether with project administration data, while the project or cluster is active and for up to 24 months after closure, unless a specific request, dispute or law requires a different period. After consent is withdrawn, no new disclosure based on it takes place; a minimal record of the previous choice may be retained for as long as reasonably necessary to demonstrate the lawfulness of processing.
Technical and security logsUsually up to 12 months; for an incident, as long as necessary to investigate it and protect rights.
Support and complaint correspondenceUp to 24 months after the matter is resolved, or longer if there is an ongoing dispute.

At the end of the period, data is deleted, securely anonymized or retained only to the extent required by law. Data remaining in backups is not used for ordinary operations and is removed through the relevant backup overwrite cycle. Following restoration, recorded deletion and restriction requests must be reapplied. In a dispute or incident, only the data necessary for that particular matter is retained longer, until its final resolution and the end of the applicable limitation period.

7. What accountable anonymity means

Accountable anonymity is not complete or absolute anonymity. Ideas and individual evaluations are shown to other participants without revealing the author, but the platform must link actions to an account to calculate results, points and specialization weights, prevent misuse and preserve the integrity of the project.

By default, the Customer receives only aggregate activity and project information. A representative of the Customer or Coordinator who participates in the Project does not gain privileged access to other participants’ identities, individual evaluations or undisclosed authorship. Pseudonymous data remains personal data if it can be linked to a person. A summary is anonymous only where a person can no longer reasonably be identified, including from a small group or additional context.

In a de-identified activity summary, “inactive” means only that a person joined the Project but neither submitted nor evaluated an idea. This view is not a competence assessment, is not used for automatic blocking or removal, and does not reveal to the Customer which individuals are included in that count.

The “Reveal authorship” button next to a participant’s idea appears only after the Project ends. The end of a Project does not automatically reveal authorship. A participant may deliberately press this button and voluntarily associate the name or pseudonym shown in their account with a particular idea for all participants in that Project to see. Other participants may already have read or saved the information, so a technical change to its display cannot undo that prior access. This does not remove the participant’s GDPR rights. This action does not disclose authorship of their other ideas, individual evaluations, final position, points or contact details, and does not constitute consent to disclose such data to the Customer.

After a Project ends, the participant-provided name or pseudonym, final position in this Project, points earned in this Project or separately provided contact details may be disclosed to the Customer for acknowledgement or an award only on the basis of separate, explicit participant consent and only within the scope they select. Individual evaluations of other people’s ideas are excluded. An invitation or registration email address is not automatically linked to a participant for this purpose, is not used on the basis of an assumption alone and is not disclosed to the Customer.

Individual authorship or evaluations may also be processed or disclosed where necessary to investigate a clear security or legal violation and where an appropriate legal basis exists.

8. Algorithms and the human role

The platform uses proprietary algorithms whose detailed mathematical formulas and source code are not publicly disclosed. Participation rules explain the main principles of result calculation and the meaning of the results. Algorithm confidentiality does not restrict participants’ statutory rights to information about processing of their personal data or, where applicable, an explanation and review of an automated decision.

The platform’s algorithms calculate the results of human evaluations, points and specialization weights under established rules. AI may help formulate prompts for ideas, but people evaluate the ideas.

METACON order administration automatically checks payment status, access links and technical security conditions. These checks are not assessments of a participant’s professional competence. If an automatic check prevents you from using the service, you may request administrator review at info@metacon.lt.

Participants’ professional qualifications and competence are not separately assessed before participation in a project. A final position and points that may be disclosed to the Customer with the participant’s consent are results of that particular Project only, not an overall assessment of the participant’s competence.

9. Your rights

Depending on the circumstances and the applicable legal basis, you have the right to:

  • receive information and access your data;
  • request correction of inaccurate data or completion of incomplete data;
  • request erasure of data or restriction of processing;
  • receive data you have provided in a structured format where data portability applies;
  • object to processing based on legitimate interests;
  • withdraw consent at any time, without affecting the lawfulness of processing before withdrawal;
  • request human intervention where an automated decision with significant effects applies;
  • lodge a complaint with the State Data Protection Inspectorate.

Send your request to info@metacon.lt. To prevent disclosure to another person, we may reasonably request verification of identity or authority to represent someone. Where the Customer controls particular data, we will help direct your request to the appropriate recipient.

Consent to disclosure to the Customer may be withdrawn at any time. Withdrawal does not affect the lawfulness of prior processing or undo the fact that data has already lawfully been provided to a recipient, but no new disclosure based on that consent takes place.

We respond to data subject requests without undue delay and no later than one month after receipt. Depending on the complexity and number of requests, this period may be extended by a further two months; we inform you of the extension and reasons within the first month.

Supervisory authority: State Data Protection Inspectorate.

10. Security, links and cookies

The customer dashboard uses HTTPS, access roles, limited-validity one-time links and session protections. An access link allows login in your name: do not share it or publish it in screenshots. Administration access is restricted to authorized persons. No system can guarantee absolute security; please report any suspected incident promptly.

The order system and customer dashboard use the essential session cookie metacon_projects: it supports login, form security and the ordering process. In the browser it lasts for the session; the browser may restore sessions according to its settings. Refusing or deleting it may require you to log in again and may prevent some functions from working. Non-essential visitor behaviour tracking scripts are loaded only after separate consent in the parts of METACON where this functionality is installed. When you move to Montonio or another external service, that provider’s cookie policy also applies. Non-essential tracking scripts are not currently loaded on this privacy policy page.

11. Cookie preferences and website usage tracking

METACON uses essential cookies needed for login, ordering and security. These generally do not require separate consent. With your consent, we may use additional cookies and similar technologies to understand how the website is used and improve it.

For this purpose, we intend to use Microsoft Clarity (provided by Microsoft). With consent, it may record pages visited, clicks, scrolling, approximate visit duration and device and browser technical data, and replay the sequence of a visitor’s actions. Cookies or similar identifiers may also be used. Such data may be personal data even if we do not know the visitor’s name.

Your choice. Visitors may choose “Accept all” or “Reject non-essential”. Neither the Clarity nor the GA4 tracking script loads before consent. The choice is saved in the browser and can be changed through “Cookie settings” where this functionality is installed. After withdrawal, no new tracking is started; data previously collected lawfully remains subject to the service’s retention and deletion rules.

Data protection. The contents of contact, registration, order and payment fields must not be recorded in Clarity. We check masking of sensitive fields before enabling tracking on the relevant pages. We do not install Clarity on payment service pages. Masking recordings does not eliminate every possible identification risk, so we limit tracking according to its purpose.

Legal basis and recipient. Non-essential tracking is based on your consent (GDPR Article 6(1)(a) and applicable electronic communications privacy rules). Microsoft and its service providers may process data under the service terms. International transfers, where they occur, are subject to GDPR Chapter V. More about Clarity: Microsoft Clarity and Microsoft Privacy Statement.

Retention. The retention of data collected by Clarity depends on the data type and service settings. Before final activation, we check the specific periods in the service dashboard and documentation. For access, erasure or other data protection rights, contact info@metacon.lt.

Google Analytics 4 (GA4). On public pages of the main metacon.lt website where analytics is installed, we also use Google Analytics 4 (provided by Google) with your consent. It helps assess traffic sources, campaign performance, page and catalog views, project expansions, clicks on project ordering links and enquiries confirmed as accepted by the sending service. A click does not count as a paid order. GA4 may process device and browser technical data, approximate location and cookie identifiers.

GA4 limits. The Google analytics script is not loaded before consent or when consent is refused. Advertising personalization and Google Signals are disabled. We do not send names, email addresses, enquiry text or access codes in our analytics events. The page address contains the public path and only permitted campaign parameters; this analytics module is not installed on account, ordering or payment pages. Automatic site search and form interaction measurement are disabled. The analytics choice is stored in browser local storage (metacon_analytics_consent_v2).

GA4 cookies and recipients. With consent, _ga and _ga_… cookies may be used; this installation sets their lifetime to up to 395 days from creation. GA4 event data retention is managed separately in the service settings. Google and its service providers process data under the applicable service terms; transfers outside the EEA, where they occur, are subject to appropriate GDPR Chapter V safeguards. See the Google Privacy Policy and how Google uses data from websites. GA4 uses the consent basis described above, and consent can be withdrawn through Cookie settings.

12. Questions and changes to this policy

Send privacy questions, requests or reports of a possible personal data breach to info@metacon.lt. Identify the relevant order or project, but do not email passwords, payment details or excessive sensitive information.

This policy may be updated when the service, technology or legal requirements change. The version and date will always be shown at the top; the coordinator will be informed directly of material changes affecting an active project.