Lixor sub-processors
The companies that process customer data for Lixor, and what each one does.
Last updated: September 24, 2026
Intelliwav LLC (Lixor) uses the companies below to process customer data in order to provide the Lixor service. Each named company publishes its own standard data processing agreement, which applies automatically once we use its service; none of them required us to sign a separate copy. We give at least 30 days' notice before adding or replacing one. To get an email when this page changes, write to support@lixor.ai with the subject "Subscribe to sub-processor updates".
Our infrastructure is located in the United States.
Sub-processors
| Company | What it does for Lixor | Data involved | Location | Transfer safeguard |
|---|---|---|---|---|
| Supabase, Inc. | Database, login, file storage, server functions | All customer data, including stored voice recordings and photos. Photos are stored at web addresses that are not access-controlled. | USA (Amazon Web Services, us-west-1) | Standard contractual clauses, UK addendum |
| Vercel Inc. | Hosting of the web app and its server routes | All data passing through the web app | USA | Data Privacy Framework (EU, UK, Swiss); standard contractual clauses |
| OpenAI, L.L.C. | The Lix assistant, search, speech-to-text for spoken product lists, reading of bottle photos | Questions and answers, a summary of your inventory data, voice recordings sent for transcription, photos | USA | Standard contractual clauses, UK addendum. OpenAI deletes API data after 30 days and does not train on it. |
| Google LLC (Gemini API) | Reading invoice photos | Invoice images | USA | Data Privacy Framework (EU, UK, Swiss). We use the paid tier of the Gemini API, confirmed in the Google Cloud console 2026-09-21; under Google's terms for the paid service, it does not use that data to train or improve its models. |
| ElevenLabs Inc. | The spoken voice in voice counting | Product names and fixed phrases. No personal data by design. | USA | Data Privacy Framework (EU, UK, Swiss) |
| PostHog Inc. | Product analytics and, where switched on, screen recordings | Name, email, usage events, screen recordings | USA | Data Privacy Framework (EU, UK, Swiss) |
| Functional Software, Inc. (Sentry) | Crash reports from the mobile apps | Technical crash data. Email, username and IP address are removed before sending. | USA | Data Privacy Framework (EU, UK, Swiss) |
| Plus Five Five, Inc. (Resend) | Sending service emails | Name, email address, email content | USA | Data Privacy Framework; standard contractual clauses |
| Anthropic, PBC | AI used by Lixor staff in internal support and operations tools | Account and inventory records, including user names and email addresses, looked up when Lixor staff ask the operations assistant a question | USA | Data Privacy Framework (EU, UK, Swiss); standard contractual clauses |
| Microsoft Corporation | Runs the support@lixor.ai mailbox | Your emails to us | USA | Data Privacy Framework (EU, UK, Swiss) |
Other companies that receive data, acting for themselves or for you
| Company | Role |
|---|---|
| Stripe, Inc. and its affiliates | Takes payment. Stripe handles card details under its own privacy policy and is responsible for them. We never see full card numbers. |
| Apple and Google | Deliver the apps and push notifications. On iPhone, speech is recognised on the device where the phone supports it and otherwise by Apple's servers. On Android, speech is recognised by Google's speech service. Each acts under its own privacy policy. |
| Your point-of-sale or distributor systems (for example Toast, Clover, Givex, Union, Fintech) | Only if you connect them. They are your providers and send data to Lixor on your instruction. |
| Telegram | Receives Lixor's internal alerts and the operations assistant's answers in a private chat used by Lixor staff: organisation names, people's names and email addresses (sign-ups, payment problems, trials ending), and questions and answers flagged from the Lix assistant. Telegram acts under its own privacy policy. We have no data processing agreement with Telegram: it does not publish one for this use, or name a transfer safeguard, and its own developer terms put GDPR compliance on us, not on Telegram. |
| Meta Platforms, Inc. (Meta Pixel) | Outside Europe only: receives visits to lixor.ai pages, including pages inside the logged-in web app, and our start-free-trial click event, through the Meta Pixel. Acts under its own privacy policy. See Cookies. |
| BarcodeLookup.com | Receives barcode numbers to identify products. No personal data. |
The Anthropic and Microsoft rows above were checked directly against the official Data Privacy Framework list and each company's own published terms on 2026-09-21. The other rows carry forward the safeguard shown on each vendor's own current statement; check a vendor's own page before relying on this list for a specific deal.
See also our Data Processing Agreement and Privacy Policy.