Privacy Policy

Events Calendar Sync (formerly Synced Events Calendar), an app for Wix sites · Effective 7 September 2026 · Name updated 14 October 2026 · Event suggestions added 18 October 2026 · Operated by operix (contact: beobjoong@gmail.com)

1. What the app does

Events Calendar Sync adds a calendar widget to a Wix site. The site owner connects one or more calendars from the Wix dashboard: a public Google Calendar, any iCal/ICS address, or the site's own events. The app fetches the events of those calendars, keeps a copy in the site's own Wix CMS, and shows them to visitors in the widget.

2. Data we process

• Calendar addresses and settings. The Google Calendar id or iCal address entered by the site owner, together with a display name, color and on/off state, is stored in a collection inside that site's own Wix CMS ("Calendar Sources"). An iCal address may be a private (secret) address; it is stored only in the site's CMS and is never shown to visitors.
• Event data. Events fetched from a connected calendar (title, start and end time, location, description, recurrence) for a window of about one month back and twelve months ahead are stored in the site's Wix CMS ("Calendar Cache") and refreshed periodically. Whatever the calendar contains is shown to visitors of the site, so the site owner controls what is published by choosing which calendars to connect.
• Event suggestions. If the site owner turns on visitor suggestions (Pro plan), a visitor can send an event for the calendar: a title, the date and time, and optionally a location, a description and a link. The suggestion is stored in the site's own Wix CMS, marked as waiting, and is not shown to visitors. The site owner approves it (it then appears in the calendar like an event the owner created) or declines it (it is deleted). The form does not ask for a name, email or other contact details; whatever a visitor types is stored as written. To limit abuse, the backend counts suggestions per site and per address in server memory for up to ten minutes; the address is not written to any log or database.
• Sync status. For each connected calendar the app records when it was last fetched, how many events were found and any error message, so the site owner can see that the calendar is working.
• Site registration. To serve the widget to visitors, we keep a record of each site where the app is installed (the Wix site id and the app instance id, both technical identifiers issued by Wix). The same record also holds usage signals about the site: counts and times of clicks on app buttons (such as upgrade or review), the reason chosen when an offer is declined, when the app was first and last seen in the dashboard, editor and published site, the plan, the number of connected calendars, and the kind of error the widget last hit together with the browser family, whether the page was visible and a rough time bucket. This record contains no personal data.
• Visitor requests. When a visitor opens a page with the widget, their browser requests the event list from the app's backend. The backend applies a per-address rate limit and keeps the requesting address in server memory for up to one minute for that purpose only; it is not written to any log or database. No cookies are set by the app.
• Site owner contact details. Wix shares the site owner's account details needed to operate the app and billing (for example the site owner's email) under the permissions shown when the app is installed.

3. Data we do not process

The app does not read customer lists, orders, payments, members' private data or submissions of other forms on the site, does not ask for access to the site owner's Google account, and does not place tracking cookies for advertising.

4. Where data is stored

Calendar sources and cached events live in the site's own Wix CMS, under the site owner's control; the owner can delete them at any time, and Wix removes the app's collections when the app is uninstalled. The app's backend runs on Wix's hosting infrastructure. Short-lived copies of merged event lists (up to 30 seconds) exist only in server memory. Calendar feeds are fetched directly from the provider chosen by the site owner (for example Google), whose own privacy policy applies to that request.

5. Legal basis and retention

We process calendar and event data on the instructions of the site owner in order to display the calendars they chose to publish. Data is kept as long as the calendar stays connected; removing a calendar from the dashboard deletes its cached events, and uninstalling the app removes the app's collections from the site. Waiting suggestions are kept until the site owner approves or declines them and are removed with the app's collections when the app is uninstalled. The site registration record is deleted automatically when the app is uninstalled (Wix notifies the app of the removal), and on request.

6. Sharing

We do not sell or share data with third parties. Data is processed by Wix (as the platform hosting the site, the CMS and the app backend) under Wix's own terms and privacy policy, and calendar providers receive the fetch requests described above.

7. Your rights

Site visitors should contact the site owner about events shown on that site. Site owners can contact us at beobjoong@gmail.com to ask about the app's processing, request deletion of registration records, or raise a complaint. Where GDPR, UK GDPR or CCPA apply, you have the rights those laws provide, including access, correction and deletion.

8. Changes

We will update this page when the app's data handling changes and note the new effective date above.