COOKIE POLICY

Last updated: 22.09.2026

Effective date: 22.09.2026

This Cookie Policy explains how DirectDemocracyS and the websites, platforms, applications and digital services operated by or on behalf of DirectDemocracyS use cookies and similar technologies.

This Policy is intended to apply, where relevant, to the DirectDemocracyS digital ecosystem, including websites and platforms operated under the directdemocracys.org domain and its subdomains, such as:

• https://www.directdemocracys.org

• https://free.directdemocracys.org

• https://ddsai.directdemocracys.org

• https://allddsai.directdemocracys.org

• and other official DirectDemocracyS websites, subdomains, applications and digital services to which this Policy is expressly linked.

Because different platforms may use different technologies and services, the actual cookies and similar technologies deployed on a particular website may differ. The specific cookie information displayed through the applicable cookie-management interface takes precedence for that particular service.

---

1. Purpose of this Cookie Policy

The purpose of this Cookie Policy is to provide clear, transparent and understandable information about:

1. what cookies are;

2. what similar technologies may be used;

3. why cookies and similar technologies are used;

4. which cookies are strictly necessary for the operation and security of the services;

5. which cookies require the user's consent;

6. how users can accept, reject or modify their preferences;

7. how long cookies may remain on a device;

8. whether cookies are first-party or third-party cookies;

9. how cookies may relate to personal data;

10. how users can withdraw consent;

11. how users can control or delete cookies through their browser;

12. how DirectDemocracyS protects users' privacy when using cookies and similar technologies.

This Cookie Policy should be read together with the applicable Privacy Policy, Terms and Conditions, and other legal or informational documents applicable to the relevant DirectDemocracyS service.

---

2. What are cookies?

Cookies are small text files or similar pieces of information that may be stored on a user's computer, smartphone, tablet or other device when a website or online service is accessed.

Cookies can allow a website to:

• remember information about a user's session;

• maintain authentication;

• remember technical or security settings;

• remember language or accessibility preferences;

• maintain a shopping or registration process, where applicable;

• protect a service against abuse or attacks;

• understand how a website is used;

• measure performance;

• remember privacy and cookie preferences;

• provide embedded or third-party functionality, where applicable.

A cookie does not necessarily identify a person directly. However, a cookie identifier can constitute personal data when it can be associated with an identifiable person or combined with other information.

For this reason, DirectDemocracyS treats cookie-related information with appropriate care and applies the applicable data-protection requirements.

The European Commission expressly recognises cookie identifiers as potentially constituting personal data, while also noting that specific rules concerning cookies arise under the ePrivacy framework.

---

3. Similar technologies

This Policy also applies, where relevant, to technologies that perform functions similar to cookies.

Depending on the services implemented on a particular platform, these technologies may include:

• local storage;

• session storage;

• authentication tokens;

• security tokens;

• pixels or tracking pixels;

• web beacons;

• device or browser identifiers;

• similar browser-side storage mechanisms;

• technologies required to maintain a secure authenticated session;

• technologies used to remember privacy choices.

References to "cookies" in this Policy should therefore be understood, where applicable, as including cookies and substantially similar technologies.

---

4. First-party and third-party cookies

Cookies may be classified according to the entity that places them on the user's device.

4.1 First-party cookies

First-party cookies are placed directly by the DirectDemocracyS website or service that the user is visiting.

They are normally controlled by the operator of that service and may be used for purposes such as:

• authentication;

• security;

• session management;

• language preferences;

• accessibility preferences;

• privacy preferences;

• technical functionality;

• service configuration;

• performance and operational purposes.

4.2 Third-party cookies

Third-party cookies are placed by a third-party service that is integrated into or accessed through a DirectDemocracyS service.

Examples may include, depending on the actual implementation:

• video services;

• mapping services;

• analytics providers;

• communication services;

• social-media services;

• security services;

• embedded external content;

• payment services, where applicable;

• other external technologies.

DirectDemocracyS does not automatically assume responsibility for the independent cookie practices of third parties. Users should consult the privacy and cookie information provided by the relevant third party when third-party technologies are used.

Where third-party technologies require consent under applicable law, DirectDemocracyS will seek the required consent before activating them, unless a specific legal exception applies.

---

5. Categories of cookies

Cookies used by DirectDemocracyS may generally fall into the following categories.

5.1 Strictly necessary cookies

Strictly necessary cookies are cookies that are necessary for a website, application or service to operate or for a functionality explicitly requested by the user.

Examples may include cookies or similar technologies used for:

• authentication;

• maintaining a secure login session;

• preventing fraudulent or abusive activity;

• maintaining security;

• load balancing;

• routing;

• maintaining technical sessions;

• storing essential technical preferences;

• remembering cookie-consent choices;

• maintaining the integrity of forms;

• protecting the service against automated attacks;

• maintaining essential functionality of the platform.

These technologies are not used for advertising purposes.

Where a cookie is genuinely strictly necessary for the provision of a service requested by the user, consent may not be required under the applicable ePrivacy rules.

However, the fact that a technology is technically necessary does not automatically mean that every subsequent processing activity associated with the information is exempt from applicable data-protection requirements.

DirectDemocracyS therefore distinguishes, where applicable, between:

a) the technical storage or access necessary for the service; and

b) any subsequent processing of personal data for additional purposes.

---

6. Authentication and account-related cookies

Some DirectDemocracyS platforms may provide registered-user functionality.

Where authentication is available, cookies or similar technologies may be required to:

• recognise an authenticated session;

• maintain the user's login;

• prevent unauthorised access;

• protect the account;

• maintain session continuity;

• distinguish between authenticated and unauthenticated requests;

• protect authentication mechanisms against abuse;

• support secure single sign-on (SSO), where implemented.

These technologies may be essential for members, registered users, administrators, representatives or other authorised users.

Authentication cookies should not be used for advertising or unrelated behavioural profiling.

Where an authentication service is shared between DirectDemocracyS platforms, the relevant authentication technologies may be associated with the technical operation of the applicable SSO infrastructure.

The precise cookies and their duration depend on the authentication architecture actually deployed on the relevant service.

---

7. Security cookies and technologies

DirectDemocracyS may use cookies and similar technologies for security purposes.

These may help to:

• identify suspicious activity;

• detect automated attacks;

• prevent abuse;

• protect registration and login forms;

• prevent session hijacking;

• mitigate certain forms of fraud;

• protect APIs and applications;

• maintain rate-limiting mechanisms;

• protect infrastructure;

• maintain the integrity of authentication;

• detect abnormal requests;

• protect the availability and reliability of the service.

Security technologies may operate without consent where they are genuinely necessary to provide a secure service or to protect the service from abuse, subject to applicable law.

Security-related identifiers must not be repurposed for advertising or unrelated tracking without an appropriate legal basis and, where required, prior consent.

---

8. Functional and preference cookies

Where implemented, functional cookies may remember choices made by the user.

Examples include:

• language;

• accessibility settings;

• interface preferences;

• display preferences;

• region or service configuration;

• previously selected options;

• cookie preferences.

These technologies may improve the user experience without necessarily being strictly necessary for the basic operation of the service.

Where applicable law requires consent for a particular functional technology, the technology will remain inactive until the required consent is obtained.

---

9. Analytics and measurement technologies

DirectDemocracyS may use analytics or measurement technologies to understand how its websites and services are used and to improve their operation.

Depending on the actual implementation, analytics may include information such as:

• pages viewed;

• approximate time spent on a page;

• browser type;

• operating-system type;

• device type;

• language;

• referring page;

• approximate geographic information;

• technical performance information;

• errors encountered;

• interaction with particular website functions.

Analytics should be configured, where technically possible, according to privacy-preserving principles.

Where analytics technologies are not strictly necessary and applicable law requires prior consent, they will only be activated after the user has provided the required consent.

DirectDemocracyS will not describe an analytics technology as "anonymous" merely because a name or email address is not collected. The actual configuration and ability to identify or single out users must be considered.

Where analytics data is genuinely anonymised so that individuals can no longer be identified, the resulting information may be treated differently under applicable data-protection law.

---

10. Advertising and behavioural tracking

DirectDemocracyS is not intended to use cookies or similar technologies to create advertising profiles of users unless such functionality is expressly introduced and appropriately disclosed.

If advertising, behavioural profiling, cross-site tracking, personalised advertising or similar technologies are introduced in the future, the applicable Cookie Policy will be updated before or when such technologies are deployed.

Where required by law, users will be asked for prior consent before such technologies are activated.

Refusing non-essential advertising or tracking cookies must not result in the user being forced to accept those cookies.

---

11. Social-media and external content

Some DirectDemocracyS pages may contain links to, or embedded content from, external services.

Examples may include:

• videos;

• audio;

• maps;

• social-media content;

• external documents;

• external communication tools;

• other embedded resources.

An embedded third-party service may potentially place cookies or access information on the user's device.

Where technically possible, DirectDemocracyS may use privacy-enhancing configurations or a consent-based activation mechanism so that third-party content does not automatically activate non-essential tracking technologies before the required consent has been obtained.

Third-party providers may change their technologies, cookie names, purposes or retention periods. DirectDemocracyS will make reasonable efforts to keep the information presented to users up to date.

---

12. Cookie consent

Where consent is legally required, DirectDemocracyS will request consent before placing or accessing non-essential cookies or similar technologies covered by the consent requirement.

A valid consent mechanism should allow the user to make a genuine choice.

The consent interface should therefore provide, as applicable:

• a clear explanation of the purposes;

• a clear distinction between necessary and non-essential technologies;

• an option to accept non-essential cookies;

• an option to reject non-essential cookies;

• an option to manage individual categories;

• information about third parties where relevant;

• a way to change the user's decision later.

Consent must not be inferred merely from:

• visiting the website;

• scrolling;

• continuing to browse;

• closing the cookie banner;

• using the website without taking a clear affirmative action.

The European Data Protection Board has specifically stated that continued browsing, scrolling or similar passive behaviour does not constitute valid affirmative consent.

---

13. Equal choice between accepting and rejecting

DirectDemocracyS aims to ensure that users can reject non-essential cookies as easily as they can accept them.

The consent interface should not deliberately make rejection substantially more difficult than acceptance.

DirectDemocracyS will avoid deceptive or manipulative consent mechanisms, including designs that attempt to pressure users into accepting optional cookies.

The European Commission has specifically highlighted the importance of avoiding "dark patterns" in cookie consent interfaces and states that, under EU rules, refusing should be as easy as accepting.

---

14. No pre-ticked consent boxes

Where consent is required, DirectDemocracyS will not rely on pre-ticked boxes as a method of obtaining valid consent.

Optional categories should normally be disabled by default until the user actively chooses to enable them.

Consent must represent an affirmative and informed action by the user.

The EDPB's consent guidance specifically addresses the requirement for affirmative consent and the problems associated with pre-ticked mechanisms.

---

15. Withdrawing or changing consent

Users may withdraw or modify consent at any time where consent is the legal basis for the relevant cookies or similar technologies.

DirectDemocracyS should provide a persistent and easily accessible mechanism such as:

"Cookie Settings"

or

"Manage Cookie Preferences"

through which users can:

• review their current choices;

• withdraw consent;

• grant consent;

• change individual categories;

• disable optional technologies.

Withdrawal of consent should be as easy as giving consent.

When consent is withdrawn, DirectDemocracyS will stop activating the relevant optional technologies as soon as reasonably practicable and according to the technical architecture of the service.

Previously collected data may continue to be retained where there is another valid legal basis for its retention or processing, subject to the applicable Privacy Policy and legal requirements.

---

16. Consent records

Where consent is required, DirectDemocracyS may retain a record of the user's cookie choices.

The consent record may contain information such as:

• the date and time of the choice;

• the version of the consent notice;

• the categories accepted or rejected;

• a technical identifier necessary to associate the preference with the relevant browser or session;

• information necessary to demonstrate that consent was obtained.

The purpose of retaining such information is to:

• remember the user's preferences;

• avoid repeatedly asking the same question;

• demonstrate compliance where required;

• maintain the integrity of the consent system.

Consent records should not be used for unrelated profiling.

---

17. Cookie duration

Cookies can be either:

Session cookies

Session cookies are normally deleted when the browsing session ends or when the browser is closed, depending on the specific technology and browser configuration.

Persistent cookies

Persistent cookies remain on the device for a defined period or until they are manually deleted.

The duration of a persistent cookie depends on its purpose.

DirectDemocracyS will seek to use the shortest reasonable retention period consistent with the purpose for which the technology is used.

---

18. Cookie inventory

The following table provides the structure that should be used for the actual cookie inventory of each DirectDemocracyS platform.

The final published version should contain only cookies and technologies that are actually deployed.

Cookie / Technology	Provider	Type	Purpose	First / Third Party	Duration	Consent Required
[COOKIE NAME]	DirectDemocracyS	Necessary	Authentication / security / session	First party	[DURATION]	No, where legally exempt
[COOKIE NAME]	DirectDemocracyS	Necessary	Cookie preference management	First party	[DURATION]	No, where legally exempt
[COOKIE NAME]	DirectDemocracyS	Functional	Language / preferences	First party	[DURATION]	[YES/NO]
[COOKIE NAME]	[PROVIDER]	Analytics	Website measurement	[First/Third] party	[DURATION]	[YES/NO]
[COOKIE NAME]	[PROVIDER]	External content	Embedded service	Third party	[DURATION]	[YES/NO]
[COOKIE NAME]	[PROVIDER]	Security	Abuse prevention / security	Third party	[DURATION]	[YES/NO]

Important: this table must be updated whenever a new cookie, SDK, embedded service, analytics service, advertising technology or similar technology is introduced.

A generic Cookie Policy should never be used as a substitute for an actual technical cookie inventory.

---

19. Platform-specific cookie inventories

Because DirectDemocracyS operates or plans to operate multiple technically different platforms, each platform may maintain its own detailed cookie inventory.

For example:

Main DirectDemocracyS website

Domain: directdemocracys.org

Possible technologies may relate to:

• website functionality;

• security;

• authentication;

• language;

• privacy preferences;

• other services actually deployed on the website.

Registration and member services

Domain: free.directdemocracys.org

Possible technologies may relate to:

• registration;

• authentication;

• session management;

• security;

• identity verification;

• user preferences;

• SSO, where applicable.

ddsAI

Domain: ddsai.directdemocracys.org

The cookie inventory should reflect the technologies actually used by the WordPress-based service and any integrated authentication, security, analytics or external services.

allddsAI

Domain: allddsai.directdemocracys.org

The cookie inventory should reflect the technologies actually used by the Laravel-based service and any integrated authentication, security, analytics or external services.

Other official DirectDemocracyS services may have separate inventories where their technical architecture differs.

---

20. Single Sign-On and authentication across platforms

Where DirectDemocracyS implements Single Sign-On (SSO), authentication-related cookies or tokens may be used to maintain a secure authenticated session.

Such technologies may allow an authorised user to authenticate across compatible DirectDemocracyS services without unnecessarily repeating the entire authentication process.

SSO technologies may involve:

• authentication sessions;

• security tokens;

• domain-specific session information;

• expiration mechanisms;

• anti-replay mechanisms;

• secure transmission;

• session invalidation;

• logout mechanisms.

The existence of an SSO system does not automatically mean that every DirectDemocracyS website receives access to all user information.

Access should be limited according to the architecture, permissions and purposes applicable to each service.

SSO cookies and authentication technologies should be treated as security-sensitive technologies.

---

21. Security attributes of cookies

Where technically appropriate, DirectDemocracyS may configure cookies using security attributes such as:

• Secure, so that cookies are transmitted only over secure connections;

• HttpOnly, where JavaScript access is not required;

• SameSite, to reduce certain cross-site request risks;

• appropriate expiration times;

• appropriate domain and path restrictions.

The exact configuration depends on the function of each cookie.

Security configuration is part of the technical protection of the service and does not, by itself, determine whether a cookie requires consent.

---

22. Cookies and personal data

A cookie itself is not necessarily personal data in every situation.

However, information associated with a cookie may constitute personal data where it can be linked, directly or indirectly, to an identifiable individual.

For example, this may occur where a cookie identifier is associated with:

• an account;

• an authenticated session;

• an IP address;

• an email address;

• a user profile;

• other identifying information.

Where cookie-related information constitutes personal data, DirectDemocracyS processes it in accordance with applicable data-protection law and the applicable Privacy Policy.

---

23. Legal bases

The legal basis applicable to cookie-related processing depends on the purpose and technology involved.

For strictly necessary technologies, the applicable ePrivacy rules may permit their use without prior consent where the relevant legal conditions are satisfied.

For non-essential technologies requiring consent, the applicable legal basis may include the user's valid consent.

Where personal data is subsequently processed, the relevant GDPR legal basis must also be considered separately.

The fact that a particular cookie does not require consent for its technical storage or access does not automatically establish the legal basis for every subsequent processing activity involving information obtained through that cookie.

DirectDemocracyS will therefore assess cookie technologies according to their actual function and the applicable legal framework.

---

24. International services and third-party providers

Some DirectDemocracyS services may use technical providers located in countries other than the country in which the user is located.

Where personal data is transferred outside the European Economic Area or otherwise subject to international-transfer rules, DirectDemocracyS will apply the safeguards required by applicable law.

Information concerning specific processors, international transfers and data-protection safeguards should be provided in the applicable Privacy Policy.

---

25. Browser controls

Most modern browsers allow users to:

• view cookies;

• delete cookies;

• block cookies;

• block third-party cookies;

• restrict cookies;

• configure cookie permissions;

• receive warnings before certain cookies are stored.

Users can therefore also manage cookies through their browser settings.

However, disabling strictly necessary cookies may prevent certain functions from operating correctly.

For example, disabling authentication or session cookies may prevent a user from:

• logging in;

• remaining logged in;

• accessing restricted areas;

• completing certain registration processes;

• using other authenticated functionality.

Browser controls do not necessarily replace a website's consent-management mechanism because they may not distinguish between all individual purposes and categories.

---

26. Deleting existing cookies

Users can delete cookies already stored on their device through their browser settings.

Deleting cookies may also delete:

• authentication sessions;

• saved preferences;

• language settings;

• cookie-consent preferences;

• other locally stored configuration information.

After cookies are deleted, a website may ask the user to make cookie choices again.

---

27. Do Not Track and similar browser signals

Browsers may provide privacy-related signals or settings, including "Do Not Track" or similar mechanisms.

The technical and legal interpretation of such signals varies depending on the technology and applicable legislation.

Where a legally recognised privacy signal is applicable to a particular service, DirectDemocracyS will assess and implement it according to the applicable legal and technical requirements.

---

28. Children's privacy

DirectDemocracyS services are designed and operated according to the age requirements and access conditions applicable to each service.

Where cookies or similar technologies involve the processing of personal data relating to children, DirectDemocracyS will apply the safeguards required by applicable law.

Where parental consent or other specific requirements apply, those requirements will be addressed through the relevant registration, access and privacy procedures.

This Cookie Policy does not replace any age-related requirements contained in the Terms and Conditions or Privacy Policy.

---

29. Changes to this Cookie Policy

DirectDemocracyS may update this Cookie Policy when:

• the website architecture changes;

• new technologies are introduced;

• existing cookies are removed;

• third-party services change;

• legal requirements change;

• security requirements change;

• the purposes of technologies change;

• new DirectDemocracyS platforms are introduced.

The "Last updated" date at the beginning of this Policy will be changed whenever a substantive update is made.

Where required, users will be informed of material changes and asked to provide consent again if the changes introduce new consent-requiring purposes.

---

30. Technical changes and cookie re-evaluation

The introduction of any of the following should trigger a review of the Cookie Policy and cookie-consent configuration:

• a new plugin;

• a new WordPress extension;

• a new Joomla extension;

• a new Laravel package;

• a new JavaScript library;

• a new analytics system;

• a new advertising system;

• a new video provider;

• a new social-media integration;

• a new payment provider;

• a new authentication provider;

• a new CDN;

• a new security service;

• a new external API;

• a new embedded service;

• a new monitoring system.

Developers and administrators should not assume that a new component is "cookie-free" without checking its technical behaviour.

---

31. Cookie audits

DirectDemocracyS should periodically review its websites and applications to identify:

• cookies actually being set;

• local-storage technologies;

• third-party requests;

• embedded services;

• JavaScript-based tracking;

• analytics technologies;

• authentication technologies;

• security technologies;

• cookie duration;

• cookie domains;

• consent dependencies.

The published cookie inventory should correspond to the technologies actually deployed.

A cookie scanner or browser inspection tool may assist the technical audit, but the results should also be reviewed manually because some technologies are activated only after specific actions, login states, geographic conditions, consent choices or interaction with embedded content.

---

32. Data minimisation

DirectDemocracyS seeks to apply the principle of data minimisation to cookies and similar technologies.

Where the same technical purpose can be achieved with:

• fewer cookies;

• shorter retention;

• less information;

• first-party rather than third-party technologies;

• anonymised or aggregated information;

• privacy-preserving configurations;

the technically and legally appropriate solution should be considered.

Optional tracking should not be introduced merely because a technical service makes it possible.

---

33. No assumption of consent

DirectDemocracyS does not consider a user to have consented merely because the user:

• visits a page;

• reads content;

• scrolls;

• clicks ordinary navigation links;

• remains on the website;

• closes a banner without making an affirmative choice;

• creates an account, unless the specific consent mechanism clearly and lawfully obtains consent for the relevant purpose.

Consent must be associated with a specific purpose or category where required.

---

34. Separation of purposes

Where consent is required, DirectDemocracyS should avoid combining unrelated purposes into a single vague consent request.

For example, where applicable, the following should be distinguishable:

• analytics;

• personalised advertising;

• social-media tracking;

• embedded third-party content;

• functional technologies;

• other optional tracking.

Users should be able to understand what they are accepting.

---

35. Refusing optional cookies

Refusing optional cookies should not prevent access to content or services that do not technically require those cookies.

However, certain optional features that depend on third-party technologies may not function when the corresponding technology is refused.

For example, an embedded external video may require activation of the relevant external service.

In such cases, the user should be informed that the functionality is unavailable because the corresponding optional technology has not been activated.

---

36. Necessary cookies and service availability

Strictly necessary cookies may continue to operate even when a user rejects optional cookies, because disabling essential technical mechanisms could prevent the website or requested service from functioning.

DirectDemocracyS will seek to ensure that necessary cookies are limited to what is genuinely necessary for the relevant technical purpose.

A cookie should not be classified as "necessary" merely because it is convenient, useful or commercially desirable.

---

37. Relationship with the Privacy Policy

This Cookie Policy explains the use of cookies and similar technologies.

The applicable Privacy Policy provides broader information concerning the processing of personal data, including, where applicable:

• categories of personal data;

• purposes of processing;

• legal bases;

• data recipients;

• processors;

• international transfers;

• retention periods;

• data-subject rights;

• security measures;

• contact details;

• supervisory-authority rights.

Where information obtained through cookies constitutes personal data, the relevant Privacy Policy also applies.

Privacy Policy: [INSERT LINK]

---

38. Contact

For questions concerning this Cookie Policy or the use of cookies and similar technologies, users may contact DirectDemocracyS through the official contact channels provided on the relevant website.

Organisation: DirectDemocracyS

Official website: https://www.directdemocracys.org

Privacy contact: [INSERT PRIVACY EMAIL]

Data Protection Officer, where applicable: [INSERT DPO INFORMATION OR DELETE IF NOT APPLICABLE]

Postal address: [INSERT OFFICIAL LEGAL ADDRESS]

---

39. Supervisory authority

Where applicable, individuals have the right to lodge a complaint with the competent data-protection supervisory authority.

For individuals located in the European Union, this may generally be the supervisory authority in the Member State of their habitual residence, place of work, or place of the alleged infringement, subject to the applicable rules.

For Romania, the competent supervisory authority is:

Autoritatea Națională de Supraveghere a Prelucrării Datelor cu Caracter Personal (ANSPDCP)

Official website:

https://www.dataprotection.ro/

Users should consult the competent supervisory authority for the most current information concerning complaints and available procedures.

---

40. Transparency commitment

DirectDemocracyS considers transparency an essential principle of its digital infrastructure.

Accordingly, DirectDemocracyS aims to:

• clearly identify non-essential cookie categories;

• explain their purposes;

• avoid unnecessary tracking;

• avoid deceptive consent mechanisms;

• provide meaningful choices;

• make withdrawal of consent accessible;

• maintain an accurate cookie inventory;

• review third-party technologies;

• minimise unnecessary data collection;

• protect authentication and security technologies;

• update this Policy when material technical changes occur.

The objective is not merely to display a cookie banner, but to provide users with meaningful control over optional technologies.

---

41. Summary of user choices

When the applicable consent mechanism is displayed, users should be able to choose, according to the technologies actually deployed:

Accept all optional cookies

Reject all optional cookies

Manage preferences

The "Manage preferences" interface should provide sufficiently granular choices for the purposes actually used by the relevant platform.

Strictly necessary technologies should remain available where legally permitted and technically necessary for the requested service.

---

42. Version and review information

Cookie Policy version: [VERSION NUMBER]

Effective date: [DATE]

Last reviewed: [DATE]

Last updated: [DATE]

Next scheduled review: [DATE]

Responsible department/team: [INSERT RESPONSIBLE TEAM]

---

Important implementation note

This Cookie Policy is a legal-information document and should be implemented together with an actual technical cookie inventory.

Before publication, DirectDemocracyS should verify the cookies and similar technologies actually generated by each platform, including cookies generated by:

• Joomla;

• WordPress;

• Laravel;

• plugins and extensions;

• themes;

• JavaScript libraries;

• SSO/authentication systems;

• security systems;

• analytics systems;

• embedded content;

• CDN or infrastructure services;

• external APIs;

• monitoring systems;

• other third-party services.

The names, purposes, providers, durations and consent requirements in the final cookie table should reflect the actual technical configuration, rather than assumed or generic cookie names.

This distinction is important because a cookie policy is most useful when it accurately describes what the website actually does.

End of Cookie Policy

Continue Reading →