Lantern Lane

Last updated 10 October 2026

Privacy notice.

This notice explains how Lantern Lane handles information when you play, sign in, make purchases, contact us or visit this website.

Who looks after your information

Lantern Lane is operated by Alexander Dagas, Ireland. Contact lanternlaneinfo@gmail.com for privacy questions, access requests or account help.

Accounts and saved homes

We use Firebase Authentication for Apple, Google and email/password sign-in. Depending on your sign-in choice, it processes your email address (including an Apple relay address), provider account identifier, authentication credentials and an internal user ID. The app does not receive your Apple or Google password. Email/password credentials are handled by Firebase Authentication. Sign-in providers may also process account profile and contact information, such as your name or sign-in phone number, plus IP address, approximate location and device/SDK information for authentication, security and SDK operation. Lantern Lane does not ask you to enter a phone number to play.

Your home layout, owned items, colours, progress and preferences are saved on your device and in Cloud Firestore. Access is restricted to your account. Cloudflare runs the game API and wallet database, which use your internal account ID, inventory, reward timestamps and currency balances to deliver the game securely. We use this information to provide the service you request and protect accounts, rewards and purchases against abuse.

Friends use a dedicated shareable code. You can choose a unique public username that friends can see. Friend requests require acceptance. For exchanges, the server reserves your selected piece and transfers both gifts atomically when a match is found; daily limits are recorded against your account. Your account email and private home layout are not shared with other players.

Purchases

Apple handles checkout and payment details. We receive purchase identifiers, product, environment, account-binding and refund information to verify and deliver your purchase. RevenueCat processes account identifiers and purchase information for purchase records and revenue reporting. Cloudflare verifies Apple’s signed purchase data and stores the game’s authoritative wallet. We do not receive your full payment-card details.

Sandbox purchases use a separate test wallet and home. They do not provide currency in the production game.

Optional ads

Ads are optional and are requested when you choose to watch for a personal cosmetic or home-cleaning reward. Google AdMob and its advertising partners may process IP address, device and app information, approximate location inferred from IP, and ad interactions to deliver, measure and secure advertising. Our app requests non-personalised ads and disables publisher first-party identifiers. Non-personalised ads can still use device storage and data for measurement, fraud prevention and frequency control.

Where required, Google’s consent form appears before an ad can be requested. You can revisit available choices through Settings → About → Ad privacy. Declining an ad or optional consent does not prevent ordinary gameplay. Google sends the game server a signed completion event and an opaque reward-attempt ID so it can save verified progress toward your chosen reward without exposing your home layout.

Gameplay analytics and optional crash reports

Usage analytics starts automatically after you sign in to a verified account. You can turn it off in Settings. Crash reporting starts off and has its own switch. Each account has separate choices on each device. Google Analytics for Firebase receives an opaque account-linked analytics ID, app-instance identifiers, device/app information, screen visits and foreground time, tab changes, scroll depth, control actions and pointer hover duration, item selection and placement previews, item and room identifiers, arrangement, storage and undo actions, cleaning, building, gifts, shop activity, optional-ad category, progress, impressions and reported ad revenue. This allows us to understand a player’s journey across sessions and devices. If you enable crash reports, Firebase Crashlytics receives crash details, app/device information and installation identifiers. We do not include your email, passwords, friend codes, search text or written notes in analytics. We send game action metadata, not screenshots or recordings of your screen.

These optional tools help us understand which features work and find crashes. Disabling them stops future collection controlled by those settings; account deletion resets analytics on that installation and discards unsent crash reports. The backend also keeps aggregate operational counters for purchases and economy actions without player or device identifiers.

Optional measurement of our Facebook and Instagram ads

In versions with Meta ad measurement, sharing starts off. After signing in, you can choose whether to allow it; keeping it off does not affect ordinary gameplay or rewards. We ask for Apple’s tracking permission before activating Meta’s SDK. Both your account’s choice on this device and Apple’s permission must allow sharing. You can withdraw your choice in Settings → About → Your account → Share ad measurement with Meta, or change tracking permission in iPhone Settings. This choice is separate from Firebase usage analytics and crash reporting.

If you allow sharing, Meta receives install and app-open/session events, including session timing, together with app/version, device/operating-system information, SDK-generated app-instance/device identifiers and technical request information such as IP address. Meta may use these events with information from its services to measure advertising effectiveness. We restrict event use to analytics and conversion measurement, disable advertising-ID collection, automatic purchase logging, automatic gameplay-event logging and Meta SDK crash/error reporting, and do not send game account IDs, emails, passwords, home layouts, purchase amounts or gameplay actions to Meta. SDK setup requires technical requests to Meta. Withdrawing consent stops future app-controlled event logging and flushing; requests already started cannot be recalled. Previously shared information remains subject to Meta’s retention and privacy controls.

Apple’s SKAdNetwork can separately report an install through an aggregated, privacy-preserving postback without identifying a player or device. This does not activate Meta’s SDK and does not require sharing permission in the game. Small audiences may not produce reportable results. Development and simulator builds do not send Meta acquisition events.

Support and this website

If you contact us, we process your email address and the information you choose to send to answer your request. Avoid sending passwords or payment-card details. This website uses Firebase Hosting and contains no analytics scripts, advertising cookies or embedded social widgets. The hosting provider may process technical request information such as IP addresses for delivery and security.

Providers and international processing

We use Apple, Google/Firebase, RevenueCat, Cloudflare and, only when you allow ad measurement, Meta for the purposes described above. These providers may process data outside Ireland and the European Economic Area under their applicable transfer safeguards. Our Firestore database is hosted in Belgium; this does not mean every provider processes all data only in Europe.

Read more in Firebase’s privacy information, Google’s privacy policy, RevenueCat’s privacy policy, Cloudflare’s privacy policy, Apple’s privacy policy and Meta’s privacy policy.

Retention, deletion and your rights

Account and home information remains while your account is active. You can delete your account in the app or contact us if you cannot sign in. Minimal deletion markers and pseudonymous transaction records may be retained when necessary to prevent repeated fulfilment, protect against fraud or comply with legal obligations. Support correspondence is retained only as needed to resolve the request and related obligations. Providers’ security, backup and optional analytics retention is governed by their applicable policies.

Where applicable, you may request access, correction, deletion, restriction or portability of your personal data, or object to processing based on legitimate interests. You can turn off usage analytics and optional crash reports in Settings, and withdraw advertising consent through the available privacy controls. Contact us to exercise these rights; we may need to verify your identity. You can also raise concerns with Ireland’s Data Protection Commission or your local supervisory authority.

Audience and updates

Lantern Lane is intended for a general audience and is not directed at children. If you believe a child has provided personal information without the consent required in their country, contact us so we can investigate. We may update this notice when the service changes; this page shows the latest update date.