Last reviewed October 14, 2026
Website operator and data controller
BedtimeBite, at www.bedtimebite.com, is independently operated by Sergej Sotlar, an individual established in Slovenia. Sergej Sotlar is the data controller for the personal data described here.
Contact
Sergej Sotlar
Country of establishment: Slovenia
Support and privacy requests: support@bedtimebite.com
This notice describes current processing. Processing-specific legal bases, retention schedules and some provider disclosures remain under owner review; it should not be treated as a complete, final Privacy Policy.
Sleep and dinner timing calculator
The calculator uses your wake time, desired sleep duration, optional dinner time and meal-size choice to estimate bedtime and dinner cutoffs. Your inputs and results stay in memory in this browser tab; they are not uploaded, synchronized to your account or saved across reloads. The default example shown before JavaScript loads contains no personal input. The timing score is a planning heuristic, not a medical or sleep-quality measurement.
Firebase Authentication and Firestore accounts
Accounts are currently available through Google Firebase Authentication. Firebase processes your email, user identifier and password credentials to provide signup, sign-in and password reset. BedtimeBite does not store readable passwords in Firestore.
Cloud Firestore stores your account email, creation timestamp and server-controlled plan state. Profiles include reserved subscription fields, but those fields do not mean a payment service is active. Client access is restricted to your own authenticated profile; subscription fields cannot be changed by the browser.
Functional browser storage and hosting
Firebase uses browser storage, including IndexedDB or local storage where available, to maintain your sign-in session, with session or memory fallback. Sign out on shared devices. This functional session storage is separate from calculator inputs. Optional Google Analytics loads only after you accept analytics. Your choice is saved in local storage and can be changed through Analytics settings in the footer. Advertising scripts are not enabled.
Firebase Hosting delivers the website and may process standard request and operational logs. Google/Firebase service processing can include technical identifiers and network information needed to operate and secure the service. See Firebase privacy and security information and Google’s Privacy Policy. The operator must verify the applicable processing terms, service locations and any international-transfer safeguards; a European Firestore location does not establish that every provider service processes data only in Europe.
Planner storage and usage controls
When the planner is activated, saved favorites contain only your owner identifier, provider, recipe ID and creation timestamp, not full recipes, instructions or ingredient histories. Authenticated Pro-only server endpoints enforce a 50-reference limit. Private usage state under your profile stores a rolling UTC day, request count and last-request time to enforce limits; it contains no planner inputs. This state and favorites are covered by account deletion. A single server-only service budget record keeps rolling aggregate counts and a short concurrency lease without user identifiers. Responses are not cached or logged with planner inputs. Provider retention, lawful bases and actual live processing arrangements still require owner approval before activation.
Support communications
If you email support@bedtimebite.com, Sergej Sotlar receives your email address, message and any information you include to answer support questions, investigate problems and handle privacy requests. Do not send passwords, payment details or unnecessary health information. The email provider and support-message retention arrangements remain under owner review.
Billing data and account deletion
The billing service uses server-controlled customer/subscription mappings and private operation state under the account profile; it does not store full invoice payloads or payment-card details in Firestore. Webhook handling keeps event identifiers, types, processing status and operational timestamps in a server-only ledger, without raw event bodies. Account billing views use actual Stripe invoice/subscription information when an approved connection exists, rather than estimates from the public list price. Ledger retention and provider record retention remain owner-review items.
For a linked subscription, account deletion expires open Checkout sessions and immediately cancels subscriptions before removing application account data. A billing failure leaves deletion queued for retry. This does not automatically issue a refund or erase Stripe invoices/customer records, prior payment attempts, support records, logs or backups; their treatment requires separate owner/legal review. Live-capable billing and deletion code remain inactive until separately approved activation.
Retention and account deletion
Calculator inputs disappear on reload or when the tab closes. Account data remains in the current account systems unless deleted; no automatic inactivity-deletion period has been verified. To request deletion, email from your account address when possible.
A separately implemented self-service deletion service is not yet activated for production. When enabled, it appears in your account, requires your current password and recent authentication, and deletes your Firebase Authentication identity, Firestore profile and descendants, and associated owned saved-reference records. Partial failures retain a server-only cleanup job so deletion can retry. The browser cannot delete privileged profile fields directly.
Completed cleanup locks are retained for at least 65 minutes to stop existing one-hour sign-in tokens from recreating deleted data, then removed by the next successful scheduled cleanup. These contain a user identifier and operational timestamps/status, not passwords or calculator inputs. Pending jobs remain until cleanup completes and require monitoring if delayed. This technical security interval is not a general account-retention policy.
Application deletion does not automatically erase support emails, provider logs or backups. Their retention and any legally required exceptions need separate review; no indefinite exception or universal immediate-erasure guarantee is asserted. Any backup restoration must honor deletion requests.
Your privacy rights and complaints
You can request access, correction, deletion, restriction, portability or objection where applicable. Email support@bedtimebite.com, explain the right and data concerned, and use your account email when possible. Identity verification may be needed; never send your password or unsolicited identity documents. If you cannot access the account mailbox, explain that in your initial request.
You may complain to a competent data-protection supervisory authority, including the Information Commissioner of the Republic of Slovenia. This does not require first obtaining permission from BedtimeBite. Applicable rights and procedures depend on the processing and law.
Future recipes, subscriptions, analytics and advertising
A Pro meal-planner interface and server-side recipe service are implemented, but live provider access remains disabled pending owner approval; Pro is not available for purchase. Isolated emulator tests use synthetic recipes and do not contact Spoonacular. Unsaved planner preferences and results stay in browser memory and are cleared on account change. When live access is separately approved and enabled, ingredient lists, exclusions, dietary filters and optional preparation-time limits will be sent through authenticated Firebase Functions to Spoonacular. Dinner and bedtime are used by BedtimeBite for ranking and are not sent to Spoonacular. Future external recipe images may send your IP address and browser request information to the image host. The live planner will also require Firebase App Check using a configured reCAPTCHA provider for abuse protection; that provider may process technical browser and network information. It is not initialized while the production planner remains disabled. All of this future processing requires final privacy review before activation.
Stripe Checkout, billing controls, reconciliation and billing-aware deletion have been implemented with separate test and live environments; live activation remains disabled. Public Checkout remains disabled, and no production subscription charges or production account-data sharing with Stripe are enabled. Automated tests use synthetic responses. Any separately approved Stripe test-mode connection would transmit test account email/identifier and customer/subscription information to Stripe. Test-mode data is still provider processing and requires review. Google Analytics 4 is optional and loads only after you accept analytics. It uses cookies to measure page views and site usage and sends technical browser and network information to Google. We do not send calculator inputs, planner preferences or account identifiers through custom analytics events. Declining keeps the Google Analytics tag unloaded; changing your choice to Decline disables collection and removes this site’s Google Analytics cookies. Withdrawal does not delete information already sent to Google. See Google’s Privacy Policy. Firebase Analytics and AdSense are not enabled. Creating an account is not agreement to future tracking or a subscription.
Updates and questions
Material processing changes should be reflected here with an updated review date. For questions or privacy requests, contact support@bedtimebite.com. See request instructions or your account.