Your diary is stored on your device and shared locally with SipLog widgets. SipLog does not require an account or upload your diary to a diary backend. The app does use online services for usage analytics, crash reporting, purchases, and notifications.
Who we are
SipLog is provided by Lighbulb Apps. For privacy questions or requests, contact support@autotap.app. This policy covers the SipLog iOS app and this website.
Your diary and preferences
Drink entries, dates, quantities, favorites, notes, expenses, spending baselines, and preferences are stored locally on your device. The app and its widgets use a shared on-device container. We do not send diary contents to Firebase, RevenueCat, or PushCore through our app integrations.
SipLog does not provide an account-based diary sync service. Your operating system’s backup and device-transfer features may include app data, depending on your Apple settings. Information displayed in widgets may be visible to someone who can see your screen.
Usage analytics and diagnostics
SipLog uses Google Firebase Analytics to understand feature use and Firebase Crashlytics to identify reliability problems. The production app enables these services. They can process installation identifiers, app and device information, usage events, and crash diagnostics.
Our custom events describe actions such as opening a screen, saving an entry, or opening a paywall. They do not include diary dates, drink names, quantities, notes, expenses, favorite identifiers, or exported images. Operational errors are reported as fixed categories rather than raw diary-related error messages.
The app disables advertising-related consent and does not supply a custom user ID to Firebase. The current app has no in-app analytics opt-out control. Learn about Google’s handling of service data in Firebase privacy information and Google’s privacy policy.
Purchases
Apple processes payments. SipLog uses RevenueCat to validate purchases, restore access, and determine whether Lifetime Pro is unlocked. RevenueCat processes an app user identifier and purchase-related information, such as receipts and entitlement status, along with technical information needed to operate the service. You do not need to create a SipLog account. We do not receive your full payment-card details through the app. See RevenueCat’s privacy policy and Apple’s privacy information.
Notifications and reminders
SipLog uses PushCore and Apple Push Notification service for remote notifications. PushCore can register an app installation when the app launches, before notification permission is requested. Registration includes installation and device information, app and operating-system versions, language, locale, time zone, and notification authorization status. An Apple push token is registered when available. Network services also receive connection information such as an IP address.
SipLog requests permission to display notifications only after you choose to enable them. The daily reminder is scheduled locally. Remote notifications may download an image from the media host identified in the notification. SipLog does not attach your diary contents to its PushCore registration.
You can change notification permission in iOS Settings and disable the daily reminder in SipLog Settings. Turning off notification delivery does not itself delete an existing installation record or stop all service registration.
Exports, sharing, and support
Exports and recap images leave the app when you choose a destination in the system share sheet. Basic exports can contain notes and expenses. Recap calendars reveal consumption patterns even if you omit the drink total. The selected service’s privacy practices apply after sharing.
If you email support, we receive your email address and the information you choose to send. Include only what is needed to resolve your question; diary exports and screenshots are not required for a general support request.
This website
This site contains no added analytics scripts, advertising, contact forms, or tracking cookies. GitHub Pages hosts it and may process technical request information to deliver and protect the site. See the GitHub privacy statement. Email links open your email application.
Retention and your choices
Local entries remain until you delete them or remove the app’s data. Export copies, device backups, and service records are separate; uninstalling SipLog does not necessarily remove those copies. We cannot retrieve or remotely delete a diary held only on your device.
Service data is retained under the relevant provider’s settings and retention practices. Support correspondence is kept as needed to handle your request and related obligations. Contact us to request access, correction, or deletion of information we hold. Depending on where you live, you may also have rights to object, restrict processing, receive a copy, or complain to your local data-protection authority. We may need information to verify and locate a request, but do not send your diary unless it is necessary.
Security and international processing
SipLog uses iOS storage protections and offers optional device-authentication app lock. No storage or transmission method guarantees absolute security. Our service providers may process information in countries other than yours; their privacy information describes their practices and applicable safeguards.
Children and changes
SipLog is intended for adults and is not directed to children. Contact us if you believe a child has provided personal information to us. We may update this policy as the app or its services change. The date on this page identifies the latest revision.