Privacy policy

Last updated: 04/09/2026

This Privacy Policy explains how Stack Chronicle, available notably at stackchronicle.com and stackchronicle.fr, processes users’ personal data.

Stack Chronicle is published from France.

1. Data Controller

The controller responsible for personal data processing carried out directly by Stack Chronicle is:

Hugo Noirtault
Publisher of Stack Chronicle
Contact: contact@stackchronicle.com

No private residential address or personal telephone number is published on this page.

2. Personal Data We May Process

Depending on how you use the website and which services are enabled, Stack Chronicle may process the following categories of information.

Information you provide voluntarily

When you contact Stack Chronicle, you may voluntarily provide information including:

  • your name or pseudonym;
  • your email address;
  • the content of your message;
  • any other information you choose to provide.

Technical information

Certain technical information may be processed when you visit the website in order to operate and secure it, including:

  • IP address;
  • browser type;
  • device type;
  • operating system;
  • date and time of requests;
  • technical and security logs.

Some of this information may be processed by Stack Chronicle‘s hosting provider, o2switch, as part of its hosting services.

Cookies, advertising and privacy preferences

Where the relevant services are enabled, and subject to consent where required, cookies or similar technologies may also process information in order to:

  • remember your privacy preferences;
  • measure website usage;
  • serve and measure advertising;
  • prevent fraud;
  • personalise advertising where you have consented to such use.

3. Purposes and Legal Bases

Personal data may be processed for the following purposes.

Website operation and security

Technical information may be processed to operate the website, detect technical problems, prevent abuse and protect its infrastructure.

This processing is based on Stack Chronicle‘s legitimate interest in maintaining a reliable and secure website.

Responding to enquiries

When you contact Stack Chronicle, the information you provide is used only to the extent necessary to process and respond to your enquiry.

This processing is based on Stack Chronicle‘s legitimate interest in communicating with its readers and other contacts.

Managing privacy preferences

Information necessary to record your choices regarding cookies and similar technologies may be retained in order to respect and demonstrate those choices.

Advertising and audience measurement

Where required by applicable law, non-essential cookies and similar technologies used for advertising or audience-measurement purposes are subject to your consent.

You may accept, reject or subsequently modify your choices through the consent management tool available on the website.

4. Google AdSense and Advertising

Stack Chronicle may use Google AdSense to support the website through advertising.

When Google AdSense is enabled, Google and certain advertising partners may use cookies, IP addresses, pixels, identifiers or similar technologies for purposes including:

  • serving advertisements;
  • measuring ad delivery and performance;
  • limiting repeated advertisements;
  • preventing fraud and abuse;
  • personalising advertising where the user has consented.

Google’s Publisher Policies require publishers to disclose data collection, sharing and use resulting from Google products, including technologies such as cookies, web beacons, IP addresses and other identifiers.

For users in the European Economic Area, the United Kingdom and Switzerland, Stack Chronicle uses, where required for its advertising services, a Google-certified Consent Management Platform (CMP) integrated with the IAB Europe Transparency and Consent Framework. Google requires publishers using its advertising products to use such a CMP when serving personalised advertising in these territories.

The advertising technology providers actually used by the website and their respective purposes may be reviewed through the consent management interface.

5. Cookies and Similar Technologies

Stack Chronicle uses or may use cookies and similar technologies.

Some are strictly necessary for the operation or security of the website. Others, including advertising technologies and certain audience-measurement tools, may require consent under applicable law.

Where consent is required, users must be given a genuine choice and must be able to withdraw consent easily.

Further information is provided in Stack Chronicle‘s Cookie Policy.

6. Recipients of Personal Data

Depending on the services actually enabled, personal data may be accessible to:

  • Stack Chronicle;
  • o2switch, as hosting provider;
  • technical service providers necessary for the operation or security of the website;
  • Google and, where advertising services are enabled, authorised advertising technology providers;
  • legally authorised authorities where disclosure is required by law.

Stack Chronicle does not sell its readers’ personal data.

7. International Data Transfers

Certain service providers, including companies belonging to international groups such as Google, may process information from countries located outside the European Economic Area.

Where international transfers occur, they must rely on a transfer mechanism permitted by applicable data-protection law, such as an adequacy decision, Standard Contractual Clauses or another appropriate safeguard.

8. Data Retention

Personal data is retained only for as long as necessary for the purposes for which it was processed.

In particular:

  • correspondence sent to Stack Chronicle is retained for the time necessary to respond to and reasonably follow up the enquiry;
  • technical and security logs are retained for the periods necessary to operate and secure the website or according to the policies of the relevant service providers;
  • consent preferences are retained for the period configured in the consent management platform;
  • information processed by Google and advertising providers is retained in accordance with their own policies and the applicable consent settings.

Where a specific retention period is required by law, that period will apply.

9. Your Rights

Under the General Data Protection Regulation and applicable French data-protection law, you may have, depending on the processing concerned, rights including:

  • the right of access;
  • the right to rectification;
  • the right to erasure;
  • the right to restriction of processing;
  • the right to object;
  • the right to data portability where applicable;
  • the right to withdraw consent at any time where processing relies on consent.

Withdrawal of consent does not affect the lawfulness of processing carried out before consent was withdrawn.

To exercise your rights, please contact: contact@stackchronicle.com

Proof of identity may be requested only where necessary to verify the legitimacy of a request.

You may also lodge a complaint with the French data-protection authority, the Commission nationale de l’informatique et des libertés (CNIL).

Article 13 of the GDPR requires controllers to provide information including their identity and contact details, processing purposes and legal bases.

10. No Sale of Personal Data

Stack Chronicle does not directly sell or commercially trade its readers’ personal data.

The use of third-party advertising services may nevertheless involve data processing by those providers under the conditions described in this Privacy Policy and through the website’s consent management interface.

11. Changing Your Privacy Choices

You may modify or withdraw your choices regarding cookies and other consent-based technologies at any time by using the:

Manage Privacy Choices

link available in the website footer.

12. Changes to this Privacy Policy

This Privacy Policy may be updated to reflect:

  • changes to Stack Chronicle;
  • the addition or removal of technical services;
  • changes to advertising services;
  • changes in applicable laws or regulations.

The date of the most recent revision appears at the top of this page.