Privacy Policy

Last updated: January 20, 2015

Our privacy policy for Lily is quite simple: You data is yours, and it stays yours. We will not look at your data, nor will we share your data with anyone — not for love or money.
All of your data resides on your device only, and in any backups you might have. There are no backups on any of our servers, nor do we have the technical ability to access the data on your device remotely.

The reason behind this very strict policy is simple as well: We are in the business of developing and providing Lily, not of collecting and selling your data. (This is why we take a little money if you want to make use of Lily's full set of features. We need to pay our bills somehow!)

Please keep in mind, however, that we will have to change details of this privacy policy at some point in the future, in case we ever want to offer data synchronization between devices, or a custom backup solution. But even then, the basic principle will stay the same: We do not want to, and never will, sell or share your data with anyone.
You should always be able to find the most recent version of Lily's privacy policy here.

There are two exceptions to the above-mentioned rules, though:

  • Support Emails

    The first exception is when you send us a support request from within Lily. In that case, Lily will create an email for you and attach the information you can find towards the end of that email. We attach this information for you because it can often help us with answering your support requests faster and more accurately. You are, however, free to remove any of this information before you send the email. Nothing else will be sent, there is no other information hidden within or attached to this email that your device wouldn't attach to any other email you send.

    In case your support request is in regard to an evaluation issue with Lily, we might ask you to create a PDF document of the cycles regarding your question and send these documents to us. Please make sure that you exclude all information that you do not want us to see when you create these documents. We do keep an archive of your support emails, but all information contained in them is covered by the same policy that is mentioned above: We will not share your data with anyone.

  • App Analytics

    The second exception is that we do collect a small set of data for our analytics. This enables us to make more informed decisions about Lily's future: When can we drop support for old iOS versions or old devices? Which languages should we support? Do users abandon Lily quickly, or do they track and evaluate larger numbers of cycles and days? Are there any pirated versions of Lily in use?

    This data set will be sent from your device to our servers automatically when you start Lily (or an update of Lily) for the first time, when you make a purchase from within Lily, when you restore a purchase, after you updated your iOS operating system, and when you start Lily for the first time after moving your data to a new device.

    At no point will there be any personal information transmitted or stored, nor will there be any way for us to identify you or your device. There is no unique identifier and absolutely none of the data you track with Lily.

    Here is a complete list of what kind of information will be saved on our servers, including an example of what that data looks like:

    • Lily's currently installed version (for example '3.0')
    • The version of Lily that you originally bought (for example '2.8')
    • The type of your iOS device (for example 'iPhone7,2' in case of an iPhone 6)
    • The version of iOS that is installed on your device (for example '8.1')
    • Your device's system language (for example 'en' for English)
    • The total number of cycles you charted up to that point (for example '5')
    • The total number of days associated with these cycles (for example '175')
    • The number of confirmed pregnancy cycles (for example '0')
    • If you have access to Lily's full set of features (for example '1' for Yes)
    • The cycle evaluation method you are using (for example 'nfp' for AG NFP)
    • In case we should ever offer more than one in-app purchase: IDs for any purchases you made (for example '1' for the full set of Lily's features)
    • If your Lily's AppStore receipt could be validated (for example '1' for Yes)
    • The AppStore receipt validation result code (for example '1' for 'valid')
  • Starting with Version 3.2, Lily also utilizes Facebook Analytics. This enables us to track if and when one of the ads we run on Facebook leads to a new download and installation of Lily. None of your Facebook related data will be transmitted and we won't have access to any of your Facebook-related data – not even the name of your account. All we can see is that someone installed and started Lily via one of our Facebook ads.

    Starting with Version 3.5, we also began using Google Analytics. Doing so enables us to collect statistics about the screens that were opened and in which order, the average time spent on these screens, average app startup times, and events like confirmed pregnancies and in-app purchases. On top of that, we track how much time is being spent with the app in total, at what time of day it is usually being used, and where (down to the city, but not further).
    Just as with Facebook Analytics, no user-specific or identifying information will be sent, stored, or tracked.
    We collect this data to see which features of Lily are used more often, and which are used less, to help us decide where to focus Lily's future development, as well as for quality control.


Change language: en | de

We do not guarantee the method of birth control or pregnancy achievement as described on this web site.

Our Apps for iOS

Our Apps for Your Mac

Proudly Made in California
2010 - 2016, by Whimsical Inc.