This versioned list describes active providers that may process data to provide NeuroDisplay. The regions shown are possible and depend on the Plan and active configuration.
1. Supabase
Service: authentication, database, storage and edge functions. Purposes: application hosting, security and server execution. Data: accounts, Organization data, content, configurations and necessary logs. Possible regions: main project configured in eu-west-1; access or subsequent subcontracting according to the supplier DPA. Transfers: applicable contractual mechanisms, including adequacy or standard contractual clauses as applicable. Added: August 1, 2026.
2. Vercel
Service: Web hosting, broadcasting and technical functions. Purposes: to serve the site and the application. Data: queries, IP addresses and technical logs minimized. Possible regions: EEA and third countries depending on the Plan and infrastructure. Transfers: Supplier DPA and applicable guarantees. Added: August 1, 2026.
3. Resend
Service: transactional emails. Purposes: invitations, security, billing and Support. Data: sender, recipient, subject, content and delivery metadata. Possible regions: Ireland and United States depending on supplier functions. Transfers: DPA and applicable contractual mechanisms. Added: August 1, 2026.
4. OpenAI
Service: artificial intelligence functions activated by the User. Purposes: generate or assist the requested content. Data: prompt, parameters and context strictly necessary during an explicit action. Possible regions: depending on API account, DPA and applicable conditions. Transfers: applicable contractual guarantees. Added: August 1, 2026.
NeuroDisplay does not reuse the Client's prompts for its own purposes and only keeps the results when they are saved by the User.
5. Non-active suppliers
Open-Meteo is classified TEMPORARILY_DISABLED_PENDING_COMMERCIAL_SUBSCRIPTION: no free endpoint is used commercially and no production calls are made. Cloudflare R2 for Future Document Library, GitHub, Mailosaur, unused Sentry, unused PostHog, development tools and local dependencies are not active processors of the Production Service.
Stripe maintains its own or contextual role for certain payment, security and fraud purposes and is not presented as a universal processor.
Version history
- subprocessors-2026-08-en-v1 - 2026-08-01 - ACTIVE