Privacy statement

Looqa Technology B.V. (trading under the name Looqa.ai) is the data controller for the personal data processed through this website and the associated applications.

Legal name

Looqa Technology B.V.

Trade name

Looqa.ai

KvK

42110646

Establishment no.

000066141419

Registered office

Damcoogh 93, 1132 EB Volendam, the Netherlands

Contact

hello@looqa.ai

Privacy contact

privacy@looqa.ai

Depending on how you use Looqa, we process the following categories of personal data:

• Account data: email address, name (optional), hashed password, language preference, style preferences and, if you set one, a profile photo. We also record that you accepted the terms and confirmed that you are 16 or older, with the version and the moment.
• Sign in with Apple: if you sign in with Apple, we receive a fixed user ID from Apple, your email address (possibly a relay address Apple creates for you) and, if you share it, your name. We do not keep an access token from Apple. Sign in with Google is not offered at the moment.
• Wardrobe content: photos you upload or add via a link, the details of your clothing (such as category, colour, brand, size, price, tags and notes), your wear log, outfits, outfit suggestions, planned outfits and resale texts you have generated (on looqa.ai).
• Invitations: if we invite you, we keep your email address, the status and the expiry date of the invitation, the group and the plan we invited you with, who sent the invitation, and a hash of the invitation link. The link itself exists only in the email.
• Waitlist signup: if you join the waitlist we record: your email address, your language, the source you arrived through and the UTM parameters and referring page of that visit, your own referral code and that of whoever referred you, the version of the consent text you saw, and an IP pseudonym. That pseudonym is not an IP address: it is a hash of your IP with the date and a secret, truncated to thirty-two characters, which changes daily. It lets us see within a single day whether someone is referring themselves, and no longer than that. We never store the raw IP address. The confirmation and unsubscribe links are kept only as hashes, so they cannot be reconstructed from our database.
• Push notifications (app): if you allow the app to send notifications, we keep an Expo push token and the platform (iOS or Android) for each device. We use it to send you notifications that belong to the service, for example a nudge on the morning you have an outfit planned. You can turn that nudge off in Settings on looqa.ai, or turn off all Looqa notifications in your phone's settings. The title and text of such a notification pass through Expo to Apple or Google, who deliver it to your device.
• Photos of yourself: we process no biometric data and no other special categories of personal data (GDPR Art. 9). A clothing photo in which you appear yourself, such as a mirror selfie, is treated as an ordinary clothing photo: we derive no body characteristics from it.
• Characteristics derived from photos: AI image analysis derives characteristics from your clothing photos, such as category, colour, pattern, material, season and style. We use these characteristics solely for the features you provide them for and do not infer ethnicity, health or other special categories from them.
• Payment data: subscription status via in-app purchases in the App Store (Apple) or Google Play (Google), with RevenueCat managing the subscription status on our behalf and knowing you by your Looqa user ID. Looqa.ai does not itself store credit card numbers or IBANs.
• Technical data: IP address, browser or device type, app version, time zone and session tokens, for security and troubleshooting. For the warning about a sign-in from a new device we keep a fingerprint of your browser or app (a hash, not the details themselves) and a readable label, such as "Safari on iPhone".
• AI usage: for each AI step we record which step it was, when, whether it succeeded and how much computing it cost. We use this to keep an eye on costs and on the limits per plan. The content of your photos or requests is not in it.
• Usage milestones: whether and when you first took a few fixed steps, such as your first item, your first outfit or your first suggestion. No content; we use it to see where new users get stuck. It goes with your account when you delete it.
• Daily activity: on which days you used Looqa, one row per day, and when you were last active. When you use the app, we also record the platform (iOS or Android) and the version, build and update of the app. No content; we use it to see how many people use Looqa and which app versions are still in use. It goes with your account when you delete it.
• Reports, feedback and moderation: if you report an AI result or send feedback from the app, we keep your report (reason and explanation), together with the screen, the app version, your device and recent errors that we attach automatically. If we act on content or on your account, we keep the decision, the reason and any appeal.
• Consents: which consent you gave or withdrew for AI processing, for email and, if you are signed in, for usage statistics on the website, with the version and the moment. Your choice for usage statistics and crash reports in the app is kept on your device and, from app build 16, also with your account, with the version and the moment, so that another account on the same device starts with both switched off. Your choice for error reports on the website is kept only in your browser.
• Onboarding answers: if you go through the introduction when you start, we keep your answers with your account: what bothers you about your wardrobe, roughly how many items you own, how often you shop, how much you spend (only if you choose to answer), the occasions and styles you dress for, your goal, and how far you got. Before you have an account they stay only in your browser or on your device, apart from the usage statistics you agree to. We use them to personalise Looqa: your plan, your suggestions and the screens that explain Pro.
• Locked items: if Pro ends (terms, section 05) while you have more items than Free holds, the items above the limit are locked. Of each locked item we make a small, heavily blurred preview of its photo, a few hundred bytes, so your wardrobe can show that the item is there without showing it. The photos themselves move to private storage until the item is unlocked.
• Contact with us: if you email us, your message and your email address are in our mailbox at Microsoft 365.

We process personal data exclusively for clearly defined purposes, and always on the basis of a GDPR legal basis:

• Performance of a contract (Art. 6.1.b): we use your account data, your wardrobe content and your push token to provide the service: storing, recognising, searching, outfit suggestions, the planner, resale texts (on looqa.ai), notifications that belong to the service, and email about your account, your security and your subscription. Your onboarding answers personalise your plan and your suggestions; the blurred previews show locked items in your wardrobe.
• Legal obligation (Art. 6.1.c): for our bookkeeping and the Dutch Tax Administration we keep the subscription events we receive from RevenueCat. On an in-app purchase, Apple or Google is the seller and issues the invoice.
• Legitimate interest (Art. 6.1.f): for security and preventing abuse (rate limiting, the warning about a new device), for server-side error monitoring (see below), for handling reports and moderation, for keeping an eye on AI costs, for your daily activity (how many people use Looqa and which app versions are still in use), and for product improvement at an aggregated level.
• Server-side error monitoring (Art. 6.1.f): if an error occurs on our servers, a report goes to Sentry and a masked line goes to our own error log. This happens without consent, because we need to see errors in the service to keep it working and secure. The reports contain no name, email address or IP address, and we mask user IDs in URLs. No screen recording is made. You can object to this (see Your rights).
• Consent (Art. 6.1.a): for your waitlist signup; for lifecycle email, such as tips and reminders, only if you ticked the box for it, when you created your account or on the screen where you accept the terms; for optional usage statistics (PostHog) and error reports from your browser or the app (Sentry); and for push notifications (the permission your device asks for). You can withdraw consent at any time, and that must be as easy as giving it: email carries an unsubscribe link in every message, the website has a link in the footer, the app has switches in your settings, and AI processing has a switch in your settings.
• The introduction specifically: which steps of the introduction you see, which answers you choose (as fixed words, never free text), what you skip and how long it takes go to PostHog only with your consent for usage statistics. Without that consent nothing is sent, also not later. Separately, we count per day, per platform and per step how often a step was shown, skipped or completed; with that count we store no user, device or IP address.
• The waitlist specifically: we process your signup on the basis of your consent (Art. 6.1.a). That consent is only given once you click the confirmation link in the first email; until then we do not count you and send you nothing else. The source and UTM data and the IP pseudonym are processed on the basis of our legitimate interest (Art. 6.1.f) in seeing which channels work and in preventing someone from referring themselves to move up the list.
• AI processing after explicit consent: your clothing photos and garment data only go to Google (Gemini) and Replicate after you have given permission for it. Gemini recognises and describes your clothing, creates a cleaned-up product photo, suggests outfits and writes resale texts (on looqa.ai). Replicate removes the background and runs an automated safety check on every clothing photo and on your profile photo. You can withdraw that permission in your settings; new AI processing then stops immediately.

AI outputs are suggestions: we do not make decisions based solely on automated processing that produce legal effects or similarly significantly affect you (GDPR Art. 22). A photo that fails the automated safety check is not added to your wardrobe; if you think that is wrong, email support@looqa.ai and a person will look at it. AI-generated or edited images are made identifiable as such, in line with the EU AI Act.

We do not keep your data longer than necessary. Where an automated job enforces the period, we say so. Where that is not yet the case, we say that too.

• Account and wardrobe: for as long as your account exists. If you delete your account, we erase your data from our database and storage immediately; copies in encrypted backups expire within 30 days.
• Onboarding answers: for as long as your account exists; they go with your account when you delete it. The copy in your browser or on your device stays until you clear your browser data or remove the app.
• Blurred previews of locked items: for as long as the item exists; they go with the item or with your account.
• Photos that were not processed: an upload that got stuck is kept for seven days so you can try again; an upload waiting because your free limit is full, for thirty days. After that an automated job deletes the photo.
• Push tokens: until you sign out of the app (we then unregister the token), delete your account, or Apple or Google tell us the app is no longer on that device. A token the app has not used for six months is deleted as well.
• Invitations: an accepted invitation goes with your account when you delete it. An invitation you do not accept expires after fourteen days (if an administrator chooses a longer period when sending it, after sixty days at most); your email address then stays with the status "expired". There is no automated period for that yet. If you ask, we erase it immediately.
• Waitlist signups: until the waitlist is closed or you unsubscribe. If you unsubscribe we keep your email address with the status "unsubscribed" as a suppression record, so a later campaign cannot write to you again. That is the only reason we keep it.
• Email send log: 90 days, cleaned up automatically. We keep the recipient, the subject and whether sending succeeded, never the body of the message.
• Which lifecycle emails you already received: for as long as your account exists. We keep only the user ID, the kind of message and the moment, so you do not get the same nudge twice. It goes with your account when you delete it.
• Consents: for as long as your account exists; they go with your account when you delete it.
• Subscription events and AI usage: these two lists are deliberately not editable. While your account exists they are linked to it. If you delete your account, that link disappears and only rows without a link to you remain, for our bookkeeping (the statutory tax retention period is seven years) and our cost control.
• Technical log files: error reports from our servers in our own log: 30 days, masked (no email addresses or keys). Other technical logs: 90 days at most. Both are cleaned up automatically.
• Error reports at Sentry: Sentry erases them automatically after the retention period of our Sentry plan. They contain no name, email address or IP address.
• Usage statistics at PostHog: for as long as your account exists. If you delete your account, we have PostHog erase your person and the events that belong to it. Events from visitors without an account are not linked to a person and follow the retention period of our PostHog plan.
• Rate limiting (Upstash): the counters expire by themselves, within about 48 hours.
• Known devices: for as long as your account exists. We keep a fingerprint of your browser or app, not the details themselves, so we can warn you about a sign-in from a new device.
• Reports about AI results and in-app feedback: two years, cleaned up automatically, so we can see patterns in recurring complaints. If you delete your account earlier, they go with it.
• Affiliate link clicks: one year, cleaned up automatically. The same IP pseudonym as the waitlist applies here: hashed, rotating daily, never the real IP address.
• Reports, moderation decisions and appeals: for as long as your account exists. If you delete your account, they go with it. The admin audit log does keep the fact that a decision was made.
• Administrator notes: a note an administrator adds to your account, for example about a support question, is kept for as long as your account exists.
• Admin audit log: this log records which administrator performed which action on which account and when, with the old and the new value of what changed. For some actions, such as a suspension or viewing as you, it also holds the reason the administrator gave. The administrator's IP address is stored only as a hash. The log is deliberately neither editable nor deletable, also not when you delete your account: its evidential value would disappear. We have not yet set a fixed retention period for it; until we do, we keep it for as long as the service exists.

If you delete your account we erase everything attached to you, including your customer record at RevenueCat and your person and events at PostHog. If you were on the waitlist and then created an account with that address or through your invitation, that waitlist row goes with your account. A few things survive the deletion, and it is fairer to say so than to leave it out: what Apple or Google keep about your purchase, under their own policies; error reports already at Sentry, until their period runs out; the email send log (recipient and subject, never the body) for up to 90 days, including the confirmation that your account is gone; masked error lines in our own log, for up to 30 days; an invitation to your address that was never accepted; the subscription events and AI usage, without a link to you; and the admin audit log. Our processors may also keep copies for a short time under their own terms, for example Google's logs of Gemini API requests for abuse monitoring and the sending history at Loops. A waitlist row that is not linked to your account, for example under another address, stays as described for the waitlist above. If you sign in with Apple and confirm the deletion with Apple in the app, we also revoke the link with your Apple ID; if that fails, the app shows you how to do it yourself.

We work with a limited number of processors that make our service possible. We conclude a data processing agreement with them, usually through their standard terms. Each processor is bound by that agreement to protect your data at least as well as this statement and the GDPR require. We never sell your personal data.

We do not process payment data ourselves. Payment runs via in-app purchases in the App Store (Apple) or Google Play (Google) under their own privacy policies; RevenueCat manages your subscription status on our behalf. Looqa receives from RevenueCat the events of your subscription (such as a purchase, renewal, cancellation or refund) with the plan, the store, the price and currency, the end of the current period and a pseudonymous customer or transaction ID, never your card details. Apple and Google are themselves responsible for what they process on a purchase, and when you sign in with their account.

Your data is stored in the EU, at Supabase in Ireland. Part of the processing takes place outside the EEA, mainly in the US: at Google (Gemini), Replicate, Expo, Loops and RevenueCat, and depending on their settings at Vercel and Microsoft. For this we use appropriate safeguards: the adequacy decision for the EU-US Data Privacy Framework for companies that have joined it, and otherwise the Standard Contractual Clauses (SCCs) of the European Commission. Your clothing photos and your profile photo reach Replicate in the US through a short-lived secure link; storage remains in the EU.

Under the GDPR you have the following rights:

• Access: request what data we hold about you.
• Rectification: have inaccurate data corrected.
• Erasure: have your account and your data deleted ("right to be forgotten"), with the exceptions listed in section 04.
• Restriction: have processing suspended during an investigation.
• Objection: object to processing based on legitimate interest, such as server-side error monitoring.
• Data portability: a copy of your data in machine-readable form (JSON).
• Withdrawal of consent: for processing based on consent.

You can exercise these rights via your settings (signed in), via the public page www.looqa.ai/account/delete (account deletion, also without the app) or by sending an email to privacy@looqa.ai. You also have the right to lodge a complaint with the Autoriteit Persoonsgegevens (the Dutch Data Protection Authority).

We take appropriate technical and organisational measures:

• Encrypted connections (TLS) for all traffic.
• Encryption at rest (AES-256) of the database and storage.
• Row-Level Security at database level: through the app and the API, a user can only access their own data.
• Your original photos are in private storage, reachable only through short-lived signed links. The edited, cut-out image of a garment, outfit images and your profile photo are in storage that can be reached through a direct link without signing in. Those folders cannot be listed and we do not publish those links.
• Rate limiting on the API, and DDoS protection by our hosting provider.
• Backups and access logging.

Who at Looqa can access your data. Only staff we designate have access to the admin panel. They are on a fixed list and hold a role (owner, admin, support or read-only), always sign in with two-factor authentication, and their session expires after twelve hours. Depending on their role, and when needed for support, moderation, a request from you or a legal obligation, they can view your account details and your wardrobe, look at your clothing photos, view Looqa as you see it for thirty minutes with read-only rights, add a note to your account and create an export of your data. To view as you and to suspend an account they have to give a reason. Every action goes into the admin audit log (see section 04).

No service is 100% secure; we continuously improve our measures. For a data breach that poses a risk to your rights and freedoms, we notify the Dutch Data Protection Authority within 72 hours and, where legally required, you.

On the website we use three kinds of technologies. You set your preferences in the cookie banner, and you can change them at any time through the "Cookie preferences" link at the bottom of every page. Withdrawing consent must be as easy as giving it (GDPR Art. 7(3)), and that link is what makes it so:

• Necessary: for authentication, session, language choice, security and remembering your cookie choice, and, if you start the introduction before you have an account, your answers and how far you got, so you can pick up where you left off. These are always active and require no consent.
• Analytics (only after consent): PostHog (EU region) for usage statistics: only events we choose ourselves, no automatically captured clicks and no session recordings, linked to an internal user ID and never to your email address. In addition, your browser remembers during your visit the campaign you arrived through (the UTM parameters and the referring page), so that a waitlist signup on a later page gets the right source. It stays in your browser, disappears when you close the tab, and is only sent along when you sign up yourself.
• Error monitoring (only after consent): Sentry (EU region). When an error occurs in your browser, an error report goes to Sentry, without name, email address or IP address and with masked user IDs, and for a share of page views a measurement of loading time. Sentry makes no screen recording (replay) of your session. If you do not consent to error monitoring, Sentry is not loaded in your browser at all.

In the app, usage statistics and crash reports stay off until you switch them on in the app itself; you can switch them off there again. Error reports from our own servers are not covered here: they are described in section 03.

We respect "Do Not Track": if it is enabled and you have not made a choice yet, we disable non-essential technologies automatically. We show no personalised ads and do no cross-site advertising tracking.

Looqa.ai is not intended for use by persons under the age of 16. We do not knowingly process data of children under 16. If you discover that a child under 16 has left personal data with us, let us know via privacy@looqa.ai and we will delete the data.

This privacy statement may be amended in the future when our service or legislation changes. We announce material changes at least 30 days in advance by email to all registered users, or we show them to you in the app or on the website before they apply to you. The date at the top of this page indicates the latest update.

Version 2.6 (3 October 2026) adds the onboarding answers and the blurred previews of locked items (sections 02 to 04). Existing accounts see it once, together with terms 2.5.

Questions about privacy or your rights? We answer everything personally within 30 days.