Cookie Policy

This page explains what gets saved on your device when you open allportugalbusinessclub.com, why it is there, what waits for your answer, and how you change your mind later. Our Privacy Policy covers what happens to your data once we have it. Section 8 of that policy gives the short version of what is on this page. This page is the long version, and the two are meant to agree.

 

3. What a cookie is, and what else counts

A cookie is a small text file a website saves in your browser. It can hold your session, the fact that you signed in, or the answer you gave in the consent window.

 

The same rules apply to everything that works like a cookie even when it is not one: browser local storage, session storage, and tracking pixels, which are tiny images or scripts loaded from another company’s server so that company learns you opened the page. Throughout this page, “files” means all of it. The law looks at what a technology does, not at what it is called.

 

4. The rule we work by

Article 5 of Lei n.º 41/2004 (the Portuguese law on privacy in electronic communications), as amended by Lei n.º 46/2012, is direct about it: storing anything on your device, or reading anything already stored there, requires your prior consent, given after clear and complete information. There is one narrow exception, for what is technically necessary to carry a communication or to deliver a service you asked for yourself.

 

Consent as a legal basis is article 6(1)(a) of the General Data Protection Regulation (GDPR). Article 7(1) puts the burden on us to demonstrate that you consented, which is why a record of your answer exists at all. Article 7(3) lets you withdraw consent at any moment, and says withdrawing must be as easy as giving.

 

We will be plain about one thing. The banner has been running on this site while this page did not exist. Consent given after incomplete information is weaker consent, and publishing this page is how we fix that rather than how we paper over it.

 

5. What lands on your device before you answer

Before you touch anything in the consent window, your device receives:

 

the core Wix platform files. They hold your session, protect forms against cross-site request forgery, keep you talking to the same server for the length of your visit, and give your browser a technical visitor identifier. The page does not assemble without them. These fall under the technical exception in article 5;

 

the consent tool itself, loaded from Usercentrics so that the window can be shown to you at all;

 

your member session, but only if you have signed in to this site before and that session has not expired. Before you sign in, nothing of the members area is stored.

 

The record of your answer appears at the moment you answer, not before. It exists so that we stop asking you on every page and so that we can demonstrate your choice under article 7(1) GDPR.

 

6. What waits for your answer

Anything that is not in section 5 is supposed to wait until you say yes. That includes analytics, advertising and retargeting tools, and embedded content served directly by another company.

 

7. The categories in the settings window

Essential. These make the page open, the form submit, the session stay secure. They cannot be switched off, and the law does not ask for consent for them.

 

Functional. These remember a preference so you do not set the same thing twice. They load only with your consent.

 

Analytical. These would show which pages people read and where they stop. They load only with your consent.

 

Marketing. Advertising and retargeting tools, including content embedded straight from a third-party platform. They load only with your consent.

 

You may also see a technical Unknown group. That is how the consent service labels a file its own scan could not place, and it is a signal to check rather than a category with a meaning of its own.

 

8. What is actually running here

This is a small site. It shows investment project listings, describes the club, takes a message through the contact form, offers a newsletter, and has a sign-in for members. Nothing is sold here and no payment is taken here.

 

To the best of our knowledge there is no analytics counter, no advertising pixel and no third-party embedded content on this site. We describe that as our current knowledge rather than as a measured fact, and section 9 explains the difference.

 

Wix platform, core files. Essential. Session, request forgery protection, server affinity, a technical visitor identifier. Confidence: high.

 

Usercentrics consent tool. Essential. Shows the window and stores the record of your answer. Confidence: high, and observed on the live site.

 

Wix Members area. Essential once you sign in, and absent before that. Your member session. Confidence: high.

 

Wix Forms, used by the contact form and the newsletter sign-up. Essential at the moment you submit, to carry your entries between steps and to guard against automated submissions. Confidence: medium.

 

Anything analytical or advertising. We believe there is none. Confidence: medium, because it has not been measured.

 

The exact name and lifetime of every file that is actually present is shown inside the consent window itself: open Cookie settings and expand any service. That list comes from the tool, updates on its own, and is more current than any table we could freeze into this page.

 

9. What we have not checked, said plainly

A full technical scan of this site has never been run. Until it is, we can tell you what this site is built from and what that normally stores, and we cannot hand you a complete, verified list of files.

 

We would rather say that than publish a tidy table that looks measured and is not. The same reservation appears in section 8 of our Privacy Policy, and it will stay on both pages until the scan is done. When it is done, this page is updated with the result, whatever the result turns out to be.

 

One more thing belongs here for the same reason. The consent tool is supposed to hold back everything non-essential until you answer. On this site that behaviour has not been verified by measurement. We state it as a requirement we have set, not as a test we have passed.