Privacy policy
Last updated 30 October 2026
Who we are
MGChufa LLC, a limited liability company registered in the State of Wyoming, USA, trading as Lumvi, of 30 North Gould Street, Sheridan, WY 82801, USA, is the data controller for the personal data described here. Contact us at support@lumvi.app.
What we collect
- Account data — name, email address, and the password hash held by our authentication provider. We never see your password.
- Business data — your trading name, address, postcode, phone, VAT and company numbers, and who you invite to your account.
- Content — the briefs you write, and the copy and images generated for you.
- Connected accounts — access tokens for services you connect. These are stored encrypted, server side, and are never sent to your browser.
- Leads — publicly visible posts from public social media groups you ask us to watch, including the author’s display name where it is public.
- Billing data — subscription status and identifiers from Stripe. We do not store card numbers.
- Usage data — a record of each AI operation and its cost, so we can apply your plan’s limits.
Why, and on what basis
- To provide the service — performance of our contract with you.
- To take payment — performance of our contract, and our legal obligations for accounting records.
- To keep the service secure and working — our legitimate interests in preventing abuse and diagnosing faults.
- Lead discovery — our legitimate interests, and yours, in identifying publicly posted enquiries. Only public groups are read, only posts, and never through a logged-in account.
Who we share it with
We use these processors, and share only what each needs: Supabase (database, sign-in and file storage, hosted in the UK), Vercel (application hosting), Stripe (payments), Anthropic (text generation), OpenAI (image generation), xAI (the AI that helps our team run and support your account), Apify (reading public social posts), Telnyx and The SMS Works (delivering text messages), and the platforms you choose to connect, such as Netlify, Meta and LinkedIn.
Some of these are outside the UK. Where that is so, transfers are covered by the UK International Data Transfer Agreement or equivalent safeguards. We do not sell personal data, and we do not use your business data to train AI models.
Text messages (SMS)
If you agree to receive text messages from Lumvi, we keep your mobile number and a record of that consent: when you gave it, how (by phone with one of our team, or on our website), and the wording you agreed to. We use them only to send you the texts you agreed to receive about Lumvi and to honour your choice to stop.
We do not sell, rent or share mobile numbers or text-messaging consent with any third party or affiliate for their marketing or promotional purposes. Mobile numbers are passed only to the carriers and messaging providers that deliver our texts, and only for that purpose.
Message frequency varies. Message and data rates may apply. Reply STOP at any time to stop receiving texts, or HELP for help. After STOP we send nothing further, and your number stays on our do-not-text list.
How long we keep it
- Account and business data — while your account is open, then up to 90 days.
- Content and websites — while your account is open.
- Leads — automatically deleted 90 days after they are found.
- Text-message consent and opt-outs — for as long as we might text you, and opt-outs indefinitely so we never text you again.
- Billing records — six years, as tax law requires.
Your rights
Under UK GDPR you may request a copy of your data, ask us to correct or delete it, object to or restrict processing, or ask for it in a portable format. Email support@lumvi.app and we will respond within one month. If you are unhappy with our response you can complain to the Information Commissioner’s Office at ico.org.uk.
Cookies
We set only the cookies needed to keep you signed in and to keep your session secure. We do not use advertising or third-party analytics cookies, so there is no consent banner to click through.
Security
Data is separated per business at the database level, so one customer cannot read another’s. Access tokens for connected services are held in a store that no browser session can read. Access to production systems is limited to people who need it.