Privacy Policy

ElNi Studio built Calendar Op.2 as a free, ad-supported app, provided as is. This Privacy Policy explains what information is collected when you use the app, how it is used, who it is shared with, and the choices you have. By using the app, you agree to the practices described here. Terms used here have the same meaning as in our Terms and Conditions unless otherwise defined.

Last updated: June 11, 2026

Your Calendar Data Stays on Your Device

Calendar Op.2 reads and writes your events through Apple’s Calendar (EventKit) framework. Your calendars and events remain on your device and, if you use iCloud, in your own iCloud account. They are never transmitted to, or stored on, ElNi Studio’s servers, and we have no access to them.

Information We Collect and How We Use It

To provide a free, ad-supported service and to keep the app stable, our third-party providers may collect the following categories of data. These categories match the privacy information shown on our App Store product page:

Device identifiers — the Advertising Identifier (IDFA, only when you allow tracking — see below), the Vendor Identifier (IDFV), and a Firebase installation ID — used for advertising, analytics, and (where permitted) tracking.
Approximate location — estimated from your IP address, not precise GPS — used for advertising and analytics.
Advertising data — such as the ads shown to you and your interactions with them — used for third-party advertising.
Product interaction and other usage data — such as which features are used — used for analytics.
Crash data, performance data, and other diagnostic data — used to diagnose problems and improve stability.

We do not ask for your name, email address, or precise location inside the app, and we do not sell your personal data.

Third-Party Services

The app uses the following third-party services, which may collect information as described above:

Google AdMob (Google Mobile Ads SDK) — serves advertising.
Firebase Analytics — measures app usage. This build uses the version of Firebase Analytics that does not collect the IDFA.
Firebase Crashlytics — reports crashes and stability issues.

For more on how Google handles data:

Identifiers, Tracking, and Consent

App Tracking Transparency (ATT). Before any tracking that uses the IDFA, iOS asks for your permission. If you do not allow tracking, the IDFA is not used and advertising is non-personalized. You can change this at any time in iOS Settings → Privacy & Security → Tracking.
Consent in the EEA, the UK, and Switzerland. In these regions we use Google’s User Messaging Platform (UMP) to obtain your consent before advertising and analytics data is collected. If you decline, analytics collection is stopped and ads are shown on a non-personalized basis.
You can review or withdraw your consent at any time in the app: Settings → Privacy → Privacy Settings (this option is shown in regions where consent applies).

Contact Form

When you reach out through our contact form, we collect the name, email address, and message you provide so that we can reply to you. To help us understand and resolve your issue, we also receive basic technical information about the device and browser you used — including your operating system and version, device model, browser, screen size, time zone, and browser user-agent string. This information is sent only to our support inbox and is used solely to respond to and diagnose your inquiry. We do not collect your IP address or location through the form, and we do not share this information with third parties.

Cookies and Similar Technologies

Our website does not use tracking cookies. Within the app, the third-party advertising and analytics services listed above may use device identifiers and similar technologies, subject to your consent and tracking choices.

Security

We value your trust in providing us your personal information, thus we are striving to use commercially acceptable means of protecting it. But remember that no method of transmission over the internet, or method of electronic storage, is 100% secure and reliable, and we cannot guarantee its absolute security.

Children’s Privacy

Calendar Op.2 is not directed to children. We do not knowingly collect personal data from children under 16 (or the minimum age required in your country) without appropriate consent.

Links to Other Sites

This service may contain links to other sites. If you click on a third-party link, you will be directed to that site. Note that these external sites are not operated by us. We strongly advise you to review the Privacy Policy of these websites. We have no control over, and assume no responsibility for, the content, privacy policies, or practices of any third-party sites or services.

Changes to This Privacy Policy

We may update our Privacy Policy from time to time. You are advised to review this page periodically for any changes. We will notify you of any changes by posting the new Privacy Policy on this page. These changes are effective immediately after they are posted.

Contact Us

If you have any questions or suggestions about our Privacy Policy, please contact us through our Help Center.

← Back to Help