Privacy policy

Lovycards is a deck of question cards for two people sharing one phone. It is built so that what you say to each other stays between you. This page says, in plain words, what the app and this website do with data.

The short version

• No account. No sign-up, no profile, no syncing between phones.
• Your answers are never stored. Not in your phone’s storage, and not anywhere else.
• Anonymous usage and crash reports are sent only if you say yes, and you can switch them off in Settings at any time.
• No ads, no advertising ID, no location, no microphone, no recording.
• Payments are Google Play’s. We never see your card or bank details.
• This website sets no cookies and runs no analytics.

Who is responsible

Lovycards is made by Michael Zappala’ (Liotrodev), Płochocińska 100, 03-044 Warszawa, Poland. For anything about privacy, write to [email protected].

The Lovycards app

What stays on your phone

Everything the app remembers is kept in its own private storage on your phone. It is left out of Android’s cloud backup and of phone-to-phone transfer, and it is deleted when you uninstall the app or clear its data.

• Your answers. Most cards are answered out loud, and the app does not listen: it never uses the microphone. On cards where you type a guess, make a choice or put a list in order, the app holds what you entered in memory, for the last 10 cards, while it is open, so that going back shows it again. It is never written to storage, and it is gone when the app closes.
• Your names. If you give them, they label whose turn it is. They are optional and never leave your phone.
• Your place and your settings. Which card each deck is on, which cards a free deck has shown today, the deck you picked as your free one, your Good card and Not for us marks, light or dark, sound and haptics, the daily question’s switch and time, and your answer about anonymous usage.
• Your favorite cards. With Premium, the cards you save with a card’s star, and when you saved each: which cards, never anything you said about them. They stay saved if Premium ends, and open again when it is back.
• Whether Premium is on. A yes or a no, as Google Play last answered. If you subscribed on this phone, also the time your paid weeks began, and whether you took a lower-price offer here. Never your Google account, an order number or a payment detail.

What the app sends if you agree

During setup the app asks, in these words:

Help make Lovycards better. Share anonymous usage with us: which cards you like or skip, how you use the app, and crash reports. Never your answers or names. You can change this in Settings.

There are two buttons, Share anonymous usage and No thanks, and neither is chosen for you. Nothing is sent before you answer. If you say no, nothing is sent at all: the analytics software is not even started.

If you say yes, the app sends events to PostHog, our analytics provider, on servers in the European Union. This is everything it sends:

• How the cards are used, never what was said. That a deck was opened, from which of the two shelves, and whether it is one of your free decks. That a card was shown, with its id, version, kind (such as a question or a riddle) and depth, and how many cards had been shown since the app was opened; that it was left, by Next, Back or Home, and after how many seconds. That a hint, an answer or both partners’ guesses were turned over, which hint it was, and how many hints were used before the answer. That a card was marked Good card or Not for us, or the mark was taken off, and after how many seconds. That a card was shared, or saved to or taken out of your favorite cards, and that your favorite cards were opened. That the day’s Let’s talk question was opened, and that its notification was tapped. That a free deck’s new cards for the day had run out.
• Setup. That it was finished, with the deck you picked, whether names were entered (never the names) and how many seconds it took; and how long after installing your first card was shown.
• Purchases and Premium. That the paywall was shown and why (a locked deck, the day’s free cards, or the favorites star or key), which deck it was opened from, whether a free trial was on offer, and how many plans Google Play returned, or that Google Play’s prices could not be fetched. Which plan was picked, by its length (weekly or yearly). That a purchase was started, and how it ended: bought, cancelled, waiting for payment, or failed, with Google Play’s error code. How many seconds the paywall was open when it was closed. What Restore purchases found. That Premium turned on or off. That Premium options was opened and what it offered, which choice was tapped, that Google Play’s subscription page was opened, and how a lower-price offer ended in Google Play. Never a price, an order number, a payment detail or your Google account, never a reason for leaving, and never whether you cancelled: that is Google Play’s to know.
• The rating request. That it was shown, and that Rate was tapped.
• Which app a card was shared to, as that app’s technical name (such as com.whatsapp), when you use Share. This shows that the app you picked is installed on your phone.
• When the app is installed, updated, opened and put in the background, with its version.
• About the app and the phone, with every event: the app’s version and build, the card catalogue’s version, whether it is a test build, the store it came from, whether Premium is on, and days since the app was installed; the phone’s make, model and hardware code name, whether it is an emulator, its Android version, screen size and density, language setting, and kind of connection (Wi-Fi, mobile data or Bluetooth); the technical description every request carries (its “user agent”); the analytics software’s name, version and its own working figures, such as how many events are waiting to be sent; and two random ids, one made for this installation and one for each session.
• Crash reports. The kind of error and where in the app’s code it happened. The error’s message is removed before it is sent, because a message could quote a card.

Each event is made of fixed labels, numbers and yes-or-no values, plus the id of a deck or a card, such as d_date or c0015, and the technical name of an app you shared to.

What is never sent, whatever you chose:

• Anything you typed, chose or ranked on a card. Your names. A card’s words.
• Your location, your time zone or your mobile carrier. The app also tells PostHog not to work out a place from your internet address.
• An advertising ID. Lovycards has no ads, and shares nothing with advertisers or data brokers.
• A recording of your screen or your taps.
• From the Spicy deck: which card you were on. An event from Spicy says the deck and never the card.

The random ids are not linked to your name, your email, your Google account or your purchases. We cannot tell whose phone they belong to. PostHog is set to discard your internet address, so it does not keep it.

Changing your mind. Settings has a switch, Share anonymous usage and crash reports. Turning it off stops everything at once: events still waiting on the phone are deleted unsent, and the installation’s random id is forgotten. If you turn it on again later, you start as a new anonymous installation.

Subscriptions and Google Play

Lovycards Premium is a subscription bought through Google Play. Google takes the payment under its own privacy policy; the app never sees your card or bank details. The app asks Google Play whether this Google account has an active subscription, whether it renews, and whether it is paused, and stores only whether Premium is on, the time your paid weeks began if you subscribed on this phone, and whether a lower-price offer was taken here.

As the app’s developer we see what Google Play reports to every developer: order numbers, what was bought and when, the price and the buyer’s country, and totals such as installs and ratings.

Google’s billing software inside the app also sends Google its own diagnostic data, and the review sheet Lovycards sometimes offers is Google Play’s own. Both fall under Google’s privacy policy.

The daily question

If you turn it on, one Let’s talk question a day arrives as a notification, at about 7 pm, or at another time you choose in Settings. It is made on your phone: there is no server and no push service behind it, and the time you chose is not sent anywhere. If you agreed to anonymous usage, the app reports that the day’s notification was tapped, and nothing else about the notification: not that it was sent, its time or your time zone.

Sharing a card

Share makes a picture of the card and hands it to your phone’s own share sheet. You choose where it goes. The picture carries the question as it is printed, never an answer, a name or a hint. The app keeps one such picture at a time, in its temporary files.

Emails you send us

Report a bug and Send feedback in Settings open your own email app with a draft addressed to [email protected]. You see it, and you send it yourself. The app adds one line, which you can delete: the app’s version, your Android version, your phone’s make and model, and the version of the card catalogue. We receive your email address and whatever you wrote, and use them only to reply and to fix what you reported. Cloudflare receives emails sent to [email protected] and forwards them to our mailbox. We keep them for up to two years after the conversation ends, then delete them.

Permissions

The app asks Android for two things: to show notifications, only when you turn the daily question on, and to be told when the phone has restarted, so that the daily question’s timer can be set again. Its internet access is used only by Google Play’s billing and, if you agreed, by PostHog.

This website

• No cookies, no analytics, no advertising, and no fonts or scripts loaded from other companies.
• Hosting. The site is served by Cloudflare, which handles the internet address and technical details of each request, as any web host must, to deliver the pages and to keep the site secure.
• The waiting list. If you leave your email address, it is stored with Kit (kit.com), our email service, together with the page you signed up on and the time. We use it to tell you when Lovycards launches and to send occasional Lovycards news, and for nothing else. Every email has an unsubscribe link, and you can also write to us to be removed. If you unsubscribe, Kit keeps the address marked as unsubscribed so that you are not emailed again; ask us and we delete it completely.

Why we are allowed to do this

Under the GDPR and the UK GDPR, we rely on:

• your consent for anonymous usage and crash reports, and for the waiting list. You can withdraw it at any time, as described above;
• our legitimate interest in answering the emails you send us and in keeping this website secure;
• your purchase, for telling the app whether Premium is on.

Who else handles data

We do not sell data, and we share it with no one else. Kit and Cloudflare are based in the United States. Transfers to them are covered by the EU–US Data Privacy Framework or the European Commission’s Standard Contractual Clauses, as set out in each provider’s data processing agreement.

How long it is kept

• On your phone: until you reset, clear or uninstall the app.
• Anonymous usage and crash reports: 14 days, then deleted.
• The waiting list: until you unsubscribe or ask us to remove you.

Your rights

Depending on where you live, you may have the right to see, correct, delete or receive a copy of the data we hold about you, to object to its use or have it restricted, and to withdraw consent. Write to [email protected].

One honest limit: anonymous usage is not tied to you, so we cannot find yours from your name or your email. Switching it off in Settings stops it and forgets the id on your phone.

You can also complain to a data protection authority. Lovycards is run from Poland, where the authority is the President of the Personal Data Protection Office (UODO); you can also complain in the country where you live.

Children

Lovycards is made for people aged 16 and over. We do not knowingly collect data from anyone younger.

Changes to this page

When the app or this page changes, we update the page and the date at its top.