Brimlo · autonomo.space
Providers and data processing
Named service providers and the functions for which data is shared.
Last updated: 2026-10-22
Scope and provider chains
The table describes service providers used by Brimlo's implemented functions. Optional integrations and communications apply when enabled or requested. A service name is not a separate direct contract with every company in its infrastructure chain: Lovable's own subprocessors and current contracting entities are documented in its linked provider materials. Paddle acts under its own privacy notice as Merchant of Record. User-selected integrations and analytics have their own roles and terms.
Locations and contractual safeguards
Provider establishment, the location of a database and the location of AI processing are different facts. This page does not label all processing as EEA-only. The Privacy Policy and DPA describe international-transfer safeguards and changes to subprocessors. Exact deployment regions, applicable contract coverage and provider retention settings must be checked for the service configuration; general provider documentation alone does not establish them.
| Provider / service | Function | Data involved | When used |
|---|---|---|---|
| Lovable Cloud / AI Gateway / Emails | Hosting (AWS eu-west-1, Ireland), backend, document storage, AI routing and system emails | Account/workspace records, files, selected AI context and email content | Core service and the relevant requested feature |
| OpenAI, through Lovable | Voice input transcription and IAE/CNAE activity-code suggestions | Voice recordings, activity name and description | You use voice input or ask for activity-code suggestions |
| Google Gemini, through Lovable | AI document recognition and AI answers | Submitted files, extracted text, prompts and selected context | AI functions, including document and Gmail recognition |
| Brevo, through Lovable connector gateway | Administrator-initiated CRM emails | Recipient address/name, subject, message and sending results | An administrator sends a CRM message |
| Paddle.com Market Limited | Merchant of Record and subscription payments | Checkout/billing data and transaction/subscription information | Paid orders and subscription management |
| Google Gmail / Amazon / Enable Banking | Connected email, marketplace and banking functions | Authorized integration data and credentials required for the connection | You connect and use the relevant integration |
| Google Analytics / Meta / Smartlook | Optional analytics, attribution and public-page session replay | Usage events, permitted matching identifiers and public-page interactions | The applicable cookie category is enabled; Smartlook is limited to landing/demo pages |
Lovable Cloud / AI Gateway / Emails
- Function
- Hosting (AWS eu-west-1, Ireland), backend, document storage, AI routing and system emails
- Data involved
- Account/workspace records, files, selected AI context and email content
- When used
- Core service and the relevant requested feature
OpenAI, through Lovable
- Function
- Voice input transcription and IAE/CNAE activity-code suggestions
- Data involved
- Voice recordings, activity name and description
- When used
- You use voice input or ask for activity-code suggestions
Google Gemini, through Lovable
- Function
- AI document recognition and AI answers
- Data involved
- Submitted files, extracted text, prompts and selected context
- When used
- AI functions, including document and Gmail recognition
Brevo, through Lovable connector gateway
- Function
- Administrator-initiated CRM emails
- Data involved
- Recipient address/name, subject, message and sending results
- When used
- An administrator sends a CRM message
Paddle.com Market Limited
- Function
- Merchant of Record and subscription payments
- Data involved
- Checkout/billing data and transaction/subscription information
- When used
- Paid orders and subscription management
Google Gmail / Amazon / Enable Banking
- Function
- Connected email, marketplace and banking functions
- Data involved
- Authorized integration data and credentials required for the connection
- When used
- You connect and use the relevant integration
Google Analytics / Meta / Smartlook
- Function
- Optional analytics, attribution and public-page session replay
- Data involved
- Usage events, permitted matching identifiers and public-page interactions
- When used
- The applicable cookie category is enabled; Smartlook is limited to landing/demo pages