Policies
Privacy Policy
What personal data we collect, why, who processes it, how long we keep it and your rights.
Version 2026-11-09 Last updated
Draft pending legal review. This document is a working template that has not yet been approved by counsel. It describes how Lusso is built to work and may change before launch; material changes will be announced in advance.On this page
- 01 Who is responsible
- 02 What we collect and why
- 03 Who processes your data
- 04 International transfers
- 05 Your rights
- 06 Cookies
- 07 Security
- 08 Children
- 09 Automated processing and AI
- 10 Changes to this policy
This policy explains how Lusso AI ("Lusso", "we") handles personal data when you visit app.lusso.ai, join the waitlist, create an account, buy or sell on Lusso, use our AI features, or contact us, and when we write to your company about advertising on Lusso or your company buys a sponsored placement. We collect only what we need to run the marketplace, we do not sell your personal information, and we do not use advertising cookies.
AI at LussoWe use AI in four places: the optional Ask-Lusso shopping assistant, Creator Copilot (drafts for creators who turn it on), Lusso, the creator assistant in Creator Studio (answers and drafts for creators who turn on its AI), and screening that helps our team spot fraud, scams and unsafe products. AI never decides about you on its own: a person decides before removing or restricting a listing, rejecting a creator application, warning, suspending or banning an account, pausing a payout or any other action that affects you. See Automated processing and AI.
The optional Ask-Lusso assistant is not enabled. If it is enabled, this policy will describe it before it goes live.
Section 01
1. Who is responsible
Lusso Labs, Inc. (d/b/a Lusso AI), a corporation registered in South Dakota, USA (Business ID DB284852), Lusso Labs, Inc., 1203 S White Chapel Blvd, Ste 100, Southlake, TX 76092, USA, is the controller of your personal data. Contact us about privacy at legal@lusso.ai.
EU representative (GDPR Art. 27): [Company details pending: to be appointed if Lusso is not established in the EU]. UK representative (UK GDPR Art. 27): [Company details pending: to be appointed if Lusso is not established in the UK].
Person in charge of the protection of personal information (Quebec) and data protection contact for Brazil (encarregado): [name or title, to be appointed], reachable at legal@lusso.ai.
For purchases, creators who receive information from us to deliver or support a product (for example a service you booked) handle it as independent controllers and must protect it under our Seller Agreement.
Section 02
2. What we collect and why
| Data | What it includes | Why (legal basis) | How long |
|---|---|---|---|
| Waitlist | Email, optional name, buyer/creator interest, optional note, where you signed up from, time and version of the privacy notice you saw, a keyed hash of your IP address | To email you about Lusso's launch, including your confirmation and your invite (consent; you can withdraw it at any time). IP hash: abuse prevention (legitimate interests) | Unconfirmed sign-ups: 30 days after the last confirmation email. IP hash: 30 days. Confirmed entries: until you delete your entry, and at the latest 12 months after launch (or 12 months after you signed up, if later) unless you create an account. If you unsubscribe, we delete your name and note at once and keep only your email address, marked as unsubscribed, so that we never email you again; it is deleted at the same 12-month point, or sooner if you ask. If you create an account, the entry is linked to it and deleted when your account is deleted |
| Account | Name, email, password hash, Google or GitHub profile picture if you sign in with one of them (with Sign in with Apple, the name and email address Apple shares, which may be a private relay address), role, country, the Terms and Privacy versions you accepted and your age confirmation | To provide your account (contract) and keep evidence of consent (legal obligation) | While your account is open. On deletion we delete or anonymise it within 30 days, except records we must keep (see orders) |
| Marketing email | Your email address and name, the date you opted in (the box at sign-up or in your email preferences) and which kinds of email you chose | To send occasional emails about new AI products and creator tools on Lusso (consent). Every email has a one-click unsubscribe link, our postal address and the sender's name | Until you unsubscribe or delete your account. We then keep only your address on a suppression list so we never email you again |
| Profile (optional) | Bio, location, website, phone number | To show your profile as you choose (contract) | Until you remove it or delete your account |
| Orders and payments | Products and licences bought, amounts, taxes, billing country and address (collected by Stripe), receipts, refunds and disputes, your withdrawal-waiver consent at checkout | To sell and deliver products (contract) and meet tax and accounting rules (legal obligation) | As long as tax and accounting law requires (typically 7 to 10 years), then deleted |
| Payment disputes (chargebacks) | If a payment is disputed with the card issuer: the order, delivery and download records (times and counts), the licence terms, and the creator's statement with short excerpts of the messages between the buyer and the creator that the creator chose | To answer the dispute through Stripe and the card network (legitimate interests in defending legal claims; contract) | The creator's statement and the message excerpts: 180 days after the dispute closes, then deleted. Excerpts of messages that are later removed, or whose sender deletes their account, are replaced with "[deleted]". What was sent to Stripe is kept by Stripe under its own policy |
| Library and downloads | What you own, download and licence-key activation events | To deliver products and prevent abuse (contract, legitimate interests) | While you own the product; event logs up to 24 months |
| Creators and traders | Legal name, address, phone, email, identity or registration documents, payout account (via Stripe), tax details including the data EU platform tax rules (DAC7) require (such as a tax identification number and, for individuals, date of birth), product listings and attestations | To run the creator programme, pay you, verify traders and report sellers' income to tax authorities where the law requires (contract; legal obligation under EU DSA Art. 30, the EU DAC7 Directive, the UK platform reporting rules and tax law) | While you sell on Lusso and 6 months after the relationship ends (trader data). Tax reporting data: as long as the reporting rules require (5 to 10 years after the reporting year, depending on the country) |
| Creator Copilot | For creators who turn it on: your listing text and product facts, your aggregated sales and view statistics, the drafts Copilot writes and whether you used them. When you ask for a reply draft: the buyer's message or review text, with names, email addresses, phone numbers, links and order numbers removed before it reaches the AI | To draft listing copy, social posts, launch kits and replies that you asked for (your consent when you turn Copilot on; you can turn it off at any time and calls stop at once). Buyers' message text: to help the creator answer the buyer (legitimate interests) | Drafts and usage counters: 90 days, then deleted. Calendar items you saved: until you delete them or close your creator profile |
| Lusso, the creator assistant | The questions you ask Lusso in Creator Studio and its answers (with the sources it cited and the drafts it showed), your choice to turn its AI on or off, and a record of each question without any text (which tools ran, the sources cited, how many sentences the accuracy check removed, tokens used). When its AI is on: totals from your Lusso data that it looks up and, when you ask for a reply draft, the buyer's message or review text, with names, email addresses, phone numbers, links and order numbers removed before it reaches the AI | To answer your questions about your business and Lusso's rules from your own data and Lusso's guides, and to write the drafts you ask for (contract; your consent when you turn on its AI, which you can turn off at any time). Buyers' message text: to help the creator answer the buyer (legitimate interests) | Conversations and question records: 90 days, then deleted. You can delete one conversation, or all of them, at any time in Lusso; turning its AI off can delete them too, and they are deleted when you delete your account |
| Messages and attachments | Messages between buyers, creators and Lusso support, and files you attach | To deliver services, support and resolve disputes (contract, legitimate interests) | While the conversation is open. Closed conversations and their attachments are deleted 24 months after they close. If you delete your account, the text of the messages you sent is replaced with "[deleted]" and your attachments are deleted |
| Lusso apps (iOS, Android, desktop) | Device name, platform and operating-system version, app version, an installation id, the sign-in session for that device with a keyed hash of the IP address and the last country it was used from, your notification settings and, if you allow notifications, the device's push token | To keep you signed in on the device and send the notifications you chose (contract). Push notifications only if you allow them in your device settings | A device sign-in ends after 30 days without use and at the latest after 180 days (12 hours for administrators); its record is deleted 30 days after it ends. Signing out on the device ends it and deletes its push token; a token the push service reports as no longer registered is deleted |
| Reviews | Rating, text and your display name | To show genuine buyer feedback and to detect fake or incentivised reviews (legitimate interests; consumer protection law) | Until you delete the review; anonymised when your account is deleted |
| Reports, notices and appeals | Your name and email if you give them, the content reported, a snapshot of that content taken when the notice is filed, our decision and statement of reasons | To handle notices and appeals and keep a record of what was reported (legal obligation under the EU Digital Services Act and copyright law; legitimate interests in defending legal claims) | As long as needed to handle the case and defend legal claims. The content snapshot stays with the case even if the content or an account is later deleted, and is deleted 12 months after the case closes (the decision, or the decision on an appeal against it), unless we must keep it for an actual or expected legal claim, in which case we keep it until that claim is resolved |
| Risk screening and fraud prevention | Signals about creator applications, listings and uploaded code, payments, refunds and disputes, and reviews: for example payment velocity, early fraud warnings from Stripe, accounts linked by a hashed IP address, device or card fingerprint, scam patterns and screening results written by rules and, where switched on, by AI models | To prevent fraud, scams and malware and keep the marketplace safe (legitimate interests in fraud prevention and safety, GDPR Recital 47; our duties under the Digital Services Act and consumer law). A person reviews before any action that affects you | Risk signals (for example a payment velocity or linked-account signal): Until the signal expires, at most 12 months. Screening assessments of listings, uploads, applications and payments: 3 years when they led to a moderation decision or a proposal a person reviewed (our record of the decision), otherwise 12 months. Hashed identifiers that link accounts (IP address, device, card fingerprint): 12 months after last seen. Queued screening jobs: 14 days after they finish |
| Security monitoring | Sign-in, two-factor, password and session events, data export downloads, administrator actions, hashed IP address and browser, country | To protect accounts and our systems, and to investigate incidents (legitimate interests; security obligations under data protection law). We monitor system events, not people: we do not score the productivity or behaviour of our staff or anyone else | Security events (sign-ins, two-factor checks, password and session changes): 180 days in our systems. A copy for investigating incidents and for security audits, which cannot be changed once written, is kept in our own cloud storage account for 400 days from the day it is made, normally the day after the event, and then deleted. When this copy is first switched on, the events then still in our systems (at most 180 days old) are copied once, so no copy is kept longer than 580 days after the event. Security counters (aggregated rates, no personal data): 90 days |
| Security and access logs | A tamper-evident log of sign-ins, two-factor checks, sign-outs and session changes; of the actions our staff take, including on your account, and of changes to settings and permissions; of each time our staff open your account, orders, store, reports or conversations (when, what was opened and which sections, the staff member's role and the purpose); of changes you make through our website and app APIs (the method, the address without its query, the result and how long it took); of payment and email notifications from Stripe and Resend (the event type and the result); and of file uploads, deletions and downloads. Each entry holds the time, the result, the account ids involved, a keyed hash of the IP address and of the browser that cannot be reversed, and the country. It never holds passwords, card data, message text, names or email addresses | To keep accounts, payments and our systems secure, to investigate incidents, and to show who did what and who looked at personal data (legitimate interests in security and accountability, GDPR Art. 6(1)(f), Art. 5(2) and Art. 32; legal obligations to keep records of decisions). The log stays in our own systems. It is not shared with advertisers or other third parties, not used for marketing or profiling, and never used to score or rate staff | Sign-ins, two-factor checks and session changes: 180 days. Security signals: 180 days. Changes made through our website and app APIs: 30 days. Payment and email notifications from Stripe and Resend: 90 days. Each time our staff open personal data: 400 days. File uploads, deletions and downloads: 24 months. Actions our staff take, including on your account: 7 years. Changes to settings: 7 years. Changes to roles and permissions: 7 years. Each entry is then deleted by a daily job. A daily fingerprint of the log, which holds only counts and hashes and no personal data, is kept 7 years |
| Contact form | Name, email, topic, subject and message, a keyed hash of your IP address | To answer you and keep a record (legitimate interests) | Support and sales messages: 24 months after the case was last updated and closed. Abuse, copyright (DMCA) and legal messages, and cases still open: as long as needed to handle the case and defend legal claims, then deleted after review. IP hash: 30 days |
| Creator and press outreach | Name, business email and the public profile or page we found it on (for creators who publish their work, and journalists), and our notes on the conversation | To invite creators to sell on Lusso and tell press about it (legitimate interests). We write only to addresses published for business enquiries, never to individuals in the UK or EU without their consent, and every message says where we got your details and how to object | Deleted 90 days after our last contact if you do not reply. If you ask us not to contact you, we keep only your address on a do-not-contact list |
| Sponsor sales outreach | About companies we offer advertising to: the company name, website, what it sells and its country; a business email address or phone number the company publishes for this kind of enquiry (for example partnerships@ or a sales line), or the name and business details of a person who gave them to us; where we found each of them; the messages we sent, replies, call notes, unsubscribes and objections | To offer companies paid, labelled sponsored placements on Lusso (legitimate interests, GDPR Art. 6(1)(f); we keep the assessment on file). We use only routes a company publishes for business enquiries, never personal, guessed, bought or scraped addresses. We send no unsolicited email to sole traders or individuals in the UK, EU or EEA, or to companies in countries where business email marketing needs prior consent. A person approves every message before it is sent; the first one says where we found the address and how to object. Unsubscribing or replying "no thanks" stops all contact with your company | Deleted 90 days after our last message if there is no reply; longer only while we are talking or doing business with you. If you unsubscribe or object, we keep only a one-way hash of the addresses, phone numbers and company domain on a suppression list, so that we never contact your company again |
| Sponsor orders | Advertiser and payer legal names, company address and website, tax or VAT number if given, the contact person's name and business email, what is promoted and any notes, the signatory's typed name, the version of the sponsor terms and the time of signing, a keyed hash of the IP address the order was signed from, payment status and Stripe references, and the creative and dates of the placement | To take, deliver, invoice and support the sponsorship (contract); to show who paid for each placement (legal obligation, EU Digital Services Act Art. 26); to keep evidence of the signed order (legitimate interests in defending legal claims); and to meet tax and accounting rules (legal obligation). Payment details are handled by Stripe | Paid orders: as long as tax and accounting law requires (typically 7 to 10 years), then deleted. Orders that were never paid (canceled or lapsed): deleted 24 months after they were placed |
| SMS consent records | For people who agreed to receive sponsorship texts from Lusso: the business mobile number, the exact consent wording, how and when consent was given and its evidence (for example a signed form reference), and when it was withdrawn | To text only people who gave prior express written consent, and to prove that consent (consent; legal obligation under the US Telephone Consumer Protection Act and similar laws). Replying STOP withdraws consent at once. No SMS provider is connected yet, so no texts are sent; the provider will be named on this page before any are | While the contact is in our sales records (see Sponsor sales outreach). After a STOP or any withdrawal we keep only a one-way hash of the number on a suppression list, so that we never text it again |
| Sponsored placement counts | When a card labelled Sponsored is at least half in view for a second, or clicked: the placement, the day, and a one-way hash of your IP address and browser (or of your account id when you are signed in) that changes every day. No cookie is set and no third-party tag is used | To count each visitor once per placement per day for the advertiser's report and the impression minimum we promise advertisers (legitimate interests). Bots, administrators and the advertiser's own account are not counted. Advertisers receive only totals | The daily hashes: 90 days, then deleted. The totals per placement and day contain no personal data and are kept for the advertiser's reports. When you are signed in and click a Sponsored card, we also keep which placement you clicked and when, for 30 days, so we can tell the advertiser how many orders followed within 7 days (a count only, never who you are). Paid placements are never targeted using your personal data |
| Partner offers (Sponsored emails) | Only if you switched on "Partner offers" in your email settings (off unless you choose it): your account id, the country on your account, whether you have bought or sell on Lusso, the sections and categories of listings you bought or saved, the creators you follow, and which Sponsored emails we sent you and whether you clicked them. Never your health, religion, politics, sexuality or any other sensitive data, and never if you have not confirmed you are 18 or older | To send you at most one Sponsored email a week about a Lusso listing that matches those interests, on behalf of the creator who paid for it, and to give that creator totals only (how many were delivered and clicked, and how many orders followed). Your consent (GDPR Art. 6(1)(a); ePrivacy; CASL). Switch it off at any time in Settings or with the one-click unsubscribe link in every such email. Lusso sends these emails itself: advertisers never receive your email address or any of your details | Which Sponsored emails you were sent and your clicks: 90 days, then deleted. The totals per email contain no personal data and are kept for the advertiser's report |
| Lusso Clipping: clippers | If you join Lusso Clipping as a clipper: your account id, the country you give, when you accepted the Clipper Terms and which version, the links to the clips you submit and the platform each is on, your confirmation that each clip is labelled as paid promotion, our review decisions and notes, the view counts we record for each approved clip (read from the platform's public counter, with the time we read it), your earnings, payout requests and transfers, and the identifier of your Stripe Connect account (never your bank details, which only Stripe holds) | To run the campaigns you join, verify views, pay you and keep the earnings ledger (contract); to pay through Stripe Connect, which checks your identity and age as its own controller (contract; legal obligation); to keep records for tax and accounting (legal obligation) | While you are a clipper. Earnings, payout and ledger records: as long as tax and accounting law requires (typically 7 to 10 years). Clip links and view records: with the campaign's records for the same period, so that a payout can be checked |
| Lusso Clipping: fraud checks | Signals that a clip or a view count may not be genuine: the same clip submitted more than once or to more than one campaign, view counts that do not match the platform, flags and the reason a reviewer gives, and a hold on your payouts while we check | To stop fake or recycled views and protect the brands who fund campaigns (legitimate interests; preventing fraud). A person decides every rejection, removal and payout hold, and you can ask us to look at it again through the contact form | With the clip's records (see the row above). A hold is lifted, and recorded as lifted, when the check ends |
| Lusso Clipping: campaign owners | If you run a campaign: your brief, rules and source links, budget, rates and limits, the Stripe Checkout payment for the budget, our review of the campaign, and refunds of unspent budget | To publish and fund the campaign, pay clippers from the budget and refund what is left (contract); to keep payment records (legal obligation) | Payment and refund records: as long as tax and accounting law requires (typically 7 to 10 years). The campaign page: while the campaign runs and as long as you keep it |
| Affiliate programme applications (Lusso staff only) | The answers Lusso's own team saves to apply to affiliate programmes for the AI app directory: company and brand name, website, a contact name and business email, country, a description of our audience and traffic, and our disclosure statement. It is about Lusso and its team, not about visitors or buyers | To prepare Lusso's applications to affiliate programmes (legitimate interests). Only Lusso administrators can see it. It leaves Lusso only when a team member copies it into a programme's own application form; Lusso never submits an application itself | Until the team member removes it or leaves Lusso |
| Ratings of AI apps | If you rate an external AI app in the directory: your account id, the star rating (1 to 5), any text you write, your optional "good for" answers, your confirmation that you use the app, whether you received anything of value for the rating, the date, and the maker's public reply. To rate, your email address must be verified and your account at least 7 days old. Ratings from other sites that we show beside an app (for example the App Store or GitHub) are published totals about the app, never about you | To publish genuine community ratings and protect them from fakes (legitimate interests; consumer protection law, including the US rule on fake reviews, 16 CFR Part 465). Public display: your rating, text, display name (never your email address), the date, "Uses this app" and, if you declared one, "Received an incentive for this review". Your "good for" answers are shown only as an average per use case, once enough people have answered. Lusso does not pay for ratings and never hides one for being negative | Until you delete the rating. When you delete your account, your name is removed from it and the rating stays without it |
| Ratings: abuse checks | Signals that ratings of an app may not be genuine: many ratings in a short time, mostly from new accounts and all on one side; reviewers of the same app whose accounts share a hashed network identity (IP address or device); ratings with near-identical text; and bursts of ratings from one account. Each signal records only the ratings concerned, counts and the kind of match, never a raw IP address | To detect review bombing, fake and coordinated ratings (legitimate interests in preventing fraud; consumer protection law). Signals only inform: a moderator decides, and a rating is never removed automatically | Risk signals (for example a payment velocity or linked-account signal): Until the signal expires, at most 12 months. Hashed identifiers that link accounts (IP address, device, card fingerprint): 12 months after last seen |
| Placement advertisers (Promote campaigns and Sponsored emails) | If you book a Sponsored placement or a Sponsored email for your own listing in Creator Studio: your account and storefront, the advertiser name shown on the label ("Paid by …"), what is promoted, the slots, weeks and prices, for a Sponsored email the headline, text and the audience you chose (sections, categories, buyers or creators, countries) and the number of recipients, our risk check and review decision with its reason, the Stripe Checkout payment and refunds, and the campaign ledger | To run, review, label, invoice and refund the campaign (contract); to show who paid for each placement (legal obligation, EU Digital Services Act Art. 26); to check campaigns for scams and unsafe listings (legitimate interests); to keep payment records (legal obligation). Payment details are handled by Stripe. Impressions and clicks are counted by Lusso itself (first-party, see Sponsored placement counts; no third-party tag or pixel), and you see aggregate totals only: impressions, clicks and the orders that followed within 7 days, never who saw, clicked or bought. A Sponsored email goes only to members who switched on Partner offers (see that row): Lusso sends it, you see a rounded audience estimate and totals, and never receive any recipient's email address or details | Paid campaigns, their payments, refunds and ledger: as long as tax and accounting law requires (typically 7 to 10 years). Campaigns that were never paid: while your creator account is open. The daily totals contain no personal data |
| Lusso's own analytics (first party) | Only while analytics is allowed: the pages you open (the address without its query string, apart from campaign tags and your search on the search page), the website you came from (its name only), clicks on key buttons and links, searches, page speed and errors, your device type and browser and operating system family, your country and region from our host's network data, and two random ids kept in your browser (not your IP address, not a fingerprint of your device). When you are signed in and allowed analytics, these are linked to your account. With marketing measurement allowed: whether our emails and campaigns brought you here. Without it, campaign tags are only added to daily totals that hold no id, so they are never linked to you or your account | To understand which pages, searches and steps help people find, sell and buy products, and to fix slow or broken pages (consent, GDPR Art. 6(1)(a) and the ePrivacy rules, where the law requires it; elsewhere legitimate interests with a notice and an opt-out). Never sold or shared, never used for advertising, and never run when your browser sends Global Privacy Control or Do Not Track. Change your choice on Privacy choices | Events: 180 days, then only daily totals without any identifier (25 months). The record of your choices: 24 months |
| Security and technical data | IP address, browser and device details and pages requested in hosting logs; error reports; rate-limit counters, which hold a keyed hash of the IP address, never the address itself; and a security log of refused requests (too many requests, blocked cross-site requests and malformed analytics data) holding the full IP address, the kind of refusal, the address requested, the time, how many times it happened in that minute and, when you were signed in, your account | To keep the Service secure and working, and to detect, investigate and block abuse and attacks (legitimate interests, GDPR Art. 6(1)(f) and recital 49). The security log is readable by security staff only and is never used for analytics or marketing | Hosting logs: up to 30 days with our host. A copy, which cannot be changed once written, is kept for 400 days in our own cloud storage account (Amazon Web Services) for investigating incidents and for security audits, then deleted. Error reports: up to 90 days. Rate-limit counters: 2 days. Security log of refused requests: 30 days, then deleted |
| Backups | An encrypted copy of the whole database, made every night; a copy of the files stored on Lusso (product files, images, message attachments), updated every night; and our database provider's rolling history of changes | To recover from loss, error or attack (legitimate interests; our duty to keep data secure) | Each database copy is deleted automatically after 30 days, and the provider's history covers the last 14 days. A file deleted from Lusso stays in the file copy for 30 days. Data you delete stays only in these encrypted copies until they expire. If we ever have to restore a copy, before the restored data is used again we repeat the account deletions, waitlist deletions and email unsubscribes made since that copy was taken. Other changes made in that time, such as a message or a review you removed, can come back after a restore: you can remove them again, or ask us to |
| Records of your choices and requests | Which versions of our Terms and this policy you accepted and when, your age confirmation, your checkout confirmations, and a record that you downloaded your data or deleted your account (when, whether on the website or in the app and, for a deletion on the website, the reason you picked from our list; never the data itself) | To show that we met our legal duties and honoured your requests (legal obligation; legitimate interests in defending legal claims) | While your account exists. After deletion, these records are kept without your name and email address: with the order records for as long as those are kept, and in our audit log, which cannot be changed once written (a daily copy of it, which cannot be changed either, is kept in our own cloud storage account for 400 days from archiving; with the one-time backfill at most 580 days after the event). The audit log also records what our staff did to an account, for example a name they corrected or the reason they gave for closing it, as they wrote it |
| Security reports | If you report a vulnerability: your name or the name you want to be credited by, your email address and your report | To fix the problem, keep you informed and credit you if you ask (legitimate interests) | Until the problem is fixed and checked, and at the latest 24 months after we close the report, unless we need it for a legal claim |
| Status updates | Your email address or phone number, if you subscribe on status.lusso.ai | To tell you about incidents and maintenance (consent; you can unsubscribe from any update) | Until you unsubscribe |
| Email delivery | Delivery, bounce, complaint and unsubscribe events | To honour unsubscribes and protect deliverability (legal obligation, legitimate interests) | As long as needed to keep honouring your choice |
Sensitive data: we do not ask for special categories of personal data, and our AI features are not designed to infer them. Please do not include them in messages, notes or reviews.
Section 03
3. Who processes your data
We use the service providers below (processors) under data processing agreements. They may use your data only to provide their service to us. The full list with update history is kept in our records of processing.
| Provider | Purpose | Data | Location and transfer safeguard |
|---|---|---|---|
| Vercel | Hosting, content delivery, serverless functions, web application firewall, request logs, file storage (Vercel Blob) and, only after you allow analytics, cookieless page and performance measurement | All data handled by the app while it is processed; IP address and request details in logs and firewall checks | USA (Washington, D.C. region) · EU-US Data Privacy Framework / Standard Contractual Clauses |
| Neon (managed Postgres database, running on Amazon Web Services) | Database hosting | Account, order, listing, message, waitlist and contact data | USA (AWS us-east-1) · Standard Contractual Clauses |
| Resend | Sending email (confirmations, receipts, notifications, and the sponsorship emails our team approves) | Email address, name, email content, delivery events | USA · Standard Contractual Clauses / Data Privacy Framework |
| Sentry | Error monitoring, and performance monitoring only after you allow analytics | Technical error data and a pseudonymous account id; emails, tokens, cookies and query strings are removed before sending | USA or EU (per project region) · Standard Contractual Clauses |
| Stripe | Payments, tax calculation (Stripe Tax), creator and clipper payouts and identity checks (Stripe Connect), fraud screening (Stripe Radar), creator plan billing | Payment details, billing address, transaction history; for creators and clippers also identity, business and bank details | USA and Ireland · Data Privacy Framework / Standard Contractual Clauses |
| Cloudflare | Turnstile bot protection on public forms (waitlist, contact, sign-up, reports, privacy requests) | IP address and browser / device signals during the check | Global network · Data Privacy Framework / Standard Contractual Clauses |
| Sign in with Google, only if you choose it; Firebase Cloud Messaging delivers push notifications to the Android app | Name, email address and profile picture from your Google account; for push, the device token and the notification text | USA · Data Privacy Framework | |
| Apple | Sign in with Apple in the iOS app, only if you choose it; Apple Push Notification service delivers push notifications to the iOS app | Name and email address (or Apple's private relay address) from your Apple account; for push, the device token and the notification text | USA · Data Privacy Framework / Standard Contractual Clauses |
| Expo (650 Industries) | Routes push notifications from Lusso to Apple and Google for the iOS and Android apps, only if you allow notifications | Device push token and the notification title, text and link, kept only as long as needed to deliver it | USA · Standard Contractual Clauses |
| GitHub | Sign in with GitHub, only if you choose it; source code hosting and automated jobs that run database migrations and encrypted backups | Name, email address and profile picture from your GitHub account if you sign in with GitHub; production data passes through migration and backup jobs; backups are encrypted | USA · Data Privacy Framework / Standard Contractual Clauses |
| Amazon Web Services (backups and log archive in Lusso's own AWS account) | Backups for disaster recovery: nightly copies of the database, kept 30 days, and a nightly copy of stored files, in which a deleted file is kept 30 days. A write-once archive, for investigating incidents and for security audits, of hosting logs, kept 400 days, and of security events and our audit log, kept 400 days from archiving; with the one-time backfill at most 580 days after the event | All stored records and files; IP address and request details in the hosting logs. Database copies are encrypted before upload with a key Amazon does not hold; everything else is encrypted with keys in our own AWS account | USA (AWS us-east-1) · Data Privacy Framework / Standard Contractual Clauses |
| Better Stack | Uptime monitoring and our status page (status.lusso.ai), only if you subscribe to status updates there | The email address or phone number you subscribe with and your subscription choices | USA and other locations · Data Privacy Framework / Standard Contractual Clauses |
| Anthropic | AI models (Claude) behind Creator Copilot, for creators who turn it on; Lusso, the creator assistant in Creator Studio, for creators who turn on its AI, when it is switched on; AI-assisted risk screening of applications, listings, uploads, payments and reviews, when it is switched on; drafts and answers for our own team (statements of reasons, dispute evidence and an internal assistant over our records), when it is switched on. Anthropic may not use this data to train its models | for Copilot, the creator's listing text, product facts and aggregated sales statistics, and for reply drafts the buyer's message text with names, email addresses, phone numbers and order numbers removed; for Lusso, the creator's questions, totals from their Lusso data and Lusso's own guides, and, when the creator asks for a reply draft, the buyer's message or review text with names and contact details removed; for screening, the listing, upload, application or review text and pseudonymous references (never buyer names, emails, addresses or raw IP addresses); for our team's drafts and assistant, minimised facts from our records with buyers shown only as pseudonymous references (never message text, names, emails, addresses, raw IP addresses or card details) | USA only (inference pinned to "us") · Standard Contractual Clauses |
Other recipients:
- Creators receive what they need to deliver and support your purchase: your display name, the product and licence you bought, and messages you send them.
- Other users see your public profile, reviews and creator storefront information you publish.
- Tax authorities receive sellers' DAC7 and platform-reporting data where the law requires.
- Authorities when the law requires it, for example a valid order under the Digital Services Act.
- A buyer of Lusso's business, if that ever happens, under the same protections.
Section 04
4. International transfers
Several providers are based in the United States. When we transfer personal data from the EEA, the UK or Switzerland, we rely on the EU-US Data Privacy Framework (and its UK and Swiss extensions) where the provider is certified, or on the European Commission's Standard Contractual Clauses (with the UK addendum) together with supplementary measures such as encryption in transit and at rest. You can ask us for a copy of the relevant safeguards at legal@lusso.ai. Personal data from other countries (for example Brazil, Canada, Japan, South Korea or Switzerland) travels under the same contractual protections. It goes mainly to the United States, and to Ireland for Stripe; where your law requires it, we tell you on request how the law of the receiving country protects it.
Section 05
5. Your rights
Depending on where you live, you have the right to:
- access your personal data and get a copy in a portable format;
- correct inaccurate data;
- delete your data (we keep only what the law requires us to keep);
- restrict or object to processing based on legitimate interests, including fraud prevention and outreach;
- withdraw consent at any time (for example, unsubscribe from marketing email or turn off Creator Copilot), without affecting earlier processing;
- not be subject to decisions based solely on automated processing that significantly affect you (we do not make such decisions), and to ask a person to look again at any decision;
- complain to us, and lodge a complaint with your data protection authority.
You can download or delete your account data from your account settings, unsubscribe or delete a waitlist entry from the link in any waitlist email, or send a request through our privacy request form or to legal@lusso.ai. Your download includes your Ask-Lusso conversations, your creator application and trader details, payouts and earnings records, the reports and appeals you filed and the creators you follow. It also lists every entry of our security and access log that is about you or was made by you, from all of its parts: your sign-ins, each time our staff opened your records (when, what was opened and why), the actions our staff took on your account, your storefront, your listings and their files, your orders and purchases (whether you bought or sold), payment disputes, your reviews, your appeals and your payout holds (such as a suspension, a takedown or a refund), changes to your role, your file uploads and downloads, security signals about your account, and the changes you made through our API in the last 30 days. Each entry shows its time, event, result and country, and for a staff action on one of your records whether you were its account holder, owner, buyer, seller or author; for staff, their role, not their name. No part of the log is held back from it. A staff action recorded against a record that concerns you only indirectly, such as a report or a message thread, is not linked to you automatically: ask us through the privacy request process and we will search for those entries and give them to you. Each download and each deletion is recorded (when and how, never the data itself) so that we can show we answered. Requests are free. We answer within one month; if a request is complex or you send several, we may take up to two further months and, if so, tell you why within the first month. We may ask you to confirm that a request comes from you first, usually with a link we email you or by asking you to reply from the email address on your account, and we never ask for more than we need to be sure it is you; an opt-out, a withdrawal of consent or a complaint needs no confirmation. If we cannot do what you ask, we tell you why and how to complain.
Complaints
If you are unhappy with how we handle your personal data, please complain to us first through our privacy request form or at legal@lusso.ai. We acknowledge every complaint within 30 days, look into it, and tell you the outcome without undue delay. You can also complain at any time to a data protection authority: in the UK the Information Commissioner's Office (ico.org.uk), and in the EU the authority where you live or work.
United States residents
If you live in California, Colorado, Connecticut, Delaware, Indiana, Iowa, Kentucky, Maryland, Minnesota, Montana, Nebraska, New Hampshire, New Jersey, Oregon, Rhode Island, Tennessee, Texas, Utah, Virginia or another US state with a privacy law, you have the right to know what personal information we hold about you and get a copy, to correct it, to delete it, and to opt out of its sale, of sharing for cross-context behavioural advertising, of targeted advertising and of profiling that has legal or similarly significant effects. We do none of those things, and we honour the Global Privacy Control signal as an opt-out. Affiliate links in the AI app directory and links to Lusso Clipping clips carry no personal data about you to the app maker, the affiliate network or the brand, so they are not a sale or a share either. In the last 12 months we collected the categories listed in section 2 (identifiers, customer records, commercial information, internet activity, country-level location, and for creators professional information and the sensitive information needed to pay them and meet tax rules) for the purposes described there. We disclosed them only to the service providers in section 3, for business purposes, and to the other recipients listed there; we did not sell or share them. We use sensitive personal information only to provide the service, keep it secure and meet legal duties, never to infer characteristics about you. We do not offer financial incentives for personal information. You can also opt out at Do Not Sell or Share My Personal Information (it also turns off marketing measurement in that browser), and without an account you can download or erase the analytics recorded from your browser on the same page.
Make a request, opt out or appeal on Your Privacy Choices. We confirm a request within 10 business days and answer within 45 days. If we decline it, you can appeal; a different person reviews the appeal and we answer within 45 days. If we deny your appeal, you can contact the Attorney General of your state. An authorised agent may act for you with your written permission. We will not discriminate against you for using your rights.
Other countries
If you live elsewhere, for example in Canada (including Quebec), Brazil, Switzerland, Australia, Japan, South Korea, Singapore or India, you have the rights your local law gives you, such as access, correction and, where the law provides them, deletion, portability and withdrawing consent. Use the same routes as above. We answer within the time your law sets, and you can complain to your local authority, for example the Office of the Privacy Commissioner of Canada, the Commission d'accès à l'information du Québec, Brazil's ANPD, Switzerland's FDPIC or the Office of the Australian Information Commissioner.
Section 07
7. Security
- Encryption in transit (HTTPS everywhere, HSTS) and at rest by our providers.
- Passwords are stored only as salted hashes; sign-in, invite, confirmation and reset tokens are stored only as hashes.
- Purchased secrets (such as revealed prompts and configurations) and admin MFA secrets are encrypted with dedicated keys.
- Raw IP addresses are stored in our database only in a security log of refused requests (rate limits, blocked cross-site requests and malformed analytics data), kept 30 days and readable by security staff only. Everywhere else, where we need to recognise repeat abuse, we keep a keyed hash for a short time.
- Access to production data is limited to staff who need it, protected by multi-factor authentication and logged in an append-only audit log.
- Security events, staff actions and each time our staff open personal data are kept in a tamper-evident log that is checked every day.
- Error reports are scrubbed of emails, tokens and cookies before they leave our servers.
- If a personal data breach puts your rights at risk, we tell the regulator within 72 hours and tell you without undue delay.
Section 08
8. Children
Lusso is for adults. You must be 18 or older to create an account or buy, and we do not knowingly collect data from children. If you think a child has given us personal data, tell us at legal@lusso.ai and we will delete it. Lusso Clipping pays clippers, so a clipper must also be 18 or older, or the age of majority where they live if that is higher, before joining or being paid.
Section 09
9. Automated processing and AI
We use automated checks to rank products (see How Ranking Works), to stop spam and bots (rate limits and bot checks), and to help our team prioritise reports.
AI-assisted risk screening
New creator applications, listings and their uploaded code, payments, refunds and disputes, and reviews are checked by rules and, where we have switched it on, by AI models from Anthropic. They look for signs of fraud, scams, malware, fake reviews and products that break our Acceptable Use and AI Policy, and give our team a risk level with the evidence behind it. The AI can raise a concern but cannot clear what the rules found, and it never acts on its own: removing or restricting a listing, rejecting a creator application, warning, suspending or banning an account, pausing a payout, refunding an order, hiding a review are always decided by a person, who sees the evidence first. When automated screening found the issue, the statement of reasons we send you says so, and you can appeal to a person. A clean creator application may in future be approved automatically, but never refused automatically. We screen for fraud and safety only. Screening does not scan private messages: messages reported to us are reviewed by people.
Creator Copilot
Creators who turn on Copilot get AI drafts of listing copy, social posts and replies, built from their own Lusso data. Drafts are labelled as AI drafts, the creator reviews and publishes them, and Copilot never sends, posts, prices or publishes anything itself. Buyers' names and contact details are removed before a message is used for a reply draft.
Lusso, the creator assistant
In Creator Studio, Lusso answers creators' questions from their own Lusso data and Lusso's guides, with the sources shown under every answer, and writes drafts with Copilot's tools. Answers are labelled as AI answers, and sentences with numbers no source holds are removed before they are shown. Lusso never publishes, prices, sends, posts, emails, charges or submits anything: the creator presses every button. Without its AI, Lusso shows passages from its guides instead.
Ask-Lusso assistant
Where enabled, the assistant answers shopping questions from our catalog. Its answers are labelled as AI-generated.
We do not use your messages, files or purchases to train AI models, and our AI provider may not use them for training either. We do not make decisions based solely on automated processing that produce legal or similarly significant effects for you (GDPR Art. 22). You can ask for a person to review any decision and object to the screening by writing to legal@lusso.ai.
Section 10
10. Changes to this policy
When we change this policy we update the version and date at the top of the page. For material changes we notify account holders and waitlist members by email before they take effect, and signed-in members are asked to review the new version the next time they use Lusso.
Keep reading
Related documents
-
Terms of Service
Read -
Your Privacy Choices
Read -
Cookie Notice
Read
Questions about this document? Contact us.