Privacy policy
In short
- The app shows a public calendar on a Wix site. It has no database and keeps no record of visitors or of sites.
- It sets no cookies and contains no analytics, advertising or tracking code.
- Where the site's consent settings permit functional storage, the visitor's browser keeps a copy of the public calendar so the page loads faster next time. That copy holds nothing about the visitor.
- The calendar's feed address is part of the page's HTML, and the whole feed is sent to each visitor's browser, so anyone who visits the page can read both. Use a calendar you mean to be public.
- Payments are handled by Wix. We never see card or bank details.
1. Who we are
The app is published by Lanternside Labs, the trading name of Benoit LE GUEN, an individual developer based in France ("we", "us"). Postal address: 132 Allée rouz, 29620 Plouégat-Guérand, France. Contact for anything in this policy: apps@fastingpioneer.com.
We have not appointed a data protection officer, because the law does not require one for an operation of this kind.
2. Who this policy is about
- Site owners: people who install the app on their Wix site and use its settings.
- Site visitors: people who view a page that contains the widget.
- People named in a calendar: anyone whose name or details appear in the events of a calendar that a site owner chose to show.
3. What happens when a visitor views the widget
The request to the app's server
The widget asks the app's server for the calendar. The server is a small piece of our code that runs on Wix's infrastructure. The request contains:
- the feed addresses the site owner configured (they are already in the page). They are sent as part of the request's address, so they appear wherever Wix records the addresses of requests;
- an access token that Wix's own software attaches, which tells Wix which site the request belongs to; and
- the standard headers every browser request carries, such as the browser type, the language and the address of the site or page the request came from.
From such a request our code reads the request method and the feed addresses, and it asks Wix for the app's record for the site to learn whether the site is on the free or the paid plan. It does not read the visitor's IP address, cookies, browser details, the other headers or any identifier, and it does not read the token's contents for visitor requests. It stores nothing about the request.
The request is repeated. While a page with the widget stays open and its tab is visible, the widget checks about every five minutes whether its copy of the calendar is due for renewal and, if so, asks the server again. On a page view that is served from the copy in the browser (see below), the widget instead sends a short request that only asks which plan the site is on; it contains the access token and the standard headers, and no feed address.
Like any web request, these pass through Wix's infrastructure, which sees network data such as the IP address. Wix handles that data under its own privacy policy; we have no access to it.
The request to the calendar's server
The app's server then downloads the calendar from the address the site owner entered. That request comes from the server, not from the visitor's browser. It carries the feed address and a fixed description of the app ("CalendarFeedWidget/1.0"), and nothing about the visitor. The calendar's server therefore does not learn who is viewing the site.
What the visitor's browser stores
The widget can keep a copy of the calendar in the browser's local storage for the site, so a later page view does not have to wait for a download. It does this only when the site's consent settings, read through Wix's consent tools, report that functional storage is permitted for this visitor. On a site with a consent banner that is the visitor's own choice. On a site without one, or before the visitor has chosen, Wix reports the site owner's default setting; the widget cannot tell a default from a choice, and the site owner is responsible for asking visitors where the law requires it.
If the answer is no, or cannot be read, no calendar copy is kept and the widget works from memory for that page view. Whatever the answer, the widget does three small things with the site's local storage: to find out whether storage works at all it writes one test entry (cfw:2:probe, containing the character "1") and removes it at once; it may look through the names, not the contents, of the entries there to find its own; and it may delete entries it stored earlier.
What is stored, under names beginning with cfw::
- for each calendar: its feed address, the calendar's complete text as published (see section 5), and the time it was downloaded;
- a small index: the size and time of each stored calendar, and a yes/no marker for whether the site was last seen on the paid plan. The marker only affects how the widget loads (whether it waits a moment before drawing, how it groups its requests and which stored calendars it looks up first); it never unlocks anything.
None of this describes the visitor. No identifier is created, nothing is read back by our server, and the stored copy is never sent anywhere. All calendars together are limited to about 1.5 million characters.
When functional storage is refused, the widget deletes everything it stored when it sees the refusal:
- at once, when the site reports the change while a page with the widget is open;
- when a page with the widget loads and the consent settings, as first read, say no;
- when the widget reads the settings again, which it does about every 30 seconds while it is working, and they have changed from yes to no.
There is one case in which earlier copies are left in place: if the consent settings cannot be read when the page loads and report a refusal only later, the copies are not used but are not deleted on that visit either. If the consent settings cannot be read at all, existing copies are not used; the widget may still delete them. Visitors can remove everything at any time by clearing the site's data in their browser.
Fonts
If the site owner chooses a font for the widget, the widget loads it through Wix's font service, in the same way the rest of the Wix site loads its fonts. The visitor's browser then requests the font files from the servers Wix names. We do not choose or operate those servers.
Links a visitor may click (paid plan)
- "Download .ics file" creates the file inside the browser. No request is sent.
- "Subscribe" is a link to the calendar's own feed address. If a visitor follows it, their calendar program contacts the calendar's server directly, and that server sees the visitor's IP address like any website would. How the calendar program connects is up to that program.
Events can also contain links written by whoever maintains the calendar. Following one leads to that third-party site.
What the widget does not do
It sets no cookies. It does not use analytics, advertising, fingerprinting or social media code. It does not build profiles and makes no automated decisions about anyone. It reads the browser's language and time zone only to format dates on the page; they are not sent anywhere by the widget.
4. What happens when a site owner uses the app
- Settings. Calendar addresses, names, colours and display options are saved by Wix as part of the site, as properties of the widget. The settings panel also saves a marker with the plan last confirmed and the time (for example
pro:1763560000000), used to refresh the widget after an upgrade or a cancellation. Like all widget settings, the marker is part of the page's HTML and can be read by visitors. We do not hold a copy of any setting. - Plan check. Each time the settings panel is opened or its window regains focus, and when you press "Check again", the app's server reads two things from the access token Wix attaches: the type of caller (so that only the site's owner side can use the owner functions) and the app instance ID, an identifier Wix assigns to this app on this site. It then asks Wix for the app's record for the site and uses these fields only: whether the plan is free, the plan name, the billing cycle, the app instance ID, whether a free trial is available, running or over, and the date a trial ends. These are returned to the settings panel together with the type of caller. Wix's answer contains other details about the site; our code does not keep, log or pass them on. The app does not ask for the owner's email address. The same record is looked up, for the plan only, on each visitor request described in section 3.
- "Test this feed". The server downloads the one address being tested and returns the result, or the reason it failed, to the settings panel.
- Upgrade. The Upgrade button opens Wix's own checkout page. The link contains the app's ID and the app instance ID so that Wix knows which site is upgrading. Payment details, invoices and tax are handled between the site owner and Wix.
- Support. If you write to us, we receive your email address and whatever you include in the message, and use them to answer you.
5. Calendar content
A calendar can contain personal data, for example the name of a speaker, an organiser or a venue. The app passes the calendar's text from the calendar's server to visitors' browsers, where it is turned into the view on the page. Only calendars that their owner has made publicly readable can be loaded; the app has no way to sign in to a calendar.
The complete feed, as the calendar service publishes it, is sent to the visitor's browser and, where storage is permitted, kept there. It can be read with the browser's tools, including details the widget does not display: for example past events, notes, and the email addresses of organisers or attendees if the calendar service includes them in its public feed.
The site owner decides which calendar to show and is responsible for having the right to publish what is in it.
6. Feed addresses are visible
The widget's settings, including each feed address, are part of the page's HTML. Anyone who views the page can read them with their browser's tools, and with the paid plan's "Subscribe" link the address is shown on purpose. Feed addresses are also sent in the address of the widget's requests (section 3).
Some calendar services offer a "secret" or private feed address that gives access to a calendar that is otherwise not public. Do not use such an address in the widget unless you accept that visitors can find it and read the whole calendar with it. The settings panel warns about this where it can recognise such an address, but it cannot recognise every service's format.
7. What the app's server keeps
- No database. The app has no database, no file storage and no list of sites or visitors.
- Memory. While a server instance is running, it holds downloaded calendars in memory, keyed by feed address, so that it need not download the same calendar for every visitor. A copy is held for up to about 24 hours after it was downloaded. It is reused without asking the calendar's server for 5 minutes; after that it is served only if the calendar's server cannot be reached, and it is dropped at once if that server says the calendar is gone or no longer public. The memory is cleared whenever Wix stops or restarts the instance, which we do not control.
- Error lines. If Wix's token or the app's record for a site cannot be read, the server writes one line to the log that Wix provides for the app. This can happen on visitor requests as well as owner requests. The line contains a fixed text of ours and the error message produced by Wix's software. We do not add the request, the feed address or any identifier ourselves, but we do not control the wording of Wix's message and cannot rule out that it contains a technical identifier.
8. Who is responsible for what
- The site owner is the controller for their website: for choosing to show a calendar, for its content, and for informing their visitors and collecting consent through their site's consent settings.
- We act as a processor for the site owner where the app handles visitor requests and calendar content on the owner's behalf. The terms that govern this are in section 9 of our Terms of use.
- We are a controller for the limited data about site owners that we use for our own purposes: the plan and app instance information described in section 4, and support correspondence.
- Wix hosts the website and the widget's settings, provides the consent tools and the infrastructure the app's server code runs on, and collects payment for the paid plan. For its own platform, accounts and billing Wix is a controller in its own right, under its own privacy policy. Under Wix's agreement with app developers, Wix and we each act as independent controllers of site owners' personal data. For visitor data that passes through its infrastructure, Wix acts as the site owner's processor under Wix's data processing addendum with the site owner.
- The calendar service a site owner uses is chosen by the owner and acts under its own terms. We have no relationship with it.
9. Purposes and legal bases
| What we do | Legal basis (GDPR) |
|---|---|
| Provide the app to a site owner: load calendars, check the plan, unlock paid features | Performance of our contract with the site owner, Art. 6(1)(b). Where the site owner is an organisation, our legitimate interest in providing the app to it, Art. 6(1)(f). |
| Restrict owner functions to the site owner, limit what addresses the server will fetch, write error lines | Our legitimate interest in running the app securely and finding faults, Art. 6(1)(f) |
| Answer support requests | Performance of a contract or steps before one, Art. 6(1)(b); otherwise our legitimate interest in answering people who write to us, Art. 6(1)(f) |
| Answer requests to exercise data protection rights; keep records the law requires | Legal obligation, Art. 6(1)(c) |
| Keep a calendar copy in a visitor's browser | The site's consent setting for functional storage, as set by the site owner and, where the site has a consent banner, chosen by the visitor. We act for the site owner here; the owner determines the legal basis for showing the calendar and for the storage, and collects consent where the law requires it. |
We do not use anyone's data for marketing, and we do not sell or share data for advertising.
10. Who receives data
- Wix (Wix.com Ltd. and its group companies): the infrastructure the app's server code runs on, hosting of the widget's settings, the consent tools, the font service, the app record for each site, and billing.
- The calendar's server, as chosen by the site owner: receives the request for the feed described in section 3.
- Our email provider, Hostinger International Ltd.: carries and stores support correspondence.
- The hosting provider of this website, Hostinger International Ltd.: see section 14.
We use no other service providers for the app, and we do not pass data to anyone else unless the law obliges us to.
11. Transfers outside the EU/EEA
Wix.com Ltd. is established in Israel, a country that the European Commission has found to provide adequate protection of personal data (Decision 2011/61/EU). Where Wix passes data on to countries without such a decision, it states that it uses the European Commission's standard contractual clauses or another safeguard the GDPR allows; see Wix's privacy policy and data processing addendum. We do not choose where Wix runs the app's server or stores a site's settings.
Our email provider and the hosting provider of this website process data in the European Union and the United Kingdom (Hostinger names the United Kingdom, the Netherlands, Lithuania and Cyprus), and Hostinger states that some of its servers are in other countries, such as the United States. For transfers outside the EU/EEA, Hostinger states that it uses the European Commission's standard contractual clauses (Art. 46 GDPR); see Hostinger's privacy policy and data processing addendum.
The calendar's server is wherever the calendar service chosen by the site owner operates it.
12. How long data is kept
| Data | Where | How long |
|---|---|---|
| Calendar copy and index | Visitor's browser | A copy older than 7 days is never shown and is deleted the next time the widget looks for that calendar. When the app's server reports that a calendar can no longer be loaded, its copy is dropped once it is more than 6 hours old. Copies of calendars that are no longer on the page remain until space is needed, storage is refused or the visitor clears the site's data. If the widget or the app is removed from the site, its code no longer runs, so the copies stay until the visitor clears the site's data. |
| Downloaded calendars | Memory of the app's server | Held for up to about 24 hours after download while the instance runs. Reused for 5 minutes; after that served only if the calendar's server cannot be reached. Gone when the instance stops. |
| Error lines | Wix's log for the app | As long as Wix keeps such logs. We do not control this period and keep no copies. |
| Plan and app instance information | Not stored by us | Read from Wix when needed and discarded after the request. The marker of the last confirmed plan is a widget setting (next row). |
| Widget settings | Wix, with the site | Until the site owner changes them, removes the widget or deletes the site. |
| Support emails | Our mailbox | Up to 24 months after the last message in a conversation, then deleted, unless a longer period is required by law. |
| Website server logs (IP address, browser details, time, page) | Hosting provider of this website | For the period Hostinger sets; it does not publish a fixed period. |
The app keeps no data of its own about a site, so we have nothing to delete when the app is removed from a site. Removing the app does not delete the copies in visitors' browsers or in the server's memory; those go as described in the table.
13. Your rights
Under the GDPR you have the right to ask for access to your personal data, to have it corrected or deleted, to have its use restricted, and to receive it in a portable form.
Right to object. Where we rely on legitimate interests (section 9: security, error lines, answering messages; section 14: website server logs), you may object at any time on grounds relating to your particular situation. We will then stop, unless we have compelling legitimate grounds to continue or need the data for legal claims.
Where processing is based on consent, you can withdraw consent at any time; this does not affect processing that took place before. For the browser copy, do this through the consent settings of the website you are visiting.
To use these rights, write to apps@fastingpioneer.com. We will confirm that we received your request and answer within 30 days, by the same channel you used to contact us. We may ask for information to confirm who you are. Please note how little we hold: we cannot identify a visitor of a site that uses the widget, because the app keeps nothing about visitors. If your request is about a calendar or a website that shows it, the right contact is the owner of that website or calendar; if you write to us, we will tell you so and help where we can.
You also have the right to complain to a data protection authority, in particular in the EU country where you live, where you work or where you think the law was broken. The authority responsible for us is the Commission nationale de l'informatique et des libertés (CNIL), https://www.cnil.fr.
Nobody is required to give us personal data. A site owner who does not want the plan check to run cannot use the app, because the check is how the app works.
14. This website
This website consists of static pages. It sets no cookies, loads nothing from other servers, and contains no analytics, fonts, scripts or embedded content from third parties. As with any website, the hosting provider's server processes the IP address and browser details of each request in order to deliver the page, and may keep them in server logs, for a period Hostinger sets and does not publish, for security and fault-finding (our legitimate interest, Art. 6(1)(f) GDPR).
15. Security
The app's own requests use encrypted connections (HTTPS). A visitor's calendar program that follows a "Subscribe" link makes its own connection, which we do not control. The app's server fetches only public https addresses, refuses addresses that are recognisably on private networks, and limits the size and number of downloads. Functions that reveal billing and trial details or the reason a feed failed are limited to the site owner's side. The most effective safeguard is that the app stores almost nothing.
16. Changes to this policy
If the app changes in a way that affects what this policy says, we will update this page and its effective date before the change takes effect. For a significant change we will also say so in the app's settings panel or its listing.
17. Contact
Benoit LE GUEN, trading as Lanternside Labs
132 Allée rouz, 29620 Plouégat-Guérand, France
apps@fastingpioneer.com
https://apps.fastingpioneer.com