1. Local calendar processing
CalendarMade does not require an account. Custom titles, logos and images are processed locally to create the preview and PDF and are not sent to ACFA.
- Calendar preferences, dates and periods saved in browser local storage.
- Uploaded logos and images saved in IndexedDB on the user’s device.
- Preferred language saved locally.
2. Consent and audience measurement
The Umami script hosted at monitoring.filippoceli.com is requested only after the audience measurement category is accepted. If it is refused, no request to that instance and no analytics funnel storage operation is made.
After consent, Umami records page views, web performance and functional events such as calendar loads and PDF exports. Data includes language, page path, referrer domain or category, sanitized UTM parameters, browser, operating system, device type, country and general calendar settings such as year, paper size and orientation.
As with any web request, the instance receives the IP address and user agent needed for communication. The current Umami configuration uses no cookie, does not track a person across websites and enables neither session recording nor heatmaps. Custom titles, logos and images are not sent.
Consent is the basis for this optional processing. It can be withdrawn at any time through “Manage cookies” in every page footer.
3. Cookies, local storage and on-device duration
CalendarMade currently sets no advertising cookie. Refusal is stored for the same period as acceptance.
- calendarmade-consent-v1 (local storage): stores acceptance or refusal for six months and is necessary to remember the choice.
- calendarmade-language and calendarmade-config (local storage): requested language and settings, kept until replaced or site data is cleared.
- calendarmade-custom-dates and calendarmade-custom-periods (local storage): calendar content, kept until changed or deleted by the user.
- calendarmade-assets (IndexedDB): local logos and images, kept until removed or site data is cleared.
- calendarmade-analytics-* and funnel data (session storage): created only after consent and removed at the end of the session or when consent is withdrawn.
4. External data services
The browser contacts OpenHolidays API when the studio opens and when a country or region is changed. That service receives the technical information needed for a web request, including the IP address and user agent. Links to official sources lead to third-party sites governed by their own policies.
5. Advertising
No advertising network, script, placement or cookie is currently enabled on CalendarMade.
Before any future activation, this policy and the choice interface must identify the relevant partners and purposes. A certified consent management platform compatible with the current TCF must be used where the advertising provider requires it. CalendarMade does not ask for consent to future advertising today.
6. Recipients and retention
ACFA uses the audience measurement data in its self-hosted Umami instance. Its infrastructure providers may act as technical processors. CalendarMade does not sell this data or share it with an advertising network.
The consent choice is stored for six months. Audience measurement information must be purged from the Umami instance within twenty-five months at the latest, with this period reviewed regularly. Functional local data remains under the user’s control on their device.
The infrastructure providers used by monitoring.filippoceli.com and any relevant transfer safeguards must be kept current in ACFA’s processing records.
7. Controller and rights
The data controller is SAS ACFA, 273 avenue des Caroubiers, 06230 Villefranche-sur-Mer, France.
For access, correction, deletion, objection or restriction requests, contact hello@calendarmade.com. You may also contact the French data protection authority (CNIL).
Last updated: 19 August 2026.