Skip to content

Privacy Policy

Updated:

How Jaukūs skoniai processes account, saved meal list, analytics and advertising data, and your privacy rights.

1. Data controller

MB „Lorjus“, company code 306249196, is the controller of your personal data. This policy covers jaukusskoniai.lt and its account features. Contact info@lorjus.com about data processing or to exercise your rights.

2. Data we process and why

You can read public recipes without an account. Account information is needed for registration, sign-in and the account features you request. Without it, those features cannot be provided.

  • Account: name, email address, email verification status, account identifier, and creation and update dates. Password sign-in stores a password hash rather than a readable password. The legal basis is performance of a contract (GDPR Article 6(1)(b)).
  • Google sign-in: we receive your Google account identifier, name, email address, verification information and, when supplied, profile photo, and process authentication tokens needed for sign-in. We do not receive your Google password. The basis is providing the sign-in service you request.
  • Saved meal lists: your meal name, selected recipes, portions and saving dates linked to your account. We use these to save and recalculate meals (performance of a contract). Avoid entering health information or other sensitive data in free-text fields.
  • Comments, ratings and replies: we store text, the rated comment’s 1–5 star rating, account and thread relationships, and publication/update dates. Your name, profile photo (if available) and posts are public on the recipe page. You can edit or delete your own posts; administrators can remove posts. Your posts are included in account exports and removed when your account is erased. Removing a rated comment also removes its thread. An authenticated live connection delivers reply notifications while you are online; notifications are not stored as an offline inbox.
  • Security: sessions, IP addresses, browser information and technical records help verify access, prevent abuse and investigate problems. The basis is our legitimate interest in website security and reliability (GDPR Article 6(1)(f)).
  • Enquiries: your email address, submitted information and correspondence are used to respond and handle complaints or data rights requests. Depending on the request, the basis is performance of a contract, a legitimate interest in communication or a legal obligation (GDPR Article 6(1)(c)).
  • Website consent evidence records the analytics-cookie choice, action, date, language, configuration and notice revisions, and a pseudonymous browser hash. Signed-in choices may be linked to the account. Earlier records may include the former local advertising choice. Google’s CMP separately manages current advertising choices; this website record is not a TC string. No IP address or browser details are saved in our consent evidence.

3. Google Analytics 4 and website statistics

When enabled, Google Analytics 4 (GA4) receives cookieless page measurements before a choice and after analytics cookies are refused. With consent, GA4 may additionally use browser identifiers for fuller visit and session statistics. Refusal does not authorise analytics cookies.

Google normally receives technical information, including an IP address, when your browser contacts its services. Google states that GA4 does not log or store individual IP addresses from the EU, Switzerland or the UK; they are used to derive approximate location and then discarded. Other analytics information may remain personal data.

Analytics cookies require consent (GDPR Article 6(1)(a)) where applicable. Cookieless measurement still sends network information to Google and is not a guarantee of anonymous data. Website tags are managed through Google Tag Manager. We do not add account profiles, emails, passwords or saved meal list content to GA4 event parameters. Query parameters and fragments are removed from app-supplied page URLs and referrers when analytics storage is denied.

4. Google AdSense advertising

Visitors without an active plan that includes ad-free browsing may be shown Google AdSense ads. If an ad-free paid plan is offered and active, AdSense ads are excluded as specified in that plan. Paid access does not itself enable or disable GA4 consent.

Third-party vendors, including Google, may use cookies or similar identifiers to deliver and measure non-personalised ads and detect fraud. Data may include ad views and clicks, browser or device identifiers and technical information.

Ad personalisation stays disabled. We load the AdSense tag to initialize Google’s published consent management platform (CMP), initially pausing ad requests until its consent result is available. Google interprets that result to select eligible non-personalised or limited ads. Refusing analytics cookies does not prevent limited ads. Non-personalised ads can still require storage consent; they are not the same as limited ads.

Advertising partners and purposes are disclosed in Google’s privacy message. Change advertising choices through Google’s privacy options or revocation link. Limited ads still transmit technical information to deliver the ad. If programmatic limited ads are enabled in AdSense, Google may use fraud-prevention-only cookies, local storage or Shared Storage. Limited ads are not a guarantee of anonymous processing.

5. Recipients and transfers

Authorised people at MB „Lorjus“ and providers of hosting, databases, file storage and communications infrastructure may process data as needed for their functions. Google receives data to provide your chosen sign-in, GA4 or AdSense under the relevant service terms. We disclose information to authorities when legally required or lawfully necessary.

When Google or other providers process data outside the European Economic Area, a transfer basis under GDPR Chapter V applies, such as a valid adequacy decision or standard contractual clauses and supplementary safeguards where necessary. Contact us for information about recipients and transfer safeguards for a particular service.

We do not trade account or saved meal list data. Advertising service transfers are described here and in the consent notice. Google may also process service data under its own Privacy Policy.

Payment data

We share your name, email, payment and billing details with Stripe. We process subscription identifiers, payment status and invoices to perform our contract and meet accounting obligations. An active plan may display its member badge and name style beside your public comments and replies. Payment details and subscription identifiers are not published with the badge. Stripe and Link handle checkout, invoicing, applicable tax, card and fraud-prevention data under their privacy policies. We store payment amounts and provider document references, rather than copies of customer billing names and addresses. Account deletion cancels subscriptions and detaches account relationships; necessary invoices and credit notes remain for the applicable statutory accounting retention period or a specific dispute.

6. Data retention

Account and saved meal list data have no automatic inactivity deletion deadline: we retain them while the website operates and you hold an account, so you can return to your saved information. Following a valid closure or deletion request, we remove them except for information we must, or have grounds to, retain for a limited period for a legal obligation or specific dispute. You can delete saved meal lists yourself.

Sessions normally last up to 7 days and may be extended with use. Session cookie expiry is not a deletion deadline for all server records. Signing out, clearing cookies or closing your browser does not delete your account.

Security and correspondence records currently have no single automatic deletion deadline. We assess the need to retain them against the security purpose, particular incident, enquiry or legal requirement; personal data that is no longer necessary must be removed. Deleted data remaining in backups is subject to the backup replacement cycle and access restrictions.

GA4 user- and event-level data follows the selected Google retention setting; standard GA4 properties offer 2 or 14 months. We may keep aggregate reports while the website operates where their nature and applicable requirements permit. Cookie expiry is a separate period. Google processes advertising data under its own retention rules. Contact us for the setting or criteria applicable to your data.

Browser consent choices last up to 180 days according to the website setting. Consent evidence is retained for up to 365 days from the choice and automatically removed; evidence linked to an erased account or the requesting browser identifier is removed during erasure. Completed deletion request records without account or browser identifiers are removed after 30 days. Private upload cleanup retries until successful; public recipe photos remain part of website content.

7. Your rights and choices

Subject to applicable GDPR conditions, you can request access, correction, deletion, restriction of processing or a portable copy, and object to processing based on legitimate interests. You can withdraw consent as easily as you gave it; this does not affect lawful processing before withdrawal.

Request erasure on the account page or email info@lorjus.com about any of your rights. We may ask for proportionate identity verification. We respond without undue delay, normally within one month. If the GDPR permits an extension, we explain the reason within the first month. Identify any additional data held by third-party systems or in public content so we can review it.

Ad personalisation is disabled on this website. The website does not make solely automated decisions that produce legal or similarly significant effects on you.

You may complain to Lithuania’s State Data Protection Inspectorate or another competent supervisory authority where you live, and seek a judicial remedy.

8. Policy updates

We publish the updated policy and its date on this page. We will appropriately notify you of material processing changes. Updating this policy does not itself obtain your consent to new purposes.