TexaCoreSubprocessors
Version 2026-10-27 · Effective 27 October 2026
This page lists the companies that process customer personal data on behalf of Next Revolution for Software Development, Dublin, Ireland ("we", "us") to run TexaCore, and what each one does. TexaCore is the name of our product. It is the list referred to in section 6 of the Data Processing Agreement. We have a contract with each company that limits its use of the data. The page is accurate for the current version of the service.
1. Core infrastructure (used for all customers)
| Provider | What it does for TexaCore | Data involved | Where |
|---|---|---|---|
| Supabase | Database, sign-in, file storage and server functions of the cloud service | All customer data, including the cloud backup copies of desktop company files | United Kingdom (London) |
| Amazon Web Services | The infrastructure on which Supabase runs our project | All customer data, stored encrypted at rest by the hosting provider | United Kingdom (London, region eu-west-2) |
| Cloudflare | Content delivery, DNS and security filtering in front of the website and the service; the optional Cloudflare tunnel of the desktop edition | Web traffic, including IP addresses and content in transit | Global network |
2. Feature providers (used only when the feature is used)
| Provider | What it does for TexaCore | Data involved | Where |
|---|---|---|---|
| Google (Gemini API and Firebase Cloud Messaging) | AI features: the assistant, reading a photographed invoice, translating names, analysing import files, describing and categorising products, generating marketing text, analysing fabric photos, transcribing voice messages and summarising calls; push notifications to the mobile app | What the user sends for the request and the data the request needs | United States and other locations of the provider |
| OpenAI | Speech-to-text for call recordings; AI generation of product images | Call audio; image prompts and images | United States and other locations of the provider |
| Anthropic | AI assistant tasks that our AI router sends to Claude models | What the user sends for the request and the data the request needs | United States and other locations of the provider |
| ElevenLabs | Text-to-speech for the voice prompts of telephone menus | The text of the prompt to be spoken | Provider's infrastructure outside the United Kingdom |
| Resend | Sending email from the service: invitations, notifications and documents that users send | Recipient addresses, message text and attachments | United States and other locations of the provider |
| Telegram | Notifications, approvals and the Telegram bot, where a customer enables them | The messages the bot sends and receives, and the account identifiers of the users who talk to it | Global network |
| LiveKit (LiveKit Cloud) | Real-time voice and video calls, including the call button of the website and the call features of the service | Call audio, video and connection data | Provider's cloud infrastructure |
2.1 Details of what each AI feature sends are in the AI Features Notice. A feature that is optional does nothing until a user uses it.
3. Integrations you connect yourself
3.1 Some features connect to services under an account that you own and choose to connect. The service you connect becomes a recipient of the data needed for the connection, under its own terms, and is not our subprocessor. Examples: Meta (WhatsApp Business, Messenger and Instagram), Twilio (SMS and WhatsApp), Google Workspace (Sheets, Drive and Calendar), and shipping carriers such as Nova Poshta. If you ask us to connect an integration, you instruct us to send it the data it needs.
4. Other recipients of technical data
These services receive technical data such as an IP address, but not customer business data.
| Recipient | Why | Data |
|---|---|---|
| GitHub | Hosts the release files of the desktop edition; update checks go there | IP address and program version |
| ipify.org, ip-api.com and get.geojs.io | Public lookup of a public IP address and its approximate location, used (with consent) by the website call widget | The public IP address |
| ipwho.is | Looks up the approximate location (country and city) of the public IP address that a desktop licence status message came from. Our server asks it; the desktop does not | The public IP address |
| jsDelivr (cdn.jsdelivr.net) | Serves two software libraries to the website call widget (with consent, or when you press the call button) | IP address |
| Our own error-tracking server | Receives technical error reports from the service and the desktop edition | The error message, program version and screen; scrubbed of tokens, email addresses and long numbers |
5. Website tools (we are the controller)
5.1 Google Analytics and Google Ads (Google), Microsoft Clarity (Microsoft) and the Meta Pixel (Meta) run on texacore.ai only if you consent. They are described in the Cookie Policy.
6. Changes
6.1 We tell customers at least 30 days before adding or replacing a subprocessor, by email to the account administrator or by a notice in the service, and we update this page. Customers may object as set out in section 6.2 of the Data Processing Agreement. The version number and effective date are at the top. Questions: [email protected].