Privacy
Privacy Policy
Last updated: October 26, 2026
1. Data controller
The controller of your personal data is the team behind Liru.app: Maciej Kaminski and Karol Jablonski. For data-related inquiries, contact us at contact@liru.app.
2. Data we collect
Account data (designer): email address, full name, design studio name, profile photo and studio logo (optional), language and currency preferences, authentication data (encrypted password, MFA tokens). Project data: project names and descriptions, property addresses, budget and financial data, photos, documents and files uploaded to the platform, product data (names, prices, photos, store links), subcontractor and supplier data, notes, comments, design decisions. Client portal data: client email address, client name (optional), brief and survey responses, style preferences (quiz results, swipe results, comments), product/visualization approvals and rejections. End clients do not create accounts - access is provided through a unique link with a token. Technical data: IP address, browser and operating system type, visit times and frequency, session identifiers, error logs (stack traces, error context). Chrome extension: product data extracted from store pages (name, price, image, URL), authentication token (Bearer token). The extension does not track browsing history - it activates only when clicked by the user. Account acquisition data: the campaign parameters of the link through which the account was created (e.g. utm_source, utm_medium, utm_campaign, utm_content, utm_term), the liru.app page from which you moved to the app, the domain of the page that brought you to liru.app, the type of ad click identifier (only its name, e.g. "fbclid", never its value), a referral, a team invitation, a waitlist sign-up, our e-mail sent before sign-up, the sign-up method (password or Google), the language, and the device type (computer, phone, tablet) together with whether the sign-up took place in the in-app browser of Instagram or Facebook. Account usage data: the days on which you use the app and the extension (first and last visit of the day), logins (login method, MFA use, device type, browser and system family, without the IP address and without the full browser identifier), plan changes, the days on which a client opened the project portal, and visits to the app from links in our e-mails. Log of sent e-mails: message type, date sent and delivery status (sent, delivered, delayed, bounced, marked as spam, failed); for messages to a designer's clients we store only a hash (SHA-256) of the e-mail address and no subject. We do not use the open or click tracking offered by our e-mail provider. Onboarding call: when you book a call on studio.liru.app/umow, the booking is handled by Cal.com, which collects your name, e-mail address, chosen time, time zone and whatever you enter in the form (e.g. what you would like to start with). If you come from a link in our e-mail, we attach your account identifier and the link's campaign parameters to the booking. In your account we record that the call was booked, rescheduled or cancelled, its time, your answer in the form and the campaign parameters. E-mails about using the service: we record which message we sent to your address and when, and your unsubscribe if you opt out. Survey on liru.app/start: if you fill it in, your answers to three questions (how many projects you run, how you work and where you want to start) travel to the app in the sign-up link, and we save them with your account.
3. Purposes and legal bases of processing
Providing the service (account, projects, portal) - Art. 6(1)(b) GDPR (performance of a contract). Sending transactional emails (invitations, notifications) - Art. 6(1)(b) GDPR (performance of a contract). Analytics and service quality improvement - Art. 6(1)(f) GDPR (legitimate interest of the controller). Error monitoring and stability - Art. 6(1)(f) GDPR (legitimate interest of the controller). AI data processing (categorization, notes) - Art. 6(1)(b) GDPR (performance of a contract). Security (rate limiting, abuse detection) - Art. 6(1)(f) GDPR (legitimate interest of the controller). Marketing and ad performance measurement (Meta Pixel on the marketing site and sending sign-up and subscription events from the app to Meta via the Conversions API) - Art. 6(1)(a) GDPR (consent). Measuring which acquisition channels work (account acquisition data), tailoring your first steps in the app to your liru.app/start survey answers, user support and service development (account usage data), checking that e-mails are delivered (log of sent e-mails) and checking ad measurement (log of events sent to Meta): Art. 6(1)(f) GDPR (legitimate interest of the controller, namely knowing where users come from and how they use the service, making sure messages arrive, and making sure ad measurement works and data reaches Meta only with consent). You may object to this processing (Art. 21). E-mails about using the service (tips when you start with Liru, an invitation to an onboarding call, a note when your client first opens the portal, a note about the end of your trial or Pro plan): Art. 6(1)(f) GDPR (legitimate interest of the controller, namely helping you get started with the service). You can unsubscribe from these e-mails with one click in each of them; transactional e-mails (e.g. invitations, notifications) still reach you. Booking and holding an onboarding call: Art. 6(1)(b) GDPR (steps taken at your request).
4. Data processors (sub-processors)
We use the following third-party services: Supabase (Supabase Inc.) - database, authentication, file storage - data in EU (Frankfurt). Vercel (Vercel Inc.) - application hosting, serverless functions, and Vercel Web Analytics - EU (preferred) / USA. Google Analytics (Google Ireland Limited) - website analytics after user consent - EU / USA. Meta Platforms Ireland Limited - Meta Pixel on the marketing site and the Conversions API (server-side transfer of sign-up events and of subscription start and renewal events), ad performance measurement and audience building, only after user consent - EU / USA. OpenAI (OpenAI LLC) - product categorization, AI note generation, summaries - USA. fal.ai (fal.ai Inc.) - image segmentation - USA / EU. Resend (Resend Inc.) - transactional email delivery - USA. Upstash (Upstash Inc.) - rate limiting, abuse protection - EU (Frankfurt). PostHog (PostHog Inc.) - product analytics - EU. Sentry (Functional Software Inc.) - error monitoring - USA. Data transfers to the USA are carried out on the basis of Standard Contractual Clauses (SCC) or adequacy decisions (EU-US Data Privacy Framework), in accordance with GDPR requirements. Cal.com (Cal.com, Inc.): booking onboarding calls on studio.liru.app/umow, USA. Google (Google Ireland Limited): calendar and Google Meet for booked calls, EU / USA. Resend also sends the e-mails about using the service described in section 3. Data transfers to Cal.com and Google follow the same rules as for our other US providers.
5. AI data processing
Liru.app uses artificial intelligence for: product categorization - product name and description are sent to OpenAI for category assignment; AI note generation - client brief responses are analyzed to create summaries; data extraction from pages - product page content is analyzed to retrieve data. Data sent to AI providers is not used to train AI models (in accordance with OpenAI and fal.ai API customer policies), is processed solely to fulfill the specific request, and is not stored by providers longer than necessary to process the request (max. 30 days for abuse monitoring).
6. Data retention periods
Account data is retained until account deletion. Project data - until account or project deletion. Client portal data - until portal deactivation or project deletion. Error logs (Sentry) - 90 days. Analytics data: PostHog - 12 months; Google Analytics and Vercel Web Analytics - according to those services' settings, with Google Analytics _ga cookies able to expire after 2 years. Storage files (Supabase) - until deleted by the user. Session data - 7 days (automatic expiration). Account acquisition data: until account deletion. Account usage days, logins and other account events: 25 months. Log of sent e-mails: 24 months. Call bookings, reschedules and cancellations recorded in your account: 25 months, like other account events. Answers to the liru.app/start survey: 25 months, like other account events. Bookings in Cal.com and events in Google Calendar: as long as we need them to stay in touch about the call; on request we delete them earlier. Records of sent e-mails about using the service and of your unsubscribe: as long as needed to avoid sending the same message twice and to respect your unsubscribe.
7. Your rights (GDPR)
As an EU/EEA user, you have the following rights: right of access (Art. 15) - you may request information about processed data; right to rectification (Art. 16) - you may correct inaccurate data; right to erasure (Art. 17) - you may delete your account and all data ("Delete account" function in settings); right to restriction of processing (Art. 18); right to data portability (Art. 20); right to object (Art. 21) - to processing based on legitimate interest; right to withdraw consent - at any time, without affecting processing prior to withdrawal. Account deletion: Settings → Security → Delete account (immediate, cascading deletion of all data). Other requests: write to contact@liru.app - we will respond within 30 days. Complaint: you have the right to lodge a complaint with the President of the Personal Data Protection Office (PUODO) or your local supervisory authority.
8. Cookies and tracking technologies
Essential (no consent required): liru_cookie_consent - saving your analytics consent choice, expiry 1 year; liru_cookie_consent_ads - saving your marketing consent choice, shared between liru.app and studio.liru.app, expiry 1 year; NEXT_LOCALE - language preferences, expiry 1 year; Supabase session - user authentication, expiry 7 days; client portal session - client portal access, expiry 7 days. Analytics (only after consent): Google Analytics 4 - website traffic measurement, _ga and _ga_<id> cookies, by default up to 2 years; Vercel Web Analytics - aggregated website analytics without cookies. In the product app, we may use PostHog for product analytics according to consent settings. Marketing (only after consent): Meta Pixel (Meta Platforms Ireland Limited) - ad performance measurement and audience building on Meta platforms (Facebook, Instagram); _fbp and _fbc cookies, expiry up to 90 days; events such as page views, button clicks and form submissions on the website (call request, contact form, newsletter sign-up; without the content of the form) may be sent to Meta together with your IP address and browser data. After you grant marketing consent, when you create an account or start or renew a paid subscription in the app, we send a sign-up or subscription event to Meta from our server (Conversions API) together with SHA-256 hashes of your e-mail address and account ID, browser data and the _fbp and _fbc identifiers, plus your IP address for sign-ups and the transaction value and currency for subscriptions. The e-mail hash is used only to match the event to the ad account; we never send the address in plain form. On our server we only record whether the event was sent and with what result (without your e-mail or IP address). Marketing cookies start only after your explicit consent, which you can withdraw at any time in the cookie settings (button in the bottom-left corner of the site or the “Cookie settings” link in the footer). Account acquisition data uses no cookies: campaign parameters travel from liru.app to the app only in the link address and in the memory of the open browser tab, and we store them on our server only when the account is created. The studio.liru.app/umow page embeds the Cal.com calendar: the booking takes place directly in Cal.com, which may use its own cookies and browser storage needed for the booking form (under Cal.com's privacy policy). We do not run product analytics on this page or on the unsubscribe page.
9. Data security
We apply the following security measures: encryption of sensitive data (AES-256-GCM), transport encryption (TLS/HTTPS), two-factor authentication MFA (TOTP), Row Level Security (RLS) at the database level, rate limiting on API endpoints, input data validation (Zod), regular security audits (latest: October 2026), password policy: minimum 8 characters, uppercase letter, digit.
10. Children's data
Liru.app is not intended for persons under 16 years of age. We do not knowingly collect data from children. If you become aware that a child has provided us with personal data, please contact us at contact@liru.app.
11. Changes to the privacy policy
We announce changes to the privacy policy on this page: the date of the latest update is always shown at the top. If a change requires your consent, we will ask for it separately. Continued use of the service after changes are introduced constitutes acceptance.
12. Contact
For matters regarding personal data protection: email contact@liru.app. Creators: Maciej Kaminski, Karol Jablonski. Platform: https://studio.liru.app.