Last updated: October 15, 2026
Notice version: 2026-10-15.1
1. Who operates this website
France Regional, available at https://franceregional.com, is operated by Marice Caballero, an individual based in Georgia, United States. The operator is responsible for the personal data processing described in this policy.
Privacy contact: info@franceregional.com
France Regional publishes a public cultural directory for a worldwide audience, with information about regional culture, living traditions and events. This policy explains our limited aggregate content measurement and separately consented optional contextual statistics when enabled, the technical services used to deliver the website, and information received through correspondence or public event sources.
2. Aggregate content measurement and optional statistics
We use our own Regional Observatory plugin. Its basic content counters and optional contextual statistics are separate. This policy describes levels 1 and 2 of Observatory 0.9.0. It does not describe or authorise the separate detailed tracking level.
Basic content counters
Where the limited basic core is enabled, it counts automatically without asking you to accept the optional statistics. You can exclude your browser through Privacy preferences. Rejecting optional source or browser statistics does not itself stop an otherwise active basic core. If the core is not enabled, it collects no content counts.
The core counts views of public posts and pages, including event pages, and recorded clicks on recognised official event links supplied by the published more_info_url field. It can also count public cultural archive displays, openings of event markers, selections of compatible map category controls, and WordPress page-not-found displays. These are separate action types: opening a marker is not a page view, and selecting a category is not an official-link click. The purpose is to understand use of our publications, navigation functions and official links, and to maintain the service. It does not measure advertising campaigns, purchases, attendance or activity after you leave our website.
An official click is recognised against the event’s current published official link. A shared public content-validation token identifies permitted event metadata, not a visitor. The measurement endpoint receives no complete destination URL or query parameters. Unrecognised, outdated or unsupported links may not count. Directions links and arbitrary external links are not automatically official-event clicks. A recorded click does not prove that the destination website loaded.
Page-not-found measurement stores a generic 404 count without the missing address, path, query or search terms. It covers WordPress responses that execute the measurement client; errors generated entirely by hosting or another service may not be counted.
Validated requests increment accumulated daily counters. Their fields are the UTC day, action type, applicable public publication/event or content identifiers, official destination domain where relevant, and total. Separate site-wide hourly counters contain only the UTC hour, action type and total. They do not contain publication, region, referral source, browser or visitor fields. There is no stored record of the exact time of an individual action.
The basic counters do not store visitor IP addresses or IP hashes, reader or session identifiers, referring URLs, detailed device profiles, precise locations, individual time on pages or individual navigation histories. We do not create fingerprints, combine the counters with server logs to identify visitors, or track people on external websites. Technical delivery information is addressed separately below.
Counts describe successfully recorded actions, not unique people or all human visits. Reloads and repeated clicks may contribute again. Privacy choices, browser signals, bots, unavailable JavaScript, unsupported maps, network failures, quotas and failed storage can affect coverage. Excluding a browser stops future contributions; it cannot subtract an earlier contribution from a total that has no reader identifier.
Optional contextual statistics
The operator can select level 2 to offer optional general referral-source and/or general browser-family statistics. Each enabled dimension is identified in the notice. The plugin waits for an affirmative current acceptance before reading those values for contextual analytics or sending their measurement request. Rejecting or withdrawing that acceptance stops optional context without interrupting an otherwise enabled basic core.
The website and maps remain available either way. Where optional statistics are offered and no current choice is remembered, a centered notice requests a decision before interacting with the content behind it. Both Accept and Reject allow access. Read our Privacy Policy opens the detailed notice before a decision is made; opening the notice does not grant acceptance. Privacy preferences remain available to change a choice.
Referral source is reduced in the browser to Google, Bing, social networks, another external source, internal navigation or unavailable. It does not send or retain the referring URL, path, search terms, campaign parameters, fragment or an arbitrary referring hostname. Unavailable does not necessarily mean a direct visit. No original source is preserved across a person’s later navigation and no campaign conversion is attributed.
Browser information, when enabled and accepted, is reduced to Chrome, Firefox, Safari, Edge or Other. The full user-agent, detailed version and device fingerprint are not transmitted as a contextual statistic. Request headers can separately be inspected temporarily for bot filtering as explained below.
Each contextual dimension is stored as an independent daily site-wide total. Source and browser are not combined with each other, a publication, event, map action, hourly period or visitor. They are not individual records and cannot reconstruct a person’s journey. Repeated accepted loads can contribute again. These figures represent the accepted and successfully recorded sample, not the whole audience; they must not be added to the basic counts as additional people.
Levels 1 and 2 do not offer country measurement, GeoIP, visitor/session IDs, unique-person counts, profiles or campaign attribution. Acceptance of context does not enable detailed tracking.
Private reports and catalogue observations
Reports are restricted to authorised administrators. Content, cultural, official destination-domain, archive and map-action reports and exports include exact stored counts for the current UTC day and earlier selected days. The current day is partial and can increase. Separate site-wide hourly totals include the current partial hour.
The global panel and content reports refresh approximately every ten seconds while open and visible; regional comparison reports and their timeline refresh approximately every thirty seconds. Short shared administrative caches can delay the next visible update. The reports show their last read and retain earlier figures with a warning when a refresh fails, rather than replacing them with zeros. A report-generation timestamp identifies when totals were read, not an individual action timestamp.
The interregional timeline compares regions using a common scale, separate colours and a selectable legend. It can show recorded event-page views or official clicks, or actions divided by comparable catalogue event counts, for selected dates and public cultural classifications. Exact recorded totals are available alongside the visual representation. Percentages and ratios may be rounded for readability. These are aggregate content reports and not records of individual visitors. Optional source/browser statistics remain separate daily site-wide totals without content, region or hourly joins.
Cultural filters use public catalogue classifications. Regions, categories, topics and tags are dynamic, and an event can belong to several groups. Their totals are not mutually exclusive. Comparisons use the current public catalogue and applicable publication dates; they do not reconstruct former availability or classifications. Views or clicks per event provide context, not a unique-person conversion rate or proof of individual interest. Opening a general page or a map is not automatically a view of every event displayed there.
Catalogue reports and snapshots examine public event records, classifications and dates independently of visitor measurement. A snapshot describes an observation of available catalogue records; it does not establish a complete census of regional culture or reconstruct unobserved past records.
Updating the plugin preserves earlier aggregate history. Some earlier periods were collected automatically and others only after acceptance. Site configuration records identify collection-method changes; they are not visitor records. A UTC day or hour spanning a transition can mix samples that existing totals cannot separate. Research comparisons must identify or exclude these mixed intervals rather than assume equal coverage. Detailed tracking history is retained separately and is not automatically mixed into the basic reports.
We may use effectively anonymous figures for a thesis, project evaluation and cultural-visibility reporting. Before external disclosure we review small groups, combinations and possible identification. Individual records are not published, and this policy does not retroactively authorise collection under earlier notices.
3. Privacy preferences and choice cookies
Privacy preferences separates optional contextual acceptance from exclusion of the basic measurement. These controls do not ask for your name or create a reader profile.
When optional contextual statistics are enabled and no valid current choice is available, the notice offers equally visible Accept and Reject buttons for the optional statistics described there. These decisions concern only the optional dimensions described there. Both allow access to publications and maps. Doing nothing, reading the policy, leaving the page or closing a tab is not acceptance. You can reopen preferences and withdraw optional acceptance at any time.
Preferences also provide a separate control to stop Observatory measurement for this browser and to restore eligibility later. Restoration does not grant a new optional acceptance; if an earlier optional acceptance is still valid, those statistics can resume too. Accepting optional statistics does not remove an existing full exclusion. Browser privacy signals and signed-in exclusions still apply.
Basic exclusion cookie
On an explicit exclusion the plugin saves a first-party cookie whose name begins with rgo_basic_optout_. Its value is the same constant for excluded browsers and contains no reader or session identifier. It is used only to remember that exclusion for up to 180 days. Ordinary visits and repeating an active exclusion do not renew it. Explicit restoration deletes the applicable exclusion cookies. Clearing cookies, changing browsers or expiry can remove the remembered exclusion; if the basic core is enabled, counting can then resume without optional contextual acceptance.
Optional contextual choice cookie
The separate first-party cookie whose name begins with rgo_context_consent_ remembers acceptance or rejection of optional context for up to 180 days from a changed choice. Its signed value is common to browsers making the same choice for the same site and current notice/configuration. It contains no random reader identifier, individual receipt, session ID, IP address or navigation history. Ordinary visits and repeating an unchanged choice do not renew it. Changing the notice or configuration invalidates earlier optional acceptance and requires a new decision; it does not convert refusal into acceptance.
Earlier Observatory versions used other choice cookies, including rgo_basic_consent_, rgo_basic_choice_ and rgo_context_choice_. Available previous global refusals remain exclusions until explicitly restored. They are not silently reinterpreted as permission for basic counting when upgrading. Previous positive choices do not grant acceptance of this version’s optional context. Legacy cookies can remain until removed, expired or explicitly cleared by the preference control.
Other exclusions and technical failures
Observatory respects supported Do Not Track and Global Privacy Control signals and excludes signed-in WordPress activity, including administrators. These exclusions take precedence over acceptance. The client stops on detected browser automation; the recipient temporarily inspects bounded user-agent information to skip recognised bots, including known AI crawlers. It does not retain the header, bot identity or a rejected-request diary in its counters. These filters reduce recognised automation and do not certify that the remaining traffic is human.
Without JavaScript the public client does not count. Browser features, network failures and unavailable preference controls can prevent collection. The client refreshes shared current settings before measurement to reduce inconsistencies caused by cached pages. This configuration exchange contains public content identifiers and shared settings, not a visitor identifier or the requested page URL. A changed notice does not silently reuse an acceptance submitted for an earlier notice.
If optional acceptance cannot be verified or safely coordinated between tabs, optional measurement remains stopped. An explicit restoration must also be safely coordinated so that a delayed response cannot override a later exclusion; otherwise measurement remains excluded. If a preference change cannot be saved safely, affected measurement stops and access to the website remains available. You can contact info@franceregional.com for help.
Observatory preferences control its audience statistics. They do not prevent technical requests needed to deliver pages, images and maps. WordPress can separately use necessary authentication cookies.
4. Hosting and technical request information
The website is hosted through Hostinger Business Web Hosting. Its main hosting server is located in Massachusetts, United States.
Delivering a web page requires the hosting infrastructure to receive technical information such as an IP address, the requested resource, request time and browser information supplied with the request. Access, error and security records may be used for delivery, maintenance, troubleshooting and protection against abuse. This is separate from the Observatory counters, which do not store visitor IP addresses.
Hostinger has not provided us with a confirmed account-specific retention period or detailed deletion timetable for each category of HTTP access, error, security or internal operational logs. We therefore do not assign those logs a numerical retention period in this policy. Information about Hostinger’s processing is available in its Privacy Policy and Data Processing Addendum, or by contacting us for the information available for our service.
Hostinger Data Processing Addendum
5. Images and interactive maps
Cloudflare R2 is used to store and deliver event images. When your browser requests an image, Cloudflare receives the technical information needed to respond, including an IP address and request information. Some images may be loaded directly from the organisation that originally published them; that organisation receives the corresponding browser request.
Our maps use Leaflet and map tiles from CARTO. OpenStreetMap tiles may be used as a fallback. The browser connects to the selected tile provider to obtain the map background. That provider receives technical request information, which may include an IP address, browser information, request time and a referring page where supplied by the browser.
CARTO’s published Basemaps Terms state that its request logs use truncated IP addresses, are stored in the United States and are retained for 30 days. These are the provider’s request logs, not Observatory records. If OpenStreetMap’s service is used, its own privacy policy applies to those requests.
OpenStreetMap Foundation Privacy Policy
The locations displayed on our maps are event or venue locations. The basic measurement does not request your browser’s precise geographical location. Selecting a Directions link opens an external mapping website; that website then processes your visit under its own terms and privacy policy.
Google Search Console
We use Google Search Console to review aggregate information about France Regional’s appearance in Google Search, such as impressions, clicks from search results, common query statistics, approximate search-origin countries, and indexing or crawling issues. This is Google Search information, not a measurement of a person’s subsequent journey through France Regional or clicks on our official event links.
Search Console ownership verification through DNS or a static verification entry does not itself install a visitor analytics tracker. Using Search Console does not establish that a separate Google Analytics tracker is installed; any such website tracking would need its own disclosure and controls.
Google’s own search and account services are governed by its privacy information. We do not combine Search Console reports with Observatory records to identify visitors.
Google Search Console documentation
6. Correspondence and public event information
If you email us, we receive your email address, message and any information you choose to include. We use it to respond, handle corrections or privacy requests, and maintain any necessary follow-up. Please avoid sending sensitive information that is not needed for your request.
The catalogue draws on public event and tourism information, including DATAtourisme and official organisations’ websites. Published listings may contain event and venue information, official links, images and professional contact details supplied by those sources. This information is used to describe and promote cultural activities, not to build profiles of website visitors. Contact us if a listing contains inaccurate information or personal information you believe should be corrected or removed.
7. Purposes and applicable legal bases
The limited automatic basic core is used only for our own audience measurement to understand content use, navigation functions and technical capacity and to maintain the service. Its configuration minimises audience information through limited action fields, immediate aggregation and no visitor identifiers or cross-service matching. Current-day exact reports are restricted to authorised administrators. We do not treat a software setting or the appearance of a consent notice as a regulatory certification.
We do not use this core for advertising, individual profiles, campaign attribution or commercial conversion tracking. Where the collection temporarily processes personal data before effective aggregation, we rely on our legitimate interest in operating and improving this cultural directory, subject to the safeguards and opposition described here.
Optional general-source and browser statistics rely on prior acceptance when offered. Where this involves personal-data processing, consent is its basis. Refusal or withdrawal does not restrict access to cultural information and does not stop a separately enabled basic core unless a full exclusion also applies. Withdrawal does not affect the lawfulness of processing based on consent before withdrawal.
The essential preference cookies are used only to remember and apply requested privacy choices. Technical processing necessary to deliver the website, protect it from abuse and maintain it relies on legitimate interests in operating a secure cultural information service, subject to applicable law and rights. Where personal data are processed before effective anonymisation, the relevant data-protection requirements continue to apply.
Correspondence and relevant published professional event information rely on our legitimate interests in operating a useful cultural information service, subject to rights and applicable law. Processing required by law relies on that obligation. Effectively anonymous figures are used as statistical information; rendering personal data anonymous is itself processing subject to applicable requirements.
Providing correspondence is voluntary. Technical connection information is generated when resources are requested. Levels 1 and 2 do not create personalised-advertising profiles, follow people across websites or make automated decisions with legal or similarly significant effects. The separate detailed level is not covered by this notice. It would need an updated description and the applicable review, safeguards and consent before activation.
8. Access, disclosure and international processing
Access to information we hold is limited to the operator, authorised administrators and technical providers who need access to supply their services. We do not sell visitor personal data or send the Observatory counter dataset to an external audience-measurement company. Only figures that have been aggregated and made non-identifying may be shared for the research and impact-reporting purposes described above. Information may also be disclosed where legally required or necessary to address abuse or legal claims.
France Regional is operated from the United States, and its main hosting server is in Massachusetts. Cloudflare and other technical providers may process browser requests in additional countries through their infrastructure. The storage country of Hostinger backups has not been confirmed.
Hostinger and Cloudflare publish data-processing terms that include European Commission standard contractual clauses where applicable to restricted international transfers. CARTO’s Basemaps Terms also describe its international-processing arrangements. The arrangements that apply depend on the service and processing concerned. You may contact us for further information or copies of applicable safeguards, subject to necessary redactions.
Hostinger Data Processing Addendum
Cloudflare Data Processing Addendum
9. Retention and backups
For the Observatory 0.9.0 level 1 and 2 configuration described in this notice, its daily and site-wide hourly audience counters, public-content action totals, separate contextual daily totals and cultural catalogue observations use a 365-day rolling retention period. The same period applies to the hourly and daily audience counters. The plugin supports configuration between 30 and 730 days; a change to the applicable period will be reflected in this policy. Referral-source and browser totals contain no separate visitor-level retention because no visitor record is created.
Scheduled daily maintenance removes expired rows in bounded batches, with continuation where needed. Execution depends on WordPress scheduled tasks and the plugin being active; it is not guaranteed at an exact anniversary time. Delays can extend the actual presence of rows until completed maintenance. Deactivating code does not itself delete the database or continue its scheduled deletion. Documents containing only non-identifying aggregate figures may be kept as research or project records.
The exclusion and optional-context preference cookies have the separate 180-day periods described above. Ordinary visits do not renew them.
Operational totals per minute cover the website as a whole: reserved collection slots, successfully stored counter increments, requests blocked by the collection quota and failed storage operations. They contain no publication/event identifier, destination domain, country, referral source, browser, IP address or visitor identifier. They help diagnose overall collection volume and capacity. Daily maintenance removes operational entries more than one hour old; scheduling delays can extend their presence until that maintenance completes.
Correspondence is kept while needed to resolve the request and necessary follow-up. Relevant records may be retained longer for a specific legal duty or to establish, exercise or defend legal claims. Published event information and separate catalogue copies are kept while needed to maintain the catalogue or cultural documentation; obsolete information is reviewed for correction or removal.
Hostinger’s automatic daily backups are retained for 7 days and weekly backups for 6 weeks, according to its documentation. They are stored separately from the main hosting storage. Their storage country has not been confirmed for this account.
Backups may contain earlier website/database versions, including data removed from the active database. Such copies remain until the applicable backup rotation removes them. Restoring a backup does not change our retention obligations.
We do not keep a separate manual archive of visitor-measurement data. Manual catalogue copies contain published event information. The 7-day and 6-week periods apply to automatic Hostinger backups, not a separate manual hosting backup. A distinct manual-hosting-backup retention/deletion period has not been confirmed; those automatic periods must not be treated as a verified manual-backup schedule. Hostinger’s HTTP/error/security log retention remains unconfirmed as explained in section 4.
Hostinger backup documentation
10. External websites
Official event links and other external links take you to independent websites. Those websites may receive technical information and use their own cookies or measurement tools after you open them. Their policies govern that processing. France Regional’s official-link counters measure only the recorded click on our website and do not observe your subsequent activity on the destination site. Optional contextual statistics do not add tracking on those external websites.
11. Your privacy rights
Depending on applicable law, you may request access, correction, deletion, restriction or portability of personal data we hold, and object to legitimate-interest processing. Through Privacy preferences you can refuse or withdraw optional contextual acceptance and separately exclude this browser from Observatory measurement without identifying yourself. These are distinct controls; accepting context does not erase an existing full exclusion. Where needed for a request about personal information we hold, we may ask for proportionate verification information.
Basic and contextual totals contain no visitor identifier, so we cannot retrieve or erase a particular person’s contribution. This does not restrict requests about other personal information, such as correspondence or published professional contact details.
Send requests to info@franceregional.com. Where the GDPR applies, we normally respond within one month; a permitted extension will be explained within that period. You may complain to the competent data protection authority. In France, information about complaints is available from the CNIL.
12. Changes to this policy
We update this notice when services or data practices change and identify the revision above. Updating this policy does not itself activate the plugin or authorise processing that requires consent. We reassess material changes to the purpose, data, integrations or report safeguards; changed contextual notices/configurations require a new optional acceptance. Existing global refusals are preserved rather than converted into permission. For questions, contact info@franceregional.com.